FR: MIDI File Program Change and Controller support for resized MIDI sequence start
-
- KVRist
- 332 posts since 26 Jul, 2012
to use a external MIDI sound module it's important, to support Programm change and Controller Commands from imported MIDI file.
Last edited by Hermu on Fri Apr 24, 2015 11:43 am, edited 2 times in total.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Any controller and program changes in the MIDI file are also imported.
Also see: http://www.mutools.com/info/docs/mulab/ ... anges.html
Also see: http://www.mutools.com/info/docs/mulab/ ... anges.html
-
- KVRist
- Topic Starter
- 332 posts since 26 Jul, 2012
yes, any controller and program changes from MIDI file are imported, but controller and program changes which are outside resized MIDI sequence has no effect to MIDI device.mutools wrote:Any controller and program changes in the MIDI file are also imported.
Also see: http://www.mutools.com/info/docs/mulab/ ... anges.html
example:
1.1.00000 Program Change 26 (outside resized MIDI sequence - gray font)
2.4.00000 Note D3 80 0.0.03750 (start of resized MIDI sequence - dark font)
in this case program change has no effect, but if MIDI sequence is not resized program change works.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Events before the start marker are indeed not played. I understand what you want to achieve. You could do this by moving the program change to the start marker position, or by moving the program change to a separate sequence and put it at the proper position.
-
- KVRist
- Topic Starter
- 332 posts since 26 Jul, 2012
what i mean is, that anyone who resize the start marker will deaktivate all program change and controller commands, but only played notes should be affected and not program change and all controller commands before.mutools wrote:Events before the start marker are indeed not played. I understand what you want to achieve. You could do this by moving the program change to the start marker position, or by moving the program change to a separate sequence and put it at the proper position.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
I know what you mean but i don't agree that there should be exceptions for events that are before the sequence start marker as that could create other complications.
-
- KVRist
- Topic Starter
- 332 posts since 26 Jul, 2012
but there are no complications if start marker is set on any position.mutools wrote:I know what you mean but i don't agree that there should be exceptions for events that are before the sequence start marker as that could create other complications.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
I'm sorry but there are no plans for changing the current behavior wrt that specific case.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Agreed. If I set a start marker, that is the start of the sequence. Any events before are not to be used. That's what I mean by sequence start position. If I set it after a program change, that's me telling MuLab not to play that event as part of the sequence. It's up to me to move the event if I want it after the start marker.
-
- KVRist
- Topic Starter
- 332 posts since 26 Jul, 2012
Ok, you're right.pljones wrote:Agreed. If I set a start marker, that is the start of the sequence. Any events before are not to be used. That's what I mean by sequence start position. If I set it after a program change, that's me telling MuLab not to play that event as part of the sequence. It's up to me to move the event if I want it after the start marker.