[kaffeine] [Bug 376844] Freeze at channel switching with GPU/VDPAU

2018-05-13 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=376844

--- Comment #14 from romeoK <romeokni...@gmail.com> ---
I need to withdraw from my above statement. After doing more tests (with
hundred of freezes) and searching the web for another 10 hours, i have to agree
with Mauro, that when you have an nvidia card and using proprietary driver with
Kaffeine/libVLC, the only way to overcome the 'failed to idle DMA' error, is to
disable vdpau (until nvidia has fixed this problem). So i inserted the line
'export VDPAU_DRIVER=none' into /home/.profile , and have had no freezes and
errors until now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 376844] Freeze at channel switching with GPU/VDPAU

2018-05-13 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=376844

--- Comment #13 from romeoK <romeokni...@gmail.com> ---
I had several other continous errors and freezes when switching channels, like
below:

core input error: ES_OUT_SET_(GROUP_)PCR  is called too late (pts_delay
increased to 300 ms)
core input error: ES_OUT_RESET_PCR called

and also

Stream seems to be too havy[sic] to be displayed.

I could completely get rid of all these errors by setting the following
parameter:

--file-caching 1000 (tested with lower values too, but gave above errors
again).

I'm not sure why file-caching and not live-caching has to be altered, but it
works. 
Hopefully this helps someone, and maybe the vlc buffer could be raised by
default?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 394201] New: Aspect ratio setting is not stored.

2018-05-13 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=394201

Bug ID: 394201
   Summary: Aspect ratio setting is not stored.
   Product: kaffeine
   Version: 2.0.15
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: romeokni...@gmail.com
  Target Milestone: ---

When changing the aspect ratio via context menu (for example to 4:3) the
setting is not stored. Next time you open Kaffeine aspect ratio is set to
automatic again (i believe) even none of the checkboxes in the context menu
under 'video/aspect raio' is set.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 394158] New: Exit dialogue when records are scheduled does not remember it's state.

2018-05-12 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=394158

Bug ID: 394158
   Summary: Exit dialogue when records are scheduled does not
remember it's state.
   Product: kaffeine
   Version: 2.0.15
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: romeokni...@gmail.com
  Target Milestone: ---

When you close Kaffeine and there are scheduled records, Kaffeine asks if you
really want to quit. If you select 'yes' and 'don't show this message again',
the next time you close Kaffeine, the same message is shown again nevertheless.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 394073] Changing the volume using the scrollwheel does not work correctly.

2018-05-11 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=394073

--- Comment #1 from romeoK <romeokni...@gmail.com> ---
Please note, that when timeshift is active, the scrollwheel is used to jump
forward/backward in the stream. This should be disabled, or it might conflict
with the volume change.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 394076] After changing key shortcuts, old bindings still active and conflicting.

2018-05-10 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=394076

--- Comment #1 from romeoK <romeokni...@gmail.com> ---
additional comment: After assigning new keys, as long as you don't restart
Kaffeine, the bindings work.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 394075] Mousepointer does not hide in fullscreen mode after movement.

2018-05-10 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=394075

--- Comment #1 from romeoK <romeokni...@gmail.com> ---
additional comment:

Since day 1 of using Kaffeine, i have this warning under settings/diagnostic,
not sure if it's related.

[Warning ] QObject::connect: No such slot DvbTab::hideCursor()

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 394076] New: After changing key shortcuts, old bindings still active and conflicting.

2018-05-10 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=394076

Bug ID: 394076
   Summary: After changing key shortcuts, old bindings still
active and conflicting.
   Product: kaffeine
   Version: 2.0.15
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: romeokni...@gmail.com
  Target Milestone: ---

(I'm using the german language version, so the terms might be slightly
different)

the standard shortcut for 'moving 15s' forward is set to 'cursor right'
the standard shortcut for 'moving 15s' backward is set to 'cursor left'

Now, for example i want to use the cursor left/right for changing the volume.

I set the shortcut for volume up to 'cursor right'. Kaffeine asks if i want to
reassign the key to the new shortcut, i say 'yes'
I set the shortcut for volume down to 'cursor left'. Kaffeine asks if i want to
reassign the key to the new shortcut, i say 'yes'

I press ok, and close Kaffeine.

Next time i start Kaffeine and use the newly assigned keys, it says "there is a
conflict/double with these keys"

When you go back into settings/shortcuts, you can see that Kaffeine has not
deleted the original keys bindings.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 394075] New: Mousepointer does not hide in fullscreen mode after movement.

