BUG: Remote Control Issues with newest Build 3.0.5201.16543

[blade005 185]

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.

 

  :)  

Thanks for the info.  Uninstalled and downloaded from website and MBT is back up and working with remote again.

[blade005 185]

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

Shaun,

 

Just rolled backed to previous version of MBT and confirmed that my standard Windows Media Center Remote with no special mappings is a PLAY only button.

[Shaun 93]

Shaun,

 

Just rolled backed to previous version of MBT and confirmed that my standard Windows Media Center Remote with no special mappings is a PLAY only button.

 

I've MCR play to play/pause in the latest build - let me know if it should be play only

[Shaun 93]

Ok

 

I think I have fixed most of the issues, though I can't guarantee I have got them all.

I've tested with 3 different remotes including a WMC r8 one. Out of interest, All 3 produce different

codes for fwd, rewind keys.

 

I've posted the code and as soon as Luke gets a new build up, I will let you know and

you can get testing.

 

shaun

[foghat 65]

I've MCR play to play/pause in the latest build - let me know if it should be play only

 

Play/Pause please.

[foghat 65]

@@Shaun, great work!

 

With the XML, I assume one can change durations to whatever they want?

[Shaun 93]

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.

 

The next version has has 5 (10 with forward and back) movement commands

 

SmallStepForward    10 seconds

StepForward             60 seconds   

BigStepForward        300 seconds (5 minute)

NextTrack                 Next Chapter

FastForward             2x,4x,8x etc

 

These are currently mapped to the following keys

SmallStepForward    FWD OSD Button,  FF FWD key on remote, Ctrl-Shift-F

StepForward            Ctrl-F

BigStepForward       '>' & '.' keys (back is '<' & '.')

NextTrack               NextTrack OSD Button, NextTrack Remote Key, (no keyboard as yet - how about 'F & 'B' ?)

FastForward          'F', Ctrl-Right Arrow  - double forward speed (REwind Ctrl-Left Arrow)

 

Note FastForward & Rewind are experimental and have no OSD support

 

I tried to stick close to XBMC & Windows Media Center mappings, but we have already diverged with  FFFWD mappings etc, so I had to change them back

 

It is now quite simple to change mapping and we will soon release a build where mappings are read from an external xml file, so everyone can map commands to what ever codes they like - chaos can reign.

[Shaun 93]

@@Shaun, great work!

 

With the XML, I assume one can change durations to whatever they want?

 yes, also most commands have a parameterized based command and non parameterized  short cuts

 

i..e  StepForward(seconds) & stepforward, smallstepforward, Bigstepforward shortcuts (for 10, 30 & 300 seconds)

  FasfForward just uses SetRatioMult(2.0), and we have SetRationAbs(ratio) and SetRationAdd(delta)

 

BUT

 

There are going to be lots of effort required to sort out remote & keyboard mapping issues. So be please be patient while we iron them out,

Edited April 2, 2014 by Shaun

[Shaun 93]

The new apha 3.0.5204.36378 is up - it  should have the changes above. If you could test it please.

[Ghostm 74]

Hmm, i never seem to get these new versions when they are released until a few days later... is it because i live in canada

Edited April 2, 2014 by Ghostm

[ragico 11]

Downloaded and installed the latest version 3.0.5204.43083

No problem with audio channels mapping.

No problem with remote.

No problem with MadVr (smooth motion disabled).

And I tested the new app to play external disks.

Seems to work fine, even if navigation through chapters is not yet implemented.

I tested also a 3D bluray and, as expected, it was played by the internal player and not by TMT6 used as external 3D player.. So, no 3D.

I really want to congratulate again all of you devs for the results you achieve in so little time.

Thank you.

 

  :)    

Edited April 2, 2014 by ragico

[Shaun 93]

Seems to work fine, even if navigation through chapters is not yet implemented.

 

 

I take it you mean Chapter navigation in DVDs ???.

Chapter navigation in online media should work fine.

[Luke 42077]

Yea chapters for external discs will require MBT to examine the media all on it's own. That's nothing major but we'll probably have to leave it for now and come back to it later.

[Shaun 93]

Luke,

 

Is there any option for rolling back to previous version of MBT as we work through these remote control issues? Losing basic functions of a remote render MBT unuseable until it can be investigated.  Appreciate everyone's efforts and the advancement of MBT, but it would be nice to be able to fall back to a previous version of MBT and still enjoy its features as the work continues.

 

Many thanks to all the Devs efforts.

 

I am not answering for Luke, just my private views.

 

