midi interface

virtualstudio · Post by **virtualstudio** » Sat May 22, 2004 1:02 pm

I had this freezing problem to with my two systems
and after doing a search found to this topic:

http://www.planetz.com/forums/viewtopic ... forum=1&36

does that mean that midi interface from the scope boards are no good?
does this has anything to do with midi drivers?

the system that freezes is only running sfp
no cubase and giga studio jet.

as soon as I disconnect the scope midi source thinghs seem to be ok !!

NOT: while I'm typing this on one system the
other system froze again !!!!!!

AndreD · Post by **AndreD** » Sat May 22, 2004 5:13 pm

hi,
try to connect the keyboard AFTER scope was started...

works fine here...

Post by **garyb** » Sat May 22, 2004 9:56 pm

some controllers don't play nice with scope(transmitting sysex,active sensing and echoing clock when you don't want them to).
if AndreD's suggestion doesn't work(i'll bet it does) a low cost midi interface(serial or usb) WILL work.

Pete · Post by **Pete** » Sun May 23, 2004 10:46 am

Hi,
I had the freezing up problem too, and fixed it. Unfortunately, I "fixed" more than one thing at a time. Regarding midi, there's this line in the version 4 install file, "Readme - Important Notes" that refers to the Scope card settings in the Windows Device Manager:

- In Windows XP the number of Sequencer source/dest modules present in the project must exactly match the number showing in the driver dialog in the Device Manager.

I did this after I re-inserted my cards, STM cable, video card, and memory, checked all cable connections, uninstalled and re-installed my Scope drivers, re-restarted, installed Scope again. Now my system is solid. I disabled USB in bios as a precaution, because USB had caused freezes with my Korg Oasys card. But that's been moved to a different computer now, uses windows ME.

There are things to read in the PDF manual and the hard copy manual about scope's midi. There's more to it than I thought.

Good luck,
Pete

Pete · Post by **Pete** » Sun May 23, 2004 11:58 am

I forgot, in my previous post, there's more I did that contributed to Scope-computer success.
Before I did all this, I had not only the freezing up, but some random restarts and blue screens with the microsoft "STOP" messages, with the long hex number. Microsoft has some posts explaining those, but most of my info came from Planet Z or Creamware's site. Thanks.

If I have this right, the default in XP is for Windows to have control over the interrupt/pci scheme using ACPI. You can easily change that to have your BIOS do it. you go to the Device Manager and update/replace the ACPI driver by selecting "Standard PC" from the list.
Here's one link:

http://www.geocities.com/sheppola/acpi.html

I did it, and there was a flurry of busy-ness when I restarted, and my devices re-allocated themselves. Then you have some control in BIOS over allocation of interrupts, if you want it. I did not change anything, but my problems disappeared at that point.

Another suggestion I used was to go to the System Properties in XP, and under the "Advanced" tab there's a "Performance" heading, and some settings. I changed the processor scheduling to "Background Services."

Pete

virtualstudio · Post by **virtualstudio** » Mon May 24, 2004 3:06 pm

great think I found thanks to you guys the problem.

Let see if it doesn't freez again while I'm typing

first off al I did the whole standard Pc thing again because with the system is new AND I have all this new software so I've been f*****g around with it so much so I've decide to de a fresh install.... (pfff again)

-I have the drivers from scope 4.0 but I 'm running the SFP 3.1c software for now.

then after this I've disconnected all the midi(3 boards) on the sytem that freezes al the time.
play a little bit with it no freezing jet!
re-started Sfp and conect the midi again.

and yes after 5 minutes the whole thing frooze again

then I was thinking as before I had also two systems running like that and no freezing problem. what did I do differnt here?

and the answer is my 01v was never connect through midi.
As soon as I pulled the midi cable out off the scope connector the whole thing un-frooze(defreeze

)

now I've looked and the 3th modules midi source and dest were not loaded.
I'm going to load those now and connect 01v again to see what happens for now looks like that is the problem.

regards and thanks again

[ This Message was edited by: virtualstudio on 2004-05-24 16:08 ]

virtualstudio · Post by **virtualstudio** » Wed May 26, 2004 12:34 pm

as the whole freezing was probably due to my videocard, and not the midi? maybe the combination?
I was reading looking at VST system link, Is it not excactly what whe have with SFP routing? you can also route asio to any other system with a scopeboard.
Or can you route the midi through the System Link cable, that would be cool

Who knows?

Immanuel · Post by **Immanuel** » Wed May 26, 2004 1:01 pm

Hi Virtual

Don't give up - it can be hard to figure out, but it is a shame not to. If you have a hardware incompatibility issue, it may be a long run though. How is your power suply?

Have you tried installing SP4?
Could be worth it to give it a go.

BingoTheClowno · Post by **BingoTheClowno** » Wed May 26, 2004 1:10 pm

I had that same problem ocasionaly under heavy audio load. Try changing the PCI Latency time. I don't know what value will work with your board (I have a dual CPU board not sure if this matters) but in my case I set it to zero. Try to lower that setting.

Also, if you don't use the serial and parallel ports you can disable them in BIOS and free 2-3 IRQs.

[ This Message was edited by: BingoTheClowno on 2004-05-26 14:11 ]

virtualstudio · Post by **virtualstudio** » Wed May 26, 2004 2:57 pm

I've 350 watt, wich I bought after a lot of people told me that I could better do that than my old 300 watt, now everybody says you have to have 400 watt

I only use the drivers from scope 4.0

as for the pci latency I looked at it in bios its on 64, should I change it? I can
somebody else with same board knows? AsusP4P800.

for now the last changes, graphic card and 4 usb instead of 8, they seem to work the system hasn't frooze a full hour now.

I've shut it down for today its been a long day restarting and restarting .
see what tomorrow brings, would like to play with my new plug-ins a bit now.

thanks for the help so far.

BingoTheClowno · Post by **BingoTheClowno** » Wed May 26, 2004 3:35 pm

64 is too much I guess. Start with zero and go higher if you get problems.

PCI latency has relevance if you have multiple PCI cards.

[ This Message was edited by: BingoTheClowno on 2004-05-26 16:36 ]

virtualstudio · Post by **virtualstudio** » Wed May 26, 2004 4:36 pm

On 2004-05-26 16:35, BingoTheClowno wrote:
64 is too much I guess. Start with zero and go higher if you get problems.

PCI latency has relevance if you have multiple PCI cards.

[ This Message was edited by: BingoTheClowno on 2004-05-26 16:36 ]

from CWA site:

In some BIOS types there is an option called 'PCI Latency Timer'. It can help to increase the value to 64 - 128 or more. If your BIOS does not feature this option, you can try to change the parameter with the program TweakBIOS (c't shareware,www.heide.de/ct/shareware).

and I have 3x CW pci-boards so it has relevance I think

BingoTheClowno · Post by **BingoTheClowno** » Wed May 26, 2004 5:53 pm

Well yes, but they wrote that probably when the top CPU speed was around 400MHz.