Plexconnect not working with Plex Server version 1.9.4

Awesome!

Will test tommorow, but I dont expect any issues :slight_smile:

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:

  1. Navigate to the PlexConnect folder
  2. Give line command 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:

  1. Navigate to the PlexConnect folder
  2. 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:

  1. I do not have the intention to develop PlexConnect beyond what exists today. I do not have enough programming skills for that
  2. 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
  3. Having said so, I would love to have PlexConnect converted to become a PMS plugin (installed via WebTools)

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. :blush:

@moody_blue said:
@pecinko Thinking again about what you said, I would like to say a few words:

  1. I do not have the intention to develop PlexConnect beyond what exists today. I do not have enough programming skills for that
  2. 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
  3. 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. The iOS profile 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.xml file).

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:

  1. Stop PlexConnect
  2. Delete ATVSettings.cfg
  3. Start PlexConnect
  4. Review settings and change if needed (Fanart, for example)

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).