Hoping i can find some assistance here.
Here is the problem i am encountering…
I have TouchOSC setup to control multiple different midi CC messages.
For this example we’ll say ‘pitch bend’.
With a midi track armed, i play a note, use the pitch bend on TouchOSC and it works as it should.
If i record the same procedure, it records the midi note but does not record the pitch bend cc info.
To trouble shoot, i record the note, then (with midi merge enabled) i go back and record the pitch bend info.
Even though ‘merge’ is enabled, it creates a new part on top of the part containing the midi note. ALso, the new part does not contain any of the pitch bend cc info.
BUT…if i look in the midi list editor, all the pitch bend cc info is recorded way before bar 0. like at bar negative 950, and all at ONE moment in the time line.
Here’s a link to a video i recorded of the issue showing what i described above
(i could’ve used a simpler tone for this example, but it’s the patch i had loaded and was using for this piece)
Now, I only noticed this happening after updating the TouchOSC app on my iPad, but after talking with their support and trouble shooting, it turns out it seems to be a Cubase issue. In the process of trouble shooting, i noticed it works fine in Digital Performer and is sending the proper midi info by using their Protokol app.
Thanks to anyone that may be able to shed light on this.
Hi and welcome,
To me it looks like TouchOSC is sending wrong time message with PitchBend and MIDI CC messages.
I agree…but how it seems to work fine in my prev DAW Digital Performer is mind boggling. I am at a loss and it’s killing my creativity at this moment, as i rely on touchOSC for a lot of midi CC messages.
Here is the response i received from Hexler Support:
We suspect this issue is more related to Cubase than to TouchOSC - TouchOSC is sending pitch bend messages in your video, and despite the fact they are seemingly not being recorded into the timeline correctly, the pitch bend messages are coming in properly as shown towards the end of the video (when you show the MIDI input log). TouchOSC has no understanding of the Cubase timeline - in this scenario, TouchOSC is sending MIDI messages to the TouchOSC Bridge when you move controls, and these messages are sent to Cubase when TouchOSC Bridge is selected as a MIDI input in Cubase. What Cubase does with these messages is up to Cubase - TouchOSC is not sending any timeline data to tell Cubase where this automation should occur, so Cubase is assigning these negative timeline values to the input automation. As to why this is happening, we would suggest contacting Cubase support (or user forums if they have them) - again, from your video we establish that TouchOSC is sending the correct pitch bend messages to Cubase - what Cubase is doing with the messages (in this case causing this seemingly buggy behavior) is entirely up to Cubase.
**** UPDATE *****
I booted Cubase in safe mode, and created a new project, added ONE midi track and TouchOSC worked fine. What the heck is going on.
correction…it did not work.
Please, try to insert MIDI Monitor to the track. What can you see with the PitchBend here while playback? I would expect some timing issues here already. Could you attach a screenshot (or export it) of the MIDI Monitor, please?
It’s not first time, when there would be a timing issue on the 3rd party side, like this.
Ok here is the midi monitor screenshot:
This was played over a 4 bar amount of time and as you can see they are all being monitored at the exact same position. (and were placed at bar (negative) -101016.3.3
Thank you so far for the help!
Here is another midi monitor image. First set of CC1 is with TouchOSC , second with Keyboard modwheel.
There must be some timing issue on TouchOSC side.
Look at this old thread, please. The very same problem there. the solution was:
you need to connect a network session in Mac OS Audio midi setup
And here is other solution:
I closed down TouchOSC Bridge and used Osculator as the “bridge” and Cubase started recording the CC1 and CC11…
So what is Osculator doing that TouchOSC BRIDGE cannot do to make Cubase and TouchOSC talk to one another??
THANK YOU!..it seems, with a brief test, that turning off TouchOSC Bridge and using OSCulator is working. Now i just need to map every single thing i created in TouchOSC editor so OSCulator knows what to send Cubase. (that will be pain staking task). But thank you!.. I will return to Hexler now with this information.