how do i fix this midi hardware setup error? FIXED

[ted]

o.k. here is,,,,

when i startup the recording computer, reaper does not recognize any midi...
the error is in midi hardware settings...

new, unknown, midi hardware settings have been enabled: e.g. - !!! NA Enabled
& the working midi hardware set has been disabled...

to fix, the !!! NA gets deleted & the working midi is enabled.
thus, all is good for that session.

next time i start recording computer i have to go thru
this exercise, again...

this been going on for a while & still i cannot find
the fix for... if you have any ideas, please, let me hear from you.

regards.
Ted

added: all this started with update 5.963
an install prior to 5.963 works fine.

today 11/29/18 - when i opened Reaper...midi hardware settings were correct... i have seen this before,too...
then, maybe next time opened, midi hardware settings screwed, again..

thank you!

[Knob Twiddler]

Delete all the N/A stuff and restart Reaper. It recognices the controllers again.
That is how I do it.

[nofish]

As Knob Twiddler said.
More info here:
https://forum.cockos.com/showthread.php?t=209673

[ted]

received your reply & tried your fix.
does or changes nothing for me...

this error is determined during the boot phase of computer...
this is a certainty. what is strange is sometimes a boots recognizes correct midi hardware setting, most boots finds wrong settings..

my best guess is somewhere there are 2 files same name that doe not test date to find latest version, therefore it uses @ random this unknown file in the boot process...all that it can be,, programs only run as programed...

or-

maybe, a registry error?

either way, just a guess.. i am no way qualified to determine, exactly, what is happening that causes this error.

but, by your response, am i 2 assume u have or have had same problem...
there must be many more. in another reaper forum, my post, same subject... there i am told to just "forget" the bad settings & they will simply disappear. 4 me that is not so...

i have 9 years invested in Reaper.. this new twist, 4 me, is clearly a frustrating situation 4 sure...

Regards,

[Knob Twiddler]

Originally Posted by ted

this error is determined during the boot phase of computer...
this is a certainty. what is strange is sometimes a boots recognizes correct midi hardware setting, most boots finds wrong settings..

my best guess is somewhere there are 2 files same name that doe not test date to find latest version, therefore it uses @ random this unknown file in the boot process...all that it can be,, programs only run as programed...

Do a test, power on your stuff before you start your pc and do a test with everything off when starting the pc. I think your problem lies in the booth process as you say. It has to do with your devices power on/off before you start your pc. While booting, windows is giving your devices a number I think.

[ted]

i've spent countless hours trying to fix...

today, i un-enabled the none existent midi hardware.
this changed status changed from NA-enabled to "not present".
enabled the real midi hardware & adjusted midi channels...

booted twice... & reaper correctly found correct midi hardware...
i never removed the not present midi hardware..

don't know it this is a real fix or not...
we'll c... certainly hope so...
this has been a real booger bear 4 me...

ted

[ted]

after several boots midi hardware problem back...
best i can conclude is that more than 1 copy of midihw.ini
must exist on computer.. & computer randomly chooses which 1 to use..

back to drawing board...

[Philbo King]

Post #6 in this thread might be worth trying.

https://forum.cockos.com/showthread.php?t=214028

[ted]

thanks for the response,,, i'll look into your solution,, later today...

all this been mostly a mystery,,, if i revert back to ver. 5.92,,, all is good...

thanks again,

[ted]

Originally Posted by ted

thanks for the response,,, i'll look into your solution,, later today...

all this been mostly a mystery,,, if i revert back to ver. 5.92,,, all is good...

thanks again,

tried your idea & best i can remember i've been there before...
anyways, i had no greyed out devices over entire device listing...

started looking for a way to disable midi (win7).. no luck there, either, so far... Microsoft made this a problem with win 7 release....

whatever is going on; i can rename a midi connection, only to boot, to find the default name back & midi channels changed to previous setting...

guess my only option is to keep computer hot 24/7...
now, this really sucks!!!!!!!!!!!!!!!!!!!!!!!

