Performance Speed Up

[KinMaynard]

Blitting plotting, drawing, zoom, pan & buttons to speed up performance of especially visualizer function.

[KinMaynard]

New theory that speed issues are from the size of the data. It's probably calling a lot of draw for each data point and audio usually has around 44100 per second points. So chunking or using collections would help and might fix the problem.

[KinMaynard]

Collections marginally helps but what needs to be done is chunking the data. I want to use a block-wise generator instead of an array of all the data for the display portions of this code. Since display doesn't require as much fidelity as playback I want to use a much smaller buffer size for the audio data. Displaying 44100 data points per second is unnecessary and impossible. It would be far more prudent to display a small power of 2 say 1024. I can use this small buffer for the display portions and use the full fidelity of the audio for playback/dsp. This error came from only understanding how necessary high fidelity is for playback and not realizing that it isn't necessary for visualization and in fact causes severe performance issues.

So where do I want to use blocks and where arrays? Use blocks for visualization functions & their tests and use arrays for dsp.

[KinMaynard]

Adding block argument to visualization functions:

• Waveform

• Magnitude

• Spectrogram

• Vectorscope

• Visualizer

• Tests

• Change 'data' argument to 'block'

• Add Loop for block generator

• Change docstring

• Change Test arguments

• Test

[KinMaynard]

Accidental closing of issue. Reopened.

[KinMaynard]

What do I want to accomplish using block processing instead of an array at 441khz/Sec?

I want to downsample the data to visualize it at around 1024 samples/sec. So I will run a generator making blocks of that size and plot 1 block per second. It's not enough to set the blocksize I also need the sample rate to be the blocksize as well and I also can process this into an array inside the import function and not change my current function calls.

[KinMaynard]

I don't even need blocks until I want realtime so I can just return a downsampled array at import along with the full fidelity one.

[KinMaynard]

Turns out you cannot downsample with soundfile.read since it reads the sample rate from the file unless it's raw input.

[KinMaynard]

Let's perform the downsampling ourselves inside the import function and return 2 arrays as previous.

[KinMaynard]

Downsample methods:
Resample - Take every nth sample
Bin - Average of Bins
Interpolate - Fit curve

[KinMaynard]

Preserving docstring for buffersize for later use
buffer: buffer size for block generator [32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, 16384] or default None

[KinMaynard]

So I would like to use both bins and interpolation to downsample the array for the analysis functions. I'll make a button for this in the magnitude spectrum plot at least possibly one in the spectrogram too.