ctlin resolution troubles

May 19, 2006 at 11:00am

ctlin resolution troubles

i’m trying to patch something like relative-CC control (only take out
the value when it has reached the given threshold), but Midi values
aren’t decoded quickly enough for (several ways used : max only, java,
js…) : i have to slowly move my controller for Max to read it !!
Is this a known problem ? How do i solve it ?

best

f.e

f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> |sublime music for a desperate people|

#26056
May 19, 2006 at 11:02am

this is a [capture] from a quick controller movement :
11 21 31 41 52 63 75 88 101 110 117 122 125 126 127 122 115 105 93 81 69
57 46 35 25 17 10 6 3 1 0

that’s crazy…

Is it related to my 512 (12 ms) buffer size ?

f.e

#77394
May 19, 2006 at 11:26am

why don’t you try a line ???

could help

best

kasper

#77395
May 19, 2006 at 4:39pm

On 19 May 2006, at 12:02, f.e wrote:

> this is a [capture] from a quick controller movement :
> 11 21 31 41 52 63 75 88 101 110 117 122 125 126 127 122 115 105 93
> 81 69
> 57 46 35 25 17 10 6 3 1 0

Are you sure that the issue is not with the controller?

– N.

nick rothwell — composition, systems, performance — http://
http://www.cassiel.com

#77396
May 20, 2006 at 7:24am

Sure. I tried several (UC33, Korg Kontrol 49…). On the UC33 screen,
data is smooth & all here. Anyway, the line solution (how could i forget
about this) seems to be ok at 10ms (but you got 10ms latency…)

f.e

#77397
May 21, 2006 at 5:25pm

> Are you sure that the issue is not with the controller?

Or with the midi interface ?
I had same problems using the midi on a M-audio FW 410, every controls was so slow and indistinct, then I decided to use a dedicated midi device to have something acceptable (as much as midi can be…)

best

Eryck

#77398

You must be logged in to reply to this topic.