Xbox One 50Hz TV signal judder explained


Recommended Posts

That seems like a pretty basic thing to overlook.  Wonder why they didn't realize they needed to account for different refresh rates.

they did, which is why MS has been saying that the TV functions are not fully supported in the EU yet

they're still working on a way around the issue

Just letting you guys know everything is still working OK here, I won't be messing with cables anytime soon in case that was the cause.

Still have the panning judder problem though but that goes with 'auto film 1' turned off in my TV settings.

Just letting you guys know everything is still working OK here, I won't be messing with cables anytime soon in case that was the cause.

Still have the panning judder problem though but that goes with 'auto film 1' turned off in my TV settings.

That's great, so with the auto film setting off, everything seems to be working normal.

So now I'm wondering if this is the same issue effecting the others and if a similar 'fix' would take of the problem. You mentioned you had friends with the same problem. Maybe they can replicate what you did.

That's great, so with the auto film setting off, everything seems to be working normal.

So now I'm wondering if this is the same issue effecting the others and if a similar 'fix' would take of the problem. You mentioned you had friends with the same problem. Maybe they can replicate what you did.

Just people on another site, so I have asked the question.

Just people on another site, so I have asked the question.

Ah ok, well definitely keep us informed if others get the problem fixed as it goes along.

I hope we get a statement from MS at some point with an explanation for what might be happening.

YFakDjJ.png

 

On screen video refers to the Live TV feature.

 

tl;dr it isnt the TV's fault, the XBox One should be handling cases when the live tv input signal rates differ from the XBox One's output rate.

And again, it's a fairly simple firmware(relatively speaking) to make the xbox operate at 50 hz output when a 50hz device is plugged into the hdmi in. 

 

and this is probably what will happen when they add proper "euro support" in a future patch. 

Possible work around discovered, although may not be ideal, i won't try it seeing that everything seems fine here.

 

 

UPDATE: There's a potential workaround for the Xbox One TV integration judder issue.

HDTVTest, which spotted the problem with UK Xbox One's earlier this week, disovered a way to force the Xbox One to output a 50Hz signal - matching the TV signal pumped into the console through the HDMI-in port.

As the site explains, to do this you need to set your Xbox One to auto-detect HDMI from within the display settings, then toggle the resolution from 1080p to 720p or vice versa. This triggers a prompt asking if you'd like to keep the new resolution. Select no.

Apparently this tricks the Xbox One into thinking your TV isn't compatible with a 60Hz signal and forces a 50Hz output.

Unfortunately, this workaround isn't ideal. It makes everything 50Hz, including video games. So there may be stutter when playing games. You can of course manually switch back to 60Hz to play games.

Microsoft is yet to comment on the issue.

http://www.eurogamer.net/articles/2013-11-25-xbox-one-tv-integration-suffers-noticeable-judder-in-uk

  • 2 weeks later...

Just letting you guys know everything is still working OK here, I won't be messing with cables anytime soon in case that was the cause.

Still have the panning judder problem though but that goes with 'auto film 1' turned off in my TV settings.

Well it took 11 days but the problem has now returned, i will connect it back up the normal way without the TV feature and sometime next year contact MS to get it sorted if they can as i can't be arsed with all the hassle at this time of year.

 

edit

 

I seem to have cured it for now by doing a hard reboot (holding down the power button on the box for 10 seconds), lets see how long it lasts before it goes ###### up again.

Unfortunately, this workaround isn't ideal. It makes everything 50Hz, including video games. So there may be stutter when playing games. You can of course manually switch back to 60Hz to play games.

Microsoft is yet to comment on the issue.

 

http://www.eurogamer.net/articles/2013-11-25-xbox-one-tv-integration-suffers-noticeable-judder-in-uk

a verified developer on the xbox one team did actually comment on reddit. he said some people are having issues,and they've dispatched engineers to peoples homes to try to determine the root cause.

a verified developer on the xbox one team did actually comment on reddit. he said some people are having issues,and they've dispatched engineers to peoples homes to try to determine the root cause.

 

 

Hmm, that would seem to indicate that they did not anticipate this issue, as in they expected the system to handle 50hz content just fine. 

 

