So this is the first time I use the OT to send MIDI CC messages to another device.
I’m trying to control a volca beats.
I assigned channel 10 to midi Track #1, and CC 54 and CC 55 for the stutter time and depth parameters of the VBeats. If I turn the knobs it works as expected, and stutter is affected accordingly.
But if I enter a trig and p-lock them, it does not.
I know about OT’s inability to assign CC values to Scenes, but everything I have read so far suggests p-locks work OK for midi CC.
it does work, but are you assuming the plocks behaviour is the same as on an internal track, it is not !
if you plock internally you will get this (one p lock on 5 of 8)
_-
externally you get this
____---- (that’s just the first pass)
to get the same you’d need to plock on 6 to bring it back down
may not be your issue of course, just a thought
i guess you have the midi cc stuff sorted and working before locking as you say
Yes, i assumed it would be different, as you ascii-arted for me
I made it work, I have been having fun all morning with this.
On midi track 1, Note page, I set NOTE chan 10.
Then I configured knob A on Ctrl2 page for CC 54 and knob B for CC55 (these are called CC5 and CC6, and the CCs refer to stutter time and stutter depth respectively).
I press play. Volca beats starts. I tweak knobs A and B and stutter is modified as expected.
Now i enter, for instance, 16 triggers, and I p-lock different A/B values for all of them. Nothing changes.
So, it works, but only when i move the knobs, and not when i p-lock the values.
You might want to stick a MIDI monitor between the OT and vBeats, and maybe try running your pattern at a lower tempo to see exactly what’s going on under the hood. This will give you more insight & confidence about exactly what the OT is sending.
Also one very annoying thing about the OT’s MIDI is that when you lock CCs on the same track/trigs that you’re sending notes on, the CCs are sent -after- each note. This may be affecting how the volca handles the messages. If that is the case, one workaround might be to put the CC locks on a lower channel than the notes. For example, CCs on track 1 and notes on track 2.
Mmmm, how can I avoid sending notes on a trigger? Maybe that IS the problem, because I am not attempting to send notes. The MIDI implementation datasheet for the volcabeats is not really self explanatory for my mid-level MIDI skills.
[quote=““NO CARRIER””]
Mmmm, how can I avoid sending notes on a trigger? Maybe that IS the problem, because I am not attempting to send notes.
[/quote]
Ah, I think I get it now! If you don’t want to trigger a note, you should be able to create a trigless trig/lock on that step that only sends your CCs. I believe this is done by holding Function and then clicking the trig you want to set, although my fingers know this better than my brain does The light on the trig should turn green. Then you can set the locks as normal by holding down the trig key and setting the CC knobs where you want them.
There was a midi channel conflict. For instance, my volca beats was on channel 10, which I knew and had properly configured on the Note Setup page for midi track 1, and thats why turning the CC encoders worked as expected.
BUT on Project -> MIDI -> CHANNELS -> Track 1… channel was set to 1. I set it to 10 (or off, as i wont be sending notes probably)… and it worked.
That was the missing piece of the puzzle.
I wrote a small tutorial in Spanish, for those that hablan español
