avidemux2 Video Editor Extreme edition psp,xvid,dvd,svcd etc
I'll second the comment about posting on Avidemux's forum and VideoHelp, if you need help - especially since I also post regularly to VH, and there's quite a few video gurus there. But just to be safe, if you want to discuss working with video under Linux, it's probably a better idea to make sure you're posting to the Linux subforum (http://forum.videohelp.com/linux-f19.html).
[ Puppy 4.3.1 JP, Frugal install ] * [ XenialPup 7.5, Frugal install ] * [XenialPup 64 7.5, Frugal install] * [ 4GB RAM | 512MB swap ]
In memory of our beloved American Eskimo puppy (1995-2010) and black Lab puppy (1997-2011).
In memory of our beloved American Eskimo puppy (1995-2010) and black Lab puppy (1997-2011).
Makoto; I thought about posting there, but after reading posts about the sync
problem and no fix other than running the vobs through ffmpeg to fix them.
The problem it seems is varying frame rates that avidemux doesn`t handle.
I`ll give it a go...
Patriot; DVD vob to avi Xvid or x-h264 video , keep the Ac3 5.1 sound.
Fairly simple, just changing the video stream format and file container.
problem and no fix other than running the vobs through ffmpeg to fix them.
The problem it seems is varying frame rates that avidemux doesn`t handle.
I`ll give it a go...
Patriot; DVD vob to avi Xvid or x-h264 video , keep the Ac3 5.1 sound.
Fairly simple, just changing the video stream format and file container.
Hmmm .....
1. If your DVD content has variable frame rates then you must use "Build VBR time map" option before encoding begins or it'll become unsync. The VBR time map will help avidemux to sync properly ...
2. Variable frame rate is not suited (read: not supported) with avi container. Use mkv or mp4 for best results.
3. I've done x264 with ac3 into avi before and the final cut works just fine ... Don't use AAC with avi, they're don't get along ...
4. Best encoding for avi is still xvid+ac3 (2ch/3ch/6ch) ... It's fine if you don't mind the size ...
5. For HD content, I suggest either mkv or mp4. Normally I prefer x264+AAC in mkv to have the so-called m-HD content.
Rgds
Sounds simple, but not quite so .....sunburnt wrote:..... DVD vob to avi Xvid or x-h264 video , keep the Ac3 5.1 sound. .....
1. If your DVD content has variable frame rates then you must use "Build VBR time map" option before encoding begins or it'll become unsync. The VBR time map will help avidemux to sync properly ...
2. Variable frame rate is not suited (read: not supported) with avi container. Use mkv or mp4 for best results.
3. I've done x264 with ac3 into avi before and the final cut works just fine ... Don't use AAC with avi, they're don't get along ...
4. Best encoding for avi is still xvid+ac3 (2ch/3ch/6ch) ... It's fine if you don't mind the size ...
5. For HD content, I suggest either mkv or mp4. Normally I prefer x264+AAC in mkv to have the so-called m-HD content.
Rgds
..in dvd it seems...hmm always used handbrake for converting from dvd to other formats..I only know that avidemux can imprt them but only done it once.. I use avidemux to work with other formats and simple editing and occasionally had problems with VBR audio (audio is often neglected with third party files) and had to resort to virtualdub or virtualdubmod to sort out the trickier ones but otherwise the best solution is not to convert the audio format.The problem it seems is varying frame rates that avidemux doesn`t handle.
Variable frame rate video...now thats mean but dvds are always adding new ways to make conversion tricky (but I paid for it!!)
ps I hate DVD's ..always did
Patriot seems to have his finger on the pulse there
regards
mike
mikeb; The number of posts saying to use other apps. to fix things makes me worry...
Patriot; I did the movie again and clicked: [Audio] "Build VBR time map",
no notice saying it had done anything and the movie was exactly the same.
Q about codecs, x264 and h264 are supposed to encode faster than Xvid... True?
One post said that Xvid takes 2 to 3 times longer? That`s hard to believe, but...
Xvid takes 2 hours for a 2 hour movie, *264 will do 2 hours in 45 min.? WOW!!!
And I assume they`re correct when they say that *264 is higher quality than Xvid.
Also I saw a post saying not to use *264 codecs with an avi container file.
A pre-processing app. is needed to produce a reliable file for the encoder-editors.
It`s been suggested to run the vobs through ffmpeg to do this.
But then why not just use ffmpeg..? But then I think avidemux uses ffmpeg...
Patriot; I did the movie again and clicked: [Audio] "Build VBR time map",
no notice saying it had done anything and the movie was exactly the same.
Q about codecs, x264 and h264 are supposed to encode faster than Xvid... True?
One post said that Xvid takes 2 to 3 times longer? That`s hard to believe, but...
Xvid takes 2 hours for a 2 hour movie, *264 will do 2 hours in 45 min.? WOW!!!
And I assume they`re correct when they say that *264 is higher quality than Xvid.
Also I saw a post saying not to use *264 codecs with an avi container file.
A pre-processing app. is needed to produce a reliable file for the encoder-editors.
It`s been suggested to run the vobs through ffmpeg to do this.
But then why not just use ffmpeg..? But then I think avidemux uses ffmpeg...
Hmmm .....
x264 encodes better not faster. In simplest terms, it means that x264 encodes more frames in better details per block of data. Of course, it comes with a price, higher cpu requirements. Similar to .gz vs .bz2 where gz is faster but bigger, bz2 is slower but smaller. The higher quality x264 result comes from the better algorithm but it also depends on whether the settings are properly done. My minimum cpu recommendation for simple x264 LC encoded content would be a p3 600Mhz. Any lower and it may stutter.
Xvid on the other hand encodes faster but generally at twice the size of x264. As I mentioned previously, if you don't mind the size then this is fine ... If you are to follow the specs then yes, x264 is not suited for the avi container. This is especially true for the windows platform where splitters+codecs can play havoc.
If you have VFR (vbr video) then you need to use a bit of sorcery to convert. It's part of the game. You need to understand that while any DVD disc looks the same on the shiny layer, the contents are not done the same way. The actual time needed to encode to x264 or xvid depends on encoder settings and final content requirement. For me, it is normal for a 2 hour video encoded with x264 to take between 3 to 8 hours for multi-pass + avg bit rate/final size.
Avidemux uses internal ffmpeg plus a set of known external libs if its available. It does not depend on external ffmpeg to work. This ensures that avidemux uses the correct ffmpeg version that it requires. Video conversions process sometimes requires multiple tools to get it right. As mikeb has noted, certain tricky content needs other tools like Virtualdub/Mod which is one of my favourites for avi conversions. No video editor/encoder is perfect, so, by just saying ffmpeg is enough to encode everything is incorrect ... Please understand, ffmpeg is a very useful and powerful tool but it is not a magic wand .....
Please, we should bring future discussions to another thread if required ...
Rgds
That could mean the audio has no VBR but the video does ... It may help by using a -1ms audio shift (one of the tricks I used before) ... Without knowing what the actual content is, it's difficult to say .....sunburnt wrote:........
no notice saying it had done anything and the movie was exactly the same.
x264 encodes better not faster. In simplest terms, it means that x264 encodes more frames in better details per block of data. Of course, it comes with a price, higher cpu requirements. Similar to .gz vs .bz2 where gz is faster but bigger, bz2 is slower but smaller. The higher quality x264 result comes from the better algorithm but it also depends on whether the settings are properly done. My minimum cpu recommendation for simple x264 LC encoded content would be a p3 600Mhz. Any lower and it may stutter.
Xvid on the other hand encodes faster but generally at twice the size of x264. As I mentioned previously, if you don't mind the size then this is fine ... If you are to follow the specs then yes, x264 is not suited for the avi container. This is especially true for the windows platform where splitters+codecs can play havoc.
If you have VFR (vbr video) then you need to use a bit of sorcery to convert. It's part of the game. You need to understand that while any DVD disc looks the same on the shiny layer, the contents are not done the same way. The actual time needed to encode to x264 or xvid depends on encoder settings and final content requirement. For me, it is normal for a 2 hour video encoded with x264 to take between 3 to 8 hours for multi-pass + avg bit rate/final size.
Avidemux uses internal ffmpeg plus a set of known external libs if its available. It does not depend on external ffmpeg to work. This ensures that avidemux uses the correct ffmpeg version that it requires. Video conversions process sometimes requires multiple tools to get it right. As mikeb has noted, certain tricky content needs other tools like Virtualdub/Mod which is one of my favourites for avi conversions. No video editor/encoder is perfect, so, by just saying ffmpeg is enough to encode everything is incorrect ... Please understand, ffmpeg is a very useful and powerful tool but it is not a magic wand .....
Please, we should bring future discussions to another thread if required ...
Rgds
Indeed facinating subject....there are whole sites dedicated to the subject.Please, we should bring future discussions to another thread if required ...
As mentioned there is no such thing as one tool does all...partly due to the plethora (lovely word) of formats present.
My preference is xvid+mp3 in avi wrapper as space is not at a premium but cpu performance is....with different hardware then another combination makes sense. Just like there is the perfect puppy for yer hardware .
So on topic....within its limits...avidemux is good sh*t maan but in some instances one needs to look elsewhere..... avcodec/ffmpeg it a common factor but not always in a common approach.
mike