Chrobrego daemon compatible code is planned :)
Cool :-)
If the "Force Direct Play" leads to a play back error it means that Plex wants to transcode it. In your case the video format is fine (H264) so that should be because of the sound that is AC-3
Try the option in Plex Web interface / Settings / Show advanced Settings: Enable Dolby Digital during AirPlay (AC3 = Dolby digital)
You will need a receiver that can handle it because Apple TV can not decode it.
I just tried following your advice, but it had no effect. I turned on the Dolby Digital inside the ATV settings too, but the error still persists: "Encountered a problem trying to read this content.... Try again later"..
Is there some way of doing a log, so I'm able to see what the actual problem might be?
In the begining I did want to fetch the PlexConnect code with git from inside the addon so basically the addon would almost not need to be updated. But that did not work. So the addon embeds the PlexConnect code, this is surely more reliable but less dynamic...
However you possibly could update the PlexConnect code used by the addon with using ssh:
cd /etc/frontview/addons/bin/PLEXCONNECT/PlexConnect env GIT_SSL_NO_VERIFY=true git pullThis being said the addon does not launch PlexConnect.py because that one does not work as daemon. So a modified version PlexConnectDaemon.py is used instead so if PlexConnect.py file is updated, a new PlexConnectDaemon.py will have to be produced, eg by a new version of the addon. I will document that change (suggested by user wilsoncd2) so that the Plex dev team maybe could incorporate this in the standard files in a way or another. If I don't update the addin, users could recreate that change too.
Setting up my PMS on the ReadyNAS takes a lot more time that i thought ;(
Any chance that your are building a "new" Add-on with the latest Commit enhancements?
I just tried following your advice, but it had no effect. I turned on the Dolby Digital inside the ATV settings too, but the error still persists: "Encountered a problem trying to read this content.... Try again later"..
Is there some way of doing a log, so I'm able to see what the actual problem might be?
Sorry I don't know. Would worth to search on the forum and maybe create a post - would be interesting to know all the options we have to avoid transcoding
Setting up my PMS on the ReadyNAS takes a lot more time that i thought ;(
Any chance that your are building a "new" Add-on with the latest Commit enhancements?
Sure, I'll do that - let me know when you are done :-)
New Plex Server up and running.
I tested your PlexConnect Add-on - and boom it works out of the Box.
BIG THANKS!
Magic, just uploaded it onto my ReadyNas and worked like a charm. Only problem I've got now is deciding whether to use plex on my Roku 3 or myATV 3 :-))
Rgds
Alex
@alex
ATV3!
@Chrobrego
I noticed one minor thing:
If i restart the PMS Plexconnect will not work until i restart your Addon too.
It would be really cool, if the Daemon would check (constantly?) if the PMS is alive.
But... not a must - your Addon is cool as it is!
Hi,
Is there any sign of development of an add-on for the os 6? I tried to put this version on my os 6 but failed miserably!!
Cheers
Hi Ho Chrobrego,
would you please build a new Addon with the latest enhancements (e.g. Clock while playing a vid)?
I really do not understand how to update to the latest commits by myself using your great Addonn :-(
Thanks
BTW: I now noticed that with the latest commit I do not need to Create the PlexConnectDaemon.py as the PlexConnect.py can be used as is in startup scripts. Once again a good step forward from the PlexConnect dev team!
BTW:
With the latest commit of PlexConnect the update procedure of the addon (without getting a new bin file) should be as simple as:
cd /etc/frontview/addons/bin/PLEXCONNECT/PlexConnect env GIT_SSL_NO_VERIFY=true git pull
It could be good if someone could feedback me whether this alternate update method works :rolleyes:
Thanks for the update Chrobrego, Awesome work and thank you..
I'm still have problems getting it to work though. The package installs but ATV3 won't connect. I tried running ./PlexConnect.py manually but get the following error:
10:33:03 PlexConnect: started: 10:33:03
10:33:03 PlexConnect: ***
10:33:03 PlexConnect: PlexConnect
10:33:03 PlexConnect: Press ENTER to shut down.
10:33:03 PlexConnect: ***
10:33:03 PlexConnect: IP_self: 192.168.0.11
10:33:03 PlexConnect: started: 10:33:03
10:33:03 DNSServer: started: 10:33:03
10:33:03 DNSServer: Failed to create socket on UDP port 53: [Errno 98] Address already in use
10:33:03 PlexConnect: DNSServer not alive. Shutting down.
I looked to see what process was running on Port 53 by running the following command "sudo netstat -anp | grep :53" and got this:
tcp 0 0 192.168.0.11:2727 192.168.0.10:53498 TIME_WAIT -
tcp 0 0 192.168.0.11:2727 192.168.0.10:53497 TIME_WAIT -
tcp 0 0 192.168.0.11:2727 192.168.0.10:53491 TIME_WAIT -
tcp 0 0 192.168.0.11:2727 192.168.0.10:53495 TIME_WAIT -
tcp 0 0 192.168.0.11:2727 192.168.0.10:53496 TIME_WAIT -
tcp 0 0 192.168.0.11:2727 192.168.0.10:53501 FIN_WAIT2 -
tcp 0 0 192.168.0.11:2727 192.168.0.10:53500 FIN_WAIT2 -
tcp 0 0 192.168.0.11:22 192.168.0.10:53274 ESTABLISHED8404/0
tcp 0 0 192.168.0.11:2727 192.168.0.10:53499 TIME_WAIT -
tcp 0 0 192.168.0.11:2727 192.168.0.10:53492 TIME_WAIT -
udp 0 0 192.168.0.11:33796 192.168.0.1:5351 ESTABLISHED3050/plexserver
udp 0 0 0.0.0.0:53 0.0.0.0:* 7741/python
udp 0 0 0.0.0.0:5353 0.0.0.0:* 2676/avahi-daemon:
udp6 0 0 :::5353 :::* 2676/avahi-daemon:
It appears that Python uses this port.?
Any ideas.?
@Rich O. , Could it be that you have other instances of PlexConnect running?
What that command outputs?
ps -ef | grep "PlexConnect" | grep -v grep
I get:
root 13787 13783 0 10:55 ? 00:00:00 python /etc/frontview/addons/bin/PLEXCONNECT/PlexConnect/PlexConnect.py
root 13867 13787 0 10:55 ? 00:00:00 python /etc/frontview/addons/bin/PLEXCONNECT/PlexConnect/PlexConnect.py
root 13868 13787 0 10:55 ? 00:00:00 python /etc/frontview/addons/bin/PLEXCONNECT/PlexConnect/PlexConnect.py
I initially ran PlexConnect through Terminal prior to trying your package, That was a while ago though.. I have rebooted my Nas since and then installed the Bin..
ok so far it looks normal. If you want to test and see the terminal output you need to stop the addon from frontview and then launch PlexConnect manually from the terminal
ok so far it looks normal. If you want to test and see the terminal output you need to stop the addon from frontview and then launch PlexConnect manually from the terminal
OK, Thank you. It appears to be running correctly in terminal but still can't get my ATV3 to connect. I'll keep trying..
Hi Rich O, there is no reason it should not work for you.
It is important that you revert any changes you may have done to run PlexConnect before the addon comes:
* The Virtual.conf file previously created in /etc/frontview/apache/addons must be deleted
* The httpd.conf in /etc/frontview/apache must be restored to the out of the box version (eg listen to port 80)
Please confirm you have done those steps.
If it still does not work please list the output you get from PlexConnect from the terminal and after you operate Plex from the Apple TV
