Am Mittwoch, den 08.02.2012, 11:21 +0000 schrieb Adam Charrett:
> You could manually try tuning to a channel, starting EPG capture with
> epgcapstart and then see if you get any data by using the epgdata command
> (note this won't close the connection it will just keep spewing data/
> pause indefinitely).
Damn it. That seems to be all my fault. After seeing data coming out
when doing "epgcapstop", "select xxx", "epgcapstart", "epgdata", I
rememeberd that in the beginning I had a multiplex with inusfficient
infos, which let the getepg fail completely. Therefore on the next run
the "session.start_epg_capture" failed. I changed that to
"session.restart_epg_capture" and forgot about it.
Now that I changed that back to the original, it somewhat works. Data
seems to be processed, but in the end I get:
-- snip --
192.168.0.2:0 (8) processing 2114.0305
192.168.0.2:0 finished
Finished updates
Traceback (most recent call last):
File "/usr/bin/getepg", line 477, in get_services_info
info = connection.get_service_info(service.dvb_id)
File "/usr/lib/python2.5/site-packages/dvbstreamer/session.py", line 157, in
get_service_info
return ServiceInfo(lines)
File "/usr/lib/python2.5/site-packages/dvbstreamer/info.py", line 98, in
__init__
super(ServiceInfo, self).__init__(lines)
File "/usr/lib/python2.5/site-packages/dvbstreamer/info.py", line 67, in
__init__
doc = yaml.load(reduce(lambda x,y: x + '\n' + y, lines, ''))
File "/usr/lib/python2.5/site-packages/yaml/__init__.py", line 57, in load
loader = Loader(stream)
File "/usr/lib/python2.5/site-packages/yaml/loader.py", line 34, in __init__
Reader.__init__(self, stream)
File "/usr/lib/python2.5/site-packages/yaml/reader.py", line 114, in __init__
self.determine_encoding()
File "/usr/lib/python2.5/site-packages/yaml/reader.py", line 170, in
determine_encoding
self.update(1)
File "/usr/lib/python2.5/site-packages/yaml/reader.py", line 204, in update
self.check_printable(data)
File "/usr/lib/python2.5/site-packages/yaml/reader.py", line 179, in
check_printable
'unicode', "special characters are not allowed")
ReaderError: unacceptable character #x0086: special characters are not allowed
in "<string>", position 24
Exporting to epg.xml... Done
-- snip --
All I get in the xml are seven of my eight multiplexes listed as
channeles in the <tv></tv> tags.
With my very little python skills, I isolated the service that is
causing this. It's indeed using special characters in its name. I
noticed that in the beginnings of my dvbstreamer time and that was the
reason why I'm not using the channel names in freevo to tune in, but the
IDs.
Actually, I modified the sqlite database manually to get rid of these
characters. Didn't help, seems to get updated again when tuned in.
Anything I could try to get rid of these charaters?
Thanks very much for your help, Adam!
Cheers,
Manuel
--
Manuel Borchers
Web: http://www.matronix.de
eMail: man...@matronix.de
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
