Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#13427 - transcode >= 1.1.0 brakes K3B DVD/CD ripping!

Attached to Project: Arch Linux
Opened by F.Di Milia (PyCoder) - Monday, 23 February 2009, 05:09 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 26 February 2009, 09:55 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



k3b dvd ripping doesn't work with transcode >=1.1.0!

Error message:


LITE-ON DVDRW SOHW-1653S CS0M (/dev/sr1, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite] [%7]
JLMS XJ-HD166S DS18 (/dev/sr0, CD-ROM, DVD-ROM) [DVD-ROM, CD-ROM] [None] [%7]

K3b Version: 1.95-svn
KDE Version: 4.2.00 (KDE 4.2.0)
QT Version: 4.4.3
Kernel: 2.6.28-ARCH

Used versions
transcode: 1.1.0

[[31;1mtranscode [0m] [31;1m critical [0m: Invalid argument for --progress_rate

transcode command:
/usr/bin/transcode --nice 19 --progress_meter 2 --progress_rate 0 -i /dev/sr0 -x dvd -T 1,-1,1 -a 0 -j 0,0,0,0 -R 1,/tmp/kde-angelus/k3b_0.log -y ffmpeg,null -o /dev/null -F mpeg4 -w 1800 -Z 1024x576

The problem is that transcode >=1.1.0 don't know "--progress_rate 0"!

Additional info:
local/k3b 1.0.5-2
local/transcode 1.1.0-2

Steps to reproduce:
Start k3b and rip a DVD!
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Thursday, 26 February 2009, 09:55 GMT
Reason for closing:  Upstream
Comment by Andrea Scarpino (BaSh) - Monday, 23 February 2009, 14:04 GMT
isn't this an upstream bug?
Comment by Ronald van Haren (pressh) - Monday, 23 February 2009, 16:26 GMT
does the same problem exists with stable k3b from [extra]?

if so, please file a bug report upstream if there is none already and post a link here so we can follow the discussion there.
Comment by F.Di Milia (PyCoder) - Thursday, 26 February 2009, 05:29 GMT
Yoah the error exist on every k3b incl. stable and kdemod.

k3b use the option --progress_rate 0 and this option doesn't exist in transcode >=1.1.0 with 0, only --progress_rate 1 works with transcode >=1.1.0.

the problem is, that the option --progress_rate 0 is hard coded in k3b -.-'
Comment by F.Di Milia (PyCoder) - Thursday, 26 February 2009, 05:39 GMT Comment by Greg (dolby) - Thursday, 26 February 2009, 09:16 GMT
When Ronald van Haren said to open a bug report upstream he meant here:
I dont know if that was what made you open the second bug report.
Comment by Andrea Scarpino (BaSh) - Thursday, 26 February 2009, 09:55 GMT