Hello to all
GaryB you got it all wrong...
Sorry if I pissed you off or anyone else in any way on this forum...
First of all I didn't say that Scope is a bad system - on the contrary. It is near perfect, and that is the reason I am so determined to solve my problem. I am not claiming that the problem is with Scope in general, but I want to investigate because of other people complaying about problems. I don't think it is only my system, but I will find out.
I only want feedback on my problem, and to see if I am the only one with it. I found that I am not, there are a lot of users with similar problems on newer systems with XP.
And two of my general bug foundings were confirmed - the screwed labels in stm16s mixer, and installation 'black mark' issue.
I found some more bugs on my system,(will see if it is only on my system), but they are really small - like messed labels.
If you want, try the ControlRoom. Start connecting 'input 1' to some sound source and all of the outputs to the mixer.
Now start switching input to output 1,2,3,4,5,6. You should notice silence when you get to output 5. If not then I am wrong - it is not a bug. If it is - then maybie this midi freeze has something with bugs.
I need someone to try this to confirm my claims. I do not have the opportunity to try it on some other system, mine is the only one with the Scope.
If you give it a try for yourself, we will see if it is only on my system, don't be so exclusive.
cheers...
This thing needs a driver update. If you check the wdm driver, you will notice the date: 2002. Windows is everchanging system. I am going to need a driver for my mouse pad soon

( with administrative rights and multi-user interface )
p.s. The remixer with grammy didn't utilise midi, and probably none of them were utilising the control room

... just kidding, maybie it is my system - I am just trying to find out...
<font size=-1>[ This Message was edited by: psionic on 2006-01-03 04:57 ]</font>