User

29.12.2012 19:20:49

Hi - I was uninstalling Plex and playing with XBMC and I no longer seem to have a Plex behaviour in Remote Buddy. I may have purposefully removed it, but now I can't seem to get it back. I've reinstalled Remote Buddy, but no dice.

Am I crazy? Wasn't there one to begin with? I'm pretty sure there was when I first installed Remote Buddy a few weeks back.

Is there someplace I can download it, or how can I reinstall a Plex behaviour?

I'm on Remote Buddy 1.22.1

Thanks! 

User

29.12.2012 22:00:01

Thanks for asking.

Remote Buddy ships with a Behaviour for Plex inside its own application bundle and decides during launch on whether or not to use it (depending on whether OS X Launch Services can find Plex on your system or not).

Which version of Plex are you using?

Best regards, 
Felix Schwarz 

User

29.12.2012 23:27:17

I am also missing a Plex behaviour. This happened since upgrading to the newest Plex Home Theater version, only available to plexpass subscribers. 

User

30.12.2012 03:20:28

That makes sense, because before I had an older version of Plex, and when I reinstalled it after doing without for a couple weeks, it's now the new "Home Theater" version of Plex. It's 0.9.9.46-20121227-8f504fc

Is there something I can edit quickly to convince Remote Buddy that this is Plex and it should enable the Plex behaviour?

Last edited: 30.12.2012 03:21:17 

User

30.12.2012 16:49:48

Another Plexpass member here and I'd also love to be able to use remote buddy with the preview release. The app's name is "Plex Home Theater" instead of "Plex". I tried simply renaming it to "Plex" but that didn't seem to allow remote buddy to recognize that it was still plex either.

If there's anything else I can do to test or try to get this working, I'll be glad to help however I can. Thanks in advance Felix! 

User

31.12.2012 16:36:01

Thanks for your answers.

Plex "Home Theater" has a new bundle identifier, so that Remote Buddy currently can't detect it as Plex.

I'm looking into the issue and will also discuss whether with Plex whether the bundle identifier change is really necessary, as it may cause issues for users beyond just Remote Buddy.

Happy new year everybody!

Felix 

User

02.01.2013 23:25:16

Any progress on this?

