zero kb on disk...?

[baybutt]

Hello.

This is probably the biggest noob problem but anyway. Here goes.

I'm trying to covert a video (.mov) to 3gp as then I'm told it'll work on my phone (nokia 6300) so I've downloaded ffmpegx and installed the binaries (I think).

I've dragged the file and encoded it etc but the resulting file says zero kb on disk when I look on the info. It doesn't play on the phone as I'm guessing there's nothing in there to actually play. It also is really quick (less than a second for 1.2mb mov file - that is my clue that it's not encoding properly)

What am I doing wrong? There's a chance I haven't installed the binaries properly but apart from the mpeg2enc one which is a text file (is that right) it all looks right. There's only so many times I can try re-installing the program and the binaries.

Can you help? Hope so.

Anyway - thanks for reading this ramble.

All the best.

RB

www.richardbaybutt.com

[Case]

I'm trying to covert a video (.mov) to 3gp as then I'm told it'll work on my phone (nokia 6300) so I've downloaded ffmpegx and installed the binaries (I think).

When you quit and launch ffmpegX again, and the screen telling you about installing one or more of the binaries does not come up, then the binaries were installed correctly. But the conversion to .3gp does not depend on any of the binaries. They are used for other conversions.

There's a chance I haven't installed the binaries properly but apart from the mpeg2enc one which is a text file (is that right) it all looks right.

mpeg2enc as a text file is common when downloaded with Safari. The installer should process it fine anyway: only what is inside the file counts.

I've dragged the file and encoded it etc but the resulting file says zero kb on disk when I look on the info. It doesn't play on the phone as I'm guessing there's nothing in there to actually play. It also is really quick (less than a second for 1.2mb mov file - that is my clue that it's not encoding properly)

Some conversions need certain settings to succeed, depending on the source file. To determine what went wrong, you could click the blue "i" button in the ffmpegX Progress window after a failed conversion. This should pop up a new window called Process Information, a sort of log. I expect the last line reads something like

Codec type mismatch for mapping #0.0 -> #0.0

It means audio and video are reversed (inverted) from what ffmpeg expects from input files. You can fix this by setting the "Invert mapping" checkbox in the Audio tab.

[baybutt]

Thanks a ton. It was the 'invert mapping' bit which was all wrong. The binaries are all in properly if that's the case - no warnings or owt.

Thank you for helping out.

RB

www.richardbaybutt.com