Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy mp3 on FCP 5

  • Erik Lindahl

    May 21, 2005 at 5:29 pm

    I must say this is one of the stranger “non excisitng” features of FCP since day one. FCP relies on QuickTime for most if not all of its media work but doesn’t handle MP3 at all (basically it’s useless). This is of course a very minor issue to most, but it is annyoing that something QuickTime Player or iTunes does easily can’t be done in FCP.

    However, selecting an editing-system based on this is mad. AVID might handle this, but after you’ve imported that mp3-file, try finding the source of it on your HD 😉

    I’m not sure compressor can do MP3 > AIFF conversion, but mostlikely it can. Create a batchfolder and wa-la.

  • Dino Sanacory

    May 21, 2005 at 6:26 pm

    Avid and FCP have fundamentally different core architectures for managing media files. An import into Avid generates a completely new file that represents a conversion of the source file into an Avid specific format. The codec used in the source file is irrelevant (as long as the system can decode it) as the imported media is a new, Avid formatted file. This form of this file is determined by the project settings.

    FCP doesn’t really import media so much as create a link to it. You can place almost any type of media that QuickTime understands into an FCP sequence, regardless of codec, frame rate, frame size, sampling rate, etc… The downside to this is that if the file is not in the same format as the sequence, FCP will need to render it or do a poor real time conversion for playback.

    MP3 is not a native Avid format. Importing them into an Avid simply converts them back into uncompressed media. This is essentially the same step you need to do for their use in FCP, except that it is here a manual process.

    To add my opinion to the discussion, I don’t think allowing lower quality compressed material to work natively is a feature. Fast, portable mass storage via Firewire/USB is so cheap and easy to use, I feel that cost/convenience as an excuse to deliver compressed source material (especially audio) is unacceptable. The time it takes to convert everything to MP3s could just as easily be used to convert to 48K aiffs.

    Dino Sanacory
    Edgeworx, NYC

  • John Davidson

    May 22, 2005 at 9:04 am

    Interesting. Limited functionality and compatability is a benefit. Maybe the program shouldn’t work with DV formats in the future, since we’re pro and all.

    I’m not upset about it, it’s just annoying that it’s like that. Another fun feature is not letting Soundtrack Pro export OMF’s. I also didn’t hear whether or not FCP-exported-OMF’s now contain clip volume information so that your mix transfers over seamlessly to Protools.

    For those of us considering a move to FCP it’s important to be aware of all the issues, large and small, before we commit to it. I’m still on the fence, and FCP has certain features that I am very attracted to, but many of the mixers and editors that work on my projects have voiced concerns that I’m hoping are fixed in FCP5.

    Certainly Avid is a beast and it’s got many quirks, but they are quirks I understand. The last thing I want are surprises that slow production. I’m just gonna wait a few weeks and let the community laud their praises, and curses, about the new version before I make a final decition.

    Deep down though, you guys know it’s weird to not be able to import mp3’s. Apple certainly sells the hell out of them online :-). oh wait, those are Apple M4P’s, but still the same quality as mp3’s. I wonder if those work in FCP….

  • Arthur Vibert

    May 23, 2005 at 9:59 pm

    This seems like a storm in a teacup. Just retransfer the CDs at full resolution and move on if you want to use FCP. Or, if it bothers you that much, stay with Avid.

    Arthur Vibert

  • John Davidson

    May 24, 2005 at 2:12 am

    Even more fun –
    FCP imports MP3’s no problem.

    I knew it had to be a mistake.

Page 2 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy