Hide logs in console about just_waveform

[ryanheise]

They are currently hard coded for debugging purposes. The intention was to remove them after the plugin had proved to be stable. Perhaps it is stable enough to consider doing that now. Have you had any stability issues otherwise?

[loic-hamdi]

So far so good, it is stable enough in my app to go to production.

Thanks for you great work on this package and other audio ones 👍

[loic-hamdi]

Hi @ryanheise , any news on hiding the log please?

[ryanheise]

I've just added it to my plans for the next work batch.

[ryanheise]

I've just pushed a commit that suppresses the logs. Would you like to test it and let me know for both iOS and Android whether it works as expected?

[loic-hamdi]

thanks @ryanheise

It is working on iOS & Android.

The only problem (not related to the logs) I am facing is when I have a lot of waveforms loading at the same time, some of them stop loading, I don't know if you ever experience it?

[ryanheise]

Simultaneous decoders is not a feature, but there is an open pull request for it if you'd like to test it.

[ryanheise]

I would also mention that each platform may have its own limit on how many simultaneous decoders you can run. because they are resource intensive. In your app, you might be able to code around that limitation by using some sort of processing pool where processes get queued beyond the pool's maximum size.

[loic-hamdi]

I would also mention that each platform may have its own limit on how many simultaneous decoders you can run. because they are resource intensive. In your app, you might be able to code around that limitation by using some sort of processing pool where processes get queued beyond the pool's maximum size.

I agree with the approach you recommend. I will actually update my code to only load the waveform for visible widget in order to limit the possible simultaneous decoders. (My work case is a chat with vocal messages)

[ryanheise]

Closing as this is now published.