soundsubs
Max Output Level: -81 dBFS
- Total Posts : 496
- Joined: 2003/11/13 13:28:52
- Location: denver
- Status: offline
reassigning driver names?
hi gang-- yesterday i moved my computer to the other side of the room. in doing so, i unplugged my midisport 8x8 and of course, plugged it into a new USB port. of course sonar threw a fit about this, and wants me to rename every port, etc, because they are all now named "2 midisport 8x8" instead of just "midisport 8x8" like before. any suggestions?
Sonar Platinum | modular synthesizers galoreWin 10 // Dell Xeon's | RME UFX | Maschine 2.3 | Virus TI | Roland System-1
|
FastBikerBoy
Forum Host
- Total Posts : 11326
- Joined: 2008/01/25 16:15:36
- Location: Watton, Norfolk, UK
- Status: offline
Re:reassigning driver names?
2012/05/19 01:55:33
(permalink)
This is a windows issue. Sonar gets the driver names from there. Windows sees the device as a separate new device if the same device is plugged into a different USB port and installs it as such. Hence the "2". It could be worse some of mine are on "4". You can use the windows variable SHOW_NONPRESENT_DEVICES as described HERE to remove the "other" instance(s) but that still isn't going to change the name of the existing instance. The only solution to get the name back to the original AFAIK is to plug the device back into the USB port it came from. Having said that there is no need as you should get asked to reassign missing devices as you load a project. Once you've reassigned it and saved the project it won't ask again unless there's another change of course. At least it is handled well by Sonar now. Several versions ago chaos would have broken out......
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/19 02:56:31
(permalink)
When using Win 7 it is supposedly preferable to stick to one USB port for each device. The reason being that Win 7 only allows up to 10 USB MIDI port hubs which basically means you could only have ten MIDI devices going at once. Not a problem for pretty much anyone because who has ten devices hooked up at once? The problem is once you install your device Windows creates the USB MIDI hub for that device and associates it with the port you originally installed it to. If you move it to another port it wants to create a new USB MIDI hub thus taking up another of your ten available hubs. It keeps the original hub in place so that's why your are getting the [device name]2 message when plugging it into the second port. This ends up causing problems for users who have a lot of devices or buy new devices because all of a sudden they ran out of MIDI hubs within Win 7 and can't create a new one for their new device. Unfortunately MS decided we as the end user are too dumb to be allowed access to those port names and settings (at least not easily) and apparently you can't even access them through the control panel (I tried just out of curiosity and no... I could not find any access through usual channels). However M-Audio supposedly has a MIDI port fixer software that supposedly will let you delete old unused hubs so you can use them with other devices but I have no need for it so have not tried it. I stumbled across this info a few months back trying to get my padKontrol up and running on my laptop. I may have some terminology wrong and I'm sure there are those smarter than I that could indeed tell you how to access those port/hub names and mess with them but as far as I know it is not really something the average user would be able to figure out easily. So the moral of the story is, when using MIDI controllers or other MIDI devices with a Win 7 system choose your USB ports wisely and always use the same port for the same device whenever possible. It will save headaches. If anyone has more info on this I'd like to hear it because it does seem to be a semi obscure tech topic and it took a bit of digging for me to find details on the subject all those months ago. Peace.
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re:reassigning driver names?
2012/05/19 03:08:39
(permalink)
Windows Vista and I am sure Win 7 allows 127 USB ports. I have 12 on my MB. I can't find anything on USB MIDI devices. That is the limit of them.
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/19 03:30:45
(permalink)
It's the actual MIDI USB that has ten. Like synth keyboards, MPC units, drum triggers... stuff like that. Mice and QWERTY keyboards don't use up the MIDI USB stuff. I'll try to find the article again. I thought I had it bookmarked but I ain't seeing it... really gotta clean up these bookmarks. lol
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/19 03:46:07
(permalink)
Okay... after hunting around a bit I finally found a reference to what I was trying to say... very poorly. Apprently what I was talking about was USB MIDI port driver slots... or something. This is from a trouble shooting article about a Korg keyboard... The 10 MIDI drivers limit of Windows may have been exceeded. Every time you use a different USB port, one of those MIDI drivers will be used until there are no more free MIDI driver registry keys available. The easiest way to check is to run the Korg USB-MIDI uninstaller which is by default installed in Program Files -> Korg -> KORG USB-MIDI Driver Tools -> Uninstall KORG USB-MIDI Device. When it runs, click the NEXT button, and it will automatically analyze the "midi" sections of the registry and give you a list of all MIDI devices. If there are more than 10 devices shown, you will need to tick the check boxes and uninstall some of them until there are less than 10 devices in the list. The "Options" button allows you to uninstall non-Korg MIDI devices. My apologies... as I said I only touch on that briefly months ago while dorking around with the pK.
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re:reassigning driver names?
2012/05/19 04:11:53
(permalink)
There is a limit on MIDI ports with Windows but its been upped since win XP. I can't remember the new number but its more than ten. BTW this has nothing to do with USB. Edit I was wrong. Read This. What I forgot is that Vista and Win 7 have no limit on MIDI ports. XP did and it was 10. after SP2 it was raised to 32.
post edited by John - 2012/05/19 06:25:18
|
soundsubs
Max Output Level: -81 dBFS
- Total Posts : 496
- Joined: 2003/11/13 13:28:52
- Location: denver
- Status: offline
Re:reassigning driver names?
2012/05/19 11:43:49
(permalink)
i wonder if unistalling the device and drivers too will reset the counter to 0? i remember having an issue once with this on XP, and korg had this midi device detector and remover that worked great... hmm time to go looking
Sonar Platinum | modular synthesizers galoreWin 10 // Dell Xeon's | RME UFX | Maschine 2.3 | Virus TI | Roland System-1
|
soundsubs
Max Output Level: -81 dBFS
- Total Posts : 496
- Joined: 2003/11/13 13:28:52
- Location: denver
- Status: offline
Re:reassigning driver names?
2012/05/19 23:30:17
(permalink)
well googling led me back to me. unfortunately the winxp korg driver viewer doesnt work in win7. so after about 30 min of plugging into other usb ports, i got them matched. i went through 6 ports before i got them. funny, win7 appended a number in front of each one.
Sonar Platinum | modular synthesizers galoreWin 10 // Dell Xeon's | RME UFX | Maschine 2.3 | Virus TI | Roland System-1
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/20 00:23:58
(permalink)
@John... your update didn't bump the thread so I didn't see it today. I think the issues I was referring to were probably, like you said, old ones as that m-audio MIDI Fix software I was talking about seems to date back to 2003. All of the info on this particular subject I gleaned from the Korg forums which don't really update as quickly as this one does... so my info was likely oooold and provided by old school keyboard kurmudgeons. That said, yes soundsubs (the op of this thread), it would probably be best to uninstall your MIDI USB device drivers and reinstall them on the new port following your device manual if you intend on switching things around. I realize I kind of f*@$ed up myself by cramming the pK into one one of the front panel USB ports on my case when I really should have installed it on one of the USB ports right on the MOBO instead... so I will be doing that dance myself and thanks for posting this to remind me. Peace and good luck.
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/20 00:34:11
(permalink)
Actually, John... do you know if uninstalling the device driver frees up the MIDI driver lane (or whatever it's called) that it was using in Win 7? Or does it stay there and when you reinstall the driver it creates a new lane/hub/thingy/whatevs? (really gotta get my lingo down, sorry)
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re:reassigning driver names?
2012/05/20 01:15:25
(permalink)
It would seem that an uninstall would get rid of a USB unit connection to a particular port but USB is also meant to install plug and play USB units. I think that once a USB device has been installed to a port Windows looks for a driver automatically. If it finds one on the system it will try to use it. This will also mean it may also be associated to a port that no longer has that device on it. Thus this may be why we have the driver with an appended number. I don't know this for sure its my guess as to how this stuff is done from using USB for a long time now. I would go into system devices and see if I couldn't delete the driver there for a specific USB port. Or search the system drive for it and try to delete it that way. The problem is that it could be in the registry too. I hate having to go to the nuts and bolts of an OS to simply install a unit or having to even talk about it. But we Windows users need to have some OS hacking ability just to keep things running well. If you know what I mean. We do have some very knowledgeable members on the forum that offer fixes for this sort of thing all the time. I try to avoid these problems by not using different USB ports for my gear. Once installed it stays installed.
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/20 01:32:56
(permalink)
Fair enough. But seriously if you start digging around for those USB MIDI things in Win 7 they just aren't there through the regular control panel options. At least I couldn't find them. I might have better luck through the Windows GodMode panel I found out about recently. However I have more pressing issues at hand... mostly meatworld ones which are far more obnoxious and boring than PC ones. ;-p
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re:reassigning driver names?
2012/05/20 01:36:21
(permalink)
Beepster Fair enough. But seriously if you start digging around for those USB MIDI things in Win 7 they just aren't there through the regular control panel options. At least I couldn't find them. I might have better luck through the Windows GodMode panel I found out about recently. However I have more pressing issues at hand... mostly meatworld ones which are far more obnoxious and boring than PC ones. ;-p This might help or it might not.
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/20 02:01:36
(permalink)
That looks to be more about general USB type stuff like mice, QWERTY's, printers, etc. I really need to find the bookmarks I had about this stuff because something is just ringing in my head about USB MIDI limitations in windows. Like specifically USB devices. It's an obscure issue but would effect people who cycle through many USB MIDI devices on the same system (like a studio perhaps) and they just can't install above a certain amount because they have too many previous instances of USB MIDI controllers. IDK... my bookmarks are the virtual equivelent of Fox Mulders desk at this point so I'm not gonna hunt around. I'd bet that Jim fellow who builds computers would know what the hell is up. It might vary between OS versions too. Like there is a certain limit within Win 7 Home and another within Pro. That article is interesting though because it seems to allude to PnP devices not actually just plugging in and working but they take up a specific little segment of Windows for themselves and if you plugged in enough devices (like over 130) you would run out of USB hubs/lanes/whatever they are called within Windows and then have to clean things up a bit. Again though... more of a tech brain teaser than something that really effects me or most users. Perhaps I'll ask my wicked smart friend if I think of it. Peace.
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re:reassigning driver names?
2012/05/20 02:08:45
(permalink)
In Vista and Windows 7 there is no limit to the number of MIDI ports. That was a problem under XP.
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/20 02:23:56
(permalink)
But specifically MIDI through USB ports is what the issue seemed to be. Not MIDI in general. It was a big thing the guys on the Korg forum were on about. I remember seeing like charts and everything. IDK... maybe it was a dream or something. God knows I've been cramming my head with far more of this tech crap than can be healthy. lulz... Anyway, I gotta eat. Take care, John.
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re:reassigning driver names?
2012/05/20 02:33:56
(permalink)
Beepster But specifically MIDI through USB ports is what the issue seemed to be. Not MIDI in general. It was a big thing the guys on the Korg forum were on about. I remember seeing like charts and everything. IDK... maybe it was a dream or something. God knows I've been cramming my head with far more of this tech crap than can be healthy. lulz... Anyway, I gotta eat. Take care, John. I'm not fully following you on this. What I get is you have been told that Windows has a limit on the number of MIDI ports. It doesn't matter whether its via USB or some other connectivity. It was a problem with XP and is no longer a problem since Vista. For example with XP and no SP it could only support 10 MIDI ports. These could be USB or serial or parallel. Now that limitation has been removed. It is not a USB issue and never was.
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/20 02:55:32
(permalink)
Okay... and really this is probably just crazy talk from scrounging the bottom of the intertubes and I am not saying this is at all factual it's just what I remember reading but what I'm saying is... MIDI in general can have the amount of lanes/hubs/drivers (whatever we want to label it for our discussion) that you are saying within Windows. That would mean through whatever MIDI connection like Firewire, PCI, regular old MIDI connections AND USB.... BUT only a certain amount of those lanes/hubs can be affiliated with actual USB ports. Once you have attached and installed enough USB MIDI devices those lanes fill up and you have to remove a previous device. You could still attach a MIDI device via other connections like a PCI card or whatever. Maybe that's a little clearer... perhaps not sane or based in reality but at least an explanation of what seems to be bouncing around in my little monkey brain. Now I will definitely have to dig through my bookmarks to find this topic. I swear I've got it in there somewhere. Man, I must sound like a lunatic. lol...
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/20 02:59:55
(permalink)
But the point is... everyone should pick a USB port for their MIDI device and stick to it. All that other crud shouldn't effect most people anyway.
|
larrymcg
Max Output Level: -64 dBFS
- Total Posts : 1310
- Joined: 2003/11/05 17:00:22
- Location: Redding (Northern California)
- Status: offline
Re:reassigning driver names?
2012/05/20 14:09:46
(permalink)
Beepster But the point is... everyone should pick a USB port for their MIDI device and stick to it. All that other crud shouldn't effect most people anyway. I'm on XP and have Cakewalk Pro Audio 9 and Sonar Home Studio 7 using an M-Audio USB MidiSport 4x4. I recently updated the driver and kept the device plugged into the same USB port. The result was that the name of the device changed a bit. This caused SHS7 to demand that I fix up the midi device assignments on every project. However, Pro Audio 9 was happy to keep using the midi interface with no changes needed on my part. Yahoo! I was using "friendly names" in SHS7 but they didn't help. The issue seemed to be with the device name the friendly names were associated with. Grrrrr...... --Larry
Intel Core i7-4790 @3.6GHz; 8GB; Win10 Pro 64bit; 1TB disk + 3TB ext disk; Midiman Fineline mixer; MidiSport 4x4 midi I/F; Roland JV-30 kbd/synth; Yamaha TG55 synth; Rx with 3 piece Home audio speakers; Sonar X3e Studio
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/20 16:11:13
(permalink)
@larrymcg... Well that just sounds infuriating. I'm glad you shared that story because if it had happened to me I wouldn't have known what the *^&$ was going on. So if I'm reading that correctly you had used a "friendly name" to rename your device, then updated the driver which changed the device back to it's factory name thus making all tracks/channels associated with the friendly name no longer work properly? I don't think I'll be using the Friendly Names option if that's the case.
|
FastBikerBoy
Forum Host
- Total Posts : 11326
- Joined: 2008/01/25 16:15:36
- Location: Watton, Norfolk, UK
- Status: offline
Re:reassigning driver names?
2012/05/20 16:21:30
(permalink)
Beepster @larrymcg... Well that just sounds infuriating. I'm glad you shared that story because if it had happened to me I wouldn't have known what the *^&$ was going on. So if I'm reading that correctly you had used a "friendly name" to rename your device, then updated the driver which changed the device back to it's factory name thus making all tracks/channels associated with the friendly name no longer work properly? I don't think I'll be using the Friendly Names option if that's the case. If a driver is unavailable for an input/output, for whatever reason, you will be asked at project load time if you wish to reassign that to another driver. You can either choose to do that if it's for a permanent reason such as a different driver instance (i.e. 2 - Midisport 8x8) in which case the reassignments will be made for you within that project. Alternatively if it's temporary change such as a device that you've just left disconnected you can choose to ignore the reassigment request in which case Sonar will reinstate the driver next time the device is present. The whole MIDI driver assignment issue was vastly improved a few versions ago. V8 IIRC - either way I've had no assignment issues for a long time and I run several MIDI ports (12 or 13+) and I also use friendly names.
|
larrymcg
Max Output Level: -64 dBFS
- Total Posts : 1310
- Joined: 2003/11/05 17:00:22
- Location: Redding (Northern California)
- Status: offline
Re:reassigning driver names?
2012/05/20 16:30:26
(permalink)
@Beepster, The friendly names still are important to me because I can use a short name so that the input or output number is visible in, for example, the console view. The physical names are long. Something like MidiSport 4x4 Out-1 and MidiSport 4x4 Out-2, etc. Since the port number is way to the right you can't see it in the console view. So I use friendly names to make them something like Out-1, Out-2, etc. The friendly names don't fix the midi device name changing issue but they do solve some other issues. --Larry
Intel Core i7-4790 @3.6GHz; 8GB; Win10 Pro 64bit; 1TB disk + 3TB ext disk; Midiman Fineline mixer; MidiSport 4x4 midi I/F; Roland JV-30 kbd/synth; Yamaha TG55 synth; Rx with 3 piece Home audio speakers; Sonar X3e Studio
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/20 16:40:03
(permalink)
I'm glad they've got it set up to hold our hands a little. With me if something dumb can go wrong it likely will so I try to make things as idiot proof as possible. In this case I think I could avoid any potential problems entirely by just leaving things on the same port. I'll probably only be using two controllers anyway so it should be very easy. pK and eventually a keyboard controller. It is possible I might look into a regular console controller at some point but as far as I can tell the pK does a pretty decent job as a stand in. I'm kind of wondering if I'll have any problems moving the pK from the front panel USB to a port directly on the MOBO. I haven't used it on any tracks though so I think all I'd have to do (if anything) is uninstall the drivers, move the pK to the new port and reinstall the drivers. But that is some fun for another day. I've got too many meatworld issues breathing down my neck at the moment.
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:reassigning driver names?
2012/05/20 16:44:12
(permalink)
@Larry... I see. I don't think I'll have any issues because as I said I'll only have a max of 2 devices and once I get a project going I'm pretty good at remembering where I put what. But you never know what the future holds. Maybe I'll become a MIDI addict and it will become a concern so definitely something to think about. Cheers!
|
soundsubs
Max Output Level: -81 dBFS
- Total Posts : 496
- Joined: 2003/11/13 13:28:52
- Location: denver
- Status: offline
Re:reassigning driver names?
2012/06/24 20:40:13
(permalink)
unfortunately this has flared back up for me. After trying (unsuccessfully) to get my Virus TI new OS5 loaded in Win7, its now showing "4-Virus TI" instead of just "Virus TI". coincidentally, i probably unistalled and re-installed it 4 times. argh. has anyone figured out how to uninstall or delete registry settings for these stupid numbers that show up in front of USB devices. this is so frustrating.
Sonar Platinum | modular synthesizers galoreWin 10 // Dell Xeon's | RME UFX | Maschine 2.3 | Virus TI | Roland System-1
|
soundsubs
Max Output Level: -81 dBFS
- Total Posts : 496
- Joined: 2003/11/13 13:28:52
- Location: denver
- Status: offline
Re:reassigning driver names?
2012/06/24 21:05:13
(permalink)
Good lordy i solved this myself. For others who might have this problem, or myself who will forget about this, google it, and end up back here: 1.) go into device manager 2.) under VIEW select "show hidden devices" 3.) delete any midi devices that are currently greyed out this should reset each counter to 1 THANKS ME!
Sonar Platinum | modular synthesizers galoreWin 10 // Dell Xeon's | RME UFX | Maschine 2.3 | Virus TI | Roland System-1
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re:reassigning driver names?
2012/06/24 21:38:12
(permalink)
You should have paid more attention to my post #12 above. In it I said much the same thing. Go to system devices.
|
FastBikerBoy
Forum Host
- Total Posts : 11326
- Joined: 2008/01/25 16:15:36
- Location: Watton, Norfolk, UK
- Status: offline
Re:reassigning driver names?
2012/06/25 01:50:15
(permalink)
John You should have paid more attention to my post #12 above. In it I said much the same thing. Go to system devices. Needed even have read that far I posted him the answer in #2.
|