ryanheise

I've made an initial implementation of the visualizer for iOS. Note that this is definitely not production ready. Some problems to investigate: 1. Against Apple recommendations, I allocate an `NSData`...

Has anyone been able to give this a whirl yet? I think this would be a really useful feature to include in the next release, so I'd like to make...

Thanks for testing that. It turns out there is another change to the behaviour of ExoPlayer in that `onAudioSessionIdChanged` is not called initially for the first value. I've done the...

Perhaps. With the null safety release of Flutter soon to reach stable, I'm not sure if I'd like to do this before or after that. Currently I'm maintaining two branches...

That's basically just the raw output from the Android API which is documented here: https://developer.android.com/reference/android/media/audiofx/Visualizer#getFft(byte[]) So it's possible you might get weird output unless you interpret that byte array as...

> Is this supported on iOS currently? The waveform visualizer is implemented on iOS but not pitch. You can track the pitch feature here: #329 There is a big question...

Hi @hemanthkb97 . Clone this repo and checkout the `visualizer` branch. Inside, the `example/` directory has been modified to demonstrate how to use the API. There are also some comments...

What is the reproducible project - is it it the provided example?

As per the above comment, I am asking people to test it on iOS the let me know whether or not it's working for them

Hi @Piero512 , yes sample data is working on iOS and Android, while FFT is currently on Android only (but you could do your own FFT in Dart I suppose)....