Log in

View Full Version : suggestion...


barkybark
8th April 2005, 13:46
How about dvd output, now that you have avi input? Then you would indeed have a very complete conversion tool......
regards
J

homermaster
4th May 2005, 02:42
that would be a great option .... However since we are having trouble getting mkv container support I think it will be a LONG TIME before we see vob output. Try TMPGenc ... the only "affordable" software that I know to do this. If you aren't worried about affordable try Sony's Vegas+DVD. :)

unskinnyboy
4th May 2005, 02:50
You guys gonna make AutoGK 'input anything'-->'output anything'? :)

AutoGK is for MPEG-4 encoding and that is how it should be. I don't understand why you need AutoGK to do MPEG-2 encoding (it is a whole different animal) when there are many other excellent tools available to do the same? Besides I don't think it is possible/easy since the whole code would have to be rewritten.

barkybark
4th May 2005, 06:56
Ok, thanks.
/J

280zx
6th May 2005, 01:13
When converting dvd format clips to xvid, it would be very helpful if a bitrate estimate was provided. As it is now, I choose custom size and just try for about 10 megabytes per minute to roughly approximate 1300kbps. Is there an easy way to estimate the bitrate you're going to get when converting a 15 minute clip for instance?

cyberVera
6th May 2005, 01:20
Is there an easy way to estimate the bitrate you're going to get

Gordian Knot easily does it. AutoGK - not.
Anyway, you can use any bitrate calculator to do that, including that one inside XviD codec shell.

unskinnyboy
6th May 2005, 01:25
Originally posted by 280zx
When converting dvd format clips to xvid, it would be very helpful if a bitrate estimate was provided. As it is now, I choose custom size and just try for about 10 megabytes per minute to roughly approximate 1300kbps. Is there an easy way to estimate the bitrate you're going to get when converting a 15 minute clip for instance?
Yes, use a bitrate calculator.

But on the other hand, you seem to be trying for consistent quality everytime. Otherwise, what's with this 1300? Maybe you should be using the 'Target Quality' option in AutoGK rather than the 'Target Size'.

280zx
6th May 2005, 01:41
I want 2 passes not one so no I don't want to use target quality. Or did they change that? I want around 1300kbps for quality. Anything below 1000 always looks blocky.

Got a recommendation for a calculator? I was thinking more along the lines of an integrated calculator like fairuse wizard has, hence I posted in a suggestion thread.

unskinnyboy
6th May 2005, 03:10
So basically what you are looking for is good quality, the kind you get right now when you aim for 1300 kbps, right? I don't know how everytime 1300 can give you good quality, so it also seems like you are encoding material which are of the same type and length everytime.

What I suggest you do is to do the following test: Encode using 75% 'Target Quality' and check the resultant bitrate. If it is say ~1200, increase the target quality a notch and try again (and the other way around if the bitrate is 'too high' for your liking). Repeat till you figure out at which percentage of quality you are getting 1300. Then you can use the same percentage everytime. Easier and faster. Does this make sense?

You realize that you cannot control both filesize and bitrate, right? Means for every encode@~1300 kbps, your resultant size will be different. So it is seriously beyond me why you weren't using 'Target Quality' in the first place.

Reg: the bitrate calculator, use the one bundled with GK.

280zx
6th May 2005, 04:39
You don't seem to get what I'm saying and I don't really care to explain it further. Nevermind.

unskinnyboy
6th May 2005, 04:49
So much for going beyond what was asked and trying to help, lol. OK then, you got your recommendation for bitrate calculator. Hope you will be able to do 2-pass encode@1300 kpbs in AutoGK 'properly' now. :rolleyes: