http://www.gnmidi.com/gnfreeen.htm sng extension,!,, man haven't seen that since my Atari died.
If N track does not have a mid. file export option then do this.
The link above has a conversion app you'll need to use to convert the sng. to a mid. file extension so Sonar can open it. It is best to "OPEN" a midi file to retain all data. If you import it you'll loose the tempo map and other sys, exclusive data.
wav. files can be imported or even just drag and drop them from a folder to a blank audio track. .
Some DAW software supports OMF import /export which lines your audio up ( in theory )
But generally each brand of DAW uses it's own format for files that contain both audio and MIDI so you have to manually import them in and re line the tracks.
I have copy pasted between Sonar and Cubase a few times.
You can OPEN the mid. file first, it will create a very plain project with all the goodies missing..( this to me is a design flaw) there will be a lot of blank midi tracks you can delete.
If you really want to use a template then the only choice is to drag and drop between the 2 programs or import and loose some data. Sometimes this is fine if all that's missing is tempo. Open a template that has enough blank midi tracks and copy paste from the other software.
Same for the audio, you can import it browsing the the folder that contained the wav. files. Or insert as many blank audio tracks you need , open the other software, highlight all the audio and copy paste to Sonar. If you do them in one big batch then the audio will all be lined up, even parts further down the time line. At least this works with Cubase and Sonar.
Then it's a matter of lining up the midi.
post edited by Cactus Music - 2013/04/20 11:56:23