Obsolete
Status Update
No update yet.
Comments
bi...@google.com
Could you please provide additional detail on which TV make and model, and what specific content you have the issue with.
da...@tekeye.biz
TV set is a 2012 model Samsung UE40D8005YUXXE. And the content is all that
are available on-demand from the national norwegian broadcaster NRK.
All material are 25/50 FPS as is common in Europe.
Both my Chromecast and my MythTV box are powered continiously.
When the TV set is switched on, I have to set the MythTV HDMI framerate to
50Hz manually - every time. I believe that the TV set initializes the HDMI
framerate to 60 Hz at power on.
If you need a tester, I will gladly cooperate with you.
9. sep. 2014 22:17 skrev <google-cast-sdk@googlecode.com> følgende:
are available on-demand from the national norwegian broadcaster NRK.
All material are 25/50 FPS as is common in Europe.
Both my Chromecast and my MythTV box are powered continiously.
When the TV set is switched on, I have to set the MythTV HDMI framerate to
50Hz manually - every time. I believe that the TV set initializes the HDMI
framerate to 60 Hz at power on.
If you need a tester, I will gladly cooperate with you.
9. sep. 2014 22:17 skrev <google-cast-sdk@googlecode.com> følgende:
bi...@google.com
Thanks for the details.
Could please confirm what you have set for the following settings on your TV:
Film Mode (Menu->Picture->Picture Options)
Motion Plus (Menu->Picture->Picture Options)
Also, could please reboot your Chromecast device, then after 1 min, start the Chromecast app on your mobile device, select your Chromecast device from the list of devices and then use the menu option to submit a feedback report. Please prefix the report feedback title with "
Could please confirm what you have set for the following settings on your TV:
Film Mode (Menu->Picture->Picture Options)
Motion Plus (Menu->Picture->Picture Options)
Also, could please reboot your Chromecast device, then after 1 min, start the Chromecast app on your mobile device, select your Chromecast device from the list of devices and then use the menu option to submit a feedback report. Please prefix the report feedback title with "
mr...@gmail.com
Settings are (and have been) as requested and feedback is returned.
Settings have no effect on judder. Judder is most visible when panning.I should wish there were an option to set HDMI framerate in Chromecast.
Settings have no effect on judder. Judder is most visible when panning.I should wish there were an option to set HDMI framerate in Chromecast.
bi...@google.com
We got your feedback, but the chromecast device logs is missing. Please make sure that the 'Send device logs' checkbox is checked in the Chromecast app for you device and please resend the feedback with the same title.
bi...@google.com
This is caused by the fact that Chromecast plays 25fps/50fps content at 60Hz output video refresh rate (as is evident by the fact that the reporter has the same juddered behavior when he plays 25/50 content on his other devices using 60Hz video mode).
Since 25 is not an exact multiple of 60, the frames are played out at an uneven rate:
2-2-3-2-3-2-2-3-2-3
(each number represents an incoming 25p input video content frame and the value is the amount of HDMI output frames that contain the input frame)
For 50p content played back at the Chromecast 60Hz video mode:
1-1-1-1-2-1-1-1-1-2
So every fifth frame is duplicated, while the rest of the frames play too fast, causing a judder effect.
However, my experience is that only about 5-30% of people actually notice such judder (and many of those don't care). This has still come up many times in the Chromecast Help Forums, for example, however.
The judder is especially noticiable in panning shots and sports content.
Similar issue happens with most movie and North American TV series content as well. Both of those are 24p (or 23.976p), and thus playing them back on a 60hz video mode causes the following frame cadence:
2-3-2-3-2-3-2-3-2-3
This is much less noticiable than the 50p/25p issues since the "pattern" is short, but still an issue (you can google for "chromecast 24p" to find people suffering from this).
To fix this, Chromecast should automatically (or add an API to allow the application "manually" to) switch the HDMI video mode to 50Hz output (e.g. CEA-861 VIC 31) for 25/50fps content and 24Hz/23.976Hz (VIC 32) for 24/23.976fps content. Doing this automatically is the behavior of e.g. Samsung blu-ray players (and others) when using Netflix, when playing e.g. British TV content the video mode switches to 50Hz and when playing back movies it goes to 24Hz (as can be seen in the TV UI as video mode), instead of being fixed to 60Hz like on Chromecast.
I'm also experiencing this issue with all of the TV content here in Finland (which is 25p or in some cases 50p). I've tried on LG 55LH5000, LG 42LH2000 (with all motion interpolation related settings off) and on some other models, but this should affect all TV models. I can provide more info if needed.
Since 25 is not an exact multiple of 60, the frames are played out at an uneven rate:
2-2-3-2-3-2-2-3-2-3
(each number represents an incoming 25p input video content frame and the value is the amount of HDMI output frames that contain the input frame)
For 50p content played back at the Chromecast 60Hz video mode:
1-1-1-1-2-1-1-1-1-2
So every fifth frame is duplicated, while the rest of the frames play too fast, causing a judder effect.
However, my experience is that only about 5-30% of people actually notice such judder (and many of those don't care). This has still come up many times in the Chromecast Help Forums, for example, however.
The judder is especially noticiable in panning shots and sports content.
Similar issue happens with most movie and North American TV series content as well. Both of those are 24p (or 23.976p), and thus playing them back on a 60hz video mode causes the following frame cadence:
2-3-2-3-2-3-2-3-2-3
This is much less noticiable than the 50p/25p issues since the "pattern" is short, but still an issue (you can google for "chromecast 24p" to find people suffering from this).
To fix this, Chromecast should automatically (or add an API to allow the application "manually" to) switch the HDMI video mode to 50Hz output (e.g. CEA-861 VIC 31) for 25/50fps content and 24Hz/23.976Hz (VIC 32) for 24/23.976fps content. Doing this automatically is the behavior of e.g. Samsung blu-ray players (and others) when using Netflix, when playing e.g. British TV content the video mode switches to 50Hz and when playing back movies it goes to 24Hz (as can be seen in the TV UI as video mode), instead of being fixed to 60Hz like on Chromecast.
I'm also experiencing this issue with all of the TV content here in Finland (which is 25p or in some cases 50p). I've tried on LG 55LH5000, LG 42LH2000 (with all motion interpolation related settings off) and on some other models, but this should affect all TV models. I can provide more info if needed.
[Deleted User] <[Deleted User]>
Please reboot your Chromecast device, then after 1 min, start the Chromecast app on your mobile device and select your Chromecast device from the list of devices. Make sure that the 'Send device logs' checkbox is checked in the Chromecast app for your device, then use the menu option to submit a feedback report. Please prefix the report feedback title with "
gr...@google.com
OK, done.
Description
Android SDK Tools:25.1.1
Host Operating System:Windows 10 64 bit
Steps to Reproduce Bug:
1. Create a new AVD (emulator) with default settings (enable keyboard input is checked in Advanced settings), e.g. Nexus 6P API 23 (Marshmallow) x86
2. Start the AVD/emulator, the emulator loads in a window with control bar next to it.
3. Try to use the keyboard commands defined in the default.keyset file.
Expected Behavior:
The PC keyboard actions defined in default.keyset work.
Observed Behavior:
Most PC keyboard actions defined in default.keyset do not work.
More details - Using command 'emulator -help-keyset':
"on startup, the emulator looks for 'keyset' file that contains the configuration of key-bindings to use. the default location on this system is:
C:\Users\JDoe\.android\default.keyset
if the file doesn't exist, the emulator writes one containing factory defaults. you are then free to modify it to suit specific needs."
This default.keyset existed from previous version of the SDK:
BUTTON_CALL F3
BUTTON_HANGUP F4
BUTTON_HOME Home
BUTTON_BACK Escape
BUTTON_MENU F2, PageUp
BUTTON_STAR Shift-F2, PageDown
BUTTON_POWER F7
BUTTON_SEARCH F5
BUTTON_CAMERA Ctrl-Keypad_5, Ctrl-F3
BUTTON_VOLUME_UP Keypad_Plus, Ctrl-F5
BUTTON_VOLUME_DOWN Keypad_Minus, Ctrl-F6
TOGGLE_NETWORK F8
TOGGLE_TRACING F9
TOGGLE_FULLSCREEN Alt-Enter
BUTTON_DPAD_CENTER Keypad_5
BUTTON_DPAD_UP Keypad_8
BUTTON_DPAD_LEFT Keypad_4
BUTTON_DPAD_RIGHT Keypad_6
BUTTON_DPAD_DOWN Keypad_2
TOGGLE_TRACKBALL F6
SHOW_TRACKBALL Delete
CHANGE_LAYOUT_PREV Keypad_7, Ctrl-F11
CHANGE_LAYOUT_NEXT Keypad_9, Ctrl-F12
ONION_ALPHA_UP Keypad_Multiply
ONION_ALPHA_DOWN Keypad_Divide
Some of the expected commands did not work:
BUTTON_POWER F7
BUTTON_VOLUME_UP Keypad_Plus, Ctrl-F5
BUTTON_VOLUME_DOWN Keypad_Minus, Ctrl-F6
CHANGE_LAYOUT_PREV Keypad_7, Ctrl-F11
CHANGE_LAYOUT_NEXT Keypad_9, Ctrl-F12
Deleted this file and the following default.keyset was created when the AVD was started:
BUTTON_POWER Ctrl-Escape
BUTTON_VOLUME_UP Ctrl-Equal
BUTTON_VOLUME_DOWN Ctrl-Minus
BUTTON_BACK Ctrl-Backspace
BUTTON_HOME Ctrl-H
BUTTON_MENU Ctrl-M
Ctrl-Escape did not work, used by Windows to bring up start menu
Ctrl-Equal and Ctrl-Minus does work but also registers = and - on the emulated device.
Ctrl-Backspace, Ctrl-H, Ctrl-M works.
Changed the file to:
BUTTON_POWER F7
BUTTON_VOLUME_UP Ctrl-F5
BUTTON_VOLUME_DOWN Ctrl-F6
BUTTON_BACK Ctrl-Backspace
BUTTON_HOME Ctrl-H
BUTTON_MENU Ctrl-M
CHANGE_LAYOUT_PREV Ctrl-F11
CHANGE_LAYOUT_NEXT Ctrl-F12
The following errors were observed:
BUTTON_POWER had to use Ctrl-P (as per control bar icon tooltip)
BUTTON_VOLUME_UP used Ctrl-= (as per control bar icon tooltip, = read by device)
BUTTON_VOLUME_DOWN used Ctrl-- (as per control bar icon tooltip, - read by device)
CHANGE_LAYOUT_PREV used Ctrl-Left (as per control bar icon tooltip)
CHANGE_LAYOUT_NEXT used Ctrl-Right (as per control bar icon tooltip)