Guest
|
 Posted:
Fri Mar 18, 2005 8:01 am Post subject:
AutoGK file size not the specified target size? |
|
|
Well I have happened upon AutoGK after getting frustrated with
FlaskMPEG (for no reason it has started spitting out files whose audio
is off, or size is way off (for two pass encoding), or no audio etc.
AutoGK is about the easiest encoder I have used and (other than the
adware [grrrrrrrr] I totally love it). I have run into a problem
though, with v1.6 and beta v1.9x; file size.
I have tried setting it to make movies that are 700MB (have tried the
1/6th DVD option too) but instead I get around 460MB almost every time.
I am hoping that I can just erase some settings file and have it
start-anew but am not sure. Is anyone else out there having this
problem, and if so have you resolved it? Any help would be greatly
appreciated!
Cheers
-Gaiko
|
|
Billy Joe
Guest
|
| Posted:
Fri Mar 18, 2005 9:33 pm Post subject:
Re: AutoGK file size not the specified target size? |
|
|
In ref: 1111114872.077458.319540@z14g2000cwz.googlegroups.com
gaikokujinkyofusho@gmail.com <gaikokujinkyofusho@gmail.com>
wrote:
| Quote: | Well I have happened upon AutoGK after getting frustrated with
FlaskMPEG (for no reason it has started spitting out files
whose audio is off, or size is way off (for two pass
encoding), or no audio etc. AutoGK is about the easiest
encoder I have used and (other than the adware [grrrrrrrr] I
totally love it). I have run into a problem though, with
v1.6 and beta v1.9x; file size.
I have tried setting it to make movies that are 700MB (have
tried the 1/6th DVD option too) but instead I get around
460MB almost every time. I am hoping that I can just erase
some settings file and have it start-anew but am not sure.
Is anyone else out there having this problem, and if so have
you resolved it? Any help would be greatly appreciated!
Cheers
-Gaiko
|
Certainly not a direct answer to your question, but .....
I don't use AGK and do use Flask, which can be quirky. I'm
pretty sure AGK works similarly to Flask, VDub, and other codec
front-ends, in that it sends parameters to the codec which in
turn does the actual work to produce a bit-rate that yields a
desired file size.
So, I'm suggesting that you take a look at the codec's parameter
pages (they are retained between uses) to see what's up? The
settings you see should compute to the file sizes you're
getting.
With Flask, when it starts to misbehave, a reinstall from the
original downloaded ZIP file almost always solves the problem.
On a few occasions, reinstalling the codec has been the
solution. After enough of these anomalies, I found that simply
deleting Flask's .\Settings info restored it from most erratic
behavior (of course I had to fill in some of the params again
upon next use).
I've had a few files, among many many, that required me to
switch codecs - usually from Divx to Xvid, to complete the
conversion - as a result, xvid has become my de facto codec.
The Divx codec occasionally returns an error to Flask that Flask
does not handle, causing it to abort. I've never stopped to
determine the cause, as switching codecs has solved it.
MPEG2 files which have been edited with either TMPGEnc or
nanoMPEG, to remove commercials for example, often result in
Flask or VDub losing a pointer to the audio track at the point
of one of the cuts - and sometimes restoring audio at the next
cut!! Such editing is far better to be done in VDub-MPEG2,
which has superb cutting/splicing tools. Flask has odd editing
behavior and no batch processing mode, so VDub is absolutely the
conversion program of choice here.
VDub also allows the user to save settings (VCF files) which
lead to almost-pushbutton operation for one or multi pass
conversions. I use VCF files that are named by codec, pass,
aspect. This wouldn't work for you, because you're interest is
in file size, while mine is in standard bit rates and audio
volumes - very few of my AVIs are smaller than 1 gig. But you
could probably work out a set of VCFs for yourself that would
require very little tweaking to get your target file size. In
the long run, that's the only thing that AGK is actually doing
for you!!
If your source material happens to be a DVD and you're using
NTFS, then use DVD Decrypter to rip it and set DVDD's File Mode
to "File Splitting: none." This will produce a single VOB that
VDub deals with perfectly. BTW, Flask will also handle this
abnormal VOB.
BJ |
|
Tom Cole
Guest
|
| Posted:
Sat Mar 19, 2005 4:04 am Post subject:
Re: AutoGK file size not the specified target size? |
|
|
gaikokujinkyofusho@gmail.com wrote:
| Quote: | Well I have happened upon AutoGK after getting frustrated with
FlaskMPEG (for no reason it has started spitting out files whose audio
is off, or size is way off (for two pass encoding), or no audio etc.
AutoGK is about the easiest encoder I have used and (other than the
adware [grrrrrrrr] I totally love it). I have run into a problem
though, with v1.6 and beta v1.9x; file size.
I have tried setting it to make movies that are 700MB (have tried the
1/6th DVD option too) but instead I get around 460MB almost every time.
I am hoping that I can just erase some settings file and have it
start-anew but am not sure. Is anyone else out there having this
problem, and if so have you resolved it? Any help would be greatly
appreciated!
Cheers
-Gaiko
|
For over / under sized AVIs see AGK FAQ at
http://forum.doom9.org/showthread.php?s=&threadid=72679 point 6.3.
As for the Adware, You can uninstall it from Control Panel -> Add or
Remove Programs and AGK will still work ok. |
|
Profile
Log in to check your private messages
Log in