as some know, I'm testing my protodeck controller with a m4L patch as interface with Live.
The hardware side is fast, tested, improved etc.
I tested it with midiOX and even if I turn pots VERY fast, no data loss etc etc.
(for those interested, I use multiplexed potentiometers and the scan frequency is ... 1000Hz)
so, no midi flow problem. I'm sure about that.
so.. the point
I mapped my pots by selecting midi flows like that:
and here is one of the sub-patch:
I feed the input with a midi in, tested too.The problem
when I turn the pots very fast, inside the patch, it works fine. the value change quickly (a little bit slower than my midi flow... not really slower, but with some fast jump... but it is fine)
BUT, in live............. strange things occur!
- if I turn it fast from minimum to maximum, without stopping it before the end of the potentiometer way, the value in Live changes but very sluggishly and, at the end of the potentiometer way, the value jump back to a lower value.
- if I turn it slower, it doesn't do that.
big lag time between the patch and Live through the API ????
I cannot understand why it does that.
I'd prefer to use live.remote~ but there are some issues unexplainable with that and I'm not sure it is the best way.
another thing I could do: midi mapping in live directly.
but I'd like to have all my config in one file: the patch. not here, there, there and there, you know?!
any ideas? experiences? suggestions?
maybe I don't use live.object
correctly or my patch is a bad nOOb patch