2014-03-04, 17:29
For some time now I've been getting errors when using the CNET podcasts add-on. I'm running XBMC on a Raspberry PI so I'm not sure if this is a Raspberry PI issue, a CNET add-on issue or just a problem with the CNET website.
When I run the add-on it plays the first video fine, but when I then try and play the next video in the list it will usually fail to play and display an error message saying that the video didn't play. A second attempt to play the video will also usually fail, but this time it will display no error message, it just doesn't do anything except show the busy sign for a short while. On the third attempt the video will usually play fine, but when I move to the next video in the list I get the same sequence of problems start all over again.
This sequence only happens on CNET podcasts and it makes no difference which CNET podcast I'm playing. It maybe a problem with the traffic to the CNET website but I'm confused as to why the third attempt usually works. If it was a traffic issue then it would be reasonable to expect it to be random which attempt would work.
I'm happy to try and produce some log files if someone can tell me how to do this. I assume there is an option to turn logging on but given that it is a Raspberry PI I've no idea how I would then transfer any logs to this website.
When I run the add-on it plays the first video fine, but when I then try and play the next video in the list it will usually fail to play and display an error message saying that the video didn't play. A second attempt to play the video will also usually fail, but this time it will display no error message, it just doesn't do anything except show the busy sign for a short while. On the third attempt the video will usually play fine, but when I move to the next video in the list I get the same sequence of problems start all over again.
This sequence only happens on CNET podcasts and it makes no difference which CNET podcast I'm playing. It maybe a problem with the traffic to the CNET website but I'm confused as to why the third attempt usually works. If it was a traffic issue then it would be reasonable to expect it to be random which attempt would work.
I'm happy to try and produce some log files if someone can tell me how to do this. I assume there is an option to turn logging on but given that it is a Raspberry PI I've no idea how I would then transfer any logs to this website.