Cross DJ 3.0 possible bug in 'stupid mistake prevention'

[MrKite]

Hi,

I think this also happened to me also in version 2.6 but I never found what it was, now I have 3.0 running and found this:

When a track is playing it is protected from loading a new track in the same deck. This is a very usefull protection against making this stupid mistake that can cause your set to go down big time (the track that was rocking the floor is not only stopped, but also gone completely so you cannot start it again).

This is something introduced by CD-J and even before and is found to be a natural feature that you first have to stop (pause, cue) the track playing before you can load a new one.

Yesterday I had the 4 players loaded and changed my mind about the running order of tracks (I have the habbit of mixing A-B-C-D-A.....) so I grab the track that's loaded on deck D and drag it with the mouse to deck C but I release the mouse when hoovering over deck A that's playing and is the master track. Boom!, track A is gone and replaced by the track loaded on deck D, nothing is playing and the fader is all the way down, just like the settings for the track in deck D.

I experimented a bit more, had a track playing/master again and I selected a track in the playlist that is already loaded in one of the other decks. Press the "load" button in my controller, Boom again same thing happening.

I could reproduce this again and again, I can not load other tracks on the master/playing deck. Can you?

Sure this is a stupid mistake we should not make but still we do and we are used to being protected so we are maybe a little careless?

I hope you find the same behaviour and it is not some obscure setting I have made wrong in previous versions.

Jimmy

[RoJeC]

I can duplicate it. Really interesting to know if it is a bug or a feature. If the latter what would be the benefit...
Makes sense that a clone does have the same volume as the source by default so it is balanced in volume with the output.

[sylMV]

This is the 'Clone Feature', allowing to clone a playing track into another deck. Mostly used by those who mix in with only one deck (MIDI, or timecode).

[RoJeC]

yes it is the clone function. Your response did not mention the potential 'buggy' part of the question.

Issue is that when non-playing source deck is cloned to the active playing deck the result is that there is no playing deck. Must be anyones nightmare as this can happen by accident.

Shouldn't Security Enabled avoid to have the active playing deck loaded?

[sylMV]

Oh, my bad, I read too fast...

Security on this point could indeed bit better. That's not the first time someone report this as an unwanted behavior.

[MrKite]

Hi,

The clone feature is ok, I can see the benefit of it in some cases, it's just the loading on the active deck that results in all sound being stopped, and the disapearance of the active track as well.

Loading a track twice can be what you want (for the same reasons the clone feature exists) but it still should be prevented that it kicks out a running track. (in my point of view, this should always be prevented.)

Meanwhile, I will be carefull when moving tracks around with the mouse (or touchpad). As stated, this I do to keep the same direction of decks, that way i always know by intuition what the next deck is I have to start.

Jimmy