LAV Filters - DirectShow Media Splitter and Decoders

[ryrynz]

Any change as far as memory consumption goes? Akim asked over at the madVR Forum so I figured i might as well ask here since this is pretty significant code overhaul.

Sent from my Nexus 5X using Tapatalk

[nevcairiel]

It could slightly reduce it, but memory is not a real focus. There is always a tradeoff between CPU and memory - ie. if you are memory constrained you can turn off multi-threaded decoding and it'll cut the memory usage down drastically, but of course everything will also be drastically slower.

[max79]

to nevcairiel:
I'm report about issue with "LAVVideoDecoder"(+"Dmitri Render"+"EVR") in last v0.69.0.33-git for h264_main_L4.0_yuv420p & h264_high_L3.0_yuv420p i didn't see picture(all in green color) in ZP. I have issue only in NVIDIA_CUVID mode. Without "Dmitri Render" i have no issue. Please see attachment.
https://forum.doom9.org/attachment.php?attachmentid=15858&stc=1&d=1492867735

[max79]

Problem with "LAV Splitter Source". It's doesn't show Album picture for remote mp3-files. Example: http://promodj.com/download/5944747/SVET%20feat.%20SevenEver%20-%20Is%20It%20Love%20%28Radio%20Mix%29%20%5BAttractive%20Music%5D%20%28promodj.com%29.mp3

Any feedback would be appreciated.

[nevcairiel]

I'm report about issue with "LAVVideoDecoder"(+"Dmitri Render"+"EVR") in last v0.69.0.33-git for h264_main_L4.0_yuv420p & h264_high_L3.0_yuv420p i didn't see picture(all in green color) in ZP. I have issue only in NVIDIA_CUVID mode. Without "Dmitri Render" i have no issue.

You posted your own solution there - disable Dmitri Renderer, and it works fine.
I recommend to get support from them, its a paid product afterall, and it doesn't function in debug mode, so I can't figure out whats wrong with it.

Problem with "LAV Splitter Source". It's doesn't show Album picture for remote mp3-files. Example: http://promodj.com/download/5944747/SVET%20feat.%20SevenEver%20-%20Is%20It%20Love%20%28Radio%20Mix%29%20%5BAttractive%20Music%5D%20%28promodj.com%29.mp3


I get cover art just fine.

[max79]

to nevcairiel:
Interesting, why i need to disable Dmitri Renderer? In v0.69 with my GTX-460SE i have no problem with CUVID mode. If you have NVidia card then download 30-day trial version DmitriRender_v3.0.0.1 install:
https://yadi.sk/d/IQBNSOIhjkHFc
After that you can update to v4_beta, download dmitriRender.dat from this link:
https://yadi.sk/d/qM2snDWU34fU8r
and copy it to your DmitriRender directory ("c:\Users\%username%\AppData\Roaming\DmitriRender").

About mp3: just fine if you previously download and playback him as local file. I'm asking about live stream playback.

[nevcairiel]

Interesting, why i need to disable Dmitri Renderer? In v0.69 with my GTX-460SE i have no problem with CUVID mode.

I tried the trial version and its green in all decoding modes, in 0.69 as well as the latest nightly.

Anyway, like I said, I can't test it properly, because in Debug mode it refuses to load. Ask the developer of that software for help instead.

[max79]

to nevcairiel:
If you have NVidia 1000series card you need to update to v4_beta, in other case you will always have green image.
About mp3-file: Why my Zoom Player didn't show album art if i playing this file in live stream mode?

[romulous]

So to everyone using nightly builds, it would be greatly appreciated if you would report any issues that appear in todays nightly (0.69.0-32 and newer), which did not occur before - either with earlier nightlies, or the 0.69 release.

I have a .ts file which in -24 (the last version prior to -32) plays fine, but in -32 and later, shows this at the very start of the clip (effect lasts for about 1 second before it clears up):
http://i.imgur.com/ILCe69U.png

LAV Splitter, LAV Video, Lav Audio - no hardware acceleration in use in LAV Video, just software.

romulous

[nevcairiel]

If you can share the file (or the start of it where this happens), then I'll see whats up.

[clsid]

You can cut a sample from the start of the file with DGSplit (http://www.datafilehost.com/d/9cbba0ed)

[romulous]

If you can share the file (or the start of it where this happens), then I'll see whats up.

Using clsid's suggestion of DGSplit, I split off the first 5 seconds of the video:
https://1drv.ms/v/s!AksqZk_W5dGsgZ9xB6vvZVy7wnc-MQ

Thanks!

[nevcairiel]

That was a silly mistake due to a missing update to the build script, which was needed from recent ffmpeg changes. Should hopefully be better now.
I also started a manual nightly run... during the day! :) There should be a new file in half an hour or so.

