[mythtv-users] New ATI Tuner that supports Cablecard
If someone already posted this, sorry for the dupe. I saw this at work and I don't have access to my home email and I wanted to post this asap. This looks very sweet and hopefully won't be too difficult for some decent developers to get working with Linux and Myth. (However, I suspect there will be some nasty DRM somewhere) http://www.anandtech.com/tradeshows/showdoc.aspx?i=2662 ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] USB on the cable box
--- Jeff Simpson <[EMAIL PROTECTED]> wrote: > > > > > > So, presumably, you want to hook up a > usb-to-serial cable from your PC > > serial port to the usb port of the cable box. The > issue is that the > > cable box expects to be the usb host and so does a > PC, whereas the > > keyboard is the usb "client". I'm not sure how a > usb-to-serial adapter > > presents itself to another usb host, but if it's > only designed to work > > with usb clients, I'd guess that a driver would > have to be written to > > emulate a usb client through the serial port, if > it's even possible. > > > The PC expects to be a usb host if you plug a USB > device into it. a > Usb->serial adapter will only look like a usb device > on the usb side - > the serial side will look like nothing but a serial > cable. If the cable box > is > designed to be the usb host and will take incoming > commands from a > usb->serial > adapter, it sounds like it will work (I will be > trying the same thing on my > satellite > STB once I get my usb->serial adapter in the mail). > > That would be ideal, and would certainly be an > inexpensive option. The > > only box I came across that actually says it > emulates a usb kbd from > > either usb or serial connection to the PC host is > a couple hundred > > bucks. > > > > I'll look into how it works, but a "port" > converter may just connect the > > wires correctly to allow communications. > > > yeah, if the port converter works, that's def the > way to go. It's around $9 > or $10 for > one of those converters if you shop around online. > > ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > See http://www.gossamer-threads.com/lists/mythtv/users/79805?search_string=protocol%20converter;#79805 The problem is converting to USB keyboard signals. What do you convert "45" to when you want to change to channel 45? It is not as simple as just echoing "45" to the serial port. You will still need something to convert the serial port output to USB keyboard signals. So either a hardware convertor or some software to convert input to USB Keyboard signals will be needed. __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
RE: [mythtv-users] Need suggestion for Frontend only fanless solution
--- MythTV <[EMAIL PROTECTED]> wrote: > Do you need the Photobridge HD (HD1500) or is the > HD1000 OK? The main > difference I see is the HD1500 has 128MB RAM and the > HD1000 is 64MB, but not > sure if that is much a limitation. > > Thanks, > Todd > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Chris Gackstatter > Sent: Thursday, October 06, 2005 2:38 PM > To: 'Discussion about mythtv' > Subject: RE: [mythtv-users] Need suggestion for > Frontend only fanless > solution > > I run MythRoku on a Roku Photobridge HD. What is > there is easy to install > and works great. MythRoku can use some more work > but it is the only HiDef > solution out there. Right now MythRoku only plays > recorded shows and you > can pause live TV. You will need a front end on > another machine to schedule > recordings and you can not rewind or FF live TV. > This will come with Time > and more people working on the port. > > I will say this I implemented MythTV because of the > Roku. I did not want > the noisy box in my media room. > > > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Brad Fuller > Sent: Thursday, October 06, 2005 11:01 AM > To: Discussion about mythtv > Subject: Re: [mythtv-users] Need suggestion for > Frontend only fanless > solution > > Todd Ignasiak wrote: > > > One frontend I've been looking into is the "Roku > Photobridge HD" ( > > > http://www.rokulabs.com/products/photobridge/index.php > ). It's a > > media player for HDTV's. It is Linux based, and > has a hardware MPEG2 > > decoder onboard. They encourage open source > developement on their > > platform, and someone has ported the MythTV > frontend. > > > > He has made some big improvements lately, and I'm > thinking of picking > > up the Roku box to give it a try. Check out > "mythroku" at > > http://mythroku.blogspot.com/ > > Do you know what mpeg2 decoder chip they use? I > didn't see the info at the > site. > ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > > > ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > With live TV, how do you change channels? The remote appears to be lacking numbers and other functions. Otherwise, this device looks sweet used in conjunction with MythTV. I am tempted to sell my frontend and pick up one of these bad boys. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
t; On Mon, 14 Mar 2005 19:01:33 -0700, Darren > Richards > > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > > My USB MCE remote just came in the mail > today. I figured if there's a > > > > > > > link to it from Jarod's guide, I should > be able to get it working. > > > > > > > Imagine my dismay when I started > searching the archives and came > > > > > > > across this thread. Jim, I'm in exactly > the same boat as you. Even > > > > > > > if there was a magical fix in CVS, I've > never successfully compiled > > > > > > > anything in my life. I'm completely > dependent upon apt-get and > > > > > > > ATRPMS. > > > > > > > > > > > > > > Please, please keep us posted if you > come up with anything. I'll > > > > > > > start digging into this probably > tomorrow, and maybe I'll have some > > > > > > > luck... > > > > > > > > > > > > > > -darren > > > > > > > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 17:45:15 -0600, Jim > Oltman <[EMAIL PROTECTED]> wrote: > > > > > > > > I just looked on ATRPMs website and > there is no listing for getting > > > > > > > > the source code for the lirc drivers. > There is also no mention of > > > > > > > > exactly what "CVS version" I am using > (0.7.0pre 4 or 5 or 6 or 7 or > > > > > > > > 8). I know that I have lirc 0.7.0-45 > from ATRPMs but other than that, > > > > > > > > I have no idea. Anyone know what > version I could be running? I would > > > > > > > > LOVE to get this remote going so I > could move on to bugging the list > > > > > > > > about other problems! :-) Thanks! > > > > > > > > > > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 14:44:10 -0800 > (PST), Joe Huffner <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > Unless ATRPMS have been updated, > then the only way to > > > > > > > > > get this to work would be to compile > the drivers. My > > > > > > > > > guess is that these drivers will be > updated in the > > > > > > > > > not-too-distant-future, but exactly > when that happens > > > > > > > > > is up to the lirc maintainers. Then > the RPMS will have > > > > > > > > > to be udpated as well. > > > > > > > > > > > > > > > > > > Something you can try is to leave > your current lirc > > > > > > > > > installed. > > > > > > > > > > > > > > > > > > 1. Download the same version you > have installed. > > > > > > > > > 2. Copy the the previously attached > source code to the > > > > > > > > > appropriate place. > > > > > > > > > 3. Configure and compile source. > > > > > > > > > 4. Copy the new lirc_mceusb and > lirc_dev modules over > > > > > > > > > the existing files. (After making a > backup of the > > > > > > > > > originals of course.) > > > > > > > > > 5. Unload the modules, then load the > new modules. (Or > > > > > > > > > reboot for the easiest way.) > > > > > > > > > > > > > > > > > > About your questions concerning my > modprobe.conf and > > > > > > > > > what not. I don't have anything > currently in their > > > > > > > > > except ethernet and video. Since my > remote wasn't > > > > > > > > > working with lirc yet, there was no > reason to put > > > > > > > > > anything in there. Also, I am > running gentoo, so I > > > > > > > > > don't know the exact format of the > modprobe.conf file, > > > > > > > > > but my guess is you would just want > the module name > > > > > > > > > you would want to load. In this case > it would just be > > > > > > > > > lirc_mceusb, all the other modules > required by lirc > > > > > > > > > should be loaded. > > > > > > > > > > > > > > > > > > --- Jim Oltman <[EMAIL PROTECTED]> > wrote: > > > > > > > > > > > > > > > > > > > Since I used apt-get to install > lirc === message truncated ===> ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
Unless ATRPMS have been updated, then the only way to get this to work would be to compile the drivers. My guess is that these drivers will be updated in the not-too-distant-future, but exactly when that happens is up to the lirc maintainers. Then the RPMS will have to be udpated as well. Something you can try is to leave your current lirc installed. 1. Download the same version you have installed. 2. Copy the the previously attached source code to the appropriate place. 3. Configure and compile source. 4. Copy the new lirc_mceusb and lirc_dev modules over the existing files. (After making a backup of the originals of course.) 5. Unload the modules, then load the new modules. (Or reboot for the easiest way.) About your questions concerning my modprobe.conf and what not. I don't have anything currently in their except ethernet and video. Since my remote wasn't working with lirc yet, there was no reason to put anything in there. Also, I am running gentoo, so I don't know the exact format of the modprobe.conf file, but my guess is you would just want the module name you would want to load. In this case it would just be lirc_mceusb, all the other modules required by lirc should be loaded. --- Jim Oltman <[EMAIL PROTECTED]> wrote: > Since I used apt-get to install lirc and > mythtv-suite, I take it that > is would be EXTREMELY difficult for me to compile > this new driver into > lirc especially since I have never compiled anything > in my entire life > (except for those 2 semesters in college compiling C > code that barely > worked). As I understand it, mythtv-suite already > has the lirc-lib > included. Is there a way around all this? Does > anyone know? My > version of the mce_usb driver is listed as v0.2 but > doesn't mention > anything about this Dan Conti. Also, on ATRPMs it > looks like Axel > last updated the lirc drivers on Mar 5th 12:27 CET. > Could you tell me > how you were able to get your MCE IR receiver up and > working (assuming > I have the right driver). What did you put in your > /etc/modprobe.conf? I didn't have a /dev/lirc0 only > a /dev/lircd so > in my rc.local I put these statements in: > > ln -s /dev/lircd /dev/lirc0 > chmod 666 /dev/lirc0 > > /sbin/modprobe lirc_mceusb > /usr/sbin/lircd --device=/dev/lirc0 > --output=/dev/lircd > > Am I incorrect? Should I be doing something > different? Thanks! > > > On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman > <[EMAIL PROTECTED]> wrote: > > Since I used apt-get to install lirc and > mythtv-suite, I take it that > > is would be EXTREMELY difficult for me to compile > this new driver into > > lirc especially since I have never compiled > anything in my entire life > > (except for those 2 semesters in college compiling > C code that barely > > worked). As I understand it, mythtv-suite already > has the lirc-lib > > included. Is there a way around all this? Does > anyone know? My > > version of the mce_usb driver is listed as v0.2 > but doesn't mention > > anything about this Dan Conti. Also, on ATRPMs it > looks like Axel > > last updated the lirc drivers on Mar 5th 12:27 > CET. Could you tell me > > how you were able to get your MCE IR receiver up > and working (assuming > > I have the right driver). What did you put in > your > > /etc/modprobe.conf? I didn't have a /dev/lirc0 > only a /dev/lircd so > > in my rc.local I put these statements in: > > > > ln -s /dev/lircd /dev/lirc0 > > chmod 666 /dev/lirc0 > > > > /sbin/modprobe lirc_mceusb > > /usr/sbin/lircd --device=/dev/lirc0 > --output=/dev/lircd > > > > Am I incorrect? Should I be doing something > different? Thanks! > > > > On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe > Huffner <[EMAIL PROTECTED]> wrote: > > > Just an FYI for those of us who bought one of > the > > > updated MCE remotes and receivers. I was > checking out > > > the lirc mailing list and someone has update the > > > driver to include support. From what I can tell > the > > > update has not been updated in CVS. > > > > > > I found the info at: > > > > http://search.gmane.org/?query=mce&group=gmane.comp.hardware.lirc > > > > > > Basically what I did was overwrite the > lirc_mceusb.c > > > in the drivers/lirc_mceusb directory with the > source > > > found in the mailing liste. (I have attached the > new > > > source file.) Then went through the install > process > > > documented. I used version .7.0 of lirc. > > > > > > Please note, from what I have read and > experienced, &
Re: [mythtv-users] Re: USB MCE IR Receiver
Just an FYI for those of us who bought one of the updated MCE remotes and receivers. I was checking out the lirc mailing list and someone has update the driver to include support. From what I can tell the update has not been updated in CVS. I found the info at: http://search.gmane.org/?query=mce&group=gmane.comp.hardware.lirc Basically what I did was overwrite the lirc_mceusb.c in the drivers/lirc_mceusb directory with the source found in the mailing liste. (I have attached the new source file.) Then went through the install process documented. I used version .7.0 of lirc. Please note, from what I have read and experienced, there are some initialization problems. What seemed to "fix it" was unplugging the receiver and plugging it back in, until I no longer got an error message stating the device did not initialize. You can check this by running "tail -f /var/log/messages". Also, I read that running kernel 2.6.11 seemed to fix the initialization problem. However I cannot confirm this as I am running Gentoo Dev Kernel 2.6.9-r9. Another problem I am having is that I am getting non-stop error messages stating: "usb 2-2: bulk timeout on ep1in" In fact, I was getting about 4 of those messages per second. If/when I get time I am planning to upgrade to 2.6.11 to see if this fixes the issue. -joe --- Jim Oltman <[EMAIL PROTECTED]> wrote: > After deleting the section in my rc.local about the > mknod /dev/lirc0 c > 61 0 and replacing it with: > > ln -s /dev/lircd /dev/lirc0 > > I am no longer getting errors from lircd in the > /var/log/messages. > IRW runs but I am not seeing anything when I press > buttons on my > Hauppauge remote (it has also been setup in the > correct lircrc files). > When I run irrecord I am getting errors about lircd > not being > started. I am going to try commenting out the other > section in > rc.local pertaining to MCEUSB and see what happens. > > > On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman > <[EMAIL PROTECTED]> wrote: > > Here is where I am at so far. In my > /etc/rc.d/rc.local I made these changes... > > > > #!/bin/sh > > # > > # This script will be executed *after* all the > other init scripts. > > # You can put your own initialization stuff in > here if you don't > > # want to do the full Sys V style init stuff. > > > > touch /var/lock/subsys/local > > mknod /dev/lirc0 c 61 0 -I added this > line in hopes it > > would attach to a line in my modprobe > > > > /usr/X11R6/bin/xset -dpms > > /usr/X11R6/bin/xset s off > > /usr/bin/mtd --daemon > > > > # I added these next two lines > > > > /sbin/modprobe lirc_mceusb > > /usr/sbin/lircd --device=/dev/lirc0 > --output=/dev/lircd > > > > In my /etc/modprobe.conf I have added this line: > > > > alias char-major-61 lirc_mceusb > > > > After implementing these changes, I can do a cat > /var/log/messages and > > see what I showed you before about the driver > being loaded for the USB > > Microsoft IR Transceiver. But I also get this > listed: > > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > accepted new client on > > /dev/lircd > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > could not open /dev/lirc0 > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > default_init(): No such device > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > caught signal > > > > I am however getting errors on boot in the > Show/Hide Details window. > > Where can I view the errors that it is showing me? > They disappear to > > quickly to read. I am pretty sure the info I want > to see (about the > > errors on boot in Show/Hide window) is not listed > in > > /var/log/messages. > > > > On Sun, 13 Mar 2005 18:38:09 -0600, Ron Johnson > <[EMAIL PROTECTED]> wrote: > > > On Sun, 2005-03-13 at 17:58 -0600, Jim Oltman > wrote: > > > > What I meant in that statement is that I got > it to recognize the > > > > receiver in the /var/log/messages but it is > still not working. > > > > > > Yes, but *how* did you get "it" to recognize the > receiver? > > > > > > P.S. - Please do not erase the whole text of the > email you are > > > replying to. That makes it quite difficult to > follow the thread. > > > > > > -- > > > > - > > > Ron Johnson, Jr. > > > Jefferson, LA USA > > > PGP Key ID 8834C06B I prefer encrypted mail. > > > > > > Legality/morality of using open wireless points: > > > "If I leave my door unlocked are you going to > come into my house > > > in the middle of the night because you need to > use the restroom? > > > I pay a fixed rate for water. It's cold water so > there is no > > > electricity usage. No financial loss. I have 2.5 > bathrooms, so no > > > loss of usage on my end. Is this OK? Please, try > this and we'll > > > see if it's OK." > > > > http://www.warchalking.org/comments/2002/9/22/223831/236/135 > > > > > > > > > ___ > > > mythtv-users mailing list > > > mythtv-users@mythtv.org > > > > http:/
Re: [mythtv-users] Firewire success stories?
I posted the links earlier in this discussion, but here they are again: For the overall web page: http://www.fcc.gov/dtv/ Scroll down to: "10/9/03, 9/10/03 FCC Eases Digital TV Transition for Consumers." The actual PDF is: http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-225A1.pdf I have talked to my cable company (Time Warner, Columbus) and supposedly someone will be dropping off a couple of boxes with firewire ports next week. However, my guess they are confusing HDMI or SATA ports with the firewire. I want to give them the chance to actually drop off the write equipment. What bugs me about this whole thing is that I am willing to pay for additional channels. I want to pay for the cable boxes if they have firewire support. I am almost positive the reason they don't offer the boxes with firewire is to force you to use their DVR. -joe --- Lane Schwartz <[EMAIL PROTECTED]> wrote: > On Fri, 18 Feb 2005 00:43:01 -0800, Jarod Wilson > <[EMAIL PROTECTED]> wrote: > > On Thursday 17 February 2005 18:25, David Madsen > wrote: > > > > as I understand it, the firewire ports on > these boxes don't output HD > > > > - the FCC requires that everything they output > is downgraded to 480p > > > > > > This is incorrect. My box definately outputs HD > streams for the HD > > > channels, both 720p and 1080i depending on the > station. > > > > I'll see what I get next week. I called Comcast > today and requested a box that > > actually has a firewire port. The person I talked > to had no clue what > > firewire or ieee 1394 was, but was thankful when I > pointed her to the FCC > > docs that say they have to provide a box with > firewire output if a customer > > requests it. Apparently, not many are... > > > > It'll be interesting to see the differences in > what I can get from the cable > > box's firewire port and what I can get hooking the > Air2PC card I just ordered > > to the same cable feed... > > Jarod, > > Could you point me to those FCC docs? :) > > Thanks, > Lane > > > -- > Meetup with other Myth users! > http://mythtv.info/moin.cgi/MUG > > ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Firewire success stories?
The URL is http://www.fcc.gov/dtv/ Scroll down the page to the year 2003, 10/9/03. The title is "FCC Eases Digital TV Transition for Consumers." The PDF is at: http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-225A1.pdf --- "Michael J. Lynch" <[EMAIL PROTECTED]> wrote: > Joe Huffner wrote: > > >My problem is that I can't seem to get my cable > >company (Time Warner Columbus, OH) to provide me a > >cable box with firewire outputs. They use the SA > >3250s, which those are listed as an option. I have > >gone to the FCC's website and printed out the > >appropriate documentation stating that if I request > a > >box with firewire, then they must provide one. > > > Can you post the URL to the appropriate stuff on the > FCC site > for this. Thanks. > > -- > Michael J. Lynch > > What if the hokey pokey IS what it's all about -- > author unknown > > > ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Firewire success stories?
My problem is that I can't seem to get my cable company (Time Warner Columbus, OH) to provide me a cable box with firewire outputs. They use the SA 3250s, which those are listed as an option. I have gone to the FCC's website and printed out the appropriate documentation stating that if I request a box with firewire, then they must provide one. I will be heading to their local office with the appropriate sections in hand. Has anyone else ran into this problem? I am prepared to file complaints with the FCC and the State's Consumer Protection if I have to, but I would rather just get the fscking boxes with firewire enabled. -joe --- Tom Dombrosky <[EMAIL PROTECTED]> wrote: > That ebuild worked great for me. You should try to > submit it for > inclusion in portage. > > Tom > > ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > __ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250 ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
