LAV Filters - DirectShow Media Splitter and Decoders

[betaking]

Looks like your ffmpeg is missing some decoders. :)



So far no-one has complained. It seems to go out the right speakers.

i download last ffmpeg from you site! :confused:
i download other build form here
http://roy.orz.hm/lavf-w32-nightlies/
same like is!:eek:
and i download http://roy.orz.hm/lavf-w32-nightlies/lavf-my110917-prores-23a517b3.7z
no problem like last stable 0.35!
http://files.1f0.de/lavf/LAVFilters-0.35-video-refactor.zip
this build no problem!

[Midzuki]

Actually, it seems that LAVFilters specifies the surround channels in 5.1 audio as being rear and not side channels. Google tells me that the opposite should be the case.

Well, "everybody" :) accepted the so-called surround channels in a 5.1 setup as rear channels, until the day the 7.1 setups started to "officially exist" :p From that day on, some people have been trying to convince us all that the old rear channels had "always" :rolleyes: and "actually" :rolleyes: meant to be side channels... O_o

[nevcairiel]

If you play 5.1 content on a 7.1 system, the surround channels are infact supposed to come out the side channels, not the rears.
A 7.1 audio signal usually has much more audio in the side channels then in the rear channels, matching that concept.

Anyway, audio drivers typically are smart enough by themself these days to output any 5.1 to the side channels, or they actually expect them to be flagged as rear channels .. its been too long since i've tested it, i just know that the "default" 5.1 layout in DirectSound appears to be with rear channels, and thats whats working fine. :)

[roytam1]

i download last ffmpeg from you site! :confused:
i download other build form here
http://roy.orz.hm/lavf-w32-nightlies/
same like is!:eek:
and i download http://roy.orz.hm/lavf-w32-nightlies/lavf-my110917-prores-23a517b3.7z
no problem like last stable 0.35!
http://files.1f0.de/lavf/LAVFilters-0.35-video-refactor.zip
this build no problem!

I wonder if you DID REPLACE ALL files.

[nevcairiel]

I know whats causing that problem, and i'll fix it later. Its nothing serious, it will not impact playback, just the config box. :p

[betaking]

I wonder if you DID REPLACE ALL files.

YES,I REPLACE ALL files!

[betaking]

I know whats causing that problem, and i'll fix it later. Its nothing serious, it will not impact playback, just the config box. :p

Thanks!and i see cuvid will Integrated into lavfilters,can you give full Compile a complete description of what?

[roytam1]

YES,I REPLACE ALL files!

Please try redownload it, replace all files, and unregister and reregister the filters again.

[betaking]

Please try redownload it, replace all files, and unregister and reregister the filters again.

problem still here by LAVVideo.ax.LAVAudio.ax and LAVSplitter.ax no problem!

[msoltyspl]

These samples can be obtained from http://samples.mplayerhq.hu/A-codecs/lossless/wavpack/test_suite/num_channels/

On a related note, I once prepared 6.1 files for testing with proper channel masks/settings (a while ago, when I was submitting a bug to ffdshow-tryouts):

http://soltys.ziu.info/temp/61v2.7z (wav with proper channel mask)
http://soltys.ziu.info/temp/61v2.flac (--channel-map=none, required to properly rely on WAVEFORMATEXTENSIBLE)
http://soltys.ziu.info/temp/61v2-from-wav.ogg

Useful thing about those samples, is that they tell you which channel should go where as a part of the sample.

[Inspector.Gadget]

I notice when playing a DVD-VOB file (Directly, not as a title set or through a DVD structure) with the LAV Splitter and LAV Cuvid that closed captions (not regular DVD subs) are solid black; being text-based, it should be trivial to render them in a readable color by default instead. Do your LAV components have any influence (via decoding Line21 content within the CUVID decoder, etc.) over this or is this strictly internal to MPC-HC? Thanks.

[nevcairiel]

I do not render subtitles at all. MPC-HC is probably doing that.

VOB Subs are bitmap subs, btw. It probably has a wrong palette for rendering which causes them to go black.

[glith]

Any possibility to implement the delay option in LAV audio(Issue 63) before next release?

:thanks:

