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

BeatLoop should extent beyond the end of a track #8408

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

BeatLoop should extent beyond the end of a track #8408

mixxxbot opened this issue Aug 22, 2022 · 3 comments
Labels
confirmed duplicate This issue is a duplicate of or superseded by another issue. feature

Comments

@mixxxbot
Copy link
Collaborator

Reported by: ferranpujolcamins
Date: 2016-01-01T18:47:00Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp1530458


Currently the end point of a BeatLoop is either the end of the track or a point n beats forward (depending which comes first).

I think Mixxx should be able to continue playing after the end of the track (playing silence), this way loops would not be truncated at the end of a track.

This is useful because sometimes loop tracks are not long enough and have the last beat truncated.

We can introduce an option to stop the deck at the end of a track to keep the current behavior. This is the approach Traktor takes.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2016-01-01T20:30:18Z


Similar: Bug #⁠1405010 and Bug #⁠1440751

@mixxxbot mixxxbot added confirmed duplicate This issue is a duplicate of or superseded by another issue. feature labels Aug 22, 2022
@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2017-05-26T05:45:14Z


#1187 modified the loop_double Control so it will not increase the size of a loop if the new loop would go beyond the end of the track. Instead of truncating the new loop at the end of the track, it just won't resize the old loop.

@mixxxbot
Copy link
Collaborator Author

Duplicate of #9478

@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
confirmed duplicate This issue is a duplicate of or superseded by another issue. feature
Projects
None yet
Development

No branches or pull requests

1 participant