Webradio irritation

Henners · 2004-10-20, 21:24

when navigating around webradio i always get a "could not parse node" error dialog even though everything appears to work ok.

presumably there is some badly formatted xml somewhere but have got no idea where to look!

not a serious problem but one that does irritate me

and would like to get rid of so if anyone could help would appreciate it.

**pike** · 2004-10-20, 22:15

an excellent example of what belongs in "python general discussion"

moving

Henners · 2004-10-21, 00:19

whoops - my bad

ok spent the last hour trying to track this down which was an interesting introduction into python

but using good old fashioned debugging techniques managed to find the culprit is related to loading the shoutcast3.gif image - more specifically where an image.open is carried out in getwidth (and presumably getheight) method. i suspect this is a pathing issue however for now i'm just going to wrap the image loading block of processelement in a try catch block.

Striker · 2004-10-21, 00:59

already answered in the kmlbrowser thread by zilvershadow

Quote:

it's a node that does not exist in the nodeslist. it can be solved by adding the node to the nodeslist.
these nodes are the fillrect, drawrect, drawline controls which do not 'yet' exist in xbmc-python and the kmlbrowser. so if someone is willing to develop that finally the browser will be complete.

i dont fully understand it though.......

Henners · 2004-10-21, 02:56

thanks for the response striker - that didn't really make sense to me either so i looked into this a bit further.

after a while of messing with the image and gif plugin i eventually found that the shoutcast3.gif was simply a png file that had been renamed as a gif - i renamed it to png and converted to gif and everything works fine now

am i the only one thats experienced this problem?

Striker · 2004-10-21, 13:36

haha weird, but it actually worked yes :kickass:

for others who would like to fix.
download the next file, rightclick, save target as and replace the old one:

shoutcast3.gif

**C-Quel** · 2004-10-21, 16:38

i just opened it in mpaint and saved over it without modifying and it solved it for me

ChEeSyBoOfS · 2004-10-21, 21:27

@henners, well done dude! :saint:

daghostmon · 2004-10-22, 06:48

i don't get it. 1.0 worked fine in fact it even hooked up to the streams faster. as soon as i downloaded 1.1 thru avalaunch i have the "could not parse node" problem and slower connect times. seems lf this is a final version this needs to be addressed. i went back to 1.0 for now.

Henners · 2004-10-22, 10:49

cheers for the praise - always nice to be appreciated :d

daghostmon - just download and replace your shoutcast3.gif image with the one striker has kindly posted above (would have done this myself but generally my web server is only up for testing purposes) and this will fix the "could not parse node issue".

as for the speed issue i can't say that i've noticed this although the fix does make it seem more responsive - probably due to the 1 second delay that was being used to display the error dialog. i don't know much about python (yet!) so not sure what the threading model is but i'm pretty sure this dialog is blocking execution while it is displayed.

2004-10-20, 22:15	#2
pike Project Manager Join Date: Sep 2003 Location: Sweden Posts: 4,281	an excellent example of what belongs in "python general discussion" moving __________________ Always read the XBMC online-manual, FAQ and search the forums before posting. Do NOT e-mail Team-XBMC members asking for support. Read/follow the forum rules. For troubleshooting and bug reporting, make sure you read this first.

2004-10-21, 16:38	#7
C-Quel Team-XBMC Scraper Specialist Join Date: Aug 2004 Posts: 1,338	i just opened it in mpaint and saved over it without modifying and it solved it for me __________________ Always read the XBMC online-manual, FAQ and search the forum before posting. Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules. For troubleshooting and bug reporting please make sure you read this first. If scraper related please always grab the latest XML relevant to the content you are trying to grab info for from this link https://xbmc.svn.sourceforge.net/svn...ystem/scrapers System Specs: A Computer with loads of shiny things that make a noise and bring life to my tv, and xbmc ofc

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Webradio 3	Hinksy	Plugin/Script (Python) Help and Support	1	2005-04-28 17:50
Webradio	Spike.M	XBMC for Xbox Specific Support	1	2005-01-06 03:20
Webradio	sjorske	XBMC for Xbox Specific Support	2	2004-12-08 12:13
Webradio	thathrillest	XBMC for Xbox Specific Support	0	2004-12-05 11:47
Webradio irritation	Henners	XBMC for Xbox Specific Support	1	2004-10-20 22:15

2004-10-20, 21:24	#1
Henners Junior Member Join Date: Oct 2004 Posts: 9	when navigating around webradio i always get a "could not parse node" error dialog even though everything appears to work ok. presumably there is some badly formatted xml somewhere but have got no idea where to look! not a serious problem but one that does irritate me and would like to get rid of so if anyone could help would appreciate it.

2004-10-21, 00:19	#3
Henners Junior Member Join Date: Oct 2004 Posts: 9	whoops - my bad ok spent the last hour trying to track this down which was an interesting introduction into python but using good old fashioned debugging techniques managed to find the culprit is related to loading the shoutcast3.gif image - more specifically where an image.open is carried out in getwidth (and presumably getheight) method. i suspect this is a pathing issue however for now i'm just going to wrap the image loading block of processelement in a try catch block.

2004-10-21, 02:56	#5
Henners Junior Member Join Date: Oct 2004 Posts: 9	thanks for the response striker - that didn't really make sense to me either so i looked into this a bit further. after a while of messing with the image and gif plugin i eventually found that the shoutcast3.gif was simply a png file that had been renamed as a gif - i renamed it to png and converted to gif and everything works fine now am i the only one thats experienced this problem?

2004-10-21, 13:36	#6
Striker Fan Join Date: Mar 2004 Posts: 477	haha weird, but it actually worked yes :kickass: for others who would like to fix. download the next file, rightclick, save target as and replace the old one: shoutcast3.gif

2004-10-21, 21:27	#8
ChEeSyBoOfS Senior Member Join Date: Feb 2004 Location: Luton Posts: 169	@henners, well done dude! :saint:

2004-10-22, 06:48	#9
daghostmon Junior Member Join Date: Jul 2004 Posts: 10	i don't get it. 1.0 worked fine in fact it even hooked up to the streams faster. as soon as i downloaded 1.1 thru avalaunch i have the "could not parse node" problem and slower connect times. seems lf this is a final version this needs to be addressed. i went back to 1.0 for now.

2004-10-22, 10:49	#10
Henners Junior Member Join Date: Oct 2004 Posts: 9	cheers for the praise - always nice to be appreciated :d daghostmon - just download and replace your shoutcast3.gif image with the one striker has kindly posted above (would have done this myself but generally my web server is only up for testing purposes) and this will fix the "could not parse node issue". as for the speed issue i can't say that i've noticed this although the fix does make it seem more responsive - probably due to the 1 second delay that was being used to display the error dialog. i don't know much about python (yet!) so not sure what the threading model is but i'm pretty sure this dialog is blocking execution while it is displayed.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)