Hello,

I'm still on the quest of Faust in the web browser... I admit, I have not
taken the time to understand completely how Faust generated WASM code (and
its JS counterparts) integrate with WebAudio and the browser, but I'm
naively going forward with using several Faust objects in the browser at
the same time. I realized that there is a global variable (const dspName)
standing in my way, but I've found a workaround.
I see that for each Faust WASM build there is JS "factory class" being
generated. As it takes a WebAudio context as constructor's argument, I
figured I can treat it as a connection target, but it doesn't seem to work
that way.
Naively trying 
FaustSource_dsp.connect(FaustEffect_dsp).connect(audio_context.destination)
didn't work, it said that
Uncaught (in promise) TypeError: AudioNode.connect: Argument 1 is not valid
for any of the 2-argument overloads.
Before trying to fully understand this error, I figured I'd better check
with some more experienced users if I'm looking in the right direction.
I'm trying to set up a pipeline that patches a sound generator (or,
ultimately, several generators) to effects. The generators and effects
would be generated by Faust, of course.

Thanks in advance for any insights!

MichaƂ
_______________________________________________
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Reply via email to