The documentation for duration() says:

Passing an ID will return the duration of the sprite being played on this instance; otherwise, the full source duration is returned.

But to get an ID, we need to call play() first. This means, if we have a sound sprite, we can't get the duration of individual sounds in the sprite without actually starting playback.

As a workaround, I found you

Looking at https://wavesurfer-js.org/plugins and https://wavesurfer-js.org/example/spectrogram/index.html it is entirely unclear how this plugin is supposed to get loaded.

The second link has an example that is literally impossible, because you can't reference a variable before it's been declared (the wavesurfer var does not exist yet, so the wavesurfer: wavesurfer instruction is an error),

In any examples, putting "start_song" parameter have no effet.
It will always set first song to index 0.

Setting "start_song":3 in the Amplitude.init object lead to have in the debug object : start_song: ""

Reproduce:

• Take the "Blue Playlist" example
• In the Amplitude init, add "start_song":3
• Load the page
• Push the big Play/Pause button. It will play song index 0

Hello, thanks a lot for your great work !
Is the documentation up to date regarding the delay please ?
I had to modify the code because the log tell me that delay time must be between 1 and 10. But the documentation says the contrary.

var delay = new tuna.Delay({
    feedback: 0.45,    //0 to 1+
    delayTime: 150,    //1 to 10000 milliseconds
    wetLevel: 0.25,    //0 to 1+
    d

The documentation should reflect that the sequencer can now have padding for the rows and columns. The RadioButton can be vertically oriented.

In the guide to create a 2D module it would be nice if we could also talk about how to save data globally in the module scope and also init the module once.

Today, our unit test is a large, monolithic test that

1. constructs a graph by passing messages to the panel script and
2. performs a massive object comparison:

https://github.com/google/audion/blob/master/tests/panel_test.js
This takes the unit out of unit testing. :(

Instead of doing a massive object property comparison, the test should assert for specific details such as the existen