Timeouts when polling demuxers

Bug #190443 reported by Arkenlond
8
Affects Status Importance Assigned to Milestone
Me TV
Won't Fix
Medium
Unassigned

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).

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Can you please attach an example the log? Are you using DVB-T?

Changed in me-tv:
assignee: nobody → michael-lamothe
importance: Undecided → High
milestone: none → station-5
status: New → In Progress
Revision history for this message
Arkenlond (arkenlond) wrote :
Download full text (7.7 KiB)

I am using DVB-T

Here is a copy of the log file

09.02.2008 13:48:32 - Me TV Version: 0.5.14
09.02.2008 13:48:32 - Loading glade file '/usr/share/me-tv/glade/me-tv.glade'
09.02.2008 13:48:32 - Loading EPG from '/home/benoit/.me-tv/epg.xml'
09.02.2008 13:48:32 - EPG file loaded
09.02.2008 13:48:32 - Channel file loaded
09.02.2008 13:48:32 - Using 'xine' engine
09.02.2008 13:48:34 - Request to change channel to 'TF1'
09.02.2008 13:48:34 - Changing channel to 'TF1'
09.02.2008 13:48:34 - Purging remaining EPG events
09.02.2008 13:48:34 - EPG events purged
09.02.2008 13:48:34 - Tuning to transponder at 562167000 ...
09.02.2008 13:48:34 - Waiting for signal lock ...
09.02.2008 13:48:35 - Got signal lock
09.02.2008 13:48:35 - Tuned to transponder at 562167000
09.02.2008 13:48:35 - Video thread created
09.02.2008 13:48:35 - About to open FIFO 'fifo://home/benoit/.me-tv/video.fifo' ...
09.02.2008 13:48:35 - Stream thread created
09.02.2008 13:48:35 - EPG thread created
09.02.2008 13:48:35 - --> Stream thread function
09.02.2008 13:48:35 - Trying to auto detect PIDs
09.02.2008 13:48:35 - Channel changed to 'TF1'
09.02.2008 13:48:40 - Exception message: 'Timeout while polling for demuxer'
09.02.2008 13:48:40 - Failed to set PIDs automatically: Timeout while polling for demuxer
09.02.2008 13:48:40 - Stream Thread: Set video PID filter to 120 (0x78)
09.02.2008 13:48:40 - Stream Thread: Set audio PID filter to 130 (0x82)
09.02.2008 13:48:40 - Exception message: 'Timeout while polling for demuxer'
09.02.2008 13:48:40 - Exception in EPG thread: Timeout while polling for demuxer
09.02.2008 13:48:45 - Exception message: 'Timeout while polling for demuxer'
09.02.2008 13:48:45 - Exception in EPG thread: Timeout while polling for demuxer
09.02.2008 13:48:50 - Exception message: 'Timeout while polling for demuxer'
09.02.2008 13:48:50 - Exception in EPG thread: Timeout while polling for demuxer
09.02.2008 13:48:55 - Exception message: 'Timeout while polling for demuxer'
09.02.2008 13:48:55 - Exception in EPG thread: Timeout while polling for demuxer
09.02.2008 13:49:00 - Exception message: 'Timeout while polling for demuxer'
09.02.2008 13:49:00 - Exception in EPG thread: Timeout while polling for demuxer
09.02.2008 13:49:05 - Exception message: 'Timeout while polling for demuxer'
09.02.2008 13:49:05 - Exception in EPG thread: Timeout while polling for demuxer
09.02.2008 13:49:06 - Failed to open video stream: No demux plugin
09.02.2008 13:49:06 - Exception message: 'Failed to open video stream: No demux plugin'
09.02.2008 13:49:06 - Exception in static void* XineEngine::video_thread_function(XineEngine*): Failed to open video stream: No demux plugin
09.02.2008 13:49:06 - Pushing error message onto queue: Failed to open video stream: No demux plugin
09.02.2008 13:49:10 - Exception message: 'Timeout while polling for demuxer'
09.02.2008 13:49:10 - Exception in EPG thread: Timeout while polling for demuxer
09.02.2008 13:49:15 - Exception message: 'Timeout while polling for demuxer'
09.02.2008 13:49:15 - Exception in EPG thread: Timeout while polling for demuxer

Here is my channel.conf file :

TF1:562167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS...

Read more...

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

I just ran `cat /usr/share/doc/dvb-utils/examples/scan/dvb-t/fr-* | grep 562` and only got:

T 562000000 8MHz 2/3 NONE QAM64 8k 1/32 NONE
T 562000000 8MHz 2/3 NONE QAM64 8k 1/32 NONE
T 562000000 8MHz 1/2 NONE QAM16 8k 1/32 NONE
T 562000000 8MHz 2/3 NONE QAM64 8k 1/32 NONE

Are you sure that your channels.conf is correct with 562167000? Is the one for xine the same?

Revision history for this message
Arkenlond (arkenlond) wrote : Re: [Bug 190443] Re: Timeouts when polling demuxers

Yes, the one for Xine is the exact same. I had to add the 167000 offset in
order to get the channels to be received (found this advice on the net from
french DVB-T users).

If I do not put these offsets, i get this error message from Me TV : Failed
to lock to channel.

What amazes me is that it used to work fine with former versions of Me TV.

With Xine, the buffering takes about 3-5 seconds in order to retrieve a
channel (my reception appears not to be that good). But afterwards, it works
fine.

2008/2/10, Michael Lamothe <email address hidden>:
>
> I just ran `cat /usr/share/doc/dvb-utils/examples/scan/dvb-t/fr-* | grep
> 562` and only got:
>
> T 562000000 8MHz 2/3 NONE QAM64 8k 1/32 NONE
> T 562000000 8MHz 2/3 NONE QAM64 8k 1/32 NONE
> T 562000000 8MHz 1/2 NONE QAM16 8k 1/32 NONE
> T 562000000 8MHz 2/3 NONE QAM64 8k 1/32 NONE
>
> Are you sure that your channels.conf is correct with 562167000? Is the
> one for xine the same?
>
> --
> Timeouts when polling demuxers
> https://bugs.launchpad.net/bugs/190443
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

In which version of Me TV did it work?

Revision history for this message
Arkenlond (arkenlond) wrote :

I can't exactly remember... it was a few months ago. 0.3 series, I imagine. But, again, the reception in my former appartement (as I moved in between) might have been better and did not have to wait for so long before getting the channel buffered.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

The "Timeout" issues are certainly indicative of reception issues. I think that some other people in France have complained that Me TV is a little more sensitive to reception issues than other players. I certainly haven't seen this issue. I've set the timeout to 5 seconds for demuxer polling ,,, maybe I should wait longer, or make it configurable.

Revision history for this message
Arkenlond (arkenlond) wrote :

We certainly could give a try to the configurable timeout, just so we ca see if this is the real issue I am having.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Arkenlond and I have tried adjusting the timeout with no luck. It might be a buffering issue. I think that FrenchNux is having the same issue. I wonder if he has the same device?

What do you have?

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

This appears to be something that is related to poor reception. Me TV does not seem to work well with poor reception.

Changed in me-tv:
importance: High → Medium
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Here's an idea, what happens when you do a scan? Does it find any channels and generate a channels.conf?

Revision history for this message
FrenchNux (christophe-pauc) wrote :

When i scan it find any channels and generate pecfete channels.conf
it find all channels ...
----------------------------------------
> From: <email address hidden>
> To: <email address hidden>
> Date: Mon, 11 Feb 2008 02:26:09 +0000
> Subject: [Bug 190443] Re: Timeouts when polling demuxers
>
> Here's an idea, what happens when you do a scan? Does it find any
> channels and generate a channels.conf?
>
> --
> Timeouts when polling demuxers
> https://bugs.launchpad.net/bugs/190443
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
Nouveau ! Créez votre profil Messenger !
http://home.services.spaces.live.com/

Revision history for this message
bojo42 (bojo42) wrote :

