[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: Plasma Media Center progress
From: Christopher Blauvelt <cblauvelt () gmail ! com>
Date: 2010-04-22 17:09:35
Message-ID: t2offa898c91004221009kfc5b6551n2212a4eab7b3e1f9 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Thu, Apr 22, 2010 at 12:15 PM, Markus <kamikazow@web.de> wrote:
> Am Donnerstag 22 April 2010 17:08:24 schrieb todd rme:
> > I think kaffeine does as well.
>
> Recording as well? LibVLC should provide all needed features and since VLC
> is
> going to be Phonon's preferred back-end (at least
>
> http://amarok.kde.org/blog/archives/1171-Rapid-Progress-in-KDE-Multimedia.html
> sounds like that), it should be installed with KDE SC anyway...
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
Recording the incoming signal is not the difficult part. The difficult part
is the management. Scheduling recordings, storing recordings, deconflicting
recordings given a variable number of tv tuners, receiving and processing
accuarate show scheduling information. These are non-trivial items which
took the MythTV folks a while to get right. If we're going to go down this
route, I think it would make more sense to connect to the MythTV backend
(whether remote or on the local machine) and manage recordings that way, but
all in due time.
Chris
[Attachment #5 (text/html)]
<div class="gmail_quote">On Thu, Apr 22, 2010 at 12:15 PM, Markus <span \
dir="ltr"><<a href="mailto:kamikazow@web.de">kamikazow@web.de</a>></span> \
wrote:<br> <blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; \
PADDING-LEFT: 1ex" class="gmail_quote">Am Donnerstag 22 April 2010 17:08:24 schrieb \
todd rme:<br> <div class="im">> I think kaffeine does as \
well.<br><br></div>Recording as well? LibVLC should provide all needed features and \
since VLC is<br>going to be Phonon's preferred back-end (at least<br><a \
href="http://amarok.kde.org/blog/archives/1171-Rapid-Progress-in-KDE-Multimedia.html" \
target="_blank">http://amarok.kde.org/blog/archives/1171-Rapid-Progress-in-KDE-Multimedia.html</a><br>
sounds like that), it should be installed with KDE SC anyway...<br>
<div>
<div></div>
<div class="h5">_______________________________________________<br>Plasma-devel \
mailing list<br><a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
</div></div></blockquote></div> <div><br> </div>
<div>Recording the incoming signal is not the difficult part. The difficult part is \
the management. Scheduling recordings, storing recordings, deconflicting recordings \
given a variable number of tv tuners, receiving and processing accuarate show \
scheduling information. These are non-trivial items which took the MythTV folks a \
while to get right. If we're going to go down this route, I think it would make \
more sense to connect to the MythTV backend (whether remote or on the local machine) \
and manage recordings that way, but all in due time.</div>
<div>Chris</div>
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic