View Full Version : LAV Filters - DirectShow Media Splitter and Decoders
markanini
2nd October 2016, 19:50
I'd love to see replaygain support.
CruNcher
3rd October 2016, 00:08
Hmm lav 68.1-31
causing sync issues again
sonyvegas14_best_hightier_360°.mov
https://www.sendspace.com/file/87bq1x
http://i1.sendpic.org/t/fv/fvlCHmb4zSNxVBIC7CmzhJ7FlY3.jpg (http://sendpic.org/view/1/i/6iThGM1DEQn3nx5JbP3JyqtQqbk.png)
Something wrong on the splitter side or the decoder or both ?
tried the file with nightly MPV it plays fine
PS: Just tried MPC-BE Internal nightly filters they work also just fine with the bitstream so looks like a bug, though the scene change issues with the transformer bitstream remain untouched.
http://i1.sendpic.org/t/lr/lrGw4REtvE0unhUuKTmsw1BFgoX.jpg (http://sendpic.org/view/1/i/oCdR6zvF85NaUwwgRMcbMhpvbTh.png)
http://i1.sendpic.org/t/v5/v5k4B0AagOBMTIqwuYqo8S8z6Tl.jpg (http://sendpic.org/view/1/i/8WfgeSxuAALrVP2v5n55MftXFUH.png)
Lentoid still fails with the bitstream and mpc-be splitter combo
http://i1.sendpic.org/t/EO/EOZR5vDTPyHuDiRGf3G9TqLxvU.jpg (http://sendpic.org/view/1/i/334l12mM7AwktFbT0W2H7QW4tNM.png)
clsid
3rd October 2016, 15:51
The Frame Time Correction option in MPC-HC can 'fix' the problems with that sample.
CruNcher
3rd October 2016, 18:21
right just pushing c with lav video and the problem is gone
aiks what is the right/wrong behavior now ?
should it always only playback with the FTC correctly on EVR with 25 fps or should it playback from itself like in MPV (ogl) and MPC-BE without FTC @25 fps on EVR ?
FTC has also impact on the Transformer Sample instead of 3 or 4 consective dropouts after a scene change you only get 1 bigger one though im not really sure which behavior is to prefer both is bad in its own way ;)
with ftc
http://i1.sendpic.org/t/zB/zBHfO1GyicTnGMBVQxyz5OsyoUp.jpg (http://sendpic.org/view/1/i/vdhfiC0ygtFV9nKt9z3Ulb3WxRr.png)
without ftc
Though if i think about it maybe it was done on purpose to get this stop hard cut effect ?
http://i1.sendpic.org/t/al/altO8EMeibuZ0oa8EgjFMYF7puj.jpg (http://sendpic.org/view/1/i/1lSbFbAAGolBz9uaOvCJNpLQHyh.png)
but that makes no sense at all as scene blends that got detected as sencechanges are also affected so most probably it really is a overflow situation on Atemes encoder side @ that time :D
fxv300
8th October 2016, 22:22
This issue also happens with AMD Polaris range.
It could be a LAV filter issue.
Blog here (https://rx480.blogspot.co.uk/)
video (https://youtu.be/hCCBxKPOI84)
Hello,
I have heavy artifacts if I use dxva2 (native) with my GTX 960 4gb, with Software decoding or QSV it's no problem.
The content is of a TV channel, some of the times its just fine on that channel sometimes I get the artifacts.
Here you can download the sample (is SD and I think H.264): https://www.dropbox.com/s/2zxhgqx2dht68qg/DXVA_NVidia_bug.ts?dl=0
Is this a known bug? Is there a workaround? Have others also problems with Nvidia graphics playing this short sample?
If needed I want to make screen record of the artifact...
Thanks and kind regards,
Clemens
nevcairiel
9th October 2016, 08:24
All these issues happen with other decoder as well, sometimes at slightly different circumstances, but still happens. Polaris decoders are just broken, if its in drivers or in the hardware only AMD can tell you.
The sample you quoted for example is also broken with Microsofts decoder, so its very likely a driver or hardware issue.
People really shouldn't jump to conclusions without proper information. H264 DXVA2 decoding in particular has been well tested over various generations of hardware, so if suddenly a specific piece of hardware shows issues, its far more likely to be that hardware (or its drivers), rather than a fundamental issue in the software. Even more so if other decoders show the same problems.
CruNcher
14th October 2016, 00:39
As i said wouldn't really surprise seeing how catastrophically UVDs Parser behavior was especially at the beginning with Broadcast and Resilience Playback Nvidia had only very minor issues that got really fast fixed 1 after another via Firmware updates early on through lot of developer and community feedback with problematic bitstreams (not bios firmware but the VPX Firmware on the Driver side) mostly.
So this is something AMD still has to go through to get their Hardware more stable in the future lot of bad decision in the past where made and Nvidia ran so fast away with their more open ecosystem approach initiated by Roy Taylor back then, until Intel arrived and hell did they pressured.
We already see some some really great things from him now being the Corporate Vice President of Alliances for practically the whole AMD Ecosystem which even became so much more open then we just could have dreamed for on Nvidias side now feedback will be the key to domination the faster this process runs now the better.
And i really see that Doom9 once again could become the major aggregation point for this feedback and enhancing process for AMDs UVD and Media SDKs ;)
Joniii
15th October 2016, 08:17
Is there any way to to make LAV Filters prefer AC3 core from TrueHD?
My receiver doesn't support TrueHD and LAV Filters always plays TrueHD if available and I have to manually change to AC3 core from MPC-HC.
ryrynz
15th October 2016, 11:02
Is there any way to to make LAV Filters prefer AC3 core from TrueHD?
Just untick 'Dolby TrueHD' under 'Bitstreaming (S/PDIF, HDMI)' options in LAV Audio.
Joniii
15th October 2016, 14:10
Just untick 'Dolby TrueHD' under 'Bitstreaming (S/PDIF, HDMI)' options in LAV Audio.
That's how I've always set it up, but LAV Audio selects TrueHD as default and I have to manually select AC3 core.
15621
sneaker_ger
15th October 2016, 15:28
Try turning off "Prefer Audio Stream with the Highest Quality" in LAV Splitter. But this will only work in some cases. I don't think there's currently any setting to always prefer AC3 over TrueHD. A workaround would be to use an additional filter that encodes to AC3 on-the-fly (like ReClock or AC3 filter) - the encoding may be less good than the original AC3 core done with (I assume) professional Dolby encoder, though.
Joniii
16th October 2016, 08:06
Try turning off "Prefer Audio Stream with the Highest Quality" and "Demux sub-streams separately" in LAV Splitter. But this will only work in some cases. I don't think there's currently any setting to always prefer AC3 over TrueHD. A workaround would be to use an additional filter that encodes to AC3 on-the-fly (like ReClock or AC3 filter) - the encoding may be less good than the original AC3 core done with (I assume) professional Dolby encoder, though.
Thanks. Sadly "Prefer Audio Stream with the Highest Quality" didn't have any effect on TrueHD. :/
@nevcairiel
Would it be possible to add new if into the audio/splitter configuration, so that if TrueHD bitstreaming is not checked, it would select AC3 core as default track? Or would that break something?
If the receiver doesn't support TrueHD and it is not selected on bitstreaming settings, it will still use TrueHD as default track and passes it as 2ch to receiver and I have to manually select core as on the screenshot on few posts back.
huhn
16th October 2016, 09:42
think about using analog.
with analog output you don't need supported bitstream formats to get surround audio. so flac, aac and other surround formats don't need realtime reencoding.
i would always avoid SPDIF if possible.
e-t172
16th October 2016, 10:48
think about using analog
...or LPCM over HDMI.
huhn
16th October 2016, 14:07
his AVR doesn't have HDMI.
clsid
16th October 2016, 14:16
The splitter functions independently from the audio decoder and is thus unaware of the bitstreaming settings. A new option would be required to prefer substreams.
sneaker_ger
16th October 2016, 16:21
Maybe it would make sense to always put the core stream above the lossless outer one (in the stream order) when "Demux sub-streams separately" is activated. No new option needed but more use-cases covered.
zerowalker
16th October 2016, 23:44
Not sure how to "report" this issue i am having.
You see if i record mkv with OBS Studio,
that file will be unseekable as in, Every time i seek, it will read through from the start of the file till that spot.
As you can imagine this takes Forever on huge files.
So i was sure it was a bug with the mkv files.
But, then someone said that it worked fine on VLC,
so i tried it, and it does for some reason. (I use MPC-HC with LAV Filter).
Now, i don't know where the issue lies, but i would guess that it's the Splitter?
Any suggestions on how to go forward with this?
Thanks:)
huhn
17th October 2016, 07:55
start with a sample maybe.
zerowalker
17th October 2016, 08:03
Problem is that it's very hard to even notice on a sample.
IT's when you reach several GBs that you actually notice it.
Cause if the file is just some megabytes,
it will read it so fast that it appears to be seekable.
nevcairiel
17th October 2016, 10:20
The likely cause is that OBS doesn't write any seeking index.
clsid
17th October 2016, 14:38
You can fix those files by remuxing them with MkvToolNix.
zerowalker
17th October 2016, 17:49
Remuxing solves it yeah.
But why does VLC work fine, any idea?
And OBS doesn't really much itself, it lets ffmpeg handle it.
el Filou
17th October 2016, 21:03
This issue also happens with AMD Polaris range.
It could be a LAV filter issue.
Blog here (https://rx480.blogspot.co.uk/)
video (https://youtu.be/hCCBxKPOI84)
For the record, the file linked in that quoted message plays just fine on my very (very veeery... :o) old Radeon 4650 on driver 8.970 with DXVA Native, so it's really the recent drivers and/or hardware from NVIDIA and AMD that have a problem with (SD) broadcast H.264, and not LAV.
That doesn't make me happy as I'm planning to buy either an RX 460 or a GTX 1050 very soon to replace the antique card in my HTPC, and I watch a lot of DVB with it, so if you ever find a fix for those issues please share here, thanks!
akim
19th October 2016, 21:11
I assume that something has changed in the drivers for AMD HD 7850 card in Win 10
I have a soft-mode does not work when you run any video (avi, sd)
card rate increases to 450-1200 and should be 300-150
I tried everything: evr, evr-cp, default system does not help
p.s tested other players, they also raise the frequency only mpv player - keeps frequency 300-150
GCRaistlin
21st October 2016, 23:54
I can't get hardware decoding enabled for an UHD file:
3840x1606 at 23.976 fps, x264, ~100 Mbps avg
LAV Video settings window says "Active Decoder: av codec, Active Hardware Accelerator: none". UHD checkbox is set, DXVA copy-back is selected.
For FullHD video, it works: http://i68.tinypic.com/m80mza.jpg
Win 8.1, HD7850, Crimson 16.10.1.
huhn
22nd October 2016, 01:36
which codec is used in that video.
and i don't know if an old AMD card can do UHD they struggle with 1080p60.
captaiŋadamo
22nd October 2016, 02:05
I can't get hardware decoding enabled for an UHD file:
3840x1606 at 23.976 fps, x264, ~100 Mbps avg
LAV Video settings window says "Active Decoder: av codec, Active Hardware Accelerator: none". UHD checkbox is set, DXVA copy-back is selected.
For FullHD video, it works: http://i68.tinypic.com/m80mza.jpg
Win 8.1, HD7850, Crimson 16.10.1.
It's not enabled because your card doesn't support it. Why would you expect an AMD card from 2012 to support UHD decoding?
NikosD
22nd October 2016, 04:33
I can't get hardware decoding enabled for an UHD file:
3840x1606 at 23.976 fps, x264, ~100 Mbps avg
LAV Video settings window says "Active Decoder: av codec, Active Hardware Accelerator: none". UHD checkbox is set, DXVA copy-back is selected.
For FullHD video, it works:
Win 8.1, HD7850, Crimson 16.10.1.
The first AMD card ever supporting UHD/4K H.264 was released on 2014 and it was the first GCN3 card - the R9 285.
Any card before R9 285 supports up to 1080p - FullHD.
VictorLS
22nd October 2016, 17:39
GCRaistlin
8 or 10bit? h264 10bit can not be accelerated by any videocard.
el Filou
What Windows (or Linux) plan you use with HTPC? If not Win10 there is old LAV CUVID Decoder 0.13 which plays DXVA_NVidia_bug.ts (and all other such files) well in Win7x64 with unchecked Use HQ DXVA Processing in properties of LAV CUVID Decoder (in XP even LAV Video Decoder plays those files and all SAT channels well with NVIDIA CUVID hardware acceleration). For h265 UltraHD you can use LAV Video Decoder with DXVA2 acceleration in Win7 (LAV CUVID Decoder can not decode h265), because nobody here want to implement h265 10bit acceleration in NVIDIA CUVID (both LAV CUVID and LAV Video Decoders) as in Linux https://devtalk.nvidia.com/default/topic/965840
It is very (very veeery... ) pity because my HTPC on WinXP 32bit is not perfect now (it can not play h265 10bit smooth both from SAT and from files - I have to boot Win7x64 for h265 10bit only - all others I watch in XP except h264 10bit at all of course.
el Filou
23rd October 2016, 17:24
el Filou
What Windows (or Linux) plan you use with HTPC? If not Win10 there is old LAV CUVID Decoder 0.13
I'm using Windows 10. I guess I'll have to check the forums before buying a new card to make sure it plays interlaced DVB streams without corruption.
I'm using MediaPortal which has a decent forum community so maybe this issue will popup over there.
huhn
23rd October 2016, 18:35
driver should fix that some time in the future and there is still software decoding.
P.J
24th October 2016, 17:41
This file is 16:9 Bottom Field First but plays as 4:3 Top Field First :confused:
General
Format : MPEG-4
Commercial name : DVCPRO HD
Format profile : QuickTime
Codec ID : qt 2005.03 (qt )
Overall bit rate mode : Constant
Overall bit rate : 117 Mbps
Writing library : Apple QuickTime
Video
ID : 1
Format : DV
Commercial name : DVCPRO HD
Codec ID : dvh6
Duration : 3mn 48s
Bit rate mode : Constant
Bit rate : 97.8 Mbps
Encoded bit rate : 115 Mbps
Width : 1 280 pixels
Clean aperture width : 1 888 pixels
Height : 1 080 pixels
Clean aperture height : 1 062 pixels
Display aspect ratio : 1.185
Original display aspect ratio : 16:9
Clean aperture display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (29970/1000) fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:2
Scan type : Interlaced
Scan type, store method : Interleaved fields
Scan order : Bottom Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 2.360
Language : English
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
VictorLS
24th October 2016, 20:31
el Filou
Win10 has only DXVA acceleration - CUVID not work in 10 and I do not know why - this is one of the many many thing why I not use Win10.
leoenc
28th October 2016, 14:28
Any chance to add support for 10-bit ProRes files?
Currently they are being interpreted as 8-bit in AVIsynth+.
With AVIsynth+'s new support for high bit depths, this could be really useful, as the only alternative is using FFMS2 but indexing of big ProRes files takes forever.
LigH
28th October 2016, 14:38
"Support" would require a source filter being able to read it and decode it to an uncompressed format supported by AviSynth+. Which source filters could that be?
a) native source filters based on libavcodec, like FFMS2 or L-SMASH Source: can be able to support it natively, but writing an index to disk is slow, and keeping the index in RAM may need much of it, as it seems to have keyframes for all frames (intra-frame only codec).
b) AviSource: would have to rely on VfW codecs installed in the Windows system, and whether they can provide high bit depth output
c) DirectShowSource: would have to rely on DirectShow filters installed in the system, and whether they can provide high bit depth output
d) mixed technology source plugins like DSS2Mod: hmm, not sure if there are any quirks...
sneaker_ger
28th October 2016, 14:43
Since LAV is a DirectShow filter I assume he's talking about that. Thing is: LAV can ouput 10 bit just fine. AviSynth+'s DirectShowSource() likely doesn't yet accept it so LAV falls back to 8 bit.
LigH
28th October 2016, 14:49
Well, DSS2Mod can use LAV Filters also with a native API. But I believe it won't request any HBD modes. That may require a specific awareness of AviSynth+.
nevcairiel
28th October 2016, 15:04
In any case LAV supports decoding ProRes in 10-bit just fine. Anything else AviSynth related is out of my hands.
P.J
28th October 2016, 19:26
This file is 16:9 Bottom Field First but plays as 4:3 Top Field First :confused:
General
Format : MPEG-4
Commercial name : DVCPRO HD
Format profile : QuickTime
Codec ID : qt 2005.03 (qt )
Overall bit rate mode : Constant
Overall bit rate : 117 Mbps
Writing library : Apple QuickTime
Video
ID : 1
Format : DV
Commercial name : DVCPRO HD
Codec ID : dvh6
Duration : 3mn 48s
Bit rate mode : Constant
Bit rate : 97.8 Mbps
Encoded bit rate : 115 Mbps
Width : 1 280 pixels
Clean aperture width : 1 888 pixels
Height : 1 080 pixels
Clean aperture height : 1 062 pixels
Display aspect ratio : 1.185
Original display aspect ratio : 16:9
Clean aperture display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (29970/1000) fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:2
Scan type : Interlaced
Scan type, store method : Interleaved fields
Scan order : Bottom Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 2.360
Language : English
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
No idea? =/
huhn
28th October 2016, 19:52
this should be the problem:
Width : 1 280 pixels
Clean aperture width : 1 888 pixels
Height : 1 080 pixels
Clean aperture height : 1 062 pixels
Display aspect ratio : 1.185
Nintendo Maniac 64
28th October 2016, 20:26
Question - is there any way to have LAVfilters enable hardware decoding for HD (720p) but not FHD (1080p)?
Currently you can only specify SD (480p), HD (1080p), and UHD (2160p)...
I'd love to see replaygain support.
I would too, but I believe this is something that would be implemented by the media player rather than LAVfilters.
(which does beg the question of why MPC-HC doesn't support it...)
CruNcher
28th October 2016, 20:45
Resilience Playback issues have arrived @ AMD ;)
https://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-Edition-16-10-3-Release-Notes.aspx
Known Issues
A few game titles may fail to launch, experience performance issues or crash if the third party application "Raptr" has its game overlay enabled. A workaround is to disable the overlay if this is experienced.
H.264 content playback may experience playback issues on internet browsers with hardware acceleration when also running gaming applications or content.
The Division™ may experience checkered corruption when using character model overlays or the game menu.
Some users without the Radeon WattMan feature may experience a Radeon Software popup error regarding Radeon WattMan.
FIFA 17™ may experience an application hang or black screen on launch for some select Hybrid Graphics or AMD PowerXpress mobile configurations.
H.264 content may experience blocky corruption when streaming using P2P content players on some Radeon RX 400 series graphics products.
Not a bad reaction time anymore, though they knowing the issues doesn't mean they will be able to fix them or when that will happen but at least they know it by now that something is wrong :D
Though it's funny they speaking of "some" not every which is strange now.
So maybe we have to differentiate between UVD inside of Polaris 10/11 as well with that information ?.
That Driver Multitasking issue is interesting who is doing wrong here Internet Browser Engine, AMD Driver or Windows, make your bets ;)
P.J
28th October 2016, 23:12
this should be the problem:
Width : 1 280 pixels
Clean aperture width : 1 888 pixels
Height : 1 080 pixels
Clean aperture height : 1 062 pixels
Display aspect ratio : 1.185
But the aspect ratio is 16:9, same as HDV 1440x1080i @ 16:9
huhn
29th October 2016, 09:03
but the decoded video is still 1280x1080 (if i understand this correct).
it needs to be displayed at 1880x1062 and the playback software needs to know and support that.
the file it self says it is 1,185:1 a TV recording is say it is 16/9. so the DAR is wrong in the file or wrong interpreted by media info. even the refreshrate is strange it should be 30000/1001 not 29970/1000
this is a TV recording:
Maximum bit rate : 20.0 Mbps
Width : 1 440 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
LigH
29th October 2016, 09:26
It sounds like this is a common issue with Apple Final Cut Pro, but even a bit perverted here: According to this forum thread (https://forums.creativecow.net/thread/8/1133273) (warning, ads and 3rd party certificates) it often happens that footage prepared in 1920x1080 HD ProRes 444 gets a "Clean aperture" cropping down to 1888x1062 in FPC project settings before being compressed to the final format, and these values don't apply to different resolutions very well...
:devil:
VHT
29th October 2016, 16:03
Hello, I've been messing around with my HTPC + 3D and picture looks fantastic with madVR + LAV Filters, but subtitle depth (plane) goes occasionally wrong resulting my eyes going awry. I'm watching original blu-ray ISO's and using madVR v0.90.20, LAVfilters 0.68.1. MPC-HC + Nvidia 373.06 drivers.
Been testing same movies with Pioneer standalone blu-ray player and the subtitle depth is correct with that.
Is this a know problem or is it just me?
I'd be really grateful for any help.
trandoanhung1991
29th October 2016, 19:32
Trying to get LAV to decode with CUVID the following clip http://demo-uhd3d.com/fiche.php?cat=uhd&id=148. Using LAV 0.68.1.
Any idea why it keeps defaulting to avcodec? I have a GTX 1070 which should be able to decode this with ease, since it supports 4k@60 10b decoding.
VictorLS
29th October 2016, 21:39
trandoanhung1991
I already tired to ask implement h265 10bit support in NVIDIA CUVID in LAV Video Decoder (I use 0.68.1 also) or even in LAV CUVID Decoder (last 0.13 but I hope to see 0.14 with h265 10bit support). Nobody answered here about it (
Although such clips are accelerated by DXVA2 in Win7-10 or CUVID in Linux https://devtalk.nvidia.com/default/topic/965840
I am sure there is a switch in code of LAV Video Decoder which force turn off hardware acceleration when CUVID is chosen and h265 10bit is playing because when h265 12bit is playing with CUVID hardware acceleration is on but with pink squares on my GTX750 GM206-150 based videocard in XP and Win7x64.
jkauff
30th October 2016, 04:59
I can't play 10-bit H.265 on my system, but I thought that H.265 was handled by a separate chip on Pascal cards, not CUVID cores. Isn't NVDECODE the interface to that chip's decoder?
I'm sure someone more knowledgeable will tell me if I'm wrong. :)
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.