Trying to get my MCE IR Receiver/Blaster to send different info to each blaster port

[kshaet]

I seem to not be able to get this to work. I have a Hauppage USB MCE receiver (Which came with my WinTV-HVR-1600 Media Kit), that has two ports on it.

If I use IR Server's Translator or blast.exe to send a command to both ports, it works. If I send to port_1, it doesn't, port_2, it does.

For one brief moment, unless I hallucinated, it worked to both ports separately. I then rebooted, to make sure it worked, and it stopped working.

I read somewhere that you needed something plugged into both Blaster ports when you install WinTV, and I did that. And it did help, a bit.

However, there must be a way to make both ports work. Does anyone know if there is a registry setting I can edit, or what I need to do?

Thanks

My setup is a small computer with an Hppge 1600 and an Hppge 250 card in it, connected to two Telus Optik CIS330 STB's. At least, that's the plan whenever it starts working. Currently running GB-PVR 1.47.

[pBS]

some recievers only have 1 actual port, and plug 2 ir eyes into it..
to see if yours is one of those, look at it's device-id in device manager..
then look in irbus.inf[i think] for that id and note comments there or post id here..
it tells in .inf which ones are singles and which are not..
if you have a single output type, nothing will make it blast the two separately...tho on those the other plug usually never lights up at all..
or it could be a 'type 1' original which i'm not sure is supported..

it works great for me with latest version and MS branded dongle..

[pBS]

ps...latest versions it's -port Port_1 or -port Port_2 or with no 'port', both...
the cmd line help is a bit sketchy on that part..

when you send to port 2 does it light both eyes?
if you can get it to blast to one only and both with separate cmds, then you may be in luck..

[kshaet]

I'm not sure what you want when you say device-ID. Are you referring to the device (it's a eHome infrared receiver (USBCIR))?
Or the hardware ID of the device, which is USB\VID_1784&PID_0001&REV_0000, if I look that up in the usbcir.inf file (I can't find an irbus.inf file in my inf directory) I find this listed %usbcir.DeviceDesc%=usbcir_Device_V2, USB\VID_1784&PID_0001 ; Topseed BB

Which doesn't really mean much to me.

As for the blasting...

If I blast to both, they both light up, if I blast to number Port_1, no go, if I blast to Port_2, it works.

[pBS]

if you blast to port 2 do they both still light up?

oh and that's a type 2 device so it's not the weird 1 port model..so it *should* work for both..
maybe try port_0 and port_3 as the index might be off..

[kshaet]

Blast to Port_1 = Nothing.
Blast to Port_2 = Port 2 transmits.
Blast to Both = Both transmit.

Thanks for the help.

[kshaet]

Got it!

Again, after some more banging of my head against the wall, and much swearing, and just as I was starting to look for a new MCE USB IR device/remote, I found LM Gestion Remote Keymap. It was able to do what Hip & IR Remote Server would not, and that is to get my Haupagge MCE with two blaster ports to work. And it was free (as in beer). I don't know what the problem was, but this program quickly learned my codes from my remote, and let me blast to both ports, independently.
I have two different IR blaster IR's, and the first one was no problem to get it to learn and transmit the signals, the second one, which I got from IR.Blaster.info, was quite a bit more finicky. I had to relearn the remote codes many many times before it started responding properly. And modifying the delays and retransmits for the codes to the IR blaster was a test of patience... my mother in law couldn't understand why I would spend so much time trying to get this work...

[jam_zhou]

old thread..but I need help. Did you get LM Gestion to work on a Win 7 x64 setup? I can't even get it to learn...LM just crashes.