ReMOSD
ReMOSD copied to clipboard
qt-kaneko
Every time PC boots up ReMOSD shows this error with the cmd prompt.
System.InvalidOperationException: Media OSD was not found :( at ReMOSD.MediaOsd.Find() at Program.<Main>$(String[] args)
+--------------------------------------------------+ | PLEASE CONSIDER SENDING A COPY OF THE TEXT ABOVE | | OR SCREENSHOT WITH THIS WINDOW TO A DEVELOPER. | | | | Telegram: @qt-kaneko | | GitHub: github.com/qt-kaneko/remosd | +--------------------------------------------------+
Press any key to close this window . . .
Does it work if you just run it manually (not in autostart)?
It does work in manual as well as autostart also, it's just that this error pops up else it's working everytime, even when there is this error.
Does it work if you just run it manually (not in autostart)?
It does work in manual as well as autostart also, it's just that this error pops up else it's working everytime, even when there is this error.
This is very strange.
If it errors out it should not possibly work (are you sure it is working / are you sure you are not using other tools that already modify volume osd?).
And does it show error when you run it manually or only when it is run by autostart?
Also are you using the latest version from GitHub releases?
Do you see volume OSD showing up when ReMOSD is executed?
My bad for reporting falsely, I reported about when it didn't show error on startup as when it did.
When the error is there on startup it doesn't hide the osd. And in this case when I launch it manually it does hide the osd.
I am using tha latest release downloaded from github and it is placed in shell:startup.
Do you see volume OSD showing up when system is started (+- when error shows up)?
Also do you see volume OSD showing up when ReMOSD is executed manually?
You can try if this one works. I have made it wait more, maybe your OS is still loading when ReMOSD starts so it can't find Media OSD cause it has not been loaded yet ¯\_(ツ)_/¯
Do you see volume OSD showing up when system is started (+- when error shows up)?
When error doesn't show up, volume osd is hidden as it should be with the app working. When error appears, volume osd is not hidden.
Also do you see volume OSD showing up when ReMOSD is executed manually?
No, I don't see volume osd showing when reMOSD is executed manually.
You can try if this one works. I have made it wait more, maybe your OS is still loading when ReMOSD starts so it can't find Media OSD cause it has not been loaded yet ¯_(ツ)_/¯
I will put this in the startup folder and see if it works without giving the error.
No, I don't see volume osd showing when reMOSD is executed manually.
I mean, ReMOSD must "flash" volume OSD for it to work, does this happen in your case?
P.S. Application will trigger show of Media OSD on launch, this is necessary for it to work. (From README.md)
Also please report if your issue was fixed with the file I have sent so I can push it to a new release if it helps.
I mean, ReMOSD must "flash" volume OSD for it to work, does this happen in your case?
It does flash it now.
Also please report if your issue was fixed with the file I have sent so I can push it to a new release if it helps.
It has been working fine for the past few startups; I will see it some more times & would report it. Also, I had autothotkey volume script that was running also on startup so could it be that it was interfering with ReMOSD?
This was the script.
; Fix Windows Volume:
F10::
SoundGet, volume
Send {Volume_Up}
SoundSet, volume + 2
Return
F9::
SoundGet, volume
Send {Volume_Down}
SoundSet, volume - 2
Return
Indeed, the script is messing with it, when the script was not running at startup ReMOSD was working perfectly now when it is it running at startup with ReMOSD it shows the error.