[NikosD]

I also started a manual nightly run... during the day! :) There should be a new file in half an hour or so.

Did you get a RyZen ? ;)

[nevcairiel]

No. LAV builds don't even take that long, ~20 minutes for full clean build for both architectures on the box the nightlies run on (if its not doing anything else right now), some haswell quad core.

[romulous]

That was a silly mistake due to a missing update to the build script, which was needed from recent ffmpeg changes. Should hopefully be better now.
I also started a manual nightly run... during the day! :) There should be a new file in half an hour or so.

Yep, fixed in -43, many thanks! :)

[biship]

For years I've been able to bitstream DTS with LAV. This stopped working about a month ago. I always run LAV bleeding edge.
I can no longer get the LAV Audio decoder to connect to my Denon AVR.
Can anyone tell me what's wrong or what I can try next?
I've spent too many years of my life trying to fix it.
(DTS will stream if I tell LAV to ignore it - then it goes out via the MC DTV-DVD Audio Decoder)

[biship]

Something broke on my HTPC about a month ago. I don't know if its LAV. I've tried almost every version of LAV since 0.69. DTS & DTS-MA bitstreaming with LAV used to work for me, and now it doesn't. Can someone please tell me whats wrong with this - or point me in the direction to try to fix it? (I've spend many hours and my head hurts).

If I enable bitstreaming in LAV, then MS DTV-DVD audio decoder is used (and not LAV), however I can not hear anything on my AVR.

If I disable bitstreaming in LAV, then LAV is used, and I can hear DTS on my AVR, however my Denon says its PCM.

[dipje]

Recent (and even not so recent) builds of ffmpeg playback DNXHR_444 files OK (reported as yuv444p10, ffmpeg flags them as 'tv' levels while most of the time they are 'full range' levels) (and there is even encoding support now).

I can't get playback (through MPC-HC) working with recent nightlies of the LAVFilters (which according to the changelog have some 'updated ffmpeg' commits done to them). Does LAVFilters need special support? Or at least a tag somewhere to accept to codec ID or something like that? It would make my life a lot easier if I could play back those files through MPC-HC.

Is a sample needed for this? ffmpeg / ffprobe reports the streams as "Stream #0:0(eng): Video: dnxhd (DNXHR 444) (AVdh / 0x68645641), yuv444p10le(tv, bt709/unknown/unknown),".
The built-in encoder for After Effects reports itself as 'RGB 10bit' but actually writes back yuv 444 with fullrange data (which ffmpeg wrongly reports as tv range).
Davinci Resolve's built-in encoder for DNXHR 444 lets you specify 'video levels' or 'full levels', but whatever you choose ffmpeg labels it as tv-range.
If there some way to override this in LAVFilters just for a single codec (or at least a single decoding- / playback session), or even just always assume fullrange levels for DNXHR in the source?

[nevcairiel]

I added handling for the AVdh type for DNxHR streams in the next build, check back in tomorrows nightly.
Overriding source range through LAV is not possible and not planned. I would recommend to report this to FFmpeg, maybe there is a flag in the bitstream somewhere which it can read (and doesn't right now).

[dipje]

Awesome, will check it then! :)

[richardpl]

It could be that 444 is always full range, but in spec its nowhere mentioned.
Could you upload 444 full and limited encoding somewhere?

[dipje]

if you want to check, test clip straight from resolve 14 public beta, dnxhr 10bit 444 in quicktime.

full levels: https://1drv.ms/u/s!AgtoBEiLfbmcpwdYM7OXzWbOqiI_
video levels: https://1drv.ms/u/s!AgtoBEiLfbmcpwidcI4aOuNevjcK

Resolve labels the dnxhr files als 'AVDn' I see, and they play back fine in MPC-HC with LAVFilters... or maybe I picked dnxhd 444 by accident instead of dnxhr? Rechecked the settings and it looked like dnxhr was still set :). Filesize is way smaller than the source, which is also DNXHR 444 10bit out of After Effects...

So it seems After Effects and ffmpeg itself label dnxhr_444 (and dnxhr_hqx apparently) as 'AVdh' but Resolve labels it as 'AVdn'... or Resolve public beta sneakily uses DNXHD encoder instead of DNXHR encoder if you seleect DNXHR 444 10bit..

