SX2.2 and Scope - glitching BAD

andrew · Post by **andrew** » Tue Sep 06, 2005 1:13 pm

I don't use firewire on the desktop so just disabled that, plus installed the intel and raid controller....

so now my irq looks like this :

http://tinyurl.com/8jawl

I didn't end up having to move my card. Do I need to now reinstall sfp or anything?

Anyhow, in the above state, with CW on it's own IRQ I tried that same cubase project (see previous posts) with the Asio EZ recording CW project, but siwtched out the standard driver for the asio 2 24 bit src driver, and i could move SFP windows around and was almost 100% glitch free - ie with a low load on CW or with very little GUI in CW - not sure which is the cause of the glitches.

Then i tried a cw project with about 60% SFP resources used on my 15dsp scope card (stm4896, a few synths etc), with the asio 2 24 bit src driver. Got regular pops glitches etc.. when i move scope gui stuff this gets much worse. This is the CW project i was using almost glitch free with logic, as i said in my first posts on this thread.

So not much improvement. perhaps i should try increasing the latency? or is there more basic configging to be done?

I still don't understand why cubase should be on lower vst usage when scope is in xtc mode as oppposed to scope mode... do you guys get that?

anyway it's late now and I've got work again tomorrow so I thankyou all for your help this evening, whereever in the world you are

will continue the fun tomorrow night

Andrew

p.s. you can check out the music I've been making with my buddy on http://www.voiceofcod.com
our album is out sept 26

_________________
http://www.voiceofcod.com
http://www.organicrecords.net

[ This Message was edited by: andrew on 2005-09-06 15:14 ]

Post by **garyb** » Tue Sep 06, 2005 5:01 pm

that looks much better.
if i remember correctly, you need to disable busmastering on that video card(in properties in device manager) afair...

another possible work around: open the dvice manager and set the sfp priority to below normal.

if you get no happiness, i would reinstall the os from scratch.(format and reinstall). it's possible that you have some file that's corrupt after all this and starting fresh might be the quickest solution. try reinstalling cubase and the scope first...

once again, i'm assuming that you have everything set up properly....in the vst setup, you chose the asioSCOPE driver not the asio multimedia driver, correct?

[ This Message was edited by: garyb on 2005-09-06 18:02 ]

andrew · Post by **andrew** » Thu Sep 08, 2005 10:55 am

On 2005-09-06 18:01, garyb wrote:
that looks much better.
if i remember correctly, you need to disable busmastering on that video card(in properties in device manager) afair...

another possible work around: open the dvice manager and set the sfp priority to below normal.

if you get no happiness, i would reinstall the os from scratch.(format and reinstall). it's possible that you have some file that's corrupt after all this and starting fresh might be the quickest solution. try reinstalling cubase and the scope first...

once again, i'm assuming that you have everything set up properly....in the vst setup, you chose the asioSCOPE driver not the asio multimedia driver, correct?

[ This Message was edited by: garyb on 2005-09-06 18:02 ]

Hey Gary -

Couldn't see any bus mastering in the properties on the Matrox Millenium - G550 display Adapter in Device Manager, just the usual stuff about updating the driver etc.

I tried reducing SFP priortity, no luck and yes I am using the ASIO scope drivers.

So I guess it's just the full reinstall to try. Am gonna finish a tune in Logic first (which takes me a while) but will let you know again how i go. Thanks again for all your posts to try to help me out.

*****Stop press... holy crap - i just tried increasing the latency from 3ms to 7...

It's all working perfectly with the scope project running at 70% and cubase vst load has dropped to 30%. hehe.. well i guess that was it and i must have xtc mode running at a higher latency than the 3ms which explains why it was workin at 30% the whole time....

wow.. cool! well I cleaned up my irq's a lot too so that can't harm.

Cheers guys

Andrew

_________________
http://www.voiceofcod.com
http://www.organicrecords.net

[ This Message was edited by: andrew on 2005-09-08 11:56 ]

dbmac · Post by **dbmac** » Thu Sep 08, 2005 11:19 am

On 2005-09-08 11:55, andrew wrote:
Couldn't see any bus mastering in the properties on the Matrox Millenium - G550 display Adapter in Device Manager, just the usual stuff about updating the driver etc.

Right click on the desktop, choose Properties, then Settings, then Advanced, then Options . .whew, still with me?
If there's a checkbox for Use Bus Mastering, uncheck it.

/dave

andrew · Post by **andrew** » Sat Sep 10, 2005 11:56 am

you're really too kind dave

Andrew

andrew · Post by **andrew** » Sat Sep 10, 2005 12:38 pm

On 2005-09-05 13:43, garyb wrote:
There should be very little performance difference between asio1 and asio2. i don't even hear much difference between the 24bit and 32bit drivers. with cubase, i use the asio2 24bit drivers. i have clients who like the asio2 flt(32bit FLOAT). the asio2 32 driver is 32bit INTEGER which is NOT supported by sx(although i don't think that's the problem).

Ok so I'm up and running with cubase now

one last query re the best drivers to use.

you say that "the asio2 32 driver is 32bit INTEGER which is NOT supported by sx(although i don't think that's the problem)"

Cubase plays fine with this driver and the vst load seems to be about the same as it is with the 24bit asio 2 driver, except that the 32 bit integer driver can have up to 32 stereo outputs whilst the 24bit can only have 16. I want the 32 outputs for my mixing.

So when you say that the driver is not supported by SX, do you mean that the 32 bit integer driver will just act as a 24bit driver as scope doesn't do 32 bit integer?

That's what it seems to be doing.

I've had a play with the 32bit float driver but they use quite a bit more vst power in cubase than the 32 bit integer. I haven't heard the difference between 32 bit and 24 bit audio yet, so I'm happy to be with 24 bit.

thanks again Gary and all who have reeeesponded

Andrew

________________
http://www.voiceofcod.com
http://www.organicrecords.net

[ This Message was edited by: andrew on 2005-09-10 13:40 ]

Post by **garyb** » Sat Sep 10, 2005 6:09 pm

yes, the with the 32bit driver the signal is truncated to 24bits in sx. the 24bit driver gives 32 i/o(16 STEREO). if you need 64i/o(32 stereo) use the asio2 24bit 64 driver.....or, just use what works presently...

andrew · Post by **andrew** » Sun Sep 11, 2005 4:43 am

On 2005-09-10 19:09, garyb wrote:
...if you need 64i/o(32 stereo) use the asio2 24bit 64 driver.....or, just use what works presently...

Without wanting to seem to pedantic Gary, as the 32 bit integer driver does the same thing, i don't have a asio2 24bit 64 driver. The only asio 2 drivers available are as in the below image, as taken from the Scope Manual. The asio2 24bit src only has 32 outputs, so I will stick with the 32 bit integer 64 driver.

http://tinyurl.com/dwfhp

anyway, your help is appreciated, thanks again

Andrew

_________________
http://www.voiceofcod.com
http://www.organicrecords.net

[ This Message was edited by: andrew on 2005-09-11 05:45 ]

[ This Message was edited by: andrew on 2005-09-11 05:46 ]