MIDI ports not detected in apps in Windows 7

[DevonB]

Id say it was a driver clash. When you install similar drivers for other devices, they are left on the PC when not used and can sometimes cause problems.

I'd have to disagree on this because this was a fresh install. With each driver addition, it's still never found a MIDI port. It never found MIDI when it was JUST the Pulsar II with its MIDI. It never found MIDI with the Uno. I removed the Uno and installed the XT. Again, same problem. Multiple interfaces work perfectly fine on Win 7 too. I've had a machine with 39 defined MIDI ports on Win 7 work just fine. Just not sure what else to check.

Devon

What other devices/software do you have connected? It could be something you've installed. Could you try it on another PC that dosnt have your usual stuff on it?

My other DAW works no problem. The only thing on this PC is the Pulsar drivers/environment, which work, LinuxSampler, demo of SampleLord and MIDIOx now. That's it. I moved the MIDI Express XT from the system that it works perfectly fine on. The Pulsar came out of another one of my machines that I'm retiring that it worked fine on for the last 10 years. The Uno works fine connected to my iPad. I really don't think it's any of the hardware in this case. I've searched the registry, and see the entries in there for all the MIDI devices. For some reason though, I cannot get any MIDI ports to surface to normal Windows apps. I can play any of the Pulsar synths no problem via MIDI though, so the MIDI absolutely works on the Pulsar and on this machine. My setup is working fine with me triggering this machine from my other DAW via MIDI. I just can't get any MIDI interface to show any OTHER program some MIDI port love. I just want to use this machine as a sampler playback machine as well as my Pulsar environment. Ugh....

Devon

[UltraJv]

I did a quick google and someone had problems (not the same as yours) with scope version 4.5. A suggestion was that v5 was needed. Compatibility mode helped as well.

http://forums.planetz.com/viewtopic.php?f=1&t=32014

http://www.hitfoundry.com/issue_04/compat.htm

[DevonB]

Id say it was a driver clash. When you install similar drivers for other devices, they are left on the PC when not used and can sometimes cause problems.

I'd have to disagree on this because this was a fresh install. With each driver addition, it's still never found a MIDI port. It never found MIDI when it was JUST the Pulsar II with its MIDI. It never found MIDI with the Uno. I removed the Uno and installed the XT. Again, same problem. Multiple interfaces work perfectly fine on Win 7 too. I've had a machine with 39 defined MIDI ports on Win 7 work just fine. Just not sure what else to check.

Devon

What other devices/software do you have connected? It could be something you've installed. Could you try it on another PC that dosnt have your usual stuff on it?

Nothing actually. This is a very minimal config on a minimal computer, seriously. I literally only have a CAT5 cable for network, no keyboard, no mouse, 1 MIDI cable to MIDI In, and two optical cables for ADAT in/out. I run it via remote desktop completely. I literally installed the OS, installed all the updates, installed the Pulsar drivers and environment, and then tried LinuxSampler and SampleLord. Seriously, nothing else is on this machine. I just set it up a few weeks ago and was triggering it from my main DAW and that was and is still working fine. It's when I started to try to set up something for sample playback that I noticed the problem.

My main DAW has significant more "stuff" connected to it and in it and it all works just fine. The MIDI Express XT was moved from this DAW, which it works fine on, and moved to this other DAW that the MIDI is not working. The Uno I was just using as well on my iPad to trigger synths on it, and it works fine. The funny part is all the drivers install fine, it looks fine in Device Manager, but I can't get it to be seen by any software that would use it.

Just hoping someone else might have run up against this problem and have some suggestions?

Devon

[DevonB]

I did a quick google and someone had problems (not the same as yours) with scope version 4.5. A suggestion was that v5 was needed. Compatibility mode helped as well.

http://forums.planetz.com/viewtopic.php?f=1&t=32014

http://www.hitfoundry.com/issue_04/compat.htm

I'm on 64 bit, so it has to be version 5.1 or higher. Win 7 and 64 bit support didn't come out until 5.1 And my environment works, so that's not the problem.

Another thought is I could roll back to Windows XP, but not exactly ideal. I bought the Win7 license for this PC for a reason....