The clip shows pure white and a bit of gray (95% white) and pure black and a dark gray (5% black), so if your levels are correct you should see the difference.

ffmpeg / ffplay labels the files as 'tv range' both, and indeed one of them shows all white/black, while the other shows the 5% and 95% patches.

[chros]

I've been working the last couple days on refactoring some internals of LAV Video to reduce overhead and make it more efficient, as well as generally cleaning up the code and updating to newer API standards of FFmpeg.
There is still some more work to come, but the big chunks are done. As a result, video decoding in basically all modes is slightly faster (except DXVA2-Native, which stays mostly the same, as it by-passed much of the logic already).
Thanks Nev for your continuous work on LAV!
I've just updated to x-43, will report back if something isn't good.

Edit: 1 question though:
why the install package contains old dlls? (avfilter-lav-5, avformat-lav-56, avresample-lav-2, avutil-lav-54, swscale-lav-3, avcodec-lav-56)
Are these also need?

[richardpl]

I checked files, and they have exactly same ACLR atom, the one which holds full/limited range flag.

[Bandits]

When using Enable Automatic Forced Subtitle Stream, is it always set to English language?

[nevcairiel]

Thanks Nev for your continuous work on LAV!
I've just updated to x-43, will report back if something isn't good.

Edit: 1 question though:
why the install package contains old dlls? (avfilter-lav-5, avformat-lav-56, avresample-lav-2, avutil-lav-54, swscale-lav-3, avcodec-lav-56)
Are these also need?

The installer does not contain those files, but its possible that previous versions may not have removed them when upgrading. They are not required.

[BluesFanUK]

I've got an issue whereby MadVR is making some of my videos look a weird purple/green colour, says the Matrix is GBR (says bitstream). The videos output type are NV12.

How do I play the vids normal? It's annoying me to no ends. I've got MadVR and Lavfilters installed using PotPlayer.

[huhn]

if the file is flagged for GBR and isn't you should contact the creator because the file has a wrong flag.

it is possible to create a GBR nv12 video but it is not practical this is a pretty bad fail.

try to add "matrix=bt709" with no " to the file name.

[BluesFanUK]

if the file is flagged for GBR and isn't you should contact the creator because the file has a wrong flag.

it is possible to create a GBR nv12 video but it is not practical this is a pretty bad fail.

try to add "matrix=bt709" with no " to the file name.

That worked, thanks :)

[chros]

The installer does not contain those files, but its possible that previous versions may not have removed them when upgrading. They are not required.
Oh, it could happen, my fault then. :o

[dipje]

The new AVDh tag for dnxhd / dnxhr files seems to work OK btw for me!

[IanD]

Using LAV with MPC-BE under Windows 8.1 EVR (Custom) to play 3D, selecting the Line Interleaved option doesn't produce a 1920x2160 frame but a 1920x1080 frame in a window consisting of 2 truncated, wrapped around, offset and interleaved images, regardless of the MPC options I set.

If I select the OU option I do get the expected 1920x2160 frame in a window.

MPC stats suggest a 1920x1080 video which doesn't sound correct when there are 2 eye view frames joined together.

Is there a bug in the Line Interleaved handling or is MPC just not setup to handle unusual aspect ratio video without scaling to regular aspect ratios?

[nevcairiel]

LAV is not involved in handling 3D rendering, you would have to ask the MPC-BE people what their renderer does.
One thing to generally keep in mind however is that most 3D display devices wouldn't accept 1920x2160 signals, so it may be intentional to compress it into 1920x1080 for HDMI transmission - but ask them why it does what it does.

Your best option is to use frame-packed 3D output anyway, if you have a HDMI 1.4 3D TV/Projector, which AFAIK only madVR implements for DirectShow players.

[IanD]

LAV is not involved in handling 3D rendering, you would have to ask the MPC-BE people what their renderer does.
One thing to generally keep in mind however is that most 3D display devices wouldn't accept 1920x2160 signals, so it may be intentional to compress it into 1920x1080 for HDMI transmission - but ask them why it does what it does.

Your best option is to use frame-packed 3D output anyway, if you have a HDMI 1.4 3D TV/Projector, which AFAIK only madVR implements for DirectShow players.
Since LAV, MPC-BE and MadVR are all involved in 3D output, it's difficult to know which one is not handling Line Interleaved properly as I have no idea how much bidirectional communication occurs through the playback chain.

