{"id":19686,"date":"2018-05-07T17:17:00","date_gmt":"2018-05-07T17:17:00","guid":{"rendered":"http:\/\/www.gamasutra.com\/view\/news\/317698"},"modified":"2018-05-07T17:17:00","modified_gmt":"2018-05-07T17:17:00","slug":"chrome-update-kills-audio-on-many-web-based-games","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2018\/05\/07\/chrome-update-kills-audio-on-many-web-based-games\/","title":{"rendered":"Chrome update kills audio on many web-based games"},"content":{"rendered":"<p>A recent update to Google Chrome had the unfortunate side effect of muting audio for a vast array of web-based games and interactive projects.<\/p>\n<p>Developers have <a href=\"https:\/\/twitter.com\/waxpancake\/status\/993520116003291136\">taken to Twitter<\/a> to call Google out for the sudden and unprompted change, noting in some cases that their HTML-5 based projects are essentially dead in the water with audio forcibly muted.<\/p>\n<p>While it\u2019s unlikely that Google will let these changes remain in the face of such backlash, the fact that a major web browser has all at once muted audio for the many, many projects that fall outside of top websites that feature audio elements understandably has many developers concerned.<\/p>\n<p>Developers like <em>VVVVV<\/em> and <em>Super Hexagon<\/em> creator <a href=\"https:\/\/twitter.com\/terrycavanagh\/status\/993464105217425408\">Terry Cavanagh<\/a> and <em>Stephen\u2019s Sausage Roll<\/em> creator <a href=\"https:\/\/twitter.com\/increpare\/status\/993470180842987520\">Stephen Lavelle<\/a> are some of the people that have\u00a0already noticed that their content has been affected by the change, while numerous other web developers and artists have spoken out against the ill effects of the new policy as well.<\/p>\n<p>The issue itself looks to be\u00a0rooted in a policy change that came with the <a href=\"https:\/\/gadgets.ndtv.com\/apps\/news\/google-chrome-update-autoplay-video-block-personalisation-1847354\">most recent update to Google Chrome<\/a>. Earlier this year, Google rolled out a Chrome update that allowed users to mute audio based on individual websites, aiming to counteract the minor annoyance of unwanted, auto-playing videos. The latest policy update takes that one step further by automatically blocking audio and video from being played on most websites, save for those on Google\u2019s list of 1,000 or so sites where a high percentage of videos opt to play media with sound.\u00a0<\/p>\n<p>Chrome additionally doesn\u2019t display any sort of notification to a user that the page they\u2019re viewing has had its audio muted, something developers have also taken issue with in the wake of this change.<\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"en\" readability=\"6.23225806452\">\n<p dir=\"ltr\" lang=\"en\">Ah fuuck sake. I had just in the last year started to begin to trust that I could reliably use audio in the browser (after years of reticence). So much for that&#8230;looks like the chrome update broke all of the audio in my html5 games as well. <a href=\"https:\/\/t.co\/gT6n9pz0VT\">https:\/\/t.co\/gT6n9pz0VT<\/a><\/p>\n<p>\u2014 Stephen Lavelle (@increpare) <a href=\"https:\/\/twitter.com\/increpare\/status\/993470180842987520?ref_src=twsrc%5Etfw\">May 7, 2018<\/a><\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>A recent update to Google Chrome had the unfortunate side effect of muting audio for a vast array of web-based games and interactive projects. Developers have taken to Twitter to call Google out for the sudden and unprompted change, noting in some cases that their HTML-5 based projects are essentially dead in the water with [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":19687,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[],"class_list":["post-19686","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/19686","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=19686"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/19686\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media\/19687"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=19686"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=19686"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=19686"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}