How do I export a Workspace?

[iMichael]

I have multiple workstations running Adobe Audition that need the same customized window layouts. I would like to export a configured workspace to be implemented on the rest of the machines. The objective is to ensure anyone using any machine has the same workspace environment.

If anyone has a better way of doing this I am open to suggestions.

[ryclark · Accepted solution]

You need to go to the settings folder for your version of Audition and copy over the Workspace folder that you will find in the settings folder. In order to discover the Audition settings folder click on the Help menu and select Reveal Log Files from the drop down menu. This will take you to the Logs folder within Audition's settings folder. So navigate up a level and you should see the Workspace folder that you need to copy to your other computers.

[iMichael]

Is there a native solution within the Adobe Audition software that will accomplish my objective?

[SteveG_AudioMasters_]

iMichael  wrote

Is there a native solution within the Adobe Audition software that will accomplish my objective?

No, I'm afraid not. If there was, ryclark would have told you. One of the reasons is that the method he mentions is relatively easy to implement across multiple installations, and if you think about it, it's what you would have to do with any other export; you've still got to move a file to the fresh installation and install it, whatever you do.

[Jean3561691748w8]

Hi Ryclark,

I've just updated from Audition 3.0 to Audition 2024. There might be 20 years in between the two versions.

I've tried to recreate my workspace from 3.0 to 2024 version but I didn't succeed. Tried your method (settings folder) but didn't find a 'settings folder' in Audition 3.0.

Attached is a JPG my workspace which I'd like to use in Audition 2024.

Could you, someone else, help?

Cheers,

JC

[SteveG_AudioMasters_]

Ryclark hasn't been around for a few years now, so I'm afraid you'll have to put up with me. 😉

Audtion 3 used the original Cool Edit PC-only codebase, and it was the last version to do so. Since then the entire package has been rewritten so that it's dual-platform, and the code is completely different. So I'm afraid that if you want anything since Audition 3 to look anything like Audition 3 used to, you have to create it for yourself - there's no way you can import any settings at all.

Look at it this way - if you do that, you'll learn something about manipulating the new software, rather than just having it handed to you on a plate. And that's a good thing, right?

[chrisb40390639]

Why can’t you use export customized application settings?

File>Export>Application Settings

According to the Adobe Audition manual: Application settings files store all current preferences, effect settings, and workspaces. Export and import these files to store groups of customized settings for specific workflows, or transfer favorite settings to another machine.

[SteveG_AudioMasters_]

chrisb40390639  wrote

Why can’t you use export customized application settings?

It depends upon the extent of what you want to export. It certainly exports basic settings, but if, for instance, you wish to export a custom preset in an effect, then it won't be there. If you do an export, you can open the .xml file and read what it exports pretty easily. Another thing you won't find in it is keyboard shortcuts you've assigned...

[ryclark]

Because, unfortunately, that information is not quite correct. Workspaces are stored in a separate folder in Audition's Settings and don't get included in the basic Application Settings file at this time.

I suspect that there is confusion between Application Settings.xml, which is what is exported, and the general Applications Settings folder which which contains many .xml files and folder describing the current customised set up of Audition. I think that the manual would be more correct in saying 'Audition's settings files store all.....'

[SteveG_AudioMasters_]

Yes it's definitely the labeling that's 'misleading' rather than the principle. It's useful sometimes to be able to select what you export, and the idea of keeping aspects of it in different folders is fine. Anybody propagating this will soon discover that - it doesn't exactly take a lot of reading of .xml contents to discover this, after all...