Re: [mythtv-users] UK - Controlling Sky boxes
Neil Bird wrote: Ah, *please* tell me ... do you have to play silly wotsits to make it work OK? I have the obligatory wrapper script 'skychannel' (with some noddy locking code I found somewhere to prevent multiple channel changes at once) calling 'digibox' (a slightly modified version of red_eye IIRC that, again, I found somewhere :) ). But I have grief making it work in one go; if I run 'digibox 101' to change to BBC1, only the initial '10' comes out. Ditto any channel: 'digibox 123' just does '12' and then the digibox times out waiting for the third digit! I've tried 'digibox 12!!!3' and all manner of variants. I resorted to three sep. commands (digibox 1; digibox 2; digibox 3) but this takes an age [in fact I now do 'digibox 12; digibox3' with some extra no-delay */= codes in there as well]. snip Edit the Makefile and increase the WAIT_TIME to two seconds. I found it was cutting the power to the device before it managed to send the three digits HTH's Steve ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MPEG2->MPEG2 cut spinning
Hi. In my case I haven't tried to use the MPEG2->MPEG2 cut before. As far as I can tell the Xvfb allows you to run a virtual frame buffer so that you can run the program without an xwindows session. I was planning on having a go with avidemux in xwindows later tonight by itself. Is it your guess this is the part that is broken? Steve On Mon, 24 Jan 2005 15:25:58 -0500, "Brad Benson" <[EMAIL PROTECTED]> said: > I've been having the exact same problem that you're reporting. It's > not a gui problem since I actually see the avidemux gui open. After > that though, it just sits there forever. Interestingly, this just > started happening a few weeks ago. I was able to successfully export > two different shows using mpeg2->mpeg2 cutting. After that I can only > presume that I updated something to a new version and that's what > broke it. Problem is, I can't figure out what that upgrade could have > been. I'm running: > > avidemux 2.0.34-5_test2 > lve-0.040322-1.1 > transcode-0.6.14-15 > > I don't have Xvfb installed at all, but that wasn't installed when it > was working before either. I've also tried downgrading avidemux to > 2.0.28, but with no success. > > Brad Benson > ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] Getting volume control to work
Hi, I have a PVR350 + Soundblaster live outputting through SPDIF to my amp. I can't work out how to get the volume control in Myth to work! I think it is because I am using SPDIF out? or maybe some option I haven't found. The volume onscreen display goes up and down, but the volume out stays the same. I am running the CVS version from end Dec I believe I am running ALSA audio (how would I check?) and does this even matter? Any pointer or tips greatly appreciated Thanks Steve ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] MythDVD cropping problem
Hi I just installed MythDVD. It plays OK, but is cropping off the bottom of the picture. If I hit "f" mplayer toggles from full screen mode to have mplayer window edges and then I can see all of the picture. When I do this the picture shifts up to be centered in the mplayer window edges and I get the bottom of the picture back. Hitting "f" again switches back to full-screen, the picture drops down say 200 pixels and I lose the bottom 100, even though there is room to display it. Any ideas? Steve ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Hard Drives that Actually Work?
On Tue, 14 Dec 2004 07:53:36 -0600, [EMAIL PROTECTED] said: > 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. > I have 12x80GB Seagate Cudda IV's in an array running 24x7 for the last 2.5 years + 2x120GB Cudda V's 18 months old. One 120GB has failed, although I believe my flatmate dropped the PC during a move, and it didn't boot again after this. They are quiet, not the fastest, but I won't buy anything else for myself. At work have various arrays with 16x300GB PATA Maxtors (with one failure in 16 months) and I just received another array with 14x250GB SATA Maxtors in it. Also one 12x300GB WD (with 8MB cache, 3 year warrenty) no failures yet that gets the s**t kicked out of it every day running for one year. I have had a lot of problems with the glass platter IBM's from two years ago 60GXPs from mem won't touch IBM anymore. Plus Seagate have same 5 year warrenty on all of their drives now ... they have my vote. All of the new Dells we buy seem to have WD drives, two failures in 8 months for 20 PC's ... not so great (Touching a lot of wood) HTH's Steve -- Steven Christall [EMAIL PROTECTED] ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
