Subject:Re-occuring "freeze" some Process commands in SF10

Posted by: acole

Date:5/21/2014 1:18:42 AM

When I endeavour to use the Resample, Extract Regions and the M-bit+ dither commands Sound Forge Pro 10 fails to show the expected appropriate boxes for me to continue with the command operation . The word Resample.., Extract Region etc.. sits in a blue filled box on the screen exactly where I clicked on it. The spinning “working” thingo” appears and remains on screen forever. When I try to close the program by clicking the close file “x”, I get the “Not responding” message. Windows searches for a solution but doesn’t find one.
No resampling, dithering etc. takes place of course, because I haven’t specified the new criteria for the program to use. The program is simply frozen.
On trying to replicate this, I have discovered that if I open another file ( or the same file ) for a second (third etc.) time and go for example to Process> and click on that blue Resample box which has remained on the screen, I do now get the Resample box and can do the resampling of the file.
The problem is the blue Resample... box remains on the screen in its original position all the time- even when closing SF and then using other programs. I need to close down the computer to have this go away. Nothing happens if I just click on the labelled blue box. If I haven't saved recently I lose the latest edits when I shut down and re-boot. Something is not right- I shouldn’t need to do an initial failed try at the Resample etc. before I can then actually resample on a second try. I certainly don’t need this blue box on the screen all day.
The above behaviour occurs when-ever I attempt to use one of these 3 commands. (There may be other commands which I have yet to find which behave this way) . Most of the other normal editing operations perform as expected. Any help will be appreciated.
Alan Cole

Subject:RE: Re-occuring "freeze" some Process commands in

Reply by: iam1ru12

Date:5/23/2014 3:22:18 AM

I am having the exact same issue and I have found the same exact things to be true with the first time it doesn't work and the second time it does. As for other commands, the Normalize command is another process command that this is occurring with. I found that logging off will also fix the blue square remnant.

I use Acid Pro 7 and don't use SF Pro 10 on a regular basis. However, when I time stretch songs in Acid, I have found the Normalize process in SF Pro 10 very useful for correcting the clips that stretching causes. I haven't been stretching a lot of music lately so I can't say exactly when this problem started. I know that before 01/2014 that this never occurred. It started around February/March, but I didn't have the time then to research the cause.

In late April I started looking into it and happened upon a thread posted by humguy1 "Sound Forge 10 & 11 Freeze on Win7". I tried all of the suggestions that were posted in that thread, but none of them worked.

I bought SF Pro 10, and a Dell 560 running Win7 Pro, 64 bit all at the same time, around 4 years ago. Like I said before, I never had a problem until a couple of months ago. I have bought new photography software this year but I don't think they are the problem either. I did three clean installs of Win7 Pro on the Dell 560, with none of those programs installed and still had this issue.

I needed and wanted a newer computer. I now have a Dell xps-8700 with Win7 Home Premium. Before upgrading to Win7 Pro I wanted to see if I still had the same problems with SF Pro, and I do. So it's not Win7 Pro, it wasn't my old computer, and it's not the new software.

Similar hardware between the old and new computer are these four items, the first three I have had for a couple of years and the issue wasn't present with any them.

My sound card and 3 HDs.

Sound Blaster X-Fi Titanium HD, that I bought in 2012 and is installed on the new computer, Dell xps-8700. They rolled out a new driver update in February, but for it to be the issue, we would all have to have the same sound card. do we?

Seagate Baracuda HD (1TB) that was the old system HD (4 years old) and is now being used for file storage.

Seagate GoFlex Desk USB External HD (2TB) that I have had for 3 years.

Seagate Backup Plus USB External HD (3TB), new this year. It is only used for backups and it is not used for any of my working files. I mention this due to it being a concern that was raised in the humguy1's thread.

I use Adobe Photoshop, I believe Humguy1's final question was if anyone else used it. But as I said before, I didn't install Photoshop on two of the clean installs.

I uninstalled SF Pro 10 507 build and reinstalled SF Pro 11.b from the original CD, and that didn't help. But then there are all of those artifacts that stay in the registry, so the aforementioned doesn't really count SF Pro updates out of the mix. Except that more people would be having this problem if it the updates were the problem. In all of the previous clean installs, I used the 507 build download.

I am at a loss

Subject:RE: Re-occuring "freeze" some Process commands in

Reply by: iam1ru12

Date:5/26/2014 3:12:49 AM

I finally got it to work. No crashes since my last post.

Two days ago I uninstalled SFP10 and all associated plugins. All except Noise Reduction 2.0i, it wouldn't uninstall, it said that it was missing a .dll file, but wouldn't say which dll file.

I moved all of the AppData Local & Roaming folders for SF Pro, all Sony Logs, and FX folders to another drive. I didn't want to throw away all of my FX presets, so I moved them instead of deleting them. I deleted the Sony folder in the Program Data folder, not sure if that was needed or not. My goal was to clean out any and all SF Pro related folders and files w/o doing anything to the registry.

I installed SFP7 from the original CD, Noise Reduction 2.0, and iZotope's Mastering Effects that came with it, and registered all of them.

I installed Sony Noise Reduction 2.0b from a CD that I have. I purchased it when I bought SFP5, it was sold separately back then.

I updated SFP7. The reason I did this was due to SFP10 not working and I was going to use SFP7 for all of the processing commands that crashed 10. In other words, I was going to use both of them.

Then I re-installed SFP10 from the original CD, reinstalled Noise Reduction to 2.0i and to my surprise it allowed the reinstall, then I reinstalled iZotope's Mastering Effects and registered all of them.

Updated SFP10 to build 506. In reading the readme files for build 507, it seems that it is mostly an update for Windows 8. I don't know if the build 507 will work or not, I didn't try updating to find out. I'm trying to give a new SSD a break.

I have been trying to recreate the app hang, using files that I know crashed it before. So far, it hasn't crashed. I'm not sure which or what solved the problem, but...

After everything started working, I moved the FX folders back to my personal folders.

My hunch is that I didn't have all of the iZotope plugins correctly registered or registered in the correct order. I don't use the effects and I don't know if I registered the Mastering Effects by iZotope or not. As I said before, I have done three clean installs since the first of the year and registering iZotope's Mastering Effects wasn't at the top of my todo list. Maybe it should have been.?

Subject:RE: Re-occuring "freeze" some Process commands in

Reply by: rraud

Date:5/26/2014 11:02:42 AM

My hunch is: the iZotope plug-ins' got nothing to do with it... though the iZotope authorization is a pain.
Many times, just reinstalling the SCS app is enough.
FWIW, it's also recommended to clean the registry prior to reinstall.