Record sysex dump into track so it can be exported as midi file?

I had the same question - I think -

http://forum.cakewalk.com...;m=1943697&mpage=1

Go down a bit and there are some good links and ideas.

If you know all about the sysex page, you probably already know you can record and play back sysex data in tracks.

Maybe you just want to know how to save sysex in a .mid file.
Make sure to uncheck the global option "Always use sysx banks for midi files (instead of sysx data)". Then save your project with sysex data as a .mid file.

Bill B

I am bringing this thread back from the dead to further clarify the subject and question the OP asked.

From what I understand, the OP wanted to create a .mid file to be used as a dump for an external piece of hardware, most likely a synthesizer. Many DAW allow direct recording of SYSX data into a MIDI track, no matter what the format. Sonar X_ does too, but only controller-based SYSX data.  In other words, if one creates a MIDI track, sets up the I/O appropriately and then twists a knob on the synth/device, then Sonar X_ will record the SYSX. However, if the same is done a a DUMP is performed, Sonar X_ will not record the data. I find this odd, but it is what it is.

The .mid file is not only a widely used method of transmitting SYSX programming data to a synth/device, some patch managers/browsers (e.g. Virus Control) utilize .mid files for its patch libraries. Furthermore and in particular, Virus Control also requires .mid files for dumps from past-Virus models (e.g. A, B, and C models).

Therefore, without being 100% familiar with how Sonar X_ handles SYSX data, one could easily go bald pulling his hair out trying to dump a patch bank directly into a MIDI track.

The following Help Page is misleading. There should be a disclaimer about SYSX data from dumps. I have submitted a "feedback."
http://www.cakewalk.com/D...N&Req=SYSX.11.html

Sonar's actual way of recording dumps is much cleaner and easier than recording direcly to a MIDI track. Instead, Sonar uses a SYSX window/manager. It is a quite-convenient and somewhat-automatic process.

The following Help Page somewhat describes the process one could use to create that much-required .mid file as previously described:
http://www.cakewalk.com/D...N&Req=SYSX.10.html

Using what the Help Page suggests, a proper patch-dump .mid file can be created as follows:

NOTE: The following is how I created a proper, .mid file from a Virus C patch dump to be used for a Virus TI, using Virus Control. Your input/outputs and dump method may vary.

01. Start a new, blank project.
02. Insert one, MIDI track.
03. Setup I/O accordingly, if required.
04. Now open the SYSX window (Alt+Shift+7). It will open in the Multi-Dock.
05. In the SYSX window, ensure Bank 0 is highlighted and then click the File dropdown, then click Receive.
06. In the Request System Exclusive window, highlight <You start dump on instrument>, then click OK.
07. Sonar waits for the dump to begin. Perform the dump process on your synth, as required.
08. When dump is complete, click Done. All SYSX data from the dump is saved neatly within Bank 0.
09. Now right-click within the MIDI track and select View: Event List. It will open in the Multi-Dock.
10. In the Event List, click the + button to add a new event. The default should be a "note" event. This is listed under the Kind column.
11. Double-click the "Note" under the Kind column. A pop-up window appears. Change the Kind of Event to Sysx Bank then click OK.
12. In the MIDI track, move the created event to the beginning of the track (1:01:000).
13. Save the file as MIDI Format 0 and name appropriately.

That's it! Your new .MID file will work for several applications! Enjoy!