Devon

[UltraJv]

I did a quick google and someone had problems (not the same as yours) with scope version 4.5. A suggestion was that v5 was needed. Compatibility mode helped as well.

http://forums.planetz.com/viewtopic.php?f=1&t=32014

http://www.hitfoundry.com/issue_04/compat.htm

I'm on 64 bit, so it has to be version 5.1 or higher. Win 7 and 64 bit support didn't come out until 5.1 And my environment works, so that's not the problem.

Another thought is I could roll back to Windows XP, but not exactly ideal. I bought the Win7 license for this PC for a reason....

Devon

I wonder if the driver install has gone wrong. Sometimes windows will install its own driver instead of the makers one. This requires the driver to be installed in a certain sequence. Are there any yellow exclamation marks on your midi drivers from control panel device manager? Do the drivers say Microsoft?

[DevonB]

I did a quick google and someone had problems (not the same as yours) with scope version 4.5. A suggestion was that v5 was needed. Compatibility mode helped as well.

http://forums.planetz.com/viewtopic.php?f=1&t=32014

http://www.hitfoundry.com/issue_04/compat.htm

I'm on 64 bit, so it has to be version 5.1 or higher. Win 7 and 64 bit support didn't come out until 5.1 And my environment works, so that's not the problem.

Another thought is I could roll back to Windows XP, but not exactly ideal. I bought the Win7 license for this PC for a reason....

Devon

I wonder if the driver install has gone wrong. Sometimes windows will install its own driver instead of the makers one. This requires the driver to be installed in a certain sequence. Are there any yellow exclamation marks on your midi drivers from control panel device manager? Do the drivers say Microsoft?

I'm thinking whatever keys the program(s) reads to see what MIDI ports are available are horked up. The driver install from Device Mananger looks the same on my working and non-working system. That's what I've not been able to Google up so far. That would make sense because I've had 3 different MIDI interfaces in this thing and they all install properly, but none of them show available interfaces.

The only thing I don't have working on the non-working system is the PCI Simple Communications Controller because there is no driver for Windows 7 and later, only Vista and sooner for the Intel Management Engine. I'm not using that feature, so not that worried about it.

Devon

[UltraJv]

I would try and get both working. It may help. PCI simple comms is usually serial port. Midi is a serial device too, i bet its that. See if windows will find a driver for it. If not.Go into details, property, hardware id. Copy n paste into google and maybe youll find a driver.

[DevonB]

I would try and get both working. It may help. PCI simple comms is usually serial port. Midi is a serial device too, i bet its that. See if windows will find a driver for it. If not.Go into details, property, hardware id. Copy n paste into google and maybe youll find a driver.

An "Unknown" device will come back as PCI Simple Communications Controller as well, but Windows 7 does a search and finds it's the Management Engine for me. The Management Engine is designed for enterprise customers who need to remotely manage their desktops en masse to get and set certain information out of the PC. You can read about it more right here -

http://intelmanagementengine.com/intel- ... rface.html

So Win7 at least knows it's some type of communications system, but there is no drivers for it for Win7, which is why it comes back with nothing. Fortunately, Intel has all the rest of the drivers for Win7 for my system

https://downloadcenter.intel.com/Search ... rodId=2781

But the IME drivers only went up through Vista -

https://downloadcenter.intel.com/Detail ... rodId=2781

I didn't know what the ME driver was, so this made me do a little research. Learned something new.

Devon

[DevonB]

dbl post

[UltraJv]

ok, one last stab at this. Have you tried installing Scope/drivers with admin rights?

[DevonB]

ok, one last stab at this. Have you tried installing Scope/drivers with admin rights?

I recall I had to give it permission, because I always leave UAC on, but I didn't right click install as admin, no. Keep in mind, the whole Scope environment installed properly and is up and working just fine. However, 3 different MIDI interfaces, including the one that comes with the Scope, does not see a MIDI port that it can use for normal Windows apps. The Scope environment sees the MIDI interface, and when I 'connect' it to a synth in the environment, it works perfectly fine.

And thanks UltraJv for trying.

Devon