Changelog:
http://forums.plexapp.com/index.php/topic/70611-plexconnect-changelog/
You can subscribe to the topic so you know when changes are made, be aware that it is bleeding edge so sometimes may results in bugs.
Changelog:
http://forums.plexapp.com/index.php/topic/70611-plexconnect-changelog/
You can subscribe to the topic so you know when changes are made, be aware that it is bleeding edge so sometimes may results in bugs.
I really can't tell from reading that what the options are that reflect the PlexConnect loosing it's link to my Apple TV?
Yes they are just commit comments.
I will add a note to the particular commit, just bear in mind you are working with fast moving beta software.
Once we release 0.1 you may want to stick with the point releases if you want a more detailed changelog.
It should, according to reports in this thread, have a workaround if you update to the latest code
GeoffKennedy: most likely commit d2f63db147 - DNSServer: catch socket.error
GeoffKennedy: most likely commit d2f63db147 - DNSServer: catch socket.error
Thank you so very much for directly pointing this out to me. I am sorry to ask, but I don't know what this is...?
GeoffKennedy:
You asked the following:
DarRoe, on 20 Jun 2013 - 19:33, said:
With the latest update it's solved for me. I still get the error but the ATV reconnects automatically and i don't have to restart plexconnect.
So many thnx.
>> Can I ask what latest update you are referring to?
I answered: The latest update he was referring to was "DNSServer: catch socket.error" - see github for details and source code.
GeoffKennedy:
You asked the following:
DarRoe, on 20 Jun 2013 - 19:33, said:
>> Can I ask what latest update you are referring to?
I answered: The latest update he was referring to was "DNSServer: catch socket.error" - see github for details and source code.
I can imagine you loathing this question, but I don't know how to execute the changes in:
https://github.com/iBaa/PlexConnect/commit/d2f63db147a3b8f8107ba709422240414ec23ad2
Is there any info you can give me?
Geoff: you don't have to execute any changes - I thought you were looking for more details on those changes.
If you want exactly those changes (and nothing newer), follow the given link to github, find and press the "browse code" button, then "clone to..." or "download zip" to get the code.
To get the latest and greatest (aehm... and potentially broken, too) just download the latest sources, using the link in my signature.
So I'm not sure if this makes me look like a dunce, or if this is helpful insight, but today I started using the PlexConnect.pyc file to launch PlexConnect and it isn't periodically dropping the connection. Before I would launch PlexConnect.py
Two comments:
.pyc is a pre-compiled version of .py.
-> being technically the same, it shouldn't make any difference.
.pyc files are generated when importing a module into python...
-> there shouldn't be a PlexConnect.pyc as the main source won't be imported.
Two comments:
.pyc is a pre-compiled version of .py.
-> being technically the same, it shouldn't make any difference.
.pyc files are generated when importing a module into python...
-> there shouldn't be a PlexConnect.pyc as the main source won't be imported.
Maybe the often-and-random disconnection of PlexConnect to the ATV was solved not by using the PlexConnect.pyc file or (more likely) I'm using a more up to date version number, but either way you made my wife happy because now PlexConnect is always on. Thanks!
Hi, I hope it's ok to use this topic, since my issue is the same as the one being discussed here and I thought it might be better to keep all the discussion at the same post.
I'm having the same issue as the others who reported here. But I couldn't solve it.
I'm using ATV3, with the current firmware.
I'm running Version: 0.3.1+
Should I try new commits? If so, how do I do it?
Thanks guys!
Hi, me again. Sorry for the double posting, but I'm a bit desperate
I'm not sure whether this topic is done due to the "solved" ticket on it. Should I open a new one?
Hi, me again. Sorry for the double posting, but I'm a bit desperate
I'm not sure whether this topic is done due to the "solved" ticket on it. Should I open a new one?
If you read the "Read Before Posting" pinned thread, it advises you to always start a new Thread as well as what information to Include when posting an Issue.
Therefore I suggest you post a New Thread with all the Information in the Troubleshooting Template so that people are able to help you.
