Hi,
I'd like to include "on-the-fly" Disc-at-once support for cdrecord in a cd
recording frontend I'm writing (Gnome-Toaster).
Fooling around with cdrecord a bit I realized that it would be great if I
could just pass stdin ( "-" ) for all the tracks to be written and deliver
data for all tracks to cdrecord's stdin. I've been successfully doing this
using cdrdao for the last couple of months, however, cdrecord's support for
cd writers is not even comparable to that of cdrdao and cdrecord is more
actively maintained as it seems. (Note to all Gtoaster users: cdrdao support
will *not* go away, I'm just planning to *extend* the whole thing so's
cdrecord dao is supported as well).
Anyway, playing around with multiple stdin references in a single call I
realized that the first track will be written correctly, then cdrecord will
close it's stdin and that's it. Dropout.
My question now is whether it would be possible to sort of brute force
cdrecord into not closing it's source fd when it happens to be stdin ?
I think this would help other frontend developers enormously when
implementing "on-the-fly" dao writing with cdrecord.
As for Gnometoaster, I'll just retreat to using different named pipes for each
track to be written and serve my data to the one currently being processed.
I consider this to be a hack, though, as things could obviously be solved
better with a little support of cdrecord.
Andy
--
Every silver lining has a cloud around it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
