Mailing List Archive

RE: mythtv-dev digest, Vol 1 #149 - 1 msg
What I'd suggest is to buy / build an IR reciever (see lirc.org for details,
it can be done quite cheaply), and just use it to record what commands your
remote sends to the dish to change channels, etc. Using this method you should
be able to duplicate anything your remote can do.

>===== Original Message From mythtv-dev-request@snowman.net =====
>Send mythtv-dev mailing list submissions to
> mythtv-dev@snowman.net
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://www.snowman.net/mailman/listinfo/mythtv-dev
>or, via email, send a message with subject or body 'help' to
> mythtv-dev-request@snowman.net
>
>You can reach the person managing the list at
> mythtv-dev-admin@snowman.net
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of mythtv-dev digest..."
>
>
>Today's Topics:
>
> 1. Re: lirc, Motorola DCT2000 and the Actisys IR blaster (David Hunnisett)
>
>--__--__--
>
>Message: 1
>Date: Thu, 7 Nov 2002 23:06:44 +0000
>To: mythtv-dev@snowman.net
>Subject: Re: [mythtv] lirc, Motorola DCT2000 and the Actisys IR blaster
>From: David Hunnisett <david@hunnisett.opensrc.org>
>Reply-To: mythtv-dev@snowman.net
>
>On Tue, Nov 05, 2002 at 12:32:16AM -0800, A Gill wrote:
>> Has anyone done any work trying to get serial port
>> control of a digital cable box to work. I have been
>> researching this for a little while now, but haven't
>> quite got the code i need. Right now I can only turn
>> the box on and off using a simple shell script, but of
>> course we need to be able to change channels. The
>> method is really simple ... its getting the hex
>> commands that I can't seem to do.
>>
>> here's what I have to turn the box on and off.
>>
>> [root@knox:/home/knox ]$ stty raw < /dev/ttyS0
>> [root@knox:/home/knox ]$ echo -ne "
>>
\x10\x70\x00\x02\x03\x40\xc8\x27\x10\x03\x10\x78\x00\x03\x03\x40\x00\x68\x96\x
10\x03\x10\x78\x00\x04\x10\x10\x40\x22\x0a\x98\xbe\x10\x03"
>> > /dev/ttyS0
>>
>> same command is used to toggle the box on and off. If
>> I had the same hex sequence need to set a channel then
>> it would be a done deal. Maybe someone else has a way
>> of finding out.
>how did you work this out?
>what box are you using?
>i am intersted in doing the same thing have a pace digital box
>what rs232 wiring etc?
>
>>
>> -- Allen
>>
>> --- Matt Zimmerman <mdz@debian.org> wrote:
>> > On Mon, Nov 04, 2002 at 11:12:28AM -0600, Carlos
>> > Talbot wrote:
>> >
>> > > The gi-motorola-dct2000 is defined in my
>> > /etc/lircd.conf file which
>> > > was extracted from
>> > http://www.lirc.org/remotes.tar.bz2.
>> > >
>> > > If someone has a better way of scripting this
>> > please feel free to
>> > > contribute any changes. I had to create the
>> > initial shell script because a
>> > > fork is required. You'll noticed during the ir
>> > tranmissions I had to delay
>> > > each digit by one second. This is long enough to
>> > cause a/v synch issues
>> > > with Mythtv. It's better that the script returns
>> > right away while the ir
>> > > is sent in the background.
>> >
>> > Excellent, I have the same unit and am glad to hear
>> > that lirc works well
>> > with it. If I can't make it work with IrDA, I will
>> > look into the Actisys
>> > unit that you mentioned; thanks for bringing that to
>> > my attention.
>> >
>> > --
>> > - mdz
>> > _______________________________________________
>> > mythtv-dev mailing list
>> > mythtv-dev@snowman.net
>> > http://www.snowman.net/mailman/listinfo/mythtv-dev
>>
>>
>> __________________________________________________
>> Do you Yahoo!?
>> HotJobs - Search new jobs daily now
>> http://hotjobs.yahoo.com/
>> _______________________________________________
>> mythtv-dev mailing list
>> mythtv-dev@snowman.net
>> http://www.snowman.net/mailman/listinfo/mythtv-dev
>
>
>--__--__--
>
>_______________________________________________
>mythtv-dev mailing list
>mythtv-dev@snowman.net
>http://www.snowman.net/mailman/listinfo/mythtv-dev
>
>
>End of mythtv-dev Digest
Re: mythtv-dev digest, Vol 1 #149 - 1 msg [ In reply to ]
Has anyone had any problems with audio echo? I understand that the audio is coming from the PCI output in my mixer, but the audio is also coming from my Line input as well. If I mute the PCM then I hear just the line, but it is ahead of the video. The output from PCM is synced with the video. The problem is how do I get just the PCM audio if the Line input must be turned up because that is where the vid card is hooked up to? Also relating to sound, does anyone know how to get KDE to cooperate with mythtv better than me having to go kill arts processes? I have an SB64D PCI that I have loaded using the es1371 module. Thanks in advance!

--Steve
Re: Re: mythtv-dev digest, Vol 1 #149 - 1 msg [ In reply to ]
On Fri, Nov 08, 2002 at 04:22:39PM -0500, ski44@aol.com wrote:

> Has anyone had any problems with audio echo? I understand that the audio
> is coming from the PCI output in my mixer, but the audio is also coming
> from my Line input as well. If I mute the PCM then I hear just the line,
> but it is ahead of the video. The output from PCM is synced with the
> video. The problem is how do I get just the PCM audio if the Line input
> must be turned up because that is where the vid card is hooked up to?
> Also relating to sound, does anyone know how to get KDE to cooperate with
> mythtv better than me having to go kill arts processes? I have an SB64D
> PCI that I have loaded using the es1371 module. Thanks in advance!

Mute the line input. It can still be used for recording even when it is
muted.

--
- mdz
RE: Re: mythtv-dev digest, Vol 1 #149 - 1 msg [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Has anyone had any problems with audio echo?

This is what I do (Mandrake 9.0) - amixer is in the alsa-utils RPM or
tarball

% amixer set Master,0 100%,100% unmute
% amixer set Line,0 100%,100% mute capture
% su -
# alsactl store
# exit

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPcw6m/c1NpCTlP0JEQKCbwCgjKGbJniXtpw480MI5vo9iyMSeh4AoOJ+
KYrllu4ug2Ldvy/1sVIvlwjp
=3Bh4
-----END PGP SIGNATURE-----