PlexConnect/ATV2: everything works, only Movie section won't play movies!?

Hi,

 

I am having a weird problem with my ATV2 (latest iOS) and Plexconnect (latest on QNap NAS TS-239proII).

 

Everything works as advertised, i.e. e.g. the TV shows section / library plays episodes and all other 6-7 sections work well, but the movies section won't play movies but "trailers not available" appears...

 

Does anybody has a idea where that problem comes from? It seems Plexconnect doesn'tredirect these requests properly!?

 

Any help would be highly appreciated!

Simliar to that? https://forums.plex.tv/topic/125047-plexconnect-times-out-when-trying-to-view-movie-sections/

Logs?

Medi info on a problem file would also help e.g. it may be that your tV is in MP4 format but films are in mkv, in which case you may run into issues on some NAS' that cannot direct stream or transcode.

I will follow up in that thread.

@f00b4r: no, it's not a bad file issue. Everything worked before (incl. the files I tried).

I will follow up in that thread.

@f00b4r: no, it's not a bad file issue. Everything worked before (incl. the files I tried).

Lets keep it here, as i mentioned in that thread it may be an entirely different issue and you will just cause confusion. Also read the sticky for the info we need to help you. 

OK.

I ran a few more tests with an old outdated version of plexconnect through my laptop: this version shows the movie info screen for ALL movies and plays most (I guess there is a 'bad' file issue).

With the latest version of plexconnect, I get only "trailers not available. try again later." and not even the movie info screen.

Here is the log:

19:33:55 PlexConnect: started: 19:33:55
19:33:55 PlexConnect: Version: 0.4-dev
19:33:55 PlexConnect: Python: 2.7 (r27:82500, Aug 21 2010, 07:52:47)
[GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)]
19:33:55 PlexConnect: Host OS: linux2
19:33:55 PlexConnect: IP_self: 192.168.2.30
19:33:55 DNSServer: started: 19:33:55
19:33:55 DNSServer: ***
19:33:55 DNSServer: DNSServer: Serving DNS on 192.168.2.30 port 53.
19:33:55 DNSServer: ***
19:33:55 WebServer: started: 19:33:55
19:33:55 WebServer: ***
19:33:55 WebServer: WebServer: Serving HTTP on 192.168.2.30 port 80.
19:33:55 WebServer: ***
19:33:55 WebServer: started: 19:33:55
19:33:55 WebServer: ***
19:33:55 WebServer: WebServer: Serving HTTPS on 192.168.2.30 port 443.
19:33:55 WebServer: ***
19:34:41 PlexAPI: ***
19:34:41 PlexAPI: looking up Plex Media Server
19:34:41 PlexAPI: ***
19:34:42 PlexAPI: GDM: Servers discovered: 2
19:34:45 PlexAPI: Servers (local+MyPlex): 3
19:35:00 XMLConverter: Background (Source): http://192.168.2.30:32400/library/metadata/22575/art/1415639266
19:35:00 XMLConverter: XML_ExpandLine - Error in {{BACKGROUNDURL(Video/art:)}}
Traceback (most recent call last):
  File "/share/MD0_DATA/.plexconnect/XMLConverter.py", line 712, in XML_ExpandLine
    res = getattr(CommandCollection, 'ATTRIB_'+cmd)(src, srcXML, param)
  File "/share/MD0_DATA/.plexconnect/XMLConverter.py", line 1433, in ATTRIB_BACKGROUNDURL
    res = res + PILBackgrounds.generate(self.PMS_uuid, key, auth_token, self.options['aTVScreenResolution'])
  File "/share/MD0_DATA/.plexconnect/PILBackgrounds.py", line 80, in generate
    background = background.resize((width, height), Image.ANTIALIAS)
  File "/share/MD0_DATA/.qpkg/Python/lib/python2.7/site-packages/PIL/Image.py", line 1290, in resize
    self.load()
  File "/share/MD0_DATA/.qpkg/Python/lib/python2.7/site-packages/PIL/ImageFile.py", line 189, in load
    d = Image._getdecoder(self.mode, d, a, self.decoderconfig)
  File "/share/MD0_DATA/.qpkg/Python/lib/python2.7/site-packages/PIL/Image.py", line 385, in _getdecoder
    raise IOError("decoder %s not available" % decoder_name)
IOError: decoder jpeg not available
 

--> looks like a problem preparing the background (pictures) ?

>>IOError: decoder jpeg not available

Yep, you somehow need to install jpeg support. It should be part of pil/pillow, but you never know. :-)

>>IOError: decoder jpeg not available

Yep, you somehow need to install jpeg support. It should be part of pil/pillow, but you never know. :-)

I followed the instructions for Linux to install PIL/Pillow in the fanart sticky thread and it seemed to have worked (plexconnect with new fanart worked, too, incl. movies section).

I'm running the PIL install again and run into this problem:

[/share/MD0_DATA/.plexconnect/PIL-1.1.7] # python setup.py build
running build
running build_py
running build_ext
--------------------------------------------------------------------
PIL 1.1.7 SETUP SUMMARY
--------------------------------------------------------------------
version       1.1.7
platform      linux2 2.7 (r27:82500, Aug 21 2010, 07:52:47)
              [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)]
--------------------------------------------------------------------
*** TKINTER support not available
*** JPEG support not available
*** ZLIB (PNG/ZIP) support not available
*** FREETYPE2 support not available
*** LITTLECMS support not available
--------------------------------------------------------------------
To add a missing option, make sure you have the required
library, and set the corresponding ROOT variable in the
setup.py script.

To check the build, run the selftest.py script.
running build_scripts

I'm not very familiar with linux: how can I check / download the required libraries and know the root dir? I guess the QNAP device does have a different folder structure than Debian, etc.

I'm still trying to properly (re)install PIL on the Qnap (any tips are highly welcome!) and work my way through forums but one thing bothers me: why did it work before, without JPEG, etc support?

sudo apt-get install python-imaging

Worked for me on Ubuntu server 14.04. 

Anyone had any luck getting PIL to work on the QNAP? starting to move my server over to my new NAS and thats almost the last thing to tick off…

Unless its in here I’m not sure how to install PIL on QNAP:

https://forums.plex.tv/discussion/123222/official-plexconnect-fanart-views

If you find a way in there or elsewhere please let us know so @roidy can update the OP.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.