3 ms·
Since we are all here, I have a question. I personally am much more interested in audio sample triggering and/or loop based production in this context than synt
by jrm4 5y ago
Since we are all here, I have a question. I personally am much more interested in audio sample triggering and/or loop based production in this context than synthesis/wave generation -- and it seems like the overwhelming majority of tools are focused on the latter.
In my head, I'm imagining a more programmatic approach to "arrangement of samples and loops," as in, instead of, or perhaps complementing, the classic "grid" or "buttons" view -- something like,e.g.:
- Specify 4/4 @ 95bpm for the piece
- Sample 1, a drum loop stretched/and or pitched
- Sample 2, a hit on the 2nd beat of each interval
- Sample 3, a simple electric piano melody, repeating over X intervals.
- Sample 4, a pad with an echo/reverb
etc. Now, what should be easy to do is to switch out, e.g. which drum loop, or change your piano to a trumpet. I get that MIDI is okay for this -- but is of course better for the latter situation and not great for effects and audio samples.
Your Abletons and so forth are not bad at this, of course, but - and maybe this what I'm describing -- Ableton's features -- but doable in vim, perhaps with the ability to create functions et al on the fly, which strikes me as a potentially powerful way to "group" musical sounds/ideas/intervals/melodies/chords/effects etc etc
- smrq 5y agoSounds like you might be more interested in live coding. Overtone [1] can do what I think you are describing, and more--it's a frontend to SuperCollider, which has all the audio synthesis stuff you aren't interested in, but it can trigger samples fine. Of course, if Clojure isn't your thing, there are other live coding tools out there. I'm partial to Orca [2] myself. [1] https://github.com/overtone/overtone https://github.com/overtone/overtone [2] https://github.com/hundredrabbits/Orca https://github.com/hundredrabbits/Orca
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- qrv3w 5y agoEchoing a lot of sentiment here, you can do pretty much all of these things with SuperCollider. I'd go straight to SuperCollider rather than a "frontend" like Overtone/SonicPi. Not that these frontends are bad, but SuperCollider also has a nice frontend - the IDE works great with builtin doc searching, autocompletion, etc. Sample wrangling becomes pretty thorny quickly as if you are triggering samples you want to make sure they don't "clip"/"pop" when you change them (due to discontinuities between the abrupt stop and the new start). I wrote a SuperCollider tutorial that demo's how to make a really high-quality sample player that takes care of these kinds of things plus gives you lots of control over rates, looping, etc. [1] That was my main hurdle with SuperCollider as that it has surprisingly few tutorials for such a long-running and deep program. Hopefully that helps :) [1] https://schollz.com/blog/sampler/ https://schollz.com/blog/sampler/
- jrm4 5y agoThis looks cool! I haven't played around with these sorts of things in a long time, but yes, it's always felt like "samples" have been a second class citizen in these deals -- but of course, ought to be able to be abstracted away with functional programming.
- iainctduncan 5y agoYou can do all that in any of the major music programming languages. Max, Pure Data, Csound, Supercollider, all have tons of facilities for this kind of thing. The Cipriani & Giri books for Max cover working with samples and loops in great detail and are fantastic books.