Dev builds are alpha releases and by their very nature can be unstable with bugs appearing and disappearing rapidly. If you need the system to be stable, for viewing use, set your automatic update level to "Beta" or better still "Official Release". Only stable dev builds that have been in use for a while and are fairly solid will end up getting promoted to Beta and Official Release. It only takes a few seconds to uninstall MBT and reinstall  with a new automatic update level setting.

 

On the other hand, we want as many people on Alpha as possible so we can get a wide body of feedback as quickly as possible.

 

Its can be challenging to test remote functionality because of the interactions between remotes, drivers &  windows versions (though I have purchased 4 different types of remotes including a WMC RM6 version, so that I can test as widely as possible).

[Shaun 93]

MBT Version: 3.0.5204.43803

Standard Windows Media Center Remote.  

 

No VOLUME control at all. No VOLUME UP, no VOLUME DOWN, no MUTE.  And no OSD controls for volume.

 

Now this is interesting.

 

As far as I can see, MBT has no internal facilities to set, control volume or to mute/unmute. These are set using external windows interactions and MBT responds to the change in volume/mute/unmute events by displaying OSD indications.

 

i.e  Windows catches the volume events from the remote (before they ever get to MBT) and windows changes the global windows volume and MBT just response to global change.

 

You can test this  manually  by using the windows volume slider in the windows volume control and seeing MBT respond.

 

hmm

Edited April 2, 2014 by Shaun

[blade005 185]

The new apha 3.0.5204.36378 is up - it  should have the changes above. If you could test it please.

MBT Version: 3.0.5204.43803

Standard Windows Media Center Remote.  

 

No VOLUME control at all. No VOLUME UP, no VOLUME DOWN, no MUTE.  And no OSD controls for volume.

 

I would prefer the PLAY button to be PLAY only.  At times I like to hit the PLAY button and get a running time at bottom of player screen without the video being paused.  There is a PAUSE button on the remote and would prefer PLAY to remain just that. But, that is just my individual preference. It was how MBT worked before these last few versions with a standard Windows Media Center remote.

 

Also noticed that with this version of MBT the LOGO for the movie is not being displayed in the upper left corner of the video player playback screen.

[Shaun 93]

MBT Version: 3.0.5204.43803

Standard Windows Media Center Remote.  

 

No VOLUME control at all. No VOLUME UP, no VOLUME DOWN, no MUTE.  And no OSD controls for volume.

 

I'll check when I get access to a remote (tonight sydney time).

Can other users please check this for me ??. With any remote.

[Shaun 93]

I would prefer the PLAY button to be PLAY only.  At times I like to hit the PLAY button and get a running time at bottom of player screen without the video being paused.  There is a PAUSE button on the remote and would prefer PLAY to remain just that. But, that is just my individual preference. It was how MBT worked before these last few versions with a standard Windows Media Center remote.

 

This seems to be the consensus and makes more logical sense than the reverse. I will make the change and it will be standard in the next build.

 

SO this will be the behaviour

 

1. Play will be play only.

2. PlayPause will  toggle but not play

[blade005 185]

I'll check when I get access to a remote (tonight sydney time).

Can other users please check this for me ??. With any remote.

Luke,

 

Is there any option for rolling back to previous version of MBT as we work through these remote control issues? Losing basic functions of a remote render MBT unuseable until it can be investigated.  Appreciate everyone's efforts and the advancement of MBT, but it would be nice to be able to fall back to a previous version of MBT and still enjoy its features as the work continues.

 

Many thanks to all the Devs efforts.

[blade005 185]

Now this is interesting.

 

As far as I can see, MBT has no internal facilities to set, control volume or to mute/unmute. These are set using external windows interactions and MBT responds to the change in volume/mute/unmute events by displaying OSD indications.

 

i.e  Windows catches the volume events from the remote (before they ever get to MBT) and windows changes the global windows volume and MBT just response to global change.

 

You can test this  manually  by using the windows volume slider in the windows volume control and seeing MBT respond.

 

hmm

Shaun,

 

Yes. If I take MBT out of full screen mode and use the volume slider in Windows, the Volume is affected in MBT and I can see the OSD for Volume in the upper right corner being adjusted. I can even use the remote for volume UP and DOWN and it works.  The issue is when MBT is made the screen in control, whether in full screen or windowed, the volume commands from the remote are not recognized.  At least that is what I am seeing on my end.

[Shaun 93]

OK

 

I spent a bit of time looking at the volume issue and I can't replicate the problem - 

 

I tested

 

1. On maximised and non maximised 

2. RC6 remote (windows media player) 

3. Non windows remote

4. Windows volume bar

5. even if another app was in front and had the focus

 

In every case the volume events work correctly. All apps, independant of having focus, get notified of volume events and

we respond by displaying  the volume osd.

 

blade005, do me a favour and run the following check

 

1. start playing a movie

2 make sure you have audible sound

3. maximise (so you get into the state where there is no OSD for volume events)

4. use the remote to change the volume

 

Does the volume change ? i.e is a display/osd issue ?

 

Does anyone else have the problem ?

 

Can people check for me that the volume control is working from the remote when they are full screen (with 3.0.5206.37273 or later)   ?

 

While doing tests above, I did find another bug  that been reported but not replicated. If you alt-tab out of MBT and then alt-tab back, you lose remote and keyboard focus. This is a great find, I have been trying to get a repeatable test case for this issues for weeks. see Issues #147 - MBT loses remote and keyboard focus after Alt-Tab - https://github.com/MediaBrowser/MediaBrowser.Theater/issues/147

 

 

[ragico 11]

I take it you mean Chapter navigation in DVDs ???.

Chapter navigation in online media should work fine.

Yes, DVD and Blu ray. Online media no problem.

[ragico 11]

Can people check for me that the volume control is working from the remote when they are full screen (with 3.0.5206.37273 or later)   ?

 

 

 

 

The latest version I can download here is 3.0.5205.37079 and can assure that there are no volume up/down/mute issues. All clearly visible on the screen either maximazed or not..

Use an RC6 remote from Pinnacle.

Edited April 3, 2014 by ragico

[blade005 185]

 

OK

 

I spent a bit of time looking at the volume issue and I can't replicate the problem - 

 

I tested

 

1. On maximised and non maximised 

2. RC6 remote (windows media player) 

3. Non windows remote

4. Windows volume bar

5. even if another app was in front and had the focus

 

In every case the volume events work correctly. All apps, independant of having focus, get notified of volume events and

we respond by displaying  the volume osd.

 

blade005, do me a favour and run the following check

 

1. start playing a movie

2 make sure you have audible sound

3. maximise (so you get into the state where there is no OSD for volume events)

4. use the remote to change the volume

 

Does the volume change ? i.e is a display/osd issue ?

 

Does anyone else have the problem ?

 

Can people check for me that the volume control is working from the remote when they are full screen (with 3.0.5206.37273 or later)   ?

 

While doing tests above, I did find another bug  that been reported but not replicated. If you alt-tab out of MBT and then alt-tab back, you lose remote and keyboard focus. This is a great find, I have been trying to get a repeatable test case for this issues for weeks. see Issues #147 - MBT loses remote and keyboard focus after Alt-Tab - https://github.com/MediaBrowser/MediaBrowser.Theater/issues/147

 

 

shaun,

 

Tested with 3.0.5025.37079 and it seems to be a windows focus issue.  Below are the steps I walked through to test.

 

1. Open MBT in full screen mode and start playing video.  No VOLUME control and no VOLUME OSD displayed.  Volume is not increased or decreased with remote. Use mouse to click on screen once video is started and VOLUME control and VOLUME OSD are displayed. (Same behavior is exhibited if MBT is started in a windowed mode and not full screen.)

2. Take MBT out of full screen mode while video is still playing.  VOLUME control works and VOLUME OSD is displayed.

3. Put MBT back in full screen mode while video is still playing. VOLUME control works and VOLUME OSD is displayed.

4. STOP video in full screen mode in MBT. Restart video and no VOLUME control and no VOLUME OSD is displayed. (Same behavior is exhibited if MBT is in windowed mode.)

 

I've tested this scenario with both a Windows MCE RC6 remote and with keyboard controls on a laptop using Volume UP and DOWN with same behavior exhibited. It seems that I have to mouse click on a playing video screen to get VOLUME controls to work (Remote or keyboard controls) and once the video is stopped and restarted a mouse click on the playing video screen is needed to reclaim VOLUME control.

 

Two (2) of my three (3) systems or on the version of MBT stated above and are exhibiting this behavior.  One system is still on 3.0.5182.20892 and does exhibit any of these VOLUME issues.  Trying to eliminate anything that might be system specific to my setup, but that doesn't seem to be the case.

 

I would be happy to test further and provide additional information if necessary. Just let me know.

 

Thanks so much for your responses and support.

[foghat 65]

How do you get this update? I have my update level set to dev. And have auto run at start up selected.

 

When I go into settings it tells me I'm up to date. But version is showing as 3.0.5201.16543