me-tv-development team mailing list archive

[Michael Lamothe <michael.lamothe@xxxxxxxxx>]

Hey Bojo,

I don't think that 167K issue is related to our issue at all.  I don't
think that totem-xine, xine and mplayer do an automatic 167K, but
kaffeine can.  Some of the guys in France need to modify the initial
tuning file go get applications to tune properly (with the exception of
kaffeine).  What they are asking for is a new feature that does what
kaffeine does, add/subtract 167K from the frequency in the initial
tuning file which will generate a channels.conf with the offsets already
applied.

Yes, it could be related.  At the moment I have no pattern except for "a
couple of guys in Europe" ... which isn't much of a pattern.

The forum sounds like an excellent idea but I'm a little busy ATM trying
to fix a few things.  Anyone else with spare time to
talk/explain/convince people?  Actually, I'm really not good at it ...
that's the real excuse ... and lazy.

Thanks,

Michael

-- 
Timeouts when polling demuxers
https://bugs.launchpad.net/bugs/190443
You received this bug notification because you are a member of Me TV
Development, which is subscribed to Me TV.

Status in Me TV, it's TV for me computer: In Progress

Bug description:
As I run Me-TV, i keep getting messages like this one in the terminal as well as the classical No Demux Plugin Found.
I really seldomly get to see anything from the first channel in the channels.conf list, and it is all the same when I try to switch to another channel.

Me TV-Message: 09.02.2008 13:48:40 - Exception message: 'Timeout while polling for demuxer'

DVB TV works seamlessly with totem-xine (libxine1-ffmpeg installed).