a.t. vish

The Patch info is in the MIDI track. I attached the screen shot of my MIDI data. Neither Format 1 nor 0, has the patch data line when I import back into Cakewalk. I ultimately am not importing this back into Cakewalk, Im importing it into a device that is going to read MIDI and send these patch changes to my HXFX pedal. I need a Patch change to be included.

The on going saga...so I jumped through a million hoops to finally get audio files and midi files exported with the correct time stamps to load into another device. But now I see that the 'Patch' changes in the midi data I had in my Cakewalk project (which triggered a Line6 HXFX to change scenes) are not included in the Format 1. I need Format 1 because I need the midi to stay with its associated audio tracks. I cant export 42 midi track individually using Format 0...WTF? Why would a midi export file not contain this Patch info?? I understand when you reimport it to Cakewalk, it automatically assigns the patch change to the channel, but its an EXPORT file. Presumably, one is taking it someplace else, other than Cakewalk.

Ya, thanks for the info. The next obstacle is the time grid. That is, each of these midi files line up with an associated audio clip in my project. When I export the multiple audio files, I need the midi data that is synced to also export in some way that I can drop into another device and have the midi line up correctly with the associated audio. I can export audio in various ways so that each audio file starts at time '0'. But I cant think of a way to also export the associated midi so it is also at time '0', thus lining my commands up with the audio file. I think I will have to simply transfer each individual set of audio and associated midi to a new project, starting at the beginning of a track, and export each set individually for this to work.

I have not seen a way to export multiple midi tracks of a project the same way one would export multiple audio tracks. I dont want just ONE midi file with seperate track info (MIDI Format 1). I have, say, 20 seperate midi tracks in my project, and I want to export them, and end up with 20 seperate midi files, so I can import them separately into another device that utilizes midi commands. What am I missing?

So, has anyone had trouble running Loom II in Cakewalk? Everything installs fine for me, but, after opening, it routinely crashes Cakewalk when clicking on the "Edit" tab in the synth. Sometimes, it has the typical error message about crash dump etc, but usually it just closes Cakewalk and thats it. Really unstable in my system for some reason. I think this synth is great, but AIR has horrible customer service. They have been no help and really dont care. Kind of confusing that I bought it thru ADSRSounds, but made by AIR, so confusing about who to contact. V

For some reason, I have had horrible times with installing ALL versions of Dimension Pro (so confused by all the versions and whether they are 32 or 64 bit, etc). For what ever reason, I had to reinstall Dimension Pro, trying to get some old projects working. I just installed every version of Dimension Pro in my old products page at Cakewalk, figuring what ever version the old project needs, it will access it. Dimension Pro installed but when it asks to register with the registration code, the registration code listed at my old Cakewalk account Products page, does not work. Im simply looking at the dialogue box that pops up with the serial number of the current Dimension Pro and I am copying and pasting the registration code that corresponds to the serial code (according to my Products list). And further, NONE of the registration codes listed for all the versions of Dimension Pro I purchased over those years will work, which I didnt think they would, of course, because they arent the reg codes for the corresponding serial number.

Yes, i set the sonar project tempo to match fruityloops, then import the wave file. And what you are saying is not the issue anyway. There is no "morphing" of a wave file when importing it. A wave file will always have the same tempo it was rendered at when one imports it into sonar. You can then change it by other means once its in sonar, but if your wave file is 50 bpm and you import it into a sonar project that is 72 bpm, its still going to be a 50 bpm tempo wave file. It just wont match your 72 bpm click tempo in sonar.

Im finding wave files that are exported out of fruityloops at a particular bpm, drift from a corresponding bpm when imported into a sonar project. I just checked this issue in reaper and i am not seeing the same thing. Infact, i exported the audio out of reaper and it is correct when i import it into sonar. So to be clear, my fruityloop project is 150bpm. I set up a sonar project same bpm/sampling rate, etc. Import wave files from fruityloops into the sonar project and they do not line up on the time grid and drift from the established 150bpm in sonar.