The state of blu-ray burning in linux is terrible

classic Classic list List threaded Threaded
37 messages Options
12
Reply | Threaded
Open this post in threaded view
|

The state of blu-ray burning in linux is terrible

Richard Shaw-6
DISCLAIMER: Yes I'm whining, but hopefully someone who wants to user their BD writer will find this useful...

Well I thought I would try to make my first blu-ray movie from some home movies instead of down converting them to DVD like I have been... Only to find out not only is it currently laborious process, it's actually technically impossible for FOSS. 

The laborious part is trying to get it into the right format (x264 with very specific settings and separate audio file), but even if you manage that part, there's no UDF 2.5 write support in linux. If you're lucky, you BD player may not care.

No problem, I'll worry about that later, I'll just burn a backup of my pictures that were getting to hard to backup on DVD's....

Put in disc... Check!
Detected in Brasero... Check!
"copy" into new data project... Check!
BURN!

ejects immediately with no helpful error message...

... skip some time spent googling only to get really mad about the whole cdrkit vs. cdrtools debacle...
... skip spending time getting cdrtools 3.01 to build ...

I'm still working on getting the kinks out of that... conflicts with several cdrkit packages (genisoimage, wodim, icedax)

Ok! Last resort, do it the PITA way...

$ dd if=/dev/zero of=/bdimage.udf bs=2048 count=12219392
$ mkudffs bdimage.udf
# sudo mount -t udf -o loop bdimage /mnt/disc

currently copying files into the image file... HOPEFULLY brasero will at least burn the image...

Richard


--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Richard Shaw-6
Ok, ran into a couple of problems:

1. You don't actually get all 25GB after formatting, you get 24.8GB so I needed to modify the dd line to:

$ dd if=/dev/zero of=./picback.udf bs=2048 count=12088320

2. Brasero now doesn't tell me that my image is too big for my disc, but still refuses to write.

Now to see if I can get cdrtools to play nice (or replace cdrkit) or give up and put it in /usr/local and hope brasero can find it there.

Richard

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Edward Martinez
On 7/28/2013 8:50 PM, Richard Shaw wrote:
> Now to see if I can get cdrtools to play nice (or replace cdrkit) or
> give up and put it in /usr/local and hope brasero can find it there.
>

       Have you taken a look at this Howto; It is a bit old, but it may
still apply.
http://www.stephencuppett.com/wordpress/2009/08/02/burning-a-blu-ray-in-linux/


--

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Tom Horsley-5
In reply to this post by Richard Shaw-6
On Sun, 28 Jul 2013 21:42:03 -0500
Richard Shaw wrote:

> currently copying files into the image file... HOPEFULLY brasero will at
> least burn the image...

Unlikely in my experience. What works for me is to download
and built from source the "real" cdrtools:

http://cdrecord.berlios.de/private/cdrecord.html

But you'll have a bigger problem if you think you can
play a movie on a commercial blu-ray player. Thanks
to the movie industry, most of them refuse to treat
writable media as anything other than a data disk.
--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Richard Shaw-6
In reply to this post by Richard Shaw-6
On Sun, Jul 28, 2013 at 10:50 PM, Richard Shaw <[hidden email]> wrote:
Ok, ran into a couple of problems:

1. You don't actually get all 25GB after formatting, you get 24.8GB so I needed to modify the dd line to:

$ dd if=/dev/zero of=./picback.udf bs=2048 count=12088320

Still ran out of "writable" space on the disc at about 97.7% complete so I guess it needs to be a little smaller. If anyone is wondering I'm getting the "count" from:

$ dvd+rw-mediainfo /dev/sr0 (with a disc in the drive obviously)

It lists several "sizes" for the media and I'm not really sure what the difference is. Interestingly though, brasero showed there would still be free space on disc with my last image file but growisofs from the command line failed...

Richard

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Richard Shaw-6
In reply to this post by Edward Martinez
On Mon, Jul 29, 2013 at 12:24 AM, Edward Martinez <[hidden email]> wrote:
On 7/28/2013 8:50 PM, Richard Shaw wrote:
Now to see if I can get cdrtools to play nice (or replace cdrkit) or give up and put it in /usr/local and hope brasero can find it there.


      Have you taken a look at this Howto; It is a bit old, but it may still apply.
http://www.stephencuppett.com/wordpress/2009/08/02/burning-a-blu-ray-in-linux/

Yup, saw that, it looks like he's just treating it as an oversized DVD rather then a true BD.

Richard 

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Richard Shaw-6
In reply to this post by Tom Horsley-5
On Mon, Jul 29, 2013 at 5:14 AM, Tom Horsley <[hidden email]> wrote:
On Sun, 28 Jul 2013 21:42:03 -0500
Richard Shaw wrote:

> currently copying files into the image file... HOPEFULLY brasero will at
> least burn the image...

Unlikely in my experience. What works for me is to download
and built from source the "real" cdrtools:

http://cdrecord.berlios.de/private/cdrecord.html

Working on that now. I've got it building but it still conflicts with cdrkit because of its "obsoletes/provides" built into the RPM for the old version of cdrtools. I'm trying to get where I can uninstall the conflicting cdrkit RPMs and install the new cdrtools RPMs but they provide different binaries (with the cdrkit binaries being symbolically linked to the old cdrtools binaries names). I may give up and just install to /usr/local if it gets to be too much trouble.


But you'll have a bigger problem if you think you can
play a movie on a commercial blu-ray player. Thanks
to the movie industry, most of them refuse to treat
writable media as anything other than a data disk.

 Yup, I think the biggest problem is lack of UDF 2.5 write support but I'll worry about that when I get that far.

Richard

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Tom Horsley-5
In reply to this post by Richard Shaw-6
On Mon, 29 Jul 2013 07:50:38 -0500
Richard Shaw wrote:

> Still ran out of "writable" space on the disc at about 97.7% complete so I
> guess it needs to be a little smaller. If anyone is wondering I'm getting
> the "count" from:

Blu-rays are exceedingly funky. There is total space, then there is "formatted
space", where there is space reserved for the hardware to try writing
a new copy of a sector that failed. A lot of writer software turns on
the formatted mode by default. I went through a lot of this getting my
isopack software to write to blu-ray, and wrote up some of it here:

http://home.comcast.net/~tomhorsley/software/isopack/isopack.html

Of course I also had a batch of media that would always fail around
97, 98%. The new media I got is working fine.
--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Richard Shaw-6
On Mon, Jul 29, 2013 at 8:35 AM, Tom Horsley <[hidden email]> wrote:
On Mon, 29 Jul 2013 07:50:38 -0500
Richard Shaw wrote:

> Still ran out of "writable" space on the disc at about 97.7% complete so I
> guess it needs to be a little smaller. If anyone is wondering I'm getting
> the "count" from:

Blu-rays are exceedingly funky. There is total space, then there is "formatted
space", where there is space reserved for the hardware to try writing
a new copy of a sector that failed. A lot of writer software turns on
the formatted mode by default. I went through a lot of this getting my
isopack software to write to blu-ray, and wrote up some of it here:

http://home.comcast.net/~tomhorsley/software/isopack/isopack.html

Of course I also had a batch of media that would always fail around
97, 98%. The new media I got is working fine.

Well I installed the "real" cdrtools cdrecord and used dconf to change the plugin priority of cdrecord in brasero but it was still a no go.

Ended up using cdrecord directly and it successfully burned my UDF image that growisofs failed on. YAY!

I've also got an idea that MIGHT get cdrtools into Fedora but I'm not going to hold my breath. As a last ditch effort if that doesn't work I'm going to go ahead and see if I can get it into RPM nonfree. I've been doing a TON of reading on the subject I understand the license (and personality) issues but at the end of the day cdrkit is crap and cdrtools works. 

