A Rant about the exports functions

[Pougri]

I'm transitionning from Cubase to Studio one, and honnestly i'm in love with it. It looks like the same software, with so many QoL and stability improvement...

BUT

Seriously, what's up with the export engine ???

- No naming options, you're forced to use what S1 is set up to. I have to rename things manually after export, wich is a massive waste of time.
- No possibility to choose multiple "in between markers". It's either all of them, either none of them.
- No regions markers
- No queued render
- Stem export is counter intuitive (sometimes it takes the sidechain, sometimes not, sometimes it takes the sends, sometimes not).
- And many, many more.

It's decades late when you compare to other softwares (Take Reaper for instance).

I work in the video game and sync industry where i need to segment my music a lot and be very careful about naming things properly, and it turns me completely crazy. All the time i spare thanks to all the QoL options are lost when exporting.

I'm honnestly in awe regarding how little care is given to this part of the DAW. And looking at the features request list, i'm apparently the only one complaining about this ? How is it possible that so few people cares about that ?

 

[Vocalpoint]

Have to agree with you.

I work in the voiceover industry - where like you - it is all about the "naming" and Studio One/Studio Pro has been lax in this specific area for years.

It is so lacking for my work that I simply do not go into this Export area at all any more and simply drag all my "named" events to the Browser and use the Batch Convertor to create the deliverables.

It is fast, furious and on point - without any need to get frustrated.

VP

 

[Pougri]

It feels like everything i listed above is technically possible, but they are all workarounds. And i can't work like that honnestly, i need a clear interface with everything on it. Reaper is such a good example on this, i feel like i'm gonna spend some time configuring it for midi and just switch to it.

 

[Vocalpoint]

It feels like everything i listed above is technically possible, but they are all workarounds. And i can't work like that honnestly, i need a clear interface with everything on it. Reaper is such a good example on this, i feel like i'm gonna spend some time configuring it for midi and just switch to it.

Trust me - I spent months trying to incorporate this into my workflow and it is not possible without compromises. So much so that I was unwilling to waste anymore time. So luckily - I found a much better method and one that does not require any compromise.

Thankfully - Studio One/Studio Pro does offer many ways to do something and while I got lucky with my discoveries - this specific Export area needs a modern rewrite in a big way.

Without modern naming options like Wildcards, Named Events (based on existing names), (saved) custom export locations and so on - this module is essentially useless if one needs to export a lot of audio - in a very specific way to a very specific location.

It does however - "export" and I guess that is all Fender really cares about at this point.

FWIW - I do not know anyone in my line of work that actually uses this area for general, day to day stuff.

VP

 

[soundofdrums]

Trust me - I spent months trying to incorporate this into my workflow and it is not possible without compromises. So much so that I was unwilling to waste anymore time. So luckily - I found a much better method and one that does not require any compromise.

Thankfully - Studio One/Studio Pro does offer many ways to do something and while I got lucky with my discoveries - this specific Export area needs a modern rewrite in a big way.

Without modern naming options like Wildcards, Named Events (based on existing names), (saved) custom export locations and so on - this module is essentially useless if one needs to export a lot of audio - in a very specific way to a very specific location.

It does however - "export" and I guess that is all Fender really cares about at this point.

FWIW - I do not know anyone in my line of work that actually uses this area for general, day to day stuff.

VP

Can you expand upon your export method? I’d be interested to know what you do to get round it. I too feel like the export options are hugely limited for pro workflows.