Driver update changes name of interface breaking every Midi !!

Author
Post
Essentials Only Full Version
larrymcg
Max Output Level: -64 dBFS
  • Total Posts : 1310
  • Joined: 2003/11/05 17:00:22
  • Location: Redding (Northern California)
  • Status: offline
2011/05/29 20:40:57 (permalink)

Driver update changes name of interface breaking every Midi !!

I've been using an old USB Midisport 4x4 midi interface (now known as M-Audio) for years (on several PCs - Win Me and a couple Win XP systems).  Has always worked great except that on this Win XP system the driver install seemed a bit weird.  The Dev Manager complained (over a year ago) that the device could not start but it worked fine -- so I ignored the device manager.  Recently I got an error that said some driver (it was the MidiSport driver) was leaking memory.  And I got a bad SHS7 crash a couple days ago (BSOD and all that fun).

So I thought a driver update was a good thing to try.  Well, I got the latest driver and installed it and all looked good EXCEPT that the new driver changed the name of the device!  All of a sudden all of my SHS7 projects complained that the midi device could not be found!  Grrrrrrr.......  I could fix up the name for that project but opening the next project would give the same error.

SHS7 allows two name for a midi interface:  The hardware name and a "friendly name".  I have been running with the "Use Friendly Name" option checked.  The error I was getting was "Device XXXX can not be found" where XXXX was the friendly name I had been using.  So I made sure the friendly name of the device was XXXX.  But SHS7 still complained that the device could not be found.  Clearly SHS7 is looking for the device using the hardware device name, which was changed by the driver update.

I've had to do a System Restore to just before the driver update was done to get my projects to run without fixing up every one of them.

I don't see a way to convince SHS7 to use the new device name in place of the old device name.
Is there a way to do that?

--Larry

