Posted by Bill's News on 04/22/06 18:23

Bob wrote:
> On Fri, 21 Apr 2006 10:22:47 -0700, "Bill's News"
> <BillsNews@pcmagic.net> wrote:
>
>> Flask may have a steep learning curve for some folk,
>
> That is an understatement.


>I could never get it to work.

I'm not sure to what this attests? What could you not get it to do?
Had something to do with subtitles and not being able to push just one
button, IIRC?

I use Flask profiles for those conversions which I do most often and
seldom have to deal with subtitles from captured TV. So, while it
takes more than a single button to process a/v in Flask, it's
relatively simple. DVD subtitles, which are captured/converted using
OCR techniques, need far too much editing to be incorporated into a
one-button process.

> I recommend Auto Gordian Knot and XviD conversions. There is also
> WinAvi which is faster.

How fast is either of these at producing 2 pass, de-interlaced, 2 mbps
video with .192 mbps stereo MP3?

Most of my conversions run on a 2gp4, 512m, with 2 internal and 2
external hard drives. These specs require about 3.5:1 (conversion to
play time) to produce Xvid results at the bit rates which I use. A
3.2gp4 (dual processor) similarly configured yields about 2.25:1.

Conversion times are less, if the source audio is retained rather than
converted (as would be the case with AC3).

I've not measured project run-times yet with Divx 6.2.1, but I didn't
get the sense, while testing for quality, that it will be any faster
than Xvid 1.1.0. Nor did the quality test convince me that Divx @ 3
mbps is any better than Xvid @ 2 mbps.

Oh, BTW, I might mention that I only recently upgraded to Koepi's Xvid
1.1.0 from 1.0.2 and that in all VDub VCF files (conversion profiles)
the codec configuration strings became invalid without a warning, thus
producing way out of spec results. Each had to be reconfigured. I
mentioned this because AGK calls VDubMod to do its grunt work, but I
do not know whether AGK uses the codec configuration string in VCFs.

[Back to original message]