it seems have something to do with the latest chrome audio policy. Anyone got a workaround?