In know that this isn't RemoteBuddy's fault, but since there is no way to manually change the identifier (because it's hardcoded into the behaviour binary …) an update would be nice :)

Last edited: 02.01.2013 23:36:12 

User

08.01.2013 23:47:21

I'd much rather have a quicker update with a duplicate of the plex behavior set to trigger with the new bundle identifier for while you work out whether or not the plex developers should change their identifier.

At present, I'm falling back to using a keyboard to navigate through plex, and it isn't nearly as nice.

-Scott 

User

09.01.2013 02:34:02

Is it really worth it to sacrifice the remote just because plex home 
theater? Is it at this stage much better than plex media center?

RB is a great software and I don't see myself going back to keyboard

On Jan 8, 2013, at 5:48 PM, ScottF 
wrote:

 

User

09.01.2013 02:36:56

PlexHT will actually play 24p content properly without the sync issues in previous releases. 

User

09.01.2013 10:19:01

Thanks everybody for their feedback.

Those who have Plex Home Theater installed can now download and install an updated Behaviour via Remote Buddy's built-in Online Updater.

Best regards, 
Felix Schwarz 

User

09.01.2013 16:31:19

Awesome! It works great.

Thanks so much for making this available. I really appreciate it.

-Scott

User

10.01.2013 04:14:38

How can I update Remote Buddy Express, so that it will work with Plex Home Theater?

Thanks,

-Fred

Last edited: 10.01.2013 04:15:28 

User

10.01.2013 04:49:34

Remote Buddy doesn't seem to be working with Plex Home Theater for me.

I had both Plex and Plex/HT installed on my machine when I updated.

I have since deleted both programs, restarted my machine, restarted Remote Buddy and then palced Plex/HT back in the applications directory.

Remote Buddy recognizes that Plex is installed (it calls it Plex not Plex Home Theater, I'm not sure if that is significant or not). When in Plex/HT and I hit buttons on the Harmony remote nothing happens.

Any ideas?

Thanks. 

User

10.01.2013 13:07:19

 
 
I just updated, and same issue for me.

The Plex behaviour now launches Plex HT instead of Plex MC (aka Laika). 
But Plex HT doesn't register button presses while RB is running. 
I tested Plex MC too, and that seems to have the same issue (that was working before the update).

So the new behaviour seems to have broken remote functionality with both versions of Plex for me.

That being said, as soon as I close RB they both work ok.

I'm using an Apple remote.

I was also hoping that I'd be able to use RB to switch between both versions of Plex. So I'd have them both in the RB menu, and be able to selectively launch and quit out of them. 
Is it possible to use RB in this way?

Last edited: 10.01.2013 13:08:25 

User

11.01.2013 09:38:02

Thanks for asking.

1) Like with pre-Plex 0.9.5 and Plex 0.9.5+, where Plex Inc. changed the bundle identifier of Plex for the first time, Remote Buddy will only address the newer one. I've explained the reasoning for this before in this forum. If you want to use an older version of Plex, please first remove the version you don't use, relaunch Remote Buddy (so it no longer finds the newer Plex/HT on startup) and you can control your old version of Plex again.

2) Plex/HT also uses a different communications port than previous versions of Plex. The updated Behaviour takes care of this. You can, however, manually (via a text editor) configure Plex/HT to use a different port or use firewall software to block access to that port (remember: Plex/HT uses a new bundle identifier (actually two depending on the version of your copy), so your old firewall settings for Plex will not apply to it! You'll need to set these up anew.).

I'm working on having the Behaviour detect even the rare case of a manually configured, different port and handle it. What I'll not be able to detect or work around though is firewall software blocking control packets (since these are UDP, the Behaviour doesn't get any information on whether the package was delivered).

Please check your system's OS X firewall settings: does Plex/HT have permission to accept incoming connections? 
Do you use any third party firewall software like Little Snitch? 
Please also run this command in Terminal.app and copy and paste its output:

sudo lsof | grep UDP

Thanks in advance.

Best regards, 
Felix Schwarz 

User

11.01.2013 19:17:59

Hi Felix,

So far as I'm aware I've not changed the ports in Plex/HT or activated my firewall.

Here is the output you requested:

launchd 1 root 12u IPv4 0xd06cb7f667b8cee9 0t0 UDP localhost:60762 
launchd 1 root 22u IPv4 0xd06cb7f667b8cd61 0t0 UDP *:netbios-ns 
launchd 1 root 23u IPv4 0xd06cb7f667b8cbd9 0t0 UDP *:netbios-dgm 
configd 17 root 10u IPv6 0xd06cb7f667b8ca51 0t0 UDP *:* 
configd 17 root 15u IPv4 0xd06cb7f667b8c431 0t0 UDP *:* 
configd 17 root 23u IPv4 0xd06cb7f667b8b4e1 0t0 UDP *:* 
configd 17 root 25u IPv4 0xd06cb7f667b8b359 0t0 UDP *:* 
configd 17 root 27u IPv4 0xd06cb7f667b8b1d1 0t0 UDP *:* 
syslogd 19 root 11u IPv4 0xd06cb7f667b89641 0t0 UDP *:63851 
mDNSRespo 45 _mdnsresponder 8u IPv4 0xd06cb7f667b8c2a9 0t0 UDP *:mdns 
mDNSRespo 45 _mdnsresponder 9u IPv6 0xd06cb7f667b8c121 0t0 UDP *:mdns 
mDNSRespo 45 _mdnsresponder 38u IPv4 0xd06cb7f667b88d11 0t0 UDP all-systems.mcast.net:5350 
mDNSRespo 45 _mdnsresponder 39u IPv6 0xd06cb7f667b88b89 0t0 UDP *:* 
mDNSRespo 45 _mdnsresponder 48u IPv4 0xd06cb7f669832d61 0t0 UDP *:49924 
mDNSRespo 45 _mdnsresponder 49u IPv6 0xd06cb7f669832bd9 0t0 UDP *:49924 
mDNSRespo 45 _mdnsresponder 50u IPv4 0xd06cb7f669832a51 0t0 UDP *:64592 
mDNSRespo 45 _mdnsresponder 51u IPv6 0xd06cb7f6698328c9 0t0 UDP *:64592 
mDNSRespo 45 _mdnsresponder 52u IPv4 0xd06cb7f6698325b9 0t0 UDP *:62372 
mDNSRespo 45 _mdnsresponder 53u IPv6 0xd06cb7f669832431 0t0 UDP *:62372 
mDNSRespo 45 _mdnsresponder 54u IPv4 0xd06cb7f6698322a9 0t0 UDP *:60843 
mDNSRespo 45 _mdnsresponder 55u IPv6 0xd06cb7f669832121 0t0 UDP *:60843 
mDNSRespo 45 _mdnsresponder 56u IPv4 0xd06cb7f669831f99 0t0 UDP *:63693 
mDNSRespo 45 _mdnsresponder 57u IPv6 0xd06cb7f669831e11 0t0 UDP *:63693 
mDNSRespo 45 _mdnsresponder 61u IPv4 0xd06cb7f667b8c5b9 0t0 UDP *:64230 
mDNSRespo 45 _mdnsresponder 65u IPv4 0xd06cb7f66b5ecbd9 0t0 UDP *:59032 
mDNSRespo 45 _mdnsresponder 73u IPv6 0xd06cb7f667b8b669 0t0 UDP *:64230 
mDNSRespo 45 _mdnsresponder 76u IPv6 0xd06cb7f66b5ecd61 0t0 UDP *:59032 
mDNSRespo 45 _mdnsresponder 77u IPv4 0xd06cb7f669830a29 0t0 UDP *:64093 
mDNSRespo 45 _mdnsresponder 79u IPv6 0xd06cb7f6698311d1 0t0 UDP *:64093 
awacsd 61 root 334u IPv4 0xd06cb7f667b8aa29 0t0 UDP 192.168.0.3:49998->173-14-22-225-colorado.hfc.comcastbusiness.net:59342 
blued 62 root 4u IPv4 0xd06cb7f667b8c741 0t0 UDP *:* 
ntpd 66 root 20u IPv4 0xd06cb7f66982f4b9 0t0 UDP *:ntp 
ntpd 66 root 21u IPv6 0xd06cb7f66982f331 0t0 UDP *:ntp 
ntpd 66 root 22u IPv6 0xd06cb7f66982f021 0t0 UDP localhost:ntp 
ntpd 66 root 23u IPv4 0xd06cb7f66982ee99 0t0 UDP localhost:ntp 
ntpd 66 root 24u IPv6 0xd06cb7f66982ed11 0t0 UDP localhost:ntp 
ntpd 66 root 25u IPv6 0xd06cb7f66982eb89 0t0 UDP media-center-mini.local:ntp 
ntpd 66 root 26u IPv4 0xd06cb7f66982ea01 0t0 UDP 192.168.0.3:ntp 
ntpd 66 root 28u IPv6 0xd06cb7f667b89c61 0t0 UDP [fe80:8::b499:e3f1:1f28:e557]:ntp 
ntpd 66 root 29u IPv6 0xd06cb7f667b89ad9 0t0 UDP [fd1e:2895:85d6:bc7:b499:e3f1:1f28:e557]:ntp 
locationd 85 _locationd 4u IPv4 0xd06cb7f667b8bf99 0t0 UDP *:* 
kdc 87 root 5u IPv6 0xd06cb7f667b8be11 0t0 UDP *:kerberos 
kdc 87 root 7u IPv4 0xd06cb7f667b8bc89 0t0 UDP *:kerberos 
EyeConnec 104 root 10u IPv4 0xd06cb7f669830ec1 0t0 UDP 239.255.255.250:ssdp 
EyeConnec 104 root 11u IPv4 0xd06cb7f669830d39 0t0 UDP *:57542 
EyeConnec 104 root 20u IPv4 0xd06cb7f667b89951 0t0 UDP 192.168.0.3:ssdp 
netbiosd 341 _netbios 3u IPv4 0xd06cb7f667b8cbd9 0t0 UDP *:netbios-dgm 
netbiosd 341 _netbios 4u IPv4 0xd06cb7f667b8cd61 0t0 UDP *:netbios-ns 
NetworkBr 344 admin 5u IPv4 0xd06cb7f667b8bb01 0t0 UDP *:* 
Plex\x20M 348 admin 50u IPv4 0xd06cb7f669830409 0t0 UDP *:32414 
Plex\x20M 348 admin 51u IPv4 0xd06cb7f669830281 0t0 UDP *:32410 
Plex\x20M 348 admin 52u IPv4 0xd06cb7f6698300f9 0t0 UDP *:32413 
Plex\x20M 348 admin 53u IPv4 0xd06cb7f66982ff71 0t0 UDP localhost:57511 
Plex\x20M 348 admin 54u IPv4 0xd06cb7f66982fde9 0t0 UDP 192.168.0.3:60844 
Plex\x20M 348 admin 56u IPv4 0xd06cb7f66982fc61 0t0 UDP localhost:60152 
Plex\x20M 348 admin 58u IPv4 0xd06cb7f66982fad9 0t0 UDP 192.168.0.3:57462 
Rowmote 355 admin 6u IPv4 0xd06cb7f667b8c8c9 0t0 UDP *:5843 
Rowmote 355 admin 7u IPv6 0xd06cb7f667b8b979 0t0 UDP *:5843 
racoon 378 root 6u IPv6 0xd06cb7f667b894b9 0t0 UDP [fd1e:2895:85d6:bc7:b499:e3f1:1f28:e557]:isakmp 
racoon 378 root 7u IPv6 0xd06cb7f667b89331 0t0 UDP [fd1e:2895:85d6:bc7:b499:e3f1:1f28:e557]:ipsec-msft 
racoon 378 root 8u IPv6 0xd06cb7f667b891a9 0t0 UDP [fe80:8::b499:e3f1:1f28:e557]:isakmp 
racoon 378 root 9u IPv6 0xd06cb7f667b89021 0t0 UDP [fe80:8::b499:e3f1:1f28:e557]:ipsec-msft 
racoon 378 root 10u IPv4 0xd06cb7f667b88e99 0t0 UDP 192.168.0.3:isakmp 
racoon 378 root 11u IPv4 0xd06cb7f667b88259 0t0 UDP 192.168.0.3:ipsec-msft 
racoon 378 root 12u IPv6 0xd06cb7f667b880d1 0t0 UDP media-center-mini.local:isakmp 
racoon 378 root 13u IPv6 0xd06cb7f669831c89 0t0 UDP media-center-mini.local:ipsec-msft 
racoon 378 root 14u IPv6 0xd06cb7f669831b01 0t0 UDP localhost:isakmp 
racoon 378 root 15u IPv6 0xd06cb7f669831979 0t0 UDP localhost:ipsec-msft 
racoon 378 root 18u IPv4 0xd06cb7f6698317f1 0t0 UDP localhost:isakmp 
racoon 378 root 19u IPv4 0xd06cb7f669831669 0t0 UDP localhost:ipsec-msft 
racoon 378 root 20u IPv6 0xd06cb7f6698314e1 0t0 UDP localhost:isakmp 
racoon 378 root 21u IPv6 0xd06cb7f669831359 0t0 UDP localhost:ipsec-msft 
Plex\x20H 94490 admin 6u IPv4 0xd06cb7f667b89f71 0t0 UDP *:* 
Plex\x20H 94490 admin 11u IPv4 0xd06cb7f6698308a1 0t0 UDP *:32415 
Plex\x20H 94490 admin 12u IPv4 0xd06cb7f669830591 0t0 UDP localhost:54876 
Plex\x20H 94490 admin 13u IPv4 0xd06cb7f66982e879 0t0 UDP 192.168.0.3:49373 
Plex\x20H 94490 admin 14u IPv4 0xd06cb7f66982e6f1 0t0 UDP *:32412 
Plex\x20H 94490 admin 23u IPv4 0xd06cb7f66982f7c9 0t0 UDP *:9778 
PlexHelpe 94496 admin 6u IPv4 0xd06cb7f667b89f71 0t0 UDP *:* 
PlexHelpe 94496 admin 8u IPv4 0xd06cb7f667b8b049 0t0 UDP *:* 
PlexHelpe 94496 admin 11u IPv4 0xd06cb7f6698308a1 0t0 UDP *:32415 
PlexHelpe 94496 admin 12u IPv4 0xd06cb7f669830591 0t0 UDP localhost:54876 
PlexHelpe 94496 admin 13u IPv4 0xd06cb7f66982e879 0t0 UDP 192.168.0.3:49373 
PlexHelpe 94496 admin 14u IPv4 0xd06cb7f66982e6f1 0t0 UDP *:32412

User

12.01.2013 12:02:02

Thanks for the info.

The port number looks fine. Remains the firewall:

Please check your system's OS X firewall settings (System Preferences > Security > Firewall in Mountain Lion): 
Is it turned on? 
If yes, does Plex/HT have permission to accept incoming connections?

Do you use any third party firewall software like Little Snitch?

Which version of Plex/HT are you using?

Thanks in advance.

Best regards, 
Felix Schwarz 

User

12.01.2013 15:09:59

Hi Felix,

No OS X firewall or 3rd party blocker. I was able to get it going though.

Working under the assumption that something from the original Plex was getting launched and confusing the situation I turned off the StartUp for everything Plex and Remote Buddy.

After I relaunched there was still a PlexHelper running in the background. A search of the hard drive turned up copies inside the applications but also in ~/Library/Application Support/Plex and also Plex Home Theater.

I moved the Plex folder out of Application Support and re-launched. No PlexHelper at startup now.

I was then able to bring up Plex/HT and Remote Buddy looks to be working well for me.

At some point I was using Plex .8 I believe. Also in Plex I had the option turned on for "Remote Always Available" or the like so some combination of these may have contributed to the issue.

Short version: 
Move ~/Library/Application Support/Plex out of the Application Support directory 
Reboot 
Remote Buddy now controls Plex Home Theater

Thanks for the great product and prompt support! 

User

13.01.2013 08:01:09

 
Hi,

Same for me too, this has fixed it.

I'm pretty sure that I didn't have the Plex Helper App running, but renaming the App Support folder for Plex Media Centre shown above has got Remote Buddy working as normal with Plex HT.

Thanks for the help and ideas everyone.

As I mentioned in my last post, it'd be good if RB let you use both versions of Plex, especially for these preview releases. 
While I'm now exclusively using Plex HT, as I haven't had any issues with it, I know from looking through the Plex forums that other people aren't as lucky. Of course no idea if they're RB users.

Thanks again. 

User

15.01.2013 04:02:06

Any news on the issue with "Remote Buddy Express"? is there an update available?

TX

Fred 

User

15.01.2013 09:40:02

Thanks for asking.

Unfortunately, as per Apple's Review Guidelines, Remote Buddy Express is not permitted to include any Online Updater.

You can, however, download the latest version of the Behaviour in your browser and install it manually:

1) Download http://static.iospirit.com/static/objectfiles/file/135/Plex.rbbehaviour.zip 
2) Unarchive the zip file 
3) Double-click Plex.rbbehaviour and follow Remote Buddy Express' instructions

