This repository was archived by the owner on Aug 23, 2025. It is now read-only.
Connect SalatRepl to other destinations and contexts - #74
Open
cephasteom wants to merge 4 commits into
Open
Conversation
…ntiation so that the underlying audioworklet can connect to something other than the default destination
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi!
A suggestion for giving the user the power to connect the SalatRepl with their own signal chain. We pass any kind of AudioNode on instantiation, it sets the audio context based on the node, then connects to it each time we run some code.
Responding to this issue.
Updated Readme.