PlanetZ forums - scopeusers.com

Well, garyb, after 14 years of sterling service, my Pulsar board has finally died and it's time to move on so I guess I won't be coming here again. I didn't want my last post to be a big "No, you're wrong" type of thing because I know how much you've helped me and countless other people over the ...

A bit late into this one, but I don't come here all that often these days.

I just wanted to point out that, according to Cakewalk, Sonar should be fine with hyperthreading enabled as from version 3 onwards. I'm using the latest Sonar Platinum and have no problems when hyperthreading is enabled.

Looks to be in the forums here.

Set this BIOS option, clear that BIOS option, add this registry key, delete that registry key, disable that service. OK, fine, but why can nobody explain why Scope 4.x 32 bit used to run perfectly on my PC with Windows XP/32 with NONE of these tweaks, and now with Scope 5.1 64 bit and Windows 7/64 ...

sorry, but totally disagree.

a favor??
drivers for the existing hardware??
Maybe Sonic Core could still produce PCI cards, maybe they can't. But my point is that a lot of people did NOT buy their cards from Sonic Core, they bought them from Creamware, a completely different company. When ...

I do have some sympathy for Elektra/Luna owners because they can't take full advantage of many of the freebies bundled with the upgrades, but then there are quite a few of us out there with higher-spec cards who already own most or even all of those freebies anyway. So how exactly do you make it ...

I was on 4.0 because I couldn't see much reason to upgrade until 64 bit support was available. So, as soon as the 5.1 beta was released, I upgraded to 5.0 so I could try the beta out.

As I understand it, when 5.1 is released then the pre-4.5 to 5.1 upgrade will cost significantly more than the ...

I'm not familiar with the products you mentioned, I use ones from the DeoxIT range. Their FaderLube F100 works fine for me as a fader lubricant, but it doesn't really sound all that different to the 7-78 you have already.

...this is weird
Being new to Windows 7, I didn't consider for a moment that my DPC latency could be different from the same PC running XP, but it seems from what I've read now that I was very wrong about this. I was still having audio glitch issues with some projects, so I fired up the latency ...

Yes, of course, it's all coming back to me now :roll: Back in those days I was running Windows 95 with a Pulsar I and still had kids at home running their old favourite legacy DOS games, so I routed the SB's output through the Pulsar so they could share the same speakers.

And then kept it that way ...

Back in the earlier days of the Pulsar, I'm sure you couldn't use it directly as a Windows sound card. There were the "Sound Card" software I/O's, but I could never get them to work properly. It's probably something that you wouldn't want to do in a professional environment anyway, but would have ...

I'm not a great one for sleeping myself, but I do like to run umm let's just call them "batch jobs" overnight, and it would be good if I could save the planet a little if they finish before I wake up.

Like I said, it's not an issue if it's not supposed to be able to sleep, I just wanted to know if ...

I'm not sure if sleep mode is supposed to work or not with a Pulsar 2. I couldn't even put my PC into sleep mode until I moved to Windows 7, and after that I waited until the 5.1 beta was available before installing the Scope software. Now, waking up from sleep triggers a slew of Scope errors ...

scope works in combination with other staf.
The Scope system can work together perfectly with 64-bit software in a 64-bit environment even if it's not all 64-bit. If you have a 64-bit host for Synthogy Ivory, you can run the 64-bit version. I use the VSL Bosendorfer Imperial with Vienna ...

ram 8)
So, which part of the Scope system do you think needs multiple gigabytes of RAM? Certainly not the DSP code, you'll run out of DSP resources or PCI bandwidth long before you run out of code memory. DSP code isn't bloatware like current x86/x64 code, it's very small and tight - even the ...

XITE-1/4LIVE wrote:Which VSTi Reverb are you using..?

The Perfect Space convolution reverb that came with Sonar 7 Producer - apparently it's a cut-down version of Voxengo's Pristine Space. I was a bit short of cash when I upgraded to Sonar 8 so I just went for the Studio edition that doesn't have as many effects.

OK, I'm now using today's 5.1 update with the new ASIO driver. Works fine with Sonar, the only downside being significantly higher CPU usage at the best ULLI setting than with WDM/KS. I may need to take that setting down a notch to give me a bit of headroom on projects with lots of DXi/VST stuff ...

As far as I understand it, the only reason why it would matter whether the Scope software is running in x86 or x64 mode is if you wanted to use the Scope STS samplers with multiple gigabytes of samples. The Scope system itself is running native on the DSP's, so with the exception of things like the ...

It might have been a good idea to upload it as "donotdownload.tmp" or something and then rename it when it was complete, I'd already downloaded an incomplete version once before realising what was going on...

I'm having an issue with Sonar and WASAPI. I skipped Vista and I've only had Win7 for a week now so I'm kind of new to it, but my understanding was that WASAPI is supposed to supersede the lower-level WDM/KS audio modes and still give reasonably low latency. When I use it I can't get Sonar to ...