can you be more specific? is this sysex messages embedded on a midi file or is it custom from the midi buses setup? are you saying some are missing and others aren't?
Hi
I went thru 10+ of my songs and I found one where the sysex remain. I can't see any pattern. It is MIDI tracks not MIDI bus.
I have an Yamaha Tx81Z where I have to have a program change + sysex + program change to make the change on the synth happen.
I hope this helps.
Mikael
I have to have a program change + sysex + program change to make the change on the synth happen.
two program changes? that's unusual and i'm afraid it's not well regarded under the qtractor model, where one track is one channel, is one program change. the latter is always sent at the beginning of the playback sequence and may interfer (or not) with any that is embedded on original midi file. that might well be the cause for your worries. but i'm not sure how that relates to missing sysex.
maybe a copy of one or two of the midi files that expose the suspicious behavior is of help here, for evidence right?
re. Attachment: qtractor song with missing sysex. verified with rosegarden.
i see... MIDI file's track 1 has only one sysex event (f0 43 17 13 44 7f f7) but apparently the imported clip length is not long enough to render it operational....
i'll try to investigate further and try finding a fix to this sort of heisenbug :)...
meanwhile, as a workaround you can just re-size the (tiny) clip to some longer length, by hovering the mouse over it's right edge, click and drag it to the right a quarter-note or two.
re. sysex missing from tracks
can you be more specific? is this sysex messages embedded on a midi file or is it custom from the midi buses setup? are you saying some are missing and others aren't?
byee
re. sysex missing from tracks
Hi
I went thru 10+ of my songs and I found one where the sysex remain. I can't see any pattern. It is MIDI tracks not MIDI bus.
I have an Yamaha Tx81Z where I have to have a program change + sysex + program change to make the change on the synth happen.
I hope this helps.
Mikael
re. sysex missing from tracks
I have to have a program change + sysex + program change to make the change on the synth happen.
two program changes? that's unusual and i'm afraid it's not well regarded under the qtractor model, where one track is one channel, is one program change. the latter is always sent at the beginning of the playback sequence and may interfer (or not) with any that is embedded on original midi file. that might well be the cause for your worries. but i'm not sure how that relates to missing sysex.
maybe a copy of one or two of the midi files that expose the suspicious behavior is of help here, for evidence right?
byee
re. sysex missing from tracks
Hi
How do I attach files?
re. sysex missing from tracks
How do I attach files?
you can attach files on the top post
byee
re. sysex missing from tracks
re. Attachment: qtractor song with missing sysex. verified with rosegarden.
i see... MIDI file's track 1 has only one sysex event (f0 43 17 13 44 7f f7) but apparently the imported clip length is not long enough to render it operational....
i'll try to investigate further and try finding a fix to this sort of heisenbug :)...
meanwhile, as a workaround you can just re-size the (tiny) clip to some longer length, by hovering the mouse over it's right edge, click and drag it to the right a quarter-note or two.
byee
re. sysex missing from tracks
might have been fixed/solved on svn trunk rev.3139+ (aka. qtractor 0.5.7.6+)
take note that this is a non-retroactive fix, meaning that the above workaround still applies for any prior sessions.
cheers
re. sysex missing from tracks
Hi
Thanks a lot!
Add new comment