Skip to content
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

issues with hotcues at 0:00 #9820

Closed
mixxxbot opened this issue Aug 23, 2022 · 5 comments
Closed

issues with hotcues at 0:00 #9820

mixxxbot opened this issue Aug 23, 2022 · 5 comments
Labels
Milestone

Comments

@mixxxbot
Copy link
Collaborator

Reported by: ronso0
Date: 2019-12-05T18:28:34Z
Status: Fix Released
Importance: High
Launchpad Issue: lp1855321


Playposition jumps to Cue when manipulating hotcues exactly at 0:00

Set hotcue

  • set Cue somewhere > 0:00
  • drag overview indicator 0:00
  • set hotcue at 0:00
    = hotcue is set at 0:00
    = playposition jumps to Cue

Remove / move / swap hotcues

  • go to hotcue at 0:00
  • remove hotcue
    = playposition jumps to Cue

Really disturbing when swapping hotcues (delete & set another hotcue at same psition) because it's cumbersome to go back to the previous position which is now lost.

@mixxxbot mixxxbot added the bug label Aug 23, 2022
@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2020-03-12T17:07:12Z


..still present in master. I consider this a blocker for 2.3
Can someone confirm?

@mixxxbot
Copy link
Collaborator Author

Commented by: goddisignz
Date: 2020-03-23T13:24:20Z


Additionally, en- or disabling quantization when the playhead is at 0:00 has the same effect.

@mixxxbot
Copy link
Collaborator Author

Commented by: goddisignz
Date: 2020-03-24T18:08:24Z


PR: #2593

in case you like to comment.

@mixxxbot
Copy link
Collaborator Author

Commented by: ninomp
Date: 2020-03-24T18:25:53Z


Hello! I introduced this feature with #1242. My use case was loading a track that has not been analyzed before loading into a deck. That is why I introduced this behaviour, which I call "cue point following".

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 2.3.0 milestone Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant