[mythtv-users] PCI-E Analog Card

[R. G. Newbury]

On 01/24/2010 10:17 PM, Brent Norris wrote:
> On 1/24/2010 8:44 PM, R. G. Newbury wrote:
>
>> One aspect you may be misunderstanding, is that with Myth the *real*
>> idea is that you do NOT watch live tv very often. You record what you
>> want to want, and retrieve it later. Even 'Live-TV' is actually
>> recorded, and then displayed. So *IF* a program is scheduled for
>> recording, and recorded, the Front-end machines can each watch the same
>> file....Your need for some hundreds of front-ends means some technical
>> problems, which probably can be overcome. Getting waaay outside my
>> knowledge limits here..I only run combined boxes! Maybe some form of
>> multicast.
>
> I have used MythTV for several years now and I do understand the
> differences between LiveTV and recorded TV, that doesn't mean that my
> teachers and staff will. It is important to realize that when you think
> of 150 classrooms it doesn't seem that impossible that there are 10
> people that would turn on LiveTV "just for noise".

Ahh, well maybe the system should be designed so that they cannot *do* 
that. I suspect it would take 2 backend setups, but you could set the 
classroom frontends to 'see' a backend which has no operating tuners: 
therefor no live tv. They can only see what has been (requested to be) 
recorded.

>> You mention Vbrick, which I deduce is the methodology which presents
>> what would otherwise be an mpg stream presented by a Myth Frontend, into
>> a Sharepoint entity. These words are 'not English' to me. This whole
>> concept is at odds with the manner in which Myth works, although I must
>> admit, serving up videos, a-la-youtube, in a browser may solve lots of
>> technical issues. Depends upon the server capabilities I suspect.
>
> Vbrick is a different animal than mythtv. Since they are a company
> solution they have paid programmers working on problems. One of which is
> webpage delivery of content. In some ways they are like mythtv and in
> other ways they are something akin to a slingbox.

Not knowing how this works, I can only guess at the technical 
difficulties. With myth, it would be serving multiple frontends on a 
'video-on-demand' basis. With Vbrick, it depends on how the files can be 
delivered. I presume that the files are encoded and delivered 'live' and 
may not be/can not be saved for later delivery. If they can be saved, it 
would really change the constraints.

Geoff

          Tux says: "Be regular. Eat cron flakes."