Best regards, 
Felix Schwarz 

User

15.01.2013 23:02:29

so i am missing menu button functionality within plex. i have the latest remotebuddy and PHT running. there is an option for menu button (held) in the mappings but nothing for menu for Plex. i followed all the directions in this thread but nothing has changed. I will say that all the other functionality seems to be working.

Last edited: 15.01.2013 23:04:09 

User

16.01.2013 10:54:01

Thanks for asking.

Do you mean that

a) there's no entry for the "menu" button in the left column of the mapping table? 
b) you can select "Navigation: Menu (held)" but don't see an entry "Navigation: Menu" in the right column of the mapping table?

Best regards, 
Felix Schwarz 

User

16.01.2013 14:45:43

hey felix..

yes to both questions... 

User

17.01.2013 05:06:57

hi.. i noticed that an update was available so i downloaded and installed.. i noticed that ajax remote now has the menu option mapped again.. but the apple remote still does not.. almost there! 

User

17.01.2013 10:27:01

Thanks for the info.

The action named "Navigation: Menu" should always be there for you to choose.

The "Menu" button entry is also always shown - except if you have already hardwired it to an action in the "Global Mapping" table. Please take a look. What action did you assign to the "Menu" button there?

Best regards, 
Felix Schwarz 

User

17.01.2013 16:11:36

