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. |
11th December 2015, 02:22 | #4861 | Link | |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
I have a strange issue with MPC-HC (64-bit) 1.7.10 (d911f14). It seems to apply a kind of automatic de-shaker filter to every video played. They are all surrounded by a black border which seems to get adapted to moving content (shrinks sometimes when letterboxes are included). It is especially obvious when you have slightly shaking footage with a logo in a corner, then you can see how the image is stabilized but the logo is shaking, half covered by the border.
What may that be? How can I disable that? I don't think I have such a filter installed, it seems to appear in MPC-HC with internal LAV Filters only (but I am not aware that they implement such a feature), not in e.g. GraphStudioNext rendering a media file (this uses MS DTV-DVD filters for decoding because there are no other DirectShow filters installed yet). Technical info: Code:
MPC-HC (64-bit) --------------- Build information: Version: 1.7.10 (d911f14) Compiler: MSVC 2013 Update 5 Build date: Nov 14 2015 18:25:24 LAV Filters: LAV Splitter: 0.66.0.0 LAV Video: 0.66.0.0 LAV Audio: 0.66.0.0 FFmpeg compiler: MinGW-w64 GCC 4.9.2 Operating system: Name: Windows NT 6.1 (build 7601, Service Pack 1) Version: 6.1 (64-bit) Hardware: CPU: AMD A4-4000 APU with Radeon(tm) HD Graphics GPU: AMD Radeon HD 7480D (driver version: 8.17.10.1116) Quote:
Oh, heck, it helps writing about it... It's not a feature of MPC-HC. It's not a feature of LAV Filters either. It's a feature of AMD, called "Steady Video". I hate AMD Catalyst drivers. They are full of ghosts you never intended to call. Last edited by LigH; 11th December 2015 at 02:26. |
|
15th December 2015, 14:54 | #4863 | Link | |
Registered User
Join Date: Dec 2010
Posts: 22
|
Quote:
The easiest way to support this is probably through x264 as it can load timecode files directly via --tcfile-in as long as the output format also supports vfr (use internal mp4/mkv muxer, optionally use external muxer after if for some reason the external muxers are preferred). Another method I know of is here http://forum.doom9.org/showthread.php?t=112199 EDIT: To address 1) FFVideoSource can output the timecodes from the file being read https://github.com/FFMS/ffms2/blob/m...s2-avisynth.md Last edited by ravewulf; 19th December 2015 at 06:31. Reason: Added additional information |
|
18th December 2015, 02:53 | #4869 | Link |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,890
|
Yep, Aften is discontinued, the same developper make the ffmpeg AC3 encoder (libav) improving stereo encode and other parts.
http://forum.doom9.org/showthread.ph...77#post1522077
__________________
BeHappy, AviSynth audio transcoder. |
19th December 2015, 18:55 | #4872 | Link | |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Quote:
Thanks, one of the update server was out of sync. |
|
23rd December 2015, 13:09 | #4873 | Link |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
The newer FFM2 plugin versions seem to require a recent AviSynth version. At least it does not work with 2.5.8 but it does work with 2.6
I am unsure which way to go. I could block all AviSynth versions which are not using the recent interface version and use the portable AviSynth instead. Or I can print out only a error message and continue with the old way. Both ways have pros and cons. Which would you prefer? |
24th December 2015, 11:45 | #4874 | Link | |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,890
|
Quote:
I prefer "use the portable AviSynth instead" for me.
__________________
BeHappy, AviSynth audio transcoder. |
|
25th December 2015, 14:50 | #4875 | Link |
Registered User
Join Date: Feb 2007
Location: Sweden
Posts: 480
|
"always use the included AviSynth" is what i use.
FFmpeg v2.8.4 is out http://ffmpeg.zeranoe.com/builds/win32/static/ |
26th December 2015, 16:18 | #4876 | Link |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Ok, I will emplement it in the way that I update the AviSynthWrapper to the recent interface version (currently 2, will be 6). With this new DLL no old AviSynth versions can be accessed. During startup of MeGUIthis will be checked and if necessary a fallback to the portable AviSynth will be done.
After this change it is not possible to use MeGUI with older AviSynth versions (replacing the DLL is the only way). |
28th December 2015, 05:22 | #4877 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
I found myself explaining to someone again today, why an anamorphic option called "Encode non-mod16" lets you encode mod16.
I still think a rename might be in order. "Encode any-mod" would work. Anamorphic "strict" as Handbrake calls it seems pretty succinct. Not to mention accurate..... |
28th December 2015, 13:51 | #4878 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
I'm using an anamorphic DVD encode to illustrate the problem. It's an MKV. I open and index it. The script creator looks like this:
Problem #1. The display aspect ratio of the source video isn't in the drop down list. So if I change it, I can't change it back, unless.... Problem #2: I create a custom aspect ratio in which case the source aspect ratio will be automatically be listed, so as long as I remember to create a custom aspect ratio first, I'm fine. Until...... Problem #3. I don't want to use the custom aspect ratio any longer and wish to delete it, but I can't unless I delete all the custom aspect ratios. Happy New Year everyone. Especially Zathor. PS. I still think it's time for MeGUI to switch from using the old ITU pixel aspect ratios for DVDs to the MPEG4 pixel aspect ratios. Because..... - They're easier to remember. - The display aspect ratios for NTSC and PAL are exactly the same, so there's only two display aspect ratios in total. - They're included in the list of pixel aspect ratios in the x264 encoder configuration. The ITU PARs aren't. - If you use --bluray-compat in the command line MeGUI (or the x264 encoder) automatically changes the ITU PARs to MPEG4 PARs. - It keeps everything more consistent. - Depending on the setting in preferences, MeGUI will choose either an ITU or generic display aspect ratios for NTSC or PAL Bluray video. I'm pretty sure both would technically be wrong. - It's 2016 (give or take a day or so). Last edited by hello_hello; 28th December 2015 at 14:36. |
28th December 2015, 14:01 | #4879 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
One more pixel aspect ratio related question. The mpeg4 and generic pixel aspect ratios are:
MPEG4: Code:
PAL NTSC 4:3 12:11 10:11 16:9 16:11 40:33 Code:
PAL NTSC 4:3 16:15 8:9 16:9 64:45 32:27 Not that it really matters, aside from the fact that once I noticed I realised I'll probably never sleep well again until I know why. Last edited by hello_hello; 28th December 2015 at 14:18. |
28th December 2015, 16:18 | #4880 | Link |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Code:
2627 [Main] detects during startup if AviSynth can be used automatic fallback to the portable AviSynth 2626 [AvisynthWrapper] updated to recent avisynth.h (requires AviSynth 2.6) improved error handling added x64 support 2625 [Flac Encoder] fixed always using compression level 0 (regression of 2536) EDIT: A positive effect is that due to the improved error handler AviSynth should not be able to crash MeGUI anymore (like with FFM2 and fast cropping). EDIT2: With hello_hello in mind I have compiled the wrapper also for XP. I hope it works :-) Last edited by Zathor; 28th December 2015 at 17:54. |
Thread Tools | Search this Thread |
Display Modes | |
|
|