Midi "file format" does not support playup or record over specific ports.
I am doing a sequenser, that will extend record and playup over multiple ports which i think is more common today then chaining "how do you chain a USB device...".
Should i just have a format that assign a port to the recorded / playedup events on ->tracklevel "it seem crazy to have on eventlevel in format?" and have some mode that default them to statndard port "whatever that may be...."?
The port on tracks could be added to events during the mixdown before playup?
I am doing a sequenser, that will extend record and playup over multiple ports which i think is more common today then chaining "how do you chain a USB device...".
Should i just have a format that assign a port to the recorded / playedup events on ->tracklevel "it seem crazy to have on eventlevel in format?" and have some mode that default them to statndard port "whatever that may be...."?
The port on tracks could be added to events during the mixdown before playup?
Accepted Answer
1
Undo
Votes
The MIDI file specification has two event types that can be used to specify a port for a track.
Have a look at the spec for details.
Have a look at the spec for details.
Jonas
changed the title from "MIDI ish" multi device sequenser format. to "MIDI ish" multi device/port sequenser format. — 2 years ago
Accepted Answer
1
Undo
Votes
The MIDI file specification has two event types that can be used to specify a port for a track.
Have a look at the spec for details.
Have a look at the spec for details.
Ok got you, thank you Eddie, i had no idea that ports was supported.
Can i ask what happen if the track port that is suggested in file is not found?
Maybe someone else like a fast explanation just like me.
http://midi.teragonaudio.com/tech/midifile/port.htm
Can i ask what happen if the track port that is suggested in file is not found?
Maybe someone else like a fast explanation just like me.
http://midi.teragonaudio.com/tech/midifile/port.htm
The MIDI file specification has two event types that can be used to specify a port for a track.
My understanding is there is only one official meta event defined in specs for specifying a port, the Device Name meta event. (On this site, go to Specs > File Formats > Standard MIDI Files > SMF Device Name and Program Name Meta Events.) But there was also a non-standard Port Number meta event that some versions of Cakewalk used, so you may encounter MIDI files or MIDI sequencers that use that non-standard Port Number event.
See previous thread Multi-Port MIDI and Multi-Channel MIDI.
(Be aware that the MIDI Technical Fanatic's Brainwashing Center gets various details about MIDI specs wrong. That page you linked to about the Device Name meta event says "In a format 0 MIDI file, it would be permissible to have numerous [Device] Name events". But the Device Name spec says "There should only be one Device Name [...] per track [...] Since a Type 0 Standard MIDI File has only one track, it can have only one Device Name Meta Event.")
0
Undo
Votes
Can i ask what happen if the track port that is suggested in file is not found?
If the port specified in MIDI file is not found, the DAW or sequencer should let the user decide which port to use instead.
0
Undo
Votes
My understanding is there is only one official meta event defined in specs for specifying a port, the Device Name meta event.
Thanks for the reminder. You are correct. According to the Recommended Practice #19, the "Device Name" meta event is the official method to use.
- Page :
- 1
There are no replies made for this post yet.
