GoogleChrome/audion

Graph visualization breaks into a single AudioContext node

midipixel opened this issue · 2 comments

midipixel commented

Hi there,

I'm experiencing a weird problem where the visualization suddenly breaks and Audion displays only a single AudioContext node. I'm not sure, but it seems to happen when some types of new nodes or audio contexts are added via JS after the initial. I managed to make a very simple test case demonstrating the problem using ToneJS. Just load the page, play the sound and then create an LFO.

Here's a video of the problem happening on a Windows machine: https://drive.google.com/file/d/1IJTQRQz72MyeoratjQsK3_f4xt3kiKq7/view?usp=sharing

This is the code:

<html>

<head>
    <title>Audion Test</title>

    <script src="https://cdn.jsdelivr.net/npm/tone@14.7.77/build/Tone.min.js"></script>
</head>

    <button onclick="play()">Play Sound</button>
    <button onclick="createLFO()">CreateLFO</button>

    <script>
        function play(){
            sound = new Tone.Player("https://tonejs.github.io/audio/berklee/gong_1.mp3").toDestination();
            sound.autostart = true;
        }

        function createLFO(){
            let lfo = new Tone.LFO();
        }
    </script>

</html>

You can also try inspecting my Web App, Blendwave, with Audion, and the same problem occurs once the page is loaded. In this case, it seems to happen when the Wavesurfer library creates its context. This didn't happen back when I wrote the app, and Audion was called Web Audio Inspector.

I'm experiencing this both on my desktop PC running Windows 10 (Chrome regular or Canary) and my old laptop running Windows 7.

Thanks for your attention!

hoch commented

I believe this is caused by the lack of a proper logic for multiple AudioContext. We have a plan to address this issue in the next phase of the development. Thank you for your detailed report!

  • 👍1
hoch commented

This issue seems fixed. Feel free to reopen if the problem persists.