Jump to content

BUG: Remote Control Issues with newest Build 3.0.5201.16543


Recommended Posts

blade005
Posted

Version Information:

MBS: 3.0.5192.19560

MBT: 3.0.5201.16543

 

Remote: Windows Media Center Remote

 

After update to latest MBT build on two machines there are remote buttons that are no longer functioning. Below is what works and what does not on my systems.  I still have one machine on the previous MBT build and have verified that all remote buttons work properly on that build.

 

FUNCTIONING PROPERLY:

Play Button

Pause Button

Volume Button

Mute Button

 

NOT FUNCTIONING PROPERLY:

Stop = No response.

FFWD / REWIND = No response.

SKIP FWD / SKIP Back = Ignoring chapter markers and jumping forward or backward in 10 minute intervals.

* (Info) Button = No response.

 

For the Remote Buttons that are not functioning properly, if you use a mouse to select the ON SCREEN buttons, these are functioning properly.  Seems to be an issue with remote control commands either not getting to MBT or in the instance of SKIP buttons, incorrect commands being sent.

 

 

blade005
Posted

Luke, 

 

Any way to fall back to previous MBT version while this is being looked at?

Posted

+1

same problem with the same buttons. 

Posted (edited)

+2

same problem here.

Also, I think that the audio channel mapping is wrong.

The back speakers are mapped as surround speakers and viceversa.

In MBC no mapping problem.

 

And the * button no longer allows to open the OSD to change audio track or subtitle.

And Madvr causes a bad judder however you configure it.

Must be disabled all the way.

I apologise for my English.

 

:rolleyes:

Edited by ragico
Posted

Yep. I have same issues as well. Except play/pause does not work for me. I have had to revert back to my 'space' key mapping for the play/pause functionality.

 

Really hope this can be addressed soon. Not being able to stop is particularly problematic.

 

The normal menu navigation/select keys still work fine.

 

+1 on wondering if there is any way to get back to the previous version.

 

And is there any sort of change log as to what this latest version brings?

Posted (edited)

+2

same problem here.

Also, I think that the audio channel mapping is wrong.

The back speakers are mapped as surround speakers and viceversa.

In MBC no mapping problem.

 

And the * button no longer allows to open the OSD to change audio track or subtitle.

And Madvr causes a bad judder however you configure it.

Must be disabled all the way.

I apologise for my English.

 

:rolleyes:

 

Just curious what you mean the audio channels are mapped wrong? Wouldnt this be a setting in lav filters (which you setup yourself?) If you give me more info i can help you narrow down this issue. I just tested with mine and 5.1 audio comes through the proper 5.1 channels, they are not coming from back channels.

 

Also for madvr do you use smooth motion? If so we asked that it not be enabled by default, some of us dont like it, so if you use that, you will need to enable smooth motion in madvr if you have not enabled it in madvr, as mbt will no longer force you to use it like before. 

 

Although that may not be your issue. If you experience bad judder that may be to other problems. I cant get it working smoothly on one of my pc's personally. It seems to require more horsepower in mbt then it does mpc-hc at the moment.

Edited by Ghostm
Posted (edited)

@@Ghostm

 

a) I use both MBT and MBC on my HTPC trough an Onkyo Receiver and to a Panasonic plasma TV.

B) I dislike bitstream and prefere decoding the audio in the HTPC which is fitted with a R9 270X radeon.

c) In MBC I use MPC-HC as the external player and the lav audio decoder has got the default settings and no problem regarding the channels mapping. (my system is 7.1)

d) In MBT I use the same settings (default) that I use in MBC and the rear speakers are feeded with the signal which should go to the surround speakers.

e) The problem has arised with the last version of MBT (updated yesterday).

 

As far as MadVr is concerned, I dislike the smooth motion so it's disabled in both apps (MBT and MBC).By the way, I did try all the various settings available for smooth motion at no avail. The judder (sometimes very bad) is always there. I got no judder at all with the previous versions of MBT. This behaviour started yesterday, after the update to the current version.

Of course no problem in MBC (smooth motion disabled).

I would like to roll back to the previous version of MBT wich, for me and in my system, was almost flawless.

Sorry for my English.

 

 

Edited by ragico
Guest VentingBow5
Posted

Same problem here. I thought it was my new Intel D54250WYK that was the issue since my ASRock 330 HT worked fine but I am glad to hear it has something to do with MBT. For me the same keys are not working: stop, *, FFWD / REWIND, SKIP FWD / SKIP Back.

Posted (edited)

Version Information:

MBS: 3.0.5192.19560

MBT: 3.0.5201.16543

 

Remote: Windows Media Center Remote

 

After update to latest MBT build on two machines there are remote buttons that are no longer functioning. Below is what works and what does not on my systems.  I still have one machine on the previous MBT build and have verified that all remote buttons work properly on that build.

 

