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. |
25th March 2007, 15:24 | #881 | Link | |||
Registered User
Join Date: Nov 2006
Posts: 799
|
Quote:
Quote:
Quote:
|
|||
25th March 2007, 15:42 | #882 | Link |
Registered User
Join Date: Feb 2006
Location: Japan
Posts: 1,560
|
Well, just install a build using MSVC8, remove ffdshow.ax.manifext and launch the dialog, you'll find Xp visual style is gone even though ffdshow.ax have a proper embedded manifest as a resource. I think it's a bug of Xp. The manifest loading CRT is processed properly in Xp without external manifest. So Xp requires both embedded and external manifest.
As for the AR problem, I found a similar problem using VMR9 renderless-mixer mode(MPC). Last edited by haruhiko_yamagata; 25th March 2007 at 15:46. |
25th March 2007, 15:47 | #883 | Link |
Registered User
Join Date: Nov 2006
Posts: 799
|
Where can I get a VC8 build of ffdshow? Your builds are not available anymore on sourceforge...
Edit: Found one on http://ffdshow.wyrdic.net/. Edit: Regarding the VS problems. Please check out 6th post here: http://forums.microsoft.com/MSDN/Sho...44703&SiteID=1 Last edited by fastplayer; 25th March 2007 at 15:58. |
25th March 2007, 16:28 | #884 | Link |
*****
Join Date: Feb 2005
Posts: 5,643
|
I will make some adjustments to the install script so that it can be used to install 64-bit binaries.
Compiling libavcodec with MSVC will probably produce a partially broken binary. Certainly if some asm code must be disabled. There are also two ToDo's that need to be fixed in ffv1.c
__________________
MPC-HC 2.1.7.2 |
25th March 2007, 16:34 | #885 | Link | ||||
Registered User
Join Date: Feb 2007
Posts: 65
|
Quote:
Quote:
Quote:
Quote:
The only thing I've found that's obviously broken in x64 is the OSD; the display is completely corrupt. This isn't new, though; the old ffdshow x64 build has the same problem, so whatever's broken has been broken for many months. |
||||
25th March 2007, 16:36 | #886 | Link | |
Registered User
Join Date: Feb 2007
Posts: 65
|
Quote:
|
|
25th March 2007, 16:42 | #887 | Link | |
Registered User
Join Date: Feb 2007
Posts: 65
|
Quote:
Both TODOs relate to C99 VLAs; there are other places in libavcodec that uses them, only they're *not* commented out. I don't think fixing them should be too hard; finding them might be trickier. |
|
25th March 2007, 17:24 | #889 | Link | |
*****
Join Date: Feb 2005
Posts: 5,643
|
Quote:
I have updated the install script to support 64-bit installation.
__________________
MPC-HC 2.1.7.2 |
|
25th March 2007, 17:30 | #890 | Link |
Registered User
Join Date: Feb 2007
Posts: 65
|
Weird. Maybe the IDE is getting confused, 'cos it's adamant that it's not defined. Not the first time IntelliSense loses touch with reality, of course. Anyway, I think I have put together some code that accommodates the lack of VLAs in VC8. Though I'm not 100% sure, as I totally hate C array/pointer declaration syntax.
|
25th March 2007, 18:12 | #892 | Link | |
Registered User
Join Date: Feb 2007
Posts: 65
|
Quote:
http://www.file.am/d/file/vcredist_x64.exe/ x86: http://www.file.am/d/file/vcredist_x86.exe/ |
|
25th March 2007, 18:34 | #894 | Link | |
*****
Join Date: Feb 2005
Posts: 5,643
|
Quote:
In the registry section you need to replace "ff_vfw.dll" with "{code:GetShortName|ExpandConstant('{app}\ff_vfw.dll'))}"
__________________
MPC-HC 2.1.7.2 |
|
25th March 2007, 18:39 | #895 | Link |
ffdshow/AviSynth wrangler
Join Date: Feb 2003
Location: Austria
Posts: 2,441
|
Okay, here's yet another updated version of my patch:
Download (MSVC build) Patch (against rev. 1074) I've added an AviSynth info item to ffdshow's OSD, which shows the number of back and ahead buffers used since the last reset (i.e. stop, seek, size change or similar); that should help a bit with finding the correct settings. It also shows the input frame number that's considered "current" for the generated frame and the frame numbers that were requested by the AviSynth script to produce it. If the current settings are too small it doesn't really matter, unless the filter doesn't work right if it doesn't get the frame it really requested. In that case, just up the buffers a bit and see what happens. Also, seeking around in the stream and/or letting it run for a bit might help finding edge cases where the script needs more frames. (Note that those values will go up when the buffers are flushed at the end of an MPEG2 stream, but that's because there is nothing left to be buffered and can be safely ignored.) The values can also be logged to a CSV file by checking "Save to" in ffdshow's OSD options. The buffer defaults were changed to 0/10/0 and Apply Pulldown is turned off by default for backwards compatibility, but of course at those settings it also doesn't really support (pseudo-)random access - but the OSD info should make tweaking the buffer settings a lot easier... I've also added some code to reset AviSynth on a BeginFlush on the DirectShow video input pin to work around a DVD Navigator bug where seeking doesn't cause an onSeek event, and without knowing that the stream was seeked the frames that were buffered before the seek get processed and played after the seek at full tilt, which looks weird and eats extra CPU time. @haruhiko: I've added an onFlush method in Tfilters and Tfilter, since that is the easiest and probably cleanest way to handle this (at least concerning the amount of code that needs to be changed and/or checked), although like you said doing anything in them other than flagging that there was a flush is probably a bad idea due to race conditions that may occur then. The flush itself is then handled when process() is next called. np: Christ - Vernor Vinge (Blue Shift Emissions)
__________________
now playing: [artist] - [track] ([album]) |
25th March 2007, 18:45 | #896 | Link |
ffdshow/AviSynth wrangler
Join Date: Feb 2003
Location: Austria
Posts: 2,441
|
Oh yeah, I noticed that (at least) the outline strength and radius sliders on the OSD font configuration page always get reset to 0 as opposed to reflecting the current settings.
__________________
now playing: [artist] - [track] ([album]) |
25th March 2007, 19:10 | #897 | Link | |
Registered User
Join Date: Mar 2004
Posts: 95
|
Hi
I use ffdshow for to encode to mpeg2 (the great libavcodec encoder). I live in a PAL country so I usually encode to 25 fps framerate. But recently I tried to encode some Quicktime trailers (the 300 movie taken from Apple site) and I get in VDub an error: Quote:
Blackness(300,640,480,"yv12",25) but this one gives the error: Blackness(300,640,480,"yv12",23.976) I noticed that encoding to mpeg4 gives the error too. I tried several ffdshow versions, including latest beta 2a and latest icl9 build, with the same result. |
|
25th March 2007, 19:16 | #898 | Link |
*****
Join Date: Feb 2005
Posts: 5,643
|
Read the first post of this topic for the answer.
__________________
MPC-HC 2.1.7.2 |
25th March 2007, 19:37 | #899 | Link |
Registered User
Join Date: Mar 2004
Posts: 95
|
I see.
Any ideea, can be fixed in the future? Not that it can't be worked around the way it is now, I can change fps in avisynth to 25 fps an then change it back in restream but would be nice to work with any input framerate. |
25th March 2007, 20:13 | #900 | Link |
Curious BetaTester
Join Date: Oct 2005
Posts: 430
|
after further tests using xvid anamorphic clips with ffdshow rev1069
this is what happens with AR changes in avi's and mp4's http://www.mytempdir.com/1269513 test1 = anamorphic-source.avi+xvid-par16x9-dar1x1.avi test2 = anamorphic-source.avi+xvid-par1x1-dar16x9.avi in vlc xvid-par16x9-dar1x1.avi: AR works xvid-par1x1-dar16x9.avi: AR works container16x9-bitstream5x4.mp4: AR works container-unspecified-bitstream16x9.mp4: AR works test1: AR works test2: AR works in mpc/ffdshow xvid-par16x9-dar1x1.avi: AR does not work xvid-par1x1-dar16x9.avi: AR does not work container16x9-bitstream5x4.mp4: AR works container-unspecified-bitstream16x9.mp4: AR works test1: AR does not work test2: AR does not work not sure if the naming scheme is correct, using xvid using the 2 types of 16x9 - 1 using PAR 16/9 and other DAR 16/9 and the mp4's i used yamp and told it to use DAR 16/9 cheers all ps. using render overlay/haali/vmr9-renderless but with vmr9-windowed all is fine
__________________
Asrock N68-S AMD Athlon(tm) II X4 620 Processor (2.6GHz) - Crucial 2GB PC6400 800MHz DDR2 - Nvidia 9600GT Tools: ProcessExplorer & ProcessMonitor - BatchCompressor Guide: MinGW Compiling GCC Last edited by cc979; 25th March 2007 at 20:18. |
Tags |
ffdshow, ffdshow tryouts, ffdshow-mt, ffplay, icl |
Thread Tools | Search this Thread |
Display Modes | |
|
|