From Allen on various mailing lists:
Just an update, as I know many are interested. Early next week we plan to deliver a fix for the text line spacing (height) issue in Shockwave 11.5 to the Shockwave pre-release testers. Expect a Shockwave update following that session. Normally such cycles take a minimum of two weeks. (We added a permanent Shockwave pre-release beta testing group, which will always be able to activate for various Shockwave updates.)
Danny K, a couple of the imaging lingo errors you reported were verified and marked to fix, but aren’t planned for this short term update. Apparently they existed in 11 as well. (performance issue on 8 bit imaging objects)
Sound concerns re the removed audio compression settings on export. The simple answer is that mp3 files are substantially more optimized and are the preferred file format in order to deal with pre-compressing audio. I think the larger community concern is that legacy projects may contain high volumes of wav files and that absent the ability to “compress at once” and store in cast it becomes untenable to imagine dealing with huge stores of files to convert to mp3. I’ve asked engineering to give me some options / perhaps a white paper for handling conversion as such. I imagine that it would be simple enough to simply write a widget in Director now that we can save mp3 etc. to just rip through the sounds in a project and save all the wavs as mp3 sounds. I’ll let you know when I either get something back substantial, or I come up with some kind of pipeline myself. Perhaps others have given this some thought as well.
3 comments March 31st, 2009