Plexify | OS X Application

I would first like to say thank you for the Plexify app.  It is wonderful to use and I look forward to its future.  

I have a situation I would like to ask about.  I use No Sleep with Mavericks so I can close the lid on my MBP and use Plexify/PlexConnect with my AppleTV 3.  That works nice. However, when I decide to not use No Sleep and close the lid (thus putting the notebook to sleep) Plexify no longer works which is expected and which is why I use No Sleep.  But, the thing is... if I reopen the lid, Plexify/PlexConnect no longer works (My movies/shows wont load) and a reboot is required in order for it to function once again.  Does anyone know what the cause is for this?  Any help would be appreciated if this is something I can resolve.

I have a strange issue when using PlexConnect (the iBaa script) and Plexify. Episodes are periodically being shown as "unwatched" even when they have been watched. Not with all shows though. And periodically when pressing play on the Apple Remote (the silver centre button on the remote) I get three choices on screen "Mark as watched", "Mark as unwatched" and "Change poster/picture?". Then I have to exit using the Menu button and use the Play/Pause button to watch. Can anyone explain?

I have a strange issue when using PlexConnect (the iBaa script) and Plexify. Episodes are periodically being shown as "unwatched" even when they have been watched. Not with all shows though. And periodically when pressing play on the Apple Remote (the silver centre button on the remote) I get three choices on screen "Mark as watched", "Mark as unwatched" and "Change poster/picture?". Then I have to exit using the Menu button and use the Play/Pause button to watch. Can anyone explain?

You may want to try updating the PlexConnect folder to the latest code for the first one.

The options you get are when you hold down on the select button and is by design, if you do not want these options then do not keep holding down on the select button when pressing it ;)

Aaaah! Hadn't thought that it was holding it down to get the selection. I do keep up to date with the latest build, though. I need these options when episodes I've watched don't update properly and keep having to fix at the server end.

Thanks for the tip!

Plexify 1.1 RC


The response to our first public beta has been great (well, mostly). The beta version has been downloaded more than 2500 times. So we decided to not stop development and just do what we were doing all this time - make Plexify better. Todays update contains a lot of bug fixes and new features you'll like. We fixed all known bugs and brought back the restart feature along with the new "force shutdown" feature... Still not excited?!
 



Main_ui.png

What's New in 1.1 RC?

  • Auto-start is fixed
  • Uptime feature is fixed
  • Advanced settings is fixed
  • New Welcome & Installation window
  • New Advanced installation method
  • Autoupdate from GitHub
  • Ability to choose your own certificates
  • Fixed Apple TV certificate installation bug (welcome window) 
  • Added Help tab
  • Restart functionality is back (Just click stop button while holding ALT/Option key)
  • Fixed bug with PlexConnect.log permission
  • Added "Force Shutdown" functionality (click start/stop button while holding Control key)
  • Faster way to detect local IP
  • Now we're cloning GitHub repository instead of just downloading, even without git being installed on your computer
  • Added ability to choose versions (branches) on installation
  • Embeded PlexConnect Wiki (Partly)
  • Better integration with PlexConnect
  • Improved stability and performance

What's New in 1.1 Beta?

 

  • New User Interface
  • Keyboard shortcuts (quit, preferences)
  • New Preferences Window
  • Welcome guide to help you configure Apple TV certificate
  • New Icon ( Application and Menubar )
  • Certificate generation
  • Download and Install PlexConnect from Github
  • Password will be asked only once!
  • Changed the way to launch and terminate PlexConnect 
  • Shows your local IP address

What's next?
Here's what we're planning for the next release of Plexify (Coming Soon)

  • Scheduled startup and shutdown
  • 10.6 Support
  • More global keyboard shortcuts
  • Localizations
  • Detection of common errors
  • Notifications for 10.8+
  • Simple way to change settings.cfg from Plexify
  • Ability to use your computer as a refrigerator for beer . . .

 

System Requirements

10.7+   |  Tested on: 10.9, 10.8.5,  10.8.4, 10.8.3, 10.8.2, 10.8, 10.7, 10.7.5, 10.7.3,10.7.1

 

Contacts

