MC33 is fine for daily use now.
Good to know, Jim, thanks. I suspect the next iteration will be released shortly, so I'll jump in at that time.
As for Debug OSD... i had read some forum posts late last night that involved creating script files, and my eyes glazed over. After a night of rest, further examination, and some trial and error, I successfully programmed the Debug OSD command onto my Harmony Companion remote.
I have some extra comments/tips to add at the end of this post, regarding the solution, but I wish to recognize the solution source, posted by forum member Ashfall in Feb 2022.
https://yabb.jriver.com/interact/index.php?action=post;quote=914492;topic=130657.250----------------------------------------------
I'm doing this with an HP MCE remote using SendKey commands. Here's how:
1. Paste the below into Notepad and save it as SendkeyCTRL+J.wsf
<package>
<job id="vbs">
<script language="VBScript">
set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.SendKeys "^j"
</script>
</job>
</package>
2. Paste the below into Notepad and save it as SendkeyCTRL+R.wsf
<package>
<job id="vbs">
<script language="VBScript">
set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.SendKeys "^r"
</script>
</job>
</package>
4. For Command Name, enter "MadVR OSD Toggle" or whatever you prefer for CTRL-J.
5. Click Add, Custom.
6. Click Add Run, then add the path and file of the wsf file you created in step 1 for CTRL-J.
7. Click OK twice.
8. Repeat steps 4-7, but name it "MadVR OSD Refresh" and use the wsf file for CTRL-R.
9. Select the new commands and click Start Learning to program them to two different buttons on your remote. Depending on the remote, some buttons won't learn this, but some will, based on my personal experience.
----------------------------------------------
Personally, I'm satisfied implementing only the 1st of the 2 script commands outlined. I'd only edit Ashfall's written steps to make it a bit clearer for a layman like myself, as follows:
1. Create
.wsf file(s) as directed above.
2. Make sure you stash the .wsf file(s) somewhere appropriate on your drive (anywhere works), as JRiver will forevermore need to find it, so long as it remains a command in the Remote Control section of JRiver settings.
3. In JRiver, go to Tools - Options - Remote Control. Click 'Add - Custom'.
4. For Command Name, enter "
JRVR Debug OSD Toggle" or whatever you prefer for
CTRL+J.
5. For Command Actions, click 'Commands - Add Run', select 'All Files (*.*)' and then point 'Executable Filename' to the .wsf file you created in step 1 for CTRL+J, and you're done creating the 1st of 2 suggested commands.
6. If desired, repeat steps 4 & 5, but name it "
JRVR Debug OSD Refresh" and point JRiver to the .wsf file for
CTRL+R.
7. Next, teach JRiver what physical remote control button(s) you wish to map to your newly created command(s). Select a new command(s) and click 'Start Learning'... press the remote control button you wish to use... and JRiver should receive the signal and map/learn the appropriate button for that new command (assumes the computer which JRiver is on has an IR Receiver or is connected via Bluetooth to your remote system (ex. Harmony Hub)).
Further note from Ashfall: 'Depending on the remote, some buttons won't learn this, but some will, based on my personal experience.'
ATTENTION ALL: Watch-out for 2.4Ghz & Bluetooth Signals When Mapping Remote Buttons!!!Setup: My Harmony Companion remote control fires RF signals to my Harmony Hub... and my HHub sends Bluetooth signals to my computer/JRiver (optionally, I could have it set to blast IR signals). For my laptop/computer mouse, I have a wireless Kensington Trackball connecting via a 2.4Ghz USB nano receiver (optionally could connect via Bluetooth).
Observation: After setting-up the .wsf Ctrl+J command and teaching JRiver the button I wish to use on my remote, i tried it out during video playback and the command acted unreliably! The Debug OSD would show up as soon as a video started... and the remote button didn't do anything, though the OSD would appear and disappear seemingly at random intervals! I tried a few different things with JRiver and with Harmony Hub button programming, but nothing worked... UNTIL by happenstance, i noticed that the Debug OSD would appear and disappear at each new movement of my Trackball... and then I observed that not to be the case with my laptop's touchpad! I then unplugged the 2.4Ghz USB dongle for my Trackball... the Debug OSD stopped appearing/disappearing, but the remote still wasn't able to control the Debug OSD. So with the 2.4Ghz dongle still unplugged, I tried remapping the remote button in JRiver and... PRESTO, it works beautifully now!
Plugged my Trackball 2.4Ghz dongle back in, and still no issue - it was only a problem during the few seconds I spent trying to map the remote button. Especially odd 'cause the remote signal I was teaching JRiver with was via a Bluetooth connection with Harmony Hub, not 2.4GHz. Anyways -
something for community here to be aware of... competing signals of ANY type, messing things up, while teaching JRiver your physical remote buttons to map.Cheers, ya'll!