With different heights, it should run into background.resize(), but somehow doesn't go further into the dprint(). At that point, we should see an error message in the logs. Or maybe a "tarceback" - which essentially is the std. python error message - in terminal.
I have no idea, why PILBackgrounds would exit like it does... and not write anything else.
I used git clone to get the latest update from github and tried again but still get the same "trailers unavailable" error but the logfile is a bit different. I attached this latest PlexConnect logfile (High logging).
If i disable fanart i can use PlexConnect normally. Anyone who can help me with this background issue?
If you continue trying (by selecting once, twice, or even 3 times) do you eventually get what you want ? PlexConnect has a 60 seconds timeout, for slow servers this is sometimes a small value.
If you continue trying (by selecting once, twice, or even 3 times) do you eventually get what you want ? PlexConnect has a 60 seconds timeout, for slow servers this is sometimes a small value.
No, when the error "trailers unavailable" has been displayed and i return to the main screen of the aTV3 i cannot open the Trailers app. It displays the message "trailers unavailable". I waited a few minutes. When i stop the PlexConnect package and restart it i can open the Trailers app. But after going to the pleplay screen i receive the "trailers unavailable" message again.
I set the loglevel to normal. The last thing i see in the log when i receive the "trailers unavailable" message is:
Maybe the aTV is timing out before the image has finished resizing, try the changes in that PULL and see if it works.
Freescale QorIQ P1022 ppc
1.067 GHz
2 Cores
2 Threads
FPU: yes
Package Arch: qoriq
RAM: 64-bit@DDR3 1GB
Notes: Hardware Encryption Engine, Wake on LAN/WAN Support
See Baa's post above here.
I wanted to reinstall SynoCommunity Python but then i had to uninstall Auto-Sub, CouchPotato, SABnzbd, SickBeard so i waited with reinstalling Python :)
nas> cd /usr/local/python/bin
nas> python2.7
Python 2.7.9 (default, Jan 7 2015, 14:23:54)
[GCC 4.3.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from PIL import Image, ImageFilter
>>> img = Image.open("/volume1/downloads/test.jpg")
>>> img = img.resize((1000,1000), Image.ANTIALIAS)
Segmentation fault (core dumped)
Anybody aware of an exit like this?
Are there newer/fixed PIL versions out there?
So in what situation is PIL broken? For example is it only broken under certain Python versions or hardware platforms? I ask because that code works fine for me with Python 2.7.8 Win32 on an Intel machine.
Does the python try/except block not catch Segmentation faults?
And if the OP's problem is a Segmentation Fault then would it not show in the console?
So in what situation is PIL broken? For example is it only broken under certain Python versions or hardware platforms? I ask because that code works fine for me with Python 2.7.8 Win32 on an Intel machine.
Can my SynoCommunity Python package be corrupt? This Python 2.7.9 package works fine on another Synology DS214Play.
I guess the first things I would try would be using artwork that is the same resolution as the aTV and thus does not need resizing, see if that works. Then I'd try changing the resize mode from Image.ANTIALIAS to Image.NEAREST.
Only after that would I try reinstalling Pyhton/PIL.
I guess the first things I would try would be using artwork that is the same resolution as the aTV and thus does not need resizing, see if that works. Then I'd try changing the resize mode from Image.ANTIALIAS to Image.NEAREST.
Only after that would I try reinstalling Pyhton/PIL.
Okay, i can try using a background with a size of 1920x1080.
NEAREST didn't work either for me;
nas> python2.7
Python 2.7.9 (default, Jan 7 2015, 14:23:54)
[GCC 4.3.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from PIL import Image, ImageFilter
>>> img = Image.open("/volume1/downloads/test.jpg")
>>> img = img.resize((1000, 1000), Image.NEAREST)
Segmentation fault (core dumped)
Umm... not sure what to suggest. You mention the Python package works fine on a different Synology model, so I assume that model doesn't fail with a Segmentation fault? Meaning the problem is specific to only certain models.
Umm... not sure what to suggest. You mention the Python package works fine on a different Synology model, so I assume that model doesn't fail with a Segmentation fault? Meaning the problem is specific to only certain models.
Yes, i used the same package (Python / PlexConnect) on another Synology (from family). It works there. I think the cpu should be powerfull enough, maybe it's the architecture, maybe it's the package for the DS413, maybe it's just broken on my Synology and i have to reinstall.
Not exactly the same package. DS214play is Intel, DS413 is PowerPC. Therefore Python package is compiled using different libraries. The Python package installed in DS214play cannot be installed in the DS413 and vice versa. Same happens with PMS, DS214play requires the Intel version, DS413 requires the PowerPC version.
Not exactly the same package. DS214play is Intel, DS413 is PowerPC. Therefore Python package is compiled using different libraries. The Python package installed in DS214play cannot be installed in the DS413 and vice versa. Same happens with PMS, DS214play requires the Intel version, DS413 requires the PowerPC version.
Yes exactly. That is what i actually meant with "maybe it's the package for the DS413". Thank you for a better description :) Maybe anyone with a PowerPC could test this?
mderksen: The next step after resizing would be blurring the lower range, in case your settings have blurRadius!=0. You should see a log about that, though.
After that, the fanart will be pasted to the gradient... it is totally possible, that Python/PIL/your CPU will freak out the same way - throwing a segmentation fault. I mean, we know there is something awfully wrong with that python library...
pecinko: Yes, you are right - sort of. You can ask PMS to transcode the image... but it won't hit exactly the resolution given, depending on the aspect ratio, I guess. Also, since we had to do the image manipulation within PlexConnect, there is no good reason to only do only part of it, forcing your machine to encode/decode to jpeg another time.
I didn't have time to play around with the "Plex New transcoder", but it is the same as ffmpeg, thus all options from ffmpeg are available, which includes cropping, blurring and blending images. You can also include fonts and render text in the images.
Maybe someone smart could play around with it to make resizing/cropping/blending work.
If this can work, we are no longer depending on PIL.
if you do an export of LD_LIBRARY_PATH with the correct path, you can execute "Plex\ New\ Transcoder" on the commandline.
Issue with this - how to get the background/fading template to the transcoder? I am not aware of a PMS service in this direction... usually PMS delivers content, and doesn't receive it. :-)
Remember, it also needs to work with PlexConnect not on the same host as PMS...
Some users, such as me, have PMS installed in ARM computers that cannot transcode. Please do not use the transcoder in PlexConnect functions, unless there is no other option.
