--===============1011449959==
Content-Type: multipart/alternative; boundary=0016362848280d3db10484d6605e

--0016362848280d3db10484d6605e
Content-Type: text/plain; charset=ISO-8859-1

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

--0016362848280d3db10484d6605e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Thu, Apr 22, 2010 at 12:15 PM, Markus <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:kamikazow@web.de">kamikazow@web.de</a>&gt;=
</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">Am Donnerstag 22 April 2010 17:0=
8:24 schrieb todd rme:<br>
<div class=3D"im">&gt; I think kaffeine does as well.<br><br></div>Recordin=
g as well? LibVLC should provide all needed features and since VLC is<br>go=
ing to be Phonon&#39;s preferred back-end (at least<br><a href=3D"http://am=
arok.kde.org/blog/archives/1171-Rapid-Progress-in-KDE-Multimedia.html" targ=
et=3D"_blank">http://amarok.kde.org/blog/archives/1171-Rapid-Progress-in-KD=
E-Multimedia.html</a><br>
sounds like that), it should be installed with KDE SC anyway...<br>
<div>
<div></div>
<div class=3D"h5">_______________________________________________<br>Plasma=
-devel mailing list<br><a href=3D"mailto:Plasma-devel@kde.org">Plasma-devel=
@kde.org</a><br><a href=3D"https://mail.kde.org/mailman/listinfo/plasma-dev=
el" target=3D"_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a=
><br>
</div></div></blockquote></div>
<div><br>=A0</div>
<div>Recording the incoming signal is not the difficult part.=A0 The diffic=
ult part is the management.=A0 Scheduling recordings, storing recordings, d=
econflicting recordings given a variable number of tv tuners, receiving and=
 processing accuarate show scheduling information.=A0 These are non-trivial=
 items which took the MythTV folks a while to get right.=A0 If we&#39;re go=
ing to go down this route, I think it would make more sense to connect to t=
he MythTV backend (whether remote or on the local machine) and manage recor=
dings that way, but all in due time.</div>

<div>Chris</div>

--0016362848280d3db10484d6605e--

--===============1011449959==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

--===============1011449959==--