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. |
17th September 2024, 23:04 | #9521 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,079
|
x265cli.cpp, lines 808 ff.:
Code:
#if !ENABLE_MULTIVIEW if (optind < argc && !inputfn[0]) inputfn[0] = argv[optind++]; #endif But it doesn't seem to work in my recently compiled v4.0+4. |
18th September 2024, 05:34 | #9522 | Link | |
Registered User
Join Date: Aug 2024
Posts: 43
|
Quote:
Last edited by Z2697; 18th September 2024 at 05:38. |
|
18th September 2024, 09:22 | #9523 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,079
|
Wondering if the cause might be wrong parameters in a cmake cache, I rebuilt my binaries. But they turned out to be the same, that was not the reason.
Now I reported it to x265_git issue 954. If any competent programmer here could have a look, that would be very appreciated. |
18th September 2024, 13:39 | #9525 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,079
|
While you are at it:
Help messages are not formatted well in new features, sometimes missing manual line breaks which happen randomly in long lines, I remember I spotted typos and strange grammar... |
18th September 2024, 13:59 | #9527 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,079
|
Regarding the specifications (in theory): Encoder library and options are metadata, pure text. They can be omitted by an encoder or removed later. Header fields describing the content (e.g. colorimetry flags, aspect ratio) can be edited with special tools (which may take care of checksums, if any exist). They just need to exist and be known ... I do remember that a patcher for raw H.264 (AVC) video streams exists. And I read that ffmpeg can be used to alter some metadata in video streams.
In other words: It is absolutely possible that software can exist which is able to patch H.265 metadata. It may even exist already. I just can't tell you a specific tool, besides ffmpeg. Last edited by LigH; 18th September 2024 at 14:10. |
18th September 2024, 21:48 | #9533 | Link | |
Registered User
Join Date: Aug 2024
Posts: 43
|
HEX editor is definitely gonna work but same for anyone that's tech-literate enough if they want to remove it.
If you don't want to do that hex editing you can mess with the version.cmake or param.cpp to change how the version string is generated or how the SEI is "printed". Or.......... you can use the x265 parameter --nalu-file to insert a custom SEI message but I never used it, I can't guarantee that it'll work, plus good luck for any of your viewers can find this easter egg (if it's only important to yourself then this is no problem) Alright, I tested it and it works, it looks like you can insert SEI message at any frame from the help msg but I can only get it working at the frame 0. An example of nalu-file: Quote:
Last edited by Z2697; 19th September 2024 at 00:40. Reason: add example |
|
19th September 2024, 16:47 | #9536 | Link | |
Registered User
Join Date: Dec 2013
Location: Berlin, Germany
Posts: 396
|
Quote:
__________________
My github... |
|
19th September 2024, 20:12 | #9537 | Link | |
Registered User
Join Date: Aug 2024
Posts: 43
|
Quote:
And LigH, yes it's base64. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|