I see your point of view... But I am a computer techie. I work in several sound studios, and my job is solving hardware and software problems.I have a long list of success stories behind me. This problem with the scope arrised when we have upgraded our DAW.
I thought that the problem was with the new DAW, not the scope. But then I saw a lot of users with similar problem. I tried to see what components were they having. I concluded that problem was 865PE chipset. But GaryB told me that his Scope works on 865. Another match was NVidia GForce 6600. I didn't see someone with ATi and this problem. I will try to change graphic card, but...
But...If it was a hardware error then it would crash always when using ( addressing ) Scope. Hardware ins and outs including midi are working ( with midi keyb sending active sensing and midi clock ). When they are routed to software using workarounds avoiding seq dest module - they are working. The problem is seq midi dest. Try it yourself with app described in my previous post. If it is not a case, Then something else is roblem.
To avoid confusion: My Scope works fine with my older computer, but not with the new.Specific component causes this. There are no shared IRQs, memory overlappings etc... Everything is updated...No overclocking...Simply, something in comp doesn't like SCOPE! I must find out what and remove it!
Intel Pentium 4 HT 3.0GHz 1MB / 800MHZ FSB s478
Gainward mobo with i865PE s478 AGP
Gainward Nvidia 6600GT 128 DDR3 AGP
Maxtor 160 GB x2
Samsung DDR pc3200 512 x 2
Everything else (modem, second audio...) is removed
Pulsar 1 & Windows XP & Cubase SX 3 seems instable
OK sorry for being persistent, but I manage to freeze the system even WITHOUT midi keyboard connected at all. Everything I need to get the problem is to send something through seq midi dest module. Only then I get the freeze problem ( prooved only with small midi keyboard module connected with seq midi dest , no cubase started, no other modules ). I have tried clean install only with Scope attached to mobo, in safe mode, even changed the mobo, and the problem is still there.
Funny thing is that the vu-meters, even cubase still run in background, but sound loops a small amount of time and everything is freezed!
Without seq midi dest, I just can't freeze the system even with active sense + clock connected to mixers and synths, for hours!
The reason I wrote all of this posts is that the Scope is really great thing, everything works perfectly smooth, I can route whatever to whatever - no limitations in work. This problem is really flaw in a diamond and I have decided to solve this at cost of throwing everything throug the window and buying new computer!!!
I thought that the Scope board is broken, but how does it work on my old comp ( same OS as in new - WINXP SP1, tried SP2 too) ?!
BTW ...tried old scope 3.1c - the same...
Funny thing is that the vu-meters, even cubase still run in background, but sound loops a small amount of time and everything is freezed!
Without seq midi dest, I just can't freeze the system even with active sense + clock connected to mixers and synths, for hours!
The reason I wrote all of this posts is that the Scope is really great thing, everything works perfectly smooth, I can route whatever to whatever - no limitations in work. This problem is really flaw in a diamond and I have decided to solve this at cost of throwing everything throug the window and buying new computer!!!
I thought that the Scope board is broken, but how does it work on my old comp ( same OS as in new - WINXP SP1, tried SP2 too) ?!
BTW ...tried old scope 3.1c - the same...
very strange.
i just finished another d865perl machine and everything was fine with it. there definitely must be some cause of your problem.....latest bios and video drivers?
what is sharing an irq with your card? check start/programs/accessories/system tools/system information/hardware resources/conflicts/sharing.
<font size=-1>[ This Message was edited by: garyb on 2005-12-28 03:08 ]</font>
i just finished another d865perl machine and everything was fine with it. there definitely must be some cause of your problem.....latest bios and video drivers?
what is sharing an irq with your card? check start/programs/accessories/system tools/system information/hardware resources/conflicts/sharing.
<font size=-1>[ This Message was edited by: garyb on 2005-12-28 03:08 ]</font>