don't stop track when loop_in/out is beyond track boundaries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Confirmed
|
Medium
|
ronso0 |
Bug Description
I create a 8-beat loop loop close to the track end and shift the loop to have loop_in at the beginning of a vocal phrase. I could move the loop let's say 1/8 beat beyond the track end (= loop_out after track end, but no indicator where that end point actually is Bug 1799576) and the loop would stop playing as soon as it reaches the track end.
I see there'a reason to not allow huge loops (unexpecedly) cross tracks' start/end, but there are use cases where this is actually very helpful:
1) I somehow didn't notice the track end is getting closer, and as a quick hack I'd enable a 4-beat loop to gain some more seconds to load and align the next track. I might be very late and that loop would cross the track end. Let it continue playing..
2) 3 beats before the track end there's a vocal I'd like to have in an 8-beat loop to match the next track, and I want that vocal only and cut off the preceeding beats. Same applies to loops crossing the first sample of a track.
2.3.0-alpha-pre
tags: | added: looping |
description: | updated |
summary: |
- loop close to track end suddenly stops deck after several cycles + loop_out should stay within track boundaries ... |
description: | updated |
summary: |
- loop_out should stay within track boundaries ... + let loop_out be beyond track boundaries, ignore track start/end then |
description: | updated |
summary: |
- let loop_out be beyond track boundaries, ignore track start/end then + ignore track start/end when loop_in/out is beyond track boundaries |
summary: |
- ignore track start/end when loop_in/out is beyond track boundaries + don't stop track when loop_in/out is beyond track boundaries |
description: | updated |
Changed in mixxx: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in mixxx: | |
status: | In Progress → Confirmed |
Changed in mixxx: | |
milestone: | 2.3.0 → none |
Ok, the current situation is odd.
I am not sure what the right solution is though.
1.) We may play past the end, which is unfortunately silence.
2.) We may not allow to move a beatloop past the track end, ignoring the beatjump.
3.) We may fix loop out at the track end, falling out of beat.
4.) We may short the loop at the last beat to not go beyond the track end but be in beat.
Unfortunately the engine can play past a track right-now. So 1. involves some refactoring. Is it worth the work, or is the silence part undesired anyway?
Does one of the other solutions suite?