Subject:SF Mac 2 bugs so far.

Posted by: bman63

Date:2/9/2014 6:29:38 AM

-Check for update button dont work.
-Sound Forge 2 doesent appear in the launchpad app.
-Cant use Sound Forge att all in other user account.
-Cant hide the toolbar in full screen mode.

Subject:RE: SF Mac 2 bugs so far.

Reply by: JohnnyRoy

Date:2/9/2014 10:20:21 AM

> "-Check for update button dont work."

Same here. I get the error: "Update Error! An error occurred retrieving update information. Please try again later."

> "-Sound Forge 2 doesent appear in the launchpad app."

Unfortunately, Sony didn't call it Sound Forge 2... it's still Sound Forge so you can't have both versions installed at the same time unless you rename one of them. Unless you specifically told it to replace the other or keep both, it probably didn't install. Try uninstalling Sound Forge before installing Sound Forge 2.

It also has a new icon so if you're looking for the old icon you won't find it.

> "-Cant use Sound Forge att all in other user account."

No sure what this is, I only have one account.

> "-Cant hide the toolbar in full screen mode."

Works for me. I always work in full screen mode and there is no tool bar unless I hover my mouse at the top to make it display. It all works fine for me.

~jr

Subject:RE: SF Mac 2 bugs so far.

Reply by: bman63

Date:2/9/2014 1:23:25 PM

Yes when you install sound forge pro 2 and have a old sound forge pro installed it called it Sound Forge Pro 2 in the application folder.
It doesn't appear in launchpad when this is the case.
When you install on a mac that doesn't have SF 1 installed it called it Sound Forge pro and then it worked fine.
As for the toolbar in full screen,its SF's toolbar i meant. SF2 has both a toolbar and an editing toolbar but when its in full screen you can't hide the toolbar as you can the editing toolbar.
Hope someone understands :-)

Subject:RE: SF Mac 2 bugs so far.

Reply by: SonySQAPete

Date:2/10/2014 2:41:12 PM

1.) -Check for update button dont work.

That's been fixed.

2.) -Sound Forge 2 doesent appear in the launchpad app.

This is actually intended behavior that was discussed extensively amongst the team during the development cycle. The "Apple Way"™ dictates that the new version of Forge continue to use the same bundle ID as the previous version, leading to what you're seeing in Launchpad. Apple doesn't intend for users to have multiple versions of the same application living side-by-side on disk.

3.) -Cant use Sound Forge att all in other user account.

This is a known issue caused by permissions. Fortunately, there's a simple workaround. With SFPM2 installed in /Applications, open a terminal and type:

sudo chmod -R 777 /Applications/Sound\ Forge\ Pro.app/

(Note: if you have both apps in /Applications, you might need to type: sudo chmod -R 777 /Applications/Sound\ Forge\ Pro\ 2.app/ instead)

You'll be prompted for an administrator password.

4.) -Cant hide the toolbar in full screen mode.

This is by design. You'll note that even if you already have the toolbar hidden, it'll appear when you enter Full Screen Mode.

Subject:RE: SF Mac 2 bugs so far.

Reply by: bman63

Date:2/11/2014 3:30:28 AM

2.) Is the intended beahvior that you want me to use the SF1?
Because thats what i got in the launchpad. If you want the apple behavior you should get rid of the install choice to keep the SF1. atleast i think i got the choice when installing the SF2? i dont really remember.
Right now i got SF2 in dock and SF1 in launchpad. that can not be intended behavior.

4.) Full screen mode is intended to use all of the screen and its very good on small laptops. if you can't hide the toolbar what's the use? I think you should go the other way,like Safari to get rid off the favorites bar when in Full screen. right now,maximize the app window manually gets a bigger content.
ie.bigger music file look.

Subject:RE: SF Mac 2 bugs so far.

Reply by: JohnnyRoy

Date:2/11/2014 6:04:11 AM

> "This is a known issue caused by permissions. Fortunately, there's a simple workaround. With SFPM2 installed in /Applications, open a terminal and type: "
> "sudo chmod -R 777 /Applications/Sound\ Forge\ Pro.app/"

