I am trying to have preset D01 of the monomachine activate Midihub preset 1, D02 activate preset 2 etc, though the monomachine sends out PC=48 at preset D01, PC=49 at D02 etc., which is too high a PC for Midihub to read.
Midihub seems to respond to PC=0 for preset 1, that I can send using a different monomachine preset (A01), which I can’t overwrite at the moment.
How do I make monomachine preset D01—D08 / PC=48—55 trigger Midihub preset 1—8? I tried using transform, turning PC=48 into 0 but that didn’t do the trick.
All it does is take your incoming PC, change it to CC so it can be remapped, then change it back to a PC to send it out.
A physical loopback is a trick to send messages out & back to Midihub so it sees them as external events.
(This is needed here cos MH only changes presets via PCs when they arrive from an physical port)
I’m expecting that selecting the same bank on my external sequencer will switch the preset accordingly, but when I try to switch bank both led lights of port D flash and nothing else moves.
In the MIDI monitor I can see that on channel 16 a Program Change message is being sent correctly (values 0 to 8). However, the preset does not switch on the unit, neither does it recall the editor project.
I also tried installing a previous version of the editor (1.15) to rule out the possibility that the latest firmware would be the cause, but that didn’t change anything.
…I think I got it, and your suspicion turned out to be right The device settings got somehow changed, and I have now set input port to D and then channel 16, and everything seems to be fine
I guess the question I had is why such settings have changed out of the blue, while I simply hadn’t used the editor for a few months. I did update it first thing though before using (also firmware got updated), not sure that was the reason
There was a bug in an earlier Editor version which would migrate these settings incorrectly. I recommend to upgrade the Editor first, then the firmware. Currently this sequence is not enforced, but I should probably make it enforced in future versions, to avoid similar problems.
Right, that makes sense. If I remember correctly it first updated the editor and then the firmware. Something got lost while migrating I also forgot myself which were the correct settings with this particular “loopback” setup, but I have made a note now, just in case.
Thanks a lot for the tip and for taking the time to program the patch for me.
The device settings got somehow changed, and I have now set input port to D and then channel 16, and everything seems to be fine
