In order to make it easier for everyone to download the latest MCEIR version and read about changes, I will update my very first post.

Latest MCEIR version is 0.18 and can be downloaded here
Its source code (Visual Studio 6) is also available here

FAQ : instead of reading this huge thread, Peter (HIP author) summarized it here

Version 0.18
- Blaster selection is now possible (1, 2 or both)
- Introduce MceIrSelectBlaster() and MceIrCheckFile() functions
- Driver now will install all MCE 2005 remote models

Version 0.17 :
- Receiving IR with REC-80 protocol is now recognized (Panasonic)
- Fix : Bug in sending RC6 Pronto files
- Fix : Poor key recognition when running CPU expensive application

Version 0.16 :
- MCEIR driver now supports going into hibernate S4 state
- Receiving IR with RC5X/RC6/RC6A protocols is now recognized
- Sending IR from all Pronto IR format is now supported (not only learned IR format)



--------------------------------------------------------------

Hi all !

I'm a french diyer and I was quite upset having bought a nice remote control with 2 IR blasters... and being unable to drive my plasma or AV receiver with it.
This is the reason why I have made these small programs just to check if I was able to make the IR blaster working... and it seems to work !

Here is the files (available here : http://burningzeroad.free.fr/MCEIR.rar) :
- MCEIR.sys : this is simply the USB BULK driver provided in XP DDK (for the moment...)
- MCEIR.inf : driver installation (for USB VendorId 471 ProductId 815)
- MCEIRREC.exe : to record raw IR codes into a file
- MCEIRPLAY.exe : to play back raw IR codes from a recorded file

So if you want to try if it works with your equipments, just install this driver instead of the MS one, then record an IR keycode (MCEIRREC -o C:\key.irk) and play it back (MCEIRPLAY -i C:\key.irk)... I will enjoy your feedback !

Next step for me is to build an API for using IR receiving/learning/transmitting capabilities so my MCE remote driver can easily beeing integrated in MCE itself (Yeaahhh!) or other applications (i.e. Girder). So if you are a developper interested in helping me for this project, I can send you C sources.

Cheers

PS: sorry for my english...

Are you planning to release a new MCE remote driver which will allow our MCE remotes "learn" other functions from audio video equipment. For example an audio reciever (such as radio tuner up/down, changing music/EQ presets, audio input/source selecter) or learn functions from a cable/satellite remote?

I am very interested!!

Sounds excellent mate, keep up the good work!

this is great. i started another thread trying to see if it was possible to do this!

What i would like to do is have starting up MCE trigger a 'turn-on-tv-and-switch-to-av' command via the IR bugs.

This would be great to get working in a simple, easily configurable way.

Will try it out tonight.

Cheers

I am the developer of HIP a free PC remote package, and I have been looking at this very problem myself (as HIP already supports a number of other IR blasters including USBUIRT and Tira, and the software is being used by people with the MCE remote but not using MCE).

I would be very interested in seeing your source if you are willing to share, and include this functionality in the program.

NOTE:

IF you do not want to read the entire thread, I have prepared a FAQ of the work that has been done which is available for download from here:

http://www.byremote.com.au/Hip/mce_remote_faq.htm

Yes, yes yes!  This will be the most useful tool to come around in a while.  I would like to get rid of my UIRT and just use the MCE IR receiver.  Do you plan on making this driver "seemless" with MCE 2005 and also include a Girder plugin?  What would be really cool if you could find someone to write an MCE program that would allow us to use these new "buttons" in MCE.  Thanks for the contributions and keep up the work.

 

samsonite

@BurningZeRoad: I was planning on visiting MS's XP DDK site to investigate something like this myself -- so I am VERY happy to see that you have already started this process. Admittedly, I am not very knowledgeable of "C" code , but I am familiar with C++/C#, .NET, and a few other web/internet related languages. This stated, I will be happy to share what I know and offer input. Also I would love to see your code, please send to: slangnasty at hotmail dot com.

Judging by the responses thus far, we definately have a group of willing beta testers!

Any idea when you will deliver the first test/driver? I can hardly wait to begin the beta testing.

Cheers!
slang

Thanx for all your encouragements guys !
For the ones who are interested, I just left sources files (Visual Studio 6 C project) here : http://burningzeroad.free.fr/MceIrSrc.rar.
@btmi : this is exactly the kind of software my MCEAPI will be for ! I didn't try it yet... but I will this evening. I will help you to integrate MCEIR if you want.
For the moment, I'm working on RC6 code recognition from raw IR codes and it's almost finished now.
@slang : have a look at sources (you can easily transform them into C++) and if you think you are able to build a GUI to setup IR keycode learning, you are welcome on board ! GUI is not my cup of tea !
I think I will be able to deliver a very first version (with harcoded TV-Receiver power on/off, volume +/- only...) within a few days.
Have a nice day !

BurningZeRoad - I would be very interested in working with you on this...I have downloaded the source and will be examining it over the next few days.  HIP already has a GUI interface for learning and saving IR codes and so alll I need to do is to write the code that lies in between.

I will be back in touch when I have some news....

im sorry if this sounds like a stupid qeustion but i still want to ask it for clarity's sake.

the aim of this thread is to be able the 'record' and 'playback' various remote codes via the IR bugs that plug into the remote receiver. Thus allowing us to control other appliances via our MCE boxes.

Is this right? Is this the intention?

At the moment i dont have a use for the coloured teletext buttons on the remote. it would be great if we could program those with remote macros for our various IR controllable home theatre stuff.

Cheers

Hey Samsonite,
are you using UIRT to change channels on your STB in MCE? Or just to control other aspects of it and if so what?

(And are you the same samsonite of BlueTwo fame on the MP forums?)

Hi btmi !
And thanx for your interest !
Don't spent a lot of time studying source code (except if you are interested in it !)...
I will provide a very simple API like this one :

BOOL MceIrRegisterEvents(HWND hWnd) => my DLL will start a thread then you will get WM_COMMAND message from the remote for each key pressed (with wParam=ID_MCEIR_KEYCODE and lParam=KeyCode)
BOOL MceIrUnregisterEvents() => to stop receiving events (if needed...)
BOOL MceIrSetRepeatTimes(DWORD FirstRepeat, DWORD NextRepeats) => to setup long keystrokes
BOOL MceIrRecordToFile(HANDLE hFile, DWORD Timeout) => to record a raw IR keycode within an X ms timeout
BOOL MceIrPlaybackFromFile(HANDLE hFile) => to play back a recorded raw IR file

I think this will be done maybe tonight or tomorrow...
If you need something else, just ask this is the right time !

@harbinger: Yes... 

In my case, I am interested in also figuring out if there is a way to get my MCE remote to "learn" other functions/macros beyond just STB channel changing, TV on/off, and Amp Volume up/down.

Specifically, I am interested in figuring out how to extend my MCE remote so it can "learn" functionality to include the following functions:

ex. AUDIO/VIDEO COMPONENT > FUNCTION

Audio Amp > Power ON/OFF
Audio Amp > Tune(r) UP/DOWN
Audio Amp > Change audio input/source (ex... change Audio input from STB, to HTPC, or DVD player, or CD player, etc... 
Audio Amp > Change Audio preset EQ modes ("Rock", "Jazz", "Movie Theater 70mm", "Dolby Pro Logic", etc...)

TV > Change Video input

hope explanation helps
slang

BurningZeRoad - a DLL would suit me nicely and it opens it up to any application.

A couple of questions:

1) MceIrRegisterEvents - Rather than using WM_COMMAND, would it be possible to use WM_USER or WM_APP to help distinguish between other WM_COMMAND events?

2) When I was capturing the input from this HID device, the defined keyboard commands were still being sent through to the keyboard handler and I was unable to override this...is this the same for you?

3) MceIrPlaybackFromFile How big are the RAW files you are capturing?  As I may look for another (in memory) way to send the commands as I will be saving them all in a flat file.

Still this all looks like fun, and I look forward to playing with your dll.

Peter

Hi Peter !

Here are your answers :

1) Done ! If you get http://burningzeroad.free.fr/MceIrApi.dll, you'll get the first API version. It includes sources and debug/release compiled DLL. I had time to replace WM_COMMAND with WM_USER.
There is also a readme.txt file describing parameters and returns.

2) No this is completely different ! Since my API requires a new driver, all the Microsoft HID stuff will disappear. My API won't ever generate any WM_KEYBOARD, WM_APPCOMMAND, WM_INPUT... only WM_USER messages ! So you can surely identify who generates the message.
Keycodes are different too : I'm sending the RC6 keycodes without any translation (see in MceIr.h for the actual exhaustive list).

3) IR files are very short (about 500 bytes). I agree with you and will include 2 new functions in the next version :
-BOOL MceIrRecordToMemory(PUCHAR pData, DWORD MaxCount, DWORD Timeout)
-BOOL MceIrPlaybackFromMemory(PUCHAR pData, DWORD MaxCount)

Have fun with the DLL !