[mythtv] OSX backend obstacles?

Robert Johnston anaerin at gmail.com
Sun Dec 11 14:54:49 EST 2005


On 12/11/05, Daniel Kristjansson <danielk at cuymedia.net> wrote:
> On Sun, 2005-12-11 at 17:02 +0000, Dave Abrahams wrote:
>
> > Which appears to be entirely concerned with getting video
> > off of capture hardware /cards/.  Since my DCT-6200
> > communicates over FireWire, I'm wondering if that ought to
> > be a non-issue?
>
> Not quite a non-issue, but a surmountable one. Right now we use
> the Linux firewire libraries. OSX probably has similar libraries
> but MythTV would have to be adapted to use them, either with an
> adaptation layer in MythTV or an external library that emulates
> the Linux firewire libraries with calls to the OSX firewire
> libraries. There are recorders like the DBOX2 that should already
> work on OSX.

Would it be possible to "Modularize" the Myth calls for recorders, so
you have an IVTV Module, a Firewire Module, a DVB Module and so on?
This would make it pretty easy to make a "Linux Firewire Module" and
an "OSX Firewire Module" (And, say, a "Solaris Firewire Module" or
whatever else people want to do) and to dynamically link them in at
runtime (So if you get a Firewire HD box, you don't need to completely
recompile Myth to use it, just compile the Required Firewire module,
drop it in, and restart MythBackend).

Just an idea. Would make for simpler additions and upgrades in the
future, and would make the code easier to debug (Easier tracking down
the problem in a small, isolated module with a simple "Test Client" (A
"Fake" backend that connects loads the module and pokes and probes it
'til it finds the data/command call that broke))
--
Robert "Anaerin" Johnston


More information about the mythtv-dev mailing list