2018-05-10 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=394075

Bug ID: 394075
   Summary: Mousepointer does not hide in fullscreen mode after
movement.
   Product: kaffeine
   Version: 2.0.15
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: romeokni...@gmail.com
  Target Milestone: ---

When in fullscreen mode, the mousepointer does hide, but only until you move
it. From then it does not hide anymore. This applies to fullscreen mode only
(afair).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 394073] New: Changing the volume using the scrollwheel does not work correctly.

2018-05-10 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=394073

Bug ID: 394073
   Summary: Changing the volume using the scrollwheel does not
work correctly.
   Product: kaffeine
   Version: 2.0.15
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: romeokni...@gmail.com
  Target Milestone: ---

Changing the volume with the scrollwheel of the mouse does not work when
pointer is inside the media window. 

You can make the scrollwheel only work like doing so:

Go into fullscreen mode. The top menu is hidden. Now hover the mouse into the
top menu and then very carefully hover back into the media window, but dont let
the top menu dissapear. Now hover up again into the top menu, and voila, the
scrollwheel works perfectly (as long as you don't leave the boundaries of the
top menu)

Would be nice if the scrollwheel works everywhere inside the application.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 394027] Fullscreen and minimal flags don't work with lastchannel

2018-05-09 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=394027

romeoK <romeokni...@gmail.com> changed:

   What|Removed |Added

 CC||romeokni...@gmail.com

--- Comment #1 from romeoK <romeokni...@gmail.com> ---
I reported something similar yesterday, already fixed i believe. 

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

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 394000] New: When starting Kaffeine with more than 2 parameters, only the last parameter is used.

2018-05-08 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=394000

Bug ID: 394000
   Summary: When starting Kaffeine with more than 2 parameters,
only the last parameter is used.
   Product: kaffeine
   Version: 2.0.15
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: romeokni...@gmail.com
  Target Milestone: ---

When i start Kaffeine with these parameters

kaffeine %U -m -t

it works as expected, Kaffeine starts in in minimal mode (-m) and always on top
(-t)

But i need to start Kaffeine like this:

kaffeine %U -m -t --channel 5

so i can avoid the intro-screen(select if tv/dvd/file etc.)

But now, the first 2 parameters are ignored, so only channel 5 is tuned.

It seems that whenever i use - and -- parameters in conjunction, then only the
-- ones are used?

I tried to change the order of the parameters, but still only the --channel 5
parameter is used then.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 376844] Freeze at channel switching with GPU/VDPAU

2018-05-01 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=376844

romeoK <romeokni...@gmail.com> changed:

   What|Removed |Added

 Status|CONFIRMED   |UNCONFIRMED
Summary|Freeze at channel switching |Freeze at channel switching
   |with VDPAU enabled  |with GPU/VDPAU
 Ever confirmed|1   |0

--- Comment #12 from romeoK <romeokni...@gmail.com> ---
Ok thanks, you are right, i am using

avcodec decoder: Using NVIDIA VDPAU Driver Shared Library  384.111  Tue Dec 19
22:55:29 PST 2017 for hardware decoding.

I will try what you suggested with the libVLC parameters.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 376844] Freeze at channel switching

2018-05-01 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=376844

romeoK <romeokni...@gmail.com> changed:

   What|Removed |Added

 CC||romeokni...@gmail.com

--- Comment #10 from romeoK <romeokni...@gmail.com> ---
Same error here with Kaffeine 2.0.14

While switching through the channellist using keyboard or mouse, sometimes
suddenly Kaffeine freezes video and audio.

In the terminal window it then prints continously the following error message: 

Failed to idle DMA
Failed to idle DMA
Failed to idle DMA
etc.

The complete system seems to hang then, the mouse barely moves. I have to press
strg-alt-backspace to logout (takes up to 10 seconds until keypress is
recognised by the system)

When i log back in, often i need to kill the process Kaffeine first before i
can use it again.

The "failed to idle DMA" only happens when switching through channels 1 out of
~25 times. It happens in fullscreen as well as in windowed-modes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 393679] New: Recording schedule: When duration of an entry is set to 00:00, nothing happens (feature request)

2018-04-30 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=393679

Bug ID: 393679
   Summary: Recording schedule: When duration of an entry is set
to 00:00, nothing happens (feature request)
   Product: kaffeine
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: romeokni...@gmail.com
  Target Milestone: ---

