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

unable to change vinyl lead in time #10319

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

unable to change vinyl lead in time #10319

mixxxbot opened this issue Aug 23, 2022 · 3 comments

Comments

@mixxxbot
Copy link
Collaborator

Reported by: zabox909
Date: 2021-02-12T02:46:22Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp1915483
Tags: easy, vinylcontrol


Since v2.3 I am no longer able to change the lead-in time. I can type a value in the field, but whenever I press apply it will reset to the default lead-in time.
I tried it both on Mac an windows with the same result, so it should be a platform independent issue. When I hover with the mouse over the field, the cursor also rapidly switches between the arrow and text form.

The only way to get around this at the moment is to manually edit the config file, but that value also resets to the standard again every few restarts (or when I change other settings related to the vinyl mode.

This renders the absolute mode for Serato cds unusable, as there seems to be an offset with the cd you're able to download from the Serato website. Not sure if this is another bug or a systemic error of the positional information, as it behaves the same across all my machines, also independent of the medium I'm playing the timecode from. Even virtual dj hast the same (about 0.5s) offset.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2021-02-23T09:06:23Z


This happens also on Ubuntu Bionic

@mixxxbot
Copy link
Collaborator Author

Commented by: ninomp
Date: 2021-04-11T18:13:15Z


#3781

@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
Projects
None yet
Development

No branches or pull requests

1 participant