PlanetZ forums - scopeusers.com

first off Ive been using Scope 5.1 64x for a few months now and im lovin it over 32 bit maybe its the accses to more ram (8 gig installed) im not sure but for me the upgrade was most defiantly worth it the problems started when the track i was working on got big eg:20-30 vocal tracks and roughly the same for midi/vsti's that's when the pops and clicks start anyway here is how i resolved these issues :
Let me add that i applied most of the tweaks but not all so please read through carefully before proceeding and backup what is important these
are just precautions ive had no problems since lets hope it stays that way by the way i am using cubase 5 for recording through Scope and mixing in Scope What a Great Sound ! also i downloaded Mz 7 Optimizer from someone on this site that really helped to so thank for that also
Ive included another tweak utility called smart which turns off win services hope this helps Good luck!

System
CPU: i7 2.8 @ 3.66
Ram: 8 gig cosair 1600
Asus:p7p55d
Soniccore cards:2x 6 + 3 =15
Win 7 64 bit home what follows is from Soniccore website:

For an audio PC (with little ASIO latency) you have to do some adjustments, because Core i7, i5, i3 PCs can have ASIO clicks even with little CPU usage and 25ms latency. At least you should deactivate the following settings in you PC BIOS :

Intel EIST
Intel C State
C1E Support
Overspeed Protection
Hyperthreading
Execute Bit Support
Set Limit CPUID MaxVal to 3 (maybe not important)
Intel Virtual Tech
Intel VT-d Tech

In addition the energy save settings of your operating system should be set to maximum.

What Follows is from
http://www.acousticguitarcommunity.com/ ... e=activity

* WARNING: There are some tweaks that involve modifying the registry. If you are not comfortable with doing this and backing up the registry don't do it!
* DISCLAIMER: I am not responsible for anything that happens to your system as a result of what is presented here. These are tweaks I have done to MY system. If there is a term, feature, function or anything else you are not familiar with do the research to learn what it is. This is what I've spent the day doing.
* Some of the tweaks listed assume some basic knowledge like how to get to Services, stop them and change their startup type.
* Before stopping services I used Black Viper's Services chart here: http://www.blackviper.com/category/guides/windows-7/
to read about each service that was started before deciding if I could safely stop the service and change the startup type to "Manual"


The Tweaks
>> Start->Right-click Computer->Properties->Advanced system settings->Advanced->Performance:Settings->Visual Effects
Select "Adjust for best performance"

>> Start->Control Panel->Appearance and Personalization->Personalization->Theme
Under Basic and High Contrast Themes, select "Windows Classic"
The "Themes" service can now be stopped
Start->Control Panel->System and Security->Administrative Tools->Services
Double-click "Themes"
Change Startup type to "Disabled"
Click the "Stop" button
Click "OK"

>> Start->Right-click Computer->Properties->Advanced system settings->Advanced->Performance:Settings->Advanced:Processor scheduling
Select "Background services" in the "Adjust for best performance of" section
Reboot

>> Start->Right-click Computer->Properties->Advanced system settings->Advanced->Performance:Settings->Advanced:Virtual memory->Change
Set C: drive (OS) to No paging file
Created paging file on F: drive (least used) and set the Custom Initial size: and Maximum size: to the Recommend Size
Reboot

>> Start->Control Panel->System and Security->Power Options->Show additional plans
Select "High Performance" then click "Change plan settings"
Change "Turn off the display" to never
Click "Change advanced power settings"
Expand "Hard disk" then "Turn off hard disk after": Change setting to "0"
Expand "Display" then "Turn off display after": Change setting to "0"
Click "OK" then click "Save changes" in the "Change settings for the plan: High performance" window
Reboot

>> Core Parking: Run "regedit" and search (F3) for 0cc5b647-c1df-4637-891a-dec35c318583
Change the "Value Min" and "Value Max" to 0
Press F3 to find the next entry as the number of instances depends on the number of power profiles in the system
Reboot

>> Windows 7 Fault Tolerant Heap: Run "regedit"
Go to this key HKLM\Software\Microsoft\FTH\Enabled and change the value to "0"
This disables the Fault Tolerant Heap entirely on the system
Reboot

>> In SONAR 8, 8.5 and X1 (only do this for quad core processor systems)
In Options->Audio->Advanced tab click Edit Config File (aud.ini)
Changed "ThreadSchedulingModel" from 1 to 2

>> Turn off System Restore and file versioning
Start->Control Panel->System and Security->System->System protection
Select hard drive where Protection is set to "On"
Click "Configure" button
Select "Turn off system protection"
Click "OK"
Repeat for other drives with protection on
Reboot

