I'm an engineer who are developing a MIDI-embedded system. I'm wondering about "PORT" MIDI meta event when using Cakewalk.
With the previous version of Cakewalk such as "Cakewalk Professional Ver. 3.00", I could assign any port numbers for each track although I didn't install several types of MIDI interface. When I save my work to ".mid" file through "Save As" then, "PORT" information is recorded as a meta event "FF 21 01 xx" - xx is a hexadecimal value which I wrote -.
But with the later versions such as "Cakewalk ProAudio" or "Sonar", I
coundn't assign an arbitrary port number. I can get only the registered MIDI Port in the port selection list box. These MIDI ports are surely registered in the "MS Windows Control Panel". And in this case, "PORT" information is not reserved as meta event which is defined in SMF spec. I don't know how port informations are reserved when I use these tools and I really want to know how I can get them from ".mid" files.
Well, I don't want to play MIDI music through all the ports. Some ports will be used to send out pure MIDI-playing data and some for extra features.
For examples, I would like to take port 0 and port 1 for real MIDI-playing and port 14 for rhythm change informations and port 15 for mp3-related informations, and so on in my applications.
As I mentioned before, my application is oriented to MIDI-embedded system. I won't make MIDI files. I just propose making music directions to musicians. So I think that it will be very troublesome for the MIDI-musician to modify MIDI files with a hex editor. And many musicians don't be equipped with older version Cakewalk, now. ^^;;
Well, would you explain the MIDI port binary data when someone make a MIDI file by Sonar or newer version Cakewalk if possible?
Is there anybody who can help me?
Any reply, E-mail, or web site address will be welcomed.
I will check my E-mail at firstname.lastname@example.org .
I hope that there are many merciful guys.
Have a good day.