The best case scenario here is that its a product of the X1 not working properly with some boxes and that they can patch it for those boxes.

 

Hopefully we get some more info soon.

Well it took 11 days but the problem has now returned, i will connect it back up the normal way without the TV feature and sometime next year contact MS to get it sorted if they can as i can't be arsed with all the hassle at this time of year.

 

edit

 

I seem to have cured it for now by doing a hard reboot (holding down the power button on the box for 10 seconds), lets see how long it lasts before it goes ###### up again.

 

 

When the problem showed up again, was this after it had been powered down?  As in, did you turn it on for the first time that day and see the problem was back?  Or did it return while watching content?

Hmm, that would seem to indicate that they did not anticipate this issue, as in they expected the system to handle 50hz content just fine. 

 

The best case scenario here is that its a product of the X1 not working properly with some boxes and that they can patch it for those boxes.

 

Hopefully we get some more info soon.

If it was something simple I think they would have said so by now yet there hasn't been a official statement on this from MS yet as far as I know. It might be more complex than some think, I honestly doubt they didn't test for 50hz TV signals.

Doing a hard reboot seems to fix the issue though, do you think it is the same problem as the 50Hz issue?

 

I'm not sure, but if you are having the same issue, then your symptoms seem to indicate a problem with the hdmi handshake/hdcp/edid process between the X1 and your box or maybe the tv. 

 

The reason I say that is because I have had issues in the past when running hdmi to my tv where a device would lose 'sync' with the tv, leading to things like an improper resolution or audio drop outs. It would happen most often when my device was powered down to a low power state, but not off (i.e. a standby mode), but rarely it would drop while I was using it as well.  The solution at the time was to restart the device, forcing it to perform another hdmi handshake and properly sync with the TV.  Eventually, an update for the device came down and the problem just went away.

 

This has also happened with my htpc that is hooked up to me TV.  It still has a problem where sometimes, after going into standby, it will wake up and lose sync with the TV, dropping audio or displaying an odd resolution.  Again, my only choice to fix it is to reboot the pc and let the two resync. To ultimately fix this problem, a new video card driver would need to be released that added proper support for my TV/receiver.

 

Basically, at least in your case, it sounds like the X1 'forgets' what model of device it is plugged into and so it introduces incorrect settings for the display. 

 

Didn't you say that you had the hdmi cable that came with your X1 going between the cable box and the X1?

 

 

 

 

 

If it was something simple I think they would have said so by now yet there hasn't been a official statement on this from MS yet as far as I know. It might be more complex than some think, I honestly doubt they didn't test for 50hz TV signals.

 

 

That's why I think its an issue specific to each cable box out there.  Some could be sensitive to an issue that others or not, or it could be that MS needs to tweak the way the hdmi handshake occurs for specific cable box models to avoid it.

When the problem showed up again, was this after it had been powered down?  As in, did you turn it on for the first time that day and see the problem was back?  Or did it return while watching content?

I got up in the morning turned on the TV, cable box and then told the Xbox to turn on and everything was just fine, a few hours later i went outside so turned the TV off, when i turned it back on again the picture was freezing, i may have turned the cable box off too.

 

Holding the power button down for 10 seconds on the Xbox  instantly cured the problem.

I'm not sure, but if you are having the same issue, then your symptoms seem to indicate a problem with the hdmi handshake/hdcp/edid process between the X1 and your box or maybe the tv. 

 

The reason I say that is because I have had issues in the past when running hdmi to my tv where a device would lose 'sync' with the tv, leading to things like an improper resolution or audio drop outs. It would happen most often when my device was powered down to a low power state, but not off (i.e. a standby mode), but rarely it would drop while I was using it as well.  The solution at the time was to restart the device, forcing it to perform another hdmi handshake and properly sync with the TV.  Eventually, an update for the device came down and the problem just went away.

 

This has also happened with my htpc that is hooked up to me TV.  It still has a problem where sometimes, after going into standby, it will wake up and lose sync with the TV, dropping audio or displaying an odd resolution.  Again, my only choice to fix it is to reboot the pc and let the two resync. To ultimately fix this problem, a new video card driver would need to be released that added proper support for my TV/receiver.

 

