Feature request: add a play_cue that doesn't overwrite the cue

[Damian Wheel]

To go to the cue point, we have two different shortcuts that do basically the same thing:

cue_play: "Go to cue point and play after release (CUP button behavior). If stopped, sets a cue point at the current location."

cue_simple: "If the player is not playing, set the cue point at the current location otherwise seek to the cue point."

play_stutter only plays from cue if the track is already playing, and cue_preview if they key is hold.

Could we have another one, that goes to the cue, plays from it (regardless if the track is currently playing or stopped), but DOESN'T overwrite it?

[Be (be.ing)]

I don't think adding even more complexity to the cue button is a good idea. If you don't like how it works, pick a different cue mode.

[Damian Wheel (tfwnogf)]

>I don't think adding even more complexity to the cue button is a good idea

You're definitely right on this, I've never used DJ software or even mixed in my life, and this whole cue thing got me really confused at start.
But this issue remains, after reading about all the different modes, I don't find a cue mode that goes for me (= just go to the cue whether it's playing or not, play from it, and don't modify it).
Unless you have a better idea about it and I missed something out?

Here in my custom shortcuts, I configured cue_set, cue_gotoandstop and cue_play. I just need something to replace cue_play that could ___just___ play from the cue.

[Daniel Schürmann (daschuer)]

We have cue_gotoandplay that might may match your needs.

However I have not yet understand how do you plan to use it.
Do you like to use your way of DJing from the skin/controller as well?

Please describe step by step how do you cue in a new track.

Btw: you can start mixxx like "mixxx --developer" this will enable a developer menu with a list of all Control Objects where you can edit them directly.

[Damian Wheel (tfwnogf)]

>We have cue_gotoandplay that might may match your needs.

Thank you Daniel, that's exactly what I wanted and I completely missed it in the docs!!

>Btw: you can start mixxx like "mixxx --developer" this will enable a developer menu with a list of all Control Objects where you can edit them directly.

I did use the --developer option earlier for a detailled bug report, however I haven't played around with it once Mixxx launched. That's good to know as well!

>Please describe step by step how do you cue in a new track.

Mh, I find a good spot in a track from where transitions could be bone, set the cue there, continue playing in the track to check if there are other spots, then go back to the cue (paused if I'm gonna work on another track, or play if I want to mix with another track right away).
Isn't it how everyone does? :P

[Daniel Schürmann (daschuer)]

I think Yes. Most of us get used to having this on a single CUE button, conditional to the playing state.

Do you plan to use two buttons of a shift button or what else?

[Jan Holthuis (holthuis-jan)]

My workflow: play the track. If I find a nice spot to set the cue, I press pause and then cue. Sometimes I then press play again and check if I find a better spot. If so, I can just repeat the process. If not, I just press cue again while the track is still playing to seek back to the cue point.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/10526