[Inspector.Gadget]

OK, thanks. I had selected the bitmap subs by mistake. By the way LAV Splitter works flawlessly with Line 21 Decoder 2 and Cyberlink MPEG-2 decoder on direct playback of VOBs.

[DJ_Phatic]

Yep, that did the trick. Thanks a lot.

I finally found a HD-DVD demo file (HD-DVD Demo 1080p VC-1 DDPlus 5.1 (http://www.techpowerup.com/downloads/530/.html)) which has the standard DD+ (E-AC3) stream (without any AC3 core).
LAV bitstreamed it to my receiver and DD+ light showed up for the first time.
The only combination to bitstream all supported audio is MPC-HC with LAV Splitter & Decoder.......guaranteed.
Thanks nevcairiel :thanks:

I just tried out the sample file as I couldn't get a remuxed HD-DVD in mkv container with a E-AC3 to playback any sound.

I get no sound with the test file either when I select the E-AC3 track. My receiver is an Onkyo 875 which supports TrueHD/DTS-MA so I presume it also supports DD+ bitstream.

[xiulet]

I just tried out the sample file as I couldn't get a remuxed HD-DVD in mkv container with a E-AC3 to playback any sound.

I get no sound with the test file either when I select the E-AC3 track. My receiver is an Onkyo 875 which supports TrueHD/DTS-MA so I presume it also supports DD+ bitstream.

In my system when switch to dd+, the video is going to stutter , my receptor is catching dd+ fine.

http://i.minus.com/i56kaN4CNkkHh.JPG

i am using mpc hc + lav audio and filter.

:thanks:

[DJ_Phatic]

In my system when switch to dd+, the video is going to stutter , my receptor is catching dd+ fine.

I was using the Realtek driver which was the problem, using the ATI driver DD+ bitstreams though I also noticed some stuttering.

[xiulet]

I was using the Realtek driver which was the problem, using the ATI driver DD+ bitstreams though I also noticed some stuttering.

i am using the realtek driver from his page i read that is better in general realtek ATI HDMI Audio Device (http://218.210.127.131/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false)

i think may be is a problem of the video or the filters.

thanks, ad1

[nevcairiel]

A short preview for the next LAV Video version. I added a whole bunch of new options, stolen from LAV CUVID. :p

http://images.gammatester.com/pics/12387c66559ca94c4e88032f45859f57.png

Although i also added one new one, which was requested for LAV CUVID a while ago, finally got around to implement it here now. :)

[mindbomb]

so, in the near future, you can get lav video to do the HQ rgb conversion with cuvid?

fantastic news for my 8600gt that can't use cuvid and madvr at the same time.

in an unrelated note, so if you try to play a 10 bit h264 video, hw decoding will automatically disable itself?

[fastplayer]

Looks great! :)
Are you gonna remove the HQ-Format-Conversion checkbox? You've mentioned it a while ago.

[nevcairiel]

so, in the near future, you can get lav video to do the HQ rgb conversion with cuvid?
Yes.

if you try to play a 10 bit h264 video, hw decoding will automatically disable itself?

Thats the plan, but not implemented yet. Its one of the things missing before a release.


Are you gonna remove the HQ-Format-Conversion checkbox? You've mentioned it a while ago.
I probably could, its mostly useless now, but no harm either way.

[SamuriHL]

So this means the LAV CUVID code base is integrated now with LAV Video? Anything we should know about building it? :D I haven't done a build in a while but was planning on doing one tonight to get the latest code.

[nevcairiel]

Anything we should know about building it?

You don't need the CUDA SDK anymore.

[SamuriHL]

You don't need the CUDA SDK anymore.

Nifty. I'll try a build a bit later. Thanks!

[nevcairiel]

Note that its not 100% complete yet.

Whats still to do for CUDA/CUVID:
- VC1 decoding will not result in proper timestamps
- Automatic software fallback on unsupported movies (10bit H264, 4:2:2 MPEG-2, etc)

I also axed MPEG4-ASP support for the time being. I don't think its really worth it, the software decoder will do it much better.

[SamuriHL]

Well, I'd like to try it out in MC16 and test it before you release a version that's combined. I'd like to make sure they won't run into any problems since they currently use LAV CUVID in some cases by default.

[nevcairiel]

LAV CUVID itself won't break of course, it just won't be updated much anymore.

[SamuriHL]

Right, but, given how they consume the filters I just want to make sure nothing gets screwy in that configuration. Matt will want to remove LAV CUVID at some point once you do a full release. The question then becomes...does he default MC16 to LAV Video in all cases. I'd personally say yes but that's not my decision. :D I know on my machines that's what I've been using and have no problems.

[nevcairiel]

They would probably require software deinterlacing before they can make the switch, or use ffdshow as a post-processor.
Well, they can decide how to handle it. I honestly don't care much. There will be a transition period until LAV Video can fully provide a full playback chain with YADIF, but i have to start somewhere, don't I. ;)

