On Saturday, November 13, 2021, Terje J. Hanssen <[email protected]> wrote:
Den 13.11.2021 17:45, skrev Andrew Randrianasulu:
------------------------
(Another one for "home-made HD videos" on Blu-ray discs (BDAV): Will it be possible to record (copy) source 1080iHDV.m2t files (video and audio) to the BD-R(E) discs?)
I was thinking about integrating tsMuxer but this does not solve problem about unavailability of pre-encoded packets in cin's vframe for mpeg2.. Probably BC_COMPRESSED type should be split for mjpeg/dv/mpeg2/h264 types but this is larger rework than I can attempt from tablet ...
If tsMuxer (or another dedicated utility) could author a BDAV Blu-Ray
for burning on BD-RE disk (and DVD-R), this could make it possible to preserve and test playabilty compliance of DV SD and MPEG-2 HD(V) streams content on the same disc, as described in these papers:
Blu-ray Disc, Rewritable Format, Audio Visual Application Format Specifications for BD-RE Version 2.1, March 2008: Figure 3.1.4.2.3: Stream file and Clip Information file for DV in BDAV directory http://www.blu-raydisc.com/Assets/Downloadablefile/BD-RE_Par t3_V2.1_WhitePaper_080406-15271.pdf
Blu-ray Disc Association. UDF2.5. 25/50GB. BDAV. As of December 2016. ROM4.0. Ultra HD Blu-ray™. ROM. Part3. V3.1. ROM. Part2. V2.0. ROM. Part1. V2.0. BDMV. http://www.blu-raydisc.info/docs/Spec_Info/AllBooksDecember2016.pdf
well, if you have player (or friend(s) with player(s)) you can try for yourself
https://github.com/justdan96/tsMuxer/commits/master
i think they have pre-compiled version. Be aware in tsmuxer context DV usually mean Dolby Vision, not dv as dv video codec.
I downloaded and unpacked an appimage, but could not see BDAV mentioned. Have you seen any good user examples for tsMuxer?
Terje J. H
if (qt5) gui works for you you can try following https://elatom.com/software/tsmuxergui-software-for-ts-muxing-with-mpeg-hevc... pure cmd line use a bit more involved from githab page --- Syntax The following lines form a list of tracks and their parameters. The format is as follows: <code name>, <file name>, <parameters>. Parameters are separated with commas, with each parameter consisting of a name and a value, separated with an equals sign. Example of META file: MUXOPT --blu-ray V_MPEG4/ISO/AVC, D:/media/test/stream.h264, fps=25 A_AC3, D:/media/test/stream.ac3, timeshift=-10000ms In this example one AC3 audio stream and one H264 video stream are multiplexed into BD disc. The input file name can reference an elementary stream or a track located inside a container. Supported input containers: TS/M2TS/MTS EVO/VOB/MPG/MPEG MKV MOV/MP4 MPLS (Blu-ray media play list file) Names of codecs in the meta file: Meta File Code Description V_MPEGI/ISO/VVC H.266/VVC V_MPEGH/ISO/HEVC H.265/HEVC V_MPEG4/ISO/AVC H.264/AVC V_MPEG4/ISO/MVC H.264/MVC V_MS/VFW/WVC1 VC1 V_MPEG-2 MPEG2 A_AC3 AC3/AC3+/TRUE-HD A_AAC AAC A_DTS DTS/DTS-Express/DTS-HD A_MP3 MPEG audio layer 1/2/3 A_LPCM raw pcm data or PCM WAV file S_HDMV/PGS Presentation graphic stream (BD subtitle format) S_TEXT/UTF8 SRT subtitle format. Encoding MUST be UTF-8/UTF-16/UTF-32 Each track may have additional parameters. Track parameters do not have dashes. If a parameter's value consists of several words, it must be enclosed in quotes. --- from old firum thread https://forum.doom9.org/archive/index.php/t-142559.html