Requests: vahagn.mkrtchyan@mit.edu
Developers: vahagn.mkrtchyan@me.com (iMessage, please use only if you're a developer)

 

How to Give a Feedback?

Check whether the bug was already reported or not. If not, just write a simple post describing the problem you have. Please, describe how to reproduce it and specify your OS version, also attach the log file.

 

 

Download 1.1 Release Candidate | 2.7 MB
 

download.png

_____________________________________________________________________

 

We're accepting donations, check Settings ❯ Donate for more details.
I'm planning to buy an Apple TV, so that I can make Plexify even better.


btn_donate_LG.gif

Purely Amazing Work.  +1 to you and your efforts.  Thank You!

There we go guys, all is not lost. Many thanks to Cyberon for sticking with it - donation on the way.

Delighted with it. Well done Cyberon and thanks!

Just one question. I'm presuming the Autoupdate from Github will only happen on relaunch of the app. Is that correct?

The app works as advertised for the trailers.app as a local solution, glad you stuck with it and got it done! I can confirm it works with my fastuser app as well to make my mac login and start your app automatically and lock itself without any user input @ boot whatsoever. Im still waiting and hoping you can implement the fast user app into your plexify app. This is what my mac looks like @boot using your app and fastuser with plexconnect working via the trailers app on the atv all without touching anything. :slight_smile: I see you are implementing a cert installation into the app, I still had to copy my old cert over since I use the same trailers.pem on all my mac’s and atv’s which I assumed I would have to anyways, no big deal.





On a side note im trying to get your app to work with a different method via a bag.plist pointed at my dyndns plexconnect app on my atv2 using @duschetz addsite method mixed with my plexconnect on the go method that works with my launchctl method and fastuser to start plexconnect and connect it anywhere in the world on my atv2’s. When I try your app to launch the modifed plexconnect within your plexify folder it freezes your app and I have to kill it via activity montior, after that when I restart your app it launches fine and loads the modified plexconnect. The only files I change are plexconnect.py (hostofplexconnect to mydyndns), webserver.py (using @dschuetz code from post #37 here: https://forums.plexapp.com/index.php/topic/81972-installing-a-new-app-on-appletv-without-hijacking-trailers/page-2 & settings.cfg (listed below), and all the files within /assets/js (change http://atv.plexconnect to http://mydyndns). I put addsite.mc and my bag.plist in the /assets folder and plexconnect.png in the /plexify folder. Obviously this is way outside the realm of most users but would be nice to get plexconnect working anywhere you bring your atv if you get a chance or know what may be causing it to not work using these mixed methods it would be great. The pic below is the plexconnect app I generated using add site. Till you can get it to go I will be using my launchctl method for the plexconnect on the go solution. Again keep up the great work! Im just picky I like having all apps operational, I don’t like hijacking any apps on the atv2 and using it anywhere I please pointing my atv2 to my dyndns at home and just bringing my atv with me :stuck_out_tongue:


[PlexConnect]

enable_webserver_ssl = False

logpath = .

enable_dnsserver = False

prevent_atv_update = True

port_dnsserver = 53

enable_plexconnect_autodetect = True

port_pms = 32400

port_webserver = 80

ip_plexconnect = 0.0.0.0

certfile = ./assets/certificates/trailers.pem

ip_dnsmaster = 8.8.8.8

loglevel = Normal

ip_pms = dyndns (no http prefix)

enable_plexgdm = False

port_ssl = 443





Another thing I noticed with your app is that when I type sudo su, it goes right in without asking me for a password. This seems like a MAJOR security risk that would give anyone root privleges on anyones mac. I assume and hope this is a work in progress and that this will be fixed.

Obviously this is way outside the realm of most users but would be nice to get plexconnect working anywhere you bring your atv if you get a chance or know what may be causing it to not work using these mixed methods it would be great. 

Seriously?  Probably better handled with a DM or one of the other many contact methods @cyberon provided rather than mucking up the main thread with such a massive corner case - before we have a stable "production" release.

@Cyberon & @nem4ara - great work guys!  Tried to donate via the paypal link but it said the account wasn't set up to receive funds yet.  Happy to contribute so I'll keep trying.

I noticed a couple things for your "to do" list prior to the stable release:

1) I chose the advanced install (because I like to live dangerously! ;) ) and while running through the script it appeared to show an area upon which I could drag/drop my existing trailers.pem, but it auto-advanced past it and didn't give me a chance to do anything.  I did drag/drop in manually so no issues in the long run.

2) in the Advanced settings "Danger Zone" there is a "REMOTE SETTINGS" button - should that be "REMOVE SETTINGS" or "DELETE SETTINGS"?  I was expecting some sort of remote access options but the popup says

"Are you sure? 

 

Settings.cfg will be deleted and a new default one will be automatically generated"

 

Which is a perfectly valid function, I just think it's a typo with "REMOTE" rather than "REMOVE" or "DELETE" or "RESTORE"

@ricardoP obviously it was off topic. They asked for testers, I am testing and giving feedback on the app SERIOUSLY. There is always someone lol. Why dont you give feedback and I will give mine, other then that please mind your own concerns, thanks. Just because you just use the trailers app ONLY doesnt mean everyone does.

Apparently you didnt READ his post:

How to Give a Feedback?
Check whether the bug was already reported or not. If not, just write a simple post describing the problem you have. Please, describe how to reproduce it and specify your OS version, also attach the log file.

Everyone should assume this app is a work in progress and nothing is final hense the BETA version in his releases.

Good job guys! 

One simple pointer that I figured could be changed: in the beginning of the install the buttons seems to be to light grey, and they would appear better if they're dark grey like in the advanced section.

Thanks again, Alex

Great work guys !!

But in my case, I have a small problem, at boot, Plexify launch but doesn't autostart. I checked if the settings where corrects, and they are. I'm running on OSX 10.9 and Plex Media Server is running on the same computer. If I quit Plexify and relaunch it, the autostart function does work. Any help ?

@Arnaud.c Check your library/launchdaemons and make sure you diabled and removed any autostarting plists for plexconnect as well as login items for applescipt generated plexconnect apps. The only app you should have is plexify in login items. I had to copy my old trailers.pem over to the new plexify generated plexconnect to get it to all work nothing else should be modified within his generated plexconnect folder. I checked all three of the auto start options in the plexify app. This app still leaves your machine unsecure since it allows you to type in sudo su without a password in terminal since its still a beta app which I assume is because it still is a work in progress. I will be still using launchctl to run plexconnect until this is fixed but still is great to see progress on this beta app for now. I am running mavericks and it is autostarting fine with the dns hijacked trailers app on the atv.

@HKMacs until that is implemented in plexify you can remove all the files in ~/library/application support/plexify (by using finder/go/goto folder). Quit and relaunch plexify and it will rerun the installer generating the newest version of plexconnect. If need be drop in your trailers.pem in ~/library/application support/plexify/assets/certificates/ and done if you need your old certs otherwise ignore the old trailers.pem transfer.

@wahlman.j, I just checked my library/launchdaemons folder and I just have 3 plists for LogMeIn and 2 for my VPN, I don't have any PlexConnect items and not even a Plexify one (maybe this my problem), I don't know how to put a Plexify plist again.

Plexify 1.1 RC

AWESOME!

Please paste the new 1.1 RC to the main post so you'll get more downloads :)

Suggest for awesome feature in the future:

Choosing the app that PlexConnect/Plexify will Hijack. every time Plexify downloading an update from Github it'll edit all the trailers.apple.com lines like people who wants to change the app PlexConnect hijack. It'll edit to the chosen app (For example if iMovie theater is chosen to hijack it'll edit the lines matchly) so we won't have to do this manually and everyone will be able to hijack the app that he, presonally, prefer! It can be awesome!!!! :)

@Arnaud.c just add plexify to your login items with your settings app using this post as an example under this section (how to autostart plexconnect and enable fastuser)

https://forums.plexapp.com/index.php/topic/84307-launchctl-and-applescript-methods-for-plexconnect-on-mavericks-osx/

You dont need a plexify plist in your /library/launchdaemons, that is the whole point of this app.

@tomer1749 Please dont quote a huge post like that! Edit your post please and remove that quote from @cyberon!

A bug, (i think) i found. If it isn't a bug please make this as a feature or option:

When opening Plexify status window (like in the photo of 1.1 RC announcement you have to click the plexify bar icon to close it, you can't click other place in the screen, to close it.

Thanks so much for your hard work :)

@Arnaud.c just add plexify to your login items with your settings app using this post under how to autostart plexconnect and enable fastuser: https://forums.plexapp.com/index.php/topic/84307-launchctl-and-applescript-methods-for-plexconnect-on-mavericks-osx/ You dont need a plexify plist in your /library/launchdaemons, that is the whole point of this app.

@tomer1749 Please dont quote a huge post like that! Edit your post please and remove that quote from @cyberon!

Ok, ok

@wahlman.j, sorry, but I don't really understand your answer. On my Mac, at boot, Plexify auto-launch but it doesn't auto-start the PlexConnect process.

If you are allowing plexify to run on its own to generate plexconnect and adding it to login items in the settings app it should work fine, at least it did for me. If not something is not correct and you will need to figure out what is causing that. I would recommend to try to launch this in terminal and see what happens if it works maybe it is something else you will need to troubleshoot further:

cd ~/library/application support/plexify

sudo ./plexconnect.py