What is the difference between midi/intern/cc & midi/intern/cc thin?

#1

Hey!

Was just wondering what the difference between the regular cc object and the ones with the thin name is. For example midi/intern/cc & midi/intern/cc thin?

Thanks

#2

I think it filters out the double values.
so, instead of 1111111111111222222222222222333333333333333333333333355555555555555555 it just sends 1 2 3 5

#3

its automatically sends the data (at a max rate of 10 ms) if the 'cc' value has changed.
remember, midi/out/cc sends out only on trigger.

so I think 'thinning' refers to the 10ms update rate, whereas a out/cc could potentially send out at k-rate.

#4

Ok. I just realised I used the thin one for all my patches. I didnt notice any weird behaviour, though.....

#5

has different behaviour, but only really if your dealing with fast updates OR you are worried about jitter.
e.g. thin will mean you potentially wont get the update for 10ms, which you could easily 'feel' if you were linking a controller to a sound engine (via axoloti)

(I guess might be important for percussion timing too... as you potentially are getting 10ms latency, but id have to 'test' that with an external drum machine to see if it matters much)

#6

Yeah. Think I am going to test it too. Ill make the same patch, but without the thin.... and see if there is a huge difference.... ANy difference in DSP loads on these two?

#7

well midi/out/cc needs a trig... so depends how you generate that,
but thin is not going to use much resources its only a comparison for change and a counter.

#8

If you'd try to send out MIDI on the DIN port at k-rate, the output queue would explode quickly (in firmware, harmless for the hardware). MIDI on DIN ports only supports ~1000 midi commands/second.

#9

Axoloti Black MIDI anyone ? :wink: