HDV on a Blu-ray Disc Without Re-encoding
This topic is treated with reference to the current Cinelerra-GG Manual (and in the Features5 document at least since early 2018): * 14.6 HDV on a Blu-ray Disc Without Re-encoding An MTS file is a video file saved in the high-definition (HD) MPEG Transport Stream video format, commonly called AVCHD. It contains HD video compatible with Blu-ray disc format and is based on the MPEG-2 transport stream. MTS files are often used by Sony, Panasonic, Canon and other HD camcorders. Legal in- put for Video – MPEG1VIDEO, MPEG2VIDEO, H264; Audio – MP1, MP2, AC3, AC3PLUS, DTS, TRUHD. For creating a blu-ray disc, if you have HDV MPEG-2 media that is in blu-ray format, you can save the original quality of your work, rather than rendering it to another format. Follow the steps below directly instead of going through C INELERRA-GG. It has been tested on 10 different MTS files. du -sb /yourHDVfile.MTS # Determine the size of your file in bytes. blocks=((size-in-bytes/2048 + 4096)) # Convert bytes into blocks + a little more. mkudffs /tmp/newfilename.udfs blocks # Create a file with that # of blocks + some extra. mount -o loop /tmp/newfilename.udfs /mntX # Use a mount point like mntX that is not in use. /<cinelerra_installed_path>/bin/bdwrite /mntX /tmp/yourHDVfile.MTS # Substitute cinelerra path. umount /mntX # You must unmount the udfs filesystem growisofs -Z /dev/bd=/tmp/newfilename.udfs # Replace /dev/bd with your bluray hardware device. OR dd if=/tmp/newfilename.udfs of=/dev/bd bs=2048000 # if using rewritable blu-ray; replace bd. =================== When the 1080i/25 HDV-source is recorded via i.Link (Firewire) to disk, the file type and format is HDV.M2T For this test I use the same, downloaded HDV file as previous mentioned (not my file or camcorded by me!) Stream #0:0[0x810]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x814]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 384 kb/s The MPEG2 Video stream is Blu-ray compatible format, while the MP2 Audio stream has to be converted to AC3. Demux, convert the audio and remux to a M2TS stream using this ffmpeg command: ffmpeg -i 20081103140154.m2t -vcodec copy -acodec ac3 20081103140154.m2ts ............. skip Input #0, mpegts, from '20081103140154.m2t': Duration: 00:00:13.44, start: 1042.400000, bitrate: 26598 kb/s Program 100 Stream #0:0[0x810]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x814]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 384 kb/s Stream #0:2[0x815]: Unknown: none ([160][0][0][0] / 0x00A0) Stream #0:3[0x811]: Unknown: none ([161][0][0][0] / 0x00A1) Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (mp2 (native) -> ac3 (native)) Press [q] to stop, [?] for help Output #0, mpegts, to '20081103140154.m2ts': Metadata: encoder : Lavf57.83.100 Stream #0:0: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], q=2-31, 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 90k tbc Stream #0:1: Audio: ac3, 48000 Hz, stereo, fltp, 192 kb/s Metadata: encoder : Lavc57.107.100 ac3 frame= 336 fps=0.0 q=-1.0 Lsize= 45549kB time=00:00:13.43 bitrate=27774.3kbits/s speed= 107x video:41008kB audio:315kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 10.225909% Comment The default AC3 bitrate 192 kb/s here is halph of the source MP2 bitrate 384 kb/s. Any idea about the quality difference? ================ So further to trouble using the procedure steps from the Manual above: Determine the size of the file in bytes. du -sb 20081103140154.m2ts 46642368 20081103140154.m2ts Try to calculate the blocks as blocks=((/466423682048 + 4096)) = 26870.59375 ?? # mkudffs /tmp/bd_20201122_hdv_m2ts.udfs blocks 26870.59375 mkudffs: invalid block-count Obviously something went wrong here. Could someone test and verify these steps and further, to see if a successful Blu-ray BDAV structure is created? (Just now I have no Blu-ray burner in my working PC, so I have to wait with burning the image to a BD-R/RE discs). ------------------ Terje J. H One current and one previous related Blu-ray mail threads as references: https://lists.cinelerra-gg.org/pipermail/cin/2020-November/002709.html https://lists.cinelerra-cv.org/pipermail/cinelerra/2016q4/005609.html
В сообщении от Monday 23 November 2020 03:51:36 Terje J. Hanssen via Cin написал(а):
This topic is treated with reference to the current Cinelerra-GG Manual (and in the Features5 document at least since early 2018):
* 14.6 HDV on a Blu-ray Disc Without Re-encoding
An MTS file is a video file saved in the high-definition (HD) MPEG Transport Stream video format, commonly called AVCHD. It contains HD video compatible with Blu-ray disc format and is based on the MPEG-2 transport stream. MTS files are often used by Sony, Panasonic, Canon and other HD camcorders. Legal in- put for Video – MPEG1VIDEO, MPEG2VIDEO, H264; Audio – MP1, MP2, AC3, AC3PLUS, DTS, TRUHD.
For creating a blu-ray disc, if you have HDV MPEG-2 media that is in blu-ray format, you can save the original quality of your work, rather than rendering it to another format. Follow the steps below directly instead of going through C INELERRA-GG. It has been tested on 10 different MTS files.
du -sb /yourHDVfile.MTS # Determine the size of your file in bytes.
blocks=((size-in-bytes/2048 + 4096)) # Convert bytes into blocks + a little more.
mkudffs /tmp/newfilename.udfs blocks # Create a file with that # of blocks + some extra.
mount -o loop /tmp/newfilename.udfs /mntX # Use a mount point like mntX that is not in use.
/<cinelerra_installed_path>/bin/bdwrite /mntX /tmp/yourHDVfile.MTS # Substitute cinelerra path.
umount /mntX # You must unmount the udfs filesystem
growisofs -Z /dev/bd=/tmp/newfilename.udfs # Replace /dev/bd with your bluray hardware device.
OR dd if=/tmp/newfilename.udfs of=/dev/bd bs=2048000 # if using rewritable blu-ray; replace bd.
===================
When the 1080i/25 HDV-source is recorded via i.Link (Firewire) to disk, the file type and format is HDV.M2T
For this test I use the same, downloaded HDV file as previous mentioned (not my file or camcorded by me!)
Stream #0:0[0x810]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x814]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 384 kb/s
The MPEG2 Video stream is Blu-ray compatible format, while the MP2 Audio stream has to be converted to AC3.
Demux, convert the audio and remux to a M2TS stream using this ffmpeg command:
ffmpeg -i 20081103140154.m2t -vcodec copy -acodec ac3 20081103140154.m2ts
............. skip
Input #0, mpegts, from '20081103140154.m2t': Duration: 00:00:13.44, start: 1042.400000, bitrate: 26598 kb/s Program 100 Stream #0:0[0x810]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x814]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 384 kb/s Stream #0:2[0x815]: Unknown: none ([160][0][0][0] / 0x00A0) Stream #0:3[0x811]: Unknown: none ([161][0][0][0] / 0x00A1) Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (mp2 (native) -> ac3 (native)) Press [q] to stop, [?] for help Output #0, mpegts, to '20081103140154.m2ts': Metadata: encoder : Lavf57.83.100 Stream #0:0: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], q=2-31, 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 90k tbc Stream #0:1: Audio: ac3, 48000 Hz, stereo, fltp, 192 kb/s Metadata: encoder : Lavc57.107.100 ac3 frame= 336 fps=0.0 q=-1.0 Lsize= 45549kB time=00:00:13.43 bitrate=27774.3kbits/s speed= 107x video:41008kB audio:315kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 10.225909%
Comment The default AC3 bitrate 192 kb/s here is halph of the source MP2 bitrate 384 kb/s. Any idea about the quality difference?
Try to listen to it (with VLC?)? *I think* 384 kb/s was for 5.1 ac3 sound .. so, stereo can be compressed further. https://www.vegascreativesoftware.info/us/forum/ac-3-bitrate--63214/ this says 448 kb/s for 5.1
================
So further to trouble using the procedure steps from the Manual above:
Determine the size of the file in bytes.
du -sb 20081103140154.m2ts 46642368 20081103140154.m2ts
Try to calculate the blocks as
blocks=((/466423682048 + 4096)) = 26870.59375 ??
# mkudffs /tmp/bd_20201122_hdv_m2ts.udfs blocks 26870.59375 mkudffs: invalid block-count
Obviously something went wrong here.
Try to round up this size in blocks? 26870.59375 -> 26871
Could someone test and verify these steps and further, to see if a successful Blu-ray BDAV structure is created?
(Just now I have no Blu-ray burner in my working PC, so I have to wait with burning the image to a BD-R/RE discs).
------------------
Terje J. H
One current and one previous related Blu-ray mail threads as references: https://lists.cinelerra-gg.org/pipermail/cin/2020-November/002709.html https://lists.cinelerra-cv.org/pipermail/cinelerra/2016q4/005609.html
Den 23.11.2020 02:20, skrev Andrew Randrianasulu:
В сообщении от Monday 23 November 2020 03:51:36 Terje J. Hanssen via Cin написал(а):
This topic is treated with reference to the current Cinelerra-GG Manual (and in the Features5 document at least since early 2018):
* 14.6 HDV on a Blu-ray Disc Without Re-encoding
An MTS file is a video file saved in the high-definition (HD) MPEG Transport Stream video format, commonly called AVCHD. It contains HD video compatible with Blu-ray disc format and is based on the MPEG-2 transport stream. MTS files are often used by Sony, Panasonic, Canon and other HD camcorders. Legal in- put for Video – MPEG1VIDEO, MPEG2VIDEO, H264; Audio – MP1, MP2, AC3, AC3PLUS, DTS, TRUHD.
For creating a blu-ray disc, if you have HDV MPEG-2 media that is in blu-ray format, you can save the original quality of your work, rather than rendering it to another format. Follow the steps below directly instead of going through C INELERRA-GG. It has been tested on 10 different MTS files.
du -sb /yourHDVfile.MTS # Determine the size of your file in bytes.
blocks=((size-in-bytes/2048 + 4096)) # Convert bytes into blocks + a little more.
mkudffs /tmp/newfilename.udfs blocks # Create a file with that # of blocks + some extra.
mount -o loop /tmp/newfilename.udfs /mntX # Use a mount point like mntX that is not in use.
/<cinelerra_installed_path>/bin/bdwrite /mntX /tmp/yourHDVfile.MTS # Substitute cinelerra path.
umount /mntX # You must unmount the udfs filesystem
growisofs -Z /dev/bd=/tmp/newfilename.udfs # Replace /dev/bd with your bluray hardware device.
OR dd if=/tmp/newfilename.udfs of=/dev/bd bs=2048000 # if using rewritable blu-ray; replace bd.
===================
When the 1080i/25 HDV-source is recorded via i.Link (Firewire) to disk, the file type and format is HDV.M2T
For this test I use the same, downloaded HDV file as previous mentioned (not my file or camcorded by me!)
Stream #0:0[0x810]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x814]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 384 kb/s
The MPEG2 Video stream is Blu-ray compatible format, while the MP2 Audio stream has to be converted to AC3.
Demux, convert the audio and remux to a M2TS stream using this ffmpeg command:
ffmpeg -i 20081103140154.m2t -vcodec copy -acodec ac3 20081103140154.m2ts
............. skip
Input #0, mpegts, from '20081103140154.m2t': Duration: 00:00:13.44, start: 1042.400000, bitrate: 26598 kb/s Program 100 Stream #0:0[0x810]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x814]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 384 kb/s Stream #0:2[0x815]: Unknown: none ([160][0][0][0] / 0x00A0) Stream #0:3[0x811]: Unknown: none ([161][0][0][0] / 0x00A1) Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (mp2 (native) -> ac3 (native)) Press [q] to stop, [?] for help Output #0, mpegts, to '20081103140154.m2ts': Metadata: encoder : Lavf57.83.100 Stream #0:0: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], q=2-31, 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 90k tbc Stream #0:1: Audio: ac3, 48000 Hz, stereo, fltp, 192 kb/s Metadata: encoder : Lavc57.107.100 ac3 frame= 336 fps=0.0 q=-1.0 Lsize= 45549kB time=00:00:13.43 bitrate=27774.3kbits/s speed= 107x video:41008kB audio:315kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 10.225909%
Comment The default AC3 bitrate 192 kb/s here is halph of the source MP2 bitrate 384 kb/s. Any idea about the quality difference? Try to listen to it (with VLC?)?
*I think* 384 kb/s was for 5.1 ac3 sound .. so, stereo can be compressed further.
https://www.vegascreativesoftware.info/us/forum/ac-3-bitrate--63214/ this says 448 kb/s for 5.1
I could not and cannot hear especial noticeable difference using VLC. (Another more suited audio file without background noise, I don't know)
================
So further to trouble using the procedure steps from the Manual above:
Determine the size of the file in bytes.
du -sb 20081103140154.m2ts 46642368 20081103140154.m2ts
Try to calculate the blocks as
blocks=((/466423682048 + 4096)) = 26870.59375 ??
# mkudffs /tmp/bd_20201122_hdv_m2ts.udfs blocks 26870.59375 mkudffs: invalid block-count
Obviously something went wrong here. Try to round up this size in blocks? 26870.59375 -> 26871
I didn't mentione I tried just that also. And again, the same error message: # mkudffs /tmp/bd_20201122.udfs blocks 26871 mkudffs: invalid block-count (I tried also other file-names without succeed, because I seem to remember back there was filename limits somewhere when rendering Blu-rays from Cin).
Could someone test and verify these steps and further, to see if a successful Blu-ray BDAV structure is created?
(Just now I have no Blu-ray burner in my working PC, so I have to wait with burning the image to a BD-R/RE discs).
------------------
Terje J. H
One current and one previous related Blu-ray mail threads as references: https://lists.cinelerra-gg.org/pipermail/cin/2020-November/002709.html https://lists.cinelerra-cv.org/pipermail/cinelerra/2016q4/005609.html
В сообщении от Monday 23 November 2020 05:15:35 Terje J. Hanssen написал(а):
bd_20201122.udfs blocks 26871
mkudffs /dev/shm/bd_20201122.udfs 26871 filename=/dev/shm/bd_20201122.udfs label=LinuxUDF uuid=5fbb20bec1715abc blocksize=512 blocks=26871 udfrev=2.01 start=0, blocks=64, type=ERASE start=64, blocks=13, type=VRS start=77, blocks=19, type=ERASE start=96, blocks=16, type=MVDS start=112, blocks=16, type=ERASE start=128, blocks=16, type=LVID start=144, blocks=112, type=ERASE start=256, blocks=1, type=ANCHOR start=257, blocks=26352, type=PSPACE start=26609, blocks=5, type=ERASE start=26614, blocks=1, type=ANCHOR start=26615, blocks=73, type=ERASE start=26688, blocks=16, type=RVDS start=26704, blocks=166, type=ERASE start=26870, blocks=1, type=ANCHOR without 'blocks' word :} but I do not know if you should set media type also? (-m)
Den 23.11.2020 03:40, skrev Andrew Randrianasulu:
В сообщении от Monday 23 November 2020 05:15:35 Terje J. Hanssen написал(а):
bd_20201122.udfs blocks 26871
mkudffs /dev/shm/bd_20201122.udfs 26871 filename=/dev/shm/bd_20201122.udfs label=LinuxUDF uuid=5fbb20bec1715abc blocksize=512 blocks=26871 udfrev=2.01 start=0, blocks=64, type=ERASE start=64, blocks=13, type=VRS start=77, blocks=19, type=ERASE start=96, blocks=16, type=MVDS start=112, blocks=16, type=ERASE start=128, blocks=16, type=LVID start=144, blocks=112, type=ERASE start=256, blocks=1, type=ANCHOR start=257, blocks=26352, type=PSPACE start=26609, blocks=5, type=ERASE start=26614, blocks=1, type=ANCHOR start=26615, blocks=73, type=ERASE start=26688, blocks=16, type=RVDS start=26704, blocks=166, type=ERASE start=26870, blocks=1, type=ANCHOR
without 'blocks' word :}
but I do not know if you should set media type also? (-m)
Yes, thanks - that works better: mkudffs /data/tmp/bd_20201122.udfs 26871 filename=/data/tmp/bd_20201122.udfs label=LinuxUDF uuid=5fbb27bd6a141f84 blocksize=2048 blocks=26871 udfrev=201 start=0, blocks=16, type=RESERVED start=16, blocks=3, type=VRS start=19, blocks=237, type=USPACE start=256, blocks=1, type=ANCHOR start=257, blocks=16, type=PVDS start=273, blocks=1, type=LVID start=274, blocks=26340, type=PSPACE start=26614, blocks=1, type=ANCHOR start=26615, blocks=239, type=USPACE start=26854, blocks=16, type=RVDS start=26870, blocks=1, type=ANCHOR mkdir /mntX mount -o loop /data/tmp/bd_20201122.udfs /mntX which bdwrite /usr/bin/bdwrite /usr/bin/bdwrite /mntX /data/video/Diverse/20081103140154.m2ts umount /mntX ============= Search for created BD file or folder: find / -name "bd_2020*" /data/tmp/bd_20201122.udfs file /data/tmp/bd_20201122.udfs /data/tmp/bd_20201122.udfs: data ========== Compare sizes of udfs older and the original m2ts file: du -h /data/tmp/bd_20201122.udfs 45M /data/tmp/bd_20201122.udfs du -h /data/video/Diverse/20081103140154.m2ts 45M /data/video/Diverse/20081103140154.m2ts ============ But I had expected a BD_folder with tree structure and empty udfs like this sample from previous rendering; tree -h /data/video/bd_20161216-153642 /data/video/bd_20161216-153642 ├── [183M] bd.m2ts ├── [ 394] bd.sh ├── [191M] bd.udfs ├── [5.3K] bd.xml └── [4.0K] udfs 1 directory, 4 files Possibly some additional steps to write it to harddisk (before BD burning)? Terje J. H
В сообщении от Monday 23 November 2020 07:07:45 Terje J. Hanssen написал(а):
Den 23.11.2020 03:40, skrev Andrew Randrianasulu:
В сообщении от Monday 23 November 2020 05:15:35 Terje J. Hanssen написал(а):
bd_20201122.udfs blocks 26871
mkudffs /dev/shm/bd_20201122.udfs 26871 filename=/dev/shm/bd_20201122.udfs label=LinuxUDF uuid=5fbb20bec1715abc blocksize=512 blocks=26871 udfrev=2.01 start=0, blocks=64, type=ERASE start=64, blocks=13, type=VRS start=77, blocks=19, type=ERASE start=96, blocks=16, type=MVDS start=112, blocks=16, type=ERASE start=128, blocks=16, type=LVID start=144, blocks=112, type=ERASE start=256, blocks=1, type=ANCHOR start=257, blocks=26352, type=PSPACE start=26609, blocks=5, type=ERASE start=26614, blocks=1, type=ANCHOR start=26615, blocks=73, type=ERASE start=26688, blocks=16, type=RVDS start=26704, blocks=166, type=ERASE start=26870, blocks=1, type=ANCHOR
without 'blocks' word :}
but I do not know if you should set media type also? (-m)
Yes, thanks - that works better:
mkudffs /data/tmp/bd_20201122.udfs 26871
filename=/data/tmp/bd_20201122.udfs label=LinuxUDF uuid=5fbb27bd6a141f84 blocksize=2048 blocks=26871 udfrev=201 start=0, blocks=16, type=RESERVED start=16, blocks=3, type=VRS start=19, blocks=237, type=USPACE start=256, blocks=1, type=ANCHOR start=257, blocks=16, type=PVDS start=273, blocks=1, type=LVID start=274, blocks=26340, type=PSPACE start=26614, blocks=1, type=ANCHOR start=26615, blocks=239, type=USPACE start=26854, blocks=16, type=RVDS start=26870, blocks=1, type=ANCHOR
mkdir /mntX
mount -o loop /data/tmp/bd_20201122.udfs /mntX
which bdwrite
/usr/bin/bdwrite
/usr/bin/bdwrite /mntX /data/video/Diverse/20081103140154.m2ts
umount /mntX
=============
Search for created BD file or folder:
find / -name "bd_2020*"
/data/tmp/bd_20201122.udfs
file /data/tmp/bd_20201122.udfs
/data/tmp/bd_20201122.udfs: data
==========
Compare sizes of udfs older and the original m2ts file:
du -h /data/tmp/bd_20201122.udfs
45M /data/tmp/bd_20201122.udfs
du -h /data/video/Diverse/20081103140154.m2ts
45M /data/video/Diverse/20081103140154.m2ts
============
But I had expected a BD_folder with tree structure and empty udfs like this sample from previous rendering;
tree -h /data/video/bd_20161216-153642
/data/video/bd_20161216-153642 ├── [183M] bd.m2ts ├── [ 394] bd.sh ├── [191M] bd.udfs ├── [5.3K] bd.xml └── [4.0K] udfs
1 directory, 4 files
Possibly some additional steps to write it to harddisk (before BD burning)?
I think structure created in file (udfs) so you can burn it already. (but you can attempt to mount -oloop it on some directory and see how it looks inside) What you have in bd_20161216-153642 just result of script doing all those steps you just did manually ...
Terje J. H
Den 23.11.2020 05:46, skrev Andrew Randrianasulu:
В сообщении от Monday 23 November 2020 07:07:45 Terje J. Hanssen написал(а):
Den 23.11.2020 03:40, skrev Andrew Randrianasulu:
В сообщении от Monday 23 November 2020 05:15:35 Terje J. Hanssen написал(а):
bd_20201122.udfs blocks 26871 mkudffs /dev/shm/bd_20201122.udfs 26871 filename=/dev/shm/bd_20201122.udfs label=LinuxUDF uuid=5fbb20bec1715abc blocksize=512 blocks=26871 udfrev=2.01 start=0, blocks=64, type=ERASE start=64, blocks=13, type=VRS start=77, blocks=19, type=ERASE start=96, blocks=16, type=MVDS start=112, blocks=16, type=ERASE start=128, blocks=16, type=LVID start=144, blocks=112, type=ERASE start=256, blocks=1, type=ANCHOR start=257, blocks=26352, type=PSPACE start=26609, blocks=5, type=ERASE start=26614, blocks=1, type=ANCHOR start=26615, blocks=73, type=ERASE start=26688, blocks=16, type=RVDS start=26704, blocks=166, type=ERASE start=26870, blocks=1, type=ANCHOR
without 'blocks' word :}
but I do not know if you should set media type also? (-m) Yes, thanks - that works better:
mkudffs /data/tmp/bd_20201122.udfs 26871
filename=/data/tmp/bd_20201122.udfs label=LinuxUDF uuid=5fbb27bd6a141f84 blocksize=2048 blocks=26871 udfrev=201 start=0, blocks=16, type=RESERVED start=16, blocks=3, type=VRS start=19, blocks=237, type=USPACE start=256, blocks=1, type=ANCHOR start=257, blocks=16, type=PVDS start=273, blocks=1, type=LVID start=274, blocks=26340, type=PSPACE start=26614, blocks=1, type=ANCHOR start=26615, blocks=239, type=USPACE start=26854, blocks=16, type=RVDS start=26870, blocks=1, type=ANCHOR
mkdir /mntX
mount -o loop /data/tmp/bd_20201122.udfs /mntX
which bdwrite
/usr/bin/bdwrite
/usr/bin/bdwrite /mntX /data/video/Diverse/20081103140154.m2ts
umount /mntX
=============
Search for created BD file or folder:
find / -name "bd_2020*"
/data/tmp/bd_20201122.udfs
file /data/tmp/bd_20201122.udfs
/data/tmp/bd_20201122.udfs: data
==========
Compare sizes of udfs older and the original m2ts file:
du -h /data/tmp/bd_20201122.udfs
45M /data/tmp/bd_20201122.udfs
du -h /data/video/Diverse/20081103140154.m2ts
45M /data/video/Diverse/20081103140154.m2ts
============
But I had expected a BD_folder with tree structure and empty udfs like this sample from previous rendering;
tree -h /data/video/bd_20161216-153642
/data/video/bd_20161216-153642 ├── [183M] bd.m2ts ├── [ 394] bd.sh ├── [191M] bd.udfs ├── [5.3K] bd.xml └── [4.0K] udfs
1 directory, 4 files
Possibly some additional steps to write it to harddisk (before BD burning)? I think structure created in file (udfs) so you can burn it already. (but you can attempt to mount -oloop it on some directory and see how it looks inside)
What you have in bd_20161216-153642 just result of script doing all those steps you just did manually ...
Ok, I try to follow the procedure explained in GG's reply to an early related post https://lists.cinelerra-cv.org/pipermail/cinelerra/2016q2/004844.html https://lists.cinelerra-cv.org/pipermail/cinelerra/2016q2/004878.html cd /data/tmp/bd_20201122.udfs mkdir /data/tmp/udfs mount -o loop ./bd_20201122.udfs ./udfs cd /data/tmp/udfs tree -h . ├── [ 520] BDMV │ ├── [ 40] AUXDATA │ ├── [ 332] BACKUP │ │ ├── [ 40] BDJO │ │ ├── [ 92] CLIPINF │ │ │ └── [ 480] 00000.clpi │ │ ├── [ 40] JAR │ │ ├── [ 110] MovieObject.bdmv │ │ ├── [ 92] PLAYLIST │ │ │ └── [ 184] 00000.mpls │ │ └── [ 124] index.bdmv │ ├── [ 40] BDJO │ ├── [ 92] CLIPINF │ │ └── [ 480] 00000.clpi │ ├── [ 40] JAR │ ├── [ 40] META │ ├── [ 110] MovieObject.bdmv │ ├── [ 92] PLAYLIST │ │ └── [ 184] 00000.mpls │ ├── [ 92] STREAM │ │ └── [ 44M] 00000.m2ts │ └── [ 124] index.bdmv └── [ 272] CERTIFICATE ├── [ 224] BACKUP │ ├── [ 40] BDJO │ ├── [ 40] CLIPINF │ ├── [ 40] JAR │ └── [ 40] PLAYLIST ├── [ 40] BDJO ├── [ 40] CLIPINF ├── [ 40] JAR └── [ 40] PLAYLIST 23 directories, 9 files ============= I don't understand why this BDMV tree structure is much larger than the simple 2016/2017 structures I got written to hdd as shown above. I thought the previous structures were some tests to hdd without the need to burn BD discs, but don't remember how they were created. As mentioned I also got successful BD video written to BD-R/RE disks at last. ============= ffplay -vf setdar=dar=16/9 -playlist 0 bluray:/data/tmp/udfs .... [bluray @ 0x7fcc980016a0] 0 usable playlists: bluray:/data/tmp/udfs: Input/output error nan : 0.000 fd= 0 aq= 0KB vq= 0KB sq= 0B f=0/0 That is ffplay did not replay the video here using that command to udf (ffplay is build with libbluray) Both ffplay and VLC does playback pointing directly to the stream file ffplay /data/tmp/udfs/BDMV/STREAM/00000.m2ts vlc /data/tmp/udfs/BDMV/STREAM/00000.m2ts
participants (2)
-
Andrew Randrianasulu -
Terje J. Hanssen