[toleolu]

There may be something on your system that's not playing nice with Windows 7.

Not suggesting you switch OS, but the sad fact is, new application software like plugins and such aren't being written with Windows 7 compatibility in mind.

May not be related to your current issue, but very likely something you'll have to deal with in the future.

Hope you're able to get this current issue resolved.

[hopi]

I saw that prob show up a few versions back... just went into the midi devices pref's and disabled all but the only one I use... that is enabled+control

been ok ever since

[ted]

Originally Posted by toleolu

There may be something on your system that's not playing nice with Windows 7.

Not suggesting you switch OS, but the sad fact is, new application software like plugins and such aren't being written with Windows 7 compatibility in mind.

May not be related to your current issue, but very likely something you'll have to deal with in the future.

Hope you're able to get this current issue resolved.

suspect your dead on right....
all this over my head... lol

take care

[ted]

Originally Posted by hopi

I saw that prob show up a few versions back... just went into the midi devices pref's and disabled all but the only one I use... that is enabled+control

been ok ever since

been all over the settings over last year....
like i've already said,, fix midi prefs. & 1st boot, normally, seems to always work... 2nd boot brings back the misery...lol

in midihw.ini for each midi channel there are 3 pieces of data: name, blank & some numbers...

when i boot & look @ midihw.ini & numbers for all active midi channels are same, upon opening reaper all is good,,,

then (normally 2nd boot) when i boot & look into midihw.ini & there are 2 sets of numbers... that's when the midi prefs. gets screwed...

don't have an answer... but, maybe a clue...

my recording computer is offline,, download all to a 2nd computer & transfer... so i have an exact copy of reaper. this morning,
thinking the midihw.ini might be corrupt, i replaced file... me & my wrong thinking,

[RobertP]

These may be long shots but ....
check all leads
turn anti virus off
turn off wifi if you have it on your pc(cant remember why this was a problem)
if you have drivers from old interfaces still installed uninstall them including in the registry.

You may want to install a clean, unused, portable version of Reaper and see if that works

good luck

[ted]

Originally Posted by RobertP

These may be long shots but ....
check all leads
turn anti virus off
turn off wifi if you have it on your pc(cant remember why this was a problem)
if you have drivers from old interfaces still installed uninstall them including in the registry.

You may want to install a clean, unused, portable version of Reaper and see if that works

good luck

already checked leads by replacing back down the road a piece,,,
no wifi,,,
clean install when upgraded to 64bit,,,

tried turning anti virus.. made no difference.

thanks for reply,

[ivansc]

So the next step is to do a fresh portable install of reaper.

By way of explanation, doing this allows you to have a new factory reset reaper install in a separate folder (Called "Reaper") in your C:\ drive, that won`t interfere with your existing install.

If you still have problems with your MIDI stuff in the fresh portable install, you`ll know you have a computer issue rather than a software one.

Hopefully the portable will NOT have the same issue & then it is just a case of figuring out what got changed in your existing install that stopped things working properly. But at least you will have a better idea of what is going on.

Good luck!

[ted]

Originally Posted by ivansc

So the next step is to do a fresh portable install of reaper.

By way of explanation, doing this allows you to have a new factory reset reaper install in a separate folder (Called "Reaper") in your C:\ drive, that won`t interfere with your existing install.

If you still have problems with your MIDI stuff in the fresh portable install, you`ll know you have a computer issue rather than a software one.

Hopefully the portable will NOT have the same issue & then it is just a case of figuring out what got changed in your existing install that stopped things working properly. But at least you will have a better idea of what is going on.

Good luck!

portable install does exactly same as reg. install..
so, midi problem not a software problem... thanks.... at least i know more than i did this morning...

[ted]

upgraded recording computer to win 10
bought RME 800 with less than 20 hours..
finished setup & my adjustments this morning
c me,,,i'm smiling...

thanks to all who offered the many suggestions.
reaper forum, the best.

regards
ted