On 03/24/2011 02:23 PM, shanx wrote: > > 1. 'rate' (the one which is set by scratch2 CO) falls always in range > > of -3.675 to +3.675 (afaik) > Okay, seems like I have resolved this one :-) > in enginebuffer.h, following is the change:
I did the same thing in the 1.9 branch since I couldn't do uzi scratching or back-spins on a controller without that value being upped to at least 20. (I set it to 50 in the 1.9 branch.) It works fine for me too, but I too would like to know from highers-up if there's a max value or if it's safe to remove the limit altogether? > One solution that I can think of is to take into account the number of > ControlObject::sync() calls in SoundManager. > ie, next time my scratch2 CO sets a value it will check if past value is > yet read by engine or not. So like an accumulator? It sounds like you might want to factor out the scratching code from the MidiScriptEngine and use it for the waveform scratching as well, since that code includes an alpha-beta filter which does exactly this accumulation & smoothing. The only catch is that it depends on being called at precise time intervals, and as you've discovered, QTimer is not up to the job. (We've been discussing how best to deal with this.) > Btw, I was looking in MidiScriptEngine, scartch2 CO is triggered at 1ms > by QTImer. This puzzles me, is the waveform motion in sync with > turntable rotations? I'm not knowledgeable with the waveforms, but my guess is that their motion is not tied to TT motion at all. They scroll at a fixed speed, referenced to 0% pitch. The only times the scroll speed changes is when scratch(2) or FF/REW are manipulated. The 1ms timer is an attempt to call the alpha-beta filter as fast as possible for best response, but it suffers from QTimer's inaccuracy causing speed jitter. Sincerely, Sean M. Pappalardo "D.J. Pegasus" Mixxx Developer - Controller Specialist ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
