I just checked and answer is positive. So this shoud allow you to program external controllers for the various TR8s parameters. I just tested sending the Sysex
F0 41 10 00 00 00 45 12 10 5A 10 04 00 0A 78 F7
to the Midi port. This should set the pitch on the BD track to minimum.
Worked well, feel free to give it a go.
Hey Almost, I’m controlling my TR-8s with a Morningstar MC6…
I’m trying to send a next pattern message to start a pattern at the end of the current playing, as if you pressed a 1-16 pad button. I can’t seem to get it to respond to any SysEx messages to do this. Works fine with Realtime start/stop and I can change patterns with PC, but that doesn’t cue to play after. I can’t seem to get it to respond to any SysEx whatsoever.
Do you have any guidance on this? At this point, I’d be happy to trade/barter/compensate or offer my first born just to get this to work!
No luck with those 2 messages with the MC6 ( https://www.morningstar.io/mc6-mkii ). Looking into MidiOx now, I have to assume it’s something in the translation/conversion the MC6 editor does. I’ve taken a snip to show the process.
One thing I noticed while reading and messing about, is that the Device ID in the Utility screen says 17, rather than 10. Is that something of concern? No one seems to talk about it.
@Almost Thanks again, super helpful! TR-8s works perfect with MidiOx, stoked! I left the Device ID = 10 (It says 17 in the Utilities), as in the messages you provided, for anyone else that has that question.
Looks like it is actually a problem with what the MC6 sends.
Just to confirm, you were able to send this message via DIN MIDI and not USB, correct?
Last night it was actually on USB, but tried this morning with DIN and I confirm it works (sending from MidiOx to a 2x2 Midiface interface).
On MIDI device - interestingly mine is on Midi device ID 17 as well. Do you have Midi RX Edit = on?
One workaround idea might be, if you use a DAW, is to use the controller to send a simple midi message to your DAW and then have your DAW deal with the SYSEX.
Lastly, a very random one - I seem to recall the TR8s has a channel for receiving pattern changes - does that not work?
I picked it back up last nigh after some tacos, which always helps. Now it’s 100% functional!
MidiOx for the win! Vital for troubleshooting. The problem was with the MC6 message, which required an entry in the front to tell it how long(?) the message is. Funny enough, the Morningstar UI has a great tool for SysEx messages that I didn’t know about.
You’re totally correct about the RxEdit and pattern channel options. I was using a real-time message to stop/start and use PC #s for pattern changes with the TR-8s, which required all those settings to be correct. Problem was, they’re all instant and I couldn’t cue a pattern. Solved all that, THANK YOU!!!
My one man band will now rule the universe (or at least the bay area)! All thanks to you! I owe you a deluxe enchilada platter, in the least!
Also, if you’re interested… I’m syncing & controlling a TR-8s, Grandmother, Streichfett synth & Boomerang III, simultaneously & flawlessly with an MC6.
Hi mate, I’m very happy to hear I was able to help! Please share live-sets if you have them! one day I’ll might get enough courage to actually perform live
I think I would actually be willing to kill for a working template for TR-6S (or TR-8S) for the BCR2000…
Thinking about dipping my toe into this water since technically I am a software engineer I should be capable to make some progress… I also have an encore electronics Knobby lying around which could theoretically be programmed, although it only has 8 knobs…
I’ve had some success, eventually going the Midi Translator Pro / BomeBox route and now I have a fully functioning EC4 controller for my FM Percussion Model! Which is awesome. Thanks so much for the efforts above to document the SysEx messages as I certainly wouldn’t have been able to achieve this without those.
I’ve also set up controls for Reverb parameters, it’s really fun to suddenly switch the reverb type, for example between Ambient and HaDou and change the Pre Delay time, to create some cool effects. Now that these are all on CCs, it’s also really easy for me to sequence the changes from any sequencer, making the instrument quite a bit more flexible.
When connected to the PC, I was even able to listen for kit changes/program changes and store the kit number as a global variable. Unfortunately I’m not able to do this via hardware only, as the Sysex edit data only seems to be sent out over USB, not over DIN.
What I’m planning to do is listen for program change messages and at least that way for my songs/performance pieces I can get the kit number to update itself.
Now to laboriously map out all the other drums and effects. LFO Rate, I see you…
Hi, please do share your learnings.
I’ve been meaning to start working on a BCR2000 template with a view of focussing on instrument parameters to enable more hands on control.
Unfortunately, while the sysex messages work perfectly well while the internal sequencer is running, sending a few while note messages are being sent by an external sequencer, well it can’t really handle it. Dropped notes and such. Experimenting with some time delay, lower resolution so fewer messages are sent, and so on, gives some improvement but still not ideal. I will keep working at it, and any suggestions will be welcome.
I have spent ages trying to solve the same problem. I can’t sniff the variation changes when i press the buttons so i don’t know the correct format.
I managed to change patterns programatically (a python script) using commands found in this thread which may have to do as I’m spending way too long on this!