bad quality of a single multiplexer

Can you please confirm that it's not a buffering issue? Which engine are you using in kaffeine?
FAQ #823: “How do I get HD channels working smoothly?”.

How do I get to know which engine am I using in kaffeine? it seems there is no option to get this info in the menus.

It's in the preferences or menu somewhere, last time I checked. I haven't used it in about 2 years.

I chcecked but there is nothing in this version of Kaffeine. It's 1.0-svn3
I checked the video driver I use in MeTV and that is xv. Tried some others but with no results.

Yep, looks like the later kaffeines are xine only.

I tried editing the xine configuration file of me-tv as suggested in https://answers.launchpad.net/me-tv/+faq/823
but the problem is still there.
Anything else I can try?

Can you confirm the exact frequency that kaffeine is using (maybe in the verbose console output)? Sometimes adding an offset to the frequency helps, maybe that kaffeine is doing that.

Also, try recording something and playing it back? Is it still choppy?

the frequency is 514, BW 8MHz but I do not know how to start the verbose output.
I tried to record a video on the cahannel that cannot be displayed. Once replayed it still chops, but at least you can see the video. Better but not perfect, it stll chops every 3/4 seconds.

514? Where is this from?

514 MHz,
Banwidth 8 MHz,
DVB-T terrestrial, Italy,

it is one of the RAI muxes here in Milano. it fetures 5 TV channels + 1 Radio channel.

I can confirm this with several multiplexers in Germany.
Normally playback starts with perfect quality, then after some time it gets choppy (me-tv sometimes even isn't able to lock to the channel).
After closing me-tv, waiting some minutes and then restarting it, quality is perfect again.
This behaviour is reproducible for me and happens several times every day, on different multiplexers and channels.

Signal quality is good, never had problems before. First time I observed this was after upgrading to me-tv 1.2.4 some weeks ago (on Ubuntu 10.04).

If I find the time, I will downgrade again and see if the problem still persists with an older version of me-tv (1.1.2, which crashed quite often...).

* Marco, is this the same with you? This seems similar but different i.e. "waiting some minutes". Isn't yours always choppy?
* What's the CPU load like when it misbehaves?
* If you've got the know-how then try the latest from the source repository which polls rather than sleeps in the frontend loop

CPU load is normal, between 5 and 25 %.
I am compiling 1.2.5 from source at the moment, I'll report later if anything has changed.

It does not seem to be precisely the same. To me the only mux with problems is the 514 Mhz.
One of the channels (RAI3) does not even lock in. If I record it, it records a choppy video.
The other channels sometimes are fine, some other are choppy, but when they are, you experience degradaton in a matter of few seconds, not after minutes. This mux was switched on by RAI on May 12th, replacing the old one who was and still is fine.

With me-tv 1.2.5 picture is still choppy.
At the moment I don't think me-tv is the problem for me, although the behaviour seems similar to the one Marco describes.
Going to try some other firmware versions for my DVB card, just to be sure. I will report if I have news for you.

Thanks Jan.

Marco, you should try the latest in the source repository also if you can. If not, then you'll have to wait until 1.2.5 is released.

Jan, please try the latest again. I've just made a change that might help.

Jan, this sounds like the same as your issue ... https://88.191.250.119/viewtopic.php?f=2&t=8252 ... not that it helps. Could be a device thing.

I think that we've found a bug that was causing the issues that you were seeing. Please try the latest in the source repository.

Hi
tried 1.2.6 but the problem is still there. Still one of the channels of the mux cannot be tuned.

This question was expired because it remained in the 'Open' state without activity for the last 15 days.