PS:  Old trusty and useful ProAudo9 allowed me to use the new device name and all the midi sequences opened just fine with PA9.  It seems like new version of applications (e.g. SHS7) somehow degrade in flexibility.  :(


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
#1

9 Replies Related Threads
    Guitarhacker
    Max Output Level: 0 dBFS
    • Total Posts : 24398
    • Joined: 2007/12/07 12:51:18
    • Location: NC
    • Status: offline
    Re:Driver update changes name of interface breaking every Midi !! 2011/05/30 08:35:07 (permalink)
    IDK the answer there Larry, but it looks like System Restore is your best friend in this case.

    questions..... if you have a lot of projects this might be a PITA to change all the device names..... but....

    Once you change the name (with the new driver running) and close the project, then reopen it again... does it work properly at that point or do you need to change the device name every time you open the files?


    Also...... did you attempt to update the driver when the system was functional or was it non-functional after the BSOD?  Was the update an attempt to get it working or was it working OK after the BSOD and you did the update to the driver?

    My website & music: www.herbhartley.com

    MC4/5/6/X1e.c, on a Custom DAW   
    Focusrite Firewire Saffire Interface


    BMI/NSAI

    "Just as the blade chooses the warrior, so too, the song chooses the writer " 
    #2
    Tap
    Max Output Level: -30 dBFS
    • Total Posts : 4536
    • Joined: 2008/10/09 11:55:30
    • Location: Newburyport, MA
    • Status: offline
    Re:Driver update changes name of interface breaking every Midi !! 2011/05/30 10:39:46 (permalink)
    It may also be possible to rename the new driver with the name of the old one???

    MC4 - M-Audio FW410 / Behringer UCA202 - Fender Strat / Jazzmaster / DuoSonic / Washburn / Peavy Foundation M-Audio Radium 49 Roland Juno 106 / JazzChorus / Seymore Duncan Convertible - HP A1230N ( AMD Athalon 3800+ 2G Ram + 200G HD )

    http://soundclick.com/cut2thechaise

    #3
    Crg
    Max Output Level: 0 dBFS
    • Total Posts : 7719
    • Joined: 2007/11/15 07:59:17
    • Status: offline
    Re:Driver update changes name of interface breaking every Midi !! 2011/05/30 11:34:08 (permalink)
    If you have named two different drivers with the same friendly name,  Win XP will look for the driver first installed. The old driver is probably still there. Did you manually delete it? Your project data may have code in it that references the old driver. I think you need to use the update driver function in device manager and delete the old driver and update to the new one.

    Craig DuBuc
    #4
    DerGeist
    Max Output Level: -84 dBFS
    • Total Posts : 329
    • Joined: 2008/01/28 16:40:56
    • Status: offline
    Re:Driver update changes name of interface breaking every Midi !! 2011/05/30 11:54:21 (permalink)
    I assume that my punishment in the pits of hell will be to attempt to get my midisport to work for eternity.
     
     
    #5
    larrymcg
    Max Output Level: -64 dBFS
    • Total Posts : 1310
    • Joined: 2003/11/05 17:00:22
    • Location: Redding (Northern California)
    • Status: offline
    Re:Driver update changes name of interface breaking every Midi !! 2011/05/30 12:17:23 (permalink)
    Guitarhacker


    IDK the answer there Larry, but it looks like System Restore is your best friend in this case.

    questions..... if you have a lot of projects this might be a PITA to change all the device names..... but....

    Once you change the name (with the new driver running) and close the project, then reopen it again... does it work properly at that point or do you need to change the device name every time you open the files?


    Also...... did you attempt to update the driver when the system was functional or was it non-functional after the BSOD?  Was the update an attempt to get it working or was it working OK after the BSOD and you did the update to the driver?


    When the project is opened, SHS7 brings up a message box saying the device (showing the friendly name) can not be found and gives a list of devices (friendly names) to use instead.  So I select the correct device (which has the same friendly name!) and close the message box.  It plays fine.  At that point the project does not show that it has been modified and if I close it it does not ask to save changes.  If I reopen the project it brings up the message box about the missing device.  However, if I force the project to save, then the next time I open it it is OK.  So I guess the short answer to your question is that Yes, the project plays correctly the next time as long as you force it to save.  (I do this by doing something simple like muting and unmuting a track.)

    I did the driver update several days after the BSOD so the system was functional (and so was the midisport).

    --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
    #6
    larrymcg
    Max Output Level: -64 dBFS
    • Total Posts : 1310
    • Joined: 2003/11/05 17:00:22
    • Location: Redding (Northern California)
    • Status: offline
    Re:Driver update changes name of interface breaking every Midi !! 2011/05/30 12:19:46 (permalink)
    Tap


    It may also be possible to rename the new driver with the name of the old one???


    I don't know how to rename the driver.  I looked for a way to do it with device manager.  No joy.  The installer doesn't provide an option for rename.  The actual file names of the installed driver don't seem to have any relationship to the driver name as listed in the device manager.

    --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
    #7
    larrymcg
    Max Output Level: -64 dBFS
    • Total Posts : 1310
    • Joined: 2003/11/05 17:00:22
    • Location: Redding (Northern California)
    • Status: offline
    Re:Driver update changes name of interface breaking every Midi !! 2011/05/30 12:31:33 (permalink)
    Crg


    If you have named two different drivers with the same friendly name,  Win XP will look for the driver first installed. The old driver is probably still there. Did you manually delete it? Your project data may have code in it that references the old driver. I think you need to use the update driver function in device manager and delete the old driver and update to the new one.


    I did the install a few different ways.  I tried installing the new driver without removing the old one first.  That left a bit of a mess with the device manager showing both working and non-working devices for the midisport. 

    So I used RevoUninstaller to totally remove the new driver.  The old driver has never shown up as an uninstallable driver but it did have an uninstall file so I used it.  I think I also tried uninstalling the old driver via the device manager too.

    So, I'm pretty sure that I ended up with only the new driver installed.  And it had the different name.

    It seems clear that the projects have references to the old driver name (both the physical driver name and the friendly name).  That's the problem since the old physical name is not present in the system any more.  The cwp projects show the friendly names but SHS7 will not use the driver even if its friendly name is the same.  It seems to demand that the friendly name and the physical name both be available.  As I noted in my OP, ProAudio9 let me change the device name in one place and then all of its projects opened fine.  Doing the same change in SHS7 does not work.  The change I'm referring to is selecting the midi interfaces via the menu Options>Midi Devices.....          To me this is a blunder in SHS7.

    --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
    #8
    larrymcg
    Max Output Level: -64 dBFS
    • Total Posts : 1310
    • Joined: 2003/11/05 17:00:22
    • Location: Redding (Northern California)
    • Status: offline
    Re:Driver update changes name of interface breaking every Midi !! 2011/05/30 12:34:38 (permalink)
    DerGeist


    I assume that my punishment in the pits of hell will be to attempt to get my midisport to work for eternity.
     
     


    I've assumed that when I go to a Win7 system I will have to get a new midi interface.  But now that I see how SHS7 handles a changed device name, I figure that whatever I do I'm screwed.

    Surely, folks out there have gotten new midi interfaces and have not had to change the device selections in every one of their projects?

    --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
    #9
    larrymcg
    Max Output Level: -64 dBFS
    • Total Posts : 1310
    • Joined: 2003/11/05 17:00:22
    • Location: Redding (Northern California)
    • Status: offline
    Re:Driver update changes name of interface breaking every Midi !! 2011/06/02 18:19:52 (permalink)
    I did a small experiment where I changed the friendly name.  No problem with that.  The existing projects just showed the new friendly name.  So it is clear to me that SHS7 looks for the device using the hardware driver name.  If the hardware driver name changes SHS7 gives errors.

    I don't really believe that SHS7 can act that way.  I has to be possible to get a new midi interface and use it wherever the old one was used without having to change all the references in the existing projects.

    Right?


    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
    #10
    Jump to:
    © 2024 APG vNext Commercial Version 5.1