LAV Filters - DirectShow Media Splitter and Decoders

[Warlock]

Originally Posted by wanezhiling

@Warlock
http://forum.doom9.org/showpost.php?...34&postcount=6
http://forum.doom9.org/showpost.php?...ostcount=15088

Thanks, my question was completely solved.

[Mercury_22]

How to use the new RTMP ?
Something like rtmp://npsaflivefs.fplive.net:1935/npsaflive-live/stream50 it's working fine with LAV in MPC-BE BUT how do I play this

rtmp://62.115.64.212/live?_fcs_vhost=cp116697.live.edgefcs.net playpath=BnazlkNDpCIcD-QkfyZCQKlRiiFnVa5I_640_360_1000@18679 pageUrl=http://www.bloomberg.com/tv/ app=live?_fcs_vhost=cp116697.live.edgefcs.net swfUrl=http://player.ooyala.com/static/cacheable/6086bd175c4cf1d14cbd4c9aa54d019d/player_v2.swf/[[DYNAMIC]]/3 swfVfy=true live=true timeout=60

which is playing OK in XBMC as a strm file

[nevcairiel]

There is no rtmp support in LAV, and even if someone enables it in the ffmpeg build, there is no official support for it, so you figure it out.

So if anyone wants to write a parser for such URLs and pass all the appropriate settings to ffmpeg, then i can add it.

[zerowalker]

Will VP9 be added?
As if i am correct, the bitstream is frozen, making a decoder that works now, works forever.

[Mercury_22]

Originally Posted by nevcairiel

There is no rtmp support in LAV, and even if someone enables it in the ffmpeg build, there is no official support for it, so you figure it out.

So if anyone wants to write a parser for such URLs and pass all the appropriate settings to ffmpeg, then i can add it.

Looks like "Someone" has remove it now It was in the git earlier today

[clsid]

Edit: it seems that FFmpeg is not able to parse the parameters given after the rtmp:// URL. The calling app need to parse them and pass them to the demuxer as options (see rtmpproto.c).

[nevcairiel]

Originally Posted by Mercury_22

Looks like "Someone" has remove it now It was in the git earlier today

I accidentally pushed a test branch, it was up for maybe 5 minutes or so, and if you had read the commit message that came with it, it would've explained that anyone testing this is on their own.

[kasper93]

@clsid @Mercury_22

LAV doesn't support rtmp so it's pointless to discuss how to pass additional parameters. RTMP support can be easily enabled by changing ffmpeg build script, but this only support simple streams. Basically only those which can be described by singe link

rtmp://server[:port][/app][/instance][/playpath]

[ryrynz]

Has anyone else experienced random glitches with what I assume is avcodec decoding? Sometimes I'll have a small square patch that displays properly while the rest of the video freezes.
It happens on both my PCs, if you rewind and replay that particular sequence there is no problems, completely random.

[dukey]

nevcairiel, does lav correctly set the average time per frame on dynamic format change ?
http://i.imgur.com/87xfqHu.png

[nevcairiel]

You should never really rely on that value, its notoriously inaccurate.
But sure, when the source sends a new time, it should end up at LAVs output as well. Unless of course its one of those cases where LAV decides to override it with a bitstream value.

[dukey]

It seems not to propagate the value, and if it has overridden it, then it's done so incorrectly I think.

[nevcairiel]

Like i said, simply don't rely on it, its unreliable.

[dukey]

I need it to properly create a dxva type, otherwise I have to guess some default rate

[nevcairiel]

LAV Filters 0.58

General
- LAV Filters now includes a manifest file to control DLL loading
- Fixed the shortcuts to the configuration dialogs created by the installer in the start menu

LAV Splitter
- Handle the "Default" flag in MKV files with multiple video streams
- Fixed a regression in VC-1 demuxing which caused some streams to fail decoding with the WMV9 DMO decoder
- Improved transition between ordered chapters in certain (badly formed) MKV files
- Improved handling of AVC1 in AVI files
- Improved accuracy of IAMStreamSelect::get_CurrentMarker
- Several potential crash fixes and stability improvements

LAV Video
- YADIF deinterlacing is now multi-threaded, significant performance improvement on multi-core CPUs
- Improved detection of progressive streams to ensure deinterlacing is disabled, especially when "Aggressive Deinterlacing" is used
- Restored Fraps constant frame rate output by proper handling of repeated frames
- Support for the new UtVideo sub-types, and fixed a regression in UtVideo decoding
- cuvid: fix double-rate deinterlacing on certain streams without timing information
- Updated the Intel QuickSync Decoder to 0.44

Download: Installer (both x86/x64) -- Zips: 32-bit & 64-bit

This message has been reduced in length due to heat.

Standard disclaimer applies, report regressions/issues, include samples, because without reproducing a bug, no fixing a bug.

So, take care, and enjoy the summer while it lasts - well, if the summer reached you yet.

[Qaq]

Thanks for the new version.
And yes, its hot on Baltic sea these days.

[DragonQ]

Heh, I'm wearing a jumper indoors!

Thanks for the new release. Would you care to expand a bit on the "Improved detection of progressive streams to ensure deinterlacing is disabled, especially when "Aggressive Deinterlacing" is used" fix?

[nevcairiel]

It does what it says, it improves the detection of 100% progressive streams to ensure deinterlacing is turned off.
Previously it would rely on the media type information for this, but when watching Live TV for example, there typically is no such information available, and it could deinterlace some progressive broadcasts which didn't need it - and even cause some issues when double-rate deinterlacing a stream which already was 59.94 progressive (as i'm told some ATSC broadcasts in the US are)

[DragonQ]

I see. I assume it's not based on looking at the actual frame images though?

[nevcairiel]

No. Just the info in the bitstream.