MIDI Input Broken

[synthetic88]

My MIDI Inputs to scope have stopped working. I have a Sequencer MIDI Source and Destination in my setup, but when I launch MIDI-OX it tells me, "CreamWare MIDI In/Out 1: There is no driver on your system." No output ports show up in MIDI-OX. This setup was working before, how do I fix it? Thanks.

[valis]

Go to your control panel, hardware tab, choose properties on one of the cards and check the settings in there.

[garyb]

i haven't seen this problem for some time, but here's a possibility:
http://web.archive.org/web/200703301946 ... entrye.htm

dumb question, but you have all the proper modules connected in the routing window?(of course you do...)

[synthetic88]

i haven't seen this problem for some time, but here's a possibility:
http://web.archive.org/web/200703301946 ... entrye.htm

That didn't fix it.

dumb question, but you have all the proper modules connected in the routing window?(of course you do...)

Setup attached. It worked before, it's my autoload or whatever Scope calls it.

[garyb]

try adding a sequencer midi dest as well. (there's none in this screen shot)
i assume midi is coming from a usb interface to midiox to scope?

[valis]

If Scope's midi drivers aren't seen by Midi-OX then they're not registered in the OS at the moment, or something else resident in memory is grabbing them first. I have a Behringer BCF-2000 cheapo that somehow manages to knock out my other USB midi device occasionally even though everything 'appears' to be working when it happens....

Have you tried adding more than 1 sequencer source/dest pair? Usually Scope will ask if u want to enable more than X number of midi devices when you reach the limit (set in the location I referred to in my post above).

[synthetic88]

I added some more software and hardware midi source/dest and that didn't do it. MIDI is coming in via MIDIoverLAN. I don't have any other MIDI devices or software running. Should I reinstall Scope?

[Cochise]

This could be a dumb advice too, since you say things were working before (before what?), however, actually I can't understand what you're exactly trying to do.

If I right remember:

1) Sequencer MIDI Source and Dest must be included in your routing window before you launch MIDI-OX, and no other MIDI host has to be running unless you include MIDI Source and Dest twice.

2) Inside Scope you can't use any external MIDI flow that not pass thru CW MIDI hardware, unless u assign that flow to a midi track in a host and the MIDI track has is out in Scope with the 'thru' enabled (==added== this example is effective for MIDI data coming through non CW hardware and going inside Scope, but it's enough to change the In/Out assignment in order to route CW MIDI to another hardware MIDI out) .







Have you tried disabling other MIDI hardware, then lauching a sequencer?

[synthetic88]

This could be a dumb advice too, since you say things were working before (before what?),

Before it stopped working.

however, actually I can't understand what you're exactly trying to do.

MIDI comes in using MIDI over LAN, which is a piece of software that allows MIDI to travel over ethernet from one computer to another. It's working fine, I can see data coming into the computer with it's monitor app.

If I right remember:

1) Sequencer MIDI Source and Dest must be included in your routing window before you launch MIDI-OX, and no other MIDI host has to be running unless you include MIDI Source and Dest twice.

Check. Nothing else is installed excpet for GVI, and that isn't running.

Have you tried disabling other MIDI hardware, then lauching a sequencer?

I don't have a sequencer installed, this is just a Scope slave computer.

2) Inside Scope you can't use any external MIDI flow that not pass thru CW MIDI hardware, unless u assign that flow to a midi track in a host and the MIDI track has is out in Scope with the 'thru' enabled (==added== this example is effective for MIDI data coming through non CW hardware and going inside Scope, but it's enough to change the In/Out assignment in order to route CW MIDI to another hardware MIDI out) .

Sorry, I didn't follow that. The Scope MIDI hardware never worked on my card (got it used). Even when it was working, I was having problems where after a while the MIDI data would get messed up. No matter what note I played on my keyboard, Scope would always play the same pitch. Restarting always fixed this, but now it isn't. So there was probably something wrong with the system all along. Perhaps I just need to reinstall Windows and Scope at this point.

[Cochise]

No matter what note I played on my keyboard, Scope would always play the same pitch. Restarting always fixed this, but now it isn't. So there was probably something wrong with the system all along. Perhaps I just need to reinstall Windows and Scope at this point.

Have you tried filtering out Active Sensing?




I think it's worth a try to disable MIDI lan as a test for possible conflict, before reinstall.

I'd also try to reinstall MIDI lan driver before rebuilding the whole system.


Trying with a sequencer could give you certainty that MIDI-OX is correctly working.
But if you have feelings that the whole system is corrupted...

It looks quite unusual however that things suddenly stop working without any hardware or software or settings change.

[garyb]

is there still no sequencer midi dest in the project?(it needs to be there BEFORE opening midiox)

[Cochise]

No output ports show up in MIDI-OX.

Actually this might look like no Sequencer MIDI Source module is loaded in Scope at the time MIDI-OX is launched

MIDI-OX it tells me, "CreamWare MIDI In/Out 1: There is no driver on your system."

I dug up MIDI-OX and made some try.

Ok go to Control Panel/System/hardware tab/Device manager, select Creamware DSP board; in the property tab select MIDI devices, select scope MIDI Device properties and check 'Use MIDI with this device'.
Even if it's checked try to change the setting, restart the machine then change the setting again and restart the system again.

Then reset the mapping in MIDI-OX, Midi devices window, check 'Automatically attach Inputs to Outputs during selection', select again your Inputs and Outputs and give a last try.

[synthetic88]

is there still no sequencer midi dest in the project?(it needs to be there BEFORE opening midiox)

Yeah, I put these in there then relaunched MIDI Ox. Many times.

Ok go to Control Panel/System/hardware tab/Device manager...

I confirmed that the device is set up to use MIDI this morning. Tonight I'll try changing it, changing it back and restarting.

Sigh, better Scope software is on the way, right? MIDI Ox seems like such an unneccesary step.

[Cochise]

[ MIDI Ox seems like such an unneccesary step.

It's no longer necessary for me to use MIDI-OX since I bought a 2nd CW card [added]( this among the other things doubled my MIDI slots )[/added].
I also had stuck notes. I don't use midi keyboard so much, but It looks like I any longer have that problem since i'm filtering Active Sensing.
[added] Actually if i'm right MIDI-OX filter out all System Real Time Messages as default setting [/added]

IMHO resetting the mapping can worth a try before reinstall.

Have you tried disabling other MIDI hardware, then lauching a sequencer?

I don't have a sequencer installed, this is just a Scope slave computer.

Just, I can see Asio modules in your Routing Windows..

[dawman]

I have a spare Digital Music Corporation MX8 as a spare which never gets used.

Promise me you'll break down and buy a Scope card someday, and I will ship it to you or Tascam.

[synthetic88]

I thought MX8 was just a patchbay?

Everything I tried seemed to make things worse, so I went with the nuclear option: reformat the drive and reinstall Windows. I got as far as installing SP2 last night, so I'll reinstall Scope tonight and see what happens.

[synthetic88]

A full reinstall fixed the problem. Only took me 6 hours.