I can confirm this and also think suffering from it since the 0.3 releases (but i also can't remember exactly). Just like above totem-xine is working well and scanning produces a correct channels.conf. Maybe it's really related to bad handling of a low signal strength, since sometimes when clicking through the EPG table some stations will work randomly. (although i wasn't able to captured this in the log right now)

I haven't posted a bug, cause since gutsy i have some stability problems with the intel graphic driver and so using the i810 driver with xv problems, therefore i thought it's caused by my setup. But reading this report i have tested MeTV on 2 two other computers with different and configurations and different places, it's always the same.

My hardware is a Terratec Cinergy T2 conected via USB on an HP notebook and i'm using DVB-T in the area of Central Germany.

Revision history for this message
Arkenlond (arkenlond) wrote :

Same receiver : Terratec Cinergy T2 via USB, DVB-T.

The auto-scan features fails to find any channel, since the 167000 offset is not included on the frequencies.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

For anyone that is able.

dvb_demuxer.h, line 42, replace with this,

 void set_filter(ushort pid, ushort table_id, ushort mask = 0xFF);

Please tell me if that helps. I think that this will work with 0.5.14 or 0.5.15 source. 0.5.15 source is available from the download page.

Revision history for this message
FrenchNux (christophe-pauc) wrote :

I changed dvb_demuxer.sh.

Now i always sound and pictures when i change channels. before i could have only sound.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Ahhhhhh nuts!

0.5.17 just got uploaded into debian and a sync request put in for Hardy. No worries, I'm quite sure that I'm still allowed to upload bug fixes and this certainly counts as one of those.

Also, I might release to my PPA tonight with this fix in it.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Revision 241, will be released in 0.5.18.

Changed in me-tv:
status: In Progress → Fix Committed
Revision history for this message
bojo42 (bojo42) wrote :

i'm very sorry to disappoint all here, but i have just compiled 0.5.14 with this change but i doesn't solve it in my case.

i did it the deb way by "sudo apt-get build-dep me-tv" + "apt-get source me-tv" + making the change to line 42 in src/dvb_demuxer.h + "fakeroot apt-get --build source me-tv" and installed the package.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Ok, we need some clarification before we can say this is fixed. I'll still release 0.5.18 with that fix/change in it because it does not seem to have any bad side effects.

Changed in me-tv:
status: Fix Committed → In Progress
Revision history for this message
bojo42 (bojo42) wrote :

I just did run "totem .xine/TV.pls --debug > totem.log" for posting it, before i changed my language settings. So maybe we can see the difference why Totem/Xine works and MeTV don't.

I did also try https://launchpad.net/me-tv/stable/0.5/+download/me-tv-0.5.18.tar.gz, as I checked src/dvb_demuxer.h but i can't see a change here, so i changed line 42 but it didn't help.

Revision history for this message
bojo42 (bojo42) wrote :

Now I log the case where it some channels worked randomly. This should be very interesting.

Revision history for this message
FrenchNux (christophe-pauc) wrote :

do you stop Definitively to make ubuntu package?
_________________________________________________________________
Microsoft vous recommande de mettre à jour Internet Explorer.
http://specials.fr.msn.com/IE7P25

Revision history for this message
FrenchNux (christophe-pauc) wrote :

Sorry i didn't understand "I've just uploaded Me TV 0.5.18 but I won't be using the typical -0ubuntu1 version for several reasons" and think you stopped to make ubuntu package.
i'm so poor in english

I'm no problem with new verison ....

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

This is crazy, we must be able to work this out, it's imperative that we fix it.

Changed in me-tv:
importance: Medium → Critical
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Bojo is trawling through the SVN revision history to find where this issue started. Good luck mate. Can anyone with the same issue please give him a hand!

Changed in me-tv:
assignee: michael-lamothe → bojo42
Revision history for this message
FrenchNux (christophe-pauc) wrote :

Sorry i have no problem
----------------------------------------
> From: <email address hidden>
> To: <email address hidden>
> Date: Mon, 25 Feb 2008 11:18:29 +0000
> Subject: [Bug 190443] Re: Timeouts when polling demuxers
>
> Bojo is trawling through the SVN revision history to find where this
> issue started. Good luck mate. Can anyone with the same issue please
> give him a hand!
>
> ** Changed in: me-tv
> Assignee: Michael Lamothe (michael-lamothe) => bojo42 (bojo42)
>
> --
> Timeouts when polling demuxers
> https://bugs.launchpad.net/bugs/190443
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
Nouveau ! Créez votre profil Messenger !
http://home.services.spaces.live.com/

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

jfestrada, I've noticed that you've subscribed to many bugs. Do you also have this issue?

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

After months of debugging we are still none-the-wiser about this issue. I'm going to have to skip it for 0.5 and try and fix it in 0.6.

Changed in me-tv:
importance: Critical → Medium
milestone: station-5 → station-6
Revision history for this message
BlackSmile[FR] (thomasclaessen) wrote :

Hi there,
I'm using Ubuntu Gutsy and if I launch me-TV via a terminal I'll get this :

Me TV-Message: 18.03.2008 00:25:06 - Me TV Version: 0.5.24
Me TV-Message: 18.03.2008 00:25:07 - Chargement du fichier glade '/usr/share/me-tv/glade/me-tv.glade' en cours
Me TV-Message: 18.03.2008 00:25:07 - Chargement du GEP à partir de '/home/blacksmile/.me-tv/epg.xml'
Me TV-Message: 18.03.2008 00:25:07 - GEP chargé
Me TV-Message: 18.03.2008 00:25:07 - Fichier de chaînes chargé
Me TV-Message: 18.03.2008 00:25:07 - Utilisation du moteur 'xine'
Me TV-Message: 18.03.2008 00:25:11 - Demande de changement de chaîne dans 'France 5'
Me TV-Message: 18.03.2008 00:25:11 - Changement de chaîne vers 'France 5'
Me TV-Message: 18.03.2008 00:25:11 - Purge des événements restant dans le GEP
Me TV-Message: 18.03.2008 00:25:11 - Evénements du GEP purgés
Me TV-Message: 18.03.2008 00:25:11 - Réglage du transpondeur à 490167000
Me TV-Message: 18.03.2008 00:25:11 - En attente du blocage du signal
Me TV-Message: 18.03.2008 00:25:11 - Signal Bloqué
Me TV-Message: 18.03.2008 00:25:11 - Transpondeur réglé à 490167000
Me TV-Message: 18.03.2008 00:25:11 - Thread de vidéo créé
Me TV-Message: 18.03.2008 00:25:11 - En train d'ouvrir FIFO 'fifo://home/blacksmile/.me-tv/video.fifo'
Me TV-Message: 18.03.2008 00:25:12 - Processus de flux créé
Me TV-Message: 18.03.2008 00:25:12 - Processus GEP créé
Me TV-Message: 18.03.2008 00:25:12 - Essai d'auto-détection des PIDs
Me TV-Message: 18.03.2008 00:25:12 - Chaîne changée à 'France 5'
Me TV-Message: message d'exception: 'Timeout durant le contact de demuxer'
Me TV-Message: message d'exception: 'Timeout durant le contact de demuxer'

And get a nice black screen

But if I launch it with another channel (let say France2) it work fine (bit slow). I change to any other channel and I won't get anything (feedback something in french like "no demuxer"). If I want to go back to France2 (the one who work just before) then it won't work again (with same error message).
I'm using Kaffeine with the xine engine and everything is OK (May I give you an advise ? add the possibility to add or substract 167 kHz to the channel for some dvb-t adapters)
Also using Channel.conf file in vlc is OK all channels working quiet well

Ho!! Not quiet sure it'll help I'm using Ati free driver with compiz enable

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Hi Thomas, I think?

Are you still using the same "Terratec cinergy T2" card? Same as Bojo?

I'm interested if there is something that I need to do to get this card working properly, maybe a delay somewhere. Have either of you used different tuner cards?

Wouldn't the add/subtract 167 kHz be better in the initial tuning file?

Thanks

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

BlackSmile and Bojo, does this issue describe your problems? https://bugs.launchpad.net/ubuntu/+source/xine-lib/+bug/36762. I know that you've gotten xine working but I wonder if there's been a recent change.

Revision history for this message
BlackSmile[FR] (thomasclaessen) wrote :

Ok! well first yes I'm using a "Terratec cinergy T2" card. It seem they need to add + 167000 for each line in the scan file to be able to find each channel (if not the command : scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/fr-<VotreVille> > ~/.me-tv/channels.conf will return an error message). the problem is, that it touch just some card so you may do like Kaffeine does : put an option when the prompt ask for your town file to add +167 kHz (am I clear enough?).

For the issue you just describe I'm not concern : first I'm on an AMD K7 (XP... i doubt) so not 64 bit using gutsy not dapper.
And again everything work quiet well with Kaffeine or with VLC using the "channels.conf" file created by the command line : scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/fr-Bordeaux > ~/.me-tv/channels.conf (corrected). My system is up to date with all repository activated.

Im on an AMD XP... / 512 Mo ram / 40 Go HDD / ATI RADEON 9800PRO (seem to be recognized as a weird 9500??) / Terratec on usb2 with a dongle for the logitech dinovo next to it.

Hope it helps

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

I've now read a bit about the +/-167k issue. I'll definitely consider this, please raise a blueprint for it so I can track it in 0.6, I don't want to add new features to 0.5.

I'm now talking to tadasss who has the same issue. I think that I broke Bojo.

Revision history for this message
bojo42 (bojo42) wrote :

no michael i'm not broken, just very busy ;)

but regarding this idea, let me see if i get it right: T2 adapters need an offset in their channel frequency. metv doesn't support, but totem-xine does it since the same channel.conf works with it rather than with metv. but if thats the case why are the older <0.4 releases (up to revision 79 in svn@sourceforge) work?

another questions is: can it be that this issue is somehow related to europe, as by now only french and german people reported it? would be nice to know if other T2 users outside of europe also got such problems.

and yes i "only" have two of these devices and i also don't know any linux user with another device. maybe we should start a post in the ubuntu forums.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

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

Revision history for this message
BlackSmile[FR] (thomasclaessen) wrote :

So nothing to get things working??
Lets say we had a clean channel.conf in me-tv. Why does it work with Kaffeine-xine (or vlc) but not with me-tv. What can I do
8-!

PS : For blueprint how does it work?? I'm not a develloper, and don't know what to set.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

There is no fix thus far. It doesn't work in Me TV because there's an issue with Me TV. This issue doesn't happen on my computer.

If you want to help, find a developer that knows DVB under linux with the same issue (not easy). I'm trying to fix it but I can't see what the issue is.

To add a blueprint go to https://blueprints.launchpad.net/me-tv/. You don't need to be a developer. The reason I get you to do this is so that you can take ownership of the issue and test it when it's implement it.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Finally, Bojo has confirmed that it's working for him on Hardy. We think that there might be something wrong with the T2 driver on Gutsy. Somehow kaffeine gets around this,

Changed in me-tv:
assignee: bojo42 → michael-lamothe
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.