9:42 p.m.
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
10:50 p.m.
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
6:42 p.m.
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 <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
2:25 p.m.
Richard Shaw wrote:
On Tue, Jul 30, 2013 at 6:42 PM, Bill Davidsen <davidsen(a)tmr.com
<mailto:davidsen@tmr.com>> 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.
Sorry, I didn't catch that. As you say, it conflicts, due to the cdrkit using
the same names as the well established and supported software.
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.
I know what it does, but I've had good luck with the tools I've been using,
so I
didn't feel the need. If that's a GUI tool I never will, I find scripting a good
way to keep my computer from getting bored. Somewhere around I have scripts to
create INF files for burning tracks rather than a total CD clone, and to grab
info and add it to the MP3 output files so tools which use them can get artist
and title.
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 :)
Thank you for the laugh, sounds like me talking about driving the car with the
automatic transmission.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
8:57 p.m.
On Tue, Jul 30, 2013 at 6:42 PM, Bill Davidsen <davidsen(a)tmr.com> 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
7:20 p.m.
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 :-).
8:44 p.m.
On Mon, Jul 29, 2013 at 8:35 AM, Tom Horsley <horsley1953(a)gmail.com> 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
8:35 a.m.
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.
7:50 a.m.
On Sun, Jul 28, 2013 at 10:50 PM, Richard Shaw <hobbes1069(a)gmail.com> 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
8 a.m.
On Mon, Jul 29, 2013 at 5:14 AM, Tom Horsley <horsley1953(a)gmail.com> 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
7:51 a.m.
On Mon, Jul 29, 2013 at 12:24 AM, Edward Martinez <edwardm1(a)live.com> 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/<http://www.stephencuppett.com/wordpress/2009/08/02...
Yup, saw that, it looks like he's just treating it as an oversized DVD
rather then a true BD.
Richard
5:14 a.m.
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.
12:24 a.m.
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-l...
--
6:56 p.m.
Richard Shaw wrote:
On Mon, Jul 29, 2013 at 8:35 AM, Tom Horsley
<horsley1953(a)gmail.com
<mailto:horsley1953@gmail.com>> 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 <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
3915
days inactive
3917
days old
13 comments
4 participants
participants (4)
-
Bill Davidsen -
Edward M -
Richard Shaw -
Tom Horsley