Jump to content

Recommended Posts

Posted

When I try to add an ogg file an error window is displayed with the message "external exception EEFFACE".

Flac and mp3 files are added with no problem. It also displayed a filter problem before the above message, but I installed Xiph.Org Ogg codecs and it disappeared. Thanks for any help you can give.

Posted

No it doesn't do it with all files and I just found that in the files that the problem occurred, in metadata there was a field called <COVERART_UUENCODED> and had ASCII characters in it. I ripped the cds with Easy cd-da extractor. Once I removed that field with mp3tag, the problem was gone.

Posted

If you still have an example of such a problem file, I'd like to have a play around with it myself to check the crash was in the directshow filter and not ImgBurn itself.

 

Is there any chance you could email it to the support address in the program's 'About' box?

Posted
If you still have an example of such a problem file, I'd like to have a play around with it myself to check the crash was in the directshow filter and not ImgBurn itself.

 

Is there any chance you could email it to the support address in the program's 'About' box?

 

Done!

Posted

Thanks.

 

Now I'm no expert on the ogg/vorbis comments but it would appear to me that the field length of the COVERART_UUENCODED is wrong in the file.

 

It lists it as 32250 bytes when in actual fact it should be 32558.

 

Comments are laid out like this...

 

 

As such, ImgBurn tries to read the next comment's length from a place that's in the middle of the previous comment and is then getting some huge value for the length - which the program cannot then allocate memory for and it causes a crash.

 

I've implemented a sanity check whereby if the comment size exceeds the file size it'll just bomb out of parsing the comments.

Posted
Thanks.

 

Now I'm no expert on the ogg/vorbis comments but it would appear to me that the field length of the COVERART_UUENCODED is wrong in the file.

 

It lists it as 32250 bytes when in actual fact it should be 32558.

 

Comments are laid out like this...

 

<length 1 (size = 4 bytes)><comment 1 (size = 'length 1' bytes)><length 2 (size = 4 bytes)><comment 2 (size = 'length 2' bytes)>

 

As such, ImgBurn tries to read the next comment's length from a place that's in the middle of the previous comment and is then getting some huge value for the length - which the program cannot then allocate memory for and it causes a crash.

 

I've implemented a sanity check whereby if the comment size exceeds the file size it'll just bomb out of parsing the comments.

 

 

Thanks for the answer. I will stay away from cover art from now on. :)

 

An excellent program by the way, I 've kissed other burning programs goodbye.

Keep up the good work!

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.