Issue metadata
Sign in to add a comment
|
Loud "buzz" sound from analog speakers when no audio is playing for more than 30 seconds
Reported by
brycetho...@gmail.com,
Oct 6 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9765.76.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.113 Safari/537.36 Platform: 9765.76.0 (Official Build) stable-channel panther Example URL: Steps to reproduce the problem: 1. Boot Chromebox, and login 2. Open a page that has audio (youtube video works) 3. pause audio source 4. wait 30 seconds 5. hear buzz 6. unpause audio source to make buzz stop What is the expected behavior? Audio from speakers should be silent when no audio is being played, no matter how long. What went wrong? After updating to Chrome 61 on my Asus Chromebox I hear a loub buzzing sound coming from my analog speakers when no audio has been played for more than 30 seconds. See the link below to see a video of this effect in action. https://photos.app.goo.gl/e5Z63wMZPS6cEYku1 Did this work before? Yes Chrome 60 Is it a problem with Flash or HTML5? N/A Does this work in other browsers? N/A Chrome version: 61.0.3163.113 Channel: n/a OS Version: 9765.76.0 Flash Version: Shockwave Flash 27.0 r0 Contents of chrome://gpu: Note: To properly save this page, select the "Webpage, Complete" option in the Save File dialog. Graphics Feature Status Canvas: Hardware accelerated CheckerImaging: Disabled Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Native GpuMemoryBuffers: Hardware accelerated Panel Fitting: Unavailable Rasterization: Software only. Hardware acceleration disabled Video Decode: Hardware accelerated Video Encode: Hardware accelerated WebGL: Hardware accelerated WebGL2: Hardware accelerated Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing decode_encode_srgb_for_generatemipmap disable_discard_framebuffer disable_framebuffer_cmaa msaa_is_slow scalarize_vec_and_mat_constructor_args rely_on_implicit_sync_for_swap_buffers Problems Detected Chrome OS panel fitting is only supported for Intel IVB and SNB Graphics Controllers Disabled Features: panel_fitting Framebuffer discarding causes jumpy scrolling on Mali drivers: 301988 Applied Workarounds: disable_discard_framebuffer Clear uniforms before first program use on all platforms: 124764, 349137 Applied Workarounds: clear_uniforms_before_first_program_use Mesa drivers in ChromeOS handle varyings without static use incorrectly: 333885 Applied Workarounds: count_all_in_varyings_packing Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565 Applied Workarounds: msaa_is_slow Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198 Applied Workarounds: disable_framebuffer_cmaa Disable KHR_blend_equation_advanced until cc shaders are updated: 661715 Decode and Encode before generateMipmap for srgb format textures on Chromeos Intel: 634519 Applied Workarounds: decode_encode_srgb_for_generatemipmap Avoid waiting on a egl fence before pageflipping and rely on implicit sync.: 721463 Applied Workarounds: rely_on_implicit_sync_for_swap_buffers Accelerated rasterization has been disabled, either via blacklist, about:flags or the command line. Disabled Features: rasterization Checker-imaging has been disabled via finch trial or the command line. Disabled Features: checker_imaging Version Information Data exported 10/6/2017, 12:06:44 PM Chrome version Chrome/61.0.3163.113 Operating system Linux 3.8.11 Software rendering list version 13.10 Driver bug list version 10.29 ANGLE commit id 0d2ecb4ea992 2D graphics backend Skia/61 0 Command Line /opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=27.0.0.130 --ui-prioritize-in-gpu-process --use-gl=egl --enable-native-gpu-memory-buffers --gpu-sandbox-failures-fatal=yes --enable-logging --log-level=1 --use-cras --enable-wayland-server --user-data-dir=/home/chronos --max-unused-resource-memory-usage-percentage=5 --system-developer-mode --disable-lock-screen-apps --login-profile=user --aura-legacy-power-button --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/oem_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/oem_small.jpg --default-wallpaper-is-oem --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --enable-consumer-kiosk --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --login-user=bryce@thormedia.com --login-profile=67aee4d880e39017861cfb2eaf69ff6031eb6927 --flag-switches-begin --enable-features=EnableBackgroundBlur,InstantTethering --flag-switches-end --vmodule=tablet_power_button_controller=1,*chromeos/login/*=1,auto_enrollment_controller=1,*plugin*=2,*zygote*=1,*/ui/ozone/*=1,*/ui/display/manager/chromeos/*=1,power_button_observer=2,webui_login_view=2,lock_state_controller=2,webui_screen_locker=2,screen_locker=2 Driver Information Initialization time 66 In-process GPU false Passthrough Command Decoder false Supports overlays false Sandboxed true GPU0 VENDOR = 0x8086, DEVICE= 0x0a16 Optimus false Optimus false AMD switchable false Driver vendor Mesa Driver version 17.1.0 Driver date Pixel shader version 3.00 Vertex shader version 3.00 Max. MSAA samples 8 Machine model name Machine model version GL_VENDOR Intel Open Source Technology Center GL_RENDERER Mesa DRI Intel(R) Haswell Mobile GL_VERSION OpenGL ES 3.0 Mesa 17.1.0-devel (git-9baf1ff8fc) GL_EXTENSIONS GL_EXT_blend_minmax GL_EXT_multi_draw_arrays GL_EXT_texture_filter_anisotropic GL_EXT_texture_compression_dxt1 GL_EXT_texture_format_BGRA8888 GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth24 GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_mapbuffer GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_stencil8 GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_EXT_texture_sRGB_decode GL_OES_EGL_image GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_type_2_10_10_10_REV GL_OES_get_program_binary GL_APPLE_texture_max_level GL_EXT_discard_framebuffer GL_EXT_read_format_bgra GL_NV_fbo_color_attachments GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_array_object GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_EXT_robustness GL_EXT_texture_rg GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer GL_NV_read_depth GL_NV_read_depth_stencil GL_NV_read_stencil GL_EXT_draw_buffers GL_EXT_map_buffer_range GL_KHR_debug GL_KHR_robustness GL_OES_depth_texture_cube_map GL_OES_surfaceless_context GL_EXT_color_buffer_float GL_EXT_separate_shader_objects GL_EXT_shader_integer_mix GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex GL_EXT_polygon_offset_clamp GL_EXT_texture_border_clamp GL_KHR_context_flush_control GL_KHR_robust_buffer_access_behavior GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex GL_OES_sample_shading GL_OES_sample_variables GL_OES_shader_multisample_interpolation GL_OES_texture_border_clamp GL_OES_texture_stencil8 GL_EXT_blend_func_extended GL_EXT_clip_cull_distance GL_MESA_shader_integer_functions Disabled Extensions GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent Window system binding vendor Mesa Project Window system binding version 1.4 (DRI2) Window system binding extensions EGL_EXT_image_dma_buf_import EGL_KHR_config_attribs EGL_KHR_create_context EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image_base EGL_KHR_no_config_context EGL_KHR_reusable_sync EGL_KHR_surfaceless_context EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_image_dma_buf_export Direct rendering Yes Reset notification strategy 0x8261 GPU process crash count 0 Compositor Information Tile Update Mode One-copy Partial Raster Enabled GpuMemoryBuffers Status ATC Software only ATCIA Software only DXT1 Software only DXT5 Software only ETC1 Software only R_8 GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT R_16 Software only RG_88 GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT BGR_565 GPU_READ RGBA_4444 Software only RGBX_8888 GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE RGBA_8888 GPU_READ, SCANOUT_CPU_READ_WRITE BGRX_8888 GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE BGRA_8888 GPU_READ, SCANOUT_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT RGBA_F16 Software only YVU_420 GPU_READ YUV_420_BIPLANAR Software only UYVY_422 Software only Log Messages [3409:3419:1006/115357.643116:VERBOSE1:drm_device_manager.cc(54)] : Could not initialize DRM device for /sys/devices/platform/vgem/drm/card1 [3409:3419:1006/115359.552484:VERBOSE1:drm_display.cc(102)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=19 connector=28 origin=0,0 size=1920x1080 [3409:3419:1006/115359.735329:VERBOSE1:drm_display.cc(102)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=22 connector=33 origin=0,1140 size=1920x1080 [3409:3419:1006/115408.109599:WARNING:screen_manager.cc(114)] : Display controller (crtc=19) already present. [3409:3419:1006/115408.109652:WARNING:screen_manager.cc(114)] : Display controller (crtc=22) already present. [3409:3419:1006/115408.143741:VERBOSE1:drm_display.cc(102)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=19 connector=28 origin=0,0 size=1920x1080 [3409:3419:1006/115408.144055:VERBOSE1:drm_display.cc(102)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=22 connector=33 origin=0,1140 size=1920x1080 Previous to Chrome 61, I noticed this same buzz before logging in, but once logged in it would work fine no matter how long it was left without audio playing.
,
Oct 12 2017
,
Oct 12 2017
Let me guess that you are using powered speakers connected to the 3.5mm jack on the chromebox. Assuming that is correct, you probably have created a ground loop. The grounds of the chromebox and the speakers are floating to different levels when not being actively driven by the headphone cable. If you google computer ground loops, you'll get some debugging suggestions. Update here if any of those solutions help or not. Thanks for reporting the issue. Dylan
,
Oct 12 2017
Thanks for the response. That is correct. I am using powered speakers on the 3.5mm connector. I tested the with headphones, and there is no buzz after 20 seconds, but there is an audible pop. I don't know anything about ground loops or levels, what I do know is that this issue was not present in Chrome 60 stable. There must have been a change that causes the Chromebox to stop driving the speakers after 20 seconds now. Maybe a new power save feature that disables the sound components of the device when not in use? I'm not really sure where to go from here. At least for now the extension is keeping it from happening.
,
Oct 12 2017
It could have been a power save change, but the audio path has been powered down when inactive for the life of that chromebox. Maybe a new component was added to your setup or some plugs were moved around. The normal path to debugging this is to unplug things one at a time until it goes away. Or you can get a decoupler for the 3.5mm line if determining the root cause isn't possible.
,
Oct 23 2017
Thanks, Bryce, for the extension. I will give it a try. My Asus Chromebox performs well, but the audio has ALWAYS been a problem. I invested in expensive, audiophile-quality loudspeakers for my desktop computer set-up, and I'm concerned that the faulty audio of the Chomebox might damage my speakers one day if I'm not really careful.
,
Oct 23 2017
dgreid -- It's not actually a hardware problem. Google has acknowledged that it is a software issue that began with the update to Chrome OS 61, and that they are working to correct it. It's true that the 60Hz hum is a ground-loop, but it is being caused by the Operating System completely shutting down the analog audio electrical signal in the Chromebox, after 30 seconds, to save energy. This feature makes sense in a Chromebook that is running on a battery, but these Chromeboxes have NO battery -- they are always powered by a wall wart plugged into AC house current. It's a real annoyance having to switch off my computer speakers before the 30 second time limit runs out. If I don't, I am blasted with that stupid hum.
,
Nov 1 2017
,
Nov 2 2017
This is issue 775486 . Good guess Dylan, Yes it is the change in power_save setting causing the regression. I am sorry about the bad experience. We should add this speaker model into our QA test rack for chromebox to prevent this kind of regression.
,
Nov 2 2017
I had high hopes the Buzzer extension would work but it doesn't for me. I guess the power saving issue overrides the extension. I ordered a Ground Loop Isolator to try but I guess the power management problem will override this too.
,
Nov 2 2017
The Ground Loop Isolator stopped the hum but the system is still emitting a loud thump when is starts and stops as the audio state changes but I am so happy the hum is gone. The first step and I know you guys are working the power state change for 62.
,
Dec 3 2017
Hi, I am having similar audio buzz issue with my Asus Chromebox - do you think below 'Ground Loop Noise Isolator' will help me? https://www.amazon.com/gp/product/B019393MV2/ref=ox_sc_act_title_1?smid=A1E57UY6AMKO25&psc=1 Thanks for help!
,
Dec 3 2017
Sorry for got to add version info : Version 62.0.3202.97 (Official Build) (64-bit)
,
Dec 4 2017
Hi srikishore, please switch to beta channel and update to R63 image. https://bugs.chromium.org/p/chromium/issues/detail?id=775486#c75 Thanks! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by brycetho...@gmail.com
, Oct 12 2017