On Tue, Jul 01, 2014 at 09:20:16PM +0200, Lieven Moors wrote: > On Sun, Jun 29, 2014 at 03:08:32PM -0700, J. Liles wrote: > > Can you be more specific about the steps to reproduce this issue? I've been > > playing around with it today and I can't make it happen. > > > > > > No, I can't put my finger on it. As far as I know now, > it just happens randomly when I record a new track. > If I can be more specific, I'll let you know...
I did an 'ls' on the wav and peak files, after this bug happened. It shows that the peak file of voc4 has become very large (larger than the wav file itself). Maybe it helps pinpointing the problem. For what it's worth, I've added the access times of those files as well. The voc4 file is the one that had it's displayed waveform changed in something I don't recognize, and this happened while I was recording voc5. (it is not empty, and shows something like background recording noise) As I said before, the actual audio data played is still correct. If you want, I could send you the files for further inspection if that would be helpful. [lieven@studio sources]$ ls -l voc4-1404495317.wav* -rw-r--r-- 1 lieven users 36275756 Jul 4 19:39 voc4-1404495317.wav -rw-r--r-- 1 lieven users 752134656 Jul 4 19:44 voc4-1404495317.wav.peak [lieven@studio sources]$ ls -l voc5-1404495668.wav* -rw-r--r-- 1 lieven users 36125228 Jul 4 19:45 voc5-1404495668.wav -rw-r--r-- 1 lieven users 749744 Jul 4 19:48 voc5-1404495668.wav.peak [lieven@studio sources]$ ls -ltu voc4-1404495317.wav* -rw-r--r-- 1 lieven users 752134656 Jul 4 19:45 voc4-1404495317.wav.peak -rw-r--r-- 1 lieven users 36275756 Jul 4 19:39 voc4-1404495317.wav [lieven@studio sources]$ ls -ltu voc5-1404495668.wav* -rw-r--r-- 1 lieven users 749744 Jul 4 19:50 voc5-1404495668.wav.peak -rw-r--r-- 1 lieven users 36125228 Jul 4 19:45 voc5-1404495668.wav
