Description of problem: DVDs burned with wodim (and other open source tools) are incompatible with various portable players while DVDs burned with commercial (Nero) and Windows equivalents work flawlessly in these players. Clearly, there seems to be a difference between the way these tools write the data to the DVD. Version-Release number of selected component (if applicable): wodim-1.1.6-11.fc9.i386 How reproducible: Every time. Steps to Reproduce: 1. Create/master DVD ISO image. 2. Burn ISO image to DVD with wodim/cdrecord (either command-line or via k3b) 3. Test in portable player Actual results: DVD is unreadable by the player. Expected results: DVD should be readable. Additional info: The problem does not exist when burning the exact same DVD ISO image using Nero or Windows equivalents.
Please note that wodim is not cdrecord. Wodim is based on a very outdated cdrecord version. The mature DVD support in cdrecord has been replaced by something half baken. In order to create a correct DVD-Video, you need to use a correctly mastered DVD Video directory tree. This is outside the scope of cdrtools. The next task is to convert the DVD-Video directory tree into a proper UDF filesystem image. This is done by calling: mkisofs -o xxx.iso -dvd-video /path/to/mastered/tree Mkisofs is known to do this right, genisoimage from the clone shipped by RedHat is known to cause problems. THe next step is to write the image to the medium. This is done by calling: cdrecord -v xxx.iso wodim is known to cause problem in this step. Fetch a recent original source from: ftp://ftp.berlios.de/pub/cdrecord/alpha/ compile and install as root. have fun and forgeht the bugs from wodim...
Joerg, I appreciate your response. Actually, you and I have already exchanged email dialog on exactly this issue (circa 9/14/2008). Unless fixes have been made to 'cdrecord' (or any of the competing tools) since then to address this particular behavior, the problem certainly still remains. The basic problem is that ALL of the open source Linux tools that I've tried (cdrecord, wodim, genisoimage, mkisofs) fail to burn a DVD that is readable in the *Portable* players I've tested (PS3, Panasonic); while DVDs burned with Windows based equivalents (Nero, ImgBurn) work flawlessly using the VERY SAME ISO IMAGES, RECORDING DEVICE, OPERATING SYSTEM (Linux) AND DVD MEDIA BRANDS. IMO, this is clear evidence of a limitation of the Linux tools themselves or the underlying Linux DVD I/O subsystem; leaving the obvious question - what's the difference between how these and their Windows counterparts write to the DVD media? As a simple user, I can offer little in the way of either understanding the underlying problem or suggestions for resolution. All I can do is report the problem as clearly as I know how, on as many channels as appropriate and HOPE for some developer to take the issue seriously. I also understand that I may be a lone voice in the wilderness on this issue - for any number of reasons - the most likely being that the portable players I'm testing may not commonly be used in the Linux community for viewing DVD copies. This would also explain the lack of problem reports from users or serious interest from Linux developers on this one issue. And I understand that developers can't always be expected to duplicate every test scenario sufficiently to see the problem for themselves. What they CAN do for this problem, however, (assuming interest is there) is to try to understand how their product differs from the Windows based counterparts. Sorry for the minor rant. Just trying to express the problem and my frustration as politely and thoroughly as possible. Thanks again, Fred
If you believe that the the problem is not the "ISO images", I can garantee you that writing the image with cdrecord will give you a working disk in case you do not need dual layer media. In case of dual layer media, you need to give cdrecord the right layer break offset by using the option driveropts=layerbreak=# (replace # with the right value). The layerbreak value is a number you may retrieve from your video formatting software. If you still have problems, one of your stetements must be wrong and the only way to help you would be that you send me a working and a non-working medium for analysing.
## System ## Operating System: Fedora 10 DVD Burner Device: LITE-ON DVDRW LH-201AP DVD Media: Memorex DVD+R (Single Layer) ISO Image: Random Test DVD Movie ## Test 1 - cdrtools/cdrecord-2.01.01a56 ## Player 1 - PC/Fedora/LITE-ON Player: DVD works Player 2 - Phillips Home Player: DVD works *Player 3 - Portable Panasonic (in my GM vehicle): DVD READ ERROR ## Test 2 - ImgBurn-2.4.2.0 (via Crossover Linux Pro 7.1.0) ## Player 1 - PC/Fedora/LITE-ON Player: DVD works Player 2 - Phillips Home Player: DVD works *Player 3 - Portable Panasonic (in my GM vehicle): DVD works I'm not sure how much more clearly I can make the case. As you can see from the results, your guarantee is only partially true. Yes, cdrecord does create a working disk, but not for *Player 3. It seems that the creators of ImgBurn (Nero too) have the advantage on this issue. Whatever they're doing results in a disk that works in every single player I've tested. Unfortunately, this is not true with cdrtools-cdrecord (or any of the other Linux recording tools I've tested). In case this is of any value, here is the output from my cdrecord operation: ============== $ ./cdrecord --dev=4,0,0 ~/ISOs/Test.iso ./cdrecord: No write mode specified. ./cdrecord: Asuming -sao mode. ./cdrecord: If your drive does not accept -sao, try -tao. ./cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 2.01.01a56 (i686-pc-linux-gnu) Copyright (C) 1995-2009 J�rg Schilling scsidev: '4,0,0' scsibus: 4 target: 0 lun: 0 Linux sg driver version: 3.5.34 Using libscg version 'schily-0.9'. Device type : Removable CD-ROM Version : 5 Response Format: 2 Capabilities : Vendor_info : 'LITE-ON ' Identifikation : 'DVDRW LH-20A1P ' Revision : 'KL0A' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Using generic SCSI-3/mmc-3 DVD+R driver (mmc_dvdplusr). Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: PACKET SAO LAYER_JUMP ./cdrecord/OBJ/athlon-linux-cc/cdrecord: Warning: The DMA speed test has been skipped. Starting to write CD/DVD/BD at speed 16 in real SAO mode for single session. Last chance to quit, starting real write 0 seconds. Operation starts. Track 01: Total bytes read/written: 4599152640/4599152640 (2245680 sectors). ==============
If you like maximum compatibility, don't use DVD+R media, rather use DVD-R media. Future versions of cdrecord will be able to do some dirty tricks with DVD+R.... But DVD+R is NOT a DVD type medium and Panasonic is one of the founders of the DVD Forum standard commitee.
FWIW - I've also tested all of this on CD-R media with EXACTLY the same results. The problem is NOT the media! The problem is NOT the player! The problem is NOT the user! The problem *** IS *** the recording software! If you don't feel you can be helpful, I fully understand. Kindly say so and abstain from the dialog. If, on the other hand, you are able and interested, here it is one more time ... DVDs created with ImgBurn (and Nero) WORK PERFECTLY in my Panasonic player DVDs created with cdrtools (and the other linux tools) FAIL in the same player ... Exact same Operating System Exact same writer device Exact same media Exact same ISO image My hope is that at least one of the creators of these linux tools would be just curious enough to know how and why their competition exceeds them and strive to improve their product accordingly. Meantime I patiently wait. :) -Fred
It is hard to judge on the problem without being able to compare the results. Normally, it is sufficient to compare file system images but you claim that there is no difference in the images. Cdrecord writes to the medium in a standard compliant way. I would need to compare two DVD-R dedia. Many standalone players do not read DVD-RW and there are some dirty tricks with DVD+R that cdrecord does not yet support.
Assuming that what we are both claiming is true, then it only stands to reason that there must be another trick/method being employed by ImgBurn, but not by cdrecord (or others). I also think it would be helpful to get away from the DVD-R vs. DVD+R question, which is not an issue in this case. As I've pointed out, ImgBurn works with either while cdrecord works with neither. Of course, you are perfectly welcome to claim standards compliance and dismiss this as a non-issue. But, are you not even curious why cdrecord fails where others succeed?
We should not talk about DVD+R as DVD+ is non-standard and as there are drives that will not read a DVD+R at all. I asume that you are not talking about Dual layer media. If you use dual layer media, you need to use DVD+R/DL and tell cdrecord the location of the layer breask. DVD-R is the standard and gives best results for single layer. Without being able to make investigations with the media (working vs. non-working), I cannot help more.
I'm willing to send my media to you if you're willing to make an honest analysis of it. Here are a couple other suggestions.... - Burn your own DVDs using both cdrtools and ImgBurn (or Nero), then analyze the difference. - Attempt to open dialog with the authors of ImgBurn (or Nero) and ask them what method/trick they might be using to produce more compatible DVDs.
ImgBurn only works on a Microsoft environment - I use UNIX ;-) Nero does not work on UNIX too. For both products, it is highly improbable that authors will show up in the net and answer questions.....
Actually, ImgBurn works very nicely with Wine/CrossOver and Nero has a Linux version. I tested using both ImgBurn and Nero ** on Linux **. I agree that the other authors may not be very willing to share ideas, but then they might. Seems worth a try. ImgBurn: http://www.imgburn.com support Nero: http://www.nero.com/enu/linux3.html Jorg... I'm honestly not trying to negatively compare cdrtools, etc. to ImgBurn or Nero. Rather, I'm simply trying to show them as examples of working software (on Linux). I don't feel like I'm being very effective at communicating that to you. Truth is, I MUCH prefer to use the Linux tools. Unfortunately, ALL of the Linux tools are disappointingly less compatible, forcing me to use the others (ImgBurn in my case). My assumption is that others are also experiencing this compatibility problem, but may not understand that there are alternatives, or they mistakenly blame the media or player.
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This problem also exists in Fedora 10 (and almost certainly in 11 also). I'm changing the version from Fedora 9 to Fedora 10.
# rpm -q --whatprovides `which dvd+rw-booktype ` dvd+rw-tools-7.1-3.fc11.x86_64 # dvd+rw-booktype Usage: dvd+rw-booktype [-dvd-rom-spec|-dvd+rw-spec|-dvd+r-spec|-inq] \ [-media|-unit|-unit+rw|-unit+r] /dev/dvd Suggestion, use dvd+rw-booktype to set the booktype to dvd-rom before the burn, I'm not 100% sure of the commandline, but something like dvd+rw-booktype -dvd-rom-spec -unit+[r|rw] /dev/dvd I believe you need to do this after inserting the blank media, immediately before burning the image (or possibly this is a generic dvd drive setting? - not all that sure since this utility doesn't work with any of my drives [supposedly only supports Ricoh, Benq and BTC]). In general read the docs at http://fy.chalmers.se/~appro/linux/DVD+RW/ ---- However, I believe you have a LiteOn drive, and that utility only supports Ricoh, Benq and Btc. http://club.cdfreaks.com/f44/bitsetting-under-linux-93589/ You can upgrade the drive's firmware to default to using dvd-rom booktype (see above linked thread), however the following is probably easiest: ----- You can use a windows utility via wine to do this. Tested that the settings sticks on my own machine. (from http://codeguys.rpc1.org/utilities.html) wget http://codeguys.rpc1.org/utilities/Settings_Utility-1.1.0.rar unrar x Settings_Utility-1.1.0.rar wine Settings_Utility.exe (close the internet explorer that pops up the first time around) You want to select your drive, go into bitsetting, set new settings to DVD-ROM and click 'set as default' for all 3 rows (dvd+r, dvd+rw dvd+r/dl) and click set on all 3 rows. The book type column should change, and should have those same values if you quit and reopen the utility. (if the book type column lists value followed by a star, then the setting holds only for the next burned media, ie. you failed to select 'set as default') I've tested the booktype settings on my Fedora 11 machine with a '[LITE-ON ][DVDRW LH-20A1L ][BL01]' burner - I can set them and they stick across the utility being closed and reopened (reboot or hard poweroff untested). However it only supports LiteOn drives and doesn't seem to work with my LG '[HL-DT-ST][BD-RE GGW-H20L ][YL05]'
Also found a solution for my LG: $ wget http://www.alexander-noe.com/cdvd/bitsetting/bitset_v2.rar $ unrar x bitset_v2.rar $ wine bitset.exe -drive=1 -set:dvd+r=dvd-rom,dvd+rw=dvd-rom,dvd+rdl=dvd-rom
Well, well... That seems to have finally solved the problem with the use of wodim/cdrecord. Although, it still doesn't explain why ImgBurn/Nero works without changing the booktype/bitsetting. But, as far as I'm concerned, the point is moot as long as this works. I can now revert back to using K3b. Thanks!!! :)
I think we can close this bug.
The explanation is simple, nero and imgburn do the bitsetting to dvd-rom for drives they know how to bitset (most major vendors) by default (although it can be changed somewhere in the advanced options).
This is probably still something that should either be added to the manpages or explicit support for it added to cdrecord (I'd probably favour the first, seeing how vendor specific it is).
In the case of ImgBurn at least, according to it's settings dialog, the default behavior is NOT to bitset. Of course, that doesn't mean that it doesn't make the attempt behind the scenes anyway on supporting hardware. Nevertheless, I tend to agree with you on the manpage addition. Although, I'm still a bit undecided as to my opinion on adding it to the code. Seems like it should be an option at least. IMO all of these tools should strive for the most reader-compatible settings by default. Granted that means possibly adding substantial logic to deal with the many different writers. Users shouldn't need to resort to using another operating system tool to override default writer behavior. It's these little gotchas with so many Linux apps that IMO tend to drive the more casual users away from Linux. Especially when the equivalent Windows apps just work. Hmmm... Seems I'm not all that undecided afterall. :)
If the problem could be solved by using bitsetting, you did _always_ use DVD+R or DVD+RW media which is no official DVD media. Cdrecord's man page mentions that DVD+ is incompatible with DVD-. On the cdrtools mailing lists, it has been discussed several times that for best compatibility with stand alone players, you should use DVD-R or DVD-RW single layer media or DVD+R double layer media. Cdrecord will add the cheat code after cdrtools-3.0 final is out.
Joerg, I appreciate your input and willingness to support the "cheat code". The fact of the matter is, as we've discussed here previously, that I have been testing with both DVD+ and DVD- media. In my latest test case, however, I used DVD-, which as I now understand, isn't really affected by the bitsetting. Thus, I have no explanation as to why DVD- now works where all my previous tests failed. To be thorough however, I do need to test this bitsetting using DVD+ media before I can claim success.