Seems dumb I don't know how to do this by now but I've never really seen this topic covered in depth. I know there are many ways to go about this stuff based on posts here on the forum so I just want to get an idea of what I can and cannot do. I'm scouring the Contents menu of the manual and there seem to be a few scattered, semi on topic entries but I'm posting this in hopes of getting a few simple procedures, concepts and keywords for me to search about for.
 
Essentially I've done a ton of MIDI stuff from inside a project. Now I want to be able to yank MIDI clips/files/whatever from various sources (like other projects or clients or the internet or wherever I need) and get them inserted where I need. Converesely I want to be able to effectively and intelligently export MIDI clips/files. It's still all a little daunting but I think if I can understand how to manage a MIDI file outside of a project I'll be closer to happiness.
 
For now I have a very specific need. I have a project that has been sent to me. It is laden with MIDI files. I only need specific tracks from that project and I don't want to work in that project. I want to create a NEW project and get the MIDI files I want into that new project and hopefully import them exactly at the point on the timeline they appear in the original project.
 
I've seen Drag Drop to the Browser or Desktop mentioned. I've seen the MIDI option in the Export dialog options. These are all things I'll be exploring I guess but I want to hear from you guys how you all do it.
 
I personal prefer starting with whatever method gives me the most options so I can see whats up. Like I've seen a lot of reports about SysX data or controller stuff causing problems when doing things like this. Maybe there is a dialog that allows any unnecessary gack like that to be stripped on export (or import) without having to do it manually.
 
Anyway... that's just an example of the type of thing I'd be doing. Really though I just want to get a good handle on how all this stuff works so I'm not coming here bugging you guys. Just need a punt in the right direction whether it's in the manual or videos or if you guys want to post some general steps/procedures for me to try.
 
Another thing is one of the reasons I want to try this is to use my own VSTi's on stuff so I guess that would fall under Drum Map stuff? Ya? Right now I think I'd be taking a Kontakt drum part and trying to translate it to Addictive Drums or maybe BFD Eco. I know a lot of the time drum stuff uses the same notes to trigger specific things but maybe not. So, and this is of course less important than the import export thing, just wondering what I can expect with that type of instrument/sampler change between those specific programs.
 
Cheers, thanks and sorry if that's all kind of dumb and crazy. lol
 
;-)

Hi. Recently I just drag and drop from the browser, to wherever I need it. It goes for both MIDI and audio.
Others will probably have a more elaborated way of doing this

Zargg71
Hi. Recently I just drag and drop from the browser, to wherever I need it. It goes for both MIDI and audio.
Others will probably have a more elaborated way of doing this

Welp, if that works then it's 1 method added to the pile. I figured this could be done in this manner but have never tried. I am concerned it may drag along MIDI instructions I don't want but I will test it.
 
Thanks.
 
1 down... I'm sure probably a dozen other methods to go. ;-)

I would simply save the project that you received as a MIDI file. This will keep everything timed in relation to one another.  You don't want to use MIDI clips unless you don't care about their time line position. The other thing is simply load the resulting MIDI do not import it. This will preserve its BPM. You will want it to be a type 1 MIDI file so all the channels are on their own track. 
 
  

John
I would simply save the project that you received as a MIDI file. This will keep everything timed in relation to one another.  You don't want to use MIDI clips unless you don't care about their time line position. The other thing is simply load the resulting MIDI do not import it. This will preserve its BPM. You will want it to be a type 1 MIDI file so all the channels are on their own track. 
 

Thanks, John... but being the dum dumd I am I have no idea what any of that means.
 
If I saved this project as a MIDI file I'm not sure what would happen. The reason I want to avoid it (and start my own new project) is because the original project is HUGE and mapped out to a ton of instruments I do not own. I also only need a few elements out of the whole thing.
 
Usually, when dealing with audio projects that have been sent to me instead of using the CWP or CWB I create my own project and set it up as needed to match the original. Just much more stable that way I find. So perhaps that mindset is tripping me up. I want to treat the MIDI tracks like I would audio (set up the project and import the individual files).
 
Knowaddimean? Of course MIDI is totally different which... well that's why I'm here, hat in hand, again.
 
Perhaps you could elaborate a bit. Everything is helpful really because it gives me ideas to scour around the manual/program for. Once I get my foot in the door I can usually dig down and sort things out.
 
Thanks.

I'm with zargg71. The browser features have evolved over the different versions of Sonar and is getting more an more useful. Drag and drop has had some recent fixes and it now works properly both ways.

You can drag and drop internally from track to browser and vice versa as well as to and from the windows desktop.

Allows you to create a repository of small clips from larger ones ones as well as use existing clips to drop into existing projects. The browser also allows you to audition clips before you commit.

PS: I also think this is the type of stuff that might help other beginners. As you know I've been studying the program independently for over three years now and I guess I figured this type of thing would have crossed my path in all that time. It has not, at least not in any way that jumps out and makes immediate sense to me. I just don't think it's all that well documented. The people that know about MIDI are probably just used to it but a dinosaur rocker like me... well it ain't clicking so good.
 
I'm sure by the time this thread concludes I'll be smacking my forehead with a hearty "D'oh". Just haven't hit that moment yet. Heheh.
 
Cheers.

mudgel
I'm with zargg71. The browser features have evolved over the different versions of Sonar and is getting more an more useful. Drag and drop has had some recent fixes and it now works properly both ways.

You can drag and drop internally from track to browser and vice versa as well as to and from the windows desktop.

Allows you to create a repository of small clips from larger ones ones as well as use existing clips to drop into existing projects. The browser also allows you to audition clips before you commit.

Yup. Definitely gonna try that out. But if it's anything like the audio D and D it won't have the plethora of options a proper old school Save/Export does. Convenience is great and that may end up being the go to option in the end but I'm a curious little monkey. I want to "understand" I guess as opposed to simply grunt through it.
 
Thanks though. It may get me through what I'm planning currently.
 
Cheers.

Dupety dupe. :-/

Beepster

John
I would simply save the project that you received as a MIDI file. This will keep everything timed in relation to one another.  You don't want to use MIDI clips unless you don't care about their time line position. The other thing is simply load the resulting MIDI do not import it. This will preserve its BPM. You will want it to be a type 1 MIDI file so all the channels are on their own track. 
 

Thanks, John... but being the dum dumd I am I have no idea what any of that means.
 
If I saved this project as a MIDI file I'm not sure what would happen. The reason I want to avoid it (and start my own new project) is because the original project is HUGE and mapped out to a ton of instruments I do not own. I also only need a few elements out of the whole thing.
 
Usually, when dealing with audio projects that have been sent to me instead of using the CWP or CWB I create my own project and set it up as needed to match the original. Just much more stable that way I find. So perhaps that mindset is tripping me up. I want to treat the MIDI tracks like I would audio (set up the project and import the individual files).
 
Knowaddimean? Of course MIDI is totally different which... well that's why I'm here, hat in hand, again.
 
Perhaps you could elaborate a bit. Everything is helpful really because it gives me ideas to scour around the manual/program for. Once I get my foot in the door I can usually dig down and sort things out.
 
Thanks.

When you save the MIDI within a project via save as MIDI it becomes a standard MIDI file that can be loaded back into Sonar as just that. MID is a native file format to Sonar. Most people import MIDI files. That is not the right way simply load them as if they were a regular project.  When you saved the MIDI from the other project it also saved all the data about the MIDI in that project. When you load the MIDI file into Sonar it will preserve all the info about it.  If you import it the BPM is stripped so it can match the project its being loaded into.
 
Make it the base for you new project.