This is related to incorrect timing issues with various devices that use a sequencer or any kind of external midi clock, and I have only tried this on Scope 7 PCI on 32bit. I dont have Scope on a 64bit OS yet, and haven't tried this on XITE, so hopefully some others can try this out and report back to see if this works for them on those setups.
After spending some time today trying to find the cause of the issue I have had with several devices that have sequencers which all seem to have wacked out timing, by a process of elimination I have found that, at least in my case here, the culprit is the DSP file, TIMECLK3.dsp
When I upgraded to Scope 7, before I uninstalled Scope PCIE 5.1 I first made a backup of the Scope PCI folder using winrar to archive it and all its subfolders. I then uninstalled Scope 5.1 which removed all the files that were installed with Scope 5.1. This left any third party files in their respective folders, and after making another backup copy of the Scope PCI folder with just these third party files and folders, I installed Scope 7 which placed all the new files into their respective folders. I didnt copy any files back over from the old Scope 5.1 backup as I seem to recall reading somewhere here that this might mess up the new Scope 7 install.
In Scope 7 I found that many devices which use a sequencer or midi clock were not working when switched to External clock, so I thought I would try and find where the issue was.
I used a utility program called WinMerge to compare the dsp files from Scope 5.1 and Scope 7, and after taking into account any third party dsps, I found that 173 files have been changed, nearly all are .dsp files but 2 are .ol files and then there is 1 file called dsp.idx .
So by copying a certain amount over from Scope 5.1 archive, then testing the external midi clock on several devices, then copying back the originals if they made no difference, I eventually came to TIMECLK3.dsp, and by using the older file from Scope 5.1 DSP folderthis seems to first of all show the correct external midi timing in the midi timing display window on all the various devices I have tested so far, and more importatnly it corrects the midi clock timing on those devices
So far it seems to have corrected the midi clock display when set to external clock such as in SB404, It has also fixed the midi seq timing with Neutron Sonic Attack, Mattomat, SpaceF LBH VIII, Solaris, and other devices that can use external midi clock, such as the Modular patch 808 Groover, etc.
While this is not a fix in itself, but hopefully it is a workaround that will help others until SC can sort this out, so any feedback would be useful. I will post this up on the Scope bug report list.
So basically, make a backup of the newer dsp file TIMECLK3.dsp installed with Scope 7 and replace it with the one from Scope 5.1.
Which brings me to a question about these 173 files in the DSP folder that have been updated. Should I have just copied all those older dsp files back over the new Scope 7 install after but I dont want to do that wIthout seeing what other users have done when they originally updated to Scope 7. Also I can make a list of those files if anyone else is interested, but it would be useful if someone could do a comparison as well and see if they come out at the same figure. I havent looked at any other folders to check the differences there, but might do that just out of curiosity
Finally if anyone needs a copy of that dsp file from Scope 5.1 let me know.
Cheers
=======================================
My setup is;
Operating system version: Win 7 32bit
Scope Hardware: Scope 7 running off 3 x Scope Pro PCI cards
Ulli settings: 3ms
Sample Rate: 48 kHz
) , I'll do the same for Presonus (Notion) (but wihout the part for wavelab because they are Studio One developpers ... and I suppose they will not demand to Steinberg an help 
) :
