New to this but I think I've almost cracked it. Just one final issue to sort out that I just cant work out.
Situation
I have set up Bome to translate the sysex fader output of a fader on the Sh-01 Gaia into a controller number (controller 60 for the moment) so I can use it to control soft synths in Logic Pro.
Midi settings
Midi in port: Sh-01
Midi out port: Bome mid translator Virtual out 1
Here's my readout from the log Window:
19: MIDI IN [SH-01]: F0 41 10 00 00 41 12 10 00 01 17 1E 3A F7
20: IN 0.0 MIDI 14 bytes: F0 41 10 00 00 41 12 10 00 01 17 1E 3A F7, pp=0x1E qq=0x3A
21: MIDI OUT [Bome MIDI Translator 1 Virtual Out]: B0 3C 1E
22: OUT 0.0 Control Change on ch. 1 with CC#:60 (0x3C) and value:pp=30
In Logic pro i have hooked up 'Bome Midi Translat' in the Clicks and Ports. The logic midi activity readout shows that I am sending controller 60 and I can assign controller 60 to an internal soft synth midi assignment. So far so good.
But when I try to get Logic to "learn" this controller 60 as part of the controller assignment section within Logic so that I can use it globally or as a smart control, it doesn't read controller 60. It reads the original sysex output from the Sh-01 instead.
I tried the Bome Virutal Port 1 instead but it's the same issue.
Anyone know what is going on here? Your help would be much appreciated. Thanks
Hi, my guess is the last two characters in your example before the F7
1E - Is likely the outgoing value of the CC
3A - Is likely the Roland checksum
F0 41 10 00 00 41 12 10 00 01 17 1E 3A F7
So your input pattern should be
F0 41 10 00 00 41 12 10 00 01 17 qq pp F7
Then set the outgoing CC value to qq
You should be able to confrim this theory by changing the altering the incoming value of the fader and seeing which bytes change.
If 3 bytes change, then it would probably be:
F0 41 10 00 00 41 12 10 00 01 qq oo pp F7
In this case, usually the first byte is the MSB, the second byte is LSB and third byte is the checksum. When converting a 14 bit value MSB LSB to a 7 bit value, you lose precision but it would be more logical to use the MSB value only so that you use full range of motion of your fader.
Steve Caldwell Bome Q and A Moderator and Independent Bome Consultant/Specialist bome@sniz.biz
I have updated to the suggestion and the issue seems to be the same. When i put in the "oo" i don't get any output (just a list of inputs from the sh01) so I assume it's not that?
I expanded the controller assignment to show what is coming through and also a screen shot of the updated midi screen . see attached.
i can see your attachments. must be my browser. I tried the bmtp file. same issue. the knob still responds as if i am sending it sysex i.e. a bit wonky
the logic pro controller assignment value says this:
i tried filtering the sysex in the midi input filter in logic pro project settings but i think the controller assignments are made before the logic environment
Did you use the file I sent you or did you modify yours? If you want to block other SysEx, you will need to remove any MIDI thru paths and also set the swallow option on the translator.
i am using the file you sent. SH-01 Sysex-to-Cc.btmp is in the top left and you've added one transltor (Amp Env Attack Time) and have ticked swallow midi message on the input. There are no cabled connections on the midi router if that's what you mean re the midi thru.
I've tried attaching files through "choose files" instead of drag and drop
Hi, your attachments are still not coming through. What Browser are you using? If you need to send me an attachment, send to my email address below (until we sort this out).
I would like to see the log in MT Pro with all boxes checked. I would also like to see how you have assigned aliases and which ports you have opened at the project level. It may be that you are checking the alias and actually the port that it points to and you need to check the alias only.
Steve Caldwell Bome Q and A Moderator and Independent Bome Consultant/Specialist bome@sniz.biz