Cannot 'Save As' without Studio One creating a new folder.

[madFloyd]

This is new behavior for me and I'm not sure if I caused this somehow or it's by design, but every time I 'save as' (which I do a LOT), Studio One creates a new folder of the same name as the new filename. Even if I choose the 'root' folder of my project, it insists on creating a new one.

Anyone have any ideas what might be going on?

 

[SwitchBack]

Maybe too obvious but did you change the name of the song to something not in the root folder already? You can't save the same name in the same directory twice. Maybe the warning is replaced by creating a new folder?

 

[Davey]

You don't say why you use Save As so much so this might not be relevant but are you aware of the "Save New Version" option in the file menu? It saves a copy of your project in the History subfolder which can then be recalled with "Restore Version".

Most of my projects end up with 3 or 4 versions in there. Typically an initial "sketch" containing lots of noodling and half-ideas, a basic arrangement with simple Presence instruments, a "final" arrangements (well, as final as anything gets...) and one where I've printed everything to audio and removed all the plug-ins so I can concentrate on final mix and master. It's a very civilised way to work.

 

[Trucky]

This is new behavior for me and I'm not sure if I caused this somehow or it's by design, but every time I 'save as' (which I do a LOT), Studio One creates a new folder of the same name as the new filename. Even if I choose the 'root' folder of my project, it insists on creating a new one.

Anyone have any ideas what might be going on?

Can you post some screenshots or a video link to show what you're seeing?

I've always been able to do a "Save As" to the same file or with another name (both shown here) without it creating new a new folder...

 

[SwitchBack]

Other thought: No write acces to the target folder. I've seen that happen sometimes with folders pulled in from the cloud or from a public drive.

 

[madFloyd]

Can you post some screenshots or a video link to show what you're seeing?

I've always been able to do a "Save As" to the same file or with another name (both shown here) without it creating new a new folder...

View attachment 1225

So, here I go doing a SAVE AS:


There is a subfolder there (Floydian 2025 June 27 Had to replace HOARD) that I did not create.

The only folder I want to save in is '2016-07-31-Floydian'

So I change the folder back and rename it (here it is just before I click Save):

So, you'd think it would reside in the '2016-07-31-Floydian' folder, but if I do Save As again, you can see a new folder was created and the song file is saved inside it.

 

[madFloyd]

You don't say why you use Save As so much so this might not be relevant but are you aware of the "Save New Version" option in the file menu? It saves a copy of your project in the History subfolder which can then be recalled with "Restore Version".

Most of my projects end up with 3 or 4 versions in there. Typically an initial "sketch" containing lots of noodling and half-ideas, a basic arrangement with simple Presence instruments, a "final" arrangements (well, as final as anything gets...) and one where I've printed everything to audio and removed all the plug-ins so I can concentrate on final mix and master. It's a very civilised way to work.

I suppose I'm effectively doing the same thing, just in an old school way - and that's really my laziness of not learning how that feature works.

 

[madFloyd]

Other thought: No write acces to the target folder. I've seen that happen sometimes with folders pulled in from the cloud or from a public drive.

I think you're on to something.

I can save multiple .song files in any of the 'new' folders, just not the original folder.