Re: [non-daw] *.peak files > 10x .wav

[ Thread Index | Date Index | More lists.tuxfamily.org/non-daw Archives ]


On Mon, Feb 22, 2010, John Murphy wrote:
> On Sun, 21 Feb 2010 23:49:53 -0600, male@xxxxxxxxxxxxx wrote:
> 
> > I have no idea what you mean by the comment "even small
> > files play silently"... In case you don't already know, you
> > have to connect non-daw's output to your desired outputs via
> > a JACK connection manager before you'll hear any sound. Port
> > auto-connection is considered harmful.
> 
> I merely meant that I wasn't so concerned about that problem.
> I couldn't find non-daw's outputs in qjackctl's connections
> dialog at the time (it was late), but I felt sure I could find
> a solution to that.
> 
> > Could you run `soxi` or `file` against the wave and post the
> > result? The peak data is a multi-resolution format, somewhat
> > like a mipmap from the world of 3D graphics. The generation
> > happens in a separate thread, which is the one you had to
> > kill. I imagine you had 10G of zeros...
> 
> Input File     : '/BIG/R-na-G/WAVs/fri-060209.wav'
> Channels       : 2
> Sample Rate    : 48000
> Precision      : 16-bit
> Duration       : 02:00:08.40 = 346003200 samples ~ 540630 CDDA sectors
> File Size      : 1.38G
> Bit Rate       : 1.54M
> Sample Encoding: 16-bit Signed Integer PCM
> 
> A hexdump of the peak data file reveals a reasonable looking
> distribution of data. Here's a small section from near the end:
> 
> 32ca0ef00  00 f8 b2 be 00 24 c2 3e  00 80 bf be 00 24 c7 3e  |.....$.>.....$.>|
> 32ca0ef10  00 e4 a3 be 00 5c 97 3e  00 6c 8b be 00 84 89 3e  |.....\.>.l.....>|
> 32ca0ef20  00 74 85 be 00 e0 55 3e  00 70 64 be 00 50 3e 3e  |.t....U>.pd..P>>|
> 32ca0ef30  00 14 ad be 00 e4 a9 3e  00 0c bc be 00 a0 b6 3e  |.......>.......>|
> 32ca0ef40  00 68 7c be 00 30 65 3e  00 48 3c be 00 78 38 3e  |.h|..0e>.H<..x8>|
> 32ca0ef50  00 38 6f be 00 10 2d 3e  00 54 83 be 00 60 3d 3e  |.8o...->.T...`=>|
> 32ca0ef60  00 ac b2 be 00 f4 b6 3e  00 54 c4 be 00 58 d2 3e  |.......>.T...X.>|
> 32ca0ef70  00 c8 9e be 00 f8 a5 3e  00 04 b5 be 00 c4 a2 3e  |.......>.......>|
> 32ca0ef80  00 18 b7 be 00 a0 b4 3e  00 94 d5 be 00 88 ce 3e  |.......>.......>|
> 32ca0ef90  00 10 b7 be 00 f0 b8 3e  00 64 ca be 00 5c cb 3e  |.......>.d...\.>|
> 32ca0efa0  00 f0 7e be 00 28 4b 3e  00 f8 75 be 00 b8 6c 3e  |..~..(K>..u...l>|
> 
> > Try deleting the .peak files and load the project again, it
> > might work... You also might try using sox, etc. to process
> > the wave file to a format libsndfile likes better.
> 
> Similar result after deleting the .peak although I only let it
> grow to about 5GB this time and a ctrl-c closed the GUI and
> stopped the peak file generation thread.
> 
> I have slightly better luck with audio this time too. One input
> and one output were available in JACK control connections, so I
> I got audio, but left channel mono only.

Try changing the track mode to 'Stereo'...

> I notice that .peak file sizes are only slightly smaller than
> the .wav they represent (Eg. 5.8MB wav = 5.1MB peak), which is
> fine, but I would hope to see the representation in much greater
> detail, if possible. Vertical zoom or adjustable height of the
> displayed track would be a great help.

Try changing the track size (vertical) or using the zoom
feature. The .peak files are large because they contain
(IIRC) ten levels of mipmapped data starting at 2-samples.
That allows the GUI to render very fast at all zoom levels.

> 
> -- 
> Thanks again, John.
> 
> 

-- 
Feb 22 2010,
John Moore Liles



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/