Re: Cross fading

I imagine someone has already discovered this but I haven't seen it
mentioned here.. I have 2 CDP-CX260's which have the 'feature' where
you can set the 'Command Mode' for the first player to either 1 or 2
and the command mode for the second player to 3. When you do this the
first player detects the second player and you can start to control
the second player with the first player.

One thing I initially liked about this is you can run the audio output
of the second player to the first player and then from the first player
to your mixer. This effectivly cuts the number of audio outputs to
your mixer in half.

But.. I have discovered that when the players are in this mode the CDJ
cross fade doesn't work properly. As the manual states.. 'When you press
the play button on either unit, the operating player stops and the idle
player starts'. What happens is CDJ sends the signal to start the second
player to begin fading in the second song but this signal to start the
second player causes the first player to stop right away. In this mode
you arn't allowed to have both players play at the same time.

Question #1.. Anybody know a way around this ?

If you keep the players independent (Command mode settings of 1 and 2)
it works fine.. but you have 2 audio outputs to deal with. I can live
with this problem...

But now I'm wondering what happens when you try to put 3 players with
this 'feature' on the same Slink-e port. Will 2 of them go into this
master / slave mode. Or are the players smart enough to realize that
there are 3 players and allow them all to work independenetly ?

Question #2.. Has anybody put 3 players capable of this 'feature' on
the same port ?.. What happens when you do ? I realize you could just
put 2 players on each port but I want to be able to use the full capacity
of the Slink-e (12 players).

Seperate topic... but related to Cross Fading...
Colby.. I have convinced myself that their is something amiss with your
graphical representation of the cross fader in CDJ. CDJ itself is working
as expected and issueing the proper fade down / up and overlap values.
But the graph representing those settings doesn't look right.

When you start off with all settings of 0, each box represents 30 seconds
of time. This makes sense since this is the maximum fade up/down allowed.
Each click of the fade up/down represents 3 seconds. Each 3 second
click of the overlap setting results in 6 seconds of the two boxes being
hilighted.. This also makes sense since you are overlapping 3 seconds
from each player for a total of 6 seconds. If you set the overlap to
30 seconds you end up overlapping both 30 second player boxes.. This
is all cool...

Now it gets confusing.. If you select a 6 second fade down time, that
6 second 'slope' should remain whether you specify an overlap or not.
But if you look carefully you will see that the 6 second slope will
only represent 3 seconds of time when you specify an overlap value.

For example.. suppose you set a fade down time of 30 seconds, a fade
up time of 30 seconds and an overlap time of 30 seconds. What this
says is, 30 seconds before the song ends on player #1, start a 30 second
fade down on player #1 and a 30 fade up on player #2 at the same time.