I made this code change (
https://github.com/default-kramer/mixxx/commit/aaf3e1c96dc1cb3d91fcb905570a9d1a65a33e3e)
and was playing around with it last night. (The feature description is here
https://bugs.launchpad.net/mixxx/+bug/1180052) Everything worked great with
one exception. I am hoping that a more experienced Mixxx developer will be
able to give me some insight.
I have two decks stuck in loops. Assume the beatgrids are already in phase.
Pushing the new function (which I named "beats_translate_to_sync") should
have virtually no effect. And in the normal case, it doesn't - the beatgrid
may shift by up to 2 samples, but this does not produce an audible
difference when you re-sync to the new beatgrid. But only on deck 2, and
only when deck 2 quantize is turned on, it shifts by hundreds or even
thousands of samples - this is wrong, and very audible when you re-sync to
the new beatgrid.
Any ideas?
(I'll be busy this weekend so apologies if it takes me a while to respond -
I'll be back at this next week for sure.)
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