It should be noted for those who don't know that this "workaround" is very dangerous because it circumvents Unix security by disabling all permissions making these files "world writable" (a hackers dream). Sony needs to fix this with the proper permissions. Currently the permissions are not correct even for a single user because every file has the execute bit set which is also very dangerous.

Using chmod 777 is not the "Apple Way"™!

~jr

Subject:RE: SF Mac 2 bugs so far.

Reply by: JohnnyRoy

Date:2/11/2014 6:23:36 AM

> Posted by: bman63 " If you want the apple behavior you should get rid of the install choice to keep the SF1. atleast i think i got the choice when installing the SF2? i dont really remember."

There was no installer or option to keep SF1. In the true "Apple Way"™ when you mount the disk image it shows you the Program and the Applications Folder and you just drag and drop the program into the folder to install (as it should be).

That should have given to the choice to overwrite or keep Sounds Forge Pro.

If you answer "Keep Both" you should have both after the copy. If you press "Replace" you get the new program in the same folder as the old program.

~jr

Subject:RE: SF Mac 2 bugs so far.

Reply by: bman63

Date:2/11/2014 6:59:57 AM

You just posted a pic of the option to keep both!
And yes i have both.
But not in the Launchpad! thats the bug.

Subject:RE: SF Mac 2 bugs so far.

Reply by: roblesinge

Date:2/11/2014 7:58:53 AM

bman, you're not listening. Pete said this is an Apple problem. Apple doesn't provision for you to have two versions of the same application sitting side-by-side. Both versions of SF for Mac have the same bundle ID. Therefore, you'll only see SF for Mac 1.0 in Launchpad. That's not something Sony can fix.

JohnnyRoy, By default, you already have executable permissions on an Application, since you have to in order to execute it. All the chmod command does is add read and write permissions for all users. You can also do this by finding SF Pro in your Applications folder in Finder, right-click and choose Get Info. At the bottom you can change permissions.

Subject:RE: SF Mac 2 bugs so far.

Reply by: bman63

Date:2/11/2014 9:00:44 AM

Yes i know this and i understand.
Still this becomes a bug who ever fault it is.
This is why im telling you here so others dont do the same faul as i did.
And yes if Sony would call it SF Pro 2 it would have been fine.

Subject:RE: SF Mac 2 bugs so far.

Reply by: SonySQAPete

Date:2/11/2014 9:26:06 AM

You could also just sub 755 for 777 if you're in an environment where you have concerns about the other users on the local machine.

Subject:RE: SF Mac 2 bugs so far.

Reply by: JohnnyRoy

Date:2/11/2014 5:59:22 PM

> Reply by: bman63 "You just posted a pic of the option to keep both!"