>> Turn Windows Features off
Start->Control Panel->Programs->Turn Windows Features on or off
Uncheck "Windows Search"
Uncheck "Tablet PC Components"
Uncheck "Windows Gadget Platform"
Uncheck "Remote Differential Compression"
Click "OK"
Reboot

>> Disable Remote Assistance and Remote Desktop
Start->Control Panel->->System and Security->System->Remote Settings
Uncheck "Allow Remote Assistance connections to this computer
Ensure "Don't allow connections to this computer" option is checked
Reboot

>> Disable IPv6
Run "regedit"
Navigate to HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
Look for "DisabledComponents" entry
If not there, create it by selecting "New" from the "Edit" menu and then click "DWORD (32-bit) Value"
Modify the "DisabledComponents" entry by double-clicking it
Enter "FF" as a hexadecimal value to disable IPv6 over all interfaces and prefer IPv4 over IPv6. Other values are possible but they
only disable specific components. "FF" disables all IPv6 components
Reboot

>> Stopped the following Services and changed their "Startup" to "Manual"
* Bluetooth Support Service
* Windows Media Center Receiver Service
* Windows Media Center Scheduler Service
* Windows CardSpace
* Peer Networking Identity Manager
* Peer Networking Grouping
* Remote access Auto Connection Manager
* Remote Access Connection Manager
* Remote Registry
* Smart Card
* Smart Card Removal Policy
* Remote Desktop Configuration
* Print Spooler
* Tablet PC Input Service
* Telephony
* Remote Desktop Services
* Remote Desktop Services UserMode Port Redirector
* Windows Defender
* Windows Remote Management (WS-Management)
* Windows Media Player Network Sharing Service
* Parental Controls
* Nero Update
* IP Helper
* Offline Files
* TCP/IP NetBIOS Helper
Reboot

>> Disable unused devices in Device Manager
Start->Right-click Computer->Manage->System Tools->Device Manager
If your system does not have a floppy drive then select
Floppy drive controllers-> Standard floppy disk controller: Right-click, select "Disable"
Read DPC Latency Checker's page to learn about disabling other devices and warnings.

Thanks!!!!

nice one, thanks. some unseen tweaks for me, will try them out...

there are some additional services screaming to be disabled, have a look at my post here:
http://forums.planetz.com/viewtopic.php?f=19&t=29760

Cheers,
Roman

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 the wave drivers still struggle to cope with playing a CD-quality stereo wave file? If I didn't need the extra memory space for Vienna Instruments I would fall back to 32 bits in an instant.

well... I've explained it so many times, that I got a bit tired to chime in each time.
It's the M$ business scheme - they can't ever (under no circumstances) deliver aproper product.
People would stop buying the follow-up.
Hence they do this and that and tell stories about what you need and what possibilities are and that you should and can't miss and it's oh, so great...
ALL BULLSHIT
There's an (almost) endless line of classic records that sold millions of copies, which were produced on machines clocked below 100MHZ ... and those weren't even multi-threaded.
Ok, those boxes were called Macintosh, had 8 MHZ (lmao) slots and SCSI disks.
Not to be misunderstood... Apple is following the same scheme for > than a decade, but at least they provide some alternative toys that fill their wallet without flooding the user with technical overkill.
These $billion corporations are self fulfilling prophecies, when they say 'upgrade' you can be sure to be p*ssed off.
They don't offer what YOU request, but sell mental debris...
ok, a very high level debris, really complicated stuff, but still debris.

I have Scope sitting in a Win98 box - 24 Adat channels are more than enough to communicate.
I'd suggest (in you case) that you keep working in your trusted XP environment (with Scope) and connect a Win7-64bit system in a similiar way...
As a virtual sampler you'd probably get along with a relatively small CPU... just try it with nothing but the sampler installed...

cheers, Tom

oh yes, and my thanks to smix, too

@PaulSh: Fair enough, but nothing is perfect, and scope 64bit is relatively new, so give s|c some time to fix it and take it or leave it. BTW, I always did OS tweaks, even back in windows xp, 3.11 or even DOS by optimizing autoexec.bat and config.sys Some tweaks might help stability and other improvements of a daw, some not.

I could ask Microsoft the same question, why is Windows7 not usable in VMWare View environments without tweaking it? And why doesn't Excel 2010 like some of my old macros anymore? If everything would be easy, I wouldn't have a job

Cheers,
Roman

Nothing of these tweaks helps here.

we still get big big problems with SCOPE 5.1 64bit on that windows 64bit machine.

