"Save to New Folder" bug in Fender Studio Pro

[commonchild]

Does anyone else experience any issues with Fender Studio Pro 8's "Save to New Folder?"

Specifically, when I save to new folder, it appends a value, incremented by 1, to the file name in the pool, so when I reopen, none of the files can be found. For example, a file named "drumloop.wav" will be changed to "drumloop(1).wav." They are all there, and get copied over, but the project is completely broken because it's looking for drumloop(1), but it's still drumloop inside the project folder. It breaks files for both the Media and the Samples folder.

I used to do this all the time in Studio One Pro 7. After I make a heavy project, that may have a lot of unused files, I like to save to new folder so everything I use gets copied over and I can safely delete the old project. I just spent a lot of time saving a bunch of projects into a new structure, and none of them load waveforms properly haha. Fortunately, I have a recent backup and was able to get it all back to normal.

I'm just curious if anyone else has noticed this, or could try a test for me and see if it changes the filenames in the pool. I ran a test in S1 7, and no issues either. This is happening in Fender...

Thank you!

I'm on macOS, 26.4.1
Mac mini m4, 16/256

 

[BobF]

Not seeing that in Win11/FSP8. The only difference is that the new folder, media subfolder doesn't have files that were previously 'deleted' from the song, but remained in the pool in the original folder.

Zero renaming of files

 

[commonchild]

Thank you for testing for me!

To clarify, it's not renaming the files, but the reference of the filename in the pool. I've attached screen shots of before and after the saving. The files all get copied over just fine with no name change.

Thanks again!

 

[Jemusic]

I have just saved a few folders from my drive enclosure (SATA 7200 rpm HDD's) over to a SSD using Studio Pro 8 and it all worked as normal. I also opened a large session from my SSD and saved to a new folder on the same SSD as well under a new name of course and that also worked as per normal. No renaming of files anywhere. Just a complete duplication and it opens normally also.

 

[Vocalpoint]

Just a complete duplication and it opens normally also.

Concur. Zero renaming.

Pro Tip - the only way a "(1)" would ever be tacked onto the end of the filename is if another one (with that exact name) already exists in the target "save" location. This is standard file collision logic within SP on any OS

What this implies (to me anyway) is that the OP is not actually saving to a new location rather "resaving" to the existing one.

VP

 

[commonchild]

Thank you for all your feed back! I really do appreciate it.

Concur. Zero renaming.

Pro Tip - the only way a "(1)" would ever be tacked onto the end of the filename is if another one (with that exact name) already exists in the target "save" location. This is standard file collision logic within SP on any OS

What this implies (to me anyway) is that the OP is not actually saving to a new location rather "resaving" to the existing one.

VP

True, and I know what you're saying, but I am definitely saving to a new folder. It happens to ALL my songs, even a test project with a few clips. I do the same steps in Studio One 7, and everything is behaving as expected. In any case, I sent a message to Fender to see what they say. It very well could be a problem with my system/set up, and not Studio Pro.

Thanks again!

 

[Vocalpoint]

Thank you for all your feed back! I really do appreciate it.



True, and I know what you're saying, but I am definitely saving to a new folder. It happens to ALL my songs, even a test project with a few clips. I do the same steps in Studio One 7, and everything is behaving as expected. In any case, I sent a message to Fender to see what they say. It very well could be a problem with my system/set up, and not Studio Pro.

Thanks again!

Some screencaps would help - but over here on Windows 10 - with SP v8.03 - I cannot replicate.

Every "Save To New Folder" works as designed for me.

VP

 

[commonchild]

Some screencaps would help - but over here on Windows 10 - with SP v8.03 - I cannot replicate.

Every "Save To New Folder" works as designed for me.

VP

Thank you. I posted a couple screenshots of the pool before and after on my second comment. I’m wondering if it could be related to macOS Tahoe. Sadly I am stuck on it for now, but I noticed one of the replies was using Sonoma. I appreciate you trying to replicate!

On a brighter note, this is the first time I’ve ever felt like reaching out to support after using S1 since version 2. Rock solid DAW

 

[Navar]

I've had something a bit similar. When doing "save to new folder", not all files got copied into the new project folder, I had to do "copy external files" afterwards. I can't reproduce it with a small test song but it happened several times and now I check this every time. Will keep an eye on it when it happens again.