FUNCTIONING PROPERLY:

Play Button

Pause Button

Volume Button

Mute Button

 

NOT FUNCTIONING PROPERLY:

Stop = No response.

FFWD / REWIND = No response.

SKIP FWD / SKIP Back = Ignoring chapter markers and jumping forward or backward in 10 minute intervals.

* (Info) Button = No response.

 

For the Remote Buttons that are not functioning properly, if you use a mouse to select the ON SCREEN buttons, these are functioning properly.  Seems to be an issue with remote control commands either not getting to MBT or in the instance of SKIP buttons, incorrect commands being sent.

 

Apologies, these are problems with the the new input mangement infrastructure

 

1. Stop = No response. - fixed, should be in next build

2. FFWD / REWIND = No response - I'll look into this

3. SKIP FWD / SKIP Back = Ignoring chapter markers and jumping forward or backward in 10 minute intervals.

     Yea, my fault, I changed the behaviour to match XBMC, I'll change it back

4. * (Info) Button = No response. I'll look into this

 

 Remote Buttons that are not functioning properly -I'll look into this

Yea this is an issues, some remotes just simulate key codes and some send APPCommands.  I'll make sure I test with as many remotes as possible in future (its a bit of a pain and I have to add/remove drivers and reboot between testing with different remotes)

 

I should be able to get these all fixed tonight and into the next build

 

shaun

Edited by Shaun
  • Like 4
Posted

Apologies, these are problems with the the new input mangement infrastructure

 

1. Stop = No response. - fixed, should be in next build

2. FFWD / REWIND = No response - I'll look into this

3. SKIP FWD / SKIP Back = Ignoring chapter markers and jumping forward or backward in 10 minute intervals.

     Yea, my fault, I changed the behaviour to match XBMC, I'll change it back

4. * (Info) Button = No response. I'll look into this

 

 Remote Buttons that are not functioning properly -I'll look into this

Yea this is an issues, some remotes just simulate key codes and some send APPCommands.  I'll make sure I test with as many remotes as possible in future (its a bit of a pain and I have to add/remove drivers and reboot between testing with different remotes)

 

I should be able to get these all fixed tonight and into the next build

 

shaun

 

Thanks.

 

Please look at the play/pause as well. Something changed there as it is no longer working for me. This issue existed a number of builds ago as well - it seemed to work for some and not others. I don't know what build this was fixed in, but something changed with this latest one. fwiw I am using mce controller to send commands and it mapped to the Play Pause Toggle command.

Posted (edited)

@@Ghostm

 

a) I use both MBT and MBC on my HTPC trough an Onkyo Receiver and to a Panasonic plasma TV.

B) I dislike bitstream and prefere decoding the audio in the HTPC which is fitted with a R9 270X radeon.

c) In MBC I use MPC-HC as the external player and the lav audio decoder has got the default settings and no problem regarding the channels mapping. (my system is 7.1)

d) In MBT I use the same settings (default) that I use in MBC and the rear speakers are feeded with the signal which should go to the surround speakers.

e) The problem has arised with the last version of MBT (updated yesterday).

 

As far as MadVr is concerned, I dislike the smooth motion so it's disabled in both apps (MBT and MBC).By the way, I did try all the various settings available for smooth motion at no avail. The judder (sometimes very bad) is always there. I got no judder at all with the previous versions of MBT. This behaviour started yesterday, after the update to the current version.

Of course no problem in MBC (smooth motion disabled).

I would like to roll back to the previous version of MBT wich, for me and in my system, was almost flawless.

Sorry for my English.

 

 

A dev would have to correct me but audio will be handled by lav filters as well in mbt, so it shouldnt be any different then mpc-hc. I tested this with latest version last night and mine was fine. I am bitstreaming, but 5.1 audio went to the proper surround channels (the back channels were muted as they should be) when i played a 7.1 track the audio went to then went to the proper back channels as well. I have never heard anyone else have this problem so i am unsure what it could be on your end. Could it also be a windows audio setting since your using decoding on the pc?

 

You may have to give me more details what your settings are, when you mention you let the htpc decode are you using reclock as well? Or just lav? Either way this sounds like a lav issue as i dont think mbt uses anything for audio other then lav filters. As for mpc-hc maybe your using mpc-hc internal preinstalled lav filters? Giving a different result. I think mbt installs separate external lav filters. Im really unsure at this point though as i have not encountered this.

 

Of course it could be none of these and it could be simply not happening for me because i bitstream. But i dont know what your settings are for decoding in lav, or if you use reclock ect... but as far as i know mbt just relies on lav filters to produce audio, again a dev would have to confirm this or correct me if im wrong.

 

