it works even at shutdown! excellent!
^C2011/08/28 15:12:16 [main:3] Shutdown started!
2011/08/28 15:12:16 [main:3] Waiting for threads to terminate...
2011/08/28 15:12:17 [harbor:3] Removing HTTP handler for '/radio' on port 7654
/mnt/archive/piradio/2011-08-28/2011-08-28-15_00_00.wav (129992732 bytes):
riff: 'RIFF'
riff length: -268435457
riff length field should be 129992724
fixed
wave: 'WAVE'
fmt: 'fmt '
fmt length: 16
format: 1
channels: 2
sample rate: 44100
bytes/second: 176400
bytes/sample: 4
bits/sample: 16
data: 'data'
data length: -268435493
data length field should be 129992688
fixed
2011/08/28 15:12:17 [threads:3] Thread "src_4927" terminated (1 remaining).
2011/08/28 15:12:17 [clock.wallclock_alsa:3] Streaming loop stopped.
2011/08/28 15:12:17 [threads:3] Thread "wallclock_alsa" terminated (0
remaining).
2011/08/28 15:12:17 [main:3] Cleaning downloaded files...
2011/08/28 15:12:17 >>> LOG END
BR, Peter
Am 23.08.2011 14:11, schrieb David Baelde:
> Hi Peter,
>
> Romain and I didn't see a better solution than adding on_close, so I
> implemented it (commit b57a1b3bd7ae). Let me know how this works for
> you. For example, you may use
> output.file(%wav,"file%Hwhatever.wav",on_close=fun(s)->system("qwavheaderdump
> -F #{s}"),reopen_when={0m},...,source).
>
> On Mon, Aug 22, 2011 at 6:52 PM, Peter Retep<[email protected]> wrote:
>> Calling a external tool triggered by on_close would require to use the
>> current filename in a command line, which is currently not supported.
> This was not the main motivation for adding it, but the new on_close
> will give you the actual filename which has been used, with the %H and
> other special things interpreted.
>
>> A advantage would be that you dont need additional fix tools unless you use
>> them.
> Yes, and it allows us to keep an encoder that works both for streams and
> files.
>
>> WAV: qwavheaderdump -F (quelcom package, tested).
>> MP3: mp3check --fix-headers (not tested).
> Thanks for the reminder (though I don't know of any problem with the
> standard %mp3 output that needs to be fixed afterwards). Once you have
> tested one or both of these features, it would be nice if you could
> propose either a snippet for
> http://wiki.sourcefabric.org/display/LS/User+Snippets or a
> documentation paragraph for the %wav section of
> http://savonet.sourceforge.net/doc-svn/encoding_formats.html (or
> perhaps something to add to output.file's short documentation).
>
> Cheers,
------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
