MIXVIBES Dj Community old forum

In "1 Turntable mode" I can switch deck focus/vinyl control with the TAB key between the decks and everything works fine - I can alternating control both decks with one turntable.

But one thing puzzles me:
Both waveforms of the beatmatch view are always responding simultaneously to the movement of the vinyl! In result: if you match the tempo of two tracks, the beatmatch view indicates two different tempos - what is predictable, since both track waveforms of the beatmatch view are erroneously "hanging" on the same needle

Not so needle view and the complete waveform of the decks; they both follow correctly the vinyl movement on the focused deck and internal sync on the non-focused deck. And the audible output to the mixer is also correct - so this is more a visual issue and the beatmatch view can not be used for beatmatching.

What am I doing wrong? Or is the beatmatch view simply not designed for "1 Turntable mode"?

Thanks in advance for some info

Hi !

I don't really get it...
The beatmatcher displays the exact position of both tracks at their respective pitch values.
If both follow your vinyl movements, it means both players follow them too (then the music too) and the only way to get that is to connect one turntable to 2 inputs (using Y cables) -- or have a defective soundcard...

Please check your setup and maybe try to give me some further details about your problem, I may have misunderstood ...

Cheers,

You need to have only one external control activate.

Ah, I am getting a clue.

My normal config with 2 TTs is:
Deck input A: vinyl control from input 1 / 2 - Deck A output 1 / 2
Deck input B: vinyl control from input 3 / 4 - Deck B output 3 / 4

with 1 Turntable I configured:
Deck input A: vinyl control from input 1 / 2 - Deck A output 1 / 2
Deck input B: vinyl control from input 1 / 2 - Deck B output 3 / 4
(I thought these settings were managed by the "Only 1 Turntable" button... )

Now I will change it to:
Deck input A: vinyl control from input 1 / 2 - Deck A output 1 / 2
Deck input B: deactivated - Deck B output 3 / 4

Thank you for quuuuuuick response, will try this tonight

barren fell wrote:with 1 Turntable I configured:
Deck input A: vinyl control from input 1 / 2 - Deck A output 1 / 2
Deck input B: vinyl control from input 1 / 2 - Deck B output 3 / 4
(I thought these settings were managed by the "Only 1 Turntable" button... )

Now I will change it to:
Deck input A: vinyl control from input 1 / 2 - Deck A output 1 / 2
Deck input B: deactivated - Deck B output 3 / 4

Thank you for quuuuuuick response, will try this tonight

You should be ok.

Hmm, NO!
With the settings of Pic 01 I can switch over Vinyl control with TAB. The vinyl deck responds to vinyl movement, the unselected deck runs on internal sync and vice versa. One can see and hear that... everything is fine. But: both waveforms of the beatmatch view are always responding on vinyl movements!

With the settings of Pic 02 and 03 (differ in "1 Turntable" button) only Player 2 responds to vinyl control. Player 1 must be started via Play button and does not react on vinyl control, no matter what player is selected via TAB. Without saying the beat match view behaves normal: player 2 reacts to vinyl, player 1 plays straight on.

Soundcard and setup is OK since it runs as always - when activating both inputs everything is normal (2 TTs controlling separate decks)

Please keep in mind: this is not really a serious issue! I just thought it could sometimes be comfortable to carry around only 1 TT....Hmm, I will continue to carry around 2 TTs - it's cooler anyway

Please zoom in, since I can only attach one pic.

Oh sorry I was talking of Cross

Sorry from my side, didn't say that I'm talking of DVS

But good idea will try this with Cross just for fun (although DVS is my favoured child atm )

Ok I have tested and the only one setup that is possible and useable is the setup of the pic2.

When I scratch or pitch, there is only one waveform that is moving accordingly BUT (and you're right) both waveform are zoomed/stretched what I think is a normal behavior (will see with the dev).