Personally on one of my pc's I cannot get madvr running smoothly, i need a more powerful card but an R9 should be plenty good enough. If it was working previously in mbt i am unsure what it could be unless somethings changed recently. The only thing i know of that was changed was smooth motion setting, but it sounds like you dont like smooth motion either like me. 

 

 

 

Just to make sure were on the same version what version are you on?

Edited by Ghostm
Posted

looking at the old code it it not clear what is the behaviour different between  FFWD / REWIND  &  SKIP FWD / SKIP Back


It seems to me that the behaviors were


 


SKIP FWD / SKIP Back  => next/previous chapter - no chapters, no actions


FFWD / REWIND  => forward/back 10 seconds  


 


is this correct ?


Posted

Should the play button (just play) act only as Play  (i.e if its playing don't pause) or as PlayPause

Posted (edited)

This might be a stupid comment (excuse me in that case), but shouldn't all this functionality just be like before?

 

Edit Oh, ok. Just noticed your post further up that it is not always clear. Sorry. :)

Edited by njoak
Posted

All

 

Right I have fixed most of the keyboard mapping issues, but I want to do a bit more testing with the Windows Media Center remote.

So it will another day or so before I post the update. Sorry for the delay.

  • Like 1
Posted

 

looking at the old code it it not clear what is the behaviour different between  FFWD / REWIND  &  SKIP FWD / SKIP Back

It seems to me that the behaviors were

 

SKIP FWD / SKIP Back  => next/previous chapter - no chapters, no actions

FFWD / REWIND  => forward/back 10 seconds  

 

is this correct ?

 

 

Yes, this is correct.  Though I'd love to see a skip forward 30 seconds, skip back 10.  Skipping forward 10 seconds just isn't enough, imo.

blade005
Posted

 

looking at the old code it it not clear what is the behaviour different between  FFWD / REWIND  &  SKIP FWD / SKIP Back

It seems to me that the behaviors were

 

SKIP FWD / SKIP Back  => next/previous chapter - no chapters, no actions

FFWD / REWIND  => forward/back 10 seconds  

 

is this correct ?

 

Shaun,

 

Correct on your behavior descriptions above.

 

PLAY button was only acting as a PLAY button before.  No PLAY / PAUSE.

Posted

Should the play button (just play) act only as Play  (i.e if its playing don't pause) or as PlayPause

 

It acts as a playpause

Posted

Shaun,

 

Correct on your behavior descriptions above.

 

PLAY button was only acting as a PLAY button before.  No PLAY / PAUSE.

 

It was acting as a play pause for me.

blade005
Posted

Yes, this is correct.  Though I'd love to see a skip forward 30 seconds, skip back 10.  Skipping forward 10 seconds just isn't enough, imo.

 

At first I wasn't thrilled with 10 second FORWARD, was used to 30 seconds FORWARD and 10 seconds BACK from previous setup.  But, the 10 second FORWARD did become more useful over time when watching sporting events.  30 second jump could get you right past something significant on a football pitch. But, I could live with either option.

blade005
Posted

It was acting as a play pause for me.

Really? It was only a PLAY for me. But, I could live with either one.

Posted

At first I wasn't thrilled with 10 second FORWARD, was used to 30 seconds FORWARD and 10 seconds BACK from previous setup.  But, the 10 second FORWARD did become more useful over time when watching sporting events.  30 second jump could get you right past something significant on a football pitch. But, I could live with either option.

Fair enough.

 

30 seconds is great for skipping tv show intros - especially when they are 2 minute+ intros like many of the hbo ones.  That is why the 10 second back works well with the 30 second forward.  If you go too far forward, just have to hit back once or twice.

 

Really? It was only a PLAY for me. But, I could live with either one.

 

Maybe there were two mappings for play.  The mce mapping I was using was playpause toggle.  And it did just that.

Posted

I did uninstall the latest version 3.0.5201.16543 and download and install again.

To my surprise the downloaded version is 3.0.5182.20892 (I think a roll back to the previous version.)

Now all is ok. No more wrong audio channels mapping, remote control working again (apart pause button that sometimes works and sometimes dont work).

Also MadVr working again without judder (smooth motion disabled).

Thank you.

 

:)  :) :)  

Posted

I did uninstall the latest version 3.0.5201.16543 and download and install again.

To my surprise the downloaded version is 3.0.5182.20892 (I think a roll back to the previous version.)

Now all is ok. No more wrong audio channels mapping, remote control working again (apart pause button that sometimes works and sometimes dont work).

Also MadVr working again without judder (smooth motion disabled).

Thank you.

 

:)  :) :)  

 

That would explain why I couldn't get the auto update to update to the latest version on my other machine.  They must have killed the 16543 version.  If there is not a new release soon, I will uninstall and reinstall on the problem machine as well.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...