I have an LG passive 3D 4k OLED which I want to send 3D interleaved to as its native 3D presentation format with minimum processing by TV or player, but have not been able to achieve so far. I can get 1920x2160 as over/under correctly, so not sure why interleaved is not working in a similar way.

I get the same result using EVR or MadVR, so it is unlikely to be an issue with the renderer.

How does LAV present the decoded 3D to the player? Does it vary depending on an output type flag sent by the player application or is that all handled by the player itself?

My next stop will be to ask MPC-BE.

I don't want frame packed output but 4k 2D output with the 3D presented as Line Interleaved and since MPC-BE has a switch to select it, it theoretically should work.

[madshi]

LAV sends the decoded left and right eye frames separately. LAV doesn't care what happens with the frames during rendering, that's the job of the video renderer.

madVR's "line alternative" mode was made for passive 1080p displays. In this mode half of the vertical resolution is lost because both left and right eye views are downscaled to 1920x540 and then interleaved. For passive 4K displays your best solution is to send frame packed 3D. The display should then automatically display this properly - and in full resolution. I don't know what EVR's "line interlaced" mode does, but it's probably similar to madVR's line alternative mode.

I suppose in theory it should be possible to also support a line alternative mode for 4K displays, which would then upscale the 1920x1080 left and right eye views to 3840x1080 (each) and then interleaves them to create a 3840x2160 line alternative view. This would be the most "native" 3D form the display would work with. I'm actually not sure what madVR does in line alternative mode if the output display mode is 4K. Have you tried that already? Maybe it already works? One thing is for sure, though: Sending 1920x2160 makes zero sense. That's neither a usual format, nor is it what your LG would natively display. If you want to keep the LG's internal processing at a minimum, you need to send 3840x2160 and not 1920x2160.

Anyway, this is the wrong thread for this discussion. Out of the 3 parties involved, LAV is the one which has nothing to do with line interleaved vs frame packed.

[nevcairiel]

Just to confirm, as madshi said, LAV only sends the image to the renderer, both eyes as separate images. Its all up to the renderer/player to convert it into a particular format for display. There is no bidirectional communication.

[IanD]

madVR's "line alternative" mode was made for passive 1080p displays. In this mode half of the vertical resolution is lost because both left and right eye views are downscaled to 1920x540 and then interleaved.

I guessed as much since a window on the 4k desktop always shows 1920x1080 and when enlarged to full 4k screen it looks softer than it should as though there is downscaling then upscaling.

Seems a little shortsighted to limit line interleaved to 1080 displays since the release of LG's passive 4k displays which can show the full 3D eye views natively without downscaling.

For passive 4K displays your best solution is to send frame packed 3D

I want more control over processing because frame packed 3D is forced to 24fps only and manipulation within the TV which I can't get access to.

I don't know what EVR's "line interlaced" mode does, but it's probably similar to madVR's line alternative mode.

EVR doesn't have a line interleaved mode: I think that is handled by MPC before passing to the renderer. However it produces the same results as MadVR, which now suggests MPC-HC is the culprit (although I think MadVR might also upset the end result if it is only configured for 1080 displays).

I suppose in theory it should be possible to also support a line alternative mode for 4K displays, which would then upscale the 1920x1080 left and right eye views to 3840x1080 (each) and then interleaves them to create a 3840x2160 line alternative view. This would be the most "native" 3D form the display would work with.

That is actually what I was expecting the LAV->MPC-BE->MadVR processing chain to do, but it isn't for Line Interleaved.

Sending 1920x2160 makes zero sense. That's neither a usual format, nor is it what your LG would natively display.

I think you misunderstand: to ensure the process chain is doing what it should, I first display output in a window on the desktop. Since I am displaying 3D as two 2D eye view frames joined together in some way on a 4k desktop, the window shows me whether the processing is being done correctly. This is how I discovered the Line Interleaved difference. Over/Under mode displays as a 1920x2160 window, but Line Interleaved displays as a 1920x1080 window when they should both be the same (albeit with the eye views structured differently within that window).

When I actually want to view the 3D as 3D, I enlarge the window to fullscreen and switch the TV to 3D mode (which means no special mode for Line Interleaved except putting on the 3D passive glasses).

If I only view the result in fullscreen, I can't definitively tell whether the process chain is working correctly.

As it happens, both Over/Under and Line Interleaved show as 3D in fullscreen, but Line Interleaved is significantly softer, which suggests the 3D is being downscaled to 1920x1080, then upscaled to 3840x2160 and throwing away vertical detail in the process. This is confirmed by viewing in a window.

