stratman70
I am all about midi and soft synths except for all guitars and all vocals.
 

Thanks for info, I guess I have a lot of "back tracking" to do, LOL
Im pretty much same, i.e., midi and soft synths except for all guitars and all vocals.
Typically I dont need to access the audio folder but good to know audio is saved there in some form to recover if needed, I guess I just figured midi files were also somehow saved independently from project somewhere as well. (I guess thats what happens when you "assume", LOL). Since Im only in it for myself as a retirement hobby and not a career Im not big on documenting all the details, but would like to preserve recordings as best as possible. 

azslow3
So looking for the next DAW I had that question in mind, with a hope and least one DAW developers also think that data preservation should not be complicated and overall what can be simple should be done simple.  
For data preservation: why not save projects into READABLE text file? Including MIDI, FX presets and everything else? And in case someone still want all MIDI in separate MIDI files, why not make an option in the DAW to allow that?
Can it be that easy? Yes!
 

Thanks, I guess thats something like what I assumed was being done, I guess sadly there's not much collaboration between DAW providers, for the collective good of all music producers.
 
Thankfully there's people like AZSlow, Cheers.
 
 
(Ive also found Reaper to likely be my alternate DAW, particularly if I can use a utility like this)
 
Thanks all
   
 

Well Reaper is relatively inexpensive, and since there is the azslow tool in the works, there is no longer a reason to feel that your creative works are trapped inside of a CWP file!!! 

Beware SPLAT does NOT always save audio files when you amend them either.
I am in the process of migrating to Studio One and for some reason could not find the vocal chorus audio. So no problem I thought I'll just cut a bit of the front as it was silence thinking I'd get a new .wav file when I saved project but to my horror nothing was updated in the project folders apart from the .cwp file.
Now I'm wondering if all my latest audio files are in fact a current reflection of the status quo?
 
 

Right click on the clip, and select "Associated Audio File..." (last option). You will see from there the sound comes.
 
But you can use "Utilities/Consolidate Project audio..." to collect all WAVs in one place.
For new projects in Sonar (if you plan some), check "Preferences/File/Audio data" section.
 
Studio One is not bad, progressing and has deep hardware integration which works out of the box. But since you come from Sonar. Presonus history shows no willing for any kind of "openness": they have not even publish the protocol of old one strip Faderport, early attempts with Studio One API are frozen, older audio interface shows over a day decisions to abandon features, the latest audio interface shows not forced locking to own eco-system.
I hope you will never be forced to transport something out of Studio One.
 
Reaper is opposite: API is always up to date, project files are in readable TEXT form. Transferring projects there (latest tests show that Sonar 7 - Platinum files can be transfered) is going to take "4 clicks".  And in disaster case (we all know that can happened with anything), transferring projects out of it is also probably going to take "4 clicks".
 

azslow3
Presonus history shows no willing for any kind of "openness": they have not even publish the protocol of old one strip Faderport, early attempts with Studio One API are frozen, older audio interface shows over a day decisions to abandon features, the latest audio interface shows not forced locking to own eco-system.
I hope you will never be forced to transport something out of Studio One.
 

 
A misguided corporate greed proprietary thing? I think all DAW suppliers would benefit more by allowing more open transferring between them, I imagine the corporate giants are more compelled to prevent this than to open things up. Creativity is stifled when forced to conform and assimilated into one way of thinking and communicating, technology while providing more opportunities to the average person to document/record and convey our messages, is also in many ways is leading us to this end.
Thankfully the music itself is still open to our own interpretations (until we're all assimilated Borgs, LOL).
Cheers   

Most DAWs are concurrents. I have observed only several more or sell distinct DAWs: Ableton, Tracktion , (m.b. FL). All other are "fighting" on the same field. And any of them want preserve its own share of (as Craig has written many times) not so huge user base.
 
Different DAWs have different imagination how open they should be. IMHO ordered list:
1) Reaper. DAW generate C++ header file for its API. Basis libraries are open source. Developed by pro programmers, with very specific finance approach (no marketing, almost no design, no army of useless for the goal managers on S-Class). I guess other have a very good reason to "fear the Reaper"...
2) Ableton, Bitwig, (ex)Sonar. Relatively open, with API. Ableton Push 2 has complete documentation (not many modern hardware devices have that, but I should admit Novation publish documentation these days. May be Focusrite influence since they was not open before).
3) Cubase. They have made VST. And just for that they should not be at the end of the list.
4) ProTools. In general close, but since they are the "standard", many things are at least partially open (EuCON, HUI, there are converters for pt files).
5) Studio One... Have they made anything "open"? The investment into design and marketing is big. Probably they have learned how to proceed from Apple: make own eco-system, make everything simple, convince users that everything is exactly what users have asked for. "You do not need 32bit plug-ins". "You do not need hardware mixer in your audio interface". But read how well they write about that features (more precisely the luck of them...). You want to believe immediately  
 

azslow3
 
5) Studio One... Have they made anything "open"? The investment into design and marketing is big. Probably they have learned how to proceed from Apple: make own eco-system, make everything simple, convince users that everything is exactly what users have asked for. "You do not need 32bit plug-ins". "You do not need hardware mixer in your audio interface". But read how well they write about that features (more precisely the luck of them...). You want to believe immediately  
 

Well, one redeeming feature about Studio One is that the software team is based in Germany. 
 
Some of the programmers even came ever from Cubase, so hopefully they are not done yet!
 
Obviously that will npt change how the parent company views the openness of their products.  One can only hope that market forces will convince them to 'join the team'.
 
Come to think of it, there are/were quite number of notable music software programmers based in Germany, besides Cubase and PreSonus.  You have Ableton, Access Music (Virus), AIR Music Tech (started as Wizoo Sound Design), Bitwig,  eMagic (the original developer of Logic, acquired by Apple),  Magix (Samplitude, etc.),  Native Instruments, SoundCloud,  u-he (Urs Heckmann), Wolfram Franke (Tracktion Biotek designer, ex-Waldorf Music), plus the inventors of MP3... other various plugin devs... etc.   Good crowd to be in! 

azslow3
Right click on the clip, and select "Associated Audio File..." (last option). You will see from there the sound comes.
 
But you can use "Utilities/Consolidate Project audio..." to collect all WAVs in one place.
For new projects in Sonar (if you plan some), check "Preferences/File/Audio data" section.
 
Studio One is not bad, progressing and has deep hardware integration which works out of the box. But since you come from Sonar. Presonus history shows no willing for any kind of "openness": they have not even publish the protocol of old one strip Faderport, early attempts with Studio One API are frozen, older audio interface shows over a day decisions to abandon features, the latest audio interface shows not forced locking to own eco-system.
I hope you will never be forced to transport something out of Studio One.
 
Reaper is opposite: API is always up to date, project files are in readable TEXT form. Transferring projects there (latest tests show that Sonar 7 - Platinum files can be transfered) is going to take "4 clicks".  And in disaster case (we all know that can happened with anything), transferring projects out of it is also probably going to take "4 clicks".
 

Thanks for the tip unfortunately 2 separate vocal tracks are pointing at same file. Well as you say hopefully Studio One will not go bust as well and see what version 4 brings later this year.