Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums AJA Video Systems Quicktime Error -2048

  • Quicktime Error -2048

    Posted by Tom Bell on March 12, 2010 at 11:28 am

    Hi,

    I have a dual boot Nehalem Mac Pro running OSX 10.5.8 and Windows XP with an AJA Xena LHe that works also as a Kona on the mac side.

    I usually capture video on the Mac side to Quicktimes using the Prores HQ 422 codec as this is sufficient for my needs. Then I encode to AVC (for BD) on the PC side which requires the use of Quicktime for Windows to decode the file. This workflow has been working fine for quite a while now!

    So recently I had a few captured HD files that I needed to encode and found that Quicktime won’t play (decode) any of my captured Quicktimes, giving me an error “Quicktime can’t find the required codec. Error -2048”. I know this is not correct as some files (captured a while ago) play fine and looking at the file info I can see they are the very same codec!!

    The only thing I can think that has changed is that I upgraded to Final Cut Studio 3 recently and since doing this Quicktime (on the Mac side) has some extra Prores codecs available (Prores 4444 and another). Even though Im not using the new ones maybe the upgrade also changed the existing Prores codecs which haven’t been updated on the Windows version yet? Would that make sense?

    Anyway, any speculation on how Apple can screw things up for me next so I can prepare for it would be welcomely received!!

    Thanks,
    Tom.

    Tom Bell replied 16 years, 2 months ago 2 Members · 2 Replies
  • 2 Replies
  • Jeremy Garchow

    March 15, 2010 at 7:35 pm

    I would assume that the QT for windows hasn’t been updated with the v2 ProRes QT component.

  • Tom Bell

    March 15, 2010 at 8:59 pm

    Thanks Jeremy. I guess Ill just haver to wait for an update!
    Apple seem to keep trying to trip me up here and there!

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