Vinyl control -- moving the needle but not position in song

[StW]

I am very much a newbie to all of this and I am not 100 per cent certain whether the mistake lies between chair and keyboard but I am at the end of my wits and here is the problem:

I recently bought a used Final Scratch 2 box. I am using it in combination with an old XP 32 bit machine. I found out that the Final Scratch time code vinyls are not doing the trick, so I switched to Serato time code vinyls which are supported in MIXXX. Now I set up the whole hardware and it is -- sort of -- working. I can listen to music and I can even scratch it. What I cannot do -- regardless of the fact the vinyl settings are on absolute or relative -- is picking up the needle, moving it a few millimetres in order to jump a minute or two. The song simply continues where it stopped when I picked up the needle. Is there anything I missed or did I stumble upon a bug?

[ywwg]

If you're in Absolute mode and the track isn't changing position when you move the needle, most likely Mixxx is not interpretting the vinyl timecode correctly. When you start the record playing and look at your vinyl preferences, you should see a nice green circle inside the quality graph, as well as a radar sweep showing the rotation of the record. If the signal is red, then Mixxx is unable to read the timecode on the record. Make sure that you've selected the right type of vinyl as well as the correct side of the vinyl -- there are separate options for side A and side B.

[Pegasus]

Also make sure you don't have a turntable outputting line-level signals plugged into a phono input on the sound card.

[StW]

Thanks. I found the problem. Mapping -- at least for me -- is only working with the b-side of Serato Scratch live. If all the settings are geared towards side a and I put side A one it still does not change to absolute mode. However, things are still not running smoothly. The signal is green, the radar is turning when I play music normally. However it turns orange once I am scratching. Also the data curve jumps back and forth a few tenths of a second while I am scratching. Changing latency seemingly does not have an effect. Any ideas?