Digital Workshop

Hello,
I am curious; what are the benefits of publishing to .exe and .ilm instead of just to .exe?

This is why I'm asking. I am working on an interactive catalog cd for a client, in which I give the user the ability to choose from 5 or 6 songs to listen to while perusing the catalog. I have to embed the music files instead of excluding them as an external link because the license of the files does not allow me to include them on a CD in such a way that the end user can obtain a copy of them. However, this makes for a large .exe that is slow to load and a resource hog.

So what I'm specfically wondering is this: If I publish to an .exe and an .ilm for each chapter, does this mean that .ilm file would only run when that chapter is accessed, and therefore, initial loading of the .exe would be faster?

Thanks,
Mike

The physical splitting of the file into data files should have no effect on the speed at which it is accessed - Opus will always attempt to load elements as needed, rather than all at once. Reading large files from CD will be always comparatively slow.

Make sure your publication pages are in the most commonly accessed order, this will make optimum use of the preloading.

What format are the sound files? If they are WAVs and you are using the Opus sound compression you could try converting them to MP3s instead - this generally offers better compression.

Hi,
Thanks for the answer. My files are in .ogg format, so they're fairly small, but there's a bunch of them.
Last night, I received word that it would not be against the music license for the files to be linked externally, so that's what I'll do.
Thanks again,
Mike