by kugmo on 24 Jan 2014, 03:44
Current setup:
Samsung Ultra 5 (Intel i5), 4GB RAM 500GB HDD
Reloop Terminal Mix 4
Cross 2.6
Cross 3.0
-------------
I've been using 2.x for some time (more than 6 months, latest version of Cross used was 2.6) with the Terminal Mix 4 on this laptop with no problems. Standard TM4 mapping used.
I installed Cross 3.0. I used the TM4 mapping shipped with it, and right away noticed weird jog behavior on deck A.
1. Loading a track on Deck A works as it should. Upon pressing Play, however, the track starts up like it was on an old school belt-driven, no-slipmat turntable. Imagine pressing Start on a turntable with the record trying to spin up to speed, that's what it sounds like. Pressing pause also shows same vinyl-like brake behavior.
2. Loading the same track on Deck B, startup is instantaneous, no problems at all
3. I exported the mapping used on 2.6 and loaded it onto 3.0. Same behavior on Deck A.
Mappings were not altered in any way.
Thinking that it may be a hardware issue, I loaded Cross 2.6, loaded the same track on A and B, used the same mapping.
This time, Deck A did NOT show the same behavior on 2.6 as it did on 3.0, so i guess hardware is not the issue.
Reloaded 3.0, same map file, then the same behavior (#1 above) happens again
Everything runs fine except for that odd jog behavior on Deck A with version 3.0. I was suspecting a brake time setting or a CD jog mapping, but default values looked clean (A and B map settings matched, and there was nothing mapped to Brake-related functions).
Please note, that under the controller's vinyl mode, everything works perfectly. It's just under CD mode where this happens (deck A having a vinyl-like play/pause behavior), and only on version 3.0
I'm not sure where else to look at or what to do to fix this. The controller did not show this Deck A behavior under 2.6. Am i looking at the wrong place? Please let me know what else to check.
Thanks!