Join GitHub today
class library: plot relative to target synth #3088
Sometimes, one needs to plot values from a synth that depends on node
This is great. I wonder if scope should have something similar? /* Josh Parmenter www.realizedsound.net/josh */…
On Aug 1, 2017, at 09:33, Julian Rohrhuber ***@***.***> wrote: Sometimes, one needs to plot values from a synth that depends on node order. E.g. a synth that reads from a bus. This patch allows us to determine the point at which the plotting synth is inserted in the node order. It is inserted after the target node. By default, this is the default group of the default server. This follows the asTarget interface, as documented in scdoc. You can view, comment on, or merge this pull request online at: #3088 Commit Summary class library: plot relative to target synth File Changes M HelpSource/Classes/Function.schelp (17) M SCClassLibrary/Common/Core/Function.sc (10) Patch Links: https://github.com/supercollider/supercollider/pull/3088.patch https://github.com/supercollider/supercollider/pull/3088.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
I'd suggest the following: for now, I don't change the names, but when we make the next version step from 3.9 to 3.10, we do the breaking change. I could open an issue with that milestone, so we don't forget.
We could use that as an occasion to fix as many similar cases as possible.
This is already milestoned as 3.10... should it not be?
If the policy is that we can always make breaking changes in a minor release, I don't see why we would need (or want) to group them.
May 12, 2018
referenced this pull request
Jul 13, 2018
i'm a little dissatisfied with this loadToFloatArray/getToFloatArray API, one only working for local servers and one working for all servers but unreliably. i don't really dig the names either, the differences between them is not obvious.
would it make sense for
if that's the case, could the get/load dichotomy be abstracted in the Buffer class? and also, let's take this opportunity to rename these methods so it's easier to tell what they're doing.
so just by calling