Sorry about reposting, but would really appreciate any input:

Ok, I've got this client I'm supposed to be creating a type of
sequence/presentation builder using director, and with images, flash, sound,
video, pdf and powerpoint files.

The client THEIR developing this for (sigh...I've got to get the gig at that
level, who KNOWS how much cash their getting for this) has given an
inventory of machines they're using right now - machines as low as 486 with
win95!! Now, we're checking if all these machines are actually going to be
targetted for playback, and what machines we might drop.

So here's the list of questions:
I see that 8.5 has lower requirements than 8.0 (133mhz vs 200mhz Pent -
small difference), and 7 has Pentium (no speed) listed.  I'm going to lean
toward authoring in 8.5 rather than 7 (because hell I can't remember all the
changes since then anyway) -- now for a plain vanilla director app I can go
by the Macromedia specs...but what should I think in terms of

video (mpg1 or QT sorenson or cinepak)
Audio (mp3 compression or not)
Flash (if at all playing in director, ie no alphas)
PDF (play within the app via pdf xtra which is slow or launch externally --
what are the system requirements of the pdf xtra?)
Powerpoint (using Ravware's PPViewer Xtra to play within the app or launch
externally)

Let's just say that the client I'm dealing with isn't very tech-savvy and
don't know director's capabilities -- they've been using it as powerpoint --
and it's one of those cases that I can make recommendations without hard
specs and they look at me like a dog who lost his food bowl.

There's no way that anything is gonna play on anything pre-pentium, but
should I shoot for Pent2?

Any help, recommendations, horror stories, etc is much appreciated.

[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email 
[EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for 
learning and helping with programming Lingo.  Thanks!]

Reply via email to