SF 9 , 10 AND 11 still have EXPORT REGION problems -Sound Forge - PC

Subject:SF 9 , 10 AND 11 still have EXPORT REGION problems Posted by: groovyone Date:1/28/2014 11:55:53 PM So I've been supporting SF hopeing that this issue with extracting regions was fixed, but it has been a bug and still after logging this multiple times this pretty important feature for game development still is not fixed. Here's what I've tried: 5.1 Wav file Create Regions (SF leaves this blank since SF8 which used to autoname) SF10: Extract Regions - this worked once to the folder - then crashes every single time afer using the same file and restarting SF10 SF11: Extract Regions on the same file : THERE ARE NO REGIONS TO EXTRACT. I add REGION NAMES 01, 02, 03 to all the regions in the meta data. Try Extract REgions again : THERE ARE NO REGIONS TO EXTRACT. This is really frustrating, becuase I just ensured there were regions to extract. I tried to bring this file back into SF10 - and tried extract regions - clearly there are 42 regions all named numerically. No crash, but no extraction - I have no clue what SF10 did. I try this again, different base file name I also tried typing the extract path as well as selecting it from the explorer window. Sometimes entering in a new path instead of using the old one that you used for the previous file or extraction will make the extraction work. I have noticed when creating multiple regions in mono, stereo, or 5.1 files, trying to extract them: 1. Same folder from same source file after the first time the regions were extracted causes crashes. Sometimes changing the path since the last time works, sometimes it doesn't. 2. Re-opening older source file with regions and extracting using a different path to than the previous time crashes or doesn't extract or ignores the new path. 3. Sometimes the long file name when turned off helps, but the path name I am using is even less than 32 characters so it's not a long path name issue. Very disappointing that Sony has not addressed or fixed this issue in 3 versions. There is some sort of memory issue with pathing and previous extractions from a file. Not sure if this is being stored in meta data or in windows registry somewhere. The code for SF8 was a lot cleaner, the extract regions worked perfectly without fail. SF9. SF10 and SF11 are very buggy in this respect. Please please, fix your code to extract regions! Message last edited on1/29/2014 12:29:22 AM bygroovyone.
Subject:RE: SF 9 , 10 AND 11 still have EXPORT REGION problems Reply by: iain_m Date:1/29/2014 7:16:42 AM I have experienced these exact problems too in SF10, working with both mono and stereo wav files. I've never been able to narrow it down to specific conditions that trigger the bug, but have found, like you, that certain files trigger the problem repeatedly. Sometimes moving the markers of the final region in the file solves the problem, although on other occasions trying to move the marker simply results in a crash. I'm very disappointed to hear that this is still happening in SF11.
Subject:RE: SF 9 , 10 AND 11 still have EXPORT REGION problems Reply by: groovyone Date:1/30/2014 1:18:48 AM These kind of work flow bugs would be a good priority. They affect quality of life. That's what I love about sound forge, it makes whittling at files a piece of cake. In this circumstance it tries your patience :)

So I've been supporting SF hopeing that this issue with extracting regions was fixed, but it has been a bug and still after logging this multiple times this pretty important feature for game development still is not fixed.

Here's what I've tried:
5.1 Wav file

Create Regions (SF leaves this blank since SF8 which used to autoname)
SF10: Extract Regions - this worked once to the folder - then crashes every single time afer using the same file and restarting SF10

SF11: Extract Regions on the same file : THERE ARE NO REGIONS TO EXTRACT.
I add REGION NAMES 01, 02, 03 to all the regions in the meta data.
Try Extract REgions again : THERE ARE NO REGIONS TO EXTRACT.
This is really frustrating, becuase I just ensured there were regions to extract.

I tried to bring this file back into SF10 - and tried extract regions - clearly there are 42 regions all named numerically. No crash, but no extraction - I have no clue what SF10 did. I try this again, different base file name

I also tried typing the extract path as well as selecting it from the explorer window. Sometimes entering in a new path instead of using the old one that you used for the previous file or extraction will make the extraction work.

I have noticed when creating multiple regions in mono, stereo, or 5.1 files, trying to extract them:
1. Same folder from same source file after the first time the regions were extracted causes crashes. Sometimes changing the path since the last time works, sometimes it doesn't.
2. Re-opening older source file with regions and extracting using a different path to than the previous time crashes or doesn't extract or ignores the new path.
3. Sometimes the long file name when turned off helps, but the path name I am using is even less than 32 characters so it's not a long path name issue.

Very disappointing that Sony has not addressed or fixed this issue in 3 versions.

There is some sort of memory issue with pathing and previous extractions from a file. Not sure if this is being stored in meta data or in windows registry somewhere.

The code for SF8 was a lot cleaner, the extract regions worked perfectly without fail. SF9. SF10 and SF11 are very buggy in this respect.

Please please, fix your code to extract regions!