|
Subject:Acid 4: Long load time
Posted by: wcreed
Date:9/2/2002 5:29:44 PM
Over all, I'm very please with Acid 4. But... It takes almost 30 seconds to load. Yawn... |
|
Subject:RE: Acid 4: Long load time
Reply by: Spirit
Date:9/2/2002 7:07:40 PM
Same here - slowest load time I've ever seen on my P4 |
|
Subject:RE: Acid 4: Long load time
Reply by: Iacobus
Date:9/2/2002 8:40:00 PM
Really? Takes about 8 seconds for me on my PIII 800EB MHz w/384 MB of SDRAM under Windows XP. Note that I don't have anything running in the background. Iacobus |
|
Subject:RE: Acid 4: Long load time
Reply by: Ted_H
Date:9/3/2002 9:05:33 AM
You may want to check for programs running in the background. Press Ctrl+Alt+Delete and choose "end task" for everything except for explorer and systray. Also make sure that your sound card and video card drivers are current, as Acid is accessing both of those devices when it launches. Ted |
|
Subject:RE: Acid 4: Long load time
Reply by: pwppch
Date:9/3/2002 9:38:11 AM
One thing we have noticed is that with certain hardware load times can be long due to the hardware having to be initialized. When we load, we intialize the DirectMusic subsystem of Windows. This causes Windows to enumerate all hardware. With hardware like the Creamware Scope or Pulsar, this can take a significant amount of time as the hardware has to load all kinds of configurations. When the ASIO drivers are hit for hardware like this also, a load routine for the hardware will take place. This can significantly increase load times. What audio hardware? Peter |
|
Subject:RE: Acid 4: Long load time
Reply by: pwppch
Date:9/3/2002 9:38:36 AM
What audio hardware are you using? Peter |
|
Subject:RE: Acid 4: Long load time
Reply by: Spirit
Date:9/3/2002 10:39:43 AM
You got it right again: Pulsar-II As you no doubt know Pulsar/Scope loads a user-definable configuration on boot. Mine's pretty slim with just the wav, asio, and audio-in routings and a couple of mixers. Does AP4 have to "rescan" all this ? btw, the long load time doesn't really bother me, just curious. |
|
Subject:RE: Acid 4: Long load time
Reply by: MacMoney
Date:9/3/2002 10:46:49 AM
It seems slow on the MOTU gear too. I thought it was scanning for VSTi or DX plugins Ron Jones |
|
Subject:RE: Acid 4: Long load time
Reply by: pwppch
Date:9/3/2002 12:41:54 PM
ACID is at the mercy of DMusic and ASIO in this regard. Telling DMusic to intialize causes it to look for any DSound compatible devices, even though we don't use DSound. When we enumerate ASIO devices, the only way to determine that the hardware is actually installed is by creating an instance of the driver. For the Creamware hardware, this forces the driver to load all the config stuff it needs to operate. For some hardware, even if the hardware doesn't exist, it causes a BSOD - the Core32 hardware does this on Win9X. Peter |
|
Subject:RE: Acid 4: Long load time
Reply by: pwppch
Date:9/3/2002 12:44:57 PM
Once VSTis and DXis are scanned initially, things should be pretty fast in here. The only time we re-enumerate plugs is when something has changed. In this case all DX plugs are looked at again and we look for new VSTis that have been installed. One note to this: For the Scope hardware, the XTC plugins actually communicate with the hardware. This can take a significant amount of time to enumerate them the first time. The Plusar actually pops up a progress dialog to indicate this load. Peter |
|
Subject:RE: Acid 4: Long load time
Reply by: wcreed
Date:9/3/2002 1:32:41 PM
I have a PIII 1Ghz, with 1.25Gigs of RAM, An Audiophile and a WaveCenter PCI. The long delay happens before I see the status dialog for scanning for DX, etc. After Acid has loaded once, it re-loads quickly. |
|
Subject:RE: Acid 4: Long load time
Reply by: pwppch
Date:9/3/2002 11:36:02 PM
>>After Acid has loaded once, it re-loads quickly. This is normal. Peter |