|
|
|
08-03-2018, 04:58 PM
|
#1
|
Human being with feelings
Join Date: Feb 2011
Location: Brooklyn, NY
Posts: 42
|
5.94 and non-existent MIDI devices.
Just install 5.94 from .93 and immediately upon launching reaper states a ton of old uninstalled MIDI devices are unavailable. Stuff I haven't used in years. Rolled back to 5.93 and everything is back to normal. Tried installing .94 twice with same results.
Win 7 64.
Cheers.
-c
|
|
|
08-03-2018, 05:29 PM
|
#2
|
Human being with feelings
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,096
|
Yeah, that's a new and afaik intendend behaviour.
Imo it makes sense for 'everyday use' that Reaper informs you that a previously used MIDI device isn't available anymore.
Of course in the transition from old to new behaviour it can be a bit annoying listing all those old devices as you experience.
You can select them in Preferences -> MIDI devices (multi-selection with Shift / Ctrl is possible), rightclick -> Forget device (that's also new in 5.94) and they shouldn't show up anymore.
Last edited by nofish; 08-03-2018 at 06:12 PM.
|
|
|
08-03-2018, 06:27 PM
|
#3
|
Human being with feelings
Join Date: Jul 2009
Posts: 7,570
|
somebody didn't read the changelog…
|
|
|
08-04-2018, 01:41 AM
|
#4
|
Human being with feelings
Join Date: Jun 2015
Posts: 8,696
|
22 unused devices appear (several duplications).
One of the best things about Reaper has been its hassle free way with adding and removing MIDI devices.
If this is deliberate how does it benefit the user when reintroducing MIDI devices worked seamlessly anyway?
"warn when a previously...."
Now going through whole list for 22 items choosing "forget device" for each one.
I hope I won't have to do this again for every new version of Reaper from now on?
|
|
|
08-04-2018, 03:22 AM
|
#5
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
Quote:
Originally Posted by Softsynth
22 unused devices appear (several duplications).
One of the best things about Reaper has been its hassle free way with adding and removing MIDI devices.
If this is deliberate how does it benefit the user when reintroducing MIDI devices worked seamlessly anyway?
|
Because if a previously-used MIDI device was not connected, the user would have no warning that it is not available (which might not be intended).
Quote:
Now going through whole list for 22 items choosing "forget device" for each one.
I hope I won't have to do this again for every new version of Reaper from now on?
|
Normally you won't have 22, this reflects all of the devices it has seen since you began using REAPER. After this one time you'll only see ones that were recently available and no longer. In any rate, you can select multiple devices, right click, and forget en masse (and if you get any present devices accidentally selected, it won't forget those).
|
|
|
08-04-2018, 03:32 AM
|
#6
|
Human being with feelings
Join Date: Jun 2015
Posts: 8,696
|
Quote:
Originally Posted by Justin
Because if a previously-used MIDI device was not connected, the user would have no warning that it is not available (which might not be intended).
Normally you won't have 22, this reflects all of the devices it has seen since you began using REAPER. After this one time you'll only see ones that were recently available and no longer. In any rate, you can select multiple devices, right click, and forget en masse (and if you get any present devices accidentally selected, it won't forget those).
|
Thanks for quick reply. If that's a one time issue I have no problem with that
I guess it is easy for me to see all the MIDI devices and test them here, maybe not for other users with different systems with physical hidden connections.
22 included multiple duplicates of the same couple of items and a few others.
|
|
|
08-05-2018, 06:37 AM
|
#7
|
Human being with feelings
Join Date: Feb 2011
Location: Brooklyn, NY
Posts: 42
|
Quote:
Originally Posted by EpicSounds
somebody didn't read the changelog…
|
True and generally new features aren't of a great interest to me. Id have never noticed this but it also didn't recognize any of my current devices immediately and had to power cycle them all. that's what brought me to my midi devices screen in the first place.
Usually when something new is added in reaper it doesn't impede my work flow so when it did... I'd assumed it was in error.
Still think it's a slightly odd addition.
|
|
|
08-05-2018, 07:24 AM
|
#8
|
Human being with feelings
Join Date: Aug 2014
Location: Netherlands
Posts: 882
|
Quote:
Originally Posted by Chvad SB
Still think it's a slightly odd addition.
|
Yes, but reporting it immediately as a bug is also slightly odd when you don't read changelogs isn't it?
|
|
|
08-06-2018, 06:26 AM
|
#9
|
Human being with feelings
Join Date: Feb 2011
Location: Brooklyn, NY
Posts: 42
|
Quote:
Originally Posted by nofish
You can select them in Preferences -> MIDI devices (multi-selection with Shift / Ctrl is possible), rightclick -> Forget device (that's also new in 5.94) and they shouldn't show up anymore.
|
Thank for the info!
|
|
|
08-06-2018, 06:27 AM
|
#10
|
Human being with feelings
Join Date: Feb 2011
Location: Brooklyn, NY
Posts: 42
|
Quote:
Originally Posted by Paul99
Yes, but reporting it immediately as a bug is also slightly odd when you don't read changelogs isn't it?
|
Thanks for the contribution.
|
|
|
08-06-2018, 06:28 AM
|
#11
|
Human being with feelings
Join Date: Feb 2011
Location: Brooklyn, NY
Posts: 42
|
Quote:
Originally Posted by Softsynth
Thanks for quick reply. If that's a one time issue I have no problem with that
I guess it is easy for me to see all the MIDI devices and test them here, maybe not for other users with different systems with physical hidden connections.
22 included multiple duplicates of the same couple of items and a few others.
|
Yeah the duplicates were one thing. I can see the value of this moving forward. Reaper launching and not finding anything previously working was what tossed me the most. Never had a update in 6 or so years that did that.
|
|
|
08-08-2018, 07:08 AM
|
#12
|
Human being with feelings
Join Date: Aug 2015
Posts: 39
|
Quote:
Originally Posted by Justin
Because if a previously-used MIDI device was not connected, the user would have no warning that it is not available (which might not be intended).
|
The problem with the new behaviour is that Reaper is not distinguishing between:
> Old MIDI devices no longer present in the studio that were once connected; and
> Current MIDI devices that are simply 'turned off'.
I've got a Studiologic NumaCompact keyboard controller which is connected via USB but now has to be powered on every time I launch Reaper else I get:
"The following MIDI inputs could not be opened: numacompact"
My options now appear to be:
>Always turn the controller on before launching Reaper; or
> Remove the nag screen by electing not to show it... but this warning has been useful in the past if a MIDI input device didn't initiate etc etc!
Shame we can't mark a device as 'current' and simply 'turned off' to distinguish from one that was once connected but is now redundant.
|
|
|
08-08-2018, 08:28 AM
|
#13
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
Quote:
Originally Posted by Jaybee
The problem with the new behaviour is that Reaper is not distinguishing between:
> Old MIDI devices no longer present in the studio that were once connected; and
> Current MIDI devices that are simply 'turned off'.
I've got a Studiologic NumaCompact keyboard controller which is connected via USB but now has to be powered on every time I launch Reaper else I get:
"The following MIDI inputs could not be opened: numacompact"
My options now appear to be:
>Always turn the controller on before launching Reaper; or
> Remove the nag screen by electing not to show it... but this warning has been useful in the past if a MIDI input device didn't initiate etc etc!
Shame we can't mark a device as 'current' and simply 'turned off' to distinguish from one that was once connected but is now redundant.
|
You can turn off warnings about unavailable MIDI devices...
|
|
|
08-08-2018, 08:58 AM
|
#14
|
Human being with feelings
Join Date: Aug 2015
Posts: 39
|
Quote:
Originally Posted by Justin
You can turn off warnings about unavailable MIDI devices...
|
Thanks Justin, I think that's the option I'll have to take going forward.
Running Windows I sometimes (though very rarely) get a scenario where I've activated something that causes a nanoKontrol or other device to stop working and the warning is good to see in that case but it's the exception not the rule.
|
|
|
08-08-2018, 10:28 AM
|
#15
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
Quote:
Originally Posted by Jaybee
Thanks Justin, I think that's the option I'll have to take going forward.
Running Windows I sometimes (though very rarely) get a scenario where I've activated something that causes a nanoKontrol or other device to stop working and the warning is good to see in that case but it's the exception not the rule.
|
We'll add more granularity to those options for 5.95.
|
|
|
08-08-2018, 01:12 PM
|
#16
|
Human being with feelings
Join Date: Aug 2015
Posts: 39
|
Quote:
Originally Posted by Justin
We'll add more granularity to those options for 5.95.
|
That would be great. Many thanks! 👍
|
|
|
08-09-2018, 06:06 PM
|
#17
|
Human being with feelings
Join Date: Apr 2012
Posts: 159
|
Quote:
Originally Posted by nofish
Yeah, that's a new and afaik intendend behaviour.
You can select them in Preferences -> MIDI devices (multi-selection with Shift / Ctrl is possible), rightclick -> Forget device (that's also new in 5.94) and they shouldn't show up anymore.
|
So I did select Midi Devices- forget device --this on devices I have not used
Funny my ASIO driver is showing up but not working
Error opening device.
So with the latest install it forgets my device without me telling it?
|
|
|
08-23-2018, 09:35 AM
|
#18
|
Human being with feelings
Join Date: May 2009
Posts: 11
|
I just noticed this new functionality too. One of my problems is that each time i plug a device into a new usb port or on a different port on my hub it gets assigned a new(id?) so some of my devices show up multiple times and its hard to distinguish which is the correct one. I just deleted all of them for now and ill hook up in the studio later and hopefully it shows up again. It would be nice to know i can hook up a device on any bus and it be recognized as the same device. have you guys noticed that?
|
|
|
08-23-2018, 09:54 AM
|
#19
|
Human being with feelings
Join Date: Aug 2015
Posts: 3,669
|
that's a result of lazy driver development. novation never fixed that shit for the og launchpad, so i had 10 Launchpad devices to delete once this useful feature was released.
|
|
|
08-23-2018, 10:02 AM
|
#20
|
Human being with feelings
Join Date: May 2009
Posts: 11
|
it gets particularly annoying when the device has 3 or more midi devices it recognizes like my Boss GT-001 has 3 different items that it show up as (times) the number times i reconnect it differently..... i just noticed that each has an input id i wonder if i can reassign that to clean up the list. ill have to mess with it later.
|
|
|
03-13-2019, 08:13 PM
|
#21
|
Human being with feelings
Join Date: Oct 2016
Posts: 100
|
I couldn't get my novation controller to work after upgrade. I figured reaper grab the driver in a previous project I then uninstalled and reinstalled that did not work so I tried to have reaper forget the device, disconnect the novation keyboard controller, and restart the computer, reconnect the to sl-mk II and start reaper. Reaper doesn't see the keyboard. How to I Unforget the device and get my midi controller Back? What's more, when I get listed how do I remove the NA prefix so I can use it. I've been trouble shooting this for a couple of hours now I'm just frustrated!
|
|
|
03-25-2019, 02:57 AM
|
#22
|
Human being with feelings
Join Date: Apr 2016
Posts: 6
|
Quote:
Originally Posted by V1b3zman
How to I Unforget the device and get my midi controller Back? What's more, when I get listed how do I remove the NA prefix so I can use it. I've been trouble shooting this for a couple of hours now I'm just frustrated!
|
Did you find a solution for this issue? I've lost the midi connections to our Behringer XR18 while updating our recording PC.
First got the Error message, then told Reaper to Forget the device. Because it was annoying. Now I would like to re-connect the midi but with no succes.
Latest drivers and firmware are installed. Also installed the latest Reaper version.
Thanks in advance!
|
|
|
11-04-2019, 05:03 AM
|
#23
|
Human being with feelings
Join Date: Oct 2015
Posts: 6
|
Argg
The following MIDI inputs could not be opened: :
Oxygen 49
Yamaha MX Series-1
Yamaha MX Series-2
Yamaha MX Series-3
Yamaha MX Series-4
Yamaha MX Series-5
Komplete Kontrol DAW - 1
The following MIDI outputs could not be opened:
Yamaha MX Series-1
Yamaha MX Series-2
Yamaha MX Series-3
Yamaha MX Series-4
Yamaha MX Series-5
Komplete Kontrol DAW - 1
My problem is, I use both the Yamaha MX49 (though not currently plugged in)
and the Komplete Kontrol S88...currently, like all the time.
I got the update notice, did so, then couldn't hear any of my tracks done on Komplete Kontrol....from an hour before.
If this was part of the update...it should have been marked in red...with WARNING before it.
How do I fix this please? My muse is only so patient.
|
|
|
11-04-2019, 09:17 AM
|
#24
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
To be clear only the warning is new -- if the devices couldn't be opened, they also wouldn't be able to be opened with previous versions. Maybe go look in the MIDI device list to see what's going on?
|
|
|
11-04-2019, 09:45 AM
|
#25
|
Human being with feelings
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,686
|
For some USB-Midi devices, Windows creates a new name every time you plug it into a different socket, using the "....--n" notation. The names each stay associated with the socket, in case you re-plugin that device.
With other devices Windows always uses the same name, actually preventing that you can use two of them at the same time.
-Michael
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 11:29 AM.
|