LAV Filters - DirectShow Media Splitter and Decoders

[max79]

to mkver: Thank you!

[mclingo]

is it just my machine or is LAV audio totally messed up, or is it the creaters update?

I cant get DTS to bitstream and its not sending the right information to my speakers. Rears are summed and i'm getting not height, height is being summed to front left and right.

if i play my test audio files in windows films and TV it works find, its just anything with LAV filters, whats going on???

edit:

found this....

Microsoft Response
The Creators Update, and Windows Insider builds 14980 and later, broke "encoding Audio Processing Objects" that are used in third-party drivers to power things like Dolby Digital Live and DTS Connect, where the output of the Windows shared-mode audio engine is sent to an external decoder such as a S/PDIF audio receiver.
We have a fix in Insider builds 16183 and later. Depending on how well this works we will consider pushing out an update to the Creators Update. from Matthew v - Microsoft Engineer
i am on 15063.250 (1703) right now so hopefully we will get this sooner then the gap to 16183 fee

[el Filou]

Microsoft Response
The Creators Update, and Windows Insider builds 14980 and later, broke "encoding Audio Processing Objects" that are used in third-party drivers to power things like Dolby Digital Live and DTS Connect, where the output of the Windows shared-mode audio engine is sent to an external decoder such as a S/PDIF audio receiver.
We have a fix in Insider builds 16183 and later. Depending on how well this works we will consider pushing out an update to the Creators Update. from Matthew v - Microsoft Engineer

What that Microsoft engineer is describing is the re-encoding in real-time of what's coming from the Windows mixer to DTS/Dolby, not the passthrough of a source DTS/Dolby bitstream.
I'm not sure waiting for this fix from MS will fix your problem.
Or are you really decoding your DTS to LPCM in LAV, and then re-encoding it with DTS Connect?

[mogli]

Btw converting floats to 32bit integers can still cause clicks for loud sounds after all this years. Recommendation in the past was to use 24bit integers instead but for my setup this means the need to do another conversion to 32bit next.

[nevcairiel]

If the audio exceeds 100%, then it can't be converted to integer without loss. Thats just how it is, and your audio file is likely bad for exceeding the valid range.

[mclingo]

What that Microsoft engineer is describing is the re-encoding in real-time of what's coming from the Windows mixer to DTS/Dolby, not the passthrough of a source DTS/Dolby bitstream.
I'm not sure waiting for this fix from MS will fix your problem.
Or are you really decoding your DTS to LPCM in LAV, and then re-encoding it with DTS Connect?


I thought that initially but if you read the thread it relates to just playback of DTS files.

DTS files play fine in the windows apps, just not in LAV filter and FFD filter apps.

If you're right than i'm not sure where to do, anyone else on creaters update have fulling working DTS-DTX - note, it might appear to be working ok but mine is summing chanels together that shouldnt be.

[max79]

Problem with LAV Audio Decoder(v0.69.0-45_Nightly_32-bit) with MP3 format. I have audio distortion with this HLS-stream:
http://wse.planeta-online.tv:1935/live/soyuz.stream/playlist.m3u8

p.s. If i use "Nero Audio Decoder 2" i didn't have such problem.

Any feedback would be appreciated.

[mogli]

What I don't get is why it only happens when converting to 32bit integers and not 16 or 24bit. It also happens when downmixing with limiting. I'm using LavFilters 32bit btw.

[max79]

Problem with LAV Audio Decoder(v0.69.0-45_Nightly_32-bit) with TrueHD+AC3 format. I have audio distortion with this file:
https://www.dropbox.com/s/8x1i95a15w24wl8/Courtesy%20of%20One%20Six%20Right%20-%20The%20Romance%20of%20Flying_%5BTrueHD%5D.thd%2Bac3?dl=0

p.s. If i use "ffdshow Audio Decoder" i didn't have such problem.

Any feedback would be appreciated.

[nevcairiel]

