QTIndexSwapper v1.4.2 update

Posted on August 14, 2008 | 6 comments

UPDATE: Get the latest here!

This release is a bug fixed around reading atom’s that are not more than 8 bytes. Thanks to Brandt Michael for pointing out the bug. I guess it affected mp4′s coming from ffmpeg.

Share the post "QTIndexSwapper v1.4.2 update"

  • Rick

    Great tool! But it is drag and drop could it also work in a sort commandline for automating process?
    Please help!

  • http://www.prolefeedstudios.com Brian Standing

    I’m trying to run QT Index Swapper 1.42 on an MP4 file produced by Sony Vegas 8.0c (Main Concept AVC encoder). I keep getting the following error:

    File.size: 195393916
    Reading Atom Metadata: [code: ftyp,size: 24,offset: 0]
    Reading Atom Metadata: [code: mdat,size: 194733721,offset: 24]
    Reading Atom Metadata: [code: moov,size: 659601,offset: 194733745]
    Reading Atom Metadata: [code: uuid,size: 570,offset: 195393346]
    ACTION: Parsing Bytes for Information 195393916
    ERROR: encountered non-QT top-level atom (is this a Quicktime file?)
    Completed Time: 3.633s

    Any ideas?

  • http://www.solovj.com Cliff Etzel

    I wrote a how to article for working with Vegas Pro 8.0b to render out an MP4 file and apply QtIndexSwapper and it worked great.

    Now I’m getting the following error message when trying to apply QtIndexSwapper to an mp4 file rendered out in Vegas Pro 8.0c:

    When I run the QTIndexSwapper (v1.42) step, I get the following error:

    File.size: 195393916
    Reading Atom Metadata: [code: ftyp,size: 24,offset: 0]
    Reading Atom Metadata: [code: mdat,size: 194733721,offset: 24]
    Reading Atom Metadata: [code: moov,size: 659601,offset: 194733745]
    Reading Atom Metadata: [code: uuid,size: 570,offset: 195393346]
    ACTION: Parsing Bytes for Information 195393916
    ERROR: encountered non-QT top-level atom (is this a Quicktime file?)
    Completed Time: 3.633s

    I've tried to render out numerous mp4 and mov files all with the same type of error message

    Any ideas why?

  • http://www.renaun.com Renaun Erickson

    It clearly doesn’t like the file but you would have to look at the file and see if there is something weird with the atoms.

  • http://frenchytech.com abds69
  • http://starpause.com/ k9d

    I’ve found that Adobe Media Encoder CS4 v4.2.0.006 places the moov atoms where they belong for progressive downloading of .f4v files (at the start).