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

updating cue point seeks to old cue point #10551

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

updating cue point seeks to old cue point #10551

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

Comments

@mixxxbot
Copy link
Collaborator

Reported by: ywwg
Date: 2021-10-08T02:43:14Z
Status: Fix Committed
Importance: Medium
Launchpad Issue: lp1946415


on main, if I try to set a new cue point, the operation works, but the track seeks to where the cue point used to be

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

Commented by: ninomp
Date: 2021-10-08T17:41:07Z


I noticed this too, but I think this only happens when trying to place cue point in preroll.

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2021-10-09T20:04:24Z


This happens to me 100% of the time, not just preroll

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2021-10-09T20:11:37Z


Ah, it's because of 036754d, which did this:

-    double cuePoint = m_pCuePoint->get();
+    const auto mainCuePosition =
+            mixxx::audio::FramePos::fromEngineSamplePosMaybeInvalid(
+                    m_pCuePoint->get());

so when the cuepoint is updated, we seek to the old position.

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2021-10-09T20:17:35Z


I'm making a small PR, should be uncontroversial?

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2021-10-09T20:23:48Z


#4370

@mixxxbot
Copy link
Collaborator Author

Commented by: Holzhaus
Date: 2021-10-09T20:40:34Z


@ywwg: I don't understand how the bug was caused by the change diff you posted. The lines are identical semantically, it's just that the variable type is different.

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2021-10-10T21:49:14Z


it's not caused by just those lines -- by assigning the cue position to a variable, when we update the cue position the variable still has the old value. See the PR for the complete fix.

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Committed.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 2.4.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