Here are still some stuttering-pops. Minimum one time per hour, most of the time there are more.

Sonic Cores support told me that I am one of 1000 where it don't work.
Its about my hardware wich don't fit.
I realy mistrust that, beacause I tried to buit up a w7 64bit system now for the third time,
always with different components, from "Core 2 Quad", over i5 2500K to i7 2600,
with two different mobos, whith all these tweaks here and enywhere in the net, but nothing changed.

I also tested it with old dsp cards and new XITE-1 D expressCard wich I ordered especially for that,
but I have to give it back, realy nothing changed.

Sonic Core also told me that is not an Scope Problem and they will not change the ASIO Driver in the future for that issue. What can I do to solve these cracles?

Have someone realy solved his crackle problem complete for a Cubase/nuendo Scope5.1 ASIO combination at a w7 64bit system?

Are there som news ?

If YOU have running a modern i7 2600 w7 64bit system using cubase/nuendo in SCOPE-ASIO-mode crackle free
could YOU please post which motherboard fits, which components dosn't, and which mayor tweeks you are using / which not.

I tried a ASUS P5W DH Delux with Core 2 Quad 2,6GHz - crackles. (BIOS to old to change EIST)
Than I bought a MSI MSI P67A-GD55 (B3) + i5 2500K 3,3GHz (with all BIOS tweaks) - crackles.
Than I bought a better CPU i7 2600 3,4GHz using the same mobo (with all the tweaks listed here) - crackles.

i've installed on a number of machines for clients. i never disable services or do anything extreme.

i go to system properties\advanced\performance settings\adjust for best performance(which turns off aero and all other visual candy that wastes resources). i go to the bios and disable whatever of this list is available:
Intel EIST
Intel C State
C1E Support
Overspeed Protection
Hyperthreading
Execute Bit Support
Set Limit CPUID MaxVal to 3 (maybe not important)
Intel Virtual Tech
Intel VT-d Tech

THAT'S IT.

everthing from a Supermicro Dual i7 XEON machine to an ancient IBM thinkcentre 8114 to a Vostro 1400 laptop works with asio and no cracklres at 44.1k @4ms.

your problems could be any one of a number of other pieces of software, host settings, power settings, i don't know....

does your XITE or cards share an irq with anything?

*edit* nevermind, i see you're posting in several places and i have my answer of "yes".

Yes SCOPE board 1 was sharing IRQ 16 with plenty others.

now I do some testings with toggled boards.
I heard from Tom, that the IRQ sharing with the second board is not so important.
So I put my Luna board wich were second to the other PCI slot,
maybe it works. If so thanks to Tom who contacted me.

If not - how to moove the Scope main card to a free IRQ per OS (win7)?

I didn't find anything in the net about that.

Tanks for your help.

I'm happy to here from you without any stottering crackles.

Best
Tobi

the only way to change irq is to swap pci slots, there's no possibility to manually assign irqs in win7. so, as gary suggested earlier, disable all unneeded devices and usb controllers in device manager and see how it goes. you can sort "by device" in device manager, so you can see, which devices can be easily disabled...

cheers
roman

For the record,
with pci card, on XP 32bit-W7 32'n 64 bit, Interrupt-Affinity Filter (IntFiltr) DO ALL the job you need.
Set affinity and mask to a single cpu for your soniccore stuff and that's it...
Use the standard out with your multimedia player.
I don't tweak the bios, or windows.
Do other tweaks rise the power of your DAW... if you have to.

i hope it's help...

ps : you should try it with Xite

that might help.

found this:
http://support.microsoft.com/kb/252867

interesting stuff, will try with my xite and see what happens...

Hi all,

I tried IntFltr with Xite-1 and pci-e card, doesn't work. after the first try windows didn't boot and went to repair itself... after second try at least windows started normally, but the xite-1 wasn't recogniced neigther by windows (device manager shows warning symbol) nor by Scope 5.1. Environment Windows 7 64bit.

Cheers,
Roman

katano wrote:Hi all,

I tried IntFltr with Xite-1 and pci-e card, doesn't work. after the first try windows didn't boot and went to repair itself... after second try at least windows started normally, but the xite-1 wasn't recogniced neigther by windows (device manager shows warning symbol) nor by Scope 5.1. Environment Windows 7 64bit.

Cheers,
Roman

Same problems here by installing IntFltr. Windows crashes totaly. I would recomand not to install intFltr on Win7 64bit - not compatible!

Best T

problems in 32bit as well....

it seems not to work with xite but pci cards are running, then...

Sorry, infiltr always does the work for me on pci cards(32'n 64 bit was tried) ...