This example demonstrates how to use an AudioWorklet in r-audio. It also shows a RAnalyser in action.
Notice that the graph only renders after both the media stream and the worklet have been initialised.
\nThis example demonstrates initialising a RBufferSource with a decoded AudioBuffer.
It also shows how to process channels separately.
\nThis example demonstrates how r-audio handles various graph configurations,\n including non-connectable nodes in pipelines and deeply nested parallel/serial connections.
\n\nIt also shows how to create ‘dead-end’ branches using the disconnected attribute.
This example demonstrates how to create custom r-audio nodes.\n This can be done by extending RExtensible,\n which is itself an extension of RPipeline.\n We define the contents of our custom node by overriding the renderGraph method,\n which simply returns a bit of JSX, just like React components'\n render method.
\n This example demonstrates how one can create feedback delay lines using the RCycle component.\n It also shows how scheduling works.\n
Make sure to always include a RGain with gain < 1 to avoid infinite feedback.
\n This example (courtesy of Tom Nixon from\n BBC R&D) shows how we can create complex multichannel graphs\n using RSplitChannels and explicit connectToChannel props.\n
\n Each channel of the stereo input signal is routed to both channels of the output signal\n and each branch is processed by a separate RGain.\n This kind of graph is particularly useful when binauralising audio.\n
\n Stereo audio recording by Freesound user debudding (Public Domain).\n
\nThis example demonstrates plugging a HTML5 Audio element to the r-audio graph using RMediaElementSource. A reference to the audio element could also be obtained via React refs.
This example demonstrates plugging aMediaStream object (from either a WebRTC peer or the native audio input device)\n into the r-audio graph using RMediaStreamSource.
{param}