Thanks to Geoff and Jason for their suggestions. The problem ended up being the sequencer sending a MIDI note to the DrumTraks to play on the same MIDI channel the Drumtraks was already transmitting on; causing the DrumTraks to get confused LOL.
I set the Drumtraks to a different Channel from the incoming key events and voila, problem solved! These songs were written by me in the 80s and so you can forgive me not remembering that I recorded all the Drumtraks "cymbal crashes" separetely. No problem if its playing live because there is not any MIDI being transmitted byt the Drumtraks.
Thanks for the help!
I set the Drumtraks to a different Channel from the incoming key events and voila, problem solved! These songs were written by me in the 80s and so you can forgive me not remembering that I recorded all the Drumtraks "cymbal crashes" separetely. No problem if its playing live because there is not any MIDI being transmitted byt the Drumtraks.
Thanks for the help!
Jay
set the type of the post as
Technical Question — 1 week ago
Hey, so an observation ...
- everything going good, triggering recording, etc then the Drumtraks plays a cymbal note C#3 and the Drumtraks STOPS sending MIDI to the Reaper recording track BUT the Drumtraks keeps playing; AND if I tap any instrument pad, it will start sending MIDI again to the recording
- somehow its getting a message to stop sending MIDI at the same moment it gets that note?? Maybe some how somewhere that note is set to a MIDI off signal or something AND you can see from this picture that all the notes are going along nicely until it gets that cymbal note and then you see the All Notes Off
... 07 you can see all is normal and recording properly
... 22 you can see that MIDI data has stopped coming into the track because Note C#3 was recieved (cymbal on the drumtraks)
... 24 I tapped a pad and the MIDI started up
Everytime Reaper gets a MIDI command to paly C#3, Drumtraks stops sending MIDI, every time I then tap any pad, Drumtraks will again begin sending the song right where it left off
Can anyone help?
Thanks!
- everything going good, triggering recording, etc then the Drumtraks plays a cymbal note C#3 and the Drumtraks STOPS sending MIDI to the Reaper recording track BUT the Drumtraks keeps playing; AND if I tap any instrument pad, it will start sending MIDI again to the recording
- somehow its getting a message to stop sending MIDI at the same moment it gets that note?? Maybe some how somewhere that note is set to a MIDI off signal or something AND you can see from this picture that all the notes are going along nicely until it gets that cymbal note and then you see the All Notes Off
... 07 you can see all is normal and recording properly
... 22 you can see that MIDI data has stopped coming into the track because Note C#3 was recieved (cymbal on the drumtraks)
... 24 I tapped a pad and the MIDI started up
Everytime Reaper gets a MIDI command to paly C#3, Drumtraks stops sending MIDI, every time I then tap any pad, Drumtraks will again begin sending the song right where it left off
Can anyone help?
Thanks!
Maybe not applicable, but I know there is a bug in Cakewalk where if a patch number is above a certain number, it will do weird things with bank selects before finally setting the proper patch. This all happens on the same tick, and isn't normally noticeable, but if you dive in to the midi data, it's clear as day. Wondering if maybe Reaper has a similar quirk with that specific note?
Try running Sema's test files and see if anything else does it as well. Files are towards the bottom, try out the "test-all-xxx" files.
https://github.com/jazz-soft/test-midi-files
Try running Sema's test files and see if anything else does it as well. Files are towards the bottom, try out the "test-all-xxx" files.
https://github.com/jazz-soft/test-midi-files
Jay
changed the title from Trigger MIDI Out Drumtraks vs MSQ Sequencer to Problem Solved! Trigger MIDI Out Drumtraks vs MSQ Sequencer — 1 day ago
Jay, glad you got it sorted!
Just for future reference, leave the original post as is and reply to it. It makes it much more useful for others who come across the thread later.
Not sure if you edited the whole thing or it glitched and lost the other parts? Your original question is gone, as are Geoff's replies.
Just for future reference, leave the original post as is and reply to it. It makes it much more useful for others who come across the thread later.
Not sure if you edited the whole thing or it glitched and lost the other parts? Your original question is gone, as are Geoff's replies.
- Page :
- 1
There are no replies made for this post yet.
