BUG: Remote Control Issues with newest Build 3.0.5201.16543

[ragico 11]

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

You have to uninstall and then download/install the new version.

 

[Luke 42077]

Or you just wait patiently and it will come to you.

[foghat 65]

OK[/size]

 

 

 

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)   ?

 

 

 

 

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.

I too am not sure how to get the latest version, but you are testing against a version older than what Shaun is asking to test against, so....

Edited April 3, 2014 by foghat

[foghat 65]

Or you just wait patiently and it will come to you.

I need to wait with mbt open I assume? I have had things set to dev build for a few days now and have tried opening and closing many times - have even watched shows during that time - but am still on the original version that initially introduced the remote issues.

 

I may just re-download. Just have a few settings that I've changed and have things working great (aside from remote issue). So I'd rather not reinstall.

[Shaun 93]

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.

 

I'll do some more testing to see If I can replicate your scenario. It should not  be related to focus/active issues as all apps get Volume event regardless of their focus state. I will follow your scenarios exactly and see if I can duplicate the issue.

 

I'll also see if I can fix the other know focus bug, you never know it might fix this issue. 

If other people could continue to test for this issue that would be great. It's only worthwhile testing if your are on 3.0.5025.37079  or latter.

[Shaun 93]

 

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.)

 

 

How are you starting MBT ? mouse ? system boot ?

How do you start playing the video ? mouse ? remote ? what key do you press ? Are the arrow keys working ?

[blade005 185]

I need to wait with mbt open I assume? I have had things set to dev build for a few days now and have tried opening and closing many times - have even watched shows during that time - but am still on the original version that initially introduced the remote issues.

 

I may just re-download. Just have a few settings that I've changed and have things working great (aside from remote issue). So I'd rather not reinstall.

foghat,

 

I uninstalled and re-installed MBT, but did not get the latest version that Shaun asked me to test against.  FYI.

[blade005 185]

How are you starting MBT ? mouse ? system boot ?

How do you start playing the video ? mouse ? remote ? what key do you press ? Are the arrow keys working ?

Will keep this to the scenario I use 99% of the time on my HTPC units.

 

1. Start MBT with an icon on Windows launch bar with mouse.

 

2. ARROW / NAVIGATE keys on remote all work and allow me to move around the MBT screens.

 

3. Select a video. Navigate to the PLAY button on screen and press the OK button on MCE Remote.  Video begins playing.  This is where I don't have VOLUME control unless I take the mouse and click on the screen while video is playing.  If I stop the video I no longer have VOLUME control. If I restart the video I don't have VOLUME control unless I mouse back onto the screen of playing video and click again.

[Shaun 93]

Will keep this to the scenario I use 99% of the time on my HTPC units.

 

1. Start MBT with an icon on Windows launch bar with mouse.

 

2. ARROW / NAVIGATE keys on remote all work and allow me to move around the MBT screens.

 

3. Select a video. Navigate to the PLAY button on screen and press the OK button on MCE Remote.  Video begins playing.  This is where I don't have VOLUME control unless I take the mouse and click on the screen while video is playing.  If I stop the video I no longer have VOLUME control. If I restart the video I don't have VOLUME control unless I mouse back onto the screen of playing video and click again.

 

 

I've just spent an hour trying to replicate your volume issue. I used the scenario above (and many others) and I can't replicate the issue.

I'll give it a  try with some other remotes and on a couple of different machines. I'll keep plugging away and see I can find something.

Remind me - when did this start happening ? Any more details you think may help ?

 

I need other users to try the above scenario and give feedback.

Luke ? Chris ? Tom ? Mark ?

 

I'm going to see if I can fix the focus issue I did find, who knows, it might make a difference.

[blade005 185]

I've just spent an hour trying to replicate your volume issue. I used the scenario above (and many others) and I can't replicate the issue.

I'll give it a  try with some other remotes and on a couple of different machines. I'll keep plugging away and see I can find something.

Remind me - when did this start happening ? Any more details you think may help ?

 

I need other users to try the above scenario and give feedback.

Luke ? Chris ? Tom ? Mark ?

 

