You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Walking through the codes, I've just found that lab::AnalyserNode class lacks an ability to set fftSize value, it has only getter. Also lab::RealtimeAnalyser lacks the same thing.
However it exists in chromium's implementation of the above classes. And it doesn't seem to be too hacky. I think this method is needed, because the spec states that this property is settable.
As a temporary workaround I could resort to re-creating the lab::AnalyserNode instance in my JS (bindings) setter, whenever the fftSize value is changed from JS. But it would really be better if we avoided the hackery and put this feature into the core.
The text was updated successfully, but these errors were encountered:
A little bit of factoring of RealtimeAnalyser could do the trick. m_analysisFrame and m_magnitudeBuffer need to be reinitialized, and it looks like everything will work fine.
Hello.
Walking through the codes, I've just found that
lab::AnalyserNode
class lacks an ability to setfftSize
value, it has only getter. Alsolab::RealtimeAnalyser
lacks the same thing.However it exists in chromium's implementation of the above classes. And it doesn't seem to be too hacky. I think this method is needed, because the spec states that this property is settable.
As a temporary workaround I could resort to re-creating the
lab::AnalyserNode
instance in my JS (bindings) setter, whenever thefftSize
value is changed from JS. But it would really be better if we avoided the hackery and put this feature into the core.The text was updated successfully, but these errors were encountered: