INTERACT FORUM
Windows => JRiver Media Center 33 for Windows => Topic started by: haggis999 on March 05, 2025, 09:59:51 am
-
The OSD is useful to me when playing videos via JRemote, but I want to turn it off when playing video clips via a batch file so that the volume slider is hidden. That slider serves no purpose for me in this situation as I control volume via an amp, not MC.
I am trying to use the following format of batch file to provide a solution, with several of these batch files being triggered in succession during a PowerPoint presentation. However, it is proving to be very unreliable. It makes no difference whether I use MC33.exe /MCC 28043 or MC33.exe /MCC 30025,0 to turn off the OSD; at least half the time the volume slider is still visible at the start of a video.
Am I doing something wrong here or are the 28043 and 30025 MCC commands broken?
@echo off
rem Turn off OSD
MC33.exe /MCC 28043
rem MC33.exe /MCC 30025,0
MC33.exe /Clear
MC33.exe /Mode Display
MC33.exe /PlayReplace "C:\xxxxxxxx\My video.mkv"
rem Turn OSD back on
MC33.exe /MCC 30025,1
rem Exit MC
MC33.exe /MCC 10078,1
-
I just tried MC33.exe /MCC 30025,0 and it made the volume buttons on my keyboard no longer show the OSD.
-
My remote button uses MC33.exe /MCC 30025,-1
It's working exactly as expected also. Have you tried just using the "toggle" switch of "-1" instead?
Your use case is niche. If you haven't tried the toggling switch, I would advise to do so, you never know...
I would be irked if any changes to accommodate this batch file approach affected my remote control button. To this end, I'm trying to help, whilst at the same time, protect my own interests ;)
-marko
-
My remote button uses MC33.exe /MCC 30025,-1
It's working exactly as expected also. Have you tried just using the "toggle" switch of "-1" instead?
Your use case is niche. If you haven't tried the toggling switch, I would advise to do so, you never know...
-marko
My original tests were made using the toggling option of MCC 30025. I moved to the ON and OFF options in the hope that they would prove more reliable.
Simply executing one of those batch file options for turning off the OSD and then checking MC to see if it had worked was never a problem for me. It seems to be an issue related to running a sequence of those batch files. I will do more testing to see if I can find any recognisable pattern of behaviour.
I would be irked if any changes to accommodate this batch file approach affected my remote control button. To this end, I'm trying to help, whilst at the same time, protect my own interests ;)
The last thing I would wish is to mess up the MC user experience for anyone else. I'm looking for a niche solution for a niche use case :)