Unable to find device in config.

[dj]

Hi, all:

Since I first replied in this thread, I've updated to an Acer Quad core with Win7 Home Premium 64 bit.

I did lose my UM-4, for which Roland has not updated the driver, but I have successfully installed my UM-1 with the new updated Roland driver.

If you haven't already, check the Roland/Edirol site for the Win7 driver.

Composer sees the UM-1 with no problem for me.

David

[Thoraldus]

Originally Posted by dj

Hi, all:

Since I first replied in this thread, I've updated to an Acer Quad core with Win7 Home Premium 64 bit.

I did lose my UM-4, for which Roland has not updated the driver, but I have successfully installed my UM-1 with the new updated Roland driver.

If you haven't already, check the Roland/Edirol site for the Win7 driver.

Composer sees the UM-1 with no problem for me.

David

David,

I've have been using the new 64 bit driver from Roland. On the off chance there was something amiss with the install I uninstalled the driver and reinstalled it. No joy. I installed MidiYoke and MidiOx and the Notation s/w was able to see the MidiYoke ports. I was able to run midi data from Notation to my synth but the timing was messed up really bad. It looked like the Notation s/w was timing out 2.5 seconds for every midi event sent. It was majorly ugly, it took 10 minutes to play a small midi file containing a simple c-d-e-f-g-a-b-c-b-a-g-f-e-d-c scale. ;-)

What version of Composer are you using? I've been trying to run the current trial versions.

Rick

[dj]

Rick:

That sounds very much like a driver conflict. If another program is trying to connect to the driver at the same time, you can run into the slowdown syndrome.

I have several Composer versions running on my computer, going back to 1.6 and they all seem to work fine with the UM-1. The version of Composer shouldn't matter at all; they're essentially the same when it comes to handling of midi ports.

The fact that you were able to send data to your synth means that the UM-1 port was working -- the fact that it was running so slowly points to a conflict. In the old days of DOS 3.0, I'd have said it was an IRQ conflict. Nowadays, it's either the driver or another program trying to access it at the same time.

Just had a thought: go to Setup/Midi Devices/Configuration/Port/Select Ports and see whether the UM-1 device shows up and whether it is checked as selected for your configuration.

Good luck.

David

[Thoraldus]

Originally Posted by dj

Rick:

That sounds very much like a driver conflict. If another program is trying to connect to the driver at the same time, you can run into the slowdown syndrome.

I have several Composer versions running on my computer, going back to 1.6 and they all seem to work fine with the UM-1. The version of Composer shouldn't matter at all; they're essentially the same when it comes to handling of midi ports.

The fact that you were able to send data to your synth means that the UM-1 port was working -- the fact that it was running so slowly points to a conflict. In the old days of DOS 3.0, I'd have said it was an IRQ conflict. Nowadays, it's either the driver or another program trying to access it at the same time.

Just had a thought: go to Setup/Midi Devices/Configuration/Port/Select Ports and see whether the UM-1 device shows up and whether it is checked as selected for your configuration.

Good luck.

David

David,

The problem is that no other midi program I am running on the system has any problem, including some pretty old x86 programs. All the other programs see the UM-1.

Just took a look at the port selects as you suggested and found the Notation Musician program had automatically selected ALL ports for input and output. Naughty - naughty! ;-) After deselecting all the inappropriate ports the program plays through MidiYoke to the synth at tempo. ;-)

The program still does not see the UM-1 directly but I am now able to evaluate the program to make a purchase decision. Thank you David for the helping hand.

cheers,
Rick