PlanetZ forums - scopeusers.com

I don't fully understand what it does... ?

it assigns a device's irq to a specific core. it's not supposed to be used with devices that share an irq. it may work for the pci cards and not the XITEs, idk.

Should work on Vista and Win 7 :

http://msdn.microsoft.com/en-us/windows ... 63378.aspx

But it has absolutely no effect on the issues I have.

Sigh.... I thought I was the only one.

Been using ASUS Maximus III Formula for a few years now on a Windows 7 32Bit system. Hasn't missed a beat. No clicks, no pops. Decided to upgrade to 64 bit, as well as update the Sonic Core Scope and now, it's all clicks and pops. Nothing has changed (only fresh 64bit install and SC upgrade). The IRQ settings are the same [shared with a network port, and the other card is sharing with the storage controllers... but 32 bit never had a single click - 64bit does and a lot]

When I load up the Luna Z-Link sources I get 'Assertion Failed - .\system.cpp (3565): fix == 1 || fix == brd

But if I load a previous Project with them already loaded, it's fine and works. But that's a different topic

Going to try a few of the tweaks and see what happens.

if you change to 64bit, you should do a complete uninstall, trash the old Scope folder and start fresh. there are system files that are different for the 64bit environment. 64bit Scope works fine, except for the STS and wave drivers. ASIO should be solid, however.

it's not a given that a shared irq that was fine in 32bit will be fine in 64bit. i've found that shared irqs are not necessarily a problem, unless it's usb.

it's very important to turn all the power stepping off that you can(in the bios).

the following is NOT aimed at anyone in particular, especially if they've posted in this thread(i'm just sayin...):

i don't understand why EVERYONE thinks that 64bit is an upgrade, when only a small part of the audio app world is truly 64bit. 32bit systems are going to be more stable just because all the apps will work together properly. this is regardless of the interface. some systems will have trouble, some will not, just for this reason. the ONLY people who benefit from 64bit are those whose use of the computer is mainly running lots of huge sample libraries, all at once. in this case, the extra system memory is a godsend....

Hi Garyb

Yeah it's a complete fresh install. In fact a new hard drive even. Even fresh install of Scope 64bit. I still have the 32bit OS on the original HD, so currently; when it's time to record, I'll just boot that system up and record that way. Did that last night. Did some drum recording tests on the 64bit with Cubase, and pops, nasty clicks. Rebooted the other HD with 32bit and ran fine.

Going to try loading an old Cubase project and see if play back is clicky. It seemed that the clicks weren't recorded, as they seemed to change in different sections of playback. So maybe it's a playback issue. Though playing Mp3s have been fine. I've been using the 64bit OS for a couple of months now, but it's only since last week that I decided to record band rehearsal.

Yeah this board has been great with the IRQ, never had a problem with the 32bit OS.

Going to try the BIOS, as maybe when updating, the BIOS refreshed itself. I did have it set previously, but it may have returned to stock settings. Thanks garyb, you've always been the one to help me out (it's been a while since I've posted on this forum too) [oh and of course others too have helped hehe]

Edit

Oh yeah that's true regarding the upgrade too. I also work with graphical modeling and figured that it would be a great time to upgrade everything. I kinda hoped that things would be ideal now (drivers, little bugs etc) due to 64bit being out for a while

do you have all of the visual fx in windows running?

real drums?

You're a genius Garyb

It's fixed . I disabled 'Intel SpeedStep Tech' and Intel C-STATE Tech (as well, I'm already sucking a lot of power anyway, so who cares about saving power lol) and that's seems to have fixed it. Just recorded 13 channels of drums and didn't hear a click or pop. Seems really good at the moment. That seems to have fixed the issue.

On my previous 32bit system, I was able to run 80+ tracks within Cubase without issues (though running a lot of waves compressor did slow down a few things). Big thank you to you Garyb, I think the issue has been fixed [currently running 44.1Khz at 7ms latency - which it was for the 32bit system [though I was recording at 48])

I have exactly the same issue but only on the output of my LunaBox (Z-link), inputs are working fine.

Luna Z-Link sources I get 'Assertion Failed - .\system.cpp (3565): fix == 1 || fix == brd

I tested just 'Intel SpeedStep Tech' tweaked in BIOS but nothing change ...
I tested IntFilter from microsoft but I have an issue at the boot of my mobo (device missing) ...

I contacted Sonic They told me it was maybe a hardware issue but if I read this thread I have doubts now !

win 7 64bits / scope v5.1 64

Not sure if I can be a huge help, but are you still using the Asus P6T?

I do know of another thread that lists people success with certain motherboards, so maybe the Asus P6T had an issue. Though in saying that, if you used it to record in 32bit then it should still be fine. Mine was, and it's an Asus as well.

I disabled the Intel SpeedStep Tech and the Intel C-STATE Tech and that worked, as per Garyb instructions. That's all I did and for me worked. Able to record 24 channels in.

Sorry I can't be more helpful

check for a newer bios...

Thanks,

I checked for a newer BIOS , I just updated it and disabled SpeedTech and C-STATE like before and always the same. It's bizarre because all work fine (multiples ASIO I/O + analogs I/O + wav + Z-link inputs (the 8 all work fine) ) and only the Z-link outputs Dest of the lunabox have this error message ... when I insert the Dest module.

My ASUS P6T deluxe run absolutely fine with scope v5.1 in 64bits mode except this dest module.

I thought maybe a param in the scope .ini to add ? ...

those things won't affect the luna box. that's neither a software, nor a computer issue. it might be a cable, the card, the connector on the card or the box, or it could be the Luna box itself.

i mentioned the bios because there were other problems that hijacked the thread a bit, my apologies for my part.

you can try running the installer again(don't unistall first!), that will overwrite any corrupt files and would eliminate the software as a suspect.

I already tried another cable, it's not that. I think it's the lunabox itself.
I reinstalled soft and it's the same.

lucky I don't need these add outputs (I have already 4 outputs from the cards) but it's always annoying when a device doesn't work with full capacities.

I'll try to find another lunabox today the price are really soft

Thanks Gary,