i think scope has problem with my new p4 hyperthreading ,i read the topic unstable midi but no fix in there
many times it got hanged in between session
and though i changed default midi in CubaseSx to creamware1,2 this problem still exists
please help
thnx
<font size=-1>[ This Message was edited by: lovenara on 2006-08-21 05:02 ]</font>
midi seem to get hanged always
First of all, hi to everybody it's been a while since the last time 
I was very furious about midi hanging up at the time ( 5-6 months ago ) and blamed the Scope, yelled and screamed at the CW staff, but now, I am pretty shure that HT causes the trouble in most cases. If you have a HT processor (I had intel@3,0 GHz 1MBcache s478 i865p mobo), there could be odd freezes all the time.
1. Disable HT (by disabling apic acpi support in BIOS or during OS install , in my case - simple disabling HT support in BIOS didn't help - refer on how to do it in this forum, or the net)
2. Do not use Scope's midi (delete "midi seq dest" module from your project)
3. Do it as I have - sell the damn processor and buy AMD ATHLON - I hated AMD a lot, but now I changed my mind. They improved since the old days.
This could not be a solution for your case. It was for me - I tried two completely different configs, part by part, keeping only CPU, and the problem persisted.
Some other people suggested midi filter - I don't agree 'cause I had midi filtering on my KORG KONTROL 49 - no midi sense was transmitted.
I hope I was of some help to you...
BTW, I am going back to Intel, but this time CORE2DUO and p965 - I hope it will work.
One other thing: CW stated at their documentation that working in 2 processor environment may couse trouble - so since HT presents an extra core, making your system see 2 vitrual cores instead of one real, I think this may lead to unstability ( who knows what dark magic has been involved in that to make 2 CPUs out of one
)
Core 2 Duo has two cores also (two real ones - no HT and similar dark sorcery), but there are many users with dual core CPUs and no problems at all... We'll see...
I was very furious about midi hanging up at the time ( 5-6 months ago ) and blamed the Scope, yelled and screamed at the CW staff, but now, I am pretty shure that HT causes the trouble in most cases. If you have a HT processor (I had intel@3,0 GHz 1MBcache s478 i865p mobo), there could be odd freezes all the time.
1. Disable HT (by disabling apic acpi support in BIOS or during OS install , in my case - simple disabling HT support in BIOS didn't help - refer on how to do it in this forum, or the net)
2. Do not use Scope's midi (delete "midi seq dest" module from your project)
3. Do it as I have - sell the damn processor and buy AMD ATHLON - I hated AMD a lot, but now I changed my mind. They improved since the old days.
This could not be a solution for your case. It was for me - I tried two completely different configs, part by part, keeping only CPU, and the problem persisted.
Some other people suggested midi filter - I don't agree 'cause I had midi filtering on my KORG KONTROL 49 - no midi sense was transmitted.
I hope I was of some help to you...
BTW, I am going back to Intel, but this time CORE2DUO and p965 - I hope it will work.
One other thing: CW stated at their documentation that working in 2 processor environment may couse trouble - so since HT presents an extra core, making your system see 2 vitrual cores instead of one real, I think this may lead to unstability ( who knows what dark magic has been involved in that to make 2 CPUs out of one
)Core 2 Duo has two cores also (two real ones - no HT and similar dark sorcery), but there are many users with dual core CPUs and no problems at all... We'll see...
i have been very much troubled with midi in the past.
my conclusion is that by setting irqs manually which happens on standard pc therefore HT disabled is very importand.
my system always freezed after some time.
asus p4c800dlx freezed, abit ic7g freezed and many others have reported freezing.
standard pc is the solution.
but take also in mind that there are some creamwares modules that do not work very well with midi nomater HT, acpi, on or off.
six-string: problematic
minimax:problematic(the update is better)
samplers:problematic
try testing as many synths as you can.
usually polyphony set to 1 does not cause midi stucks, but when you raise polyphony midi stucks appear.
offcourse there are some synths that do not stuck notes.
i have noticed also that midi notes become more stable when you let the dsps fully load.
the tip of unloading a device and reload it back again will not make any difference if you do not let it take its time to fill the dsps. wait also to dsps to get filled when changing sound on a specific synth.
according to xp installation, the main reason i do not upgrade to a new systm with core2 etc.. is because you cannot assign irqs manualy.
my conclusion is that by setting irqs manually which happens on standard pc therefore HT disabled is very importand.
my system always freezed after some time.
asus p4c800dlx freezed, abit ic7g freezed and many others have reported freezing.
standard pc is the solution.
but take also in mind that there are some creamwares modules that do not work very well with midi nomater HT, acpi, on or off.
six-string: problematic
minimax:problematic(the update is better)
samplers:problematic
try testing as many synths as you can.
usually polyphony set to 1 does not cause midi stucks, but when you raise polyphony midi stucks appear.
offcourse there are some synths that do not stuck notes.
i have noticed also that midi notes become more stable when you let the dsps fully load.
the tip of unloading a device and reload it back again will not make any difference if you do not let it take its time to fill the dsps. wait also to dsps to get filled when changing sound on a specific synth.
according to xp installation, the main reason i do not upgrade to a new systm with core2 etc.. is because you cannot assign irqs manualy.
Are you sure you don't have a midi synth that sends active sensing? I have used Creamware's midi i/o on a machine with HT without any issues, but the only thing that it connected to was another PC. I use a USB based midi i/o for all my other external gear & controllers. This eliminated any lockups & blue screens I had been experiencing, and without the need for 'standard PC'.
In regards to IRQ sharing (which is why you would need to manually assign irqs) just make sure you read a motherboard's manual before purchasing it, and check for the manufacturer to list PCI SLOT SHARING of irq's with onboard devices. You'll want to find a board that has the middle slots shared with things that you can disable. Once you have a slot with all shared devices disabled it should make a good match for your primary Scope card, and allow you to use ACPI mode without any issues.
These are my observations from having Scope cards for 6 years now...
In regards to IRQ sharing (which is why you would need to manually assign irqs) just make sure you read a motherboard's manual before purchasing it, and check for the manufacturer to list PCI SLOT SHARING of irq's with onboard devices. You'll want to find a board that has the middle slots shared with things that you can disable. Once you have a slot with all shared devices disabled it should make a good match for your primary Scope card, and allow you to use ACPI mode without any issues.
These are my observations from having Scope cards for 6 years now...
To Valis:
Hi,
yes, I am positive, tried to connect KORG to other midi-in on audigy, and used midi monitor (not the SCOPE, but the external one, standalone) just to check that there is no active sensing, monitoring was ok, because there WAS midi sensing when I enable it.( trough midi A, KORG is very scr*wed up to set the desired option). Besides that I tried a few more keyboards (yamaha kn1x and m-audio radium 49), so I am pretty shure about it.Midi filter can help to have this effect of freezing delayed, because midi commands are sent much slower. Try to move knob, and - there it is again... I think it is only a temporal solution.
And again, it was only in my case, don't have to be for you, maybie you'll find midi filter helpful. Usig other midi interfase (like usb) and avoiding SCOPE's MIDI system will solve the problem 100% (but SCOPE's MIDI is so powerful...)
To all:
Honestly, I do not dare to think what will happen when I switch to C2D. I may finally get rid of the Scope card, but knowing that there is no HT on C2D is somewhat encouraging... There are a few different chipsets (iP965 i975x nVidia 570, 590 etc. ) I will think about intel chipset twice, because I haven't seen anybody having some other chipset and mentioned midi problems which again, doesn't prove anything. But there was a great number of HT mobos CPUs and working SCOPE envs - according to other users on this forum. So this is case-to-case problem.
One more thing: TRY to get very good branded power supply. I had HardDisks going into PIO mode, tried everything, wanted to return mobo, but when I changed my PSU with one worth 70e, HDDs worked just fine in UDMA 5. I have a few more stories with faulty PSU - no good filtering - no stabillity, including all components, not only SCOPE. And it is well known that HT is great power consumer!
Do you hear funny clicks from time to time out from HardDisks like they are booting up in the middle of windows, but noting goes on, even no lockup? It is bad filtered power coming out from PSU!
So - think about it.
( Wanna buy my 70e PSU ? - just kidding )
<font size=-1>[ This Message was edited by: psionic on 2006-09-05 07:04 ]</font>
Hi,
yes, I am positive, tried to connect KORG to other midi-in on audigy, and used midi monitor (not the SCOPE, but the external one, standalone) just to check that there is no active sensing, monitoring was ok, because there WAS midi sensing when I enable it.( trough midi A, KORG is very scr*wed up to set the desired option). Besides that I tried a few more keyboards (yamaha kn1x and m-audio radium 49), so I am pretty shure about it.Midi filter can help to have this effect of freezing delayed, because midi commands are sent much slower. Try to move knob, and - there it is again... I think it is only a temporal solution.
And again, it was only in my case, don't have to be for you, maybie you'll find midi filter helpful. Usig other midi interfase (like usb) and avoiding SCOPE's MIDI system will solve the problem 100% (but SCOPE's MIDI is so powerful...)
To all:
Honestly, I do not dare to think what will happen when I switch to C2D. I may finally get rid of the Scope card, but knowing that there is no HT on C2D is somewhat encouraging... There are a few different chipsets (iP965 i975x nVidia 570, 590 etc. ) I will think about intel chipset twice, because I haven't seen anybody having some other chipset and mentioned midi problems which again, doesn't prove anything. But there was a great number of HT mobos CPUs and working SCOPE envs - according to other users on this forum. So this is case-to-case problem.
One more thing: TRY to get very good branded power supply. I had HardDisks going into PIO mode, tried everything, wanted to return mobo, but when I changed my PSU with one worth 70e, HDDs worked just fine in UDMA 5. I have a few more stories with faulty PSU - no good filtering - no stabillity, including all components, not only SCOPE. And it is well known that HT is great power consumer!
Do you hear funny clicks from time to time out from HardDisks like they are booting up in the middle of windows, but noting goes on, even no lockup? It is bad filtered power coming out from PSU!
So - think about it.
( Wanna buy my 70e PSU ? - just kidding
)<font size=-1>[ This Message was edited by: psionic on 2006-09-05 07:04 ]</font>
