intfiction.org

Here's a copy of spy1.blb that I know works in Windows Frotz, Unix Frotz, DOS Frotz, and sFrotz. It also tests good using blorbScan and I can extract all the contents using rezrov. Here is also a copy of the bad blorb.

_________________
David Griffith

Yes, that looks good to me.

Any ideas on the bad one?

_________________
David Griffith

Looks like a bad length field? Not off-by-one, but completely screwy.

The chunk length on the first AIFF chunk is 1933246464, or 0x733b0000. Maybe that's supposed to be 0x733b, although that doesn't match any of the lengths in the valid blorb file. I think it's just wrong.

What happens if you use the Windows Inform 7 IDE to build the second game I posted and wrap it up with two AIFF files?

_________________
David Griffith

I don't know why I didn't fully appreciate this problem at first. It seems that rezrov.c has a bug in it that causes it to create invalid AIFF files when extracting from a Blorb file. Those files I extracted from spy1.blb I then tried to reencapsulate into another Blorb. That's where my problem started. But still, there's code in perlBlorb and cBlorb that is supposed to pad chunks if they're not even, but the code doesn't seem to work.

_________________
David Griffith

An odd-length AIFF file is technically invalid, but I think we're on the wrong side of Postel's Law there. Lots of them exist, and AIFF-playing libraries accept them, so they're never going to go away. We should pass them through the Blorb layer unchanged.

Whoops, I edited something and you responded to my old post.

_________________
David Griffith