I’m trying to use Ch1 CC64 as a sustain message for all midi instruments in Ableton. Seems simple enough, but though the translation is making it through, nothing is sustaining. Somehow in the recent past I’ve been able to get it to work intermittently, but now it’s consistently inoperable.
Hi, I would need to see the incoming log also. It appears you don’t have sustain-on in your outgoing log so you may have a problem with one of your translators.
Sustain-On would be B0 40 7F - Which I don’t see
Where Sustaion-Off is B0 40 00 - Which I do see.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
OK, so you are getting MIDI from your Morningstart MC6MK2 on MIDI Channel 8 with value of 7F (127). Are you trying to control your sustain with that device? I suspect that Ableton is looking for MIDI CH1 .
Also your device selection for your translator may be wrong. I would need to see the relavent translator of your project file.
If you check MIDI IN, MIDI OUT, Incoming, and OUTGOING. In the log window and then press and release sustain, we could see what is happening and whether it is being controlled by translators or a MIDI thru path.
You will see ‘Incoming’ if the trigger is in alignment with a translator, otherwise, you will only see MIDI IN.
You will see ‘Outgoing’ if the output is from a translator.
You will always see MIDI IN and MIDI OUT for any opened devices whether handled by a translator or the MIDI router (MIDI Thru path). (As long as it is MIDI data)
You also may need to address the proper device selection of your translator.
For more information about device selection, see this tutorial.
Edit: Translator 4.10 looks like it is converting from CC40 to CC1.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Yeah, I’m sending a MIDI CH8 CC64 through the Morningstar MC6 from another device (that for certain reasons has to send through CH8) and having Bome translate that into the MIDI CH1 CC64 that Ableton needs for the sustain message. I might be missing something, but it seems like everything is translating and the initial message is being swallowed, but Ableton isn’t responding to it.
I removed the aliases and simplified the port routes. My midi monitor is showing that Bome is translating the message from the MC6 correctly, but Ableton is still not responding to it.
The weird thing is that if I uncheck ‘remote’ under Ableton’s MIDI preferences for Bome, it works! …the problem is I lose functionality with most of my other translations. Hmmm…
You can use a different MIDI port for your CC64 function only with remote unchecked. Then send that to the port with remote removed and all other translator to the old port with remote checked.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Are you saying Ableton could recognize 2 different Bome ports? If so, that could definitely work… and how would I get Ableton to recognize that? (Sorry if this is basic stuff)
Yes, or instance, use alias “Ableton Remote” as an alias for BMT 1. Then use BMT 1 in Ableton with Remote On (for all translators except your Cc64.
Then alias “Ableton Track” for CC64 as “Track” without Remote Enabled and assign that toe BMT 2 for that translator and any other translators that you want to send to track only.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Ahhh, ok. Great! I’m still trying to wrap my head around routing vs. aliases. Would both be routed the same- say, from the Morningstar to Bome virtual port?
Yes, you can route your MIDI messages at the project level (default) then override the project routing at the preset level, and override both project and preset routing at the translator level.
For more information about device selection, see this tutorial.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz