MIDI assign with Blueboard (Fixed)

Jack

trust.but.verify wroteHello, I am having trouble getting MIDI assign to work with a Blueboard pedal board. I can successfully assign a button to a global "Play / Stop" command, so it is recognizing the device, but not with group-specific record or mute commands. So it will stop / start play, but not start a recording. Is this also related to velocity? I didn't know the Blueboard sent velocity information. Best, Michael

Hey Michael, sorry to hear this. The velocity bug is now fixed in version 1.1.2 so it shouldn't be that. What sort of commands are you sending out with the Blueboard? It's best to send out just one command per pedal. GTL supports note, program change and control change commands. Also Is it possible that you have set record to 'hold' rather than 'tap' in MIDI settings? It may be worth talking to krass, member of this forum. He has a Blueboard working well with GTL.

krass wrote ..The iRig Blueboard (which works great with your app by the way  :) ) only has 4 switches so trying to juggle resources a bit....

If you're still having problems just let me know and we'll try and resolve them. Cheers

trust.but.verify

Thank you. I tried a different way using an iPhone to generate MIDI (using Apollo). As before, global stop / start works fine. The "Loop 1 in group" remain problematic. When I set bindings with "Tap" nothing happens. When I set bindings with "Hold" I get some response. The screen will show "Mute" or "Clear" with a sweep-second hand animation, but then nothing is muted or cleared. Any ideas? This seems to transcend just Blueboard then.

Jack

Hey Michael, sorry for the late reply. Have you selected the group first? In the 'Global' bindings section you will find 'select next group' and 'select previous group'. Set one of those to a blueboard pedal to select a group. Once you have selected a group you will be able to use the 'loop in group' bindings. The selected group will have an orange boarder around it. You might find that this is not the best solution for you as the blueboard only has 4 pedals. That's one pedal for each loop in a group but non left to actually select the groups with. An alternative would be to select loops individually instead of selecting groups. e.g. Pedal 1: record selected loop. Pedal 2: mute selected loop. Pedal 3: select previous loop. Pedal 4: select next loop. Apologies for the rant!

trust.but.verify

Thank you, that did the trick. I think with four bindings for Select Next Group, Select Next Loop, Play/Stop Group and Record Selected Loop I can do what I need. I want to record a 16-bar verse, then straight-away a 16-bar chorus, then play them back under my control while I solo over them on guitar. I think I can do that with the four buttons and the bindings above. Loopy over time has added more specific actions for bindings (e.g. record then mute current loop then record next loop). To the extent you can add more of these, each button becomes more powerful and accomplishes what today takes multiple buttons. I appreciate your help!

trust.but.verify

Hello, I am having trouble getting MIDI assign to work with a Blueboard pedal board. I can successfully assign a button to a global "Play / Stop" command, so it is recognizing the device, but not with group-specific record or mute commands. So it will stop / start play, but not start a recording. Is this also related to velocity? I didn't know the Blueboard sent velocity information. Best, Michael