-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cue point is reset when pressing cue #13350
Comments
Which cue mode do you use? Looking at the code, the CO is never reset, this could be causing an issue. Sadly I don't own this device. Are you comfortable with JavaScript and Mixxx mapping? |
That is quoting the sampler code. I don't think that matters here. The CO also doesn't need to be reset, as only the signal is relevant, not the value in this case. |
But it would be good to know if the issue can be reproduced without the hardware attached using the onscreen buttons. |
cue-mode is set to Mixxx mode (default)
okay, i tried multiple variations, here are my findings:
|
Thats good to know. That isolates the problem to the controller mapping.
Can you elaborate on what you mean with wrong Cue point? There is only ever one cue point per track. Do you mean hotcue? |
shure! I start the song by hitting the PLAY button. |
thats weird. I don't know what the culprit could be. can you share your log when starting mixxx with |
shure. did the same as in the video. |
i dare to mention @Holzhaus at this time as he – if i remember correctly – has the same controller and wrote the mapping. |
Bug Description
i encountered a new issue with cue-mode set to mixxx mode with Roland 505.
[expected]
· a cue point is set at the beginning of the song
· press PLAY to start the song
· press CUE to jump back to the cue point
· repeat ad libitum
[experienced behaviour]
· a cue point is set at the beginning of the song
· press PLAY to start the song
· press CUE to jump back to the cue point
· now this happens, ** but the cue point is set to the point when CUE was pressed**
· press PLAY to start the song
· press CUE -> jumps to the new set, but wrong CUE point
[additional info]
· i experienced this strange behaviour last night at a gig, i think i did everything as always
· happens on both decks, so at this time i don't think it's a faulty hardware button
ty
Version
2.4.1
OS
Archlinux
The text was updated successfully, but these errors were encountered: