Bug 387750 - TV frame rate too low
Summary: TV frame rate too low
Status: RESOLVED DUPLICATE of bug 389783
Alias: None
Product: kaffeine
Classification: Applications
Component: general (show other bugs)
Version: 2.0.13
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Mauro Carvalho Chehab
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-09 20:45 UTC by nolli111
Modified: 2018-11-08 10:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
attachment-31108-0.html (3.52 KB, text/html)
2017-12-11 14:26 UTC, nolli111
Details
attachment-30802-0.html (2.52 KB, text/html)
2017-12-11 19:15 UTC, nolli111
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nolli111 2017-12-09 20:45:48 UTC
TV-bilder laufen mit höchstens 20 Bilder inder secunde
Comment 1 Mauro Carvalho Chehab 2017-12-11 11:47:33 UTC
(In reply to nolli111 from comment #0)
> TV-bilder laufen mit höchstens 20 Bilder inder secunde

English please.
Comment 2 Mauro Carvalho Chehab 2017-12-11 11:59:29 UTC
(In reply to Mauro Carvalho Chehab from comment #1)
> (In reply to nolli111 from comment #0)
> > TV-bilder laufen mit höchstens 20 Bilder inder secunde
> 
> English please.

If I understood what you meant, from Google translator, you're saying that:
   "TV stream is at most 20 frame per second."

Right?

Yet, you didn't provide any information about what you're trying to watch, nor if libVLC is using vdpau or not.

The stream frame rate comes from a few factors:

1) the amount of frames per second at the recorded video;
2) the amount of time required to decode a video stream;
3) the amount of time required to display a single frame.

If the video is recorded with a low fps (1), there's nothing we can do: as far as I know, libVLC doesn't try to generate inter-frames to convert a low-fps video into a pseudo-higher-fps video.

Both (2) and (3) are directly related to the size of the video. I mean: a 4K resolution video takes a lot more time to be decoded/displayed than HD. Also, both depends on having a CPU (or GPU) good enough to allow watching videos with high fps. If your CPU/GPU aren't good enough, the only solution is to upgrade your hardware. If they are, that's something that you could fix, likely by installing some packages that will allow libVLC do to hardware decoding.

What kind of video are you trying to watch? What's their resolution? Are you using hardware acceleration for video codec decoding?
Comment 3 nolli111 2017-12-11 14:26:50 UTC
Created attachment 109314 [details]
attachment-31108-0.html

I'm talking about the jerkiness in Kaffeine TV

Television pictures do not run smoothly

my English is not good



________________________________
Von: Mauro Carvalho Chehab <bugzilla_noreply@kde.org>
Gesendet: Montag, 11. Dezember 2017 12:59:29
An: gerhard.arnold@live.de
Betreff: [kaffeine] [Bug 387750] TV frame rate too low

https://bugs.kde.org/show_bug.cgi?id=387750

--- Comment #2 from Mauro Carvalho Chehab <mchehab+kde@kernel.org> ---
(In reply to Mauro Carvalho Chehab from comment #1)
> (In reply to nolli111 from comment #0)
> > TV-bilder laufen mit höchstens 20 Bilder inder secunde
>
> English please.

If I understood what you meant, from Google translator, you're saying that:
   "TV stream is at most 20 frame per second."

Right?

Yet, you didn't provide any information about what you're trying to watch, nor
if libVLC is using vdpau or not.

The stream frame rate comes from a few factors:

1) the amount of frames per second at the recorded video;
2) the amount of time required to decode a video stream;
3) the amount of time required to display a single frame.

If the video is recorded with a low fps (1), there's nothing we can do: as far
as I know, libVLC doesn't try to generate inter-frames to convert a low-fps
video into a pseudo-higher-fps video.

Both (2) and (3) are directly related to the size of the video. I mean: a 4K
resolution video takes a lot more time to be decoded/displayed than HD. Also,
both depends on having a CPU (or GPU) good enough to allow watching videos with
high fps. If your CPU/GPU aren't good enough, the only solution is to upgrade
your hardware. If they are, that's something that you could fix, likely by
installing some packages that will allow libVLC do to hardware decoding.

What kind of video are you trying to watch? What's their resolution? Are you
using hardware acceleration for video codec decoding?

--
You are receiving this mail because:
You reported the bug.
Comment 4 Mauro Carvalho Chehab 2017-12-11 14:53:18 UTC
(In reply to nolli111 from comment #3)
> Created attachment 109314 [details]
> attachment-31108-0.html
> 
> I'm talking about the jerkiness in Kaffeine TV
> 
> Television pictures do not run smoothly

As I said, it is very likely due to either hardware issues or GPU driver.
Can you provide some logs with Kaffeine started with --debug?

What's your GPU?

> my English is not good

English is not my native language either. Yet, you English is very likely better that my German, as I don't know more than a few words in German :-)

Also, we use English on BZ and discussions, as that makes easier for people to understand each other.
Comment 5 nolli111 2017-12-11 19:15:31 UTC
Created attachment 109322 [details]
attachment-30802-0.html

My GPU is nVIDIA GTX1070

Where do I find the logs or how do I retrieve those in Kaffeine that started with --debug to provide them to you? I have been working with UBUNTU 17.10 and have no idea about Linux.

In reality, I can not speak English. I write all the texts in German and translate them with the Google translator. I then copy these into my emails.

________________________________
Von: Mauro Carvalho Chehab <bugzilla_noreply@kde.org>
Gesendet: Montag, 11. Dezember 2017 15:53:18
An: gerhard.arnold@live.de
Betreff: [kaffeine] [Bug 387750] TV frame rate too low

https://bugs.kde.org/show_bug.cgi?id=387750

--- Comment #4 from Mauro Carvalho Chehab <mchehab+kde@kernel.org> ---
(In reply to nolli111 from comment #3)
> Created attachment 109314 [details]
> attachment-31108-0.html
>
> I'm talking about the jerkiness in Kaffeine TV
>
> Television pictures do not run smoothly

As I said, it is very likely due to either hardware issues or GPU driver.
Can you provide some logs with Kaffeine started with --debug?

What's your GPU?

> my English is not good

English is not my native language either. Yet, you English is very likely
better that my German, as I don't know more than a few words in German :-)

Also, we use English on BZ and discussions, as that makes easier for people to
understand each other.

--
You are receiving this mail because:
You reported the bug.
Comment 6 Mauro Carvalho Chehab 2017-12-12 01:08:34 UTC
(In reply to nolli111 from comment #5)
> My GPU is nVIDIA GTX1070

Ok. You should then be sure that libVLC will use GPU for video codec.
This link could be helpful:
   https://wiki.videolan.org/VLC_GPU_Decoding/

You'll likely need to install some Ubuntu packages (if you didn't yet), in order for video accel to happen, using vdpau. You'll need to install them with something like:
   $ sudo apt install mesa-vdpau-drivers vdpau-driver-all

VLC version 2.2 and upper should use it automatically. Ubuntu 17.10 comes with vlc 3.0-git. So, it should automatically detect it.

Eventually, you might need to install the nvidia proprietary driver. personally, I don't like it. I stopped using it (and nvidia boards) years ago, because it used to be painful to make it work right. So, if I were you, I would try to make it work with the opensource nouveau driver first.

> 
> Where do I find the logs or how do I retrieve those in Kaffeine that started
> with --debug to provide them to you? I have been working with UBUNTU 17.10
> and have no idea about Linux.

Just call:
    $ kaffeine --debug

> In reality, I can not speak English. I write all the texts in German and
> translate them with the Google translator. I then copy these into my emails.
Comment 7 Mauro Carvalho Chehab 2018-02-20 19:03:12 UTC
This bug can be a duplicated bug:

   https://bugs.kde.org/show_bug.cgi?id=389783

As reported there, with some channels, enabling interlacing is too CPU intensitive. Please try disabling interlace. On -git version, this is now disabled by default.
Comment 8 Mauro Carvalho Chehab 2018-11-08 10:26:07 UTC
*** This bug has been marked as a duplicate of bug 389783 ***