Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
5th August 2017, 16:20 | #41 | Link |
Registered User
Join Date: Feb 2014
Posts: 61
|
Hi videofan3D,
so I did some tests with h264offset3D and it works pretty fine. The only problem is that after inserting the original offsets back into the mvc stream after reencoding, and remuxing, I get blocking artefacts when playing on my Sony standalone player. This doesn't happen without inserting the offsets. h264offset3d seems to brake something in the stream. Do you have any idea what it could be?? Thanks for creating this nice tool at all |
5th August 2017, 16:40 | #42 | Link | |
Registered User
Join Date: Dec 2002
Posts: 5,565
|
Quote:
AVC/HEVC specs cover endless use-cases. Much of it is irrelevant in the real world. It's way too complicated. |
|
5th August 2017, 19:03 | #43 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
|
|
11th August 2017, 12:30 | #45 | Link |
Registered User
Join Date: Feb 2014
Posts: 61
|
Hi,
over the last few days I did quit a few tests with h264offset3D. And I can say that it works absolutely stable and exactly as it is meant to work. Thanks @videofan3D! As for muxing frim-encoded streams with integrated offsets, I had some difficulties. TSMuxer muxes them perfectly fine, however the output can't be played on every standalone player because TSMuxer uses the out-of-mux method for 3D folders. This is of Course not a problem of Frim or h264offset3d. A solution is to only mux with TSMuxer using it's BluRay ISO output option. But you can have only one title per Disc using this method. For people like me, who want to have some menus and generate them with Scenarist the situation is a bit more complicated. Scenarist muxes FRIM encodes withOUT offsets perfectly. Hoewever you need to uncheck "Spec check mode" in MUI generator. You'll get a 3D bluray out of Scenarist that plays in every single standalone player because Scenarist is a professional tool and designed for perfect compatibility. But as FRIM encodes have broken offset structure, subtitles can't have any depth, not even if you want to set Offsets manually, because scenarist doesn't offer the option to manage Offsets at all with FRIM encodes. This is where videofan3d's new h264offset3d gets important. With this tool you can extract offsets from original files or generate a text file with offsets manually and intergrate them into the mvc stream after encoding with FRIM. This works perfectly. Now even Scenarist recognizes the FRIM encoded file as valid (no need to disable "spec check mode"). In Scenarist you can now manage offsets in every possible way. However, the resulting disc shows some block artefacts every 5-10 seconds during playback on standalone players. This didn't happen without integrating offsets. Luckily there is an easy fix for this using jdobbs' BD-Rebuilder. Just process the disc you got out of Scenarist with BD-Rebuilder. If you set the output size accordingly, BD-Rebuilder won't reencode any video files. It only remuxes the disc using the in-mux file structure, which is also compatible with every standalone player. As Offsets are only assigned within the mpls files (thanks @videofan3D), the offsets you assigned in Scenarist will be there even after remuxing. Now the discs work perfectly fine with menus and 3d subtitle offsets at the same time. And we are able to make perfect backups of original discs with FRIM and h264offset3D as well. I hope my post will help some people in creating their backups or own movies with Scenarist, Frim and h264offset3D. Big thanks to @videofan3D for creating these wonderful tools. |
24th August 2017, 21:32 | #46 | Link |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
BDTools 2.30
BDTools 2.30 released:
MPLS2JSON - added support for id.bdmv files - sound.bdmv - WAVE files are extracted to the same directory as .json file h264Modify - added -frame_packing for insertion or deletion of frame packing SEI messages: CHECKER or 0 - for checkerboard COLINT or 1 - column interleave ROWINT or 2 - row interleave SBS or 3 - side by side TAB or 4 - top above bottom MONO or 6 - mono - 2D frame TILE or 7 - tile format (frame alternation (mode 5) is not supported yet) h264Offset3D - minor bugfixing - no new features AVCHDInfo - new tool. Displays recording date/time of each frame of AVCHD.MTS file extracted from vendor-specific information (if available) - in textual or tab-separated format. Vendor-specific information contains sometimes additional data like camcorder model, recording aperture, gain, GPS info, etc. However this format is not standardized nor unified and each vendor like SONY, CANON, PANASONIC etc. uses its own coding. Further vendor-specific data might be possibly extracted in future versions of AVCHDInfo. |
12th September 2017, 21:36 | #47 | Link |
Registered User
Join Date: Sep 2017
Posts: 2
|
MPLS2JSON 2.30? and clpi?
I downloaded ver 2.30 of your awesome tools and found that MPLS2JSON seems to still be the previous version (2.20) in the 2.30 download. The release notes say that id.bdmv support was added in 2.30...
Also the help info says that it can show info for clpi files, but when I try it it states failed signature match: found "" This is one of the most useful tools I've found so far! Keep up the great work! As a side request, could you add the Windows standard help argument "/?" as an alias to the Linux standard "--help"? Thanks! |
14th September 2017, 22:56 | #48 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
There might be slight mismatch in numbering, but "MPLS to JSON - version 2.20 (build: Aug 14 2017)" support id.bdmv - you can test it. Regarding clip and signature match: found "" - please give me the particular .clip file, I will check it. Regarding /? ... try -help (I don't like Microsoft's /?, it confuses regular "questions mark" meaning. Standard UNIX uses only single "minus") |
|
16th September 2017, 12:14 | #49 | Link |
Registered User
Join Date: Sep 2017
Posts: 2
|
MPLS2JSON clpi
Oh, interesting... I'm not sure which file I tried it on. CLPI is indeed working on other files... curious (on my end).
Please ignore that problem I guess. If I can remember the file again I'll send it. |
21st September 2017, 12:06 | #50 | Link | |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
A spanish user ask me about a problem playing (with a BDplayer) a custom BD with a h264 stream like this:
Quote:
Is that stream allowed in BluRay specs? Do you know a tool to modify the h264 deleting the EIA-608 subs? Sample
__________________
BeHappy, AviSynth audio transcoder. Last edited by tebasuna51; 21st September 2017 at 12:12. |
|
21st September 2017, 22:34 | #51 | Link | |
Registered User
Join Date: May 2006
Posts: 3,997
|
Quote:
You can remove the EIA-608 caption by re-encoding the stream. |
|
31st January 2018, 13:47 | #53 | Link | |
Registered User
Join Date: Dec 2002
Posts: 5,565
|
Quote:
Code:
mkvextract tracks "F:\Movies\ULTRON.mkv" "0:F:\Movies\ULTRON.264" h264Modify.exe F:\Movies\ULTRON.264 -sar 1:2 F:\Movies\ULTRON-UPDATED.264 mkvmerge -o "F:\Movies\ULTRON-UPDATED.mkv" --stereo-mode 0:1 "F:\Movies\ULTRON-UPDATED.264" --no-video "F:\Movies\ULTRON.mkv" Last edited by sneaker_ger; 31st January 2018 at 14:08. |
|
13th October 2018, 23:27 | #54 | Link |
Registered User
Join Date: Aug 2018
Posts: 68
|
First of all, thank you very much for providing us with these great tools. My issue is pure novice. When I want to create the output from mpls to json it says can't create the file. This is the syntax I write. Any help is more than appreciated.
C:\>MPLS2JSON 00800.mpls 00800.json Save failed: 00800.json |
2nd June 2019, 13:59 | #58 | Link |
Registered User
Join Date: May 2019
Posts: 2
|
Hello videofan3d,
I use these BDTools 2.30 since several month, really great helpfull tools :-) Now, I have some issues with subtitle depth. Inside a playlist file there are different planes for different subtitles. After reconvert from .json to .mpls ALL .pgs subtitle streams are set to plane#0. short example: (original .mpls file with different planes after conversion to .json) Code:
"PG_stream": [ { "PG_textST_offset_sequence_id_ref": 11, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 12, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 1, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 2, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 3, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 4, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 5, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 6, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 7, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 8, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 13, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 15, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 9, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 14, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 10, "reserved01": 0, "dialog_region_offset_valid_flag": 0, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 } ], "IG_stream": [] After another conversion of this new .mpls once again to .json I see that the content has chainged: Code:
"PG_stream": [ { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 }, { "PG_textST_offset_sequence_id_ref": 0, "reserved01": 0, "dialog_region_offset_valid_flag": 1, "is_SS_PG": 0, "is_top_AS_PG_textST": 0, "is_bottom_AS_PG_textST": 0 } ], "IG_stream": [] For editing .json file I use Free JSON Editor: https://www.mediafreeware.com/free-json-editor.html If you need more infos, just let me know :-) |
3rd June 2019, 20:30 | #59 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
Someone shows he/she still uses these little tools Version 2.30 uploaded to this web has a bug in 3D subtitle depth extraction. You can check this using command mpls2json -selftest 00000.mpls when in case of BD3D it will not re-create identical .mpls. Fixed version 2.31 uploaded. Last edited by videofan3d; 7th June 2019 at 05:33. |
|
7th June 2019, 17:31 | #60 | Link |
Registered User
Join Date: May 2019
Posts: 2
|
Hello vidofan3d,
thank you so much for fast fixing. I just tested version 2.31 on a seamless branching mpls file: AFTER USING NEW VERSION 2.31 ALL PLANES FOR 3D SUBTITLES ARE SAME LIKE ON ORIGINAL MPLS Thank you once again for fixing. Especially for me, your BDTools is the best software for editing blu-rays. Before, I used bdedit...but yours are way better (for me) |
Thread Tools | Search this Thread |
Display Modes | |
|
|