Having to reinstall files each start

[SeveralButchersApron]

Each time I start the program a dropdown shows up asking me to reload mpeg3enc, mencoder and mplayer. Is there a way to make this path permanent?

Many thanks,
SBA

[SeveralButchersApron]

Oops -- that's mpeg2enc...

[drewincanada]

I'm having the same problem. Did anyone post a solution?

Every time I launch, the "ffmpegX components self-installer" pops up and asks me to install the binaries.

They ARE installed, though. I checked the library/application support/ffmpegX folder, and they were installed properly the first time.

Odd thing is, if I click "Cancel" and don't reinstall them, the application seems to work fine.



Mac OS 10.5.6 -- Intel processor.

[SeveralButchersApron]

No resolution here. Still have the same issue. And same result as you...

[Case]

Your two setups likely have something in common that is different from what other users have.
At launch, ffmpegX tries to check the validity of the binaries. If this check returns a "something's wrong" status, then the installer window will pop up.
- Are there any special characters in the boot volume name? The author suggests "Macintosh_HD" to be safe.
- Does your user account have admin privileges? Is the user account for working with ffmpegX the same as the user account for installing ffmpegX?
- Is ffmpegX in /Applications on the boot volume? Avoid putting ffmpegX in a subfolder with characters that ffmpegX may not like, such as spaces and special characters.
- Are all binaries mentioned in red in the installer window? If not all, which are in black, which in red?
- Do not put the binaries manually in /Library/Application Support/ffmpegX/ . The installer does a few more things than just installing and altering the three files. You should let it do so.
- Did you see more items in /Library/Application Support/ffmpegX/ ? The installer should put a few more binaries in there as well.
- Are the three downloaded binaries from the URLs given in the installer window? Only the validity of those binary versions will pass the test. (If you purposely use an older or newer version of e.g. mencoder, then it is expected that the installer window pops up.)
- If you choose to re-install, remove the old files first.

Odd thing is, if I click "Cancel" and don't reinstall them, the application seems to work fine.

Did you try to let ffmpegX use all three binaries? Try a mencoder conversion to test mplayer and mencoder. Try an mpeg2enc conversion. Do these work well?

[antoniong]

I have the same problem (and maybe more people have it but do not report it). My answers:

- Are there any special characters in the boot volume name? The author suggests "Macintosh_HD" to be safe.

Nothing special.

- Does your user account have admin privileges? Is the user account for working with ffmpegX the same as the user account for installing ffmpegX?

User is admin and install was done by same user.

- Is ffmpegX in /Applications on the boot volume? Avoid putting ffmpegX in a subfolder with characters that ffmpegX may not like, such as spaces and special characters.

That's where it is.

- Are all binaries mentioned in red in the installer window? If not all, which are in black, which in red?

It is always mpeg2enc

- Do not put the binaries manually in /Library/Application Support/ffmpegX/ . The installer does a few more things than just installing and altering the three files. You should let it do so.

I did.

- Did you see more items in /Library/Application Support/ffmpegX/ ? The installer should put a few more binaries in there as well.

There are 15 files in that folder.

- Are the three downloaded binaries from the URLs given in the installer window? Only the validity of those binary versions will pass the test. (If you purposely use an older or newer version of e.g. mencoder, then it is expected that the installer window pops up.)

Yes.

[Case]

It is always mpeg2enc

Try re-downloading (Alt-click/Control-click) the mpeg2enc.intel binary using a different browser. Alternatively, try this zipped copy, as .zip files cause less confusion (for both browsers and users). Unzip using the Mac-OS-built-in decompressor BOMArchiveHelper. The (unzipped) file size should be 492 KB (501,480 bytes).

[antoniong]

Using your zipped mpeg2enc apparently solved the problem.


Strang, but thanks!

[SeveralButchersApron]

Thanks for all your help. I'm still having trouble. I d/l'd the mpeg2enc.intel and dragged it into the folder where the others are, then deleted the one that had been there. Not sure what to do next. All the answers to the questions asked about are positive, i.e., no glitches there.

Thanks!

Dave.

picture%202.png

[tomlee59]

You shouldn't have to drag anything. Let the install script move things to where they belong. If you're guessing, you'll guess wrong.

Follow this procedure:

1) Download the bits to any folder. Unzip anything that's zipped.
2) Point the installer to the unzipped bits.

That's it. Don't drag stuff, don't copy anything. Let the installer do its job. Don't second-guess it.