• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: QT -208 error
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: QT -208 error


  • Subject: Re: QT -208 error
  • From: Vassilis <email@hidden>
  • Date: Wed, 11 Apr 2012 19:08:19 +0300

Thanks again for your reply. Informed and explanatory, very concise. I have to get permission in order
to send you a small file (maybe even more) from the person that sent me those files. I hope they won't mind
and will be very happy to send you some.

Best Regards,
Vassilis


On Wed, Apr 11, 2012 at 6:15 PM, Richard Dobson <email@hidden> wrote:
There is a fault with the file, as reported in the screenshot, in that the iXML chunk after the data chunk is shown as starting at an odd-valued address, whereas all chunks should start at a word-aligned address (an odd-sized chunk, as may easily arise with 24bit audio data, should be followed by a pad byte).  Whether that is what is foxing QT7.6.6 I can't say - might not matter if it simply doesn't bother to read non-essential chunks after the data chunk.

One very clever thing about the "sndfile-info" utility is that it does not only report chunk details, it reports any chunk arithmetic or size errors as well. I would like to have a short example soundfile with the same features (i.e. the audio content itself is immaterial, a sinewave would do), to post on a web page I am planning illustrating such odd/wrong aspects of file formats, especially as created by leading industry-standard software. You could be forgiven for thinking those software houses aim to employ best practice in writing soundfiles, but unfortunately the evidence is that they happily play somewhat fast and loose with "so-called standards".

Richard Dobson



On 11/04/2012 14:08, Vassilis wrote:
Hello to all, thanks for the replies.
..

Given that QT X has a rebuilt underlying engine, I think it makes sense
that the modification
in the header simply confuses the older QT 7 and I don't see this
fixable. Of course, I 'd love to be proven wrong, hence my posting
to this mailing list. I found a very handy utility online, bwavreader,
that gave me even more information, those who want can check it out
here, it is a simple png screenshot:

http://www.sendspace.com/file/iuc20x

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >QT -208 error (From: Vassilis <email@hidden>)
 >Re: QT -208 error (From: tahome izwah <email@hidden>)
 >Re: QT -208 error (From: Stephen Davis <email@hidden>)
 >Re: QT -208 error (From: Vassilis <email@hidden>)
 >Re: QT -208 error (From: Richard Dobson <email@hidden>)

  • Prev by Date: Re: QT -208 error
  • Next by Date: Re: QT -208 error
  • Previous by thread: Re: QT -208 error
  • Next by thread: Re: QT -208 error
  • Index(es):
    • Date
    • Thread