[CinCV TNG] Creating a Blu-Ray with Cinelerra 5.1

Good Guy good1.2guy at gmail.com
Sun May 8 20:28:42 CEST 2016


>
> # cd /home/terje/Cin_Video/bd_20160506-112338
>
> # mount -o loop /home/terje/Cin_Video/bd_20160506-112338/bd.udfs
> /home/terje/Cin_Video/bd_20160506-112338/udfs
> ls -l /home/terje/Cin_Video/bd_20160506-112338/udfs
> total 0
> drwxr-xr-x 2 root root 40 May  6 13:51 lost+found
>
> # du -sc <target>/udfs
> -bash: target: No such file or directory
>
> # du -sc /home/terje/Cin_Video/bd_20160506-112338/udfs
> 0    /home/terje/Cin_Video/bd_20160506-112338/udfs
> 0    total
>

It looks like the bdwrite step doesnt even start.  If it runs, but in
error, it still creates a BDMV/ set of files in the target udfs path.  I
suggest you run bdwrite by hand one time, to see what the $@#@ is the
problem.

cd /home/terje/Cin_Video/bd_20160506-112338/
mount -o loop ./bd.udfs ./udfs
/<cin-bin-path>/bdwrite ./udfs ./bd.m2ts

If this produces error messages, please send the log to me.

then look at the results in ./udfs
in particular, the stream file should exist in
./udfs/BDMV/STREAM/00000.m2ts
and have the same size as the ./bd.m2ts file size.

gg

On Sun, May 8, 2016 at 7:58 AM, Terje J. Hanssen <terje at nordland-teknikk.no>
wrote:

> GG,
> I have made yet another attempt to burn the Blu-ray video disk with the dd
> command, but sorry, still unsuccessful here.
>
> It doesn't look to be any failure with the Blu-ray device either, as I can
> copy and paste with Nautilus file manager which starts writing bd.m2ts or
> bd.udfs to the same BD-RE DL disk. I even quitted writing bd.m2ts after
> 4.7GB, and this video clip was also possible to playback afterwards.
> And I have previous written video and image backups to a handful BD-R DL
> and a BD-RE DL data disks (iso I think).
>
>
> Below follows some collected screen shots and terminal I/O (more or less
> loose), in case you can discover more information out about what prohibit
> the dd Blu-ray to work here.
>
> 1. LinuxUDF BD disk
>
> a) Attached screen shot from Nautilus when the BD-RE formatted disk is
> loaded with its properies
>
> b) Terminal I/O
> df -h /run/media/terje/LinuxUDF
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/sr0         34G  5,1G   29G  16% /run/media/terje/LinuxUDF
> (this command is taken after the test to copy&paste with Nautilus to the
> BD-RE disk. Even I deleted the test files, it didn't free up the available
> space to 34G as before?)
>
> c) I can umount and eject the BD-RE disk both with Nautilus and with root
> privilegies in a terminal
>
> (However, once while burned DVD disk was mounted I got a problem to
> unmount it, and got this information beside:
> # umount /run/media/terje/CDROM
> umount: /run/media/terje/CDROM: target is busy
>         (In some cases useful info about processes that
>          use the device is found by lsof(8) or fuser(1).)
>
>
> 2. Blu-ray created hdd files
>
> a) Attached screen shot from Nautilus
>
> b) Terminal I/O
> cd /home/terje/Cin_Video/bd_20160506-112338
>  ls
> bd.m2ts  bd.sh  bd.udfs  bd.xml  udfs
> file  *
> bd.m2ts: data
> bd.sh:   Bourne-Again shell script, ASCII text executable
> bd.udfs: data
> bd.xml:  XML document text
> udfs:    directory
>
> 3. bd.sh
>
> cat bd.sh
> #!/bin/bash -ex
> PATH=$PATH:/home/cin
> mkdir -p $1/udfs
> sz=`du -sb $1/bd.m2ts | sed -e 's/[     ].*//'`
> blks=$((sz/2048 + 4096))
> mkudffs $1/bd.udfs $blks
> mount -o loop $1/bd.udfs $1/udfs
> bdwrite $1/udfs $1/bd.m2ts
> umount $1/udfs
> echo To burn bluray, load writable media and run:
> echo growisofs -dvd-compat -Z /dev/bd=$1/bd.udfs
>
> 4. loopback mount the <target>/bd.udfs
>
> # cd /home/terje/Cin_Video/bd_20160506-112338
>
> # mount -o loop /home/terje/Cin_Video/bd_20160506-112338/bd.udfs
> /home/terje/Cin_Video/bd_20160506-112338/udfs
> ls -l /home/terje/Cin_Video/bd_20160506-112338/udfs
> total 0
> drwxr-xr-x 2 root root 40 May  6 13:51 lost+found
>
> # du -sc <target>/udfs
> -bash: target: No such file or directory
>
> # du -sc /home/terje/Cin_Video/bd_20160506-112338/udfs
> 0    /home/terje/Cin_Video/bd_20160506-112338/udfs
> 0    total
>
> # umount /home/terje/Cin_Video/bd_20160506-112338/udfs
>
>
> 5. Tried to burn the BD_RE video disk (in a Gnome session)
>
> # cd /home/terje/Cin_Video/bd_20160506-112338
>
> # dd if=./bd.udfs of=/dev/sr0 bs=2048000
> dd: error writing ‘/dev/sr0’: No space left on device
> 2296+0 records in
> 2295+0 records out
> 4700372992 bytes (4.7 GB) copied, 1.52918 s, 3.1 GB/s
>
> # dd if=./bd.udfs of=/dev/sr0 bs=2048000
>
> 1174+0 records in
> 1174+0 records out
> 2404352000 bytes (2.4 GB) copied, 563.295 s, 4.3 MB/s
>
> One question:
> Shouldn't there be terminal outputs to show the progress (when it works),
> in a similar way like for DVD burning as shown in the Features5 manual
> section 7.1?
>
> But again unsuccessful - still no content was written to the disk, even it
> seemingly should do this with the blu-led lamp flashing for several hours.
>
> What is also bad,, as it doesn't seem to be possible to quit this false
> burning process.
> The Blu-ray burner get a "hard hang" and the machine won't shutdown or
> reboot either. The only thing that I found can stop this behaviour is the
> Power Off button, to get the disk released and ejected.
>
>
> 6. Tried to burn the BD_RE video disk (in console mode)
>
> Tried also to logon as root in console mode and test the burning from
> there to avoid possibly unwanted behaviour from Gnome .
> This run during this night (several hours) and outputted several I/O
> errors that I also could get out with dmesg afterwards:
>
> # cd /home/terje/Cin_Video/bd_20160506-112338
>
> # dd if=./bd.udfs of=/dev/sr0 bs=2048000
>
> # dmesg | grep "I/O error"
> [ 6695.783866] blk_update_request: I/O error, dev sr0, sector 43630640
> [ 6695.783873] Buffer I/O error on dev sr0, logical block 5453830, lost
> async page write
> [ 6695.784041] Buffer I/O error on dev sr0, logical block 5453831, lost
> async page write
> [ 6695.784379] Buffer I/O error on dev sr0, logical block 5453832, lost
> async page write
> [ 6695.784822] Buffer I/O error on dev sr0, logical block 5453833, lost
> async page write
> [ 6695.785315] Buffer I/O error on dev sr0, logical block 5453834, lost
> async page write
> [ 6695.785779] Buffer I/O error on dev sr0, logical block 5453835, lost
> async page write
> [ 6695.786221] Buffer I/O error on dev sr0, logical block 5453836, lost
> async page write
> [ 6695.786657] Buffer I/O error on dev sr0, logical block 5453837, lost
> async page write
> [ 6695.787095] Buffer I/O error on dev sr0, logical block 5453838, lost
> async page write
> [ 6695.787524] Buffer I/O error on dev sr0, logical block 5453839, lost
> async page write
> [ 6733.929814] blk_update_request: I/O error, dev sr0, sector 43664368
> [ 6733.929976] Buffer I/O error on dev sr0, logical block 5458046, lost
> async page write
> [ 6733.930274] Buffer I/O error on dev sr0, logical block 5458047, lost
> async page write
> ........ snip
> [10418.911402] Buffer I/O error on dev sr0, logical block 6343445, lost
> async page write
> [10418.911680] Buffer I/O error on dev sr0, logical block 6343446, lost
> async page write
> [10551.079426] blk_update_request: I/O error, dev sr0, sector 50852400
> [10551.079564] Buffer I/O error on dev sr0, logical block 6356550, lost
> async page write
> [10551.079702] Buffer I/O error on dev sr0, logical block 6356551, lost
> async page write
> [10551.079877] Buffer I/O error on dev sr0, logical block 6356552, lost
> async page write
> [10551.080155] Buffer I/O error on dev sr0, logical block 6356553, lost
> async page write
> [10551.080433] Buffer I/O error on dev sr0, logical block 6356554, lost
> async page write
> [10551.080713] Buffer I/O error on dev sr0, logical block 6356555, lost
> async page write
> [10551.080992] Buffer I/O error on dev sr0, logical block 6356556, lost
> async page write
> [10551.081269] Buffer I/O error on dev sr0, logical block 6356557, lost
> async page write
> [10551.081550] Buffer I/O error on dev sr0, logical block 6356558, lost
> async page write
> [10551.081824] Buffer I/O error on dev sr0, logical block 6356559, lost
> async page write
>
> 1174+0 records in
> 1174+0 records out
> 35767906304 bytes (36GB) copied, 15550.5s, 2.3 MB/s
>
> (15550,5 s seems to be 4.3 hours).
>
>
> Terje J. H
>
>
>
> Den 06. mai 2016 20:25, skrev Good Guy:
>
>> the /<path>/bd_<date>_<time>/bd.sh file is a script similar to the dvd.sh
>> script.  The general design of the dvd/bd generation operations is to:
>> 1) render media using batch rendering
>> 2) terminate cinelerra to start a script which creates the target device
>> filesystem data.
>> these scripts are the dvd.sh and bd.sh scripts written into the target
>> directory.
>>
>> For dvd, the general plan is to write a directory <target>/iso with the
>> dvd
>> filesystem via dvdauthor.
>> then to generate an iso9660 filesystem and write it to a dvd via growisofs
>> -dvd-compat -Z ....
>>
>> For the bluray, the filesystem generation is slightly harder.
>> First, it creates an empty filesystem image <target>/bd.udfs using
>> mkudffs.
>> This empty filesystem
>> is loopback mounted: mount -o loop ./bd.udfs ./udfs.  The linux kernel
>> manages the filesystem image.
>> The bdwrite program creates the needed BDMV bluray filesystem onto udfs,
>> which the kernel stores
>> onto the image file bd.udfs.  When udfs is unmounted, the kernel finalizes
>> the disk image on bd.udfs.
>> The bd.udfs image can be written directly to a bluray disk, via dd or
>> growisofs.  rewrite-able disks
>> must be initialized once before they are usable via: dvd+rw-format
>> /dev/sr0
>>
>> One booby trap may be that the distro sw may automount the loopback system
>> once it has
>> been discovered via mount -o loop ... which may cause the umount
>> <target>/udfs to not
>> close the session since the OS is still looking at /dev/loop0  =
>> /run/media/root/LinuxUDF.
>> I don't know if this is serious, but it may be.
>>
>> The dd if=... in your log output seems to say that dd:
>>
>> dd if=./bd.udfs of=/dev/sr0 bs=2048000
>> dd: error writing ‘/dev/sr0’: No space left on device
>>
>> ran out of space on the earlier runs.  Any idea what this is?
>> Looks good on the last report.  Here is an experiment to try:
>> loopback mount the <target>/bd.udfs image, and see if it has
>> the BDMV filesystem written to it.
>>
>> mount -o loop <target>/bd.udfs <target>/udfs
>> ls -l <target>/udfs
>> du -sc <target>/udfs
>> umount <target>/udfs
>>
>> also, see if this sequence coerces the os to mount
>> /run/media/root/LinuxUDF.
>> it would be nice to know when this issue is invoked.
>>
>> ffplay -vf setdar=dar=16/9 -playlist 0 bluray:<target>/udfs
>> (while it is still mounted) should replay the recorded media,
>> if ffplay has been built with libbluray.  I can help with this if you
>> would
>> like.
>> I usually try to do this before I burn, since burning can take a long
>> time.
>>
>> Other players my be useful for this, even cinelerra.  The system stream
>> for
>> the media is copied to: <target>/udfs/BDMV/STREAM/00000.m2ts
>> which may be opened directly by ffmpeg in cinelerra, BUT be sure that
>> ffmpeg probes early is set, the format is close to mpeg, and libzmpeg3
>> will try if it sees it first, and it will only see the audio.
>> be sure to umount the image when you are done testing it, and before
>> burning.
>>
>> good bluray documentation is hard to come by.  I will look around to see
>> if
>> I can
>> find a 422 format.  I have no idea what may be useful.  Most of this comes
>> from
>> the ffmpeg/codec presets, not from an authoritative source.
>>
>> I have written usable BD disks, and even multi-title sets (by hand using
>> bdwrite).
>> Both write-once, and re-writable media have worked on my home bd players.
>> Phyllis says she will give it a try from scratch using the docs, and see
>> what
>> if there is enough said to make a go of it.
>>
>> gg
>>
>>
>>
>> On Fri, May 6, 2016 at 11:24 AM, Terje J. Hanssen <
>> terje at nordland-teknikk.no
>>
>>> wrote:
>>> The "BD burning finished  finally, but unsuccessful - no content on the
>>> BD-RE disk:
>>>
>>> # dd if=./bd.udfs of=/dev/sr0 bs=2048000
>>> 17464+1 records in
>>> 17464+1 records out
>>> 35767906304 bytes (36 GB) copied, 12286.2 s, 2.9 MB/s
>>>
>>> # ls -la /dev/sr0
>>> brw-rw----+ 1 root cdrom 11, 0 May  6 19:05 /dev/sr0
>>>
>>> df -h /dev/sr0
>>> Filesystem      Size  Used Avail Use% Mounted on
>>> /dev/sr0         34G  2,1M   34G   1% /run/media/terje/LinuxUDF
>>>
>>> du -sh /run/media/terje/LinuxUDF
>>> 0    /run/media/terje/LinuxUDF
>>>
>>> ls /run/media/terje/LinuxUDF
>>> lost+found
>>>
>>>
>>> Terje J. H
>>>
>>>
>>>
>>> Den 06. mai 2016 17:42, skrev Terje J. Hanssen:
>>>
>>> I've tested to create my first Blu-ray video disk using the latest
>>>> Cinelerra 5.1 binary for openSUSE Leap 42.1 (2016-05-04 21:49, dynamic
>>>> linked) and the procedures given in the Features5 manual.
>>>>
>>>> 1) ProRes SD PAL sources
>>>> For this test I loaded five 10-bit ProRes 422 (HQ) Quicktime (.mov)
>>>> files
>>>> of a oototal video duration of almost 6 hours (5 hours, 53.5 minutes)
>>>> according to ffprobe
>>>>
>>>> terje at linux-ysan:/video> du -sh Hi8*
>>>> 40G    Hi8_tape_1_1992+1993.mov
>>>> 35G    Hi8_tape_2_1992.mov
>>>> 35G    Hi8_tape_3_1992.mov
>>>> 31G    Hi8_tape_4_1992.mov
>>>> 56G    Hi8_tape_5_1992+1993.mov
>>>>
>>>>
>>>> 2) Indexing (idx)
>>>> The same comments as for Creating a DVD
>>>>
>>>>
>>>> 3) Set Format window (see the attached screen shot)
>>>> PAL presets contained correct 720x576 at 25fps
>>>>
>>>> Selected Color model: RGBA-Float (as for previous .pro)
>>>>           Aspect ratio: 16:9 (the source i 4:3)
>>>>           Audio; 2 channels (stereo)
>>>>           Interlaced: unknows (?)
>>>>
>>>>
>>>> 4) Create BD window (attached screen shot)
>>>> Same comments as for Creating a DVD
>>>>
>>>> Selected:  Media: 50 GB (Dual layer BD-RE)
>>>>             Aspect ration: 16x9 (?)
>>>>
>>>>
>>>> 5) Batch render window (attached screen shot)
>>>> The same comments as for DVD except for FFMPEG
>>>>
>>>> Selected Video bitrate: 12000000 (from default 8000000)
>>>>
>>>> Which codec is used, H.264?
>>>> Which color model? Looks like 4:2:0 see the result
>>>>
>>>> Is 4:2:2 an options, possibly only for HEVC (H.265)?
>>>>
>>>>
>>>> 6) BD rendering
>>>>
>>>> ETA: 01:58 or near 2 hours or about 1/3 of the 5.9 hours total video
>>>> duration
>>>>
>>>> CPU load: ca. 390-490% according to top
>>>>
>>>> My i7-6700K Skylake CPU is a Quad Core cpu but has 8 threads
>>>> Because of 490% it looks for me like the CPU load % is for the threads
>>>> and not for the cores?
>>>> If so, 4/8 - 5/8 of the total cpu power is used, and possibly could have
>>>> been extended to 6/8 - 7/8 ?
>>>>
>>>> The cpu fan seemed to run continuously.
>>>>
>>>> MEM load looks low also for Blu-ray rendering, only 2% (I have 32GB
>>>> available)
>>>>
>>>>
>>>> 7) Created BD files
>>>>
>>>> cd ~/Cin_Video/bd_20160506-112338
>>>> file *
>>>>
>>>> bd.m2ts: data
>>>> bd.sh: Bourne-Again shell script, ASCII text executable
>>>> bd.udfs: data
>>>> bd.xml: XML document text
>>>> udfs: directory
>>>>
>>>> du -sh *
>>>> 34G    bd.m2ts
>>>> 4,0K    bd.sh
>>>> 2,2M    bd.udfs
>>>> 24K    bd.xml
>>>> 4,0K    udfs
>>>>
>>>> The size given above for bd.udfs is wrong, I don't know wh(?).
>>>> Nautilus file manager showed 35.8 GB for both bd.m2ts and for bd.udfs
>>>>
>>>> ls -la bd.udfs
>>>> -rw-r----- 1 terje users 35767906304 mai    6 13:51 bd.udfs
>>>>
>>>> ffprobe bd.m2ts
>>>> Input #0, mpegts, from 'bd.m2ts':
>>>>    Duration: 05:53:25.01, start: 0.000000, bitrate: 13490 kb/s
>>>>    Program 1
>>>>      Metadata:
>>>>        service_name    : Service01
>>>>        service_provider: FFmpeg
>>>>      Stream #0:0[0x1011]: Video: h264 (Constrained Baseline)
>>>> ([27][0][0][0] / 0x001B), yuv420p, 720x576 [SAR 213:200 DAR 213:160], 25
>>>> fps, 25 tbr, 90k tbn, 50 tbc
>>>>      Stream #0:1[0x1100]: Audio: ac3 ([129][0][0][0] / 0x0081), 48000
>>>> Hz,
>>>> stereo, fltp, 224 kb/s
>>>>
>>>> As seen, Video: h264 and yuv420p
>>>>
>>>> Is it possible to preserve the 422 color from ProRes source to BD,
>>>> or will this not be compatible with previous 3k BD players?
>>>> The new generation 4k BD players support 422 and HEVC (H.265)
>>>>
>>>>
>>>> 8) Burning the BD video on BD-RE (rewriteable, 1-2x speed, 50GB dual
>>>> layer)
>>>> As seen three attempts were neccessary, and I tried to unmount the BD
>>>> device with Nautilus each time in case this disturbed the burn process.
>>>> (Nautilus also asked to drag file for the device when I opened it)
>>>>
>>>> cd /home/terje/Cin_Video/bd_20160506-112338
>>>>
>>>> ls
>>>> bd.m2ts  bd.sh  bd.udfs  bd.xml  udfs
>>>>
>>>> dvd+rw-format /dev/sr0
>>>> * BD/DVD±RW/-RAM format utility by <appro at fy.chalmers.se>, version 7.1.
>>>> * 50.1GB BD media detected.
>>>> * formatting 0.0\
>>>>
>>>> dd if=./bd.udfs of=/dev/sr0 bs=2048000
>>>> dd: error writing ‘/dev/sr0’: No space left on device
>>>> 1+0 records in
>>>> 0+0 records out
>>>> 2048 bytes (2.0 kB) copied, 0.0259193 s, 79.0 kB/s
>>>>
>>>> dd if=./bd.udfs of=/dev/sr0 bs=2048000
>>>> dd: error writing ‘/dev/sr0’: No space left on device
>>>> 1+0 records in
>>>> 0+0 records out
>>>> 2048 bytes (2.0 kB) copied, 0.00495079 s, 414 kB/s
>>>>
>>>> dd if=./bd.udfs of=/dev/sr0 bs=2048000
>>>> .....
>>>> Still burning, hopefully. The blue led lamp has flashed over 2 hours so
>>>> far.......
>>>>
>>>>
>>>> Terje J. H
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Cinelerra mailing list
>>>> Cinelerra at lists.cinelerra-cv.org
>>>> http://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra
>>>>
>>>> _______________________________________________
>>> Cinelerra mailing list
>>> Cinelerra at lists.cinelerra-cv.org
>>> http://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra
>>>
>>>
>>
>> _______________________________________________
>> Cinelerra mailing list
>> Cinelerra at lists.cinelerra-cv.org
>> http://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra
>>
>
>
> _______________________________________________
> Cinelerra mailing list
> Cinelerra at lists.cinelerra-cv.org
> http://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cinelerra-cv.org/pipermail/cinelerra/attachments/20160508/ee08b6de/attachment.html>


More information about the Cinelerra mailing list