Angus Hewlett wrote: > > From: Angus Hewlett <angus@...> > > At 13:58 02/12/99 +0100, you wrote: > >From: "Frank W.Kooistra" <pipeline@...> > > >Pulsar is a quite capable system although it does tax the system rather > >heavily because of the lack of onboard Ram. > > and the stupid, totally over-the-top GUI, which hogs RAM even when you > don't want it - i.e. GUI is loaded even when Pulsar is running in system > tray mode - and uses insane amounts of CPU cycles for its glows, > alpha-blends, shadows, etc. Hmm bit overreacting : but i can imagine if your system is just too small. one does so because of that.My first system was big ( 64 MB ) and it took only 10 minutes to load : all because of extensive swapping .. I do not get what you mean with system tray mode ( I guess when you just see the connection diagram) there is a mode which is quit useful , when you do not need interactive access : this is the mode which is started in winstart.pro : In this mode you can use the card as a multi I/o card with out the overload of gui. winstart.pro is configurable so routing to emagic is possible .. > Pulsar uses _vast_ amounts of memory, up to 40M per device in some cases. > If you're planning on running DAW software on the same machine, you really > do need 256M. It's also a good idea to run it in systray mode and build an > environment or equiv. to control it - that way the graphics can only eat > all your RAM, not your cpu cycles as well :-) > > >The synths on board are great , the modulars are very flexible and > >double as fx units. I/O is clean. > >Extremely flexible is possibilities, but the number of dsp are consumed > >rather quickly > > agreed - but if you take the above measures to stop it hogging the PC's > cpu, you can still run a decent amount of native FX. > > Regards, > Angus. regards Frank w. Kooistra