cdrecord burned at almost 6X which is the rated speed of the disc while growisofs only burned at about 2.8X!

Richard

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Thomas Schmitt
In reply to this post by Richard Shaw-6
Hi,

sorry for breaking the thread. I was not subscribed up to now
and did not yet find an archive that exposes message ids.

--------------------------------------------------------------

It is not that bad with Blu-ray. At least with the backends.
(I am the developer of libburn and use BD-R and BD-RE media daily.)

But wodim (or "cdrecord") out of cdrkit should really be used
only for CD.

The slowliness of BD media comes from their Defect Management
which checkreads the written blocks while they are still present
in the drive's buffer. In case of poor read quality the blocks
get written again or redirected to the Spare Area where the data
get stored in replacement blocks.
This checkreading reduces write speed to at most half of the
nominal speed of drive and BD medium.

BD-R do Defect Management by default if they are formatted.
BD-RE can only be used formatted and do Defect Management by default.

--------------------------------------------------------------

Original cdrecord out of cdrtools was already discussed in the this
thread. To my knowledge it is fast with BD-R, because it does not
format them. It is not fast with BD-RE, because it uses SCSI command
WRITE(10) which does not allow to override the slow Defect Management.

--------------------------------------------------------------

growisofs out of dvd+rw-tools has a little bug with BD-R.
  https://bugzilla.redhat.com/show_bug.cgi?id=858029
  https://bugzilla.redhat.com/show_bug.cgi?id=868527
It is supposed to be fixed in
  dvd+rw-tools-7.1-13.fc19
The tiny patch is shown in
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016
Workaround is to explicitely format the BD-R before use by
  dvd+rw-format /dev/sr0
or to use option
  -use-the-force-luke=spare:none
when giving an unformatted BD-R to growisofs.

growisofs formats BD-R by default and then uses slow Defect
Management. This can be prevented by option
   -use-the-force-luke=spare:none
growisofs has no means to prevent Defect Management on BD-RE media.

--------------------------------------------------------------

My own programs, libburn based cdrskin and xorriso, do not format
BD-R by default. So they are as fast as with cdrecord.
Other than with cdrecord it is possible to format BD-R on request
  cdrskin -v dev=/dev/sr0 blank=format_if_needed
  xorriso -outdev /dev/sr0 -format as_needed
which makes them capable of slow Defect Management.
Other than growisofs and cdrecord, cdrskin and xorriso offer the
opportunity to disable Defect Management on formatted BD-R and
on BD-RE
  cdrskin stream_recording=on ...cdrecord-like-burn-options...
  xorriso -stream_recording on ...xorriso-burn-commands...
This is especially helpful with 2x BD-RE, which elsewise need
an awfully long time to write their capacity of 22.5 GiB.


Have a nice day :)

Thomas

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Tim-163
On Tue, 2013-07-30 at 08:52 +0200, Thomas Schmitt wrote:
> I was not subscribed up to now and did not yet find an archive that
> exposes message ids.

For future reference:  The gmane newsgroup interface is one way to read
old messages and respond to them, in thread.  Messages sent through it,
end up back on this list.  It works in both directions.

If I've recalled the right group correctly:

News group: gmane.linux.redhat.fedora.general
Information:  http://dir.gmane.org/gmane.linux.redhat.fedora.general

--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686

Don't send private replies to my address, the mailbox is ignored.  I
read messages from the public lists.



--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Richard Shaw-6
In reply to this post by Thomas Schmitt
On Tue, Jul 30, 2013 at 1:52 AM, Thomas Schmitt <[hidden email]> wrote:
It is not that bad with Blu-ray. At least with the backends.
(I am the developer of libburn and use BD-R and BD-RE media daily.)

But wodim (or "cdrecord") out of cdrkit should really be used
only for CD.

The slowliness of BD media comes from their Defect Management
which checkreads the written blocks while they are still present
in the drive's buffer. In case of poor read quality the blocks
get written again or redirected to the Spare Area where the data
get stored in replacement blocks.
This checkreading reduces write speed to at most half of the
nominal speed of drive and BD medium.

BD-R do Defect Management by default if they are formatted.
BD-RE can only be used formatted and do Defect Management by default.

Ahh.. Makes sense.


growisofs out of dvd+rw-tools has a little bug with BD-R.
  https://bugzilla.redhat.com/show_bug.cgi?id=858029
  https://bugzilla.redhat.com/show_bug.cgi?id=868527
It is supposed to be fixed in
  dvd+rw-tools-7.1-13.fc19

Thanks! I just installed it from updates-testing. I'll give it a try.

 
The tiny patch is shown in
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016
Workaround is to explicitely format the BD-R before use by
  dvd+rw-format /dev/sr0

Ok. A related question to that... When I use dvd+rw-mediainfo I see several different capacaities. Obviously if you use the formatting with defect management then you're going to loose some capacity, but the output is not clear which one is the correct. Since I'm using my BD-R's for backup purposes, I want to know exactly how much space I have to work with.


My own programs, libburn based cdrskin and xorriso, do not format
BD-R by default. So they are as fast as with cdrecord.
Other than with cdrecord it is possible to format BD-R on request
  cdrskin -v dev=/dev/sr0 blank=format_if_needed
  xorriso -outdev /dev/sr0 -format as_needed
which makes them capable of slow Defect Management.
Other than growisofs and cdrecord, cdrskin and xorriso offer the
opportunity to disable Defect Management on formatted BD-R and
on BD-RE
  cdrskin stream_recording=on ...cdrecord-like-burn-options...
  xorriso -stream_recording on ...xorriso-burn-commands...
This is especially helpful with 2x BD-RE, which elsewise need
an awfully long time to write their capacity of 22.5 GiB.

I learn something new every day! The great thing about linux is there's usually multiple ways of getting something done... The problem with linux is there's usually multiple ways of getting something done! :)

I'm quite comfortable on the command line but sometimes for some things I really just want an easy/GUI way to do things. In this case, I just want to pull up a project (brasero) and drag files/folders over to the project, and click burn.

 It seems that brasero can use libburn but I have had no luck in getting brasero to actually burn. It recognizes the disc, tells me if I'm over capacity or not, but just will not burn. Should I try bumping up the priority for the plugin for libburn? 

After I get my pictures backed up, my next project is to get blu-ray video working (at least as well as it can without UDF 2.5 write support). Can your tools help me there?

Thanks,
Richard

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Thomas Schmitt
Hi,

Richard Shaw wrote:
> When I use dvd+rw-mediainfo I see
> several different capacaities. Obviously if you use the formatting
> with defect management then you're going to loose some capacity, but
> the output is not clear which one is the correct.

You probably mean something like this:

 Mounted Media:         41h, BD-R SRM
 Media ID:              CMCMAG/BA5
 ...
READ FORMAT CAPACITIES:
 unformatted:           12219392*2048=25025314816
 00h(3000):             11826176*2048=24220008448
 32h(0):                11826176*2048=24220008448
 32h(0):                5796864*2048=11871977472
 32h(0):                12088320*2048=24756879360

It is an overview of sizes from which you could choose.
00h and 32h are the Format Codes for the SCSI command FORMAT UNIT.
(3000) is the size of the Spare Area in hexadecimal numbers
counting clusters of 64 KiB. (Cough.)
For some reason my burners report (0) with the format code 32h by
which i could choose a particular payload size. I read different
prescriptions in MMC-5 specs. Shrug.

12219392*2048=25025314816 tells the number of payload blocks,
the block size 2048, and the number of payload bytes.

The command
  dvd+rw-format -ssa=256m /dev/sr0

