Setsunaaa
29th January 2007, 21:07
Will DIB input (VirtualDub frameserver) be supported?
My Usage:
Recording from DVB-S opened in Virtualdub-mpeg from http://fcchandler.home.comcast.net/index.html.
Reason to still stick with virtualdub: MOST robust mpeg2 decoder when it comes to those unpreventable stream errors in the recording, all others show visible errors. Second reason: better filters for me.
Currently running aviproxy + an HUGE avisynth script containing:
AviSource("framserver.avi")
ConvertToYV12()
It would save me the avs script if x264 were able to read that directly, Virtualdub can read that windows-typical uncompressed input, so the source is out there.
This obscure way of x264 encoding doesn't improve the quality/compression very much over the last vfw build, but it is WAY faster even with higher moiton search settings.
My Usage:
Recording from DVB-S opened in Virtualdub-mpeg from http://fcchandler.home.comcast.net/index.html.
Reason to still stick with virtualdub: MOST robust mpeg2 decoder when it comes to those unpreventable stream errors in the recording, all others show visible errors. Second reason: better filters for me.
Currently running aviproxy + an HUGE avisynth script containing:
AviSource("framserver.avi")
ConvertToYV12()
It would save me the avs script if x264 were able to read that directly, Virtualdub can read that windows-typical uncompressed input, so the source is out there.
This obscure way of x264 encoding doesn't improve the quality/compression very much over the last vfw build, but it is WAY faster even with higher moiton search settings.