Problem with LAV Audio Decoder(v0.69.0-45_Nightly_32-bit) with TrueHD+AC3 format. I have audio distortion with this file:
https://www.dropbox.com/s/8x1i95a15w24wl8/Courtesy%20of%20One%20Six%20Right%20-%20The%20Romance%20of%20Flying_%5BTrueHD%5D.thd%2Bac3?dl=0

Raw files with combined ac3+thd are not actually any valid file format. Don't create them. LAV does not support them and never will.
You can't just mix two audio codecs into one stream, and expect software to figure it out. We have containers with multiple-stream support for this.

[nevcairiel]

LAV Video was already updated to the new SDK in the last couple hours to make use of the new functionality.

[thrawnrulz68]

Has anyone ever been able to get LAV Filters to play id software ROQ files or VivoActive VIVO files? They have never worked for me.

Any help would be appreciated!!!

[mclingo]

pretty sure the problems I am having with windows 10 creaters update and DTS are connected to LAV filters, if I add the FFDSHOW filters and knock off DTS from LAV formats I get full bitstreaming back in in MPC-BE and KODI.

its a ballache to have to add these filters but at least I have a workaroud now.

Recap: cant get DTS to bit stream using LAV filters and PCM is no longer outputting DTS-X height dignals.

I dont think this is purely LAV though as i went back to 68.1 and that didnt fix the problem, its a combination for LAV and creaters update I think.

Some people might not even know theres is broke, few people bit stream, fewer have DTS-X speakers setups with ceiling or heights.

Have all of you using creaters update tested your DTS setups?

[nevcairiel]

Either you bitstream, or you don't. There is no way to half-bitstream and somehow lose your height channels.
Bitstreaming still works perfectly fine for me (receiver recognizes DTS-HD MA and everything), but I don't have any DTS:X hardware, and not going to buy any. If Creators Update broke it, I suggest you complain to Microsoft and/or your graphics drivers, which control HDMI bitstreaming.

[sneaker_ger]

Has anyone ever been able to get LAV Filters to play id software ROQ files or VivoActive VIVO files? They have never worked for me.
Do they work in ffplay/ffmpeg?

[mclingo]

Either you bitstream, or you don't. There is no way to half-bitstream and somehow lose your height channels.
Bitstreaming still works perfectly fine for me (receiver recognizes DTS-HD MA and everything), but I don't have any DTS:X hardware, and not going to buy any. If Creators Update broke it, I suggest you complain to Microsoft and/or your graphics drivers, which control HDMI bitstreaming.

i never suggested I was half bit streaming, I just cant bit stream with DTS for some reason using LAV filters. I can get audio back when I turn off bit stream but for some reason i'm not getting any DTS-X height information, its getting summed to front left and right.

I've no idea if creaters update has caused this or not, I think it has as I rolled back LAV, MADVR, reclock and graphics/HDMI drivers back a few months and it didn't fix it.

[clsid]

ROQ is supported by LAV Splitter. To make playback work the RoQV mediatype {56516F52-0000-0010-8000-00AA00389B71} needs to be added to the video decoder by nevcairiel.
VIVO is only partially supported by FFmpeg. Most samples don't play.

[thrawnrulz68]

ROQ works with MPC-BE's internal splitter (ROQ Source) and decoder (ROQ Video Decoder) but it will not work with LAV Filters far as I can tell. Judging by the list of supported formats in the configuration for LAV, what clsid is saying makes sense... adding that would be great!

VIVO files are very hit or miss all around. VLC and LibreOffice claim to play them but both choke on most of them. SMPlayer fairs better but is also not quite perfect. I have not seen LAV Filters work with them at all... not sure if this is possible? Maybe a handful of files out there do work? As I understand it, most of the files are H263 and G723...

[mclingo]

think i've found the problem with windows 10 creaters update with DTS and LAV filters, its the AC3 filter, disable it and everything comes back to life, bitstreaming everything, boom.

[nevcairiel]

ROQ works with MPC-BE's internal splitter (ROQ Source) and decoder (ROQ Video Decoder) but it will not work with LAV Filters far as I can tell. Judging by the list of supported formats in the configuration for LAV, what clsid is saying makes sense... adding that would be great!