would choose 256 MiB Spare Area and 24756879360 payload bytes.
("256m" computed from  (25025314816 - 24756879360) / 1024 /1024 )

You may issue own size wishes with a granularity of 16 MiB.
I am not sure whether very small Spare Area sizes below 256 MiB
are supported.

xorriso would report by
  xorriso -outdev /dev/sr0 -list_formats

a similar list
  Format idx 0 : 00h , 11826176s , 23098.0 MiB
  Format idx 1 : 32h , 11826176s , 23098.0 MiB
  Format idx 2 : 32h , 5796864s , 11322.0 MiB
  Format idx 3 : 32h , 12088320s , 23610.0 MiB

and allow choosing by
  xorriso -outdev /dev/sr0 -format by_index_3

or
  xorriso -outdev /dev/sr0 -format by_size_23610m

Other size wishes may be submitted.


> It seems that brasero can use libburn but I have had no luck in
> getting brasero to actually burn. It recognizes the disc, tells me if
> I'm over capacity or not, but just will not burn. Should I try
> bumping up the priority for the plugin for libburn ?

I cannot tell much about Brasero. My problem as user is that i
do not have the Gnome stuff that is needed for recent versions.
My problem as backend developer is that i cannot get in contact
with Brasero developers who would know about its usage of the
backends.


> blu-ray
> video working (at least as well as it can without UDF 2.5 write
> support). Can your tools help me there?

I am not aware of tools to produce UDF 2.50. mkisofs/genisoimage
create UDF 1.02, afaik.

Maybe you get lucky with the Linux kernel capability to mount
UDF read-write. It will be at least more modern than 1.02.
I.e. create large file (by truncate -s, qemu-img, ...),
format by mkudffs, mount -o loop -t udf, then cp into it what
you need, umount, burn file to BD-R.

DVD video and BD video would be an interesting topic for me
to explore (UDF specs are public and free, but sooo awful to read).
I roughly know what mkisofs writes into its ISO 9660/UDF hybrid
filesystems.
I lack of testers resp. test equipment, though.
A BD player and a bunch of factory made DVDs and Blu-rays would
be a good start. But which player and whose Blu-rays are
sufficiently standards compliant to serve as reference ?
The risk is to buy some overly tolerant embedded Linux which
would play any kind of video file from any kind of filesystem.


Have a nice day :)

Thomas

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Richard Shaw-6
On Tue, Jul 30, 2013 at 9:58 AM, Thomas Schmitt <[hidden email]> wrote:
Hi,

Richard Shaw wrote:
> When I use dvd+rw-mediainfo I see
> several different capacaities. Obviously if you use the formatting
> with defect management then you're going to loose some capacity, but
> the output is not clear which one is the correct.

You probably mean something like this:

 Mounted Media:         41h, BD-R SRM
 Media ID:              CMCMAG/BA5
 ...
READ FORMAT CAPACITIES:
 unformatted:           12219392*2048=25025314816
 00h(3000):             11826176*2048=24220008448
 32h(0):                11826176*2048=24220008448
 32h(0):                5796864*2048=11871977472
 32h(0):                12088320*2048=24756879360

It is an overview of sizes from which you could choose.
00h and 32h are the Format Codes for the SCSI command FORMAT UNIT.
(3000) is the size of the Spare Area in hexadecimal numbers
counting clusters of 64 KiB. (Cough.)
For some reason my burners report (0) with the format code 32h by
which i could choose a particular payload size. I read different
prescriptions in MMC-5 specs. Shrug.

So the "unformatted" one is pretty obvious which explains my first failure... but then I tried reducing the image using the 24756879360 (24.8GB) size, which still failed. Should I assume then that failure was because growisofs reserved more spare space in its formatting than I allowed for by my image size? 

If I use 24220008448 when creating my image should my burns always succeed unless I reserve more than a default amount of space for defect management?

