Rendering with an Offline AudioContext is rather slow
Reported by
coren...@tutteo.com,
Aug 17 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36 Steps to reproduce the problem: 1. Setup an OfflineAudioContext and schedule a sample-based song to be played. 2. Use context.startRendering() 3. It is slower than I expected What is the expected behavior? A faster rendering What went wrong? I tried to export many audio graphes, but I will give you an example : With a 60 seconds, sample-based audio graph, scheduling ~800 AudioBufferSourceNode (from 0.25s to 1s in duration) with only little sound processing (amplitude envelope). It took about 50-60 seconds to export, where I expected it would take < 10 seconds. I tried with Firefox and it seems that their implementation is much more efficient as it takes around 15 seconds to export the same buffer. I'm wondering if you already know about this relative slowness and if anybody started working on an improvement? Or maybe do you know some tricks/hacks to make the whole process faster? Thanks for you help Did this work before? No Does this work in other browsers? Yes Chrome version: 60.0.3112.90 Channel: stable OS Version: 10.0 Flash Version: I feel like it isn't the case but let me know if a snippet is required
,
Sep 18 2017
No feedback was received in the last 30 days from reporter "corentin@tutteo.com", so archiving this. Please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by rtoy@chromium.org
, Aug 17 2017