Open Asmatzaile opened 5 months ago
Hey, just looked onto that code! And I think I am coming closer to understanding the purpose of guides :)
As sig, segment and discretise are very related to oscillator use, maybe I could reword that part, making it more guide-like? Like "creating custom oscillators"and walk you through a how-to, with sig
. For segment
and discretise
, something like: "using oscillators as structure" and also a how-to guide? I think I would need some help with the sig
function :)
And about the section on sample manipulation, I'm down for it! Maybe the guides on sample trimming and sample slicing could be combined in a guide about dealing with longer samples, like lessons 2-3-4 from week 3 in Alex's video course. But maybe that would result in too long of a guide. What do you think about that?
That makes sense to me!
Maybe the guides on sample trimming and sample slicing could be combined in a guide about dealing with longer samples, like lessons 2-3-4 from week 3 in Alex's video course. But maybe that would result in too long of a guide. What do you think about that?
I think it's totally fine if we don't replicate the information in the video course but just link to it, if we want to keep the section from getting too long.
I made a more guide-like sample-slicing page proposal at #7 :)
Oscillators/signals guide at #11, sample trimming guide at #12
Hey, thanks for this! As I'm taking a look today, I realised that this is basically the list of functions and descriptions that were moved into the source code ... In other words, these function lists are already included in the reference section (e.g.,
sig
,segment
,discretise
, etc.).The guide section should contain guides that specifically walk the user through the process of achieving something specific, (see the section on how-to guides in the GUToD).
So, I'm currently thinking that we can maybe add the idea for a section on sample manipulation on the to-do list, to make a proper guide, and keep these functions in the reference section for now. What do you think?