Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy What’s up with these quicktime -2048 errors?!?

  • What’s up with these quicktime -2048 errors?!?

    Posted by Matty@switch on October 1, 2005 at 4:30 pm

    Hi all-

    Ok.. I’m at my wit’s end. I’ve been hitting the wall with this problem for the last 3 days as my
    client’s patience quickly evaporates. I can’t lick it! Has anyone else been in this pickle before??
    no… didn’t think so 😉

    Here’s the deal: Captured a 99min HD feature (1080i) from HDCam in 20 minute chunks (due to
    a 60% full XRAID). Used a Blackmagic HDLink Pro card and captured using uncompressed BM 10-bit
    codec. Resulting captures were cut into timeline and rendered off using the same codec to a single
    file using Quicktime conversion. The resulting 720GB .mov can be opened from my XRaid in the finder
    and in Quicktime with no problem.

    However, once I copy the file to the client’s 1T LaCie portable (a fun 5-hour copy!) the file is no
    longer recognized by Quicktime. Sure, it has a Quicktime icon in the finder, but there is no preview
    available and once I launch it into Quicktime player I get an error -2048 “Quicktime doesn’t recognize
    this filetype”. WTF?!?

    I have tried every method I can think of to complete this process in alternative ways. I’ve rendered
    directly to the LaCie drive… I’ve Un-installed Quicktime, and the Blackmagic drivers and re-installed.
    I’ve tried different versions of Quicktime and the BM drivers. I’ve tried different external disks (three
    different at this point). I’ve tried mounting the externals on a different computer. I’ve tried different
    cables. I’ve tried re-capturing several times, and have run every diagnostic I have including Disk Utility,
    Disk Warrior, Symantec, etc. I’ve used the Blackmagic Deckcontrol utility to capture. I’ve reset P-Ram,
    trashed preferences all to no avail.

    I’m not aware of any filesize limitations with Quicktime, but interestingly enough, when I rendered small
    chunks of the video out to the external drives (a 200mb chunk) IT was recognized no problem. I wondered
    if the Mac file system had issues with large files in the root directory, and tried copying to a sub-directory
    but that didn’t work either.

    This is a process I have done many times in the past for these clients – always without a hitch. The only
    thing that has changed recently in my system was a power outtage we experienced two weeks ago. Didn’t
    see any adverse affects at the time, but I wonder if this has anything to do with anything…

    Any input would be great!!

    -Matt

    MY System Specs:
    Dual 2.5 G5 w/ 2.5gb ram
    OSX 10.4.2
    Quicktime 7.0.2
    Blackmagic 5.1
    FCP 5.0.2
    XRaid 2.7T
    Apple Fiber Channel Card

    Matty@switch replied 20 years, 10 months ago 2 Members · 5 Replies
  • 5 Replies
  • Annaël Beauchemin

    October 1, 2005 at 5:21 pm

    is the Lacie formatted in HFS+?

    If it’s FAT32, there *is* a 2gb limit. If it’s NTFS, it’s read only.

  • Matty@switch

    October 1, 2005 at 10:14 pm

    No… Its OSX Journaled

  • Matty@switch

    October 1, 2005 at 10:14 pm

    No… Its OSX Journaled

  • Annaël Beauchemin

    October 2, 2005 at 4:40 pm

    in my experience, this error means somethings like “end of file was reached prematurely”. So either the file is corrupted when it is written on the Lacie or when it is read on it.

    Did you try copying back the file to the Xraid? Is the Lacie one of those funky drive with two drives inside RAIDed toghether?

  • Matty@switch

    October 4, 2005 at 12:39 am

    Yes… It must be one of the funky LaCie drives with two 500gb raided together… only way I can figure
    how they got 1T in one small case.. are there known issues?

    an update:
    Under Apple’s supervision I have upgraded my XRaid’s firmware, pulled and cleaned all connectors,
    pulled the raid controllers and reseated them, and pulled the fiber-channel card and reseated that.
    I have noticed some improvement, but haven’t fully tested my problem out yet…

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