LAV Filters - DirectShow Media Splitter and Decoders

[clsid]

Yes, it is normal that you see such generic pin info in case of bitstreaming.

You need to set LAV Splitter as preferred source filter in MPC-BE options. Go to MPC-BE support topic if you need help, as this is not a problem with LAV Filters itself. Or switch to MPC-HC which uses LAV by default.

[Yups]

I have issues with AV1 videos encoded from Intel Arc A380, the AV1 videos stutter, even on a TGL-U device with Iris Xe hardware decoder.


Potplayer with integrated FFmpeg decoder no problem, runs fine. LAV 0.76.1 and 0.75.0 stuttering. I've tried with MPC Home Cinema and VLC player on two PCs with same result. Could someone check this out?


Sample can be downloaded from here: https://drive.google.com/file/d/1jRK...JVITFzQxR/view

[nevcairiel]

Whatever encoded that file seems to have screwed up the timestamps. The timestamps move backwards and forwards as if the video had B-Frames, but AV1 does not have B-Frames.

[Yups]

Originally Posted by nevcairiel

Whatever encoded that file seems to have screwed up the timestamps. The timestamps move backwards and forwards as if the video had B-Frames, but AV1 does not have B-Frames.

It's from Intels Arc control panel (ingame recording). AV1 does not have b-frames? Interesting.

[YGPMOLE]

Originally Posted by clsid

Yes, it is normal that you see such generic pin info in case of bitstreaming.

You need to set LAV Splitter as preferred source filter in MPC-BE options. Go to MPC-BE support topic if you need help, as this is not a problem with LAV Filters itself. Or switch to MPC-HC which uses LAV by default.

Thank you for the answers! Everything it's properly done in MPC-BE, and other files are correctly opened/splitted/decoded by LAV, so it just seemed strange to have DTS 5.1 input and S/PDIF 2.0 out when bitstreaming, but if you says it's OK so I'll take it for the normal behavior of the pin info.

Any idea why LAV Splitter is not able to open that file and MPC Matroska Source it's used instead? It appears a normal Matroska .H264/AVC file to me...

[tormento]

DGTools is out with a beta, reading 444 flawlessly on nVidia cards. I have played those kind of files thru AVS on MPC-BE too.

I hope that it will encourage 444 support for LAV Filters.

[clsid]

There is no nightly build for latest LAV changes.

Can anyone confirm if AV1 hardware acceleration got broken after last ffmpeg update? You can use latest MPC-HC dev build to test, as that contains newest LAV build.

[lvqcl]

MPC-HC 1.9.22.34, LAVF 0.76.1.9-git - no HW acceleration for AV1.

[nevcairiel]

Should be fixed, ffmpeg didn't automatically enable a component it needs.

The nightlies should hopefully also build again, I rebuild the server recently that handles it.

[gendalv]

I thought installing this would make thumbnails show up for x265 10b .mkv files :/
In Codec Tweak Tool all things are selected for thumnails.
How to do it? Win11.

[Klaus1189]

I think I found new introduced typos: https://github.com/Nevcairiel/LAVFil...de9e4c4d074277

It is designed to offer the ability to take over the graph-building process from the player`s side.
It only exports one function which LAV Splitter will call when a stream change happens on the user`s requests

To be more precise, not simple typos but the Acute accent should not be used as Apostroph
wrong:

player`s

right:

player's

wrong:

user`s

right:

user's

[Klaus1189]

I just corrected it here:
https://github.com/Nevcairiel/LAVFilters/pull/512

[clsid]

Originally Posted by gendalv

I thought installing this would make thumbnails show up for x265 10b .mkv files :/
In Codec Tweak Tool all things are selected for thumnails.
How to do it? Win11.

No, LAV Filters is not used at all for thumbnails. You need to install Icaros.

[LigH]

Thanks, just last week I tried to remember its name...

[filler56789]

Originally Posted by Klaus1189

To be more precise, not simple typos but the Acute accent should not be used as Apostroph
wrong:

player`s

right:

player's

wrong:

user`s

right:

user's

You meant GRAVE accent alright

But you are right, neither of them is a replacement for the apostroph.

[Balling]

Originally Posted by nevcairiel

I don't think you really get it at all.

Its not about there being random mentions of 4:4:4 (without context, without further information which profiles are supported, for which codecs, etc), but the absolute lack of clear information what is actually supported. The feature matrix does not mention 4:4:4 at all, in fact it lists a bunch of profiles that are all 4:2:0. Some other feature pages list 4:4:4, some qualify that to lossless, some don't elaborate at all. Its a messy situation, and one I do not want anything to do with.

I specifically wrote it all on wikipedia. For avc only 444 predictive can be lossless, high is not lossless. Nvidia does not support 10 bit avc anyway.

[Balling]

Originally Posted by Sir Enhancealot

No point doing 4:4:4 when even Blu-ray is 4:2:0. All U R doing is WA$TING CPU & file size = LOL!!

Quote: "Blu-ray and UHD Blu-ray both store the video signal in the 4:2:0 format."

You will never get 444 Blu-rays (RGB Blu-ray more like it) if there is no support. Why do you think nvidia added lossless RGB and YCbCr 444 nvenc hevc? And, anyway, cameras from Panasonic, Leica and Nikon Z9 do lossless in some cases (Nikon) bayered N-RAW, true RAW, that is only supported by Red as it is covered by their patents (above 24p). Davinci uses lossless hevc decoder in nvidia. Does not use ffmpeg, cause 3 or 4 bugs are not present there.

Look at this nutjob samples, XAVC 444, maybe even lossless: https://trac.ffmpeg.org/ticket/9898#comment:13

[Balling]

So when atmos open source decoder? https://github.com/VoidXH/Cavern

Brownian motion: https://photos.app.goo.gl/biAubMWnT8AM18Xm6

[Balling]

Originally Posted by Sir Enhancealot

' All the 'RAW' stuff is silly because if U simply set up the camera or whatever 2 save things in a natural-looking way with the 'correct gamma curve & saturation' & stuff in the first place, when U shoot, then U don't need 2 WA$TE all that data & 'extra resolution' trying 2 keep 'everything' instead of just what U will actually NOTICE! =)

About your black comments: eye is adapted to black outside. Try walking in the dark with your phone on. It is very not nice, but I do it often. Black is more prominant in the closed space. It is also scene referred: black just means camera 20 stops cannot quite get it. The N-RAW video that is truely patented by Red >24 fps and Red is suing Nikon for it: https://forum.grassvalley.com/forum/...ample-download

Open it in Davinci. You will be shocked if you render it to BT.2020 PQ HDR. Believe me. Red is not suing them for nothing, 8256x4644x50fps.

[max79]

Originally Posted by clsid

MPC-BE Menu > Play > Filters

It is probably using "File Source (URL)", which may be caching the whole file before playback starts.

You can edit this registry key to change the source filter:
HKEY_CLASSES_ROOT\ftp
LAV = {B98D13E7-55DB-4385-A33D-09FD1BA26338}

Hello,
is the any way starting to play such URLs in "LAVSplitterSource":
ftp ://MyPassword@SiteName.com/FolderName/FileName.mp3

At this moment works only URLs like this:
ftp ://SiteName.com/FolderName/FileName.mp3