[solved] MCE custom mapping lost (1 Viewer)

[ssenyer]

My MCE remote worked perfectly since 5 years until tonight. I just want you ask same question.

Why fix what ain't broken ?

 

[Stéphane Lenclud]

My MCE remote worked perfectly since 5 years until tonight. I just want you ask same question.

Be specific and open a new thread describing your problem and providing logs please.

 

[Stéphane Lenclud]

Well, I wouldn't go that far, but the new skin and the changes to the remote handling are really hard to swallow.

If you have specific issues with remote handling and skin please open dedicated threads describing them I'm sure the community will try to help you out.

 

[spachti]

Thanks for the offer. But since I don't like that "candy store" skin in 1.13 anyway, I might as well stay with 1.12 and don't have to go through the hassle.

 

[Stéphane Lenclud]

Thanks for the offer. But since I don't like that "candy store" skin in 1.13 anyway, I might as well stay with 1.12 and don't have to go through the hassle.

Absolutely, not upgrading is a perfectly valid option.
Though your extensive feedback would be much welcome so that we can take it into account for the next releases.
I have not tried the new skin yet, my production environment is using a third party skin called StreamedMP.
However we would never be able to please everyone with a skin since it's very much a matter of taste.

I still would very much welcome more feedback concerning your remote issues in 1.13.

 

[HTPCSourcer]

Thanks for the offer. But since I don't like that "candy store" skin in 1.13 anyway, I might as well stay with 1.12 and don't have to go through the hassle.

1.13 is not deactivating the existing skins. You can continue using it.

 

[spachti]

Thanks for the offer. But since I don't like that "candy store" skin in 1.13 anyway, I might as well stay with 1.12 and don't have to go through the hassle.

Absolutely, not upgrading is a perfectly valid option.
Though your extensive feedback would be much welcome so that we can take it into account for the next releases.
I have not tried the new skin yet, my production environment is using a third party skin called StreamedMP.
However we would never be able to please everyone with a skin since it's very much a matter of taste.

I still would very much welcome more feedback concerning your remote issues in 1.13.

Well, where to start?
Ok, first the sarcasm, since you seem to like that.
Why should I piss off my better half with a skin even I don't like myself?
Second, I'm using the old HP transceivers including the remotes with all my MePo computers. Never had a problem with the old MCE settings. I've tried the new HID part once.
That didn't work very well, better it didn't work at all. I'm in the US and use the blaster functions exclusively.
So, now to the serious part, at our age, which is probably more than twice the age of the average user here, you like to stay with stuff that works. I do understand that the devs here are doing the job foremost for their own entertainment and their needs. And I also know that people have different tastes and priorities. That's why I kept my response low and didn't complain.

Edit:
After re-reading your posting again, I would like to take the "sarcasm" remark back. I've misread a part.
Sorry.

 

[HTPCSourcer]

I understand the frustration.

Why should I piss off my better half with a skin even I don't like myself?

As I said, you are free to keep the old skin. We should have noted this more explicitely in the release news.
@catavolt , could you please amend the release news accordingly if you have a minute?

Second, I'm using the old HP transceivers including the remotes with all my MePo computers. Never had a problem with the old MCE settings. I've tried the new HID part once.
That didn't work very well, better it didn't work at all. I'm in the US and use the blaster functions exclusively.

The change is very technical and invisible. Actually the HID handling is much more logical but I certainly understand that you challenge the need for it. AFAIK the HP transceivers are perfect eHome devices, however, I a m not at all familiar with the blaster side of MePo and hence won' make any judgement here.

...at our age, which is probably more than twice the age of the average user here, you like to stay with stuff that works.

It would not be very difficult to redefine correct settings in the config. I have to confess that we did discuss (many months ago) about any automated import of existing MCE mappings on to the Generic HID definitions, but it got lost in the process. We'll take up the subject again to see if we can either provide an automatic import or at least a more detailed explanation of how to migrate existing customizations to the HID side..

It is understandable that you "like to stay with stuff that works". In that case you may want to apply caution before upgrading a system that is acting to your needs.

I do understand that the devs here are doing the job foremost for their own entertainment and their needs.

That may be true for some devs but definitely not for everybody. In this specific case Stephane has upgraded the remote handling to be fully Microsoft-compliant. It solves a lot of other issues and the only - yet unpleasant - thing needed, is to possibly redefine the different keys in the remote settings. IN my specific case I have never changed the standard MCE settings of MePo, therefore I did not even noted any change.

 

[Stéphane Lenclud]

Ok, first the sarcasm, since you seem to like that.

I don't mind sarcasm really, however there were none in my above comments I can assure you.

Why should I piss off my better half with a skin even I don't like myself?

Just pick one you like really there is nothing in MP 1.13 that prevents you to do just that.

I'm using the old HP transceivers including the remotes with all my MePo computers.

References, pictures, links, please. I don't think you provided any system specs in your profile, you may want to fill it.

I've tried the new HID part once.
That didn't work very well, better it didn't work at all.

Did you provide feedback back then?

I'm in the US and use the blaster functions exclusively.

Interesting, not sure how the new handler would break that though.

I do understand that the devs here are doing the job foremost for their own entertainment and their needs

Surely you mean "their needs for entertainments" You did ask for sarcasm did you not?

That's why I kept my response low and didn't complain.

The MediaPortal dev team do need feedback from the community to make the right decisions.


If you want us to try and understand why your remote is not working with HID please provide the information requested above.
You could also try this HID demo application and see if it picks up your remote buttons.
Enabling extensive logs from the HID configuration and providing logs could also help.

If there is no way to get it to work with HID we will be happy to bring back the MCE handler in an upcoming release.

 

[mm1352000]

Yeah, I'm confused about the HID comments as well. Specifically, these two comments seem to contradict:

Second, I'm using the old HP transceivers including the remotes...

...and use the blaster functions exclusively.

@spachti
When you say you're using the blaster functions exclusively it makes it sound like you're not using the receiver at all, but that seems to disagree with the "...including the remotes..." comment.

Both the MCE and HID handlers in MP were/are solely for receiving input from a remote. If you are only using the HP unit as a receiver then getting a MCE-compatible remote working should be as simple as enabling the HID handler. If that doesn't work, Stéphane is the right guy to help you, but you'll need to provide all the info he requested.

If you are only using the HP unit as a blaster then the advent of MP 1.13 should have been uneventful. As you probably know, MCE-compatible blasters like your HP unit are supported via IRSS's TV3 Blaster plugin for TV Server. Nothing in TV Server has changed to break that.

Finally, if you are using the HP unit as both receiver and blaster then I have two guesses about why your remote has stopped working.

Theory 1
If two programs - in this case MP and IRSS - attempt to use/control either or both the receiver and/or blaster at the same time then either or both the receiver and/or blaster may not work. It's for this reason that I thought the standing recommendation was to disable MP's MCE remote handler if using IRSS + MCE-compatible transceiver, and instead use IRSS's MP Control plugin for remote control support. I would have assumed that the same recommendation [to disable] applies with MP's new HID handler. In other words, I'm saying that my understanding is that there is and was no guarantee that either MP's new HID handler or old MCE remote handler would co-exist happily with IRSS. What definitely should work is IRSS handling both receiver and blaster via its MP Control plugin for MediaPortal and TV3 Blaster plugin for TV Server respectively.

Continuing this line of thought...

Theory 2
Whether recommended or not, it is common to use IRSS and its plugins to handle both receiver and blaster. If we assume that this is what you were doing (ie. you were mistaken about using MP's MCE remote handler and were actually using IRSS's MP Control plugin) then please be aware there is a new and known incompatibility between MP 1.13 (both PR and final) and the MP Control plugin. This incompatibility would have caused the plugin to be disabled and your remote to stop working. A new [unofficial] version of IRSS has been provided to take care of that incompatibility. Update to the latest version of IRSS and hopefully the remote and blaster will be working again.


So in short: if either of the above theories are correct, the suggested solution is to install and configure the latest unofficial IRSS release.