[mythtv-users] Re: Best place to load dvb_bt8xx from?
Gregg
3gemail at gmail.com
Fri Apr 15 21:54:16 UTC 2005
This helped my out I am running fc3.
http://www.gossamer-threads.com/lists/mythtv/users/121385?search_string=%20mythtvsetup%20and%20dvb;#121385
-Gregg
>
> Hey all:
>
> I'm looking for the best way to trigger the load of the DVB driver
> for my HD2000 card.
>
> I'm assuming I want the module loaded before mythbackend starts?
>
> Where's the elegant way to trigger the module load? I'd like to
> think there's a better way to do it than with rc.local.
>
> Suggestions?
>
> Thanks,
> John.
>
> ------------------------------
>
> Message: 13
> Date: Fri, 15 Apr 2005 00:45:57 -0400
> From: Robert Tsai <rtsai1111 at comcast.net>
> Subject: Re: [mythtv-users] Best place to load dvb_bt8xx from?
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID: <20050415044557.GA9431 at post.harvard.edu>
> Content-Type: text/plain; charset=us-ascii
>
> On Thu, Apr 14, 2005 at 09:37:03PM -0700, John Freer wrote:
> > I'm looking for the best way to trigger the load of the DVB driver
> > for my HD2000 card.
> >
> > I'm assuming I want the module loaded before mythbackend starts?
> >
> > Where's the elegant way to trigger the module load? I'd like to
> > think there's a better way to do it than with rc.local.
>
> You should have some file like /etc/modules to list the modules you
> want loaded at boot time.
>
> --Rob
>
> ------------------------------
>
> Message: 14
> Date: Fri, 15 Apr 2005 00:54:15 -0400
> From: "jjlong" <jjlong at zoominternet.net>
> Subject: RE: [mythtv-users] RF remote
> To: "'Discussion about mythtv'" <mythtv-users at mythtv.org>
> Message-ID: <067401c54177$2c965310$2302a8c0 at PIII933MHz>
> Content-Type: text/plain; charset="us-ascii"
>
> I have this remote and have had a lot of luck programming it to work
> with all of my other devices. I agree that the button layout is a
> little awkward, but overall I'm happy with it.
>
> I haven't had much luck setting it up with myth though. I tried
> installing it like the ATI remote but I was never able to make it work.
> I searched all the LIRC and Myth archives, but never found anything that
> was much help. I gave up on it for now, but would really like to make
> it work in the future.
>
> >-----Original Message-----
> >From: mythtv-users-bounces at mythtv.org
> [mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Zole
> >Sent: Thursday, April 14, 2005 11:58 PM
> >To: devan at lippman.net; Discussion about mythtv
> >Subject: Re: [mythtv-users] RF remote
> >
> >
> >Just got the Niveus PC Remote, which seems to be similar to the ATI
> Remote Wonder and even uses the lirc_atiusb
> >module. Setting up the USB RF dongle with LIRC was very easy in my
> case, unlike the Hauppauge remote that came with
> >my capture card which was kind of a pain. The Niveus is also an IR
> remote for controlling TVs, cable boxes, DVD
> >players, etc. I've got it working with my TV, cable box, and
> PlayStation 2 (for DVDs), and you're supposed to be able
> >to program individual buttons using the original remote, but I haven't
> been able to make that work yet.
> >
> >
> >As a remote, it's OK. The buttons are gummy, and the button layout is
> kind of ridiculous (all the keys I find useful
> >are tiny and scrunched together towards the bottom of the unit).
> There's also some lag when using the remote in RF
> >mode, and so far keys aren't auto-repeating in MythTV (probably a
> config problem). But overall, it's serviceable.
> >
> >--Zole
>
> ------------------------------
>
> Message: 15
> Date: Fri, 15 Apr 2005 14:48:39 +0930
> From: Matthew Phillips <mythtv at mattp.name>
> Subject: Re: [mythtv-users] MythMusic playback speed too fast
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID: <8495556ffb7b84d8bc114839456b17ac at mattp.name>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> On 03/04/2005, at 4:34 PM, Matthew Phillips wrote:
> > MythMusic 0.17: when playing back mp3's (LAME-encoded,
> > alt-preset-standard) the playback speed is noticeably too fast, but
> > strangely no other distortion (e.g. no pitch shift). A side-effect is
> > that tracks also finish early, e.g. a 4:47 track finishes at about
> > 4:28. I'm using ALSA output to SPDIF on an EPIA M10K/FC3 system.
>
> Just a followup on this.
>
> It turns out I maligned mythmusic when in fact it was an issue with the
> SPDIF output. SPDIF needs a sample rate of 48KHz, while mythmusic,
> mplayer, etc output 44.1KHz from most music sources, since this is
> their native rate. Using "-srate 48000" fixed mplayer. To fix mythmusic
> I needed to add the following to /etc/asound.conf and tell mythmusic to
> use "ALSA:rate_convert" as the device.
>
> pcm_slave.test
> {
> pcm "spdif"
> rate 48000
> }
>
> pcm.rate_convert
> {
> type rate
> slave test
> }
>
> I'm sure there's a much better way to do this in general, in particular
> by using the advice at
> http://www.mythtv.info/moin.cgi/DigitalSoundHowTo and adapting it from
> the nforce example to the VIA 8236 chipset on my board.
>
> Does anyone already have such a beast for the VIA?
>
> Matt.
>
> ------------------------------
>
> Message: 16
> Date: Thu, 14 Apr 2005 22:31:20 -0700
> From: Jim Kusznir <jim at kusznir.net>
> Subject: [mythtv-users] XvMC on a nVidia MX440
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID: <425F51A8.6080705 at kusznir.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi all:
>
> When I set my myth system up a couple months ago, I initially had a lot
> of stuttering on video playback. I asked on the irc channel, and they
> helped me trace it down to XvMC; once I disabled it, my stutters went away.
>
> I've seen a lot of traffic in the last few days about the joys of XvMC
> and been seeing loades in excess of 2.4 on my myth system, so I'm
> attempting to reinvestagate using it.
>
> I'm using an nVidia MX440 (AGP) with kernel 2.6.9 and nVidia drivers
> 6111. If I recall correctly, I ended up having to downgrade to nvidia
> 6111 due to 6629 (or whatever was the latest release) not working with
> MX440s, and that forced me to kernel 2.6.9, as 6111 wouldn't compile
> cleanly against newer kernels. I also seem to recall the helpful fokes
> on irc letting me know that 6111 and MX440 don't play well with XvMC.
>
> So...Is the above paragraph correct? Does anyone have any suggestions
> as to how to fix this? I'm a bit hesitant to do much tinkering without
> prior knowledge, as this is my production box and its getting pretty
> heavy use (from family members -- I practically have to get up in the
> middle of the night to get time on it).
>
> Does anyone have any suggestions for me?
>
> Thanks again for all the wonderful work!
>
> --Jim
>
> ------------------------------
>
> Message: 17
> Date: Thu, 14 Apr 2005 23:21:52 -0700
> From: leith <techie at eleith.com>
> Subject: [mythtv-users] commercial flagging at set times
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID: <425F5D80.6090000 at eleith.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> could I modify mythcommflag to only run say at 3 in the morning, rather
> then just after the program is finished recording?
>
> ------------------------------
>
> Message: 18
> Date: Fri, 15 Apr 2005 14:25:47 +0800
> From: Nathan Manzi <plasma at synaptik.com.au>
> Subject: Re: [mythtv-users] DVICO Fusion DVB, Volume Control and an
> Epia MII
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID: <425F5E6B.1090505 at synaptik.com.au>
> Content-Type: text/plain; charset="iso-8859-1"
>
> In mythfrontend, go to Setup->General and try changing the channel myth
> controls in the mixer (Like from PCM to Master, or the other way around).
>
> - Nathan Manzi
>
> Michael Carmody wrote:
>
> >And amazingly it is working really well... on slackware...in Australia even...
> >
> >Using release 0.17, xorg 6.8.1 recompiled from CVS, unichrome, xvmc/vld and tv
> >out on the epia board. The remote is even working...
> >
> >Except for the fact that the volume control seems to have no effect whatsoever
> >on the actual volume.
> >
> >I can move it form 0 to 100 and the volume stays the same. If I bring up
> >alsamixer in the console I can manipulate the master volume their quite
> >easily. Why is Myth unable to manipulate volume ?
> >
> >No pertinent error messages seem to be appearing.
> >
> >Any clues anyone ?
> >
> >-Michael Carmody
> >
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >mythtv-users mailing list
> >mythtv-users at mythtv.org
> >http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> >
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 256 bytes
> Desc: OpenPGP digital signature
> Url : http://mythtv.org/pipermail/mythtv-users/attachments/20050415/0f238018/signature-0001.pgp
>
> ------------------------------
>
> Message: 19
> Date: Fri, 15 Apr 2005 06:47:02 -0000
> From: "Risto Treksler" <risto at elkhornbanff.ca>
> Subject: Re: [mythtv-users] commercial flagging at set times
> To: "Discussion about mythtv" <mythtv-users at mythtv.org>
> Message-ID: <200504150647.j3F6l2pE009173 at os7.megawebservers.com>
>
> leith <techie at eleith.com> said:
>
> > could I modify mythcommflag to only run say at 3 in the morning, rather
> > then just after the program is finished recording?
> >
>
> If no command line arguments are specified to mythcommflag,
> all unflagged shows will be flagged.
>
> disable automatic commercial flagging for each each show
> and
> do a "crontab -e" and add:
>
> 03 3 * * * /usr/bin/mythcommflag
>
> ------------------------------
>
> Message: 20
> Date: Fri, 15 Apr 2005 08:05:39 +0100
> From: David <myth at dgreaves.com>
> Subject: Re: [mythtv-users] MythMusic playback speed too fast
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID: <425F67C3.6000309 at dgreaves.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Matthew Phillips wrote:
>
> > I'm sure there's a much better way to do this in general, in
> > particular by using the advice at
> > http://www.mythtv.info/moin.cgi/DigitalSoundHowTo and adapting it from
> > the nforce example to the VIA 8236 chipset on my board.
> >
> > Does anyone already have such a beast for the VIA?
>
> It's identical - the comments that imply it's nvidia specific need removing
>
> David
>
> ------------------------------
>
> Message: 21
> Date: Fri, 15 Apr 2005 03:12:58 -0400 (EDT)
> From: "Chris Pinkham" <cpinkham at bc2va.org>
> Subject: Re: [mythtv-users] commercial flagging at set times
> To: mythtv-users at mythtv.org
> Message-ID: <200504150712.j3F7CwnF020472 at panther.bc2va.org>
> Content-Type: text/plain; charset=us-ascii
>
> > leith <techie at eleith.com> said:
> >
> > > could I modify mythcommflag to only run say at 3 in the morning, rather
> > > then just after the program is finished recording?
> > >
> >
> > If no command line arguments are specified to mythcommflag,
> > all unflagged shows will be flagged.
> >
> > disable automatic commercial flagging for each each show
> > and
> > do a "crontab -e" and add:
> >
> > 03 3 * * * /usr/bin/mythcommflag
>
> Even better in current CVS (and 0.18 when it is released) is the
> ability to set a time window for the JobQueue to run new jobs. So if
> you only want commercial flagging jobs to start running from 3am-9am,
> you can do so. The jobs will just queue up until 3am and then get
> run as they normally would by the JobQueue.
>
> --
> Chris
>
> ------------------------------
>
> Message: 22
> Date: Fri, 15 Apr 2005 00:13:02 -0700
> From: Jomama <tirebiter at gmail.com>
> Subject: Re: [mythtv-users] Commercial Flagging Idea - Distributed
> Commercial Flagging (long)
> To: Christopher David Petersen <christopher.david.petersen at gmail.com>,
> Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID: <e8b547830504150013716856fd at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I will be glad to help out with this very daring pilot program.
>
> On 4/14/05, Christopher David Petersen
> <christopher.david.petersen at gmail.com> wrote:
> > I'm starting this thread so I don't pollute the discussion of fingerprinting
> > for commercial flagging (which is a brilliant, but separate idea).
> >
> > This thread is meant to discuss that idea of distributed commercial flagging
> > (DCF) via existing algorithms to reduce load and increase accuracy.
> >
> > In brief, here's the basic idea:
> >
> > 1) Collect commercial flagging information from participating users at a
> > central server (hopefully, this isn't a DMCA violation).
> > 2) Analyze the data to determine groups of users who have performed
> > duplicate work.
> > 3) Analyze the data to predict groups of users who will be performing
> > duplicate work.
> > 4) Distribute the future duplicate work among the users to reduce each users
> > individual load.
> >
> >
> > Here's an example using _Lost_ and _Alias_ (chosen for their short names):
> >
> > Givens:
> > - 23 users with Comcast Analog Basic Cable service in Portland, OR record
> > and flag new episodes of _Lost_ and _Alias_ each week.
> > - These users use a variety of commercial flagging methods.
> > - The machines have a variety of available CPU power.
> >
> > Scenario:
> > - 23 users submit data to the DCF server via a secured and anonymous
> > interface. This data includes, which shows they flagged and the start and
> > end times of each commercial segment. All times are synchronized, to the DCF
> > server's highly-accurate clock (more on this later).
> >
> > - After submitting each show's data, the DCF server indicates to the client
> > whether the client can join a "partnership".
> >
> > - "Partnerships" are created when the DCF server determines that 2 or more
> > users are performing (and will perform) duplicate work (with similar output)
> > for 1 or more shows.
> >
> > - 10 users are invited to join the new partnership for new episodes of
> > _Lost_ and _Alias_ on Comcast Analog Basic Cable, Portland, OR. These ten
> > users are invited because they're machines are of similar power (i.e.
> > commercial flagging occurs after a similar delay and in a similar amount of
> > time). These users are now "Partners" within the "Partnership".
> >
> > - At first, none of the partners are "trusted" or have earned any "credits"
> > within the partnership. As partners submit more data they earn more credits.
> > The exact amount they earn per submission is weighted by how much they are
> > trusted (their "fidelity" factor") and the accuracy of the submitted data
> > (how similar it is to other data). Once partners have earned enough credits,
> > they can "purchase" data from the partnership.
> >
> > - After N weeks, only 7 users have earned enough credits to share data.
> >
> > - 3 partners are selected to flag next week's episode of _Lost_.
> >
> > - 4 partners are selected to flag next week's episode of _Alias_.
> >
> > - Of the 3 partners selected to flag _Lost_, all do so and submit their
> > data.
> >
> > - Of the 4 partners selected to flag _Alias_, only 3 do so and submit their
> > data. The 1 user who did not submit data has lessened his "fidelity" factor.
> >
> > - The 6 partners who submitted data, earn credits and increase their
> > fidelity factor.
> >
> > - The 3 partners who *do not* have _Lost_ flag data spend credits to receive
> > this data (at a discounted cost, because of their increased fidelity).
> >
> > - The 3 partners who *do not* have _Alias_ flag data spend credits to
> > receive this data (again, at the discount cost).
> >
> > - The flag data is not perfect: clocks, settings, reception, etc. vary. The
> > partners use the "purchased" flag data to limit their own commercial
> > flagging to those suspect times within the shows (with perhaps a 1 minute
> > margin before and after). The results of these "verification" flag jobs are
> > submitted back to the server.
> >
> > Summary:
> > So, now 7 users have formed a partnership to share the load of flagging
> > _Alias_ and _Lost_.
> > 6 of them are significantly reduced their flagging load for these two shows.
> > 1 partner needs to regain the trust of the partnership by submitting data in
> > a timely manner.
> >
> > One can easily imagine a greatly expanded model, where a particular user
> > could belong to dozens of partnerships. Each partnership could have hundreds
> > of users, and dozens of shows. As a result of participating in partnerships,
> > the user may one be required to flag a few shows (in their entirety) each
> > week.
> >
> > Benefits:
> > - Reduced commercial flagging for individual partners.
> > - Increased accuracy of commercial flagging (via consensus).
> > - "Leaching" is not allowed.
> > - Negative effects of poisoning are reduced through "fidelity" factors and
> > credits.
> > - New methods of commercial flagging (either local or distributed) can be
> > seamlessly incorporated.
> > - The available CPU power could be used for new extremely processor
> > intensive flagging methods.
> >
> > Drawbacks:
> > - Requires central server.
> > - Requires many participants.
> > - Requires frequent communications with the server (albeit, not much data s
> > transferred).
> > - Requires changing commercial flagging to acquire partnership data.
> > - Requires changing commercial flagging to allow for flagging just parts of
> > the show.
> > - Requires interface changes to alert users when they are about to "fail in
> > their partnership duties" by not recording and flagging a show.
> > - The central DCF server stores recording habits of users. It's anonymous,
> > but still concerning.
> > - Requires similar "content streams". Anecdotal experience (hearing the same
> > commercials over the phone with friends) make me suspect that commercial
> > *times* don't vary within the same Service Provider. Analysis of submitted
> > data will be the acid test. If they server never finds suitable
> > partnerships, then everybody's content streams must be different, and the
> > whole project is a failure.
> >
> > - If the project is successful, content providers will further vary the
> > content streams.
> >
> > Progress:
> > - I have built a local database to store the DCF data.
> > - I am building a sql script to populate the DCF database from mythconverg.
> > - I will be collecting data (via emailed output of the sql script) from
> > other users.
> >
> > - I have outlined a solution for time synchronization. Basically, partners
> > submit the machines local time with every transaction.- I am defining a
> > secure and anonymous interface for the DCF server.
> > - I am defining factors which I believe should effect the "fidelity" of data
> > submitted.
> >
> > Ideas, questions, comments, criticisms are welcome.
> >
> >
> > --
> > Christopher David Petersen
> > Member of PoORMUG http://poormug.bitbucket.com/
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> >
> >
>
> ------------------------------
>
> Message: 23
> Date: Fri, 15 Apr 2005 09:17:44 +0200
> From: Kees van Bemmel <keesvanbemmel at gmail.com>
> Subject: Re: [mythtv-users] XvMC on a nVidia MX440
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID: <25bfc7160504150017479b9ae8 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Don't know a lot about XvMC. I do know you could try nvidia driver
> 7174 (I believe those are the latest now). They work for me, even
> though 6629 didn't work at all! At least it won't pin you down to
> 2.6.9.
>
> On 4/15/05, Jim Kusznir <jim at kusznir.net> wrote:
> > Hi all:
> >
> > When I set my myth system up a couple months ago, I initially had a lot
> > of stuttering on video playback. I asked on the irc channel, and they
> > helped me trace it down to XvMC; once I disabled it, my stutters went away.
> >
> > I've seen a lot of traffic in the last few days about the joys of XvMC
> > and been seeing loades in excess of 2.4 on my myth system, so I'm
> > attempting to reinvestagate using it.
> >
> > I'm using an nVidia MX440 (AGP) with kernel 2.6.9 and nVidia drivers
> > 6111. If I recall correctly, I ended up having to downgrade to nvidia
> > 6111 due to 6629 (or whatever was the latest release) not working with
> > MX440s, and that forced me to kernel 2.6.9, as 6111 wouldn't compile
> > cleanly against newer kernels. I also seem to recall the helpful fokes
> > on irc letting me know that 6111 and MX440 don't play well with XvMC.
> >
> > So...Is the above paragraph correct? Does anyone have any suggestions
> > as to how to fix this? I'm a bit hesitant to do much tinkering without
> > prior knowledge, as this is my production box and its getting pretty
> > heavy use (from family members -- I practically have to get up in the
> > middle of the night to get time on it).
> >
> > Does anyone have any suggestions for me?
> >
> > Thanks again for all the wonderful work!
> >
> > --Jim
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
>
> ------------------------------
>
> Message: 24
> Date: Fri, 15 Apr 2005 09:25:47 +0200
> From: Ryszard <ryszard99 at gmail.com>
> Subject: Re: [mythtv-users] PVR500 in a Pundit?
> To: MagicITX <magicitx at gmail.com>, Discussion about mythtv
> <mythtv-users at mythtv.org>
> Message-ID: <9d6bc23605041500257a8b415b at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> are we talking pundit or pundit-r here, and is this a definitive yes?
> a 500 will fit in?
>
> I just had a look at teh diff between the -r and the non -r, and from
> teh asus site, they look
> pretty much the same, (beside the obvious chipset differences).
>
> I'm interested in getting a hold of a 500 (or a 150) to compliment the
> 350 in there already, but dont want to rush out and get one if it wont
> fit (obviously).
>
> On 4/15/05, MagicITX <magicitx at gmail.com> wrote:
> > On 4/14/05, Christopher David Petersen
> > <christopher.david.petersen at gmail.com> wrote:
> > >
> > >
> > >
> > > On 4/13/05, Niklas Brunlid <nbr at ticalc.org> wrote:
> > > > As I'm probably about to replace the PVR250 in my Pundit I have to decide
> > > > between a new 250, a 150 (or 150MCE or 150LP), or a 500. Has anyone used a
> > > > 500 in a Pundit (old or new)? Is it a tight fit? The 250 fits but there is
> > > > less than 1mm between the edge of the card and the metal case...
> > > >
> > > > / Niklas
> > >
> > >
> > > I also would like to know if the PVR-500 will fit into the Pundit.
> > >
> > > Interesting that your PVR-250 has 1mm clearance in your Pundit. I have to
> > > contort my Pundit case to insert the PVR-250 and the card has less that zero
> > > clearance (I'm probably stressing the PCI riser card). I wonder if the
> > > Pundit's PCI slot is in violation of the PCI mechanical spec. or the
> > > PVR-250?
> > >
> > > I find that the Pundit is nearly a perfect low-cost machine for MythTV. Its
> > > only drawbacks are:
> > > - the PCI card size problem
> > > - the lack of optical sound ports on the back
> > > - the lack of FireWire on the back
> > > - the lack of linux drivers for the 4-in-1 card reader
> > > - single IDE header, single serial header
> > >
> > > But for only $130 you get a lot of what you need for a MythTV box:
> > > - Svideo, Composite, DVI, and VGA out.
> > > - small, quite form factor
> > > - integrated CPU fan
> > > - good linux driver support (except the 4-in-1 reader)
> > > - Integrated LAN
> > > - Integrated LPT port (for useful LEDs
> > > http://poormug.bitbucket.com/node/7/15#comment-15 )
> > > - socket 478 support for Northwood processors (much lower heat)
> > >
> > >
> > > --
> > > Christopher David Petersen
> > >
> > > MythTV 0.17 (from Jarod's guide)
> > > Asus Pundit (frontend & backend)
> > > 2.4 GHz Celeron
> > > 768 MB DDR333
> > > 200 GB Maxtor HD
> > > PVR-250 w/ RS 15-2116 remote
> > >
> > > _______________________________________________
> > > mythtv-users mailing list
> > > mythtv-users at mythtv.org
> > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> > >
> > >
> > >
> >
> > The PVR500 is 135mm long (face of bracket to edge of card). The top
> > of the card is 5mm above the angle part of the bracket.
> >
> > --
> > Tim
> > www.magicitx.com
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
>
> ------------------------------
>
> Message: 25
> Date: Fri, 15 Apr 2005 09:44:28 +0200
> From: "Niklas Brunlid" <nbr at ticalc.org>
> Subject: Re: [mythtv-users] PVR500 in a Pundit?
> To: "Christopher David Petersen"
> <christopher.david.petersen at gmail.com>, "Discussion about mythtv"
> <mythtv-users at mythtv.org>
> Message-ID: <opso9jsef8e4det6 at localhost>
> Content-Type: text/plain; format=flowed; delsp=yes;
> charset=iso-8859-15
>
> On Thu, 14 Apr 2005 14:15:34 -0700, Christopher David Petersen
> <christopher.david.petersen at gmail.com> wrote:
>
> > On 4/13/05, Niklas Brunlid <nbr at ticalc.org> wrote:
> >>
> >> As I'm probably about to replace the PVR250 in my Pundit I have to
> >> decide
> >> between a new 250, a 150 (or 150MCE or 150LP), or a 500. Has anyone
> >> used a
> >> 500 in a Pundit (old or new)? Is it a tight fit? The 250 fits but there
> >> is
> >> less than 1mm between the edge of the card and the metal case...
> >>
> >> / Niklas
> >
> > I also would like to know if the PVR-500 will fit into the Pundit.
> > Interesting that your PVR-250 has 1mm clearance in your Pundit. I have
> > to
> > contort my Pundit case to insert the PVR-250 and the card has less that
> > zero
> > clearance (I'm probably stressing the PCI riser card).
>
> It could be because I have PVR350 in the lower PCI slot - maybe it pushes
> the case outwards, giving more clearance to the PVR250. :)
>
> > I wonder if the
> > Pundit's PCI slot is in violation of the PCI mechanical spec. or the
> > PVR-250?
>
> My guess would be the 250 (and the entire PVR line, except the 150LP) -
> the edge of the circuit board is way outside the end of the metal bracket!
>
> > I find that the Pundit is nearly a perfect low-cost machine for MythTV.
> > Its
> > only drawbacks are:
> > - the PCI card size problem
> > - the lack of optical sound ports on the back
> > - the lack of FireWire on the back
>
> I've never used those ports, but with the exception for DV I don't see the
> point of having them in the front. Lack of space in the back?
>
> > - the lack of linux drivers for the 4-in-1 card reader
>
> Would be nice to have.
>
> > - single IDE header, single serial header
>
> Never use the serial, but I'd very much like a SATA connector or two.
> Makes more sense in such a compact box.
>
> > But for only $130 you get a lot of what you need for a MythTV box:
> > - Svideo, Composite, DVI, and VGA out.
>
> Well, the SVideo/Composite is as good as most other GFX card TV-out
> offerings, i.e. ties to the GFX card and sucks at "real" TV out. :)
>
> > - small, quite form factor
> > - integrated CPU fan
>
> Mine gave up after less than 6 months and the new one doesn't fit the
> funnel.
>
> > - good linux driver support (except the 4-in-1 reader)
> > - Integrated LAN
> > - Integrated LPT port (for useful LEDs
>
> / Niklas
>
> ------------------------------
>
> Message: 26
> Date: Fri, 15 Apr 2005 00:45:17 -0700
> From: Chris Nelson <crnelson at gmail.com>
> Subject: Re: [mythtv-users] Setting LiveTV default channel/tuner??
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID: <c83cbbfd050415004571110ba4 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I've got a very similar issue. Anyone know how to make this work?
>
> On 4/14/05, Jim Kusznir <jim at kusznir.net> wrote:
> > hello:
> >
> > Is there any way to set which tuner LiveTV will default to (such that it
> > picks a tuner that would not necessarily be the same as what recordings
> > would choose)?
> >
> > I have digital cable and a single set-top box connected to a PVR-250.
> > I've also added a PVR-500 with a direct RF feed (which has access only
> > to the analog channels). I've set my tuner prioritys with the 500's
> > tuners being higher priority than the 250. I've also configured the
> > video sources so myth knows and understands that the 500's have a subset
> > of the channels the 250 gets.
> >
> > So when I schedule a recording on an analog channel (as 95% of my
> > recordings are), it uses a 500 tuner if available; using the 250 only if
> > both tuners on the 500 are busy. This is good. If I schedule a
> > recording on a digital channel, myth automatically schedules it on the
> > 250, which is also good.
> >
> > Now, unfortunately, liveTV defaults to one of the 500's most of the
> > time. I have set a "select a tuner less likely to interfeer with
> > recordings" option, which usually results in giving me the second tuner
> > on the 500.
> >
> > Most of the users in the house often use liveTV, and like to browse all
> > the channels, including the digital ones. Right now, I've had to teach
> > them to use the "y" command to cycle through the tuners until they get
> > the right one. This actually has a fairly high failure rate (the user
> > education end of it), and has been leading to considerable frustration
> > with using Myth here.
> >
> > If I could only make LiveTV choose the 250's tuner by default (which is
> > available most of the time because nearly all our recording occurs on
> > the 500), this would fix a lot of our user problems.
> >
> > Is there some way to set this? Perhaps I need to edit the database
> > directly? Any suggestions?
> >
> > Thanks!
> >
> > --Jim
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
>
> ------------------------------
>
> Message: 27
> Date: Fri, 15 Apr 2005 03:50:29 -0400
> From: Isaac Richards <ijr at case.edu>
> Subject: [mythtv-users] 0.18's available
> To: mythtv-users at mythtv.org
> Message-ID: <200504150350.29946.ijr at case.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> Get yourself to the website if you want it.
>
> Isaac
>
> ------------------------------
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
> End of mythtv-users Digest, Vol 27, Issue 87
> ********************************************
>
More information about the mythtv-users
mailing list