1 person found this helpful
I would be inclined to blame QuickTime for the crash you describe. If it's the "standard" Windows crash dialog you can click the 'more info' link and examine implicated modules. When you do so, look out for the first xtra, Director-related dll or QuickTime-related dll file cited. This can often give you an idea of the culprit.
Try turning off acceleration and test again: go to Control Panel -> QuickTime, activate the Advanced tab and deselect 'Enable DirectDraw acceleration' and 'Enable Direct3D video acceleration'
Which version of QuickTime is installed on the machine/s you tested on?
Thanks for the tips. Unfortunately turning off the acceleration preferences in QT control panel didn't help. Neither did adding member(pSelectVideoMember).unload() to the endSprite handler of the Quicktime elements. I didn't try deselcting streaming in Director as I think this wont make a difference.
The computers are running QT7.6
I've noticed that the Quicktime asset xtra is 6. Could this have a negative effect?
The dlls reported in the error report are the general projector .dlls that are added to an xtras folder. msvcr71.dll, msvcp71.dll, proj.dll, ImL32.dll, msvcrt.dll, Imm32.dll, Dirapi.dll. These were littered in that order throughout about 20 other modules that listed other general windows dlls.
It is starting to crash more consistently on the 17th or 18.dir...usually stuttering on the last clips in 17 then crashing in 18. But I don't know what this really could tell you, all 27 dirs are duplicated. The text memebrs just have different text typed in them, and the video placeholders contain code to switch to the appropriate video member.
Since the error doesn't list the QT asset could there be a different problem? The only thing leading me to accuse the video is that it didn't crash when I only looked at text, or by skipping 3/4 of the videos. Once I look at all the video elements it crashes. I did write code that resizes and repositions all the stage elements based on a global in the beginmovie handler. ( i tried reading desktop rect list and using drawRect but text and basically everything looked like crap so I didn't use it).
Quicktime was not the culprit, or so it seems anyway. I commented out all the code in behaviors used for reposition and resize of stage elements and found that it didn't crash anymore. Why would this be fine on a mac, and not on a PC? Unfortunately a major part of the DVD is cut off when not resized.
I am not really great with globals... I must need to unload them when moving to the next dir on an end movie handler.
I think I am just going to make 4 different sized duplicates of my dirs and link to them from the start menu. I didn't really want to do this cause of the shear amount of dirs I would have to resize by hand but seems like the solution with the least amount of potential problems.
Why oh why doesn't a full screen director projector just resize and fit itself to a users screen? Is this really 2009?
I've had a similar problem working with dir 11.5 on the Mac. While testing the .dir file with lots of videos it eventually won't play the videos. Sounds like a memory management problem in Director to me.
I have the same problem. I can run a dir file in director 11 just fine, but when I create a projector the app causes a problems that makes windows close the app. I have tried several different codecs, h264, prores422, motion jpegB and I have tried a test score stripped to the waist and still have the same error. Has anyone solved this issue?
Are you testing on Windows XP with service pack 4 or higher? That
seems to be all that dir 11 supports. I've had to go back to dir 9
to get director projectors that work on XP with service pack 3 or
earlier windows platforms (included win 98). But you have to have
both a windows and a Mac version of director 8.5 or 9 to make
projectors for both platforms, and I don't know if you can even buy
them any more!
The movies in my programs also require quicktime for windows, which
is a free download, and that seems to be working fine for my movies
(created with imovie).
The Windows XP Pro version 2002 Service pack and has Quicktime installed. The movies play fine in Quicktime player. What is really wierd is that in Parallels on my mac the app works just fine. I have Director 11 on both platforms and have compiled the app in place. The quicktime plays while director is running. It only crashes when a projector is made and run.
Failing application stAnthony4.exe, version 11.03.466, faulting module quicktime.qts, version 188.8.131.52, fault address 0x0086b09e
Quicktime version 7.6.2 (515)
Dell Vostro Quad @ 2.83Ghz, 3 GB ram
That is really weird. I gather that Parallels is a windows emulator
on the Mac, correct? If you've verified that the windows machne is
running XP service pack 4 then it sounds like Director is at fault.
I think you can send them a small app that isn't working and have
them check it out.
There is no windows service pack 4 for XP. Service pack 3 is the last available. Service pack 4 is for servers and NT.
Yes Parallels rums a virtual PC on OSX.
I finally got this to run without crashing. I turned off DTS on the clips. I believe this is a memory problem. But I just guess. The clips are 1440 x 480 scaled up over two monitors. They will only play at 1 frame per second, where on every other machine (mac or windows) they run 30fps.
It is QuickTime that is responsible for your crash, and I suggest you try encoding your video to a FLV file that the Flash Asset xtra can play, using a codec like On2VP6
That's strange... The web site for Director says that the newest
director 11 requires service pack 4, and that it's also compatible
My movies are small, 320 by 240, and I play them direct to stage with
no controller. So far I've mainly been using director 9 for
development and to create projectors that run on XP service pack 3
and lower. I've got to do more testng with the dir 11 ones, but
don't have ready access to machines with vista or XP service pack 4.
I'm out of town now, but will be doing more testing in a couple of
weeks with the dir 11 version. The only testing I've done so far,
with a different file, worked OK. I have my fingers crossed!