New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error opening MPEG-TS files: Error getting frame property "_Matrix" #6
Comments
You can try the latest version. |
It works alright now. Many thanks. 😊 |
Sorry, but I was hasty in closing this issue thread. Now the preview opens OK but the pixel type is incorrectly set to I've seen the same issue with another HDR video (HLG |
I guess you're testing with hardware decoding again because with software decoding I cannot reproduce the issue. |
Thanks. With the new binary, I've run into this weird phenomenon. The first PQ HDR10 sample opens well with or without Software decoding: Hardware decoding: However, with the HLG HDR sample, it's weird. Software decoding: works well But when I delete the cache file and put hardware decoding option, the pixel type becomes weird. Hardware decoding: I have no clue. 😓 |
What's NVIDIA driver version? You need 456.71 or newer. |
My Nvidia driver is NVIDIA Studio driver 471.41 (the most recent one released on July 19, this year).
I tested with HolyWu's 20210423 build, and have found that it suffers the same issue. I was not testing it thoroughly back then and didn't find it out. 😓
I'm observing this phenomenon here. Although the reported pixel type of the AviSynth+ script is
(The duration becomes different than the source file, and I guess it's in turn an issue with Now I suspect it might be a driver issue although I'm not sure. Or maybe the sample file is corrupt(?). Since software decoding seems to be working OK, I'll go with software decoding first when it comes to HDR TS files. Thanks for your help. |
For comparison, I used For reference, The script code is as follows.
And unlike So it turns out that it's not a video driver issue. |
LWLibavVideoSource (software decoding) is giving the correct pixel type but the clip ( Anyway, I would recommend to not rely ffmpeg decoding for .ts and similar. |
Got it. Thanks for the detailed info. |
… field in mpegts Updates #6. Signed-off-by: akarin <i@akarin.info>
Don't know if it's same issue with prefer_hw=1 in Vapoursynth, you can check and notice to AkarinVS. He will fix it in GPU support and Asd-g will backport to avisynth ver |
…files Fixes HomeOfAviSynthPlusEvolution#6. Signed-off-by: akarin <i@akarin.info>
LWLibavVideoSource
on AviSynth+ 3.7.0)Here's the script code:
And the screenshot of the error (AvsPmod v2.6.8.7)
This is the same video opened with HolyWu's 20210423 build:
And the same video opened with
ffms2
(87bae19 StvG, here)The text was updated successfully, but these errors were encountered: