LAV Filters - DirectShow Media Splitter and Decoders

[Damien147]

Nevermind.Older adrenalin driver stopped the crashes.

[magic144]

can't find an an answer to this after several searches:

in the LAV Video Decoder properties page, if choosing a Hardware Device for DXVA2/D3D11 copy-back, my (in this case NVIDIA GeForce RTX 2060) card is listed twice

is there any reason for the duplicate? is there any difference between the two entries?

thanks

[clsid]

The way that enumeration works in Windows API is through displays. So if you have two displays, the GPU will be listed twice. There is no difference. But you can't just filter out duplicates, since it is technically possible to have two distinct identical GPUs in a system.

And on laptops with switchable graphics, you may only see the GPU that is currently active. Tip: you can configure a preferred GPU per app in Windows 10/11 display settings in this case.

[magic144]

hmm, ok thanks

I only have 1 display connected though? unless it's some vestige of a previous display still held by the system somehow/somewhere? is there anything I can check to uncover the source of the duplicate?

EDIT: perhaps it's related to Citrix?
my System Info lists a "Citrix Indirect Display Adapter"

[Sunspark]

Wow, I just ran into an issue.. for the first time, I have encountered a video that reports a fps of 47.952 (2x 23.976). What is truly awful about this is that you can hit play from any point in it, the subs and video are in sync with the audio, and then as it plays, the video drifts out of sync more and more (though the subs stay synced with the audio). The only way to fix it is to hit stop and then play again and it is back in sync. I do have Auto A/V sync turned on in LAV and tried disabling it just now, I think it helped but not completely sure.

Is this a bug or a different issue?

[Klaus1189]

Can you upload the file somewhere? Cutting out a small part with MKVToolNix would perhaps fix the file and produce a file with other specs.

[Sunspark]

Originally Posted by Klaus1189

Can you upload the file somewhere? Cutting out a small part with MKVToolNix would perhaps fix the file and produce a file with other specs.

Ok, I snipped out the first 10 seconds, though this won't be long enough to notice the audio drifting out of sync with the video. MKVToolNix didn't change the specs.

10 second snip of 47.952 file

This is odd.. MadVR says 47.952.. looking at it in the EVR-CP HUD says Frame rate: 23.shifting numbers ( 20.854 ms = 47.952, P).. VLC also says 23.976 in the statistics screen. MPV statistics say 23.976 FPS.. so, am I looking at a MadVR bug here? Except it should be 41.71 ms for 23.976 and the EVR-CP HUD said 20.854 ms.. so that's a clue of some sort.. I will add to this, I grabbed the file again from a different encoder and the EVR-CP HUD reports 23.### (41.708 ms = 23.976, P).

41.708/2 = 20.854.. so ???

[SeeMoreDigital]

Originally Posted by Sunspark

Ok, I snipped out the first 10 seconds, though this won't be long enough to notice the audio drifting out of sync with the video. MKVToolNix didn't change the specs.

Hmmm...

Sounds like some VFR encoding related nonsense. When you created the encode did you remember to select 'constant frame rate' encoding?

[Sunspark]

I didn't create it, the NHTFS group did.

[Balling]

Originally Posted by Sunspark

Ok, I snipped out the first 10 seconds, though this won't be long enough to notice the audio drifting out of sync with the video. MKVToolNix didn't change the specs.

10 second snip of 47.952 file

This is odd.. MadVR says 47.952.. looking at it in the EVR-CP HUD says Frame rate: 23.shifting numbers ( 20.854 ms = 47.952, P).. VLC also says 23.976 in the statistics screen. MPV statistics say 23.976 FPS.. so, am I looking at a MadVR bug here? Except it should be 41.71 ms for 23.976 and the EVR-CP HUD said 20.854 ms.. so that's a clue of some sort.. I will add to this, I grabbed the file again from a different encoder and the EVR-CP HUD reports 23.### (41.708 ms = 23.976, P).

41.708/2 = 20.854.. so ???

That file says in Mediainfo that its Original framerate is 47.952, i.e. 48/1.001 (47.95204795204795).


The issue is because it has a wrong fps in first frame. Alas

ffmpeg.exe -an -i "47.952 issue sample.mkv" -c copy -bsf trace_headers -f null -


[trace_headers @ 000001de1f985740] 163 num_units_in_tick 00000000100111110001101011001011 = 10427083
[trace_headers @ 000001de1f985740] 195 time_scale 00111011100110101100101000000000 = 100000000

[SeeMoreDigital]

Originally Posted by Sunspark

I didn't create it, the NHTFS group did.

Who are these people?

[Sunspark]

Originally Posted by SeeMoreDigital

Who are these people?

Some scenesters.

Update, sorry guys, it's not the decoder.. should have done this first, but just now I tried "None" as the decoding method, and it didn't change anything.. so that means MadVR as a video renderer is permanently buggy with whatever this type of encoding has done.

Other renderers like MPCVR while it can see the ms times aren't quite right, it does report a framerate of 23.976 as do other renderers. Oh well, hopefully whatever this problem is doesn't spread because it'll always have audio drift under default settings. This is not a 47.952 native framerate, unless Apple is doubling it and then releasing it like that, which I doubt.

[Balling]

Originally Posted by Sunspark

roblem is doesn't spread because it'll always have audio drift under default settings. This is not a 47.952 native framerate, unless Apple is doubling it and then releasing it like that, which I doubt.

48 fps is a thing. Even youtube supports that.

[Sunspark]

Nope. It's an encoder screw-up.

Actual HFR content is really rare, this is a list of movies: https://en.wikipedia.org/wiki/List_o...gh_frame_rates

No TV shows that I am aware of.

[SeeMoreDigital]

Originally Posted by Balling

48 fps is a thing. Even youtube supports that.

Native 48.000fps was a thing in cinemas around ten years ago (ie: The Hobbit movie). However, 48.000fps wasn't able to make any headway in home media due to 48.000Hz not being supported within the HDMI specification.

Maybe that's changed now. I would certainly like to see native 48.000fps content displayed at 48.000Hz, instead of being re-flagged and displayed at 60.000Hz.

As for capturing content at native 60.000fps or higher (ie: Gemini Man) and displaying it at 60.000Hz (59.940Hz), I haven't been that impressed. It just looks weird to my eyes/brain...

[Balling]

Originally Posted by SeeMoreDigital

Native 48.000fps was a thing in cinemas around ten years ago (ie: The Hobbit movie). However, 48.000fps wasn't able to make any headway in home media due to 48.000Hz not being supported within the HDMI specification.

Maybe that's changed now. I would certainly like to see native 48.000fps content displayed at 48.000Hz, instead of being re-flagged and displayed at 60.000Hz.

As for capturing content at native 60.000fps or higher (ie: Gemini Man) and displaying it at 60.000Hz (59.940Hz), I haven't been that impressed. It just looks weird to my eyes/brain...

Well, my Galaxy s22 Ultra with VRR supports 10 fps, 24, 30, 48, 60, 96, 120

EDID can in detailed timing describe any rate you want. VRR of HDMI 2.1 and others support all rates, whatsover.

[FranceBB]

Originally Posted by SeeMoreDigital

Native 48.000fps was a thing in cinemas around ten years ago (ie: The Hobbit movie).

Avatar too, when I saw the second one at the theatre it made me remember that 4D 48fps was actually a thing...

Originally Posted by SeeMoreDigital

As for capturing content at native 60.000fps or higher (ie: Gemini Man) and displaying it at 60.000Hz (59.940Hz), I haven't been that impressed. It just looks weird to my eyes/brain...

It feels weird at first 'cause we're not really expecting that level of smoothness, but after a few minutes I didn't mind. And let's face it, 90% of the population leaves true-motion or whatever the vendor of their TV calls linear interpolation / optical flow on, so they're used to seeing "high frame rate" contents all the time, but at least with actual 60p contents they won't see interpolation artifacts eheheheheh

[SeeMoreDigital]

Perhaps in the future some media streaming services might offer us some native 48.000fps/48.000Hz content for displaying on supporting TV's.

Sadly we're never going to have native 48.000fps/48.000Hz content on 4K UHD discs, not that our 4K UHD disc spinners are capable of supporting it anyway!

[flossy_cake]

Originally Posted by Sunspark

This is odd.. MadVR says 47.952.. looking at it in the EVR-CP HUD says Frame rate: 23.shifting numbers ( 20.854 ms = 47.952, P).. VLC also says 23.976 in the statistics screen. MPV statistics say 23.976 FPS.. so, am I looking at a MadVR bug here?

MadVR's OSD framerate value is completely untrustworthy for anything with a variable framerate. The only way I've been able to determine if a file is truly variable frame rate or not is to switch to MPC-HC's own video renderer, turn on its OSD and watch its reported fps value fluctuate in real time. If it fluctuates then I know it's a VFR file.

On a separate note I was just looking into HRTF for headphone usage (I saw you guys were discussing this on the previous page) and would really like that feature. In fact I was just Googling it now and it lead me to this thread.

I saw MPC-HC's Audio Renderer and also the Sane Audio Renderer both have a somewhat vaguely related feature called "crossfeed" which kind of shifts the stereo imaging forward to try and simulate the soundstage of having a pair of stereo speakers infront of you rather than having left and right channels piped directly into your ear, but I don't think it's the same thing as HRTF, and the effect is quite subtle (although I definitely can notice it, and kind of like it for headphone use).

In any case if LAV could wire in ffmpeg/libav's HRTF feature if it exists, that would be fantastic. If you've heard the barber shop demo track with a good pair of phones you'll know how convincing it can potentially be.

[PirateIce]

Hello, the site https://files.1f0.de/lavf/nightly/ links to here as the place to report issues with the latest lav builds, so I am reporting an issue with build 0.78.0-3, it appears to be an incomplete upload
edit: fixed