Awesome!
Will test tommorow, but I dont expect any issues 
Thx guys!
Awesome!
Will test tommorow, but I dont expect any issues 
Thx guys!
Worked like a charm! Thanks guys! Working on 1.9.5
I have a problem. If update plexconnect over Openplex i can not start plexconnect. The traffic light remains red. Downgrade to the last plexconnect version starts plexconnect again.
@Cleaner_2000 I do not support OpenPlex (@âwahlman.jâ does), letâs wait for his answer.
Edit: But you can try the git clone method:
git clone https://github.com/iBaa/PlexConnect
Can also confirm this is working again⊠(Latest Plexconnect on Windows 10, Plex Server 1.9.4.4325 on Windows 2012 R2 and three (3) ATV3s.
Thanks guys!
@moody_blue said:
@Cleaner_2000 I do not support OpenPlex (@âwahlman.jâ does), letâs wait for his answer.Edit: But you can try the git clone method:
- Navigate to the PlexConnect folder
- Give line command
git clone https://github.com/iBaa/PlexConnect
@moody_blue thank you for your efforts, but that doesnât work for me. I have too much error messages.
@moody_blue said:
Frankly I would prefer to convince Plex to allow us to have our own profile so that we are less âvulnerableâ to changes in the iOS.xml profile.
Just a side note - why do you need profile at all? PlexConnect is targeting two specific devices thus it would suffice to have profile logic in app itself and have more robust playback control.
Profiles are recommended whenever requests are sent to PMS. Otherwise PMS will use the generic profile, which will DirectPlay everything.
I spoke with Plex development and their suggestion was to use âprofile augmentationâ. This is what has been implemented now in PlexConnect using iOS profile as its base. I could have picked an âempty profileâ such as generic.xml but this requires a more complex âprofile augmentationâ.
What do you mean with âmore robust playback controlâ ? Today PlexConnect analyses the codecs to decide âshould I use DirectPlayâ, I know itâs not perfect. Plex is removing such capability on their own clients, and relying on PMS to take the correct decision, using profiles and âprofile augmentationâ (basically to pass client settings to PMS to influence the transcode decision process), which is the technique that PlexConnect is now using.
Hi, does this method also work on Synology NASses? I now use 0.5-18 from bwynants. Not sure what will happen if I try to use the git pull commandâŠ
Could use a few pointers.
@ericborst69 If you reinstall 0.5-18 from bwynants over your existing install it will get the latest PlexConnect version from iBaaâs master and preserve all your settings.
@pecinko Thinking again about what you said, I would like to say a few words:
Thanks, Moody. However, after manually installing the package again over the existing version, the plexconnect version in the log is still 0.5-dev-210316.
Ah, forget it. my bad, I should have read the first post with a bit more attention. 
@moody_blue said:
@pecinko Thinking again about what you said, I would like to say a few words:
- I do not have the intention to develop PlexConnect beyond what exists today. I do not have enough programming skills for that
- If someone else wants to take that task I will support him. The problem I see is that the original team had a âlegionâ of testers, and I donât know if we can count on this today
- Having said so, I would love to have PlexConnect converted to become a PMS plugin (installed via WebTools)
i second it. Would love to support someoneâs effort to take plexconnect to either a plugin OR possibly a full atv4 app. Either way, would also be glad to help test.
@moody_blue said:
Found the problem. TheiOSprofile always had this line<Setting name="HlsExtraMultiChannelAudioStream" value="ac3" />but PMS was ignoring it. It means that AC3 can be streamed to iOS devices (including ATV3).So the best temporary solution would be to remove that line from the iOS profile (
iOS.xmlfile).
Updated to Version 1.9.4.4325 and found all my mkv files would not play via plexconnect and the ATV3âs. Would play fine on other plex media players
Implemented the above fix and now they are working again.
I continue to have this problem after upgrading PlexConnect. Iâm running Plex 1.9.6.
EDIT - I should also add that in PlexConnect Settings under Dolby Digital i see âERROR:SETTINGâ. Not sure this is related, but was reviewing settings in case I maybe missed something, and noticed this.
@PrairieSailor Maybe ATVSettings.cfg file is corrupt. You can rebuild it with the following procedure:
ATVSettings.cfg
Not sure if this is related but thought I would share anyway.
My ATV3âs would lose AC3 also. To fix, I edit PlexAPI.py line 478 and 479 from iOS to tvOS. I also remove eac3 from everywhere in tvOS.xml file and leave only ac3 (my AV receiver supports it, but not some of my TVâs).
All of my ATVâ3 play AC3 perfectly, and all iPhones play audio fine too.
@hutchpuppy The last version of PlexConnect works Ok, no need to modify PlexAPI.py, no need to modify the tvOS.xml profile (which is needed for ATV4âs, in case you plan to have any).
Thanks for the info, i had the same problem and i had to remove that line from the iOS profile (iOS.xml file).