encoded movie problem

[monkeymon]

after i have encode my divx movie. the show will jerky every 5~10 sec..

i used flaskmpeg 6.0 and 5.0 codec to encode the movie at a bitrate of 1840fps and mp3 128bit sound.

izzit the bitrate too high that cause the problem or is the software i used ?

my computer config is 866 p3, 256 sdram, geforce2 MX 64mb


sorry if i post at the wrong forum.

[monkeymon]

if anyone know why pls help mi
becoz i have been figuring this for quite long and still cant find the reason for it

[Acaila]

I don't know what the problem is, but I can only suggest that you try a 'real' encoder like GordianKnot(VDub) or Vidomi. Flask gives most people nothing but trouble...

[monkeymon]

i have used the vidomi but it always have the sound out of synn problem...


when i used the GordianKnot its bitrate like not correct... i also dunno why

[yokotsoko]

The problem might probably be the sound. To find out if the sound causes the jumpy results just encode a small portion of the film without the sound. If this is the problem then download the radium codec. In my computer it worked better (which means caused no problems with flaskmpeg - xmpeg) than the lame.acm and anyway radium uses the lame source code I think. Another hint is to try xmpeg 4.5 which is identical to flaskmpeg so you won't have problems using it.

[monkeymon]

without the sound is perfactly alright

maybe i should download the radium

thanks

[theReal]

and anyway radium uses the lame source code I think.Radium is a hacked version of the Fraunhofer mp3 encoder. It's a good mp3 codec, but it does certainly not use Lame's source code...

[yokotsoko]

thank you theReal for the information
@monkeymon
you can find radium here
http://www.doom9.org/Soft21/Audio/ra-codec12.zip
I suggested this codec because even lame didn't work as it should xith xmpeg in my computer.
After installing it you must change its priority among the other audio codecs. If you are using winXP hit the flag button and Pause.Go to the hardware card -> device manager -> sound video and game controllers -> audio codecs -> properties. Then find the codec and lower the number that indicates its priority. Make it lower than any other mp3 codecs you may already have installed. In any case don't remove the fraunhofer codec already installed in your computer because windows uses this one.
Then when using flask/xmpeg the mp3 codec will then have changed.
Now there is a question I would like to ask to the others. Is it better to use cbr in order to be 100% sure that you'll get rid of asynch problems?

[theReal]

To be 100% sure for any player and any hardware environment, I'd use CBR mp3. For example BSplayer always seems to run out of sync with VBR and ABR mp3 on my computer (works for many other, though).

However, be careful with the Fraunhofer codec - if you encode audio seperately, the codec sets a slightly wrong bitrate and slightly changes the file-length (out of sync for sure!). VDub corrects this problem if you encode audio and video at the same time, I think XMpeg also corrects this.

Whatever, I always encode audio seperately with LAME, either using BeSweet or Razorlame as frontends. It gives me the best results and the best audio-synch. If I wanted CBR mp3, I'd use "--alt-preset cbr" with lame.

[yokotsoko]

I had this impression that vbr sometimes creates sync problems and that's why I encode with CBR. I also use Besweet as it's sound is far superior than the sound produced by Xmpeg. I usually use 96 kbs mp3 with resampling to 48khz. Anyway do you think that using VBR or ABR (which one is best?) with Besweet and then muxing with Nandub I won't experience any async problems?

[jggimi]

Ask any user of Gordian Knot. Azid/LAME or Besweet abr mp3, hundreds of users, no sync problems.

Gordian Knot process uses dvd2avi to demux .ac3 files, then eventually Nandub to mux encoded video and transcoded .mp3 audio, using milliseconds delay/advance provided by dvd2avi.

[prom3theus]

This is hopefully for theReal and others in this thread who are comfortable using lame mp3 for most things, and encoding separately.

I have problems using lame in that a lot of my editors I use for various things (like virtualdub) don't seem to correctly identify the header code and show an unknown file type, even though the code flag shows up the same (0055 right?).

It seems like the only thing that needs fixing is some string needs slightly changed to fit the right format, sort of like when a hard drive fails to recognize in Windows just because the file system string "Fat32" is not perfect.

Is there some fix for this? I'm using the latest version of lame (at least it is only a few months old at most), and I still have odd problems.