| Age | Commit message (Collapse) | Author |
|---|
|
|
|
with respect to all DiskReaders
|
|
SerializedRCUManager can't do this by itself
|
|
|
|
|
|
since we started
|
|
|
|
|
|
|
|
changes unless it actually changed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
when there's actually no failure
|
|
|
|
this development branch
|
|
|
|
|
|
capture_offset appropriately
|
|
manipulations into Track
|
|
|
|
|
|
reader/writer objects drop their reference
|
|
|
|
leading to a single sample being written when nothing should be.
Also, rename "outgoing" as "disk_signal" to be more clear.
|
|
incorrect state(s)
|
|
|
|
|
|
|
|
|
|
|
|
correct numbers
|
|
|
|
|
|
|
|
|
|
|
|
DiskWriter is a processor and as such has no Input object. This means
that the "Automatic" setting must be handled by the Track, which
does have an Input object to check for port connections to physical
or non-physical sources
|
|
|
|
|
|
|
|
|
|
master
|
|
|
