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.

Reply via email to