Thanks for explaining how MadVR works though as it suggests there is a flaw when it comes to displaying 3D on a 4k desktop in Line Interleaved mode, however I expect there is also a similar issue in MPC-BE, perhaps for the same reason.

[IanD]

Just to confirm, as madshi said, LAV only sends the image to the renderer, both eyes as separate images. Its all up to the renderer/player to convert it into a particular format for display. There is no bidirectional communication.

Thanks for the clarification and confirmation: it's not obvious to a layman such as myself.

[Fabulist]

Hello everyone, excuse me if this is a silly question, but I have been researching for awhile and I cannot come up with a definite answer.

Is there a reason the mixer's levels are set at 0.71 and not at 1.0? Why would you not want the "Surround Mix Level" set at 1.0 when 7.1 are being downmixed to 5.1?

Thanks to anyone who responds in advance.

[nevcairiel]

Its typically done because the front channels are more important, and one might not want the surround channels to overshadow the fronts.
Note that the Surround Mix Level is only relevant for Stereo down mix, for 7.1 -> 5.1, its not used.

[Fabulist]

I see, thank you. So none of the options available concern 7.1 to 5.1?

[e-t172]

Is there a reason the mixer's levels are set at 0.71 and not at 1.0?

Because that's what the standard mandates. (https://www.itu.int/dms_pubrec/itu-r/rec/bs/R-REC-BS.775-3-201208-I!!PDF-E.pdf#page=11)

[Fabulist]

I see, thanks. So there none of the options serve for 7.1 to 5.1 downmixing? There is nothing I can change that will affect that in the mixer settings?

[Midzuki]

I see, thanks. So there none of the options serve for 7.1 to 5.1 downmixing? There is nothing I can change that will affect that in the mixer settings?

You can always tell LAV to leave the decompressed audio unchanged, and then let ffdshow or AC3Filter do the post-processing.
And you'd better know what you're doing (or trying to do), of course :)

[Fabulist]

Sorry but I did not understand what you said and how it is relevant to my question.

What I do is downmix 7.1 sources (95% blu-ray movies) to 5.1, by mixing the side speakers to the rear speakers. For technical reasons, the setup is a "legacy 5.1" setup, meaning I lack the side channels but have the rear ones - this is how the receiver is also setup.

Due to difficulties with the room, the rear speakers are set on a 90° diagonally behind me, on a 3 meter distance. So I wanted to know the 'best' way to mix the side channels to the rear ones and have relative sound accuracy.

However, seeing that the settings I mentioned do not consider this setup, I suppose there is nothing else I can do but let it be?

[mclingo]

I've switched off bitstreaming a while back to use reclock but after deciding to go back to bit stream I cant get DTS to bitstream at all, I just get silence and sometimes even no picture.

Its defo a LAV filter issue as its working fine in KODI and Windows 10 films and TV player.

I think i've tried everything, totally wiped MPC-BE settings and reinstalled, still no joy. I get the same problems with any media player using LAV filters.

I'm using ATI RX480, anyone have any ideas?


EDIT: doesnt work in KODI so it must be an issue with FFMEG as well on my PC, might try some different GFX drivers.

[max79]

Problem with LAV Splitter Source(v0.69.0-45_Nightly_32-bit) I have zero duration in GraphEdit(& ZoomPlayer) for this remote file if playback him as live-stream on first attempt run:
http://s1.demo-world.eu/hd_trailers.php?file=lg_beyond_reality-DWEU.mkv

Any feedback would be appreciated.

[max79]

Problem with LAV Audio Decoder(v0.69.0-45_Nightly_32-bit). This .TS-file have only 5.0 channels without LFE but audio filter can somehow output LFE(and output the audio as 5.1) despite the fact that Mixing is disable:
https://www.dropbox.com/s/i5euiw7gzx40z3b/stream_cid%3D4560.ts?dl=0

Any feedback would be appreciated.

[mkver]

Problem with LAV Audio Decoder(v0.69.0-45_Nightly_32-bit). This .TS-file have only 5.0 channels without LFE but audio filter can somehow output LFE(and output the audio as 5.1) despite the fact that Mixing is disable:
https://www.dropbox.com/s/i5euiw7gzx40z3b/stream_cid%3D4560.ts?dl=0

Any feedback would be appreciated.
Untick "Convert Output to Standard Channel Layouts" (which adds silent channels as appropriate).