United Kingdom
Hello,
Just upgraded to MP 1.2.1.0, (brilliant job MP team it is clean, quick and the upgrade was effortless making all the backups I took useless).
As it always the case I have ran into problems with my remote/blaster setup. It is a generic eHome device which looks like the HP MedaCenter remote without the HP logos. As I have a multiseat client/server installation going back to a single STB for the TV service I use the blaster ports on the IR receiver to blast the channel changes via the STB when I select a channel in the EPG.
Historically, I could never get the IR blasting to work with any of the generally accepted solutions (IRSS etc) so I ended up using some software from LMGestion (LM Remote) with a hacked version of the TVBlaster3.dll for the blasting from the TV server that he provides. Suffice to say he has gone quiet and is not answering any posts on his support forum re the upgrade to 1.2.1.0 as the DLL is considered incompatible.
I have tried replacing the TVBlaster3.dll with the new one posted in these forums for IRSS but as I suspected that does not work.
I have spent hours trying to get IRSS working but like my last attempt before I went the LMRemote route I failed :-( I have also tried editing the DLL via a resource editor to fool the TVServer into thinking the DLL is compatible with TV Server 1.2.1.0 by changing the version number of the DLL. Alas the check for the version number I believe MP uses to identify if a plugin is compatible with the version of MP being used seems to not look at any of the file version information properties you can see via Windows explorer, or maybe MP does not check just the file version information?
Is it possible to configure MP (the TV Server component) to ignore the version numbers for plugins so that I can get my blasting up and running again via a config setting change somewhere, maybe it will not work but at least if this is possible I can test it?
Thanks.
Gary.
MediaPortal Version: 1.2.1.0
MediaPortal Skin: Default Wide
Windows Version: Windows XP SP3
CPU Type: Intel Core 2 Duo 2.2Ghz
HDD: ST340014AS, ST3500820AS
Memory: 4096MB
Motherboard: ASUS P5N-EM HDMI
Video Card: nVidia GeFor 7100/nForce 630i
Video Card Driver: 6.14.12.5896
Sound Card: RealTek HDA/nVidia HDMI Audio
Sound Card AC3:
Sound Card Driver: 5.10.0559/1.00.00
1. TV Card: WinTV PVR 250
1. TV Card Type: Analog
1. TV Card Driver: 1.18.21.23257
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: Hauppage WinTV PVR PCI II
MPEG2 Audio Codec: Klite Codec Pack 6.6.0 (Full)
h.264 Video Codec: Klite Codec Pack 6.6.0 (Full)
Satelite/CableTV Provider: Virgin
HTPC Case: NA
Cooling: 1 x 12cm Case Fan, Generic Intel Cooler
Power Supply: Generic
Remote: Generic RC6 eHome
TV: Hanspree Xv-S
TV - HTPC Connection: HDMI
Just upgraded to MP 1.2.1.0, (brilliant job MP team it is clean, quick and the upgrade was effortless making all the backups I took useless).
As it always the case I have ran into problems with my remote/blaster setup. It is a generic eHome device which looks like the HP MedaCenter remote without the HP logos. As I have a multiseat client/server installation going back to a single STB for the TV service I use the blaster ports on the IR receiver to blast the channel changes via the STB when I select a channel in the EPG.
Historically, I could never get the IR blasting to work with any of the generally accepted solutions (IRSS etc) so I ended up using some software from LMGestion (LM Remote) with a hacked version of the TVBlaster3.dll for the blasting from the TV server that he provides. Suffice to say he has gone quiet and is not answering any posts on his support forum re the upgrade to 1.2.1.0 as the DLL is considered incompatible.
I have tried replacing the TVBlaster3.dll with the new one posted in these forums for IRSS but as I suspected that does not work.
I have spent hours trying to get IRSS working but like my last attempt before I went the LMRemote route I failed :-( I have also tried editing the DLL via a resource editor to fool the TVServer into thinking the DLL is compatible with TV Server 1.2.1.0 by changing the version number of the DLL. Alas the check for the version number I believe MP uses to identify if a plugin is compatible with the version of MP being used seems to not look at any of the file version information properties you can see via Windows explorer, or maybe MP does not check just the file version information?
Is it possible to configure MP (the TV Server component) to ignore the version numbers for plugins so that I can get my blasting up and running again via a config setting change somewhere, maybe it will not work but at least if this is possible I can test it?
Thanks.
Gary.
MediaPortal Version: 1.2.1.0
MediaPortal Skin: Default Wide
Windows Version: Windows XP SP3
CPU Type: Intel Core 2 Duo 2.2Ghz
HDD: ST340014AS, ST3500820AS
Memory: 4096MB
Motherboard: ASUS P5N-EM HDMI
Video Card: nVidia GeFor 7100/nForce 630i
Video Card Driver: 6.14.12.5896
Sound Card: RealTek HDA/nVidia HDMI Audio
Sound Card AC3:
Sound Card Driver: 5.10.0559/1.00.00
1. TV Card: WinTV PVR 250
1. TV Card Type: Analog
1. TV Card Driver: 1.18.21.23257
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: Hauppage WinTV PVR PCI II
MPEG2 Audio Codec: Klite Codec Pack 6.6.0 (Full)
h.264 Video Codec: Klite Codec Pack 6.6.0 (Full)
Satelite/CableTV Provider: Virgin
HTPC Case: NA
Cooling: 1 x 12cm Case Fan, Generic Intel Cooler
Power Supply: Generic
Remote: Generic RC6 eHome
TV: Hanspree Xv-S
TV - HTPC Connection: HDMI
