View Issue Details
|Dell D830 core2duo T9300 2.5GHz
|0002977: Trimming the end of a region, involved in a multiple drop in record, reveals material incorrectly.
|Trimming the end of a region, involved in a multiple drop in record, reveals material incorrectly.
Record arm a track. Arm the master record and press play. A region starts to record. Press the master record button to drop out of recording, but leave the transport in play. Wait a while. Drop back into record again and record a second region. Now press stop. There are now 2 regions with a space between them.
Now drag the end of the first region. The region will extend revealing more audio. The audio it reveals is in fact the contents of the second recorded region.
A region should not be allowed to be trimmed beyond its own material.
|No tags attached.
|Assumption is that this is a function of every record pass being recorded into the same file, regardless of how many regions are dropped in.
Further thinking. Shouldn't a multiple drop in record (to the same file) record silence into the file between drop ins. ie the resulting file should be 'audio''Silence''audio' not 'audio''audio', with the silence not present.
the idea of the single file is as a repository of that's take's audio, not as a literal record of the gaps as well as the audio.
the idea probably needs to be revisited. the main benefit that it brings is that a single capture/take is represented by a single file and can thus be destroyed more easily than if a multi-punch take consists of N different files.
unix filesystems would allow ardour to seek in between the punches and thus create "fake" silence.
|The biggest problem I see is that if this file is opened in another audio application then it would be a continuous stream of audio with an odd change part way through.
|Note Added: 0007266
|Note Added: 0007378
|Note Added: 0007385
|Note Added: 0007388
|bugs => bugs2
|bugs2 => bugs
|new => acknowledged