MIDI Files Location?

I was wondering the same thing yesterday. I ended up dragging them from the project to my desktop so I could get to work. I'm still curious though.
 
Rocky 

KPerry
They are embedded in the cwp file.

Ok thanks so if Sonar ever cant be activated I would probably lose all my midi recordings?

I typically Drag and Drop my finished (sometimes even partial = verse, bridge, chorus) midi files to the browser for back up because if a Cakewalk project becomes corrupt, its all over. no way to recover them.
 
I also bounce down my midi tracks(or freeze them to audio for Drag and Drop) just in case because years from now, I my new DAW or system might not support those VST-I instruments or their sound library may not be loaded in my future system.
 
I posted a thread 2 years ago about how to back up and more importantly: Label tracks -
http://forum.cakewalk.com/Orginizing-Labeling-Audio-and-Midi-Tracks-m3448904.aspx

Reaper does it like that I believe: XML(?) files that can be edited to change data reliably.

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!!! 

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
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.