2013-06-13, 13:19
Today with this latest version on my Windows 7 laptop, when playing Sigur Ros tracks its crashing again.
Although maybe its still not the correct code base you said "_use_correct_artwork starts on line 191" below from my log its line 170 !
How do we ensure I have the correct code base?
Sorry to be a pain in the arse but hoping to get to the bottom of the problem no pun intended.
EDIT: Does the same on the main Linux HTPC - If I install the current version of the add-on from the Github site and the reproduce the unicode error it says in the log: _use_correct_artwork starts on line 170 and not line 191.
Although maybe its still not the correct code base you said "_use_correct_artwork starts on line 191" below from my log its line 170 !
How do we ensure I have the correct code base?
Code:
12:05:05 T:6776 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.UnicodeEncodeError'>
Error Contents: 'ascii' codec can't encode character u'\xf3' in position 7: ordinal not in range(128)
Traceback (most recent call last):
File "C:\Users\Stuart\AppData\Roaming\XBMC\addons\script.artistslideshow-master\default.py", line 782, in <module>
slideshow = Main()
File "C:\Users\Stuart\AppData\Roaming\XBMC\addons\script.artistslideshow-master\default.py", line 133, in __init__
self._use_correct_artwork()
File "C:\Users\Stuart\AppData\Roaming\XBMC\addons\script.artistslideshow-master\default.py", line 170, in _use_correct_artwork
log('current artist is %s' % artist.decode("utf-8"))
File "C:\Program Files (x86)\XBMC\system\python\Lib\encodings\utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xf3' in position 7: ordinal not in range(128)
-->End of Python script error report<--
12:05:05 T:7644 DEBUG: ------ Window Init (DialogKaiToast.xml) ------
12:05:05 T:6776 INFO: Python script stopped
Sorry to be a pain in the arse but hoping to get to the bottom of the problem no pun intended.
EDIT: Does the same on the main Linux HTPC - If I install the current version of the add-on from the Github site and the reproduce the unicode error it says in the log: _use_correct_artwork starts on line 170 and not line 191.