From owner-freebsd-multimedia@FreeBSD.ORG Wed Dec 20 00:42:10 2006 Return-Path: X-Original-To: multimedia@freebsd.org Delivered-To: freebsd-multimedia@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3EA1D16A407 for ; Wed, 20 Dec 2006 00:42:10 +0000 (UTC) (envelope-from stephen.hocking@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B4F243C9F for ; Wed, 20 Dec 2006 00:42:09 +0000 (GMT) (envelope-from stephen.hocking@gmail.com) Received: by py-out-1112.google.com with SMTP id f31so1080887pyh for ; Tue, 19 Dec 2006 16:42:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=KUk3L8L+75qI5KwUa0qIqJSMjjG/nN2eTpAs1vb6Y4Bbq/N4LK2S+Z64iBPpnMr4CzxI4y3eaM5bseKZnR6LkFXUkhxe3lrzXtlwZdaxaepoNRhioo45x/al6x8YVsmG3HD8Wm+UMsAuy4n7YtFVAf5lDZ63VVo+zSEvXNcd/Bs= Received: by 10.65.93.18 with SMTP id v18mr8245058qbl.1166575328703; Tue, 19 Dec 2006 16:42:08 -0800 (PST) Received: by 10.65.216.7 with HTTP; Tue, 19 Dec 2006 16:42:08 -0800 (PST) Message-ID: <6300771b0612191642k3cda3985o4b860b839847f9d8@mail.gmail.com> Date: Wed, 20 Dec 2006 11:42:08 +1100 From: "Stephen Hocking" To: "usleepless@gmail.com" In-Reply-To: MIME-Version: 1.0 References: <6300771b0612181401i72e7cc58ta08e12de8d68d4d0@mail.gmail.com> <20061218232247.GQ4364@wantadilla.lemis.com> <6300771b0612181533m6ece3f38p379c78a75912d10d@mail.gmail.com> <6300771b0612181534h3158342aw554869660fc707ea@mail.gmail.com> <20061218234041.GU4364@wantadilla.lemis.com> <20061219224005.GC4364@wantadilla.lemis.com> <6300771b0612191524y64af793cy10f9bff4193536c7@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: multimedia@freebsd.org Subject: Re: MythTV (was: Possible FreeBSD port?) X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2006 00:42:10 -0000 On 12/20/06, usleepless@gmail.com wrote: > > Stephen, > > On 12/20/06, Stephen Hocking < stephen.hocking@gmail.com> wrote: > > On 12/20/06, usleepless@gmail.com wrote: > > > > > > > > > i did not make a port, but i am willing to help. but if people are > > > interested in a 0.18-fixes-postgresql-heavily-modified port of mythtv, > > > let me know. if there is enough interest we might pull it off. > > > > > > but i got the impression of the list that only the most recent version > > > of mythtv is worth aiming for ( i have no need to go to .19 or .20 ) > > > > > > > > I think that you're probably right as regards the versions, but have you > > > thought of pushing your patches back to the maintainers > > of MythTV? > > > > Stephen > > thank you for asking. > > are you subscribed to any of the mythtv lists? i am. Yup, certainly am. There's a few outstanding bugs that bother me (backend crashes after transcode when another program is being watched). they don't want to talk about changes to the database-layer: they > don't think the database is important and would rather have nothing to > do with sql. when i proposed to make mythtv cross-database-compatible > ( mysql, postgresql, mssql etc ), they responded with "we might move > to a embedded db like firebird"?. shutting off postgresql totally. Yeah, I can vaguely recall some of the debate on the lists. It's a shame - I try & write code so that it's as portable as possible, with appropriate abstraction layers, which dates from the time I used to port stuff from BSD over to uPort V/AT (286 SVR2). furthermore, the interprocess-communication in mythtv is horrific, > mostly busy wait loops, which makes a context-switching-hell. > unfortunatly mythtv developers lack essential db and ipc skills. the > abstraction is pretty good though. What were they smoking? Surely a simple select(2) would be good enough? they are hunting ghosts too: in the mailing lists "hickups" are > discussed regulary: they are fiddling with process priorities between > frontend and database/backend. at the same time they throw immense > queries to the db which could be so much more efficient with a proper > datamodel. Yes, I've seen the recommendations about putting the DB on a separate spindle to the recordings. for my own install, i implented a "settings cache" even before they > did! before this, every setting was queried from the db _everytime_ it > was used (ie: roundtrips all the time ). Yeah, it's not likely that you'll be changing things on a another session when you're currently active. > i am under the impression that most of the changes in .19 and .20 are > digital-broadcast-specific. this is of no interest to me: i am running > on 2 pvr500s. I'm all digital, and as far as I'm aware, there's no settled kernel API for DVB-T cards (or video really, in general) for FBSD. Stephen