Sending CC to Playbeat from Loopy Pro

setfield

Hi all! I’m using AUM and I’m having issues sending cc messages from a LP button to PlayBeat 3. Specifically, I’m trying to use a button in LP to change the Quick Preset in PB3. Results are inconsistent at best. I’m fairly certain I’ve got the routing set up properly. Have the CC set for each Quick Preset in the PB3 settings page. Loopy Pro and PlayBeat are each in their own AUM channel (audio channels, fwiw).

Anyone else had an issue with this or been able to successfully do something similar?

Thanks!

uncledave

Hi. Could you post a screenshot of the AUM MIDI routing matrix (snake icon in upper right of AUM main screen)?

Just to be sure, do you mean the actual settings page inside PB3, or do you mean the AUv3 controls in AUM (sliders icon in the PB3 window title bar)? The MIDI routing is different for each option.

Edit: Also, try routing the MIDI output from Loopy Pro to a MIDI monitor, to confirm that it's actually sending what you intend.

setfield

I think this is a bug. When I create a brand new session in AUM and make all the needed routes the very first press of a button in LP triggers the preset change in PB3 successfully. Same for a cc driven change of pattern in Patterning. However, any successive button taps have no effect.

I used a midi monitor and confirmed that the cc is being sent. I also see the vertical orange bar next to the PB3 (or Patterning) node when I tap.

Can someone else try and report back? Thanks!

setfield

Oh, and sorry… yes, the settings in PB3. There is no other way (that I can see) to change presets using cc in PB3.

espiegel123

@setfield said:

I think this is a bug. When I create a brand new session in AUM and make all the needed routes the very first press of a button in LP triggers the preset change in PB3 successfully. Same for a cc driven change of pattern in Patterning. However, any successive button taps have no effect.

I used a midi monitor and confirmed that the cc is being sent. I also see the vertical orange bar next to the PB3 (or Patterning) node when I tap.

Can someone else try and report back? Thanks!

Pay close attention in the midi monitor to the values you are sending. I helped someone a while back and the values they were sending were not what the receiving AU needed. They were sending on/off values (127 and 0) but the AU in question needed the preset number.

Some AU want an on/off pair.

setfield

I think I tried that to no avail. Has anyone else tried this and confirmed?

espiegel123

@setfield said:
I think I tried that to no avail. Has anyone else tried this and confirmed?

I re-read your post, are you saying it doesn’t work sending to patterning either?

And you have confirmed in the midi monitor that with each button press the expected midi is being sent?

setfield

Correct. MIDI monitor is receiving the messages but only the first message to change is getting through to the receiving app be it PB3 or Patterning. If I create a patch from scratch the first time I click a button to send a message it changes the preset but subsequent presses do not.

setfield

Here’s a video demonstrating the issue. I walk through all of the settings beforehand. I dearly hope that someone here will point a finger and show me what I’m doing wrong.

Interestingly, mapping the CC to show and hide or disable the plugin works when I map it to the CC being sent by the LP buttons. The issue is using the CC to switch presets using PB’s MIDI CC Mappings.

espiegel123

@setfield said:
Here’s a video demonstrating the issue. I walk through all of the settings beforehand. I dearly hope that someone here will point a finger and show me what I’m doing wrong.

Interestingly, mapping the CC to show and hide or disable the plugin works when I map it to the CC being sent by the LP buttons. The issue is using the CC to switch presets using PB’s MIDI CC Mappings.

Are you sure you are supposed to send values 1 and 2? And not value 127?

I don’t have playbeat but I do have patterning 3. Can you create a simple aum project that you think should work but doesn’t?

setfield

@espiegel123 said:

@setfield said:
Here’s a video demonstrating the issue. I walk through all of the settings beforehand. I dearly hope that someone here will point a finger and show me what I’m doing wrong.

Interestingly, mapping the CC to show and hide or disable the plugin works when I map it to the CC being sent by the LP buttons. The issue is using the CC to switch presets using PB’s MIDI CC Mappings.

Are you sure you are supposed to send values 1 and 2? And not value 127?

Tried both, actually. Neither work.

I don’t have playbeat but I do have patterning 3. Can you create a simple aum project that you think should work but doesn’t?

The project in the video is one I created after having this problem in another. I’ll create another and see what happens.

Thanks for your help!

setfield

Just created a brand new project and can confirm… The very first press of a button in Loopy selected the correct preset but any subsequent presses fail. See enclosed.

espiegel123

@setfield said:

@espiegel123 said:

@setfield said:
Here’s a video demonstrating the issue. I walk through all of the settings beforehand. I dearly hope that someone here will point a finger and show me what I’m doing wrong.

Interestingly, mapping the CC to show and hide or disable the plugin works when I map it to the CC being sent by the LP buttons. The issue is using the CC to switch presets using PB’s MIDI CC Mappings.

Are you sure you are supposed to send values 1 and 2? And not value 127?

Tried both, actually. Neither work.

I don’t have playbeat but I do have patterning 3. Can you create a simple aum project that you think should work but doesn’t?

The project in the video is one I created after having this problem in another. I’ll create another and see what happens.

Thanks for your help!

If you upload a project with patterning 3 and loopy, I can try it.

Have you been in touch with the playbeat developer?

wim

I don't have PlayBeat so I'm not going to be much help. I did watch the video carefully. One thing is for certain - there's nothing going wrong with Loopy Pro. It's sending what you've told it to. That means the problem is most likely that the values you're sending don't match what PlayBeat is expecting.

I agree with @espiegel123 that PlayBeat is probably expecting 127, not the values you have in the video. However, my suggestion is to try setting the value to 127, but then try adding a second midi message to each button with the same CC# and value 0.

The app may be expecting something more like a momentary switch on a foot controller. A momentary switch will send an on/off combination. Sending 127 followed by 0 may do the trick.

Another suggestion would be to try sending a Note instead. I see there's a toggle switch in the PlayBeat mappings to use a Note instead. Sending a note from Loopy would act like a momentary switch as well (a note-on+velocity value, then a note-off).

setfield

@wim said:
I agree with @espiegel123 that PlayBeat is probably expecting 127, not the values you have in the video. However, my suggestion is to try setting the value to 127, but then try adding a second midi message to each button with the same CC# and value 0.

The app may be expecting something more like a momentary switch on a foot controller. A momentary switch will send an on/off combination. Sending 127 followed by 0 may do the trick.

@wim, you’re my hero! That did the trick!

Another suggestion would be to try sending a Note instead. I see there's a toggle switch in the PlayBeat mappings to use a Note instead. Sending a note from Loopy would act like a momentary switch as well (a note-on+velocity value, then a note-off).

I will try that too. Thank you!