Which version of Quicktime and QT MPEG2

[jridenour]

We've been testing ffmpeg to convert QT files to run a in very proprietary system. (Requires only muxed mpeg 2 stream files at a certain bitrate) We tried it on a Mac mini and works well except it takes a very long time to encode. We are encoding it in an MPEG2 mux for streaming. However, we decided to move the ffmpegx to our G5 in hopes to sped things up. It won't encode. Hit the "encode" button, the little sundial spins once and that's it. The progress window does not pop up and it appears nothing happens. Since it works on our Mac mini (10.4) and QT 7 and it says it works on 10.3, the only thing that is different is the G5 is still using QT 6. Since I could not find any documentation saying which QT was required, I believe that may be the problem.

Also, the Mac mini has the QT Mpeg2 encoder, the G5 does not. Not sure if that has anything to do with it.

Thanks

[Case]

We've been testing ffmpeg to convert QT files

What kind of QT files (codecs)? Do they play equally well on QT 6 and 7, as you seem to be mixing these versions in your workflow?

we decided to move the ffmpegx to our G5

You didn't actually move the installed app, did you? Did you try re-installing on the G5 with a fresh download of the app and the binaries?

The progress window does not pop up and it appears nothing happens.

Even on failed encodings, the progress window should still come up.

the G5 is still using QT 6.

Depending on your source files, QT 6 should work. (H.264 is an example of codec addition in QT 7.)But your rationale for not updating to QT 7 is beyond me. QuickTime 7 came out ages ago (on April 29, 2005).

Since I could not find any documentation saying which QT was required, I believe that may be the problem.

ffmpegX can use QuickTime to decode files, if this option is selected. In those cases it is essential that QT plays the source files satisfactory. See also the comments about QuickTime mentioned in the Product requirements (bottom of the page).

the Mac mini has the QT Mpeg2 encoder, the G5 does not.

A QT Mpeg2 encoder is not used or accessed by ffmpegX.

[jridenour]

I'm sorry I was in a hurry last night and didn't explain myself to well.

First, the G5 is our main FCP editing system. It uses an old Pinnacle Cinewave card that is no longer supported and never approved for QT 7. THAT'S why we use QT 6. (Some have upgraded to 10.3.9 and QT 7 and got it to work but not without headaches. The Cinewave will be replaced in a month anyway and it works now for what it is intended for just fine.)

The Mac Mini was only a temp solution to a huge problem. We use Final Cut on it and everything works on it (including ffmpeg). A 10 minute video file is exported out to the QT animation codec making about a 1.5 gig QT file. That file is then dropped into ffmpeg and roughly 40 minutes later, we have a muxed MPEG2 streaming file (about 200 - 300mbs). That file is then put in the MX-5 Channel Controller which only likes those MPEG2 streams and it rolls out onto the cable channel. Doing this channel was forced upon us and we did not have any budget or equipment to take it on. Thus the mac mini to produce the media. (When bosses start screaming, you just get it done with whatever you have, damn the torpedoes full speed ahead). Problem is we have anywhere between 3 - 7 of these 10 minute vids to produce a day (not counting the editing) and at 40 minutes a pop, you can see why we want the G5 to handle the heavy lifting.

We downloaded and installed the binaries and ffmpegx to the G5. (We didn't move anything, just the workflow, bad choice of words). Set everything exactly to the settings on the mini and nothing. We have problems with Cinewave interfering with QT programs, but I unchecked "use Quicktime" in the options on ffmpeg and tried the mplayer instead (I also tried it without anything checked). The QT 7 file off the mini runs fine in QT 6 on the G5. Again no go on the G5. No progress window. The ffmpeg window just sits there, the enocde button slightly pulsing and the "Save as" line does add a suffix to the name, but nothing more.

I'm getting ready to actually edit a spot on the FCP (which makes us a hell of a lot more money than that damn channel we've been forced to do), so I probably won't get a chance to work on it until later.

We love the program, it really saved us to begin with, but on a Mac mini, just too much time (of course, you can't explain anything to screaming bosses).

Hope this answers your questions, I apologize for not being to clear first time around.

Jim R.

G5 Dual 2.0 ghz, 3 gigs ram, 160 HD, 10.3.7, QT 6

[major]

Check that your disk name has no spaces or special characters. Check that you installed ffmpegX in /Applications. To be sure, redownload the dmg and reinstall again. Also enable "Open terminal window" in the ffmpegX menu in the apple bar.

[jridenour]

Well, this gets even more strange...

Installed ffmpegx on our old Dual 1 gig G4 - works like a charm, cut the conversion time in half.
Tried again on the G5, even removing the Cinewave components. Still nothing. Watched the activity monitor and realized ffmpeg was crashing. So I copied the crash report and here it is

Host Name: FCPCinewave.local
Date/Time: 2006-10-24 14:57:50 -0500
OS Version: 10.3.7 (Build 7S215)
Report Version: 2

Command: Progress
Path: /Applications/ffmpegX.app/Contents/Resources/Progress.app/Contents/MacOS/Progress
Version: ??? (???)
PID: 483
Thread: Unknown

Link (dyld) error:

dyld: /Applications/ffmpegX.app/Contents/Resources/Progress.app/Contents/MacOS/Progress can't open library: /usr/lib/libstdc++.6.dylib (No such file or directory, errno = 2)

Apparently, it's not finding some library just before the progress window pops up. Program crashes but doesn't quit. As I figured, this is definitely on our end, but have no idea how to fix it. Oh, well, we'll use the old G4 dual for now and hope once our new FCP system is up and running, we can completely start from scratch on the old G5 (wipe everything, start anew!)

I want to thank you for the terrific program and support here.