Re: [mythtv-users] New version of MythTV (0.17)
Andy Long wrote: The mythtv.org site has a posting showing a new release coming out in a week or so. Next, a cheerleading squad hops in singing: Myth Tee-Vee! Myth Tee-Vee! We love thee! We love thee! Ev-en Windows Ex-Pee Em-Cee-Ee! Don't make as much versions as we! Ooooh! MythTV! ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] EPG
Mattia Martinello wrote: is there a way to get EPG information about programs shown in the TV screen in Mythtv? Why don't you have a look at the keys.txt file in the myth source directory? ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] lirc pause button
skeeterskip wrote: I just got Mythtv setup with my remote and I've noticed a few things about certain buttons. I can't seem to get Pause to work while playing a video. Command looks like that below. begin prog = irxevent button = pause config = Key P CurrentWindow end Why would you need irexevent to control myth? Myth supports lirc natively (see ~/.mythtv/lircrc): begin prog = mythtv button = pause config = P end Also, I've noticed that when I browse around clicking left and right on Streamzap remote, it will skip sometimes from Watch Videos to Listen to Music and skip right owver Watch Recordings. This could be a problem with the repetition rate of the remote button. Add a repeat = x (where x is a positive integer) line to tell lirc it should only use every x'th repetition, as such begin prog = mythtv button = pause repeat = 3 config = P end ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] no one on here uses dial up then?
Aaron Aguilar wrote: My dream of setting up a MythTV box seems to have been shattered now. Unless of course someone else has successfully used dial up in their setup. Please let me know if you have successfully used dial up. My TiVo box is using it, but I know it is different. I have made two dial-up myth setups for other people (I have cable). For security reasons, they had to manually open the connection and run mythfilldatabase. But I don't see why you cannot make it dial in and run mythfilldatabase automatically. I guess this script should work after you put it in the cron(or a script similar to it): #!/bin/sh wvdial wait 30 mythfilldatabase kill pidof wwvdial ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MythLED Picture
David George wrote: I thought about adding a thread to the backend to do this, but figured it would be better to have a separate processes that asks the backend for the info. First by doing it this way we can have multiple LED boxes (one for each frontend). Also I wanted to have the ability for the box to detect if the backend is ever unavailable. I have not a really clear picture about how the front- and backends communicate, but if we use the TCP/IP connection the backend would have the unavailability option already (asynchronous socket error), plus it will solve most of the protocol questions. You could also choose to run a secundary protocol on onother port. Yust my 0.02 EUR. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Will a PVR-[23]50 help HD playback?
Brandon Beattie wrote: On Mon, Jan 17, 2005 at 07:50:22AM -0700, Comments wrote: Anyone tried this? Is it possible? Yes, many of us have. A pvr-x50 will Not decode HD. The PVR is very picky what format it decodes. Transcoding arbitrary video sources to the PVR acceptable format is still somewhat of a holy grail.Everybody knows it should be possible, but nobody has found it yet.Boy, I wish I knew more about video formats... ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] MythDVD ogle_ir
I was trying out ogle to see if it better suited my DVD needs than MPlayer. Installing ogle was no problem after I found the RPM's, but instaling the LIRC support (http://rosko.net/ogle/ogle_ir/) is basically aetch-ell-double-hockeysticks. I even can't get it through configure... I use Suse 9.0, but it also accepts the redhat PRM's. Any suggestions? Are there rpm's for ogle_ir? ___ After several tries solves I got stuck here: suse-linux/bin/ld: cannot find -lgtk collect2: ld returned 1 exit status the correct path (/opt/gnome/bin) is in /etc/ld.so.conf and libgtk.so is located there, so I have no idea why it can't find it. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] PVR350 Audio problems . . sigh
Lischka wrote: I bought a PVR-350 and tried it out on my main desktop setting up Knoppmyth on a partition on an old 40Gb disk that was lying around). This went reasonably well although I had a lot of trouble setting up the UK tv grabber. After many abortive attempts, the Knoppmyth hard disk failed, so I tried again under Gentoo (my main distro). Again I got pretty close to where I wanted to be, but a different set of problems (2.6.4 and lirc didnt seem to be compatible). Anyway, I got some TV shows successfully recorded, and even got myth through TV-Out onto the TV screen. Has anyone got any ideas what to try next? Any more diagnostic info to give me a clue as to what is wrong? Oh yes, I tried compiling the latest ivtv-0.3.2a drivers but it made no difference. With the 0.1 versions, I had intermittently sound and no sound with my Myth box. I used this hack which worked for me: /usr/local/bin/test_ioctl -v input=7,output=1 /usr/local/bin/test_ioctl -v input=2,output=2 The 0.3 versions are experimental (that means unstable) at the moment. Better try 0.2.0rc3c. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] X output to both TV and monitor
Carlos Fernandez Sanz wrote: Hi, Is it possible to use a PVR-350 in X to output to TV and, at the same time, use a regular video card (an Nvidia FX 5200 to be exact) to output to monitor? I'd like to use both at the same time... would be really useful to me. Configuring myth using the TV can't be good for the eyes... How about this idea: I have a second computer running win98. Useing the X forwarding of my myth box I can configure it on Cygwin/X (with ssh) on the windows box. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] PVR350 - snow
Ah! the Philips FM1216 ME MK3. Well actually it can use nearly all the PAL flauvours (We have PAL-G and I had it in a Win98 box and it worked beautifully). I have 1 2 and I have the same problem. I hear a lot of stories by other people who have trouble with it too. May I ask, what kernel distro are you using? You could try and apply Chris's 'new tuners' kernel path (kernel recompile needed) even though Chris's README says it's not needed, URL: http://205.209.168.201/~ckennedy/ivtv/new_tuners/ I didn't have any succes, if you had (or hadn't) please tell me. sigurdne wrote: Hi I have a PVR350 with mandrake 10.1 I have followed Maiku's Setting up MythTV under Mandrake 10.1 Guide, and everything seems to start fine - exept that I am only receiving static. I have tested the card with windows - and all channels appear fine in windows - but only as static (same channels) in mythtv. I live in a PAL(B/G) country Norway - but it seems from the log that PAL(D/K) is selected. I initialise the drivers as a start-script '/usr/local/bin/start-ivtv' (as proposed in the guide) #!/bin/bash /sbin/modprobe i2c-core /sbin/modprobe i2c-algo-bit /sbin/modprobe msp3400 simple=1 /sbin/modprobe videodev /sbin/modprobe saa7115 /sbin/modprobe ivtv ivtv_std=2 tda9887=0 /sbin/modprobe ivtv-fb /sbin/modprobe lirc_i2c /usr/local/sbin/lircd -d /dev/lirc0 --permission=666 ln -s /dev/lirc0 /dev/lirc /etc/init.d/mythbackend start Dec 20 21:59:31 localhost kernel: ivtv: START INIT IVTV Dec 20 21:59:31 localhost kernel: ivtv: version 0.2.0 (rc3b) loading Dec 20 21:59:31 localhost kernel: ivtv: Linux version: 2.6.8.1-10mdk 686 gcc-3.4 Dec 20 21:59:31 localhost kernel: ivtv: In case of problems please include the debug info Dec 20 21:59:31 localhost kernel: ivtv: between the START INIT IVTV and END INIT IVTV lines when Dec 20 21:59:31 localhost kernel: ivtv: mailing the ivtv-devel mailinglist. Dec 20 21:59:31 localhost kernel: ivtv: Autodetected WinTV PVR 350 card Dec 20 21:59:31 localhost kernel: ivtv: Found an iTVC15 based chip Dec 20 21:59:31 localhost kernel: ivtv: Unreasonably low latency timer, setting to 64 (was 32) Dec 20 21:59:31 localhost kernel: ivtv: VIA PCI device: 0x3205 vendor: 0x1106 Dec 20 21:59:31 localhost kernel: msp34xx: ivtv version Dec 20 21:59:31 localhost kernel: msp34xx: init: chip=MSP3418W-B3, has NICAM support, simple (D) mode, simpler (G) no-thread mode Dec 20 21:59:31 localhost kernel: msp34xx: $Id$ compiled on: Dec 19 2004 21:16:16 Dec 20 21:59:31 localhost kernel: ivtv: i2c attach [client=MSP3418W-B3,ok] Dec 20 21:59:32 localhost kernel: saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005) Dec 20 21:59:32 localhost kernel: saa7115: detecting saa7115 client on address 0x42 Dec 20 21:59:32 localhost kernel: saa7115: writing init values Dec 20 21:59:32 localhost kernel: ivtv: i2c attach [client=saa7115[0],ok] Dec 20 21:59:32 localhost kernel: saa7115: status: (1E) 0x40, (1F) 0xc0 Dec 20 21:59:32 localhost kernel: tveeprom: Ignoring new-style parameters in presence of obsolete ones Dec 20 21:59:32 localhost kernel: tveeprom: Hauppauge: model = 48139, rev = K257, serial# = 7596580 Dec 20 21:59:32 localhost kernel: tveeprom: tuner = Philips FM1216 ME MK3 (idx = 57, type = 38) Dec 20 21:59:32 localhost kernel: tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) Dec 20 21:59:32 localhost kernel: tveeprom: audio_processor = CS5331 (type = 9) Dec 20 21:59:32 localhost kernel: ivtv: i2c attach [client=tveeprom[0],ok] Dec 20 21:59:32 localhost kernel: ivtv: Tuner Type 38, Tuner formats 0x00400e17, Radio: yes, Model 0x00ad2557, Revision 0x0001 Dec 20 21:59:32 localhost kernel: ivtv: Radio detected Dec 20 21:59:32 localhost kernel: tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 Dec 20 21:59:32 localhost kernel: ivtv: i2c attach [client=(tuner unset),ok] Dec 20 21:59:32 localhost kernel: saa7127: Ignoring new-style parameters in presence of obsolete ones Dec 20 21:59:32 localhost kernel: saa7127: video encoder driver version V 0.3 loaded Dec 20 21:59:32 localhost kernel: saa7127: Selecting NTSC video Standard Dec 20 21:59:32 localhost kernel: saa7127: Selecting S-Video+Composite Dec 20 21:59:32 localhost kernel: saa7127: Turn WSS off Dec 20 21:59:32 localhost kernel: saa7127: Widescreen Mode 4:3 Full Format Dec 20 21:59:32 localhost kernel: saa7127: Selecting Normal Encoder Input Dec 20 21:59:32 localhost kernel: saa7127: Enable Video Output Dec 20 21:59:32 localhost kernel: ivtv: i2c attach [client=saa7127[0],ok] Dec 20 21:59:32 localhost kernel: tda9885/6/7: chip found @ 0x86 Dec 20 21:59:32 localhost kernel: ivtv: i2c attach [client=tda9887,ok] Dec 20 21:59:32 localhost dhclient: sit0: unknown hardware address type 776 Dec 20 21:59:33 localhost kernel: ivtv: Encoder revision: 0x02050032 Dec 20 21:59:33 localhost kernel: ivtv: Encoder Firmware is buggy, use version 0x02040011 Dec 20 21:59:33 localhost kernel:
Re: [mythtv-users] PVR350 - snow
sigurdne wrote: On hauppauges support, there is a file for x250: pvr250_22_inf.zip - may be this one? http://www.hauppauge.com/pages/support/support_pvr250-350.html#app Result: ivtv: Encoder revision: 0x02050032 ivtv: Encoder Firmware is buggy, use version 0x02040011 ivtv: Decoder revision: 0x02020023 The playback is: *Singing* let it snow, let it snow, let it snow... *Singing* ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] PVR350 - snow
Sigurd Nes wrote: I cant get it to work it might be the fact that I can't get the add below to load from modprobe.conf in mandrake 10.1 What is your configuration I might consider changing distribution if that is a solution. Sigurd I'm using Suse 9.0. If I may be so frank: Use another disro (I hear knoppmyth is good). Suse is like a lady, you have to know her quirks. ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Static on
Rob Rosenfeld wrote: Seems real obvious, but how do you know that -p 4 is the right ivtvctl argument to pass for your input? I gather you've tried all the other -p values? No I don't, but this is the only one who gives me static i.s.o. a black screen. ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] Static on
I'm really out of options. So I am asking for some help. If you think I'm whining please say so. I've got a PVR350 which so far has given my nothing be static (I tried both ivtv0.1.9a, from zzz, and 0.2.0rc3b from Chris). When I change channels The pattern in the static doesn't change so I believe It's not doing anything. In my Win98 box the card works ok. I've checked the modules.conf, I've upgraded the firmware (pvr_1.18.21.22266_inf.zip), I've set the right values though ivtvctl (-f width=720,height=576, -p 4, -u 0xff), tried the new tuners patch. All with no effect.And oh, and funnily enough in ptune-ui.pl the frequency table (europe_west) is not in the table (weird). Any ideas? Here's a list of my data and stuff: From tveeprom: ivtv: i2c attach [client=MSP3418W-B3,ok] tveeprom: Hauppauge: model = 48139, rev = K257, serial# = 7597097 tveeprom: tuner = Philips FM1216 ME MK3 (idx = 57, type = 38) tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) audio_processor = CS5331 (type = 9) ivtv: i2c attach [client=tveeprom[1],ok] From /var/log/messages: Dec 14 09:44:43 mythtv last message repeated 3 times Dec 14 09:44:43 mythtv kernel: saa7115: decoder disable output Dec 14 09:44:43 mythtv kernel: saa7115: decoder enable output Dec 14 09:44:44 mythtv kernel: saa7115: decoder disable output Dec 14 09:44:44 mythtv kernel: saa7115: decoder enable output Dec 14 09:44:55 mythtv kernel: saa7115: decoder set picture bright=127 contrast=63 saturation=63 hue=0 Dec 14 09:44:55 mythtv last message repeated 3 times Dec 14 09:44:55 mythtv kernel: saa7115: decoder set size Dec 14 09:44:55 mythtv kernel: saa7115: decoder disable output Dec 14 09:44:55 mythtv kernel: saa7115: decoder enable output Dec 14 09:45:23 mythtv kernel: saa7115: decoder set picture bright=127 contrast=63 saturation=63 hue=0 Dec 14 09:45:23 mythtv last message repeated 3 times From modules.conf.local: alias char-major-61 lirc_i2c alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv options ivtv ivtv_debug=1 ivtv_std=2 tuner=28,38 options msp3400 once=0 simpler=1 simple=1 add below ivtv msp3400 saa7115 saa7127 tuner add above ivtv lirc_dev lirc_i2c ivtv-fb ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] Question about Chris's new tuners patch.
I've got a question about the new tuner path from Chris Kennedy. Since it's marked for a specific kernel version, I'll have to downgrade my kernel (I want to stick with 2.4). Does this mean I have to recompile everything (ivtv, mythtv, mysql, lame, etc)? [I just don't want to work up a sweat if none is needed]. By the way, has somebody got an unofficial howto about this proces? ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Hard Drives that Actually Work?
Brian May wrote: Terrence To mitigate the risk I recommend either RAID1 Unfortunately, RAID1 will not help in the case the hard disk returns random data but fails to report an error. Erroneus read data cannot be corrected in any way, so that's all in the game. And that only corrupts a few files while a complete hard disk crash just looses you entire info. And if I understand you correctly, RAID1 *does* protect you againt that. Moreover the CRC checks on hard disk makes it report an error before it get's the chance of reading the wrong info. Hmm, I think I want a RAID in my new PC. ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] Two PVR 350's One works, one not. PAL Issues?
I've been trying very hard to get two PVR 350's in one box to run with ivtv-0.2rc3b (PVR 250's are just not available in this part of Europe). The first one is working like a charm, but the second card is just not tuning (there is a stream, but it is black or static).Tveeprom reported: tveeprom: Hauppauge: model = 48134, rev = J347, serial# = 2756226 tveeprom: tuner = LG TP18PSB01D (idx = 47, type = 28) tveeprom: tuner fmt = PAL(B/G) (eeprom = 0x04, v4l2 = 0x0007) tveeprom: audio_processor = CS5331 (type = 9) i2c attach [client=tveeprom[0],ok] (...) ivtv: i2c attach [client=MSP3418W-B3,ok] tveeprom: Hauppauge: model = 48139, rev = K257, serial# = 7597097 tveeprom: tuner = Philips FM1216 ME MK3 (idx = 57, type = 38) tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) audio_processor = CS5331 (type = 9) ivtv: i2c attach [client=tveeprom[1],ok] According to Chris's site (http://205.209.168.201/~ckennedy/ivtv/new_tuners/) I do not need the tuner update. But here is something interesting: tveeprom reports that the second is a PAL(D/K), whereas I'm in PAL-G land, might that be the problem? Or is it just something I did wrong? Please help. The rest of my config: From modules.conf.local: alias char-major-61 lirc_i2c alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv options ivtv ivtv_debug=1 ivtv_std=2 tuner=28,38 #options tuner debug=0 type=1 #options saa7127 enable_output=1 output_select=0 pal=1 options msp3400 once=0 simpler=1 simple=1 #options saa7115 debug=0 add below ivtv msp3400 saa7115 saa7127 tuner add above ivtv lirc_dev lirc_i2c ivtv-fb When running the second card /var/log/messages logs: Dec 14 09:44:43 mythtv last message repeated 3 times Dec 14 09:44:43 mythtv kernel: saa7115: decoder disable output Dec 14 09:44:43 mythtv kernel: saa7115: decoder enable output Dec 14 09:44:44 mythtv kernel: saa7115: decoder disable output Dec 14 09:44:44 mythtv kernel: saa7115: decoder enable output Dec 14 09:44:55 mythtv kernel: saa7115: decoder set picture bright=127 contrast=63 saturation=63 hue=0 Dec 14 09:44:55 mythtv last message repeated 3 times Dec 14 09:44:55 mythtv kernel: saa7115: decoder set size Dec 14 09:44:55 mythtv kernel: saa7115: decoder disable output Dec 14 09:44:55 mythtv kernel: saa7115: decoder enable output Dec 14 09:45:23 mythtv kernel: saa7115: decoder set picture bright=127 contrast=63 saturation=63 hue=0 Dec 14 09:45:23 mythtv last message repeated 3 times ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Hard Drives that Actually Work?
Over the last two years I bought 5 hard disks as upgrades for the Myth boxes I've made; 2 Maxtor, 3 WD. Once a WD was DOP (Dead on Purchase) and got it replaced. I also got a lot of old (20 GB) drives and my experience is that most drives (regardless of the brand) die after a year or 5 to 10. [EMAIL PROTECTED] wrote: I just had my second Western Digital Special Edition 200 GB drive die on me. Since I'm using an ASUS Pundit, I figured heat was the culprit, so the second drive had a dual-fan cooler on it. No such luck. After about three months of use, performance suddenly degrades, and the journals begin to corrupt. A few days later, I/O errors crop up, and the drive is pretty much useless. Are these drives just not up to the stress of a PVR? I'm interested in hearing what kind of drives people have had good luck with, as I've about had it with these. I'll get my third on warranty, but It won't be going back into a myth box. Thanks, Paul ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] PVR-250 + PVR-350
Søren Pingel Dalsgaard wrote: Having ditched the idea of getting anything sensible out of my dxr3-card I have decided to move up to PVR-350. Has anybody tried a configuration with a PVR-250 + PVR350. Are there any pitfalls? (how) Do I load the ivtv driver twice? If you have the PVR350 running and set up correctly, it shouldn't be moch more than editing the modules.conf, a depmod and editing myth's setup. You might have to do some tweaks. But it didn't take me more than 15 min. Unfortunately for me there are no more PVR250's available in the whole of the Benelux. :-( ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
