I'm getting all sorts of pops, glitches and sync problems when I use any ASIO driver other than old ASIO source/dest - 16 bit. It even works better with ASIO Multimedia drivers than with the SCope driver. Any ideas appreciated.
The system is a P4 2.4 with gigabyte GA-8ST667 mobo, Cubase SX is v.1.01.
Also, my primary IDE controller won't change from PIO mode - it's a Seagate Barracuda HDD - is this just a hard drive limitation or is there somthing I can do to get it into DMA mode?
Cubase SX won't cope with Scope
I solved a similar problem by disabling "ide to PCI masterbus" in bios (via chipset).I guess that all the data from the IDE devises were streamed through the mastebus.
Try to experiment with the buffersizes in cubase even try to disable them and also try to optimize latency. In controlpanel -system-propeties-advanced-visual effects performance choose best performance,and same place "advanced" choose background servises instead of programs.
My terms might not be totally correct because I use a Danish version of XP
Kim
Kim
Try to experiment with the buffersizes in cubase even try to disable them and also try to optimize latency. In controlpanel -system-propeties-advanced-visual effects performance choose best performance,and same place "advanced" choose background servises instead of programs.
My terms might not be totally correct because I use a Danish version of XP
Kim
Kim
Well after thoroughly testing both ways of installing WinXP, I have now decided Standard PC mode is the only way to get everything working glitch free, even with Scope 4, which I had hoped would work in ACPI mode.....It means I can't use HT, but seems a small price to pay for a smooth running system, and when I say smooth, I really mean it: the difference on my 2.8 PIV is unbelievable.....boot time is dramatically quicker, and I haven't heard one crackle. [I did have Standard PC mode originally, but so many people seem to be happy with ACPI that I had to check it out, and believe me I've tried everything to get it working.....probably coz I've got an old Yamaha SW1000XG in the system (which I love for the PLG An Analogue Daughter-board)]
Well for whatever reason, I've decided the old addage 'If it ain't broke, don't fix it' really rings true......
Standard PC is the way for me
Well for whatever reason, I've decided the old addage 'If it ain't broke, don't fix it' really rings true......
Standard PC is the way for me
I have two Seagate Barracuda drives both configured for DMA - no problem there with XP. Not sure why you are having a problem configuring the drives for DMA?
As far as ACPI vs. Standard - I have nothing meaningful to add except in Standard mode I can make sure both my boards (Pulsar 2 & XTC) are sharing the same IRQ. To my knowledge, I didn't have a problem running in ACPI mode but yesterday decided to try Standard mode so that both boards have the same IRQ. I'm not noticing any improvement one way or another yet.
As far as ACPI vs. Standard - I have nothing meaningful to add except in Standard mode I can make sure both my boards (Pulsar 2 & XTC) are sharing the same IRQ. To my knowledge, I didn't have a problem running in ACPI mode but yesterday decided to try Standard mode so that both boards have the same IRQ. I'm not noticing any improvement one way or another yet.
EUREKA! After months of frigging around with this beast it's finally purring. It was the old 'stuck in PIO mode' problem of course.
This happens when Windows detects failures in the hard drive which, in my case were caused by an old version of Gigasampler (the filesys f’up), and prevents you from resetting the IDE controller to DMA mode.
After finding two posts on this issue, one of them of at microsoft, and still not solving it after two registry changes I compared the resistry settings with the Secondary IDE Controller and found an entry Windows had kindly deleted. I'll post the details in announcements for anyone who's really interested.
It's a relief to have gotten past it but makes me think, Man, what a lame dog of a system, I should start thinking about a Mac. Well, got that off my chest. Thanks guys!
This happens when Windows detects failures in the hard drive which, in my case were caused by an old version of Gigasampler (the filesys f’up), and prevents you from resetting the IDE controller to DMA mode.
After finding two posts on this issue, one of them of at microsoft, and still not solving it after two registry changes I compared the resistry settings with the Secondary IDE Controller and found an entry Windows had kindly deleted. I'll post the details in announcements for anyone who's really interested.
It's a relief to have gotten past it but makes me think, Man, what a lame dog of a system, I should start thinking about a Mac. Well, got that off my chest. Thanks guys!