Alternative to actor thumbs?

F00b4r,

Thanks for showing me your agents order.  I figured that the freebase agent was the cause of the actor thumbs.  I moved it lower on my list and it now works.

Umm... Honestly I'm not sure what the problem is, all the needed information is in the xml so it should work fine.

Could you open Debuy.py in a text editor and change the debut level of XMLConverter from 1 to 2, resave the file, run PlexConnect again, navigate to the movies preplay screen and repost the terminal output.

Thanks

Hi Roidy,

Here it is as a text file. It was too big for pastebin. By the way the debug level in the Debug.py was "0" not "1". I changed it to "2" as you asked.

Just curious, has anyone else experienced the preplay screen ((ERROR:VAL)) glitch I mentioned earlier or is it just me?

Also, it occurs for every video in all my libraries.

Just curious, has anyone else experienced the preplay screen ((ERROR:VAL)) glitch I mentioned earlier or is it just me? Also, it occurs for every video in all my libraries.

Sorry, haven't forgotten about your issue, what version of Python are you using? It seems your system isn't able to access indexed xml keys.

{{VAL(Video/Role/tag)}} - works

{{VAL(Video/Role[2]/tag)}} - doesn't

Very strange.

Sorry, haven't forgotten about your issue, what version of Python are you using? It seems your system isn't able to access indexed xml keys.

{{VAL(Video/Role/tag)}} - works

{{VAL(Video/Role[2]/tag)}} - doesn't

Very strange.

I get the same output on a machine with python 2.6.1 installed.

`cc

Roidy, I am using Python 2.7.4 on snow leopard 10.6.8

I have this same problem as well. of having ((ERROR: VAL)) none of the images are showing as well.

What version of python?

What version of python?


I resolved the image issue. But I'm still seeing the exact same issue you are. im using python 2.7.5 on osx.

I know you guys are busy but I was wondering if there has been any progress on the ((ERROR:VAL)) display bug on the preplay screen. This is an issue that occurs in the most up to date versions of Baa & Roidy’s build as well as on elans.

I know you guys are busy but I was wondering if there has been any progress on the ((ERROR:VAL)) display bug on the preplay screen. This is an issue that occurs in the most up to date versions of Baa & Roidy's build as well as on elans.


Can you provide a screenshot and XML media info for a sample movie? I thought this had been fixed.

They are in this thread on page one, I believe, unless you need brand new ones.

Might be best as the code has changed, just want to make sure the same files are causing the issue.

The image of the preplay screen on page one (2001: Space Odyssey) still applies, nothing has changed there.

Here is the xml of that film from PMS and the terminal readout with Debug debut level for XML Converter set to 2.

There was also a slight error when I first clicked on the video icon. The preplay screen did not load the first time, but did the second. I assume that will show up in the terminal output but I don't think it has anything to do with the ((ERROR:VAL)) display bug which occurs all the time even when things are otherwise working as they should.

Was wondering if any progress has been made on this? It still exists with latest build. It is the only Plexconnect glitch for me.

Same problem here with the "((ERROR:VAL))" display glitches under Actors, Directors, and Producers. The actor, director, and producer fields are empty on PMS. The metadata field glitch appears if I run PlexConnect from one system, but doesn't appear if I run it from another system. Both systems have the same version of PlexConnect installed.

I see the glitches when running PlexConnect (the latest release as of June 18th) on Snow Leopard Server 10.6.8 with Python 2.6.1. Both PlexConnect and PMS are on the same computer, my Mac Mini.

plexmetadataerror2.jpg

Interestingly however, I don't see this glitch if I run the PlexConnect script from my MacBook Pro running 10.8.4 and Python 2.7.2 with the PMS still on my Mac Mini.

known, not solved... it is a python issue. 2.6 does not support access to indexed XML elements using something like elem[index].

Baa, i get the error and I am using python 2.7.4 (determined by typing python in terminal) and someone earlier noted they are using 2.7.5.

I was wondering if my Plexconnect is using a different version of python than terminal indicates (I know that 2.6 is the Snow Leopard 10.6.8 default python environment). Is there a way to check what version of python a specific app is using? Can’t seem to find this online.

http://stackoverflow.com/questions/11170827/how-tell-python-script-to-use-particular-version

Try it with both :)