On 1 Apr 2011, at 11:11, Roger Burton West wrote: > I don't have scope to test this in place, but broadly speaking I would > expect you could get away with something like this. Set up @cmd1 and > @cmd2 to be the first and second system() calls, then: > > my $buffersize=1024*4096; > > open(INPUT,'-|',@cmd1); # or report the error > binmode INPUT; [snip]
I would suggest writing to an intermediate AAC file instead of using a pipe. That way, if something goes wrong, the AAC artefact is left available for debugging. Just remove upon successful creation of m4a file. _______________________________________________ get_iplayer mailing list get_iplayer@lists.infradead.org http://lists.infradead.org/mailman/listinfo/get_iplayer
