nspindel

Thanks for all the replies. As for the question about whether it is on the hard drive or cd, I tried it both ways. Neither one yielded good results. I'm going to experiment and see what happens if I cut the mp3 apart into smaller files, perhaps that makes some difference in the way the exe manages its memory. I'll also try cutting down some of my jpeg resolutions. Some of them are pretty high, so the files are large. If that doesn't work, then the folks I distribute this too will just have to upgrade to a nice fat new PC (or suffer).

I recently created a show with about 450 jpeg pictures and a 45 minute mp3 soundtrack. The soundtrack is one continuous mp3, not separate songs. I synced the show using the timeline and Al Robinson's spreadsheet (great work, Al). The slideshow works great on my machine, which is 2.4ghz P4 with a gig of ram. When I go to play it on a slower machine (400mhz P2 w/ 256 megs of ram), I get sub-par results. The syncing remains intact, but it seems the slideshow trips over itself in several locations. Either the music "skips" rather like an LP record, or pictures either stay up longer than you would expect or shorter than you would expect. But the end result is that if the show does somehow get confused because of a slow processor, it corrects itself in these annoying ways. Also, the fade-in/out is awful on this type of machine. I am wondering what else I can do to optimize this show for an audience with potentially slow machines. Perhaps I need to split the soundtrack up into separate files? If I do that, do I run the risk of different machines putting or not putting pauses between the tracks, which would throw my sync off? The current executable is about 125megs on disk.