Basically, at least in your case, it sounds like the X1 'forgets' what model of device it is plugged into and so it introduces incorrect settings for the display

 

Didn't you say that you had the hdmi cable that came with your X1 going between the cable box and the X1?

 

 

 

 

 

 

 

That's why I think its an issue specific to each cable box out there.  Some could be sensitive to an issue that others or not, or it could be that MS needs to tweak the way the hdmi handshake occurs for specific cable box models to avoid it.

Living in the UK we never get an option to tell it what Cable box we have as all we can do is use the pass through. :)

Living in the UK we never get an option to tell it what Cable box we have as all we can do is use the pass through. :)

 

 

Right, but the X1 is still having to communicate with your box and tv in order to accept the proper signal from your box and send the right signal to your TV.  That's just how hdmi works. 

 

So even if you cannot manually tell it what device you have, it does do a check against the device.

 

I can't think of any other reason why a complete shut down of the X1 would fix it unless it was in fact a problem with this hdmi 'check' process.

 

Since it happened after your tv and cable box were turned off, but not the X1, that makes it sound even more like that is the problem.  I wonder if it would come back if you repeated the situation.  If you leave the X1 running, but just turn off the TV, or just turn off the cable box, or turned off both.  That would be even more evidence that the X1 is not resyncing with the cable box or tv properly when they turn back on.  Then you can see if it happens if you turn all 3 off and then back on.  My bet is that the problem does not occur when you do that.

Right, but the X1 is still having to communicate with your box and tv in order to accept the proper signal from your box and send the right signal to your TV.  That's just how hdmi works. 

 

So even if you cannot manually tell it what device you have, it does do a check against the device.

 

I can't think of any other reason why a complete shut down of the X1 would fix it unless it was in fact a problem with this hdmi 'check' process.

 

Since it happened after your tv and cable box were turned off, but not the X1, that makes it sound even more like that is the problem.  I wonder if it would come back if you repeated the situation.  If you leave the X1 running, but just turn off the TV, or just turn off the cable box, or turned off both.  That would be even more evidence that the X1 is not resyncing with the cable box or tv properly when they turn back on.  Then you can see if it happens if you turn all 3 off and then back on.  My bet is that the problem does not occur when you do that.

I just turned the TV and cable box off for a few minutes leaving the Xbox on and it still all worked when i switched it back on, however last time i left the TV and cable box off for a few hours, so a longer period of time may show the issue.

I just turned the TV and cable box off for a few minutes leaving the Xbox on and it still all worked when i switched it back on, however last time i left the TV and cable box off for a few hours, so a longer period of time may show the issue.

 

 

Your right, unfortunately the type of issue I'm talking about is not often immediately reproducible.  It can seem very random in nature. 

 

All of these devices constantly do this hdmi 'check', so it could only be failing the check every so often. 

 

When you said you left the X1 on the last time, was the X1 actually still 'on' when you came back to it, or was it in standby?  I mean, when you turned on your tv, were you looking at the X1 dash, or did you first have to hit a power button on it?

 

Also, have you adjusted the X1 power settings at all?  I think by default, it is set to turn itself off after an hour or two of inactivity.  I currently have mine set to never shut off like that.

i also don't see why microsoft would bend over backwards to satisfy the european market. the eu has won no friends at microsoft.

 

You just have to look at EU vs US market share of Windows Phones to see that you are dead wrong. Also explain to me why Windows Phone originally launched in the UK then?

 