I added the RoQ Video format to LAV Video

[Aleksoid1978]

I have Windows 10 creaters update - and no any issue with AC3/E-AC3/DTS/DTS-HD/True-HD spdif/bitstream hdmi output.

[mclingo]

I have Windows 10 creaters update - and no any issue with AC3/E-AC3/DTS/DTS-HD/True-HD spdif/bitstream hdmi output.

Do you have ATMOS height or ceiling speakers, does you AMP display the decoder information on the screen?

[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.
Does LAV send the 3D eye views as separate images in a standardised form that can be interpreted by subsequent directshow filters as regular video, such as 1920x1080 48fps interleaved, or does any following filter need to be written specially to interpret the incoming data?

I have tried connecting LAV Video Decoder to Ffdshow Raw Video filter, but it doesn't seem to interpret 3D as anything other than 1920x1080 24fps video.

Are there any other readily available directshow filters that can take the 3D output from LAV and simply interleave or even just stack it into a 1920x2160 window for display on a 4k passive 3D TV?

[nevcairiel]

Its a special format for 3D videos that contains both views separately, and a filter would have to be specifically adapted to support it. Nothing like that exists.

[IanD]

Its a special format for 3D videos that contains both views separately, and a filter would have to be specifically adapted to support it. Nothing like that exists.

Unfortunate, but thanks for confirming that situation.

On a separate issue, I have noticed that LAV Video Decoder has undefeatable dithering with only the option to select ordered or random. Since MadVR has its own more advanced options for dithering, is it possible to disable LAV's dithering as I wouldn't think dithering an already dithered source would be desirable?

[huhn]

lavfilter output is bit perfect if possible.
if that is not the case and bit perfect output is impossible than it may use dither for conversation.

dithering is for example used in RGB output with YCbCr source but as long as you are not outputting RGB with lavfilter it is not doing that.

[thrawnrulz68]

I added the RoQ Video format to LAV Video

Thanks!!

Is this in the nightly version 0.69.0-71? I don't see RoQ in the Video Decoder configuration for that version

[LigH]

Because it is mainly a container format. The contained video appears to be similar to MotionJPEG (https://wiki.multimedia.cx/index.php/RoQ#0x1012_-_RoQ_JPEG).

[nevcairiel]

Thanks!!

Is this in the nightly version 0.69.0-71? I don't see RoQ in the Video Decoder configuration for that version

Not every minor format got a option, which means you just can't turn it off, but it still works.

[nevcairiel]

On a separate issue, I have noticed that LAV Video Decoder has undefeatable dithering with only the option to select ordered or random. Since MadVR has its own more advanced options for dithering, is it possible to disable LAV's dithering as I wouldn't think dithering an already dithered source would be desirable?

As huhn already said, LAV Video only dithers when it needs to, if it wouldn't that would deteriorate quality.

If you use madVR and don't mess with LAVs output format settings, then it'll generally never dither, since it can output bit-exact images.

[IanD]

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.

If output display mode is 4k, MadVR still only creates a 1920x1080 window containing 3D information (structured as SBS, Top/Bottom or Line Interleaved). When this window is enlarged to full screen, I suspect it is simply scaling the 1920x1080 window to 3840x2160 because the 3D image looks a bit soft and especially in Line Interleaved mode it pains the eyes to look at (presumably because the independent left and right eye views have now been scaled to cross both polariser strips on the display).

If you want to be pedantic, sending 1920x2160 (line interleaved 3D) to a window on the display will not provide the proper aspect ratio and retain the 3D nature of the source, but then neither does sending 3840x2160 because the window frame makes scaling necessary which undoes the line interleaved 3D registration anyway. The only way to properly view such 3D is in fullscreen mode. I have only mentioned 1920x2160 because that is the bound of the data when you interleave the left and right eye 1920x1080 views.

If you could see your way to providing a 4k 3D option that simply interleaves the unmodified left and right eye views (or stacks them horizontally or vertically depending on output mode) and utilises fullscreen scaling to create the proper aspect ratio, those of us with 4k passive 3D displays would be appreciative. Since processing is minimal, it should also lower display render times.

[thrawnrulz68]

Hey nevcairiel,

I've been looking through the list of supported types in the splitter and testing some file types located at the ffmpeg archive. I've been having trouble getting the following types to play:

Yamaha SMAF - http://samples.ffmpeg.org/A-codecs/suite/MMF/ - will not play; is listed in LAV splitter

Also, the following types appear to be working in the splitter but, like ROQ before it was fixed, they all seem to have a standard codec that is used which is NOT supported in LAV:

Microsoft XMV - http://samples.ffmpeg.org/game-formats/xmv/ - the audio plays but the video codec for all the files has the FOURCC of 2VMW which will not play.
Commodore CDXL Video - http://samples.ffmpeg.org/game-formats/cdxl/ - audio plays but the CDXL video does not. Is it possible to add support?
Wing Commander III Movie - http://samples.ffmpeg.org/game-formats/wc3-mve/ - audio plays but FOURCC WC3V does not appear to be supported.

Is it possible to add these?

[max79]

to nevcairiel:
Problem with LAV Splitter Source. I have error message: E_FAIL (0x80004005) in GraphEdit if playback this MP3-file that have built in chapters(like in .CUE-files) as live-stream:
http://www.electromixes.com/zik/electromix_v118.mp3

p.s. If i use "FileSource(URL)+LAVSpltter" i didn't have such problem.

Any feedback would be appreciated.

[Artofeel]

Its a special format for 3D videos that contains both views separately, and a filter would have to be specifically adapted to support it. Nothing like that exists.
so that why I can't play 3D with LAV in Stereoscopic Player?
it expects two streams, but LAV gives one...

https://forum.doom9.org/attachment.php?attachmentid=15891&stc=1&d=1495189030

can you just split it in two streams? Option maybe?

also there is no 3D at all in new versions (from LAVFilters-0.69-45-av1_test30-git-r3851)

LAVFilters-0.69-av1_test15-git-r3806(42b9649)
https://forum.doom9.org/attachment.php?attachmentid=15892&stc=1&d=1495191044

LAVFilters-0.69-76-av1_test31-git-r3882(f72d508)
https://forum.doom9.org/attachment.php?attachmentid=15893&stc=1&d=1495191068

[nevcairiel]

I do not plan to offer alternate 3D transport modes, using 2 streams is inherently inferior since it requires manual synchronization, instead of just getting both views in one stream. Also, I cannot offer any support for modified custom builds.

[amayra]

I do not plan to offer alternate 3D transport modes, using 2 streams is inherently inferior since it requires manual synchronization, instead of just getting both views in one stream. Also, I cannot offer any support for modified custom builds.
since we are talking about modified custom builds "tmod" Is there any particular reason why you didn't use it this as patch/pull for vanilla builds ?

[nevcairiel]

since we are talking about modified custom builds "tmod" Is there any particular reason why you didn't use it this as patch/pull for vanilla builds ?

I can only review or comment on patches if they are submitted to me.
I'm not spending my little time on trolling the web for any changes someone made without the slightest attempt of submitting them to me.

But since you mentioned this set specifically I looked it up, and not one of the patches in there is something I would apply without serious questioning.

[Budtz]

I an using latest nightly.

In hdr files using cuvid madvr says unknown properties with reagrd to hdr. With dxva it corectly converts the content.

[nevcairiel]

I an using latest nightly.

In hdr files using cuvid madvr says unknown properties with reagrd to hdr. With dxva it corectly converts the content.

You just answered your own question, didnt you? Use DXVA.
CUVID doesn't support a bunch of things, including HDR metadata, and thats unlikely to change, since the NVIDIA API doesn't export that data.

I have said this in the past - DXVA2 Copy-Back should generally be preferred over CUVID.

[Artofeel]

I do not plan to offer alternate 3D transport modes, using 2 streams is inherently inferior since it requires manual synchronization, instead of just getting both views in one stream
fine then
anyway what this format IS, name? it's not field\frame separated, so then how?
and it's normal that LAV doesn't play Subset MVC (MEDIASUBTYPE_EMVC) ?
it's listed here but it's not working
https://github.com/Nevcairiel/LAVFilters/blob/master/common/includes/moreuuids.h
*using latest nightly build

[nevcairiel]

The format doesn't have any particular descriptive name. Its something simple and effective which madshi and myself designed last year for 3D image transport. If anyone wanted to support it, the technical descriptions are publicly available in LAVs repository.

LAV Video requires the MVC stream to be interleaved, like LAV Splitter outputs it as well. So no, that subset format is not supported (and also will not be, since its inherently more complex and a bit pointless).

[Warlock]

Is anyone having problems with nightly versions? Kaspersky is deleting all versions of https://files.1f0.de/lavf/nightly/, it is considering all of them as virus UDS.DangerousObject.Multi.Generic. I downloaded the official version of github, which it normally accepts, but the versions posted at https://files.1f0.de/lavf/nightly/ it deletes immediately. Is it some false positive or some other problem?

[ryrynz]

Will be a false positive. Best you submit a report and add whatever it detects to your trust list. You won't ever have to worry about infections from Nevcairiel's host.

[nevcairiel]

You can always check with eg. VirusTotal: https://www.virustotal.com/en/file/96b5cb89201bc01f4ff0d1835aac2b9b0e491f10e72f9cfafdf233e421315d68/analysis/1495352742/
If only one or two of 60 solutions find something, its often a false-positive from a heuristic match - especially when its called "generic" or something.

[Warlock]

Will be a false positive. Best you submit a report and add whatever it detects to your trust list. You won't ever have to worry about infections from Nevcairiel's host.

:thanks:

You can always check with eg. VirusTotal: https://www.virustotal.com/en/file/96b5cb89201bc01f4ff0d1835aac2b9b0e491f10e72f9cfafdf233e421315d68/analysis/1495352742/
If only one or two of 60 solutions find something, its often a false-positive from a heuristic match - especially when its called "generic" or something.

Got it, no problem. The most interesting is that it has no problems with the normal version, LAV 0.69 (https://www.virustotal.com/pt/file/ca247ddea684e5000647b20cfeb0e91eb83b91faed14e15add07750f515369a6/analysis/1495370695/), it passes 100%. Checking the kaspersky logs, it is deleting the test versions because of two files: unins000.exe and a temp file called LAVFilters-0.69.0.7x.tmp, because of these two files, it deletes any of the test versions . In the normal version, these 2 files pass smoothly, they consider them safe, does it be because of some different information between the files is causing the false positive?

[NikosD]

New (?) DXVA specs for known codecs flavors:

DirectX Video Acceleration Specification for H.264/MPEG-4 AVC Multiview Video Coding (MVC), Including the Stereo High Profile
https://www.microsoft.com/en-us/download/details.aspx?id=25200

DirectX® Video Acceleration Specification for Windows Media Video® v8, v9 and vA Decoding (Including SMPTE 421M "VC-1")
https://www.microsoft.com/en-us/download/details.aspx?id=25228

[RealSnoopyDog]

I tested two nightlies: 0.69.0-43 and 0.69.0-73. Everything seems to work fine except that i can not playback Blu-Rays anymore using the DLLs libaacs.dll and libbdplus.dll. When media playback should start it says "Can not render Video/Output pin, error: 0x80004005 unknown error".

With the last official LAV release 0.69 this still works.

[nevcairiel]

Try again with -80, it may also depend where you put those DLLs. In the directory where the players executable is should probably work best.

[Mark Regalo]

Why is there an audible difference between "Don't mix Stereo sources" enabled and disabled when the input is stereo and output is 5.1? What is being downmixed? The output is still stereo AFAIK but the sound is quieter when "Don't mix Stereo sources" is disabled.

[nevcairiel]

Why would it have to be downmixed for that option to do something? With the option on, stereo is output as stereo, with the option off, its output as 5.1, certainly there can be an audible difference between those two depending on how your audio device handles this.