I'm going to see if I can fix the focus issue I did find, who knows, it might make a difference.

Shaun,

 

Thanks for all of your effort looking into this. I really appreciate it.

 

This issue seemed to present itself after version 3.0.5182.20892 of MBT.  I still have one system running 5182.20892 and don't have any volume issue.  After that version is when the issue presented itself.

[Shaun 93]

This issue seemed to present itself after version 3.0.5182.20892 of MBT.  I still have one system running 5182.20892 and don't have any volume issue.  After that version is when the issue presented itself.

 

I see if I can figure out what was the last commit ti that corresponded to and  have a look at the code

[foghat 65]

@@Shaun

 

Finally go 5205.37079 installed.  PlayPause, stop, and skip 10 seconds now operate as they did before.  However my chapter skip (mapped to MCE - skipfwd, skipback) now skips forward/back 1 minute instead of to the next chapter, as it did before these remote issues popped up.

 

I have resolved this by changing my chapter skip mappings to VK_MEDIA_NEXT_TRACK and VK_MEDIA_PREV_TRACK.

 

So, from my pov, remote is working well now.  Thanks.

[Shaun 93]

 

The MCE skipfwd  & skpback don't generate  keyboard events of  VK_MEDIA_NEXT_TRACK but instead generate a APPCOMMAND_MEDIA_NEXTTRACK event.

One is a keyboard event (i.e if you have a multimedia keyboard with skipnext & skipprev Keys) and the other an appcommand.

 

It does not really matter as we map both the keyboard event VK_MEDIA_NEXT_TRACK & the  appcommand APPCOMMAND_MEDIA_NEXTTRACK. to the same MBT Command                 "Command.NextTrack"

 

Out of interest, what was it mapped to before ?

[Luke 42077]

They should be next/prev chapter whne video is playing

[foghat 65]

What mce calls skipfwd and skipback used to control next/prev chapter. Now they skip in 1 minute intervals.

 

The actual command being passed by mce for skipfwd and skipback is:

 

<SendInput Cmd="skipback" vk="66" Shift="false" Ctrl="true" Alt="false" />

<SendInput Cmd="skipfwd" vk="70" Shift="false" Ctrl="true" Alt="false" />

[blade005 185]

I see if I can figure out what was the last commit ti that corresponded to and  have a look at the code

MBT has now forced an update on my one system that still had 3.0.5182.20892 (set to Official Release) and the Volume control issue is still present.  Is there no option to stay on a previous version of MBT until this can be worked out?  Until then, MBT is no longer an option for me to enjoy as a preferred viewing option. 

[Shaun 93]

The volume issue is my #1 bugs right now. I'll see what we can find as quickly as possible.

[Shaun 93]

Could anyone with the volume issue please

 

1. set mbt to debug logging

2. run a volume issue scenario

3. send me the logs

 

or post here

[blade005 185]

Could anyone with the volume issue please

 

1. set mbt to debug logging

2. run a volume issue scenario

3. send me the logs

 

or post here

Shaun,

 

Ran the following scenario.

 

1. Started MBT and tried Volume Control on main screen. Result: NO RESPONSE

2. Selected Video and selected PLAY. Tried Volume Control. Result: NO RESPONSE

3. Moused over playing video screen and clicked on it. Tried Volume Control. Result: RESPONDED PROPERLY

4. Stopped video and tried Volume Control. Result: NO RESPONSE

5. Re-started video and tried Volume Control. Result: NO RESPONSE

6. Moused over playing video screen and clicked on it. Tried Volume Control. Result: RESPONDED PROPERLY

7. Stopped video and tried Volume Control. Result: NO RESPONSE

 

Attached is log file.  http://paste2.org/vGNU7Wwh

 

Let me know if there are other scenarios or testing that would assist.

 

Thanks for all of your efforts.

[Shaun 93]

Shaun,

 

I didn't know if this might help, but thought I would provide the information just in case.  I fell back to the previously working MBT version 3.0.5182.20892 and ran the same scenario as above with the VOLUME UP and DOWN working PROPERLY in all scenarios.  Not sure if there is something between the two logs that might assist with your discovery efforts.

 