After cuvid is done, my next goal is either integrating the MS wmv9 software decoder (for vc-1 interlaced), or a Intel hardware decoder. Not sure yet which to tackle first.

[VipZ]

Awesome work nev.

After cuvid is done, my next goal is either integrating the MS wmv9 software decoder (for vc-1 interlaced), or a Intel hardware decoder. Not sure yet which to tackle first.

I vote MS wmv9 ;)

[SamuriHL]

I would vote for the MS decoder. :D That would be quite useful. And yea, I'll maybe start a thread over there to make them away that LAV CUVID code is being integrated into LAV Video and that they may want to start considering switching over to LAV Video for the default. Interlace stuff isn't that big a deal to handle. As you said, there are multiple ways to do it including just using MS decoder for VC1 interlaced content. They can figure that out. :)

[madshi]

JFMI, what would be the benefit of integrating the MS VC-1 decoder over using the already existing MS DMO?

[nevcairiel]

Alot of DirectShow players have issues disconnecting and re-creating the video decoder/renderer on the fly, so it would be beneficial if there is one good decoder for all needs, which can just switch decoders internally.
This is mostly aimed at future advanced Blu-ray support (title switching, full navigation, even menu support), where the video type can switch on the fly between titles, but nothing really relevant right now.

But alot of people keep asking for it as well, not sure what they want to get out of it, but i have fun doing it, so why not! :)
I guess it simplifies their filter setup somewhat.

There is also my idea of using hardware deinterlacing with software decoding, but i guess thats only half-valid, as you could as well just use a hardware decoder for VC-1i then.
Maybe i'll go with the Intel decoder first. I already saw a patch for VC-1i decoding with libavcodec. It produces some kind of image, but its still somewhat a WIP. But there is hope. :)

[SamuriHL]

For MC16 it'd be useful because you could just tell it to use LAV Video for everything and it'll switch internally for whatever content you're playing.

[SeeMoreDigital]

There is also my idea of using hardware deinterlacing with software decoding, but i guess thats only half-valid, as you could as well just use a hardware decoder for VC-1i then.

Can a similar idea be incorporated to add AVClossless decoding to your "LAV CUVID" decoder?


Cheers

[CruNcher]

Can a similar idea be incorporated to add AVClossless decoding to your "LAV CUVID" decoder?