that was totally it.. i had long ago re-mapped globally the menu to launch plex.. and when i set it back to the defaults and delete all the preference files it came back. it was working fine before.. but i'll adapt and keep the default mapping! 

User

18.01.2013 15:03:01

If you want to launch Plex when you press the menu button and you don't currently control any other application, you can assign the "Behaviours > Activate Plex Behaviour" action to the Menu Button in the "Default Mapping" table at Prefs > Mapping. That table is used as fallback when no other Behaviour could be found to fit the current scenario.

Best regards, 
Felix Schwarz 

User

23.06.2013 15:03:03

i've recently had the same issue after installing plex home theatre for plex pass members... tried the install solution above and worked perfectly... new plex works with the remote... but unhappy with the bugs in that version of plex at this stage, and reverted back to just the free plex till they're sorted... now my remote doesn't work... is there a way to bring back the old plex behavior like the above solution updated to the new plex app supported behavior? 

User

27.06.2013 11:06:01

Thanks for asking.

Remote Buddy determines the version of Plex ("old Plex" or "Plex HT") you use during launch and will stick with the result for as long as it runs for performance reasons.

So, if you up- or downgrade your Plex version, please restart Remote Buddy afterwards to give it an opportunity to detect the change and react accordingly.

You may also want to check your system for left over versions of "Plex Helper“ on your system from the respective previously installed versions as these are usually incompatible with the respective other version of Plex and - depending on your setup - will render the remote unfunctional until you clean up after the respectively previously installed version.

