Display Server Install

SuperO P4 HT 3.2G, 2G Ram, no video (technically it has some POS ATI 4M server card), 1U rackmounted server

 

The OS

Windows Server 2003 Standard

Loggin in as nonAdmin user (and admin to fix issues)

 

Issues (all fixed)

msconct3.ocx was just not on the server, so that had to be downloaded and registered

Only "Administrator" recieved the desktop and menu Icons

Install did not fully install as non-admin (even though I ran as administrator)

I reinstalled while logged in as admin, everything was fine. I then created shortcuts to the two Aurora files for the user.

The non admin user did not have access rights to C:\Program Files\Aurora Sequencer, I added the user to the ACL.

 

Aurora then worked perfectly. Sequencer AND Scheduler, except...

The audio for the first minute of WiW is just not there, the sequencce is there, just not the sound. After about 1 minute, the audio picks up where it should be at 1 minute. This happens for both the sequencer and sceduler.

 

Side note, playing sequences took about 80% of one if the "cores" of the single cored P4 HT.

CPU... Sequencer  uses nothing 1%? Schedular (for the first song) uses about 1/2 of each core (yes, I know that P4s only had one core,but it's two graphs so "core" is easier to use), after the first song, schedular goes to about 80% of a single core, trading it's running core after seach song.

scedular is useing 50% of the CPU, and about 24M RAM, 10 Threads.

You did ask specifically what file though. "aurora_schedular.exe"

 

I currently DO NOT have the RS485 in, just running schedular. nothing else.

 

Regarding CPU use: The scheduler will use a full "core" during playback.  This is not a bug, although it will be improved in future versions. 

 

Basically, "command prefetch and action deferrment" (for lower CPU use) is a relatively new feature of the Aurora playback engine, so while it is partially (but not completely) in use in the sequencer we intentionally left it disabled in the scheduler until it has seen some more "real world" usage to tweak the algorithm with.  As always, we're "playing it safe" on the "live" part of Aurora (the scheduler) while taking more risks with the "non live" (sequencer) part.  Present "in the lab" analysis says we should be able to get the CPU use down to about 1 or 2 percent after a few more tweaks, but we're not going live with those until adequate testing has been done.