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

echo effect time interval seems inverse to pitch fader location #9500

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

echo effect time interval seems inverse to pitch fader location #9500

mixxxbot opened this issue Aug 23, 2022 · 6 comments
Labels
duplicate This issue is a duplicate of or superseded by another issue.

Comments

@mixxxbot
Copy link
Collaborator

Reported by: iamcodemaker
Date: 2018-10-31T06:27:45Z
Status: New
Importance: Undecided
Launchpad Issue: lp1800771


Using Mixxx 2.2 beta. My echo effect time interval seems to be affected by the inverse of the pitch fader tempo. In other words, when I use the pitch fader to lower the tempo, the echo time interval decreases as well making the echo cycle faster (it should get slower with the song), and the reverse is true if I increase the tempo, the echo gets slower.

@mixxxbot mixxxbot added the duplicate This issue is a duplicate of or superseded by another issue. label Aug 23, 2022
@mixxxbot
Copy link
Collaborator Author

Commented by: iamcodemaker
Date: 2018-10-31T06:31:53Z


I have quantize enabled on the effect and the time parameter knob at the 12 o'clock position.

@mixxxbot
Copy link
Collaborator Author

Commented by: uklotzde
Date: 2018-10-31T09:14:25Z


If this is the actual cause of https://bugs.launchpad.net/mixxx/+bug/1800771 than this could be an easy fix.

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2018-10-31T10:46:15Z


Uwe, did you intend to link to Bug #⁠1793232? If so, yes, the fix should be pretty easy.

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2018-10-31T11:17:52Z


Thank you for investigating and reporting this. Yes, it turns out the fix was simply switching from a multiplication to a division sign.

@mixxxbot
Copy link
Collaborator Author

Commented by: uklotzde
Date: 2018-10-31T11:31:56Z


Yes, of course bug #⁠1793232.

@mixxxbot
Copy link
Collaborator Author

Duplicate of #9442

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue is a duplicate of or superseded by another issue.
Projects
None yet
Development

No branches or pull requests

1 participant