Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In theory we only need to do this if the use of a loop for a given overwrite differs
from the previous refill or overwrite. However, keeping track of this is hard, and
this way effectively enforces the notion that if we do the arithmetic correct,
for cases where there's no change in the use of a loop location, this ends up
being a no-op (i.e. we are resetting it back to its current value)
|
|
|
|
|
|
loop for loop play
|
|
Session::destroy() calls drop_references(),
which leads to InternalSend::send_from_going_away()
calling InternalSend::propagate_solo().
This looks up the SoloControl to test soloed_by_others(), incl.
and VCA maters. Those VCAs however may already have been destroyed,
and (weak pointer) _master.lock() fails.
|
|
|
|
|
|
|
|
|
|
be read
There's no need to fill the whole buffer, because we do not consider the whole buffer readable.
This uses the recently-added PlaybackBuffer::overwritable_at() API to compute the correct
amount of data to overwrite
|
|
|
|
|
|
Since we now (correctly) do not locate for loop changes, this member
is unnecessary
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Don't rely on ev->locate_transport_disposition
|
|
|
|
|
|
|
|
loop ends)
|
|
|
|
|
|
Replacement to follow in subsequent commit
|