Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
30th November 2012, 11:44 | #13201 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
I hope you updated LAV in MC properly, in its plugins folder? Otherwise the version mismatch of its integrated plugin and any stand-alone installed versions can easily result in crashes.
What kind of video? Everything? Anything special? The only changes between 0.53.2 and 0.54.1 are either DVD or DXVA related, nothing much else. Do you use DXVA?
__________________
LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 30th November 2012 at 11:52. |
30th November 2012, 11:57 | #13202 | Link | |
Registered User
Join Date: Aug 2005
Posts: 231
|
Quote:
Only tried regular DVB-T SD H.264 channels, using DXVA copy-back/native. It'll almost always crash after a while. I'll keep using 0.53.2 and post back if it crashes, too. |
|
30th November 2012, 12:04 | #13203 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
It plays fine, and then without doing anything it would suddenly crash?
In Live TV only, in MC18 too? Or also file playback?
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
30th November 2012, 22:24 | #13207 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
The first Intel with DXVA was the G35/G965 chipset, plenty old.
Anything before Sandy Bridge only supports Intels special "ClearVideo" mode (except possibly for MPEG-2). Sandy Bridge and above add support for standard H.264 DXVA, but not for VC-1 (VC-1 only runs through QuickSync)
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
1st December 2012, 12:59 | #13208 | Link |
Registered User
Join Date: Apr 2011
Posts: 1,184
|
About ClearVideo and QuickSync, you could click the link:http://en.wikipedia.org/wiki/Compari...fth_generation
Note1: All Clarkdale and above GPUs support QuickSync decoding, Celeron and Pentium just dont support QuickSync encoding. Note2: Egur's QuickSync decoder blocked Clarkdale, so you need a SNB CPU @ least. About DXVA, click the link above again.http://en.wikipedia.org/wiki/Compari...ocessing_units Start from G33(third generation), MPEG2 has been fully supported, but no H.264 and VC-1. Start from G45(fourth generation), H.264 and VC-1 are fully supported too, which is a "milestone" for Intel HD technology. Note: Clarkdale/SNB/IVB(fifth/sixth/seventh generation) GPUs' VC-1 is a bit strange. Only CyberLink and ArcSoft have access to VC-1_VLD(full acceleration), other players/decoders stay VC-1_IDCT(partial acceleration). Last edited by wanezhiling; 1st December 2012 at 13:02. |
1st December 2012, 13:30 | #13209 | Link |
Registered User
Join Date: Mar 2012
Posts: 38
|
Guys, how dxva native has incompatibility problem with the xy-VSFilter? I did a test, every time I select the dxva native mode, I open any video, falls in software mode. The only format that works in dxva native when the xy-VSFilter is enabled, it is .MP4. I turned off the xy-VSFilter and activated the subtitle renderer of mpc-hc. After that, all videos began to be recognized by the dxva native mode, with the exception of 10-bit videos. How can I solve this problem between dxva native and xy-VSFilter?
|
1st December 2012, 13:52 | #13210 | Link | |
契約者
Join Date: Jun 2008
Posts: 1,576
|
Quote:
Last edited by Keiyakusha; 1st December 2012 at 13:54. |
|
1st December 2012, 14:17 | #13211 | Link |
Registered User
Join Date: Sep 2006
Posts: 212
|
Win 7 64 bit, Zoom Player
nev, seemed to have stumbled upon a bug using LAV Splitter 54.1 where certain widescreen .mp4 or .m4v/avc vids don't display properly as they should (in widescreen format) but instead as a square fullscreen. Using a different mp4 splitter such as AVSplitter fixes the problem so can only assume the problem is with LAV Splitter. I went back four or five LAV versions to see if the problem persisted and it did so it seems this is not a new problem. Sample link: http://filestay.com/p1ercgk44qcx/mp4_displays_in_fullscreen.m4v.html |
1st December 2012, 14:58 | #13212 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
The file is working as intended, its just muxed wrong.
The MP4 file specifies a AR of 3:2, and the H264 stream an AR of 16:9. Which should be used for playback? LAV Splitter will always output the 3:2 AR, because its a splitter, it reads the container values, not the stream values. LAV Video (by default) trusts the AR from the Splitter in MP4 files, because most people do the muxing correct and the encoding wrong. The muxed value is also easier to fix then the encoded value in the video stream. There is an option to control how Stream AR is handled in the LAV Video options if you don't like it behaving correctly. PS: Please use better file hosts, that page is just horrible. Took about 5 minutes until the download started, and took like 40 minutes to download that 67mb file. Whats wrong with mediafire?
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
1st December 2012, 16:38 | #13214 | Link |
契約者
Join Date: Jun 2008
Posts: 1,576
|
Never understood why container AR should take preference. The option to chose between them should be of course, as you not always can fix already broken files. But default should read stream info only. User should be forced to do one of the following: a) fix the existing stream b) reencode stream with correct settings c) temporarily change setting in LAV to read container ar d) temporarily redefine ar in player's playback settings
Plenty of options! And by using container AR they'll just never learn how to produce correct files. User should see that what they did is not correct. There is no way to make a warning in x264 or something as it have no idea what ar should be in which situation. Personally I always use ar info only. BTW half-checked ar setting in LAV decoder fails with this file. But obviously works with reading ar from stream. There is no more correct way to produce this file, so why should broken files work and normal not? Last edited by Keiyakusha; 1st December 2012 at 16:45. |
1st December 2012, 16:44 | #13215 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
It doesn't "fail", you just produced a broken file, with conflicting information. In my experience (from users complaining and files i have seen), its far more common for the container AR to either: not be set at all (which is fine, and stream AR is used), or the container AR be set correctly, sometimes with a non-existant or broken stream AR, and the users expect it to be used for playback. Note that this only applies to MKV and MP4.
Using the container AR is perfectly valid, because not all video formats even have a stream AR. If you think anything else is better, the option lets you configure it however you want. Quote:
There have been plenty complains to other decoder authors for not adding an option to ignore stream AR, because they didn't want it to be used.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 1st December 2012 at 16:46. |
|
1st December 2012, 16:47 | #13216 | Link | ||
Registered User
Join Date: Dec 2002
Posts: 5,565
|
Quote:
Quote:
Last edited by sneaker_ger; 1st December 2012 at 16:49. |
||
1st December 2012, 16:50 | #13217 | Link | |||
契約者
Join Date: Jun 2008
Posts: 1,576
|
Quote:
Quote:
Quote:
Resolution is constant, ar is different. It doesn't needs to be supported. ar info exists in stream, martoska ar perfectly fine to be used as fallback. Last edited by Keiyakusha; 1st December 2012 at 16:57. |
|||
1st December 2012, 16:54 | #13218 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
It doesn't matter what you think is the correct way to produce files anyway. The defaults in LAV are choosen to be correct with as many files as possible, based on empirecal evidence based on user complaints and sample files i gathered over the years. A correctly encoded and muxed file would usually work, broken in any direction needs some kind of compromise.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
1st December 2012, 16:58 | #13219 | Link | |
Registered User
Join Date: Dec 2002
Posts: 5,565
|
Quote:
Your solution: LAV uses bitstream AR by default and people will make files without using the correct container AR Whatever LAV does, people will produce broken files. And who is to define that bitstream AR takes preference over container AR anyways? |
|
1st December 2012, 17:01 | #13220 | Link | |
契約者
Join Date: Jun 2008
Posts: 1,576
|
Quote:
There is no way to produce incorrect container ar unless you explicitly set it incorrectly. These users just need to RTFM. On the other hand by not setting stream ar it produces incorrect result. Last edited by Keiyakusha; 1st December 2012 at 17:03. |
|
Tags |
decoders, directshow, filters, splitter |
Thread Tools | Search this Thread |
Display Modes | |
|
|