VideoHelp Forum




+ Reply to Thread
Results 1 to 10 of 10
  1. Member
    Join Date
    Jul 2006
    Location
    United States
    Search Comp PM
    I don't know how to setup Avidemux with twolame and ffmpeg.

    Please tell me how to setup/configure everything to work properly.

    I use Windows XP Professional.

    I really can't find anything to help me, since Avidemux homepage and forums tend to cater to Linux users.

    TIA.

    Peace.
    Quote Quote  
  2. Member steveryan's Avatar
    Join Date
    Jan 2003
    Location
    Manchester
    Search Comp PM
    Go to Audio/Encoder choose your encoder then hit configure codec, that's it.
    He's a liar and a murderer, and I say that with all due respect.
    Quote Quote  
  3. Member
    Join Date
    Jul 2006
    Location
    United States
    Search Comp PM
    Originally Posted by steveryan
    Go to Audio/Encoder choose your encoder then hit configure codec, that's it.
    Not so fast, that doesn't work.

    Error message when TwoLame is selected and save audio is selected:

    "TooLame Initialization Failed

    Not Activated"

    Error message when ffmpeg mp2 is selected and save audio is selected:

    "FFmpeg mp2 Initialization Failed

    Not Activated"

    Using AviDemux 2.2 Preview 2 (svn revision 2083) and the latest versions of twolame & ffmpeg.

    Peace.
    Quote Quote  
  4. Member
    Join Date
    Dec 2004
    Location
    Australia
    Search Comp PM
    You linked statically or dynamically? I always link statically, although I would have thought that avcodec/format are always linked statically. Also why 2.2 and not 2.3? Especially if you really ported the latest ffmpeg codec over.
    Quote Quote  
  5. Member
    Join Date
    Jul 2006
    Location
    United States
    Search Comp PM
    Originally Posted by celtic_druid
    You linked statically or dynamically? I always link statically, although I would have thought that avcodec/format are always linked statically.
    You have to remember, I'm a newbie.

    I don't understand the question. How do you link? What's the difference between static and dynamic? Could you elaborate?

    Just by your question, I can tell you are light years ahead of me in terms of understanding avidemux, ffmpeg, and twolame.

    Originally Posted by celtic_druid
    Also why 2.2 and not 2.3? Especially if you really ported the latest ffmpeg codec over.
    I just followed the tool link at videohelp.com and the download link to the win32 binaries were for avidemux 2.2. I only recently came across the doom9 thread w/ the download link to avidemux 2.3.

    Unfortunately, the doom9 thread is all about h.264 and it's an advanced thread that doesn't touch on my newbie question on how to setup avidemux.

    Thank you for responding to my thread, please offer additional help and/or direct me to resources/guides that will help me setup the software correctly.

    TIA.

    Peace.
    Quote Quote  
  6. Member
    Join Date
    Dec 2004
    Location
    Australia
    Search Comp PM
    Ok, so you have an old version and you don't have the latest ffmpeg, you have ffmpeg code from that time. Same could be true for twolame, although it isn't updated as often as ffmpeg (changes aren't ported over to avidemux straight away though).

    That build would be linked dynamically. Fact is that some libs like gtk have to be linked dynamically since there are no static libs for win32.

    Using means cross builds should be as simple as unpacking. Some builds are just updates though and depend on dll's from previous builds.

    You can try my builds from: http://celticdruid.no-ip.com/xvid/ If you are missing any dll's. Use the gtk installer from gimp win32. All other dll's should be included.
    Quote Quote  
  7. Member
    Join Date
    Jul 2006
    Location
    United States
    Search Comp PM
    Originally Posted by celtic_druid
    Ok, so you have an old version and you don't have the latest ffmpeg, you have ffmpeg code from that time. Same could be true for twolame, although it isn't updated as often as ffmpeg (changes aren't ported over to avidemux straight away though).

    That build would be linked dynamically. Fact is that some libs like gtk have to be linked dynamically since there are no static libs for win32.

    Using means cross builds should be as simple as unpacking. Some builds are just updates though and depend on dll's from previous builds.

    You can try my builds from: http://celticdruid.no-ip.com/xvid/ If you are missing any dll's. Use the gtk installer from gimp win32. All other dll's should be included.
    You're joking right???

    I have Avidemux 2.2 Preview 2 win32 binaries dated 6/18/06 (recent enough for my purposes, i.e. NO h.264 encoding). FFmpeg revision 6129 win32 binaries dated 8/30/06 (again recent enough for my purposes), and Twolame 0.3.8 dated 7/3/06 (the most recent version on the developer's website).

    My problem is NOT getting the latest and greatest version of Avidemux (they are ALL unstable versions and them most recent branches change daily). My problem is setting up/configuring Avidemux, FFmpeg, and Twolame to work properly, PERIOD. It's NOT a fancy solution, just a newbie question, due to Avidemux's website and forum's poor support/documentation for win32 binaries.

    I can already demux the video and audio elementary streams from an avi container (Xvid video & AC-3 audio) using Avidemux. However, the audio is PCM/LPCM (which is rather large) and I would like to use Avidemux's option to extract the audio elementary stream in mp2 audio. I will later use this to create a SVCD, which requires mp2 audio NOT AC-3. My transcoding program chokes on AC-3 audio, so I am doing the conversion to convert the AC-3 to mp2, and then mux the video back to avi. Then I can transcode to mpeg-2 for SVCD authoring.

    I could transcode the PCM/LPCM in BeSweet, but I have heard of audio sync problems, and I would prefer converting the audio once (though Avidemux) instead of twice (using Avidemux, then BeSweet), to minimize the possible sychronization problems. To me transcoding twice, instead of once, give the potential for twice the synchronization problem.

    The reason I explained what I am trying to do is that your posts don't make any sense to me.

    They don't address my question(s), I'm not using Avidemux to transcode h.264 like everyone on Doom9 forums, but I simply want to use Avidemux to transcode the audio from AC-3 to mp2 in ONE STEP.

    Thanks for responding, but I really need some help solving my problem, not finding the latest and greatest version of Avidemux for this week.

    TIA.

    Peace.
    Quote Quote  
  8. Member
    Join Date
    Dec 2004
    Location
    Australia
    Search Comp PM
    Avidemux uses internal ffmpeg code, not an external ffmpeg binary. It uses whatever twolame lib it was linked against. It doesn't use twolame.exe.

    So the fact is that you can't be using the latest twolame if 0.3.8 came out after the avidemux build, then that build must be linked against an older twolame lib. Same goes for ffmpeg.

    I don't recall mentioning h.264. Avidemux hasn't changed in that regard in a fair while. Latest change of note was probably the addition of Aften support for AC3 encoding.

    My comment about 2.3 vs. 2.2 was because the 2.2 branch was basically killed off. If you want stable, go with the 2.1 branch. If you want new features, etc. go with 2.3, not 2.2.

    Don't worry, I won't try and help you in future.
    Quote Quote  
  9. Member
    Join Date
    Jul 2006
    Location
    United States
    Search Comp PM
    Originally Posted by celtic_druid
    Avidemux uses internal ffmpeg code, not an external ffmpeg binary. It uses whatever twolame lib it was linked against. It doesn't use twolame.exe.

    So the fact is that you can't be using the latest twolame if 0.3.8 came out after the avidemux build, then that build must be linked against an older twolame lib. Same goes for ffmpeg.

    I don't recall mentioning h.264. Avidemux hasn't changed in that regard in a fair while. Latest change of note was probably the addition of Aften support for AC3 encoding.

    My comment about 2.3 vs. 2.2 was because the 2.2 branch was basically killed off. If you want stable, go with the 2.1 branch. If you want new features, etc. go with 2.3, not 2.2.

    Don't worry, I won't try and help you in future.
    Okay, now I understand it a little better. I would have like to have gotten this reply earlier.

    So you have to compile from the source code, that's what you meant by linking?

    All in all, sounds like too much of a hassle to get this to work, especially w/o documentation/help from forum members.

    I only mentioned h.264 because the Doom9 people seem to think that h.264 is the reason Avidemux will win out over competitors like Virtualdub, once the kinks are ironed out. So I decided to try to use Avidemux instead of Virtualdub, for that reason. However, Avidemux is sounding more and more like a continual beta, so I will just use BeSweet and be done w/ it.

    I didn't mean to sound ungrateful, but I couldn't understand anything you were posting earlier.

    UPDATE: Avidemux is officially deleted from my computer.

    Peace.
    Quote Quote  
  10. Member
    Join Date
    Dec 2004
    Location
    Australia
    Search Comp PM
    2.1 is the stable branch. Basically that means a feature freeze. Only bugfixes from the non stable branch are ported. Recent 2.3 builds are reasonably stable though. The reason people at doom9 say that Avidemux will win out over VDub is because avidemux isn't based on VfW. The fact that it is cross platform I think helps to.

    You don't have to compile it, since I and others provide win32 binaries.
    http://fixounet.free.fr/avidemux/win32/
    http://home.wildit.net.au/celticdruid/mirror/avidemux/
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!