SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a Pioneer BD-207 BluRay burner that is rated at 12x on BD-R media. I have Verbatim disks rated at 6x. Whenever I try and burn BD-R disks with K3b (2.0.3), it initially sets the burn speed to 5x (why?) and then reports that the burner doesn't support that speed before dropping to 4x!
The disks are burned just fine, but it is obviously taking quite a bit longer than it should were everything running at the quoted speeds.
Am I missing something here? Is there anything I can do to improve matters?
Burning software adjusts the write speed according to specific media used. There is info in cd/dvd/bd about what writing speeds it supports. Also the recording service adjusts the write speed based on recorder info.
Probably that is a bug in that software, you may try something else. But actually veerain told you the software will try to find out the possible values based on the device capabilities and the supported speed(s) of the cd/dvd/bd. http://www.linuxquestions.org/questi...urning-922094/
Interesting! I would expect the system to burn at the lowest common speed - in my case set by the 6x media rather than the 12x of the burner - but that doesn't explain why it insists on burning at only 4x, which jamieson20000e's reply indicates is normal!
I have a different drive, and not a BD drive at that, but I am using Verbatim discs for DVD+R rated at 16x. Using mostly K3b, I rarely have a burn faster than ~6x. It does not matter if speed is set to Auto or if I just go ahead and select 16x. I'm not suggesting it is the disc because I just don't know. Maybe when this supply runs out, I will find out which disc(s) are supposed to be the best and try that.
I'm going to say it's probably the hardware (the burner). I don't have the Pioneer, but have a LG WH14NS40 BD-RE. I use either Philips or JVC single-layer 6x white inkjet hub printable (I don't 'print' on them, just use my own handwriting).
This setup when I start to burn, usually *starts* at the 6x speed of the media, but *will* in all cases eventually get to almost 15x (~90MB/sec!). I only use K3B also.
YMMV but this seems to be a good explanation as to why you can't burn at better speeds.
Just as a good rule of thumb, whenever you burn anything for long-term data storage purposes, always use the slowest write speed allowed by the drive and software. Even the best error correction often can fail with faster write rates. The old saying, "Good things come to those with patience" often applies.
Lots of good points there, and I can endorse what reaperX7 says about "slower is better" - or at least more reliable long term! However, most of this stuff is video and short term really, but as I do a fair bit of it, it would be nice to cut down the amount of time waiting for it to burn.
Green_vein's experience is the behavior I would expect - or at least the start speed is. What I can't get my head around is that if 6x is the lowest common denominator, why it starts at 5x before deciding that the burner doesn't support 5x, and dropping even lower.
I have found a thread elsewhere that suggests that unless multi-session is specifically disabled, K3b will try and use growisfs instead of cdrecord, and that growisofs has issues with Bluray. The suggested remedy is to specifically disable multi-session AND specify cdrecord for burning, rather than allowing K3b to auto-select.
I'll give that a try next time I have to burn a disk. It shouldn't be long.....
Just as a good rule of thumb, whenever you burn anything for long-term data storage purposes, always use the slowest write speed allowed by the drive and software. Even the best error correction often can fail with faster write rates. The old saying, "Good things come to those with patience" often applies.
That applies in some circumstances, yes, but in burning large BD's (25GB+) I'll disagree wholeheartedly. Out of 50 that I've burned so far, 45 are fine and the other 5 were just bad BD's and nothing to do with the burning process. As has been said before, waiting for a single-layer BD to burn for 30+ minutes sucks by miles over waiting for one to finish being burned in 15 minutes, especially if one does a lot of burning (figure on average I'll have about 200MB leftover on each of my 25GB BD's, so that's still, just to keep it simple, 25x45=1TB+ of data I have, then figure the time I saved @15 minutes per BD 15x45=675 minutes=11.25 hours sure beats 22.5 hours). This is just me, of course. I follow the 'patience' rule in more important aspects of life, heh heh, when I'm sitting at the computer I don't want to twiddle my thumbs any longer than necessary and when one is burning, trying to do other things on the computer really slows *everything* down badly.
Last edited by green_vein; 01-15-2015 at 09:48 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.