Yes, but that option is not coming from the Sony Installer, that is the standard Mac dialog box for any time you copy something into a folder were it already exists. So Sony did not give you an option to keep both, Apple did, but I understand that if you are not familiar with the Mac you might think that the Sony installer (which doesn't exist) was doing this.

> Reply by: bman63 "But not in the Launchpad! thats the bug."

Actually it's not a bug. At least not Sony's bug. This is because you have the same program name in two different folders and the launchpad thinks they are the same thing. You probably need to refresh the launchpad database. If you Google for: "mac refresh launchpad database" you'll find several tutorials. It will refresh itself eventually but when it does, both programs will say Sound Forge Pro just with different icons.

~jr

Subject:RE: SF Mac 2 bugs so far.

Reply by: JohnnyRoy

Date:2/11/2014 6:05:43 PM

> Reply by: roblesinge "JohnnyRoy, By default, you already have executable permissions on an Application, since you have to in order to execute it. All the chmod command does is add read and write permissions for all users."

No, it does more. 7 turns on read, write, and execute for all files. Read is 4 (100), Write is 2 (010), and Execute is 1 (001). All together they are 4+2+1=7 (111) all bits on!

While I agree that the application requires the execute bit, all of the text files and .plist files etc do not and this actually makes them executable so someone could edit them and add malicious code and it will happily execute when double-clicked on. This is very dangerous!

~jr

Subject:RE: SF Mac 2 bugs so far.

Reply by: SonySQAPete

Date:2/11/2014 10:44:19 PM

JohnnyRoy,

A 755'd text file would only be considered a "potential script" in the loosest of terms, namely because it's only modifiable by that file's owner.

I'm confident in saying that if someone has unfettered access to your own account on your local machine, you've got larger issues to address than the granular permissions of a text file buried within an app bundle. <g>

I'd be careful with the directions that you've provided, as they'd explicitly strip the execute bit from a slew of libraries and executables within the .app that require that bit. It'll leave you with a non-functional application. (It won't even launch. Were it to launch, none of the built-in plugins or processes would work, nor would the update framework.)

Please do me a favor and delete those directions from your post.

The issue with the permissions on the SFPM2.app was an unintentional bug that was introduced outside of our standard build system. This will be resolved with an update.

My directions were intended to provide a one-line workaround for a specific issue with an acceptable level of inelegance. That's not how we traditionally handle permissions, but it's a better option than asking users to wait for the update.

I'd invite you to to examine the permissions within our other app bundles if you have concerns. You'll note that they're correct.

Subject:RE: SF Mac 2 bugs so far.

Reply by: cmarolt

Date:2/21/2014 10:10:09 AM

- Does not seem to playback 48k files at the correct speed
- (Not a bug... lack of feature) No "insert loop" as it behaves in SF for PC.

Subject:RE: SF Mac 2 bugs so far.

Reply by: Adam M

Date:3/18/2014 2:16:15 PM

Hi everyone,
some stuff I've found (Mac OS X 10.9.2, SFP 2.0.1 build 190, Convrt 1.0.1 Build 98). Not all bugs necessarily..I'm generally very happy with the updates but still some little things could be improved on.

SFP

1) "open with" from finder will not include Sound Forge Pro as an option. You have to take the extra step to click on "Other" then navigate to the application. My other audio software is listed in the "open with" options so I'm not sure what the issue is here. This was also a problem in SFP 1

2) mono files playback only on Left headphone output. I haven't messed around with this a ton.. somehow I thought it would play back correctly (i.e. out both L/R) a week ago, but it isn't today. In preferences - audio I also don't see a way to route/remap this.

3) No way to save regions in mp3 files. When you make regions then save as mp3 they are lost. I guess this has to do with the mp3 format. The issue then is that SFP should warn when region data will be stripped due to saving.


4) Is there a way to rename audio files directly from SFP? I'm also confused about what exactly is the "name" of the file vs metadata stuff (may not be a SFP issue). For example, "Summary Information" has the "title" metadata which is not the same as filename. I guess that is working as intended?


CONVRT
1) Convrt seems to stall out when I try peak normalize about 40 files. It crashed earlier just converting from AIF to WAV but today that seemed to work. Normalize process seemed very slow (it made it about half-way through my list before it hung.. or maybe I just didn't give it enough time? It seems much faster in SFP. Peak normalize shouldn't be an intensive process, right? I went out for coffee to let it run on 40 files, approx 2 hrs of total material.. that shouldn't long to peak normalize, I think...)

2) I haven't noticed Convrt giving a pop up or notification or status change when the process is complete. That would be nice

3) Pressing "stop" leads to a crash. Program itself is unresponsive while processing: doesn't update status on file processing often; I think one time I tried scrolling through the file list while it was processing and that let to a spinning wheel.

4) Is there a way to overwrite files? I was trying to peak normalize into the same directory as source and it created new files i.e. XYZ.wav ---> XYZ (2).wav. I didn't notice an overwrite option but maybe I missed it...

Subject:RE: SF Mac 2 bugs so far.

Reply by: Adam M

Date:3/18/2014 2:35:59 PM

Ah- I might have figured out the hanging issues I was having in CONVRT. I had generated a bunch of audio files in Max/MSP but I didn't always remember to "close" the files after I made them (unfortunately losing the audio...). This meant that I had files like 68 KB in size that were effectively corrupted wave files. I removed those and the batch normalizing worked fine. Then I tested on one of the corrupted files and indeed it stalled CONVRT.

One other CONVRT request:
- a way to view file properties (i.e. format, sample rate, bit depth etc) within the file browser in CONVRT. like command-i.

Adam

Subject:RE: SF Mac 2 bugs so far.

Reply by: Adam M

Date:3/19/2014 10:45:35 AM

and.. I figured out the mono playback. It was simply the wrong settings on my system prefs in OS X.
/shame