xorriso would report by
  xorriso -outdev /dev/sr0 -list_formats

a similar list
  Format idx 0 : 00h , 11826176s , 23098.0 MiB
  Format idx 1 : 32h , 11826176s , 23098.0 MiB
  Format idx 2 : 32h , 5796864s , 11322.0 MiB
  Format idx 3 : 32h , 12088320s , 23610.0 MiB

and allow choosing by
  xorriso -outdev /dev/sr0 -format by_index_3

or
  xorriso -outdev /dev/sr0 -format by_size_23610m

Two questions here... First, in reading about xorriso it's really just for ISO formats correct? But in the case of simply formatting the media, we haven't affected the format choice, right? At this point I could still go with ISO9660 or UDF.

Second question/problem. When I try xorriso -outdev /dev/sr0 -list_formats I get the following:

# xorriso -outdev /dev/sr0 -list_formats
GNU xorriso 1.3.0 : RockRidge filesystem manipulator, libburnia project.

libburn : SORRY : Cannot open busy device '/dev/sr0' : Device or resource busy
libburn : FAILURE : Cannot access '/dev/sr0' as SG_IO CDROM drive
xorriso : FAILURE : Cannot aquire drive '/dev/sr0'
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE' 

This is as root. As you can see I'm running the latest release. I'm also running 1.3.0 of libburn, libisoburn, libisofs... etc.


I am not aware of tools to produce UDF 2.50. mkisofs/genisoimage
create UDF 1.02, afaik.

No, but udftools will create an image up to 2.01, which is what I've been using to format my image files.

Thanks,
Richard

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Thomas Schmitt
Hi,

> So the "unformatted" one is pretty obvious which explains my first
> failure... but then I tried reducing the image using the 24756879360
> (24.8GB) size, which still failed. Should I assume then that failure
> was because growisofs reserved more spare space in its formatting
> than I allowed for by my image size?

growisofs formats blank BD-R to the default size, which is listed with
format code 00h, unless you use option
  -use-the-force-luke=spare:none
which will leave the BD-R unformatted and write with full nominal speed
and without checkreading.

If you cannot get the GUI frontend to using this option, then you
may format the BD-R by dvd+rw-format to the smallest possible size.
(A bold try with -ssa=16m or -ssa=128m should not kill drive or media
 but rather succeed, or fail and leave the BD-R blank. -ssa=256m
 should work in any case.)
This also avoids the little bug at the end of a growisofs BD-R run.


> in reading about xorriso it's really
> just for ISO formats correct?

Currently no UDF, at least. (Bootability leads quite far off ISO,
but not nearer to UDF.)
DVD and BD video would be a new endeavor to me.


> But in the case of simply formatting
> the media, we haven't affected the format choice, right?

We have to distinguish media level formatting and filesystem format.
In the case of DVD and BD video, the medium formatting is not
decisive, except that some media just cannot be written unformatted.

DVD and BD format compatibility is clearly only about the filesystem,
because there is only one readable sector size with these media.
(On CD there is half a dozen sector layouts. From 2352 bytes audio
to 2048 bytes data.)

> # xorriso -outdev /dev/sr0 -list_formats
> ...
> libburn : SORRY : Cannot open busy device '/dev/sr0' : Device or resource busy

Some program holds the device file open with flag O_EXCL, which
has a special meaning on Linux device files. It indicates that
a drive is mounted and shall not be written directly.
We burn programmers joined that club. For us it means that it
shall not be touched at all. (Touching a CD burn can spoil it.)

What do you get from
  mount | fgrep /dev/sr0
  lsof | fgrep /dev/sr0


> udftools will create an image up to 2.01,

Hasn't udftools been superseded by kernel UDF ?


Have a nice day :)

Thomas

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Richard Shaw-6
On Tue, Jul 30, 2013 at 2:53 PM, Thomas Schmitt <[hidden email]> wrote:
> # xorriso -outdev /dev/sr0 -list_formats
> ...
> libburn : SORRY : Cannot open busy device '/dev/sr0' : Device or resource busy