MBT Version 3.0.5182.20892 log:  http://paste2.org/Mkj9avaU  (Volume control working PROPERLY in all MBT screen tests.)

 

Very Very Useful !.

 

I'm making a little  progress now we have the logs.

Can you (and anyone with the same problem  send me

 

1. The make and model of your remote control

2. Details of the IR Receiver - is it built in or via a USB port

3.  OS

4. System hardware - high level details ie dell, ASUS, homebuilt

 

regards

shaun

[blade005 185]

Shaun,

 

Ran the following scenario.

 

1. Started MBT and tried Volume Control on main screen. Result: NO RESPONSE

2. Selected Video and selected PLAY. Tried Volume Control. Result: NO RESPONSE

3. Moused over playing video screen and clicked on it. Tried Volume Control. Result: RESPONDED PROPERLY

4. Stopped video and tried Volume Control. Result: NO RESPONSE

5. Re-started video and tried Volume Control. Result: NO RESPONSE

6. Moused over playing video screen and clicked on it. Tried Volume Control. Result: RESPONDED PROPERLY

7. Stopped video and tried Volume Control. Result: NO RESPONSE

 

Attached is log file.  http://paste2.org/vGNU7Wwh

 

Let me know if there are other scenarios or testing that would assist.

 

Thanks for all of your efforts.

Shaun,

 

I didn't know if this might help, but thought I would provide the information just in case.  I fell back to the previously working MBT version 3.0.5182.20892 and ran the same scenario as above with the VOLUME UP and DOWN working PROPERLY in all scenarios.  Not sure if there is something between the two logs that might assist with your discovery efforts.

 

MBT Version 3.0.5182.20892 log:  http://paste2.org/Mkj9avaU  (Volume control working PROPERLY in all MBT screen tests.)

[Shaun 93]

I have found and fixed the remote volume bug (I hope). It only affected users with multimedia keyboards and remotes that generated APPCommands for media control events (a small subset).

 

After I thoroughly test the fix, I'll update Luke and he will then push a new dev build. I expect it will take a day or so.

 

see Issue #150

 

https://github.com/MediaBrowser/MediaBrowser.Theater/issues/150

[Shaun 93]

confirmed as fixed in 3.0.5212.14381

[DevonLad 1]

This is really with the aim of providing more information on Remote Control function issues, rather than them being a big problem for me.

 

I am using MBT 3.0.5214.16310 on a long-term HTPC that was running Media Center and MB2 before, with the remote working as expected.  The HTPC has a built-in IR Sensor and uses iMon software to handle the IR commands - this is where the problem is for me.  I am using a Harmony Remote, using the standard Media Center commands, which still works perfectly in Media Center.  However, in MBT I get these scenarios:

 

If I use the iMon Sensor, the OK, Arrows and Return/Back keys all work, but Play, Pause, Stop and Chapter Forward/Back do not work at all.

If I plug-in a Microsoft Media Center IR Sensor (and disable iMon), all of those functions above work properly, except the Chapter Forward, which works fine with TV Series (MKVs, if that makes a difference), but NOT with my Movies (VIDEO_TS), where it rather oddly makes the video go back, not forward.

 

I can't update the iMon software, as AFAIK, they stopped developing it quite a while back.  Having an update might not solve anything anyway, because all of the IR commands, via iMon, work as expected in MCE, just not in MBT.

 

So:

(1) this might help someone else who uses iMon and is having remote problems

(2) it might help the MBT team to identify some issues and causes

(3) at some point, MBT might be made to function exactly as MCE does, so that I can go back to using my built-in iMon Sensor. (I know iMon is, and always has been flaky, but I don't want to buy a new HTPC Case)

 

If any other information is useful, please let me know.

Edited April 12, 2014 by DevonLad

[Shaun 93]

I don't have a imon so I can't test the specific key issues. If you turn on debug logging and have a look at the log it might help provide some useful data.

I will have a look at MVK versus ripped DVDs (VIDEO_TS) issue