Have a feature request or suggestion? Post your idea here!

Publicação

3 seguidores Seguir
0
Avatar

XDJ-1000 MK1 Hotcue BUG

HI,

I am facing a following bug on my 1000s MK1.

Scenario:

1) Playing tracks from USB drive

2) Auto loading of hotcues is enabled and works fine

3) Load a track from a playlist

4) Use NEXT button to load next track from the playlist

==> the hotcues are not (re)loaded for the new track and are still pointing to the previous track.

When I am loading the track from the browse menu using the encoder, its fine. Bug happens only when using the "next" button.

 

BTW: Would be sweet if you fix it so it works as expected and add some of that bloody new features when someone will be already messing with the firmware - it really will not kill him...

 

Thanks

thanks

Marek Respondido

Comentário oficial

Avatar

Not a bug, this is as designed to maintain a performance aspect for the player. Certain methods of loading a track will sacrifice features in order to load more quickly (eg. not loading the hot cues automatically even if that's your preference in the settings).

Pulse
Ações de comentário Permalink

Publicação fechada para comentários.

6 comentários

0
Avatar

Hi Pulse,

Sorry but the UX is terrible in this case - faster doesn't mean better....
1) The fact I am loading the track using the next/prev buttons doesn't mean that I want it without the hotcues at all (thats why I checked the "auto load hotcues" in the menu)
2) If THIS is a feature, why the old hotcues are not unloaded but the old hotcues having no context to the current track remain?
3) Using a dedicated button for the same function doesn't mean it should/want sacrifice a core functionality of the player - why pressing "browse" button, rotating the encoder and pressing the encoder should mean that I want to be able to use the hotcues, while directly loading the next track from the playlist should not allow me to do that and forcing me to call the hotcues?
4) The behaviour of the "auto load hotcues" should be consistent across all the ways of how the track is loaded.

Marek

Marek 0 votos
Ações de comentário Permalink
0
Avatar

I understand, and I've had the same conversation with the product planners, but their current view is to keep it as-is for a performance priority.

I don't necessarily see it was a bad thing to not unload the hot cues, what if you want to jump around in a performance?

The reason it would make it preferential in not loading hot cues when you use the knob to browse is you're spending significantly more time to do that than simply pressing "NEXT" and calling the next track in the playlist, so clearly you don't mind if it takes an additional moment to load the hot cues. If I were in a fast performance situation where I want to get from song to song, playing as quickly as possible, I'd rather have the ability to hit next, then start playing right away rather than waiting.

Pulse 0 votos
Ações de comentário Permalink
0
Avatar

No this also happens when loading via the encoder. Sometimes the hot cues seem to be loaded correct, sometimes the waveform shows the correct hot cues, but the blue buttons aren't all enlighted an the only loaded hot cue points back to a track played a few minutes ago. This can't seem right ?

Tobias Bauer 0 votos
Ações de comentário Permalink
0
Avatar

That's the way it SHOULD be, but seems to doesn't work all the time.

Tobias Bauer 0 votos
Ações de comentário Permalink