gavspav

I've just 'invested' in two Dj-Tech VTT-101 controllers to replace the DJ Hero Decks in my Scratch Yourself Stupid Installation.

The controllers spit out relative values I think, 63 for one direction and 65 for the other. If I count the values each way I get an approximate absolute value but it does drift a bit so I guess it misses some values.

Anyway I'm going to map the jog wheels to scratch a buffer. Previously I used groove~ - calculated the speed from the jog wheel data, smoothed it a bit and that was it.

I'm having a bit of a brain fart as the best way to do it with these new values so I thought I'd ask if anyone has any ideas or experience.

EDIT ** By the way I gave up on the DJ hero controllers because I have been chasing a bug for about 3 years using i2c and Arduino where the input kept freezing. Could never sort it out but I feel a bit dirty, trying to buy my way out of the situation! Even though it will only cost 30 quid and some time.

The controllers spit out relative values I think,  63 for one direction and 65 for the other. If I count the values each way I get an approximate absolute value but it does drift a bit so I guess it misses some values.

EDIT ** By the way I gave up on the DJ hero controllers because I have been chasing a bug for about 3 years using i2c and Arduino where the input kept freezing. Could never sort it out but I feel a bit dirty, trying to buy my way out of the situation! Even though it will only cost 30 quid and some time.


using-relative-jogwheel-data-to-scratch-a-buffer

I realise this whole thing is a bit dated anyway but here's what I've got so far: 

Using relative jogwheel data to Scratch a Buffer