![]() My standalone GUI does not yet support dev mode but the one in staxrip does.ĭemuxing with l-smash and ffms2 might not be the best way, especially when dealing with TS, which type of file do you have? There should be better demuxers for all type of files. ![]() It's sad how many people still use CMD and how few people use PowerShell and Windows Terminal.īoth Mulders GUI and the original GUI show the API parameter names only in XML view and not in text view, my GUI can show it in text view, it's searchable which is the most important feature and it supports High DPI. I've also a standalone GUI you can try, I don't remember if it supports dev mode. You need to enable developer mode in the context menu otherwise it does not show you the parameter names used by the MediaInfo API. The docs have a config example to show you exactly the configuration you need: My GUI shows it, I think it's the best GUI because it's searchable which dramatically boosts productivity, to use it you will need to learn Open with++ and you need staxrip. I don't know if Lord Mulders GUI shows it, if not you can ask him to support it. The official MediaInfo CLI app is probably able to show it but I think using a GUI is much easier for this kind of task. To use the PowerShell function you will need a proper MediaInfo GUI which will show you the names of the parameters you need to query, I don't think the official GUI shows this because I tried it and couldn't find out how to do it. You know PowerShell? It's hard to learn but I'm absolutely willing to help.Īre you sure ffms2 or l-smash need total index and not kind index? Sounds like bad design and besides that I don't think MediaInfo gives you this info, I just checked and couldn't find it. I wish you luck with this project, at least with the CLI version MI, it is not a totally pleasant task. Then we need to know TOTAL STREAM ORDER index, and tell LSMash/ffms2 to extract that track (or maybe it is eg video index with LSMash and total index with ffms2, Or the other way around, cant remember, but at least one of them is awkward). When using LSMash or ffms2, and wanting to know specific info about a stream that we are perhaps gonna extract (maybe we want stream with greatest video resolution and so have to find out which one we want), One thing I want is "TOTAL STREAM ORDER" index (dont know what else to call it, ie stream order where all streams of all types are counted). [You can extract everything, and then extract from that, there are functions to do it in MIFO_LIB). Even the same source, just the duration encoded is different.MediaInfo CLI does not allow to interrogate specific info from a stream that is one of many streams of same type, eg 2nd audio stream when there are 4 audio streams.Īudio stream index 0, is used for single stream count stream, and 1 for first of multi-stream audio.ĭont allow for multi-stream info extraction, because the CLI dont work proper. ![]() Also the short one has all the light level and liminance info but the long one doesn't. So you will see on the short one there is HDR_Format info where the other there isn't. Maximum Frame-Average Light Level : 1166 cd/m2 MasteringDisplay_Luminance_Source : Stream Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2 MasteringDisplay_ColorPrimaries_Source : Stream Mastering display color primaries : BT.2020 HDR format : SMPTE ST 2086, HDR10 compatible Go back to Media Encoder and use the same settings just reset the project and encode a brief duration. Matrix coefficients : BT.2020 non-constant Inform : English, 20.0 Mb/s, 3840*1600 (2.40:1), at 23.976 (24000/1001) FPS, HEVC (Main : 1įormat/Info : High Efficiency Video Codingįormat profile : Main media type : video/H265Ĭodec ID/Info : High Efficiency Video CodingĬolour_description_present_Source : Stream One is the full hour and a half movie that returns in MediaInfo: OK so that's the settings for both encodes. So I'm finding a weird thing iwth the latest version of Premiere Pro 2020 on Windows.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |