Jittery midi CC from midiparse ?

[joachimpastor]

Hello, i'm trying to make a device controling my midi synths. It's the first time I use M4L to create a device.
I've already solved a first issue with my device, here : viewtopic.php?f=35&t=245102 thanks to "chapelier fou".


Basically, i'm using imp.midiin to get midi messages from a hardware synth, then midiparse to extract the CC messages.
I would like to have one pot per function. Each pot is controlled by the midi from the synth, but the same pot per function also sends CC to the synth, this way i can basically use my synth as a plugin, but still make presets and record automation using the real thing.

Midiparse sends a pair (CC + value), and I'm using a gate to filter the CC, to let the value through each corresponding pot.
The problem I'm running into : if i print the output of the CC+value coming from midiparse, the value always comes first, then the CC.

So if i touch the CC29 pot, and set it at value100, and then touch the CC30 pot wich is already set at a value of 20 (for example), the CC29 is going to jump from 100 to 20 (and then stay there). Basically it almost works but this jittering makes is not usable.


Is there a way around this ? am I going to wrong way ?

[chapelier fou]

First : use [route] instead of [gate].
Also, check [swap], and the use of a "$2 $1" message.

[[jur]]

Timing! Always make sure events' timing and order are correct.

[joachimpastor]

Hello, just to follow up on that, a bit late, i'm sorry.

it worked, i used the swap function and now it's all in order.

this forum is great, thank you for your time.

[chapelier fou]

this forum is great, thank you for your time.

Actually I find that this place is getting a bit better nowadays. It used to be awesome.
I still think that the m4l section should be, in a perfect world, filled with creative people sharing their patching issues/ideas.
Let’s make it together!

[joachimpastor]

for sure.
actually I've used the "route" instead of the "gate", as advised by you (gate has a maximum output of 100, and some of my synths use CC above 100 anyway, plus route is more elegant that gate for that purpose).

I've got my thing working good :
I can get infos from "midiparse", send it directly to route (don't even need to swap them, which was necessary with "gate"), then pilot pots on ableton, and this pot is itslef connected to "ctlout" to send the CC to the synth.

Now i run into another problem, it seems like i get an insane, increasing delay in my midi communication.
if i let the thing run for 20 second, with automation on 2 CC from ableton to the synth, i'll have 3 second delay, not just on CC but also on note communication.

Are the CC's overloading the midi channel ? is there a way to avoid that ? I had a similar problem a long time ago when i made a midi controler with arduino, my program was running so fast it would overload the CPU, maybe it's a similar problem ?

[joachimpastor]

I used "print" to monitor thing and i believe i know what the problem is, the value sent by "route" is 7 digit after the comma.

so on a ableton CC automation slope, the refresh rate and amount of info sent to the synth is overwhelming.

i'm going to try to fix that so it only increments full numbers.

[joachimpastor]

You guys must think i'm such a noob

Ok so i've tried converting the Float into integer, but it still overload the midi (with int instead of float).

If i change the pot type from "float" to "int", then it works perfect, but in ableton i get the nasty grid step for automation, really not practical.


What i found, that works, is to set the "update limit (ms)" of the pot from 1ms (default) to 13ms.


I'll take any advice you have, unless the update limit is the best way to fix this problem.



here is where I am at the moment :

[[jur]]

I still think that the m4l section should be, in a perfect world, filled with creative people sharing their patching issues/ideas.
Let’s make it together!

It used to be the case during the early M4L years. That's a general move, but it's particularly relevant regarding the M4L sub-forum: a lot of people did get used to other places (social medias... ).
Just tell them to come in here if you happen to use those platforms.

[chapelier fou]

I am not in front of the computer but my bet is :
Instead of going straight to the live.dials, use a [prepend set] object or a message “set $1” before live.dial. So you set the value without sending it. You’re probably making a midi loop.

[chapelier fou]

Also, if I may suggest two things :
Take the habit to use the [trigger] object instead of relying on physical arrangement of patch cables. Also, midi channel information is ignored in M4L patches.

[chapelier fou]

Oh, and the [int] going to message boxes is probably a mistake. When you do this, I believe it doesn’t bang the message contents, but rather pass the [int] value through the message box.

EDIT : I was wrong about this. My mistake.

[chapelier fou]

I still think that the m4l section should be, in a perfect world, filled with creative people sharing their patching issues/ideas.
Let’s make it together!

It used to be the case during the early M4L years. That's a general move, but it's particularly relevant regarding the M4L sub-forum: a lot of people did get used to other places (social medias... ).
Just tell them to come in here if you happen to use those platforms.

Interesting. What kind of social media ?
(I’m not on Facebook)