Help: [skip ci] Getting Started should model correct use of 'out' arg #5137
Conversation
This file contains 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose and Motivation
Just saw a question on Facebook where a new user had hardcoded bus 0 into a SynthDef, and then used a feature that assumes the bus will not be hardcoded.
Since the question was coming from a user who had just started, I wondered if our tutorial series was pointing in the right direction about bus usage.
It doesn't. The tutorials throughout write
Out.ar(0, ...).This PR replaces all of those with
outarguments (following the convention used throughout the class library).I can understand why we wanted the tutorial series to start in the simplest possible place. But the question this morning reveals also that users extrapolate principles from our code examples. So I'm proposing this in the interest of improving the code models we give to beginning users.
Types of changes
To-do list