{"action":"opened","issue":{"url":"https://api.github.com/repos/d0kt0r0/estuary/issues/48","repository_url":"https://api.github.com/repos/d0kt0r0/estuary","labels_url":"https://api.github.com/repos/d0kt0r0/estuary/issues/48/labels{/name}","comments_url":"https://api.github.com/repos/d0kt0r0/estuary/issues/48/comments","events_url":"https://api.github.com/repos/d0kt0r0/estuary/issues/48/events","html_url":"https://github.com/d0kt0r0/estuary/issues/48","id":391418723,"node_id":"MDU6SXNzdWUzOTE0MTg3MjM=","number":48,"title":"Chrome autoplay policy changes can cause large delay in evaluation audio responsiveness","user":{"login":"SpencerPark","id":9256594,"node_id":"MDQ6VXNlcjkyNTY1OTQ=","avatar_url":"https://avatars0.githubusercontent.com/u/9256594?v=4","gravatar_id":"","url":"https://api.github.com/users/SpencerPark","html_url":"https://github.com/SpencerPark","followers_url":"https://api.github.com/users/SpencerPark/followers","following_url":"https://api.github.com/users/SpencerPark/following{/other_user}","gists_url":"https://api.github.com/users/SpencerPark/gists{/gist_id}","starred_url":"https://api.github.com/users/SpencerPark/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SpencerPark/subscriptions","organizations_url":"https://api.github.com/users/SpencerPark/orgs","repos_url":"https://api.github.com/users/SpencerPark/repos","events_url":"https://api.github.com/users/SpencerPark/events{/privacy}","received_events_url":"https://api.github.com/users/SpencerPark/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-15T22:57:23Z","updated_at":"2018-12-15T22:57:23Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"As per https://developers.google.com/web/updates/2017/09/autoplay-policy-changes, I've just updated chrome to a version with this policy in effect and it has a pretty major issue for Estuary. From the home page there needs to be at least 1 user interaction to get to a page that plays audio so the issue is not that the context remains `pause()`ed but rather the clocks get way out of sync.\r\n\r\nAfter the page loads, the audio context is in suspended state until there is a user interaction with the page. The renderer seems to be scheduling under the assumption that this clock is never paused and as such keeps counting up on it's internal clock. This delay between page load an first interaction seems to be the same delay between making a definition change and hearing the update leading me to believe that the internal clock is ahead of the audio clock by this duration.\r\n\r\nI think the internal clock (used for rendering tidal patterns) should be occasionally synced to the audio clock. As such this is likely related to #15 but could potentially be a separate issue."}}
{"actor":{"display_login":"SpencerPark"}}