[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Low burning speed



Growiso doesn't work properly with LG GSA4163B burner and DVD+RW 8x
discs. Burning speed is about 4x (even when burner speeds up
switching from 4x zone to 8x - it's a ZCLV burner), it's well visible
with K3b. There's no problem with all other types of media, including
DVD-R 8X.

Version 7.0.1 and 7.1, data: big, small, in combination, doesn't
matter, media: Verbatim made by Mitsubishi and TDK made by Ricoh. Here's
output:

tomasz@debian:~$ growisofs -Z /dev/hdc /mnt/hda6/WinFast\ WorkArea/Poszukiwacze\ Czindici2.avi /mnt/hda6/WinFast\ WorkArea/odessa.avi /mnt/hda7/WinFast\ WorkArea/JFK.mpg /mnt/hda7/WinFast\ WorkArea/Nieukończony\ cud\ 2.mpg
WARNING: /dev/hdc already carries isofs!
About to execute 'mkisofs /mnt/hda6/WinFast WorkArea/Poszukiwacze Czindici2.avi /mnt/hda6/WinFast WorkArea/odessa.avi /mnt/hda7/WinFast WorkArea/JFK.mpg /mnt/hda7/WinFast WorkArea/Nieukończony cud 2.mpg | builtin_dd of=/dev/hdc obs=32k seek=0'
I: -input-charset not specified, using utf-8 (detected in locale settings)
/dev/hdc: "Current Write Speed" is 8.2x1352KBps.
  0.24% done, estimate finish Tue Mar 25 22:09:03 2008
  0.49% done, estimate finish Tue Mar 25 21:58:44 2008
  0.73% done, estimate finish Tue Mar 25 21:55:19 2008
  0.97% done, estimate finish Tue Mar 25 21:53:35 2008
  1.21% done, estimate finish Tue Mar 25 21:52:34 2008
  1.46% done, estimate finish Tue Mar 25 21:53:01 2008
  1.70% done, estimate finish Tue Mar 25 21:52:22 2008
  1.94% done, estimate finish Tue Mar 25 21:51:53 2008
...............
...............
 99.48% done, estimate finish Tue Mar 25 21:55:48 2008
 99.72% done, estimate finish Tue Mar 25 21:55:49 2008
 99.97% done, estimate finish Tue Mar 25 21:55:49 2008
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
2060711 extents written (4024 MB)
builtin_dd: 2060720*2KB out @ average 3.6x1352KBps
/dev/hdc: flushing cache
/dev/hdc: stopping de-icing
/dev/hdc: writing lead-out

3.6x with below parameters sounds like recording was progressing at 1/2 of advertised velocity, i.e. started at 3x and then switches to 4x at about half recording. Question is does it run uniformly at 1/2 or does speed jump up and down? Read on...

And here's output of media info:

tomasz@debian:~$ dvd+rw-mediainfo /dev/hdc
INQUIRY:                [HL-DT-ST][DVDRAM GSA-4163B][A106]
GET [CURRENT] CONFIGURATION:
 Mounted Media:         1Ah, DVD+RW
 Current Write Speed:   8.0x1385=11080KB/s
 Write Speed #0:        8.0x1385=11080KB/s
 Write Speed #1:        6.0x1385=8310KB/s
GET [CURRENT] PERFORMANCE:
 Write Performance:     6.0x1385=8310KB/s@[0 -> 112639]
                        8.0x1385=11080KB/s@[112640 -> 2295103]
 Speed Descriptor#0:    02/2295103 R@3.3x1385=4584KB/s W@8.0x1385=11080KB/s
 Speed Descriptor#1:    02/2295103 R@3.3x1385=4584KB/s W@6.0x1385=8310KB/s

Looks all right... I can think of following reasons (in ascending order of likelihood).

1. Even though so called Page 05 settings should not affect DVD+ recordings (per MMC specification), unit looks at the page and misinterprets the settings. This happened before, though not in DVD+RW context.

2. Under high-speed recordings unit lies about available buffer capacity tricking growisofs to sleep for longer intervals, long enough to drain the buffer and affect performance. This happened before with some Pioneer units, and it should be handled, but your unit might lie in yet more confusing manner.

3. growisofs is periodically tricked to issue SYNCHRONIZE CACHE command, which drains the buffer, which in turn results in idle revolutions, hence lower performance.

Could you do following. Download source, unpack some place, open growisofs_mmc.cpp with text editor, locate line that reads "sync_cache:" (it's line 665 in 7.1), add following line after it:

fprintf(stderr,"-- SYNC CACHE %x\n",errcode);

Then 'make' and run './growisofs -use-the-force-luke=moi -Z /dev/hdc /mnt/hda6/...' directly from current working directory and collect output. Questions are: how does speed varies in progress indicator? Steady or jerky? Do you see SYNC CACHE and if yes, how often and what's the code? [There is a chance that there will be a lot of SYNC CACHE lines, don't hesitate to abort recording with Ctrl-C]. How does UBU value in progress indicator vary? A.



Reply to: