Doh - think I replaced the default samples with the new ones instead of adding:
s.waitForBoot {
~dirt = SuperDirt(16, s); // two output channels, increase if you want to pan across more channels
~dirt.loadSoundFiles("/Users/Me/Desktop/Tidal/samples-extra/*"); // load samples (path containing a wildcard can be passed in)
// for example: ~dirt.loadSoundFiles("/Users/myUserName/Dirt/samples/*");
// s.sync; // optionally: wait for samples to be read
~dirt.start(57120, [0, 0]); // start listening on port 57120, create two busses each sending audio to channel 0
Edit just saw this * You’ll see a line with ~dirt.loadSoundFiles; , which loads the default samples.
Keep that line, creating a new line underneath that looks like this:
Ended up repasting superdirt_startup.scd into startup.scd.
It can be useful if you want to keep your personal sound library separated from the default tidal installation e.g. on a USB stick, separate partition etc. (that's something I do a lot since I frequently format my drive, reinstall the OS and whatnot)
Or maybe you want to make a GitHub repo for your tidal work: basically just create a folder (e.g. my-tidal-folder) where you'll keep all your samples, code snippets, notes, songs etc. and put it on a GitHub repo. This way you don't risk loosing anything and your material is always available and up to date, even on multiple machines; all you have to do is download the folder and set up the path as shown in the video. Here's mine as an example. I've also added the BootTidal.hs and startup.csd so I don't lose them
CPU Electro samples! I’ve been loving their releases, looking forward to exploring these samples further. One note from my install process: in Windows it was necessary for me to include the drive letter in that path.
Hey! It worked for me on the Mac (Catalina) as well. The only hiccup was that somehow the file was read-only through superCollider but I could edit it through the terminal.
I have a doubt regarding the bigger loops in the break folder. When I play them in tidal they get all mushy and cramped. How can I play them at their normal speed?
Hi @indiantinker, working with long samples is a fairly large topic that we will get to later in the course.
The problem you’re hearing is that in tidal, you’re triggering the sound every cycle, but the break sounds last longer than a cycle. There are a few ways around this, here’s one:
d1 $ loopAt 2 $ chop 32 $ sound "break"
Adjust the loopAt number to spread the break over that number of cycles. You can also adjust the tempo with e.g. setcps 0.6, trying different numbers to hear the effect.
As I say there are a lot of different approaches to this, there is fun to come!
Ah, I have the latest development version which I see Julian Rohrhuber (the creator of SuperDirt) has changed a bit recently. I don’t think you’ll see any difference with your version, I don’t understand it fully but think this change is just a small tweak. However if you want the latest version you can copy and paste it from here: https://github.com/musikinformatik/SuperDirt/blob/develop/superdirt_startup.scd
I have changed it but it doesn't make much of a difference.
I have also noticed that when I recompile the class language it does not instantly import the samples from the folder, I have to run the script to load in the samples. This appears to be different to how yours load in the video, am I missing something here as well?
Hi @yaxu,
I have a question!
What do you exactly mean by:
Does this mean that collider only indexes the dirt-samples folder once (e.g. the time of the creation of the folder) so even if I added some custom tracks to it, they wont be indexed?
No I mean that if someone contributes more sounds to the dirt-samples quark, and you’ve changed your copy, the supercollider gui won’t be able to download the new samples.
Yes you’re probably using an old startup file? The current one should start with 12 orbits by default. d1, d2 etc are set up to use a different orbit, e.g. so they have separate global effects like reverb (will have a closer look at this sometime).
