Quote:
Originally Posted by kemuri-_9
No, --video-filter is very different functionality.
I was originally referring to the last clauses of this and this |
I see, thanks.
Quote:
Originally Posted by kemuri-_9
I don't see where that information came from, there's overhead in the vfw system when interfacing with avisynth so using vfw4x264 is actually slower. also the latter point doesn't make sense.
|
That's what I found with a quick search, not my personal experience.
Here are some quotes (from 2009-2010):
Quote:
Originally Posted by Alf Bundy
Quote:
Originally Posted by Zathor
Can you please try out the avs4x64 file and compare it in terms of speed to vfwx264? (Simply rename avs2x264 to vfw2x264)
|
Just updated to x264 1400 and made 2 quick tests :
Quote:
- Test 1 : Source MPEG-2 decoded with DGmultiSource()
640x480 25fps (44min 35")
avs4x264.exe - Fast 1st pass : avg FPS = 72,92fps - 15min 16"
vfw4x264.exe - Fast 1st pass : avg FPS = 80,73fps - 13min 49"
|
Quote:
- Test 2 : Source VC-1 ES decoded with DGmultiSource()
1280x544 23.976fps (1000 frames)
avs4x264.exe
- Fast 1st pass : avg FPS = 27,04fps - 36 sec
- 2nd pass : avg FPS = 3,5fps - 4min 46"
vfw4x264.exe
- Fast 1st pass : avg FPS = 27,69fps - 36sec
- 2nd pass : avg FPS = 3,51fps - 4min 45"
|
Win7 x64, C2D E7400 @ 3Ghz, GPU = NV 9800GTX+
MeGUI 0.3.3.0, DG tools build 2005
PS : about MeGUI's version , in update (dev. server) I see Existing version 0.3.3.0 / latest version 0.3.2.3
Is that normal ? |
Quote:
Originally Posted by MuLTiTaSK
try with vfw4x264.exe instead it's faster for me and others it also doesnt corrupt MPEG2 streams loaded with MPEG2Source("") like avs4x264.exe does  |
Quote:
Originally Posted by Zathor
Are you using the latest dev build? I'm asking because the latest build is using vfw4x264 and not avs4x264 because of some problems (e.g. with mpeg2 input).
|
Quote:
Originally Posted by JoeH
Zathor,
I just tried the latest development build with vfw4x264.
It works great, and for me runs even slightly faster (between .5% and 2%) than the avs4x264!
|
But I also found these now:
Quote:
Originally Posted by Zathor
In my benchmarks there has been no real difference between both wrappers.
|
Quote:
Originally Posted by Zathor
Quote:
Originally Posted by [ReX]
It's using vfw4x264.exe now instead of avs4x264.exe?
Why the change?
avs4x264.exe is faster here.
|
Because avs4x264 produces garbage if the source is mpeg2 with DGDecode_mpeg2source serving this file (I do not know if dgmpg is the source of the problem or mpeg2 in general or avs4x264). vfw4x264 has no known problems. |
And the MPEG-2 problem was fixed, obviously:
Quote:
Originally Posted by Zathor
I have updated a few tools (x264, mkvtoolnix, dgindexnv). I'm only writing this because I have moved to the x264 build from Komisar and replaced the avs4x264 file with a new one from alwa. This should fix the problem with DGDecode_mpeg2source but I did not test it and therefore vfw4x264.exe is still used for x64.
|