Some program holds the device file open with flag O_EXCL, which
has a special meaning on Linux device files. It indicates that
a drive is mounted and shall not be written directly.
We burn programmers joined that club. For us it means that it
shall not be touched at all. (Touching a CD burn can spoil it.)

What do you get from
  mount | fgrep /dev/sr0
  lsof | fgrep /dev/sr0

That showed the problem... For some reason optical media mounting and unmounting have not been reliable for me for several Fedora releases. Sometimes when I put in a disc, it isn't detected, other times when I switch disc, the old disc is not properly unmounted, which was the case here. 

Currently I have a blank BD-R disc in the drive but mount was still showing the previous disc volume label which is why xorriso was failing...  

 
> udftools will create an image up to 2.01,

Hasn't udftools been superseded by kernel UDF ?

I can't answer that, but when you say "kernel UDF" what exactly do you mean? I'm pretty sure I'm using the kernel UDF modules for reading and writing UDF, I'm just using mkudffs from the udftools package to format the image file.

Thanks,
Richard 

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Bill Davidsen
In reply to this post by Richard Shaw-6
Richard Shaw wrote:

> DISCLAIMER: Yes I'm whining, but hopefully someone who wants to user their BD
> writer will find this useful...
>
> Well I thought I would try to make my first blu-ray movie from some home movies
> instead of down converting them to DVD like I have been... Only to find out not
> only is it currently laborious process, it's actually technically impossible for
> FOSS.
>
> The laborious part is trying to get it into the right format (x264 with very
> specific settings and separate audio file), but even if you manage that part,
> there's no UDF 2.5 write support in linux. If you're lucky, you BD player may
> not care.
>
> No problem, I'll worry about that later, I'll just burn a backup of my pictures
> that were getting to hard to backup on DVD's....
>
> Put in disc... Check!
> Detected in Brasero... Check!
> "copy" into new data project... Check!
> BURN!
>
> ejects immediately with no helpful error message...
>
> ... skip some time spent googling only to get really mad about the whole cdrkit
> vs. cdrtools debacle...
> ... skip spending time getting cdrtools 3.01 to build ...
>
Don't know what issues you have building, it always built flawlessly for me, and
installed in /opt/schily/{bin,lib,man,etc}. Add /opt/schily/bin to the *FRONT*
of PATH, MANPATH, and you are good to go, replaces the stuff Fedora includes
which makes a lot of it start working better.

> I'm still working on getting the kinks out of that... conflicts with several
> cdrkit packages (genisoimage, wodim, icedax)
>
Icedax? Never tried it, too many alternate way to do that.

> Ok! Last resort, do it the PITA way...
>
> $ dd if=/dev/zero of=/bdimage.udf bs=2048 count=12219392
> $ mkudffs bdimage.udf
> # sudo mount -t udf -o loop bdimage /mnt/disc
>
> currently copying files into the image file... HOPEFULLY brasero will at least
> burn the image...
>
The loop mount stuff is a good way to go, you can keep an image fresh and just
burn it when you need a current copy.

--
Bill Davidsen <[hidden email]>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Bill Davidsen
In reply to this post by Richard Shaw-6
Richard Shaw wrote:

> On Mon, Jul 29, 2013 at 8:35 AM, Tom Horsley <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     On Mon, 29 Jul 2013 07:50:38 -0500
>     Richard Shaw wrote:
>
>      > Still ran out of "writable" space on the disc at about 97.7% complete so I
>      > guess it needs to be a little smaller. If anyone is wondering I'm getting
>      > the "count" from:
>
>     Blu-rays are exceedingly funky. There is total space, then there is "formatted
>     space", where there is space reserved for the hardware to try writing
>     a new copy of a sector that failed. A lot of writer software turns on
>     the formatted mode by default. I went through a lot of this getting my
>     isopack software to write to blu-ray, and wrote up some of it here:
>
>     http://home.comcast.net/~tomhorsley/software/isopack/isopack.html
>
>     Of course I also had a batch of media that would always fail around
>     97, 98%. The new media I got is working fine.
>
>
> Well I installed the "real" cdrtools cdrecord and used dconf to change the
> plugin priority of cdrecord in brasero but it was still a no go.
>
> Ended up using cdrecord directly and it successfully burned my UDF image that
> growisofs failed on. YAY!
>
> I've also got an idea that MIGHT get cdrtools into Fedora but I'm not going to
> hold my breath. As a last ditch effort if that doesn't work I'm going to go
> ahead and see if I can get it into RPM nonfree. I've been doing a TON of reading
> on the subject I understand the license (and personality) issues but at the end
> of the day cdrkit is crap and cdrtools works.
>
Actually my big complaint is that Fedora took the name(s) of programs which have
been continuously maintained for about 20 years (I first used it when a CD
burner was a SCSI device and the fast one did 2X). But his software works! I
really wish he had trademarked the names of the programs, I think offering a
knock-off under the same name is like one of the $50 Rolex watches. Fedora
prides themselves on having only open source software, but the ethics of
including an ersatz hack under the original, still maintained, name is ethically
murky. They could have modified every package to call wooden instead.

So please, if you can get it into RPMfusion or similar, that would be great.It
would give us a more functional alternative.

Note that I'm surprised that growisofs didn't work to burn the data once you put
it in an image file, though. You might join the burning mailing list and discuss
with the authors and maintainers. On occasion my problems have been user error,
the documentation and examples of some features are NOT up the quality of the code.


--
Bill Davidsen <[hidden email]>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Tom Horsley-5
On Tue, 30 Jul 2013 19:56:31 -0400
Bill Davidsen wrote:

> Note that I'm surprised that growisofs didn't work to burn the data once you put
> it in an image file

By default growisofs does a "formatted" write, so if your iso image
is exactly the size of the unformatted media, it won't fit. (Why it
can't notice this ahead of time, I'm not sure :-).
--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Reply | Threaded
Open this post in threaded view
|

Re: The state of blu-ray burning in linux is terrible

Richard Shaw-6
In reply to this post by Bill Davidsen
On Tue, Jul 30, 2013 at 6:42 PM, Bill Davidsen <[hidden email]> wrote:
Richard Shaw wrote:
... skip spending time getting cdrtools 3.01 to build ...

Don't know what issues you have building, it always built flawlessly for me, and installed in /opt/schily/{bin,lib,man,etc}. Add /opt/schily/bin to the *FRONT* of PATH, MANPATH, and you are good to go, replaces the stuff Fedora includes which makes a lot of it start working better.

I never run "make install" directly. Since I'm a Fedora packager I always build EVERYTHING in an RPM. So I'm trying to get it to play nice with cdrkit but it may be more trouble than it's worth. 

 
I'm still working on getting the kinks out of that... conflicts with several
cdrkit packages (genisoimage, wodim, icedax)

Icedax? Never tried it, too many alternate way to do that.

It provides the cdrkit alternatives to cdda2wav and cdda2ogg and is pulled in by brasero. I've never used it directly.

 
Ok! Last resort, do it the PITA way...

$ dd if=/dev/zero of=/bdimage.udf bs=2048 count=12219392
$ mkudffs bdimage.udf
# sudo mount -t udf -o loop bdimage /mnt/disc

currently copying files into the image file... HOPEFULLY brasero will at least
burn the image...

The loop mount stuff is a good way to go, you can keep an image fresh and just burn it when you need a current copy.

Yeah, I don't have a problem doing things from the command line but sometimes I just want drag-n-drop and click a button :)

Richard 

--
users mailing list
[hidden email]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
12