It is not completely broken. It was just working in near-lossless mode ( https://x265.readthedocs.io/en/stable/lossless.html ) which is 99,9% lossless.
It is fixed in the next version.
P.S.: One post would've been enough.
Beiträge von Vouk
-
-
Yes, I got the same result with mediainfo, and it doesn't look right. I even confirmed this with testing the file using this method: https://superuser.com/questions/1487…able-frame-rate
Codeffmpeg.exe -i filename.mkv -vf vfrdet -an -f null -MP4
Codeframe= 125 fps=0.0 q=-0.0 Lsize=N/A time=00:00:05.00 bitrate=N/A speed=68.8x video:65kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown [Parsed_vfrdet_0 @ 00000167765a3ec0] VFR:0.000000 (0/124)MKV
Codeframe= 125 fps=0.0 q=-0.0 Lsize=N/A time=00:00:05.04 bitrate=N/A speed= 73x video:65kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown [Parsed_vfrdet_0 @ 0000029a8cbea240] VFR:0.032258 (4/120) min: 19 max: 61 avg: 40It also only seems to happen when an audio track is included.
I will investigate this.
Edit:
[FRAME]
media_type=video
stream_index=0
key_frame=1
pkt_pts=0
pkt_pts_time=0.000000
pkt_dts=0
pkt_dts_time=0.000000
best_effort_timestamp=0
best_effort_timestamp_time=0.000000
pkt_duration=40
pkt_duration_time=0.040000
pkt_pos=722
pkt_size=2883
[/FRAME]
[FRAME]
media_type=video
stream_index=0
key_frame=0
pkt_pts=61
pkt_pts_time=0.061000
pkt_dts=61
pkt_dts_time=0.061000
best_effort_timestamp=61
best_effort_timestamp_time=0.061000
pkt_duration=40
pkt_duration_time=0.040000
pkt_pos=5652
pkt_size=23
[/FRAME]
[FRAME]
media_type=video
stream_index=0
key_frame=0
pkt_pts=101
pkt_pts_time=0.101000
pkt_dts=101
pkt_dts_time=0.101000
best_effort_timestamp=101
best_effort_timestamp_time=0.101000
pkt_duration=40
pkt_duration_time=0.040000
pkt_pos=6798
pkt_size=23
[/FRAME]
Frame 0:
- Time: 0ms
- Duration: 40ms
Frame 1:
- Time: 61ms (Should be actually 40ms here!)
- Duration: 40ms
Frame 2:
- Time: 101ms (Should be actually 80ms here!)
- Duration: 40ms
...
So when analyzing the stream it finds the first frame takes 61ms, the second 40ms and there we have a variable frame rate.
It looks to me this is happening from rescaling the timing from 1/25 to 1/1000 and syncing it with the audio track sample rate. If I change the sample rate the offset (61ms) changes too. Seems this issue is deep within FFmpeg.
-
I tested this and this happens as soon as you say "preset=bd". I don't know if that is a bug or a feature, but if it's a bug it's most likely in FFmpeg or in NVENC.
What happens if you use a different preset? Does that work on your player?
-
It's like asking: Is there any demand for this?
-
Hybrid encoding is not possible with the i.e. Adobe product line.
Is there anybody else still needing an MPEG2 encoder with vob output?
-
OptimFROG is not included in FFmpeg and might also not get into it (https://codecs.multimedia.cx/2016/03/optimfrog/).
YULS is also not included in FFmpeg.
As voukoder in it's current state only supports encoders that are included with FFmpeg it is not possible to add this.
-
Not seeing a use case for this old codec. Probably not maintained anymore. Can not find it in FFmpeg either.
-
SVT-AV1 does not have provide (to my knowledge) a dedicated lossless option (other than crf/qp=0).
-
Who are you to decide what this product is and should be? The logo stays as it is.
P.S.: It is not for AME only.
-
OK, what about releasing these encoders first: LAME, OPUS, AC-3, DTS?
All of them are implemented already (for years).
-
To my knowledge only effect plugins need changes. Seems to be working already.
-
No, I don't think so.
-
What is it exactly?
-
Again I've learned more stuff about HDR in FFmpeg and I will add ways to add CLL and Master Display data using the "Side Data" tab (for all encoders).
Maybe that helps improving the HDR situation a bit.
-
Voukoder 10 - RC1
RELEASE CANDIDATE - NOT FOR PRODUCTION USE!
Make sure you are using the latest connector for your application(s). For using NVENC (SDK 9.1) encoders driver version 436.15 or later is required.
Fixes / Changes
- Added options to set the language meta data for audio and video tracks
- Fixed intel QSV issues
Credits
Thanks to my all supporters by either PayPal, Patreon or BTC. Also thanks alot to the translators.
Top Patrons
7even_7, Gronkh,Schauerland, Andreas Martin Aanerud, Michael Wooldridge and Chris Woods
Download
-
Did you follow the instructions and install both components?
-
Normally there I'm releasing a new version around every 2 months. Currently there are not many bugfixes / new features in the queue. Just:
- Added options to set the language meta data for audio and video tracks
- Fixed Intel QSV issues
-
According to NVIDIA ...
https://developer.nvidia.com/video-encode-a…port-matrix-new
... 10bit should only work with HEVC / h265, it seems.
-
Elheat First, yes, your CPU is a bit slow (Passmark score of only 5734). Second, Prores is an intermediate codec used for exchange a video within the editing workflow. Thus it is less compressed than i.e. h264 files. You will notice scrubbing in ProRes files is faster than in h264 files. This results in a larger file size. Also ProRes encoding can't be GPU accelerated (with the current GPUs). So I think it is pretty normal.
-
The setting is the correct one.
Unfortunately I cound not get the alpha channel data from DVR. There are open support quesions regarding this matter in the BM forum but they never replied to me so far.
Edit: https://forum.blackmagicdesign.com/viewtopic.php?f=12&t=138829
