Support
All support resources for our products. Here you can find answers to frequently asked questions, discuss with other users, recover a lost license code or file a support request.
Forum closed
This forum was closed and turned into an archive effective April 21, 2018. It is no longer possible to create new topics or reply to existing topics.

Thanks everyone for all the great questions and contributions over the years.

Please use the Contact form to get in touch.

Remote Buddy Forum

Overview 

AuthorThread
User

17.03.2010 20:14:29
Re: Can't get Plex to recognize multiple virtual remotes

This posting is older than 6 months and can contain outdated information.
Hi Felix,

Thanks for the information.

I created a separate behavior for this because it was greatly different from the built in Plex behavior, and I wanted to test this as an alternative without losing the built in. I did disable the original behavior for Plex and I also called the new one something different. Now that you mention it, however, the old one is still showing up in the selection menu when I activate RemoteBuddy. If it is unchecked in preferences, it should not be there, right? I'll have to check that again.

I am aware of the built in Plex capability that was built by Plex, but reading the forum entries about it, I believe this would be a better alternative. If you use their new approach, then you must configure Plex to not respond to normal Apple Remote commands, and this could lead to difficulties down the road. From what I read, they are also using a sequence of 3 commands to invoke each function... so 3 commands times the 6 buttons to get all the functions. This means that it takes 3 times as long to send each command vs. using the virtual remotes approach which sends a single command for each button press.

So back to my question, is there any way to troubleshoot this to test whether the actions are working correctly beyond what I described. Is there a way to exercise the behavior as a test without the remote? I am brand new to your product and still in the trial period, so forgive me if I'm not doing something correctly here.

Thread-display::