SF15Pro - regions converting to markers when saving the file

SteveMTNO wrote on 4/28/2021, 2:19 PM

This just started today. I'm using SF15Pro, build 45, Windows 10.

Normally when I work on a file, I'll use markers to mark the start of a track, then double click between them to create a region. This works as expected, but when I save the file, the regions turn to markers and I end up with double markers and no regions.

Any ideas/suggestions?

Thanks in advance,

Steve

Comments

Product-Owner_OOO_ wrote on 8/19/2021, 7:03 AM

Which file format are you using?

rraud wrote on 8/19/2021, 11:41 AM

Hi @SteveMTN, the 'region' marker may be hidden under an existing 'marker'(s), You can slide the marker or region to the side and delete it... Or.. use "Edit> Region list> Convert markers to regions", in which the original marker(s) is eliminated. A keyboard shortcut can also be created for this command as well, A another option is to create a script and add a toolbar icon.

btw, this behavior exists in the legacy versions of SFP, so it does not appear to be a SFP-15 (or build 64) bug.

SteveMTNO wrote on 8/19/2021, 9:11 PM

Build 64 seems to have fixed this issue.

SteveMTNO wrote on 8/15/2022, 5:40 PM

This issue just popped up again. I'm using SP15Pro, build 161. Here's what I'm doing:

I am working in a 24/192 file, .wav format. The markers are all in place. I double-click in between two markers to select the region, then I hit "R" to create the region. Simple and straightforward. I've been doing it for years.

Then I save the file (Ctrl-S), and the regions all disappear.

The file I'm currently working on has 26 regions. After the file is saved and I repeat the process above (just to try to create the regions again, since they disappeared), the regions start at 27 instead of 1, as if the 26 regions are still there - even tho they are not in the regions list.

I tried closing the program and repeating the steps above - same thing. Tried it twice, same thing.

I've seriously been doing this same workflow for YEARS. It worked yesterday. Nothing has changed on my system (aside from not being able to create/save regions in a file).

Overall, I've been happy with SF15Pro, but it's been pretty frustrating lately...

rraud wrote on 8/15/2022, 7:01 PM

Hi @SteveMTNO,
Confirm you have "Save metadata with the file" enabled in the 'Save as' window. I overlook this setting occasionally and wonder, "duh, what happened to my f__kng markers and regions"

SteveMTNO wrote on 8/15/2022, 10:00 PM

Hi @SteveMTNO,
Confirm you have "Save metadata with the file" enabled in the 'Save as' window. I overlook this setting occasionally and wonder, "duh, what happened to my f__kng markers and regions"

Hi rraud,

That was the first thing I looked for.. ;)

Yes - it's checked...

rraud wrote on 8/16/2022, 10:07 AM

Try resetting and clearing the cache. Unfortunately most of your custom settings will be reset to default as well. but you can at least back up the keyboard and display layouts in the Sound Forge Appdata system folder which is typically in C:\Users\--YOUR USER NAME--\AppData\Roaming\MAGIX\SOUND FORGE Pro\15.0. Or try a straight reinstall which should retain your settings but it may not help the markers/regions issue. Most other custom settings are in the registry.

SteveMTNO wrote on 8/16/2022, 10:32 AM

I'm beginning to think that SF15 is just 'flaky'.

Last night, I tried creating markers in a different file and it worked just fine. Then I went back to the file where I first had this problem again, created a single region, saved it, and it stayed there. Makes no sense.

I really don't want to do a reinstall, because that will reinstall the damned Update Notifier.

For now, I'm just gonna leave things as is and hope for the best. If it happens again, I'll post another comment here..

Thanks for jumping in to help, rraud!

rraud wrote on 8/16/2022, 2:05 PM

Some file formats like the Mac PCM format <.aif> does not support metadata (at least in Windows).
I do not recall ever losing metadata in any version of SF except by pilot error or when saving as a format that does not support it... there is an alert option though in "Options> Preferences> General"

SteveMTNO wrote on 8/17/2022, 9:26 AM

I'm just using basic 24/192 .wav files. Nothing out of the ordinary. I've been using them for years...

rraud wrote on 8/17/2022, 10:52 AM

@SteveMTNOI have tried different scenarios with sample rates, bit depths and from different versions of SF from other PCs and cannot duplicate the behavior . The only thing I can recommend is uninstall / reinstall using a third-party tool like 'Revo Uninstall' that can remove the left-over registry entries and other pertinent data the OS uninstall leaves behind, which can cause issues to reoccur.. Revo Uninstall has a pro and freeware versions. The free version is adequate in most cases, Unfortunately, it will also remove your custom settings like the SF 'reset, clear cache' procedure.
If you have not done so already, request a Magix Sound Forge Tech Support ticket.

PS - If you do not need to use 64 bit plug-ins, try using the x86 version of SF-15. Both the x64 and x86 versions will coexist, The second install does not count as another activation either and they share many of the same user settings.

SteveMTNO wrote on 8/17/2022, 2:19 PM

Well, I just tried it again and it worked perfectly....