LAV Filters - DirectShow Media Splitter and Decoders

[nevcairiel]

I already told you that I'm not very interested in streaming stuff. Streaming is delivered "as is", either it works or it doesn't. If something doesn't work, test with and report to ffmpeg.

[LigH]

Originally Posted by max79

FONT="Comic Sans MS"

Somehow I am biased...

[max79]

Originally Posted by nevcairiel

I already told you that I'm not very interested in streaming stuff...

Okey. But through LAV Splitter_v0.69 i can see built in CUE marks(Chapters) for MP3 remote files(from my SR#15) and now in v0.70(and newer) it's broken, you did not answer why it happened...
And my SR#27 was about local file playback. You did not answer too.

[clsid]

Originally Posted by max79

Problems with "LAVSplitter" & "LAVSource". Seeking didn't work for .DTSMA & .MLP-files and appear wrong mediafile duration[00:00:00] for that reason seeking is impossible. Examples:
https://www.dropbox.com/s/1mevg3htmr...Hz%5D.mlp?dl=0
https://www.dropbox.com/s/yh6ly2jw0k...%5D.dtsma?dl=0
Any feedback would be appreciated.

Raw audio and video files do not have a known duration, and hence seeking will not work. You need to put it into a container format if you want seeking. Duration can only be determined (accurately) by parsing the whole file.

[max79]

Originally Posted by clsid

Raw audio and video files do not have a known duration, and hence seeking will not work. You need to put it into a container format if you want seeking. Duration can only be determined (accurately) by parsing the whole file.

Thanks again for quick response clsid. But you are wrong! Through other filters duration shows and seeking works too. Have a look:
https://forum.doom9.org/attachment.p...1&d=1499469771
https://forum.doom9.org/attachment.p...1&d=1499469744

[nevcairiel]

He is not wrong. raw vbr audio files have no duration information and you need to read the entire file from start to finish to figure it out, and LAV/ffmpeg does not do this (and will likely not start doing this, either).

[LigH]

VBR MP3 may have an additional non-audio frame with per-frame bitrate statistics (e.g. "Xing VBR frame").

Or not. Then the decoder would have to scan the whole file and build such statistics before playing.

Anyway, no decoder is forced to care about non-audio frames.

[P.J]

Originally Posted by huhn

it is technically not possible to deinterlance a 4:2:0 source that is transformed to RGB the image is scaled vertical so it can't be deinterlanced anymore. (well there is a very a technically way to do that but... complicated and unnecessary)

so RGB deinterlancing support is just bad.

if EVR-CP can handle 4:2:2 correct you should report this to MPC-HC/BE.
EVR normal has nothing to do with that.

you can force 4:2:0 by disabling everything that is not 4:2:0

The source is 4:2:2 and the problem happens with both EVR/EVR-CP
Also deinterlacing doesn't work correctly when forcing 4:2:2 to play in NV12/YV12 mode, ghost colors...

[huhn]

when EVR CP is creating such artifacts you should contact the MPC-BE MPC-HC team. there is no need to use NN on chroma.

edit:
i got the chroma sub sampling wrong 4:2:2 is half horizontal not half vertical. you can't scale it to 4:2:0 because you can't scale an interlanced image vertical without "deinterlancing" it before.

[VictorLS]

Due to Aleksoid1978 I get hardware acceleration of h265 10bit via NVIDIA CUVID again - diff for 0.70.2.1-git https://yadi.sk/d/9xRWsX343KyoFB - and he said: "in WinXP CUVID not supported P016 output (even for HEVC 10/12bit)".
nevcairiel, before you stop support WinXP can you spend some minutes of coding LAV Video Decoder to force NV12 output in case of decoding h265 10bit via NVIDIA CUVID in WinXP like it done in diff in future releases of LAV Filters?

[TheShadowRunner]

nev did you implement TrackSet/TrackSetEx or am I dreaming!?

[nevcairiel]

There is no support for this, and unlikely to ever be.

[TheShadowRunner]

I'm confused as hell, using LAVSplitter in the graph for certain and getting this:
http://videoff7.free.fr/lav_editions.jpg
Going to explore how it's done..

[nevcairiel]

Editions have been supported for a couple years now. But thats unrelated to TrackSets.

[TheShadowRunner]

Oh right, bad memory on my end. What's not possible with Editions is to pre-define which given audio/sub tracks should be used.

[hubblec4]

Originally Posted by TheShadowRunner

nev did you implement TrackSet/TrackSetEx or am I dreaming!?

The TrackSet/TrackSetEx functionality is a Haali-Splitter feature and not a Matroska feature.
It is not possible to build a TrackSetEx with the Matroska-Elements.
Only with multiple editions and the ChapterTrackNumber(s) you could have a kind of TrackSetEx, but if you change the edition(to change the Tracks) always the movie start from beginning.

I would say, TrackSetEx are easy to implement. Its only a Tag like the edition-tags. LAV-Splitter could read this "new Tag".
All editions are shown in the TrayIcon-menu and now here could shown the TrackSetEx also.

When I change an audio or subtitle track, I make a click on the new track and LAV change it for me. Why can't LAV change two things at the same time.
A click on a "TrackSetEx" change first the audio and then the subtitle track.

[DragonQ]

Originally Posted by VictorLS

Due to Aleksoid1978 I get hardware acceleration of h265 10bit via NVIDIA CUVID again - diff for 0.70.2.1-git https://yadi.sk/d/9xRWsX343KyoFB - and he said: "in WinXP CUVID not supported P016 output (even for HEVC 10/12bit)".
nevcairiel, before you stop support WinXP can you spend some minutes of coding LAV Video Decoder to force NV12 output in case of decoding h265 10bit via NVIDIA CUVID in WinXP like it done in diff in future releases of LAV Filters?

You know you can submit a pull request in GitHub, right?

I don't think nev is planning to "stop" Windows XP support, I'm pretty sure he stopped supporting it years ago (as did Microsoft).

[VictorLS]

Originally Posted by DragonQ

You know you can submit a pull request in GitHub, right?

I don't know why nevcairiel don't want spend about 5 minutes to add h265 10bit hardware acceleration via CUVID in WinXP by implementing 100% working code in LAV Filters https://github.com/Nevcairiel/LAVFilters/issues/145 and then officially stop WinXP support in LAV Filters. All people using WinXP (I often see here in the bottom of posts too) will know i.e. 0.70.3 is last fully functional in WinXP version of LAV Filters and if they have (or buy) GM206-based videocard h265 10bit hardware acceleration via CUVID must work in their old sweet WinXP. I believe that's right.
PS. May be nevcairiel affraid National Security Agency (NSA) prohibit using WinXP to easier watch for people all over the world?

[fijam]

Is the development of LAV Filters going to be impacted by MPC-HC ceasing development?

[LigH]

LAV filters can also be used via DirectShow API (which is used in MPC-HC when you disable internal decoders and splitters), in case LAV Filters might become incompatible to an older build of MPC-HC as substitute for internal filters.