Cheers
Nope the best way (most efficient though also most complex way) is to dynamically jump between Hardware and Software Decoder cores currently but the different reaction on different renderer (and then you have the different performance, the logic of what is better for your Hardware what gives you the best experience for this Format Hardware Playback or Software (will this 60 fps stream playback fast enough in my setup on the Discreete DSP or will it fail and should i better use the Software Decoder), and the switching logic though in terms of hardware and Renderer limitations that is already good under control) with different input and different behavior for different parser makes this all a pain with dshow :( inlcuding the Deinterlacing things to keep in mind :( and then the Interface side without hurting quality in any scenario and there are a lot of Playback Scenarios (content wise).
Just a big complex mess if you aren't doing everything in context from the Player on and in those regards you are heavily dependent on what the Vendors are doing in their Drivers also which Renderer they support with their implementations and so on :(
And in this equation isn't included the differences between NT 5 and NT 6 behavior, just if you would say only 1 OS keeping complexity small as possible is hard over multiple OS it gets crazy especially if you want to support all 3 major Vendors currently Intel, Nvidia , AMD (their you need to know the limitations then of every of their solutions also to make these decisions efficiently).
So somehow it's understandable that Intel says NT 6 support only :P

The easiest way is forcing EVR (its supported by everyone it supports Shader and with Aero tearing is history but it's not efficient as EVR-CP nor MadVR and then you get into issues again, user demands and hardware issues tearing performance because of Aero not supported or to slow) :(

[SeeMoreDigital]

Bummer!

[CruNcher]

So my concept was you have a Player and inside it a small benchmark and analyze logic that tests @ first your system Performance and the Performance of the Vendor Hardware your system consists of in your configuration (VPx,UVD,Quicksync) and based on these individual System benchmarks (Vendor API,DXVA) you can do the decisions for the most popular formats and playback scenarios which for every Vendor are the same VC-1,Mpeg-2,H.264. Though obviously this is only a part of the whole "Smart Playback Decisions" thing.

[Mustaffi]

when l play some H264 4:2:2 videos they are rare colors y random artifact all over....

screen:

http://img831.imageshack.us/img831/2449/422u.png

[roytam1]

Awesome work nev.



I vote MS wmv9 ;)

As I own AMD GPU and VC1-i issue is fixing by libav guys, I vote for DXVA.

[xiulet]

hi all my friends, from my ignorance, i have a question for you , what is the real possibility of make something like lav cuvid (or gpgpu stuff audio/video ) using opencl, today?

thanks, ad1

[Mixer73]

hi all my friends, from my ignorance, i have a question for you , what is the real possibility of make something like lav cuvid (or gpgpu stuff audio/video ) using opencl, today?

Much, much less likely than AMD exposing their API for video decoding, which looks increasingly unlikely.

[sneaker_ger]

Much, much less likely than AMD exposing their API for video decoding, which looks increasingly unlikely.

Didn't they already do the latter?
http://developer.amd.com/sdks/AMDAPPSDK/assets/OpenVideo_Decode_API.PDF

[nevcairiel]

Their API is useless. It doesnt allow interoperability with D3D, which would be required for deinterlacing. just for decoding, its not worth implementing

[betaking]

So my concept was you have a Player and inside it a small benchmark and analyze logic that tests @ first your system Performance and the Performance of the Vendor Hardware your system consists of in your configuration (VPx,UVD,Quicksync) and based on these individual System benchmarks (Vendor API,DXVA) you can do the decisions for the most popular formats and playback scenarios which for every Vendor are the same VC-1,Mpeg-2,H.264. Though obviously this is only a part of the whole "Smart Playback Decisions" thing.

I did set the codecpack process had brought a bag with hardware and system test functions, can automatically switch to the corresponding operating system and hardware decoders and splitters!:)

[nevcairiel]

when l play some H264 4:2:2 videos they are rare colors y random artifact all over....

H264 4:2:2 is not yet supported.
Where do you get such content anyway?

As I own AMD GPU and VC1-i issue is fixing by libav guys, I vote for DXVA.

That was not a valid option in the poll.

[ForceX]

I just found out I could use LAV CUVID with my CUDA 2.2 driver thanks to working CUDA acceleration in roytam's latest LAVFilters build. xD Last time I checked (months ago) it wouldn't work and I hadn't bothered checking the thread because I don't expect devs to extend backwards compatibility anymore. >.> Nev, you're awesome.

Stupid never updated laptop drivers...

[mindbomb]

i vote for wmv9.

that affects more ppl i think, since it would be almost everyone who doesn't use lav cuvid atm.

[nevcairiel]

Since madshi brought it up before, someone explain to me again why they want wmv9 instead of using the MS decoder in the first place. :)


I just found out I could use LAV CUVID with my CUDA 2.2 driver thanks to working CUDA acceleration in roytam's latest LAVFilters build. xD Last time I checked (months ago) it wouldn't work and I hadn't bothered checking the thread because I don't expect devs to extend backwards compatibility anymore. >.>

Thats actually just a side-effect of dynamically loading the functions i need. That way it doesn't depend on a specific dll anymore, it just works as long as the dll you have exports all the required functions. :)