Kaffeine 2.0.14

I know this is not a real bug, but it could become a new feature:

Right now, when you edit an existing entry in the recording schedule, and set
the duration of the event to 00:00, then when the recording starts, nothing
happens (i.e. no data is written to disk, no channel is switched).

Could this behaviour be used to easily implement the most missing feature in
Kaffeine: 'just tune into the given channel at the given time and do not record
anything on disc'?

It sounds consequentially to me:

1. a schedule entry should do something, at least. 
2. if the duration is set to 00:00, not a single second of video should be
written to disk. 
3. but the programmed channel should be tuned in, obviously

I can't think of any negative sideffects when this get implemented. For
example, when a 'normal' user programs an recording event from the epg, there
are no shows that have a duration of 00:00, so everything works as expected for
him.

My motivation: I have a recurring schedule of about ~10 shows/day which i want
Kaffeine switch automatically to (e.g. switch to newschannel X at 3pm, stay
there until next scheduled event takes place). Right now, gigabytes of data are
written on my SSD Drive everyday, without any need, because there's no way to
prevent scheduled recordings from doing so.

This would be my most wanted missing feature in Kaffeine.

I also want to refer to
https://blog.codinghorror.com/thats-not-a-bug-its-a-feature-request/

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 393650] New: On scheduled recording, user can inadvertently initiate a second recording on the same channel.

2018-04-29 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=393650

Bug ID: 393650
   Summary: On scheduled recording, user can inadvertently
initiate a second recording on the same channel.
   Product: kaffeine
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: romeokni...@gmail.com
  Target Milestone: ---

Kaffeine 2.0.14

When a scheduled recording is running, the user can initiate another recording
on the same channel using the menu item 'Instant recording' (or by defined key
"R"), so that 2 identical streams are written parallel to disk at the same
time. 
(With only 1 dvb card installed in the system)

I believe this is an unwanted behaviour.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 393647] New: Screen turns black when scheduled recording starts (single dvb-card)

2018-04-29 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=393647

Bug ID: 393647
   Summary: Screen turns black when scheduled recording starts
(single dvb-card)
   Product: kaffeine
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: romeokni...@gmail.com
  Target Milestone: ---

Kaffeine 2.0.14

The following bug may NOT happen if there is more than 1 dvb card installed.

Steps to comprehend the behaviour:

-Start Kaffeine and program a scheduled recording on channel "B".
-Now go and watch live-tv on channel "A" (on a different transponder)
-When the scheduled recording begins, Kaffeine turns channel "A" black, giving
the following message: 'no available device found'. In fact Kaffeine internally
switched to the scheduled channel "B" and records it (writing data to disk).

You can "follow" the scheduled recording by hand, switching to channel "B"
manually. (So you can have a picture again).

Suggestion: when a scheduled recording starts (and only 1 dvb card is
installed) don't turn the screen black and give error "no available device
found", instead tune to the recording channel.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 393533] Kaffeine --lastchannel does not work when using minmal-mode

2018-04-26 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=393533

romeoK <romeokni...@gmail.com> changed:

   What|Removed |Added

 CC||romeokni...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 393533] Kaffeine --lastchannel does not work when using minmal-mode

2018-04-26 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=393533

--- Comment #1 from romeoK <romeokni...@gmail.com> ---
I need to add that in the configuration of Kaffeine, you have to set the
startup-display-mode set to: 'Minimal mode' or 'remember last setting'.
Otherwise the described bug does not appear.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 393533] New: Kaffeine --lastchannel does not work when using minmal-mode

2018-04-26 Thread romeoK
https://bugs.kde.org/show_bug.cgi?id=393533

Bug ID: 393533
   Summary: Kaffeine --lastchannel does not work when using
minmal-mode
   Product: kaffeine
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: romeokni...@gmail.com
  Target Milestone: ---

Kaffeine 2.0.14

Tune in a tv channel and put Kaffeine into normal mode. Then close Kaffeine.
Next time you open Kaffeine with --lastchannel it does tune to the last tv
channel, it works as expected.

Now tune in a tv channel and put Kaffeine into minimal-mode. Then close
Kaffeine. Next time you open Kaffeine with --lastchannel it does tune to the
last tv channel too, but this time the intro selection screen is overlayed and
does not disappear even when you press '5'. You then have to switch interface
modes back and forth to get rid of the selection-screen and bring up the tv
stream.

-- 
You are receiving this mail because:
You are watching all bug changes.