[mythtv-users] can I use xine (VeXP) instead of mplayer in myth?

[and]

So maybe my statement was a bit broad and unrefined, but I actually 
just conveyed the information in the same form I found/received/read 
it....

The issue is still that you need to have one of the sanctioned distros 
(even mdk9.1 is out) to get the binary mpeg stuff. And my favorite 
Debian is completely out for now. But assuming you do use one of these 
I agree that you can just use the same hooks as the VeXP after a big 
bit of reverse engineering.

I really have been trying hard to figure these things out and have been 
reading the list faithfully as well as other lists, forums, goolge and 
the guys at VIA ( a bit more than a few minutes... ;-), and I don't 
think my original question was so stupid or uninformed in the light of 
the above limitations of the VIA mpeg. Asking questions is a time 
honored way to learn and some of us just also nee to ask the stupid 
questions to understand. This is a myth-user list and not the developer 
one... ;-)

As a user and noncoder the task of hooking mythtv up to the mpeg 
library was quite out of my league, but I thought that if myth had been 
using a player for the tv presentation (it wasn't that obvious as I 
mentioned before that it didn't) I could probably figure out how to 
switch it to VeXP given a bit of guidance.

rgds
anders

On Wednesday, August 27, 2003, at 06:29 AM, Scott Blomfield wrote:

> Any program can hook into that binary precompiled driver in the same 
> way
> VeXP does.... if VeXP can use it to decode MPEG, so can any other
> application. The source code to VeXP is open. You shouldn't need
> anything else. This is what Isaac and I have been saying all along.
> Don't get me wrong, the work is not trivial by any measure, but there 
> is
> existing example work anyone could look and copy across without signing
> an NDA, and it would be legal.
>
> The following is not a flame, it's an observation you really ought to
> think about:
>
> Since you readily admit that you do not understand this stuff, perhaps
> you might consider not making blanket statements and assertions about
> it. I appreciate that not everyone can know everything about this 
> stuff.
> Personally, I don't know that much about it either, but I at least
> looked up the details and tried to understand it, and I *listen* to the
> responses that I get. I read the list a lot, and gain knowledge that 
> way
> too. Two minutes spent on google can provide a wealth of information.
>
> -----Original Message-----
> From: and [mailto:hons at rcn.com]
> Sent: Tuesday, August 26, 2003 11:16 PM
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] can I use xine (VeXP) instead of mplayer in
> myth?
>
> You are right, and I don't really understand this as I'm not a code
> person.
> As I understood it they provide precompiled binary cle266 drivers for
> some distros and VeXP hooks into it and that is why you can only use
> VeXP on a few distros at the moment.
> With an NDA from VIA sales you can get access according to their
> opensource liaison guy I emailed with, so I guess you could get hold of
> the mpeg2 code and integrate it in myth... ;-)
>
> anders
>
> On Tuesday, August 26, 2003, at 05:30 PM, Isaac Richards wrote:
>
>> On Tuesday 26 August 2003 07:36 pm, and wrote:
>>> Mainly because the VIA open-source team are very unlikely to release
>>> the mpeg code for fear of reprisals from the movie industry.
> According
>>> to the viaarana forum discussions.
>>
>> Um.  How do you think support was integrated into Xine?
>>
>> Isaac
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users