Wonder if anyone can help me make sense of this?
I have recently purchased a new PC running XP Home on an Intel dual core 2.4 ghz cpu, 2gig ram, an Asus P5B-E motherboard with a Gigabyte GV-RX165256D-RH Radeon X1650Graphics accelerator which uses a PCI Expressx16 slot. I've plugged my Pulsar 1 card in & loaded Scope v4.0.
If load a mixer with an ASIO 24 bit source driver with 16 chnls & an ASIO 24 bit destination driver with 16 chnls + 2 instances of masterverb then load up Cubase SX3 I get the PCI- Master-Overflow error msg.
If I do exactly the same thing but swap the 24 bit ASIO drivers for the 16 bit vsns, I don't have this problem.
I have set the scope to max latency & sample rate is 44.1 khz. I have tried the Pulsar card in a different PCI slot but to no avail.
I'm trying to achieve 24 bit recording.
I'd appreciate any advice you can offer.
PCI-Master-Overflow msg!
well, that mobo is known for a very good PCI performance - it's the limit of the Pulsar One you run into...
I get the exact same result, if those 16 'channels' are stereo
with 16 mono channels the 4th masterverb will cause the overflow
I habe 3 Pulsar Ones in the box and no more than 5 masterverbs (active) are possible under whatever circumstances, as you can see active(!) Asio channels reduce that number.
Scope seems to ignore the Asio load as long as just the 'module' is loaded in the project, but no sequencer with the respective number of channels is running.
cheers, Tom
I get the exact same result, if those 16 'channels' are stereo
with 16 mono channels the 4th masterverb will cause the overflow
I habe 3 Pulsar Ones in the box and no more than 5 masterverbs (active) are possible under whatever circumstances, as you can see active(!) Asio channels reduce that number.
Scope seems to ignore the Asio load as long as just the 'module' is loaded in the project, but no sequencer with the respective number of channels is running.
cheers, Tom
It doesn't ignore the load, there's nothing running on the cpu that loads the asio driver until you run something that uses ASIO.
Something to think about with ASIO, you don't need the same number of destination channels as you do source channels. You only need as many destination & source channels as your workflow requires. I personally use about 6 ins max at any time (2 for a full stereo mix, and 4 extras for recording external sources, printing fx & scope synths, etc). Also, if you're using 16 ASIO outs (source module) from your sequencer I assume you're mixing on a Scope mixer? A bit of buss mixing (mix some elements to stems) in Cubase might be able to help you reduce the number of channels you have loaded in the source module.
16 bit versions of the ASIO driver have less overhead because they have 1/3rd less bits than 24 bits, of course.
Astroman is telling you that the Pulsar 1's PCI performance isn't the same as the 'second generation' cards, which also get lower latency in the ULLI settings along with the improved performance. I added a Puisar2 to my Pulsar1 and made sure the P2 is the primary card and a lot of my old issues vanished.
Also consider using a tool like Doubledawg to reduce the PCI latency of your ATI card to 128 while you're doing audio work (it's probably set to well over 240, out of a possible 0-255). Read more on the Doubledawg page, which you can easily find at google.
Something to think about with ASIO, you don't need the same number of destination channels as you do source channels. You only need as many destination & source channels as your workflow requires. I personally use about 6 ins max at any time (2 for a full stereo mix, and 4 extras for recording external sources, printing fx & scope synths, etc). Also, if you're using 16 ASIO outs (source module) from your sequencer I assume you're mixing on a Scope mixer? A bit of buss mixing (mix some elements to stems) in Cubase might be able to help you reduce the number of channels you have loaded in the source module.
16 bit versions of the ASIO driver have less overhead because they have 1/3rd less bits than 24 bits, of course.
Astroman is telling you that the Pulsar 1's PCI performance isn't the same as the 'second generation' cards, which also get lower latency in the ULLI settings along with the improved performance. I added a Puisar2 to my Pulsar1 and made sure the P2 is the primary card and a lot of my old issues vanished.
Also consider using a tool like Doubledawg to reduce the PCI latency of your ATI card to 128 while you're doing audio work (it's probably set to well over 240, out of a possible 0-255). Read more on the Doubledawg page, which you can easily find at google.
Yes, I was a bit blurry in the expression... I referred to the PCI load in the way an 'unconnected' masterverb seems to reserve capacity (I dunno the internals, but that's how it looks).valis wrote:It doesn't ignore the load, there's nothing running on the cpu that loads the asio driver until you run something that uses ASIO...
When I add the Asio modules, set their number of channels and connect them to mixer and Adat ports, I can still load all 5 possible masterverbs - as long as I don't load a sequencer... with the full number of Asio channels active
It's just a irritating the first time, no big deal.
Your tips should sort it out, either by optimizing the required # of channels or by adding a 2nd generation card.
cheers, Tom