Re: [mythtv-users] 1080i Mitsubishi WS-48311
On Jan 13, 2006, at 12:33 PM, Jason Kraftcheck wrote: I haven't been able to find a working modeline for 1080i display on my TV. My TV is a Mitsubishi WS-48311 (48 rear-projection, Mitsubishi 2003 model series). Is there anyone who has a working 1080i modeline for this TV? I've tried defining my own modelines and I've tried a bunch of modelines I've found in messages to this list and on various web sites. For all of them, the initial nVidia logo is is wrapped around the screen (it begins near the right edge of the screen and wraps around to the left edge) and for most there are some additional artifacts in the logo display. Once myth starts I have a vertical white bar down the center of the screen, but the image is correctly centered (not wrapped). Display of the actual (NTSC) TV content is not wrapped around, but the vertical white bar persists and for some modelines only the first frame is displayed while the audio continues correctly. I have no problems when outputting video at 480p. My setup: Debian testing Mythtv packages from ftp.nerim.net/debian-marillat nVidia driver version 1.0.7174 X.org X server version 6.9.0 Video output using a VGA to (RCA) RGBHV breakout cable Mitsubishi WS-48311 48 rear-projection TV I assume the problem with only the first frame of video being shown is a bug in either the nVidia driver or the X server. What about the vertical white bar problem? Is this a problem with: the modeline, the video connection, some software, my TV? I'd greatly appreciate a verified working modeline for this particular TV so I can determine if the problems I'm encountering are due the modelines I've tried or not. Otherwise, any insight anyone can provide into the specific problems I'm encountering would be helpful. thanks, - jason ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users I have an older 46 Mitsubishi TV connected via an RGBHV breakout cable. I've wrestled quite a bit with different modelines and finally settled on a 960x540p mode. I remember having the problem you describe with the display wrapped, but it was wrapped for everything, not just the nvidia logo. I can't remember what modeline/configuration I had that problem with. Here's the modeline I'm using: ModeLine 960x540p 37.26 960 976 1008 1104 540 542 548 563 +hsync +vsync The TV is a Mitsubishi WT-46809, and it interprets that modeline as 1080i. It has been working very well for almost a year now. My system configuration is quite a bit different from yours: Fedora Core 4 X.Org 6.8.2 Nvidia driver version 1.0-7676 Myth built from svn version 6905 - David Sims ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Problems with VGA/RGBHV and Mitsubishi HDTV
On Sep 14, 2005, at 12:19 PM, [EMAIL PROTECTED] wrote: My problem is that my TV doesn't want to wake up after I turn it off for an extended period of time. I leave the Myth frontend running and I turn the TV off when I'm done to prevent burn in. If I leave it off for more than a half hour when I come back to turn it on it comes on for about 5 seconds and shuts itself off. I can get it working again by unplugging the VGA from the back of the computer, turning on the TV, and then rehooking the VGA cable back to the computer. What's odd is that I can turn the TV off and back on, just not for an extended period of time. I have a Mitsubishi TV connected the same way with a breakout cable. I have a problem similar to yours, although it's not as severe. Quite often when I turn on the TV, if the connected computer is on and the TV is set to that input, it will immediately turn itself off. When that happens I can immediately hit the power button again and it will stay on. I never have to disconnect the VGA cable. My fear is that the voltage levels from the VGA output on the video card aren't exactly right for the TV. If that's the case, we're likely slowly damaging our TVs. This post back in March talked about adding some inline resisters to the breakout cable: http://www.gossamer-threads.com/lists/mythtv/users/120314? search_string=DVI%20and%20RGBHV;#120314 ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] ripping EVERYTHING on a DVD to a single file
On Sep 11, 2005, at 5:45 PM, Jesse Guardiani wrote: On Sunday 11 September 2005 7:29 pm, Khanh Tran wrote: How do I just rip an entire DVD (without transcoding) to disk as a single file? Most dvd ripping programs rip to an ISO image. DVD::RIP can rip to a VIDEO_TS folder and then you can use K3B to make an ISO. If you prefer the Windows programs, DVD Shrink is an old favorite along with DVDFab Decrypter. Both also work in Linux under Wine... Is there a way to do this from the MythDVD ripper? An ISO Image option was added to the MythDVD ripper back in July, so it's available in the latest SVN. I presume it'll be in the next official release. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Trouble Playing Ripped DVDs
On Jul 26, 2005, at 1:02 AM, Nick Rout wrote: However a recent thread alerted me to the fact that you can make an iso of the DVD and then use xine to play the iso. This would mean you are dealing with one file only. Thats what i recommend doing. And to make that easier, an ISO Image rip option has recently been added to mythdvd. It was committed to svn last week. So if you don't mind running the latest development you wouldn't even have to go outside Myth to generate the iso. - David Sims ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] pcHDTV 3000: Questions from a MythTV newbie
Take a look at this thread: http://www.gossamer-threads.com/lists/mythtv/users/135131? do=post_view_threaded Sounds like you might have the same problem. I think the long term answer is to figure out how to use the dvb drivers. I'm still using the v4l drivers with my hd-3000, because that's what I got working first and haven't taken the time to get the dvb drivers working. I've had difficulty like you have with them, but I honestly haven't spent much time on it. - David Sims On Jul 21, 2005, at 10:14 AM, [EMAIL PROTECTED] wrote: All, I've been scanning the archives of this list for quite some time now and I had a few questions regarding the pcHDTV 3000 and it's compatibility with Myth on Fedora Core 3. I've compiled the drivers xine-hd (comes with the pcHDTV card) and tested HDTV reception and NTSC reception. Both work great. I used xine to test the HDTV (ATSC) signals and tvtime to test NTSC. I am using the v4l drivers, not the DVB drivers for reasons I'll discuss in a second. When I load the v4l drivers (modprobe cx88_atsc) the cx88xx drivers (NTSC) load as well as the ATSC drivers. This creates several devices (duh), namely /dev/vbi0, /dev/video0, and (I think) /dev/audio0. The ATSC device is created as /dev/video1. To get xine to recognize /dev/video1 as the ATSC driver, I made a symbolic link to /dev/video1 called /dev/dtv. This works great. However, when I try to set up Myth to read this card (I am using Myth 0.18.1), the ATSC card is not recognized. I can set up NTSC, but if I erase all those card settings and try to set up an ATSC card, mythsetup just tells me that it couldn't find inputs for the device (I know that they are there, though, because xine works great). I have tried to every possible combination of Global TV settings (NTSC with standard TV, ATSC with HDTV, NTSC with HDTV, etc), just on a whim that it might work. So why am I not using the DVB drivers? When I load the pcHDTV DVB drivers (modprobe cx88_dvb), several devices are created (/dev/dvb0.dvr0, /dev/dvb0.frontend0, etc). However, I don't know how to use these devices and none of the programs from interpreting DVB seem to recognize or even look for these devices. Since, I could test and the v4l drivers and confirm that they work, I went that route. My system is built on the default FC3 load (kernel 2.6.9), one pcHDTV card, nVidia FX 5200, 2.8 GHz HT pentium 4, if that helps. I guess my real question is what MythTV is looking for to discover the v4l ATSC driver and if I should be using DVB drivers, how should I configure them? I installed Myth with the RPMs available on atrpms (myth-suite package). If anyone could clear up the confusion that I'm having, that would be great! I would hate to have to spend the time to rig up a pseudo-PVR replacement. Thanks! -B ___ 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
Re: [mythtv-users] Configuring X with my GF4 for TV Out
On Jul 6, 2005, at 7:13 PM, Justin Popa wrote: I am currently having issues getting the resolution right in my TV-Out setup. I had no luck using Jarod's guide with my GF4MX440, so I kind of scrounged things together from multiple sources. Right now the resolution for the TV is getting set to the same as the monitor on the system. The way I am thinking, it seems to me that the way I have set it up(no experience with configuring X) the TV just clones the monitor. I guess I am kind of lost on how to set this whole thing up. Does anyone have a working config using nvidia for ONLY tv out? Thanks Here are the Device and Screen sections I have. I'm not currently using svideo on my GF4 card, but this is the config that worked quite well when I was. This configuration was for svideo out ONLY. I did not have a monitor connected. Section Device Identifier Videocard0 Driver nvidia VendorName Videocard vendor BoardName NVIDIA GeForce 4 MX (generic) Option TVStandard NTSC-M Option TVOutFormat SVIDEO Option ConnectedMonitor TV Option TVOverScan 0.7 Option NoLogo TRUE Option HWCursor TRUE Option RederAccel FALSE EndSection Section Screen Identifier Screen0 Device Videocard0 MonitorMonitor1 DefaultDepth24 SubSection Display Virtual 800 600 Depth24 Modes 800x600 EndSubSection EndSection ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] pcHDTV HD-3000 2.0 Drivers
Here's a diff for the changes I made to the cx88-atsc.c source file in
the 2.0 driver.
# diff -U 4 cx88-atsc.c.orig cx88-atsc.c
--- cx88-atsc.c.orig2005-03-20 14:11:27.0 -0700
+++ cx88-atsc.c 2005-03-20 15:00:01.0 -0700
@@ -466,9 +466,21 @@
return 0;
}
/* -- input switching -- */
case VIDIOC_ENUMINPUT:
- return -ENOIOCTLCMD;
+ {
+ struct v4l2_input *input = arg;
+ if( input-index 0 ) return -EINVAL;
+ sprintf( input-name, Television\0 );
+ input-type = V4L2_INPUT_TYPE_TUNER;
+ input-audioset = 0;
+ input-tuner= 0;
+ input-std = V4L2_STD_ATSC_8_VSB;
+ input-status = 0;
+ memset( input-reserved, 0, 4 );
+/* return -ENOIOCTLCMD;*/
+ return 0;
+ }
case VIDIOC_G_INPUT:
{
unsigned int *i = arg;
*i = dev-core-input;
On Jun 10, 2005, at 7:31 AM, Blair Preston wrote:
I've had no luck as yet. Would LOVE to see you modifications to the
Driver.
Thanx David,
-Blair
David Sims ([EMAIL PROTECTED]) wrote:
On Jun 9, 2005, at 8:35 PM, Blair Preston wrote:
First, thanx for the responce Greg.
Actually, I have Over the Air Digital ATSC (in the States, pulling
from a
Digital Antenna). And the tuner card is actually working as I am able
to pull
up a picture using mplayer /dev/video2 . The tuner card/driver
(which
is the
cx88-atsc driver) seems to be working fine. The issue 'appears' to
be
something myth related in this kernel/driver configuration.
Otherwise
I don't
know why I can view TV from mplayer accessing this tuner card ( I
just have
to change channels by issuing a 'dtvsignal /dev/video2 channel
number'
command). Myth seems to see the card, but can't find the inputs
(i.e.
Television, Composite, S-Video). Kinda strange.
By the way, the same box, booting a 2.6.8 kernel, works fine with
myth, but I
have to use the HD-3000 1.5 drivers to compile on this kernel.
I believe I had this same problem with the 2.0 cx88-atsc driver for
the
HD-3000. I ended up actually modifying the driver itself slightly,
because it didn't appear to be responding to the call Myth makes to
query the inputs. All works fine now, but I have hoped to find a way
to get it to work without a custom modification to the driver. If you
figure it out please post your findings. Otherwise I'd be glad to
provide the changes I made to the driver if you want to try it.
- David
___
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
Re: [mythtv-users] pcHDTV HD-3000 2.0 Drivers
On Jun 9, 2005, at 8:35 PM, Blair Preston wrote: First, thanx for the responce Greg. Actually, I have Over the Air Digital ATSC (in the States, pulling from a Digital Antenna). And the tuner card is actually working as I am able to pull up a picture using mplayer /dev/video2 . The tuner card/driver (which is the cx88-atsc driver) seems to be working fine. The issue 'appears' to be something myth related in this kernel/driver configuration. Otherwise I don't know why I can view TV from mplayer accessing this tuner card ( I just have to change channels by issuing a 'dtvsignal /dev/video2 channel number' command). Myth seems to see the card, but can't find the inputs (i.e. Television, Composite, S-Video). Kinda strange. By the way, the same box, booting a 2.6.8 kernel, works fine with myth, but I have to use the HD-3000 1.5 drivers to compile on this kernel. I believe I had this same problem with the 2.0 cx88-atsc driver for the HD-3000. I ended up actually modifying the driver itself slightly, because it didn't appear to be responding to the call Myth makes to query the inputs. All works fine now, but I have hoped to find a way to get it to work without a custom modification to the driver. If you figure it out please post your findings. Otherwise I'd be glad to provide the changes I made to the driver if you want to try it. - David ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] New MCE 2005 Remote
On Jun 1, 2005, at 12:00 AM, Cenk Ozkan wrote: Really trying to avoid using the kernel from source. I am using the FC3 kernel 2.6.11-14, lirc 0.7.0. Which Martin Blatter driver are you using ? I don't have access to the computer it's setup on anymore, so I can't double check, but I believe it's the one dated April 1. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] New MCE 2005 Remote
On May 31, 2005, at 9:42 AM, Nigel Metheringham wrote: It semi-worked. I came to find out that my motherboard/usb controller (ohci I believe) had an issue with that kernel. On my hardware, with kernels up to 2.6.11-1.14 (FC3 distribution) I was getting very intermittent hardware detection/module loading (ie one in 20 times). I haven't yet tried it against the newer kernel version. The way I handle this is to build just that kernel module and install it manually. I recently helped setup an MCE 2005 remote with lirc, and also had the intermittent detection/module loading problems. The stable combination ended up being lirc 0.7.0 built from source, kernel 2.6.11.7 built from source, and Martin Blatter's driver. This was a couple months ago and that combination of lirc/kernel/driver is still running with no detection/loading problems, and the remote is fully functional. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up USB MCE remote in LIRC?
Hi Lee, Sounds like you're making progress. For MythTV to work with LIRC, you'll have to have the appropriate lircrc file in the ~/.mythtv directory. Notice the filename is lircrc and not .lircrc (no dot in front). That's the lircrc file that maps your remote buttons to MythTV commands. In addition, for lirc to work with the external applications launched by mythfrontend like mplayer, you will need the lirc configuration for those applications in the correct place. Which I believe is typically ~/.lircrc (notice that one does have the dot in front). A couple things I can think of off hand to check if things still don't work: 1. Check the lircd log file as you start mythfrontend to make sure it's getting a client connection when mythfrontend starts 2. Verify the button names displayed by irw match exactly the button names in ~/.mythtv/lircrc I've never used KnoppMyth before so I'm not sure how to configure lirc to autostart on it. Using FC3 we've put it in /etc/rc.d/rc.local: /usr/local/sbin/lircd -L /var/log/lircd /usr/local/bin/irexec -d I suspect you could do the same on Knopp. - David On May 4, 2005, at 4:43 AM, [EMAIL PROTECTED] wrote: Hmmm, the thread seems to have drifted onto the 2005 remote, I'm trying to set up the older 2004 style remote... With Davids clues, I've built the lirc 0.7.1 lirc_mceusb module, and copied the lirc.conf to /etc/lirc/ and the .lircrc to the two dirs whose names escape me. When I run irw, it all seems to be working, the red led on the receiver flashes, and all of the buttons are shown on the screen when I press the buttons on the remote... :) I've switched to the i686 version of MythTV, which should have built in native lirc support... However, nothing happens in Myth when I press buttons on the remote... :( Any ideas? Lee Also, I'm running KnoppMyth, how do I get it to autostart LIRC? ___ 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
Re: [mythtv-users] Setting up USB MCE remote in LIRC?
For the new style remote I had to download a new driver, which is not yet part of the lirc distribution. Written by Martin Blatter the lirc driver for the new style remote can be downloaded at http://blatter.com/mceusb/. There's a tarball of the driver, an example lircrc file for Myth, and some installation instructions. Actually I think he has three different versions of his driver there. I just downloaded the newest one. To use that new driver you'll need to build lirc 0.7.0 from source (0.7.1 didn't work very well for me). Just download the lirc source tarball and extract it (if you haven't already), then extract the tarball from Martin Blatter on top of it. Then configure, build, and install lirc as I described in the previous post. With the combination of kernel 2.6.11.7, lirc 0.7.0, and Martin Blatter's driver, the new style remote seems to work quit reliably. - David On May 1, 2005, at 9:02 AM, Nathan Whittacre wrote: So you got the new style remote working with lirc? Could you share some insight on what you did to get it to work. I am using kernel version 2.6.11.8 and lirc 0.7.0 and can't get it to work. It recognizes the remote, but I can't get any data from it. I've also tried lirc 0.7.1. Thanks, Nathan David Sims wrote: On Apr 29, 2005, at 4:53 PM, Lee wrote: Having just got my new MythTV install running nicely, I'd like to integrate my (old style) Windows MCE remote into the set up. I've googled for ages and there are lot's of people that seem to have got it working (include Jarod), but I can't find any how-to's or crib sheets. Being a total Linux noob, this leave me at a loss, can anyone point me in the right direction? Many thanks, Lee I haven't had any experience with the old style MCE remotes, but I recently worked with setting up one of the new style remotes with pretty good success. I'm not sure how far back you can go with lirc, but I know lirc 0.7.0 and newer has a driver for the old style MCE remote. If you're comfortable building and installing packages from source code, it's really very easy to do with lirc. I haven't had much luck getting the ATrpms.net lirc packages to work in my setup, so I can't really help if you prefer to go that route. I didn't find any detailed how-to's on the MCE remote either, so I'll describe what my brother and I did to get the new style remote working. Hopefully this can get you going as well. I obtained the lirc 0.7.0 source from the lirc web site: http://www.lirc.org - Extract the source tarball and then configure and build from the extracted source directory like this: # ./configure --with-kerneldir=/lib/modules/`uname -r`/build --with-driver=mceusb # make # make install The install should copy the correct lircd.conf file to /etc/lircd.conf. - You'll also want to put the following in /etc/modprobe.conf: alias char-major-61 lirc_mceusb - I'm not sure if this is really required, but I saw it in some lirc instructions somewhere. Create the /etc/udev/rules.d/lirc.rules and put this in it: KERNEL=lirc[0-9]*,NAME=lirc%n KERNEL=lirc0, SYMLINK=lirc - Then make sure the usb receiver is plugged in and load the lirc modules: # modprobe lirc_mceusb - Try out lircd and irw to see if it works: # lircd -n # irw You should see a message printed indicating that lircd accepted a new client connection. Then if you press buttons on the remote you should see messages indicating which buttons are being pressed. If that doesn't work, you may need to reboot. If you reboot with the usb receiver plugged in, the lirc modules should automatically load which you can verify with the lsmod command: # lsmod | grep lirc lirc_mceusb10884 1 lirc_dev 13388 1 lirc_mceusb then try the lircd and irw commands again. One last thing to note. I'm not sure if this is due to the driver for the new style MCE remote, lirc, the kernel, or my own incompetence, but we couldn't get lirc working correctly with version 0.7.1 of lirc or the 2.6.10-1.770 kernel from ATrpms. We had to use lirc 0.7.0 and kernel version 2.6.11.7 built from source. Hope that helps, David -- -- ___ 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 ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up USB MCE remote in LIRC?
On Apr 29, 2005, at 4:53 PM, Lee wrote: Having just got my new MythTV install running nicely, I'd like to integrate my (old style) Windows MCE remote into the set up. I've googled for ages and there are lot's of people that seem to have got it working (include Jarod), but I can't find any how-to's or crib sheets. Being a total Linux noob, this leave me at a loss, can anyone point me in the right direction? Many thanks, Lee I haven't had any experience with the old style MCE remotes, but I recently worked with setting up one of the new style remotes with pretty good success. I'm not sure how far back you can go with lirc, but I know lirc 0.7.0 and newer has a driver for the old style MCE remote. If you're comfortable building and installing packages from source code, it's really very easy to do with lirc. I haven't had much luck getting the ATrpms.net lirc packages to work in my setup, so I can't really help if you prefer to go that route. I didn't find any detailed how-to's on the MCE remote either, so I'll describe what my brother and I did to get the new style remote working. Hopefully this can get you going as well. I obtained the lirc 0.7.0 source from the lirc web site: http://www.lirc.org - Extract the source tarball and then configure and build from the extracted source directory like this: # ./configure --with-kerneldir=/lib/modules/`uname -r`/build --with-driver=mceusb # make # make install The install should copy the correct lircd.conf file to /etc/lircd.conf. - You'll also want to put the following in /etc/modprobe.conf: alias char-major-61 lirc_mceusb - I'm not sure if this is really required, but I saw it in some lirc instructions somewhere. Create the /etc/udev/rules.d/lirc.rules and put this in it: KERNEL=lirc[0-9]*,NAME=lirc%n KERNEL=lirc0, SYMLINK=lirc - Then make sure the usb receiver is plugged in and load the lirc modules: # modprobe lirc_mceusb - Try out lircd and irw to see if it works: # lircd -n # irw You should see a message printed indicating that lircd accepted a new client connection. Then if you press buttons on the remote you should see messages indicating which buttons are being pressed. If that doesn't work, you may need to reboot. If you reboot with the usb receiver plugged in, the lirc modules should automatically load which you can verify with the lsmod command: # lsmod | grep lirc lirc_mceusb10884 1 lirc_dev 13388 1 lirc_mceusb then try the lircd and irw commands again. One last thing to note. I'm not sure if this is due to the driver for the new style MCE remote, lirc, the kernel, or my own incompetence, but we couldn't get lirc working correctly with version 0.7.1 of lirc or the 2.6.10-1.770 kernel from ATrpms. We had to use lirc 0.7.0 and kernel version 2.6.11.7 built from source. Hope that helps, David ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
