I've noticed recently that there seems to be some inprecision when using external midi controllers - when I turn a knob on my Phatboy 2 or even press a key on my keyboad I've noticed controls on softsynths are wobbling a bit instead of a turning smoothly they are jittery. It doesn't happen when I use the synth's own keys (for those that have them) or turn knobs with the mouse - just with both my external controllers. I also tried using Scope's keyboard but it doesn't work at all and tried using the midi filter to filter out different things to try and narrow it down but that didn't make a difference.
<font size=-1>[ This Message was edited by: Kymeia on 2006-08-16 00:20 ]</font>
Midi seems unstable
There's something else weird about how Scope is handling midi. I set up 2 midi ins in my project but most apps are treating midi 1 as invisible or refusing to accept midi from it, except for Logic and Ableton Live - they will only acept midi from 1 and give me a message that midi 2 is not working.
Is there a way to maybe reset midi (do I need to reinstall?) - I can't think what has gone wrong (unless its installing NI Kore recently that did it though I don't use its ASIO or Midi in any apps and have disabled them)
Is there a way to maybe reset midi (do I need to reinstall?) - I can't think what has gone wrong (unless its installing NI Kore recently that did it though I don't use its ASIO or Midi in any apps and have disabled them)
I've noticed that, in my daw, midi is more unstable when the hard disk is working strong. Could you notice the same behaviour? I've throubles only when I use the midi connections of the board.
If you could install a cheap soundblaster you could use it as midi source. (I've resolved my midi problems this way).
Hope it helps.
If you could install a cheap soundblaster you could use it as midi source. (I've resolved my midi problems this way).
Hope it helps.
-
irrelevance
Ok this does sound strange. How many cards do you have installed in your system, you failed to mention.
Obviously first thing to check is that windows has the right amount of midi ports selected, i can't remember what the default is.
Check under device manager->scope(whatver card you might have)->properties
I have had problems in the past whereby my startup had become corrupt and defaulted to my pulsar2 rather than my scope pro thus nothing worked, I don't know if it's possible that some hardware modules may have changed to a different card (if you have one?)
Post your system specs
Obviously first thing to check is that windows has the right amount of midi ports selected, i can't remember what the default is.
Check under device manager->scope(whatver card you might have)->properties
I have had problems in the past whereby my startup had become corrupt and defaulted to my pulsar2 rather than my scope pro thus nothing worked, I don't know if it's possible that some hardware modules may have changed to a different card (if you have one?)
Post your system specs
Thanks
1 Pulsar 2 and a Luna combined (9DSP's)
P4 3.6 with hyperthreading on
3 160 GB hardrives - 1 system/apps, 1 sample lib and one audio/scratch disk (not lots of disk activity as asked)
2 GIG DDR2 RAM
ASUS Extreme AX graphics card (PCI-Ex16-Intel bus)
The Midi controllers are a Korg N364 and a Phatboy 2 (merged in Scope)
Other hardware using USB2 ports:
Nord G2 Engine
Hartman Neuron VS
NI KORE
I'm a little reluctant to use KORE for midi as I'm planning to use that for my laptop soon and also I like being able to merge my Phatboy and Korg so I can use them at the same time with synths and I also have a midi switcher module so I can send midi out to my Yamaha VS as well.
1 Pulsar 2 and a Luna combined (9DSP's)
P4 3.6 with hyperthreading on
3 160 GB hardrives - 1 system/apps, 1 sample lib and one audio/scratch disk (not lots of disk activity as asked)
2 GIG DDR2 RAM
ASUS Extreme AX graphics card (PCI-Ex16-Intel bus)
The Midi controllers are a Korg N364 and a Phatboy 2 (merged in Scope)
Other hardware using USB2 ports:
Nord G2 Engine
Hartman Neuron VS
NI KORE
I'm a little reluctant to use KORE for midi as I'm planning to use that for my laptop soon and also I like being able to merge my Phatboy and Korg so I can use them at the same time with synths and I also have a midi switcher module so I can send midi out to my Yamaha VS as well.
Most of the Roland synths I've used (especially older ones) get rather nasty (-30db or so) crosstalk from the sblive, far beyond just unfiltered 60hz. The Yamahas I've tried had it but it was within the same noisefloor as the sblive's crappy outputs (down around -60db). So the grounding issue with the sblive will vary based on what you have connected. I just tend to be anal & avoid it now, as tempting as it is to use it for an extra midi i/o. I do have it connected to my tape returns for use with audio apps when I have Logic using the ASIO drivers for my RME. I'm aware of it's transcoding issues & poor frequency response so I don't use it for clinical work. I think I'm rather OT now...On 2006-08-16 03:12, Lima wrote:
Wow, not noticed yet! I'll check it for sure! Thanks for the info
Does this occur under high cpu load only? Or does this occur with any cpu load? Are you using Cubase Sx/Nuendo?On 2006-08-14 08:57, Kymeia wrote:
I've noticed recently that there seems to be some inprecision when using external midi controllers - when I turn a knob on my Phatboy 2 or even press a key on my keyboad I've noticed controls on softsynths are wobbling a bit instead of a turning smoothly they are jittery. It doesn't happen when I use the synth's own keys (for those that have them) or turn knobs with the mouse - just with both my external controllers. I also tried using Scope's keyboard but it doesn't work at all and tried using the midi filter to filter out different things to try and narrow it down but that didn't make a difference.
kymelia, go into the control panel, sounds & audio devices, go to the 'hardware' tab and select either creamware card, choose properties (or dbl click the card entry), in the Creamware Pulsar Properties page go to the 'Settings' tab and set your number of Wave & MIDI 'software' drivers. This is the end that connects to your audio application or sequencer.On 2006-08-16 00:19, Kymeia wrote:
There's something else weird about how Scope is handling midi. I set up 2 midi ins in my project but most apps are treating midi 1 as invisible or refusing to accept midi from it, except for Logic and Ableton Live - they will only acept midi from 1 and give me a message that midi 2 is not working.
Is there a way to maybe reset midi (do I need to reinstall?) - I can't think what has gone wrong (unless its installing NI Kore recently that did it though I don't use its ASIO or Midi in any apps and have disabled them)
Now in Scope look under Software IOs and add the appropriate number of 16 or 24bit Wav drivers and the appropriate number of Midi Sequencer Source & Dest modules. Note that you don't always need to have ALL of the modules loaded that you've defined in the properties panel, but you can't add MORE than are defined there (Scope will give an error). Now to connect the Luna & Pulsar2 midi ports you need to look under the Hardware IOs and add the Pulsar2 MIDI A Source, Dest & the Luna MIDI A Source & Dest. Connect the hardware source & dest pairs to the sequencer source & dest pairs as needed.
I realize some or all of this info may be redundant but I was trying to be thorough.
<font size=-1>[ This Message was edited by: valis on 2006-08-16 10:30 ]</font>
Hi
CPU load seems to be irelevent (and in fact I get the same jitter using hardware to control the knobs on my Scope synths as I do with VSTi's though with the mouse it's smooth)
I looked in settings - how many midi ports should I have set in device manager? - at the moment I have it set to 6 wave devices and 2 midi for each board - is that too much?
(btw - Ot but I just noticed it says it's set to 16 bit audio in the "preferred bit depth" section and the 24 and 32 boxes are greyed out - that can't be right? I have 24 bit set in Scope and I know it's recording at that bit depth.
Not got Cubase - using Live 5.2 qand Tracktion 2.
CPU load seems to be irelevent (and in fact I get the same jitter using hardware to control the knobs on my Scope synths as I do with VSTi's though with the mouse it's smooth)
I looked in settings - how many midi ports should I have set in device manager? - at the moment I have it set to 6 wave devices and 2 midi for each board - is that too much?
(btw - Ot but I just noticed it says it's set to 16 bit audio in the "preferred bit depth" section and the 24 and 32 boxes are greyed out - that can't be right? I have 24 bit set in Scope and I know it's recording at that bit depth.
Not got Cubase - using Live 5.2 qand Tracktion 2.
In my default project I have 1 midi source coming from my Pulsar (which is connected to the Korg) and one from my Luna (which is connected to the Phatboy) - then they are merged so I can use both at the same time in various softsynths and Scope synths.
I only have one midi dest which goes to my KORG .
I only have one midi dest which goes to my KORG .
The settings you have now are fine actually, although I wonder if there's a driver conflict somewhere due to your bsod issues. The greyed out 24/32bit options aren't a worry, you control the bit depth by the module you load in Scope now, those are legacy settings from 1.x & 2.x under win98 I believe. 6 wave & 2 midi ports shouldn't be causing problems.
The ks.sys I'm not sure about.
The ks.sys I'm not sure about.
I managed to change the settings to one midi port per card by going into safe mode - however it made no difference and also I hadn't realised it would limit the number of sequencer dests I could have - I thought it was just referring to the hardware ports, so then I went back to the default settings. That seems to have fixed the problem with Live and Logic not recognising midi 2 at least - maybe one of the ports was corrupted? Still getting the jitters though.
From googling it seems ks.sys may be related to my PCI-E graphics card or hyperthreading or both - seems to be some different reports.
From googling it seems ks.sys may be related to my PCI-E graphics card or hyperthreading or both - seems to be some different reports.
I do have sp2 installed. I have heard of midi problems with hyperthreading on - could this be it? I have tried setting affinity for SFP to just the first processor but can't see a difference in performance. I don't really want to turn it off completely if I can help it as some of my graphics apps prefer it on.
