User

09.02.2009 14:19:15

Hi Felix,

I was notified today that there was a new Plex behaviour available, but I can't find any notes about what has changed.

Also I now have the following behaviours in my list:

Plex 
Plex 
Plex II (this one I believe I somehow imported ages ago)

How do I know which is the 'current' one and/or best to use? Is there a way to remove the dupes?

Thanks,

Tom 

User

09.02.2009 15:14:16

Thanks for asking.

You can find more information on the blog.

If you didn't restart Remote Buddy after the update, you might have 
two entries for Plex. Usually, this is not necessary, but this is a 
special case, where a scripted Behaviour (created with the Behaviour 
Construction Kit) is replaced by a native Behaviour (written in 
Objective-C, compiled in Xcode).

Regarding "Plex II": this is not part of Remote Buddy. If you 
installed or created it yourself, you'll find it at

~/Library/Application Support/Remote Buddy/Behaviours/

(Re)moving it from there and restarting Remote Buddy should do the 
trick.

Best regards, 
Felix Schwarz 

User

09.02.2009 16:07:46

Thanks for the reply.

I've now removed Plex II, and a restart got rid of the duplicate Plex behaviours.

I've also decided for now to get rid of the multiple remotes I had added for Plex. It just creates too much confusion with other apps trying to work out what key the Harmony is sending in order to determine how to map it.

On a separate note, I can't seem to get a particular function to work properly with the new behaviour. Previously I had the 'Menu' button mapped to go to previous menu in Plex - this was done by mapping it to the Virtual Remote, Menu button. Now this just brings up the on-screen menu in Plex. I've also tried changing the mapping to 'Navigation:previous menu' but this does the same (brings up the Plex on-screen menu).

Any ideas how to resolve this?

Thanks,

Tom 

User

12.02.2009 17:46:07

The "Navigation: Previous Menu" sends the same button event packet to 
Plex as the Apple Remote support that comes bundled with Plex itself 
(and which the usage of the Virtual Remote did trigger). "Previous 
menu" sends the "previousmenu" XBMC command to Plex. Both are 
interpreted and handled by Plex itself.

I see three possibilites that this can go wrong:

1) Plex' keymap.xml file 
Did you modify the keymap.xml of Plex (or try to move it away and have 
Plex recreate it with its default settings)? The keymap.xml defines 
all reactions to button event packets that Plex is receiving.

2) Wrong mapping in Remote Buddy 
Also, did you try to reset the mapping of the Plex Behaviour to its 
defaults?

3) The Harmony sends other Apple Remote button codes than you expect 
for a particular button, consequently also triggering a different 
action. 
Please try with a stock Apple Remote / Apple Remote Harmony profile.

Best regards, 
Felix Schwarz 

User

12.02.2009 18:03:23

Thanks Felix.

I suspect the 'issue' is in Plex itself. I believe the 'previous menu' command when viewing video launches the on-screen menu rather than backing out of the playback into the previous menu.

For whatever reason this worked previously, so the behaviour may have changed in a recent Plex release. I've not modified any keymaps, but I will try deleting and letting Plex rebuild to see if that helps.

Failing that, a workaround seems to be programming a key press/hold as the 'Stop' command. I preferred the old method though and will try to find a way to get it back.

Will post once I work it out.

Regards,

Tom 

User

12.02.2009 23:03:16

I think one possibility could be that XBMC (and thus Plex) implements 
the overlay player controls as "menu", so that when you access the 
player controls and then "close" them, the command to go to the 
previous menu will show the overlay player controls again. I think 
I've observed this during development of the new XBMC Behaviour, but I 
may be wrong.

To me (from my outside perspective and observations - I'm not familiar 
with XBMC internals, so I may be wrong in parts) it looks like if XBMC 
internally has no real menu hierarchy, but really allows to have any 
menu follow one another. The magic that gives you the impression of 
hierarchical menus seems to be located inside the keymap.xml, which 
allows different actions to be executed for button presses depending 
on which menu is currently shown. The keymap.xml is honored by XBMC/ 
Plex if you use "Navigation: Previous menu", it is not honored and 
you're just taken to the previous menu on the stack of menus when 
using "Previous menu".

What happens if you press the menu button more than one time? Does 
XBMC take you to the previous menu as you'd have expected it to do 
with your first press?

Best regards, 
Felix Schwarz 

User

12.02.2009 23:08:11

 
Thanks for the reply. A second press of Menu when the on-screen controls are showing just hides them. If you stop the video and return to the previous menu, the 'Menu' key again works as expected.

It sounds like some fiddling with the keymap file might be able to sort this out, but it's odd behaviour anyway. There are others with the same complaint on the Plex forum, which is how I originally arrived at the solution to map Menu to virtual remote > menu. 

User

12.02.2009 23:19:07

I'm afraid this is really only solvable by/in Plex itself.

Have you tried to control Plex while Remote Buddy is not running? You 
should see the exact same behaviour of Plex without Remote Buddy 
running.

In general:

- Remote Buddy's Plex Behaviour doesn't know anything about which menu 
Plex is currently showing and will just send the same action/button 
event regardless of context.

- For all actions prefixed "Navigation:" the actions are 100% 
identical to those that Plex' own Apple Remote driver ("JS0:Apple 
Remote") would send to Plex (checked with the Wireshark packet sniffer).

- For all actions not prefixed with "Navigation:" it'll send events 
containing the actions that (usually) have the same name as displayed 
in Remote Buddy.

Best regards, 
Felix Schwarz