Hope that helps.

Best regards, 
Felix Schwarz 

User

18.09.2013 01:22:50

Hi Felix, 
So just so that I understand properly: with both Plex and Plex Home Theater on my Mac, I can't use RB to control them both right? The reason is, I use Plex for video viewing and PHT for airplaying music (which is nice because it shows visualizer/album cover/etc). It doesn't seem to be possible to toggle between both... please let me know if I'm mistaken or if there is any way to allow both at once. 
Thanks! 

User

23.09.2013 10:19:01

Thanks for asking.

Remote Buddy will control the latest generation of Plex that it finds while Remote Buddy launches.

For added clarity, here are a few scenarios:

1) If you have Plex and Plex/HT installed, it will control Plex/HT. 
2) If you have Plex installed, it will control Plex. 
3) If you have Plex installed, launch Remote Buddy and then install Plex/HT, Remote Buddy will control Plex. You need to relaunch Remote Buddy to control Plex/HT. 
4) If you have Plex/HT installed, launch Remote Buddy and then install Plex, Remote Buddy will control Plex/HT. You'd need to remove Plex and relaunch Remote Buddy to control Plex/HT.

Best regards, 
Felix Schwarz 

User

26.11.2013 12:22:04

 
 
Just wondering - why cant both be installed and managed separately as two separate applications?

best 
Jesper 

User

26.11.2013 22:26:01

There are more, but mainly for two reasons:

1) installing both Plex and Plex/HT can have many undesirable side effects like them fighting for the same resources (mostly the Apple IR Receiver/Remote). That’s not a setup I can realistically provide technical support for.

2) many Plex users have customized their mapping and would not be amused if they had to do it all over again. But that’s exactly what would happen. Giving each of Plex and Plex/HT a Behaviour of their own would also mean that they no longer share the same mapping table.

Best regards, 
Felix Schwarz