[Ffmpeg-devel] Re: OT: cdrecord

[Michel Bardiaux]

M?ns Rullg?rd wrote:
[snip]

> 
> 
>>There are also heuristics to detect buffer underruns when burnproof is
>>enabled - they are far from perfect, but if buffer underruns occur all
>>the time then they work quite well.. So cdrecord could print a warning
>>at the end of the process if it thinks that a lot of buffer underruns
>>have occurred and that the disc quality may have suffered. Then the user
>>can decide if he wants to burn it again or not.
> 
> 
> Cdrecord already prints the number times burnproof was used.  Even when
> burning with the source files on NFS over wireless LAN, and a loaded system,
> it is virtually never needed.  Modern burnerns have typically 8MB buffers,
> so there would have to be quite a bit going on for cdrecord to lose the CPU
> long enough to make a difference.
> 
True for the CPU. But with heavy I/O you can easily overwhelm the buffer 
cache. I know *now* that even using 2-pass burn (disk image, then actual 
burn), I should not unrar a 600MB archive while burning...

-- 
Michel Bardiaux
R&D Director
MediaXim S.A.  Bd. du Souverain, 191  B-1160 Bruxelles
Tel : +32 2 790.29.41