File error in Flask and Xmpeg

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Angie
    Junior Member
    Junior Member
    • Jan 2002
    • 28

    File error in Flask and Xmpeg

    Both the latest Flask Mpeg and Xmpeg give the same error as soon as I set them to encode into AVI:

    "An error occurred when trying to generate the file. Check that you're not using the output file, or the program is set up correctly"

    If left with the dialog open for a couple of minutes, both will crash and Windows shuts them down.

    This is on Windows 2000. I'm running as Administrator, so permissions shouldn't be a problem, no other programs are running. Still, I get the error. This happens in 1-pass and 2-pass mode.
  • Trancemaster
    Snoogins
    • Dec 2001
    • 149

    #2
    Just make sure you're not trying to save your .avi in the same directory as your input
    Snooch to the Nooch!

    Comment

    • Angie
      Junior Member
      Junior Member
      • Jan 2002
      • 28

      #3
      That isn't it

      I've made sure files are in different folders. I think something may be up with file permissions, but I am running in admin mode. Could these programs somehow run under their own inferior permissions?

      Comment

      • harold_smith8
        Junior Member
        Junior Member
        • Dec 2001
        • 1

        #4
        I got this off of a search of newsgroups on Dejanews.com and it worked for me. I was having the same file error with XMPEG 4.2a, but not FlaskMPEG 0.6 Preview?

        It's a codec problem. Install an MP3 codec like radium or lame. Then disable any other mp3 codecs
        (control panel>sounds>hardware>audio codecs) and you'll
        be fine. It's a WinXP prob.


        Hope this helps.

        Comment

        • Angie
          Junior Member
          Junior Member
          • Jan 2002
          • 28

          #5
          Thank you! I found two mp3 codecs in the control panel (BTW, in Windows 2000 it's in Device Manager : Sound, video and game controllers : Audio Codecs), one "professional" and one "advanced." I found in the Radium FAQ on my machine that the Radium codec will be the one listed as "professional" so I disabled the "advanced" one.

          Works great now. Now I just wonder if this will mess up any other applications, but I can always disable it for DiVX encoding and re-enable it afterwards.

          Comment

          Working...