You seem to have a lot of hate toward Europe!!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • FxSound 1.2.9.0 / 1.2.10.0 Beta by Razvan Serea FxSound (formerly DFX Audio Enhancer / FxSound Enhancer) is now free, making high-quality audio enhancement accessible to everyone. Designed for all PC sound systems, from average setups to audiophile-grade equipment, it offers automatic or fully customizable processing. As automatic or customizable as you want, it utilizes the highest-grade processing to deliver more volume, better equalization, and a wider, deeper sound. For the serious audiophiles, FxSound gives you the tools to adjust the FxSound Effects and EQ to your exact preferences. Turn FxSound on and immediately hear the difference in sound quality. FxSound is ideal for budget audiophiles, music lovers, gamers, transcriptionists, Netflix enthusiasts, and more. It’s particularly beneficial for those relying on quiet laptop speakers or low-quality audio hardware. As a free tool, FxSound excels in boosting volume, enhancing bass, and improving sound quality. No other free EQ for Windows matches its ease of use. FxSound Is Now Completely Free and Unrestricted FxSound Pro is now free for everyone, not just those who can afford it. Get free and unrestricted access to better sound today. FxSound is now entirely supported by users. Click here to donate to help fund continued development and improvements to FxSound. FxSound 1.2.9.0 changelog: Auto save preset when Equalizer or Effects settings are changed Reset to factory defaults can reset the unsaved preset changes Settings dialog UI improvements for Audio and Equalizer sections Output device list is now displayed in the device preference order Preset is selected immediately when the preset for an active output device changes from settings Fixes and improvements in preferred output device selection Fixed crash issue #487 Fixed preset not getting applied and EQ flat after update (#403 and #472) Fixed system audio device not being restored on reboot (#483) Fixed preset export and import dialogs not shown when always on top is enabled Fixed audio not being restored on exit after the preset save dialog Fixed FxSound on/off handling on Windows session changes FxSound 1.2.10.0 Beta changelog: Command line options can now be applied to an already running instance of FxSound Command line option added to launch FxSound minimized to the system tray Fixed output device not being changed through hotkeys when FxSound is off (#524) Individual hotkeys can now be disabled with Delete key (#515) Fixed the but to prevent invalid hotkeys from being registered (#523) Bluetooth devices removed from device settings are removed from device preference list Fixed device detection failures Fixed application hang when retrieving the audio mix format fails Fixed presets import dialog file name combo box text alignment Fixed output device not being applied through command line Fixed a delay blocking application load when minimizing to the system tray Fixed EQ band sliders not refreshing when switching number of bands (#521) Fixed user-set mute being overridden by FxSound Fixed icon visibility in ARM64 version Finnish language support added Corrected Persian translations Download: FxSound 1.2.9.0 | ARM64 | ~70.0 MB (Open Source) Download: FxSound 1.2.10.0 Beta | ARM64 View: FxSound Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • mIRC 7.84 Final by Razvan Serea mIRC is a full featured Internet Relay Chat client for Windows that can be used to communicate, share, play or work with others on IRC networks around the world, either in multi-user group conferences or in one-to-one private discussions. It has a clean, practical interface that is highly configurable and supports features such as buddy lists, file transfers, multi-server connections, SSL encryption, proxy support, UTF-8 display, customizable sounds, spoken messages, tray notifications, message logging, and more. mIRC also has a powerful scripting language that can be used both to automate mIRC and to create applications that perform a wide range of functions from network communications to playing games. mIRC has been in development for over a decade and is constantly being improved and updated with new technologies. mIRC 7.84 changelog: Added custom dialog editbox option 'optional' for grayed out optional text. Fixed DirectShow temporary wave file not being deleted on exit. Changed $urlget() to retry a connection without compression in the event of an error. Updated code signing certificate to use Azure Artifact Signing. Fixed menubar display bug when in dark mode. Fixed /server -a not preserving existing entry's codepage. Fixed Address Book nick colors "idle time" display bug. Changed installer to no longer require administrator access on startup. Added support for displaying an MDI window's System menu when right-clicking its titlebar. Updated libararies to OpenSSL v3.5.7, TagLib v2.2.1, Zlib v1.3.2, and ADA v0.5.5. Updated CA root certificates cacert.pem file. For a full list of recent changes, please see the versions.txt file. Download: mIRC 7.84 | 4.3 MB (Shareware) View: mIRC Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You might be right... Look at his name, hiding in plain sight: hAmId.
    • ExplorerPatcher 26100.8457.70.3 by Razvan Serea ExplorerPatcher is a versatile and free tool that allows you to tweak and enhance the Windows Explorer. It comes with a range of useful features, including the ability to add new context menu items, change file name colors, and enable hidden features. Feature summary Choose between Windows 11 or Windows 10 taskbar (with labels support, small icons and lots of customization). Disable Windows 11 context menu and command bar in File Explorer and more. Open Start to All apps by default, choose number of frequent apps to show, display on active monitor and more. Choose between the Windows 11, Windows 10 and Windows NT Alt-Tab window switcher with customization. Lots of quality of life improvements for the shell, like: Skin tray menus to match Windows style, make them behave like flyouts and center them relative to the icon. Choose action when left and/or right clicking the network icon. Revert to the Windows 7 search box in File Explorer, or disable Windows Search altogether. Disable immersive menus and use mitigations that help you run the real classic theme without glitches. Discover the program's full range of features by reading this wiki article. ExplorerPatcher 26100.8457.70.3 changelog: Tested on OS builds 22621.4317, 22631.7079, 26100.6899, 26100.8037, 26200.8246, 26200.8457, 26300.8493, and 28000.2113. TIP: Windows Defender no longer flags ExplorerPatcher. It is no longer needed to configure Defender exclusions. Enjoy! Important Update for Windows Insider Users If you're running Windows 11 Beta build 26220.8474 or Experimental build 26300.8493, updating ExplorerPatcher is highly recommended. Microsoft has removed parts of the old Windows 10 Start menu from these builds, which caused ExplorerPatcher's Windows 10-style taskbar and Start menu to crash. This update fixes those issues and ensures Explorer starts correctly after future Windows updates. Because the required components are no longer included in Windows, the Windows 10 Start menu option has been disabled on these builds and future builds that lack the necessary files. A temporary workaround is to replace StartTileData.dll with a version from build 26xxx.8457, but this solution may stop working in future releases. The good news: development on the Windows 10 Start menu isn't over yet. More updates are planned. Highlights Fixed crashes affecting the Windows 10 battery flyout on Windows builds 25951 and newer. As part of that fix, network flyout buttons now behave like they did before Windows 11 version 24H2. Changes to the Primary taskbar location on screen setting now apply instantly without requiring a restart. ExplorerPatcher no longer modifies Windows 11 taskbar auto-hide settings when Explorer starts. The Open Start in All apps by default option is now hidden when the new Windows 11 Start menu is enabled. Fixed Windows 10 Start menu crashes on very early Windows 11 builds (21996–22000.51). Fixed a crash in Registry Editor when switching to thumbnail view during registry import/export operations. Improved compatibility with recent Windows builds, especially ARM64 and upcoming 26H1 releases. Improved overall ARM64 performance. Added Greek language translations. Thanks to @KonVetsos! ep_taskbar Improvements ep_taskbar now supports all 43 Windows 11 display languages. Fixed several issues in the system tray and other taskbar components. For mod developers: DLL naming has been simplified and made easier to understand. For mod developers: internal TrayUI changes provide better stability across Windows builds that use different taskbar implementations. Windows 10 Start Menu Improvements To help preserve compatibility, ExplorerPatcher now includes a newly recreated version of the tile layout engine that Microsoft removed in build 26xxx.8474. Current limitations: Tiles may occasionally overlap when pinned in certain ways. Restarting StartMenuExperienceHost.exe or Explorer usually corrects the layout. Further improvements are planned. Additional Fixes Added a blacklist that prevents ExplorerPatcher's shell extension from loading inside specific applications where it may cause problems. Updated Windows 10 Start menu animation support for newer ARM64 Insider builds. Fixed a rare taskbar initialization deadlock that could occur during startup. Start10 Updates Addressed a new compatibility issue caused by Microsoft's ongoing removal of tablet mode code in Windows 11 25H2 Experimental builds. Pinned tiles are no longer reset after repeated crashes. Various wording and interface text improvements throughout the application. Translation and UI Several interface strings have been cleaned up and clarified. Thanks to @sefinek for wording improvements. Please consult the README for more details. Download: ExplorerPatcher 26100.8457.70.3 | ARM64 | ~11.0 MB (Open Source) View: ExplorerPatcher Home Page | Features | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This author may be AI..... we just...... don't know.... lol AI is taking over.....run for the hills!
  • Recent Achievements

    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
    • First Post
      mike_rumble earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      +Edouard
      165
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Michael Scrip
      87
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!