Syntakt Science Lab

Probably yes, what we could do is gather just all available sounds and then make a public excel sheet and rate them or smth.

The only problem I see is that when you make a kick from a HH sound, you rely a lot on the FX track , so sounds should be sufficient as is. That will be a testament to the machine though. We could also annotate with a * if a sound needs boost from fx

this is a great idea indeed!

as an alternative or in addition, how about having a dedicated thread per elektron device for distributing / showing off individual sounds, optionally in the context of a song.

simple rules could be:

  1. a few words about how the sound works, how it was made (for educational purposes)
  2. an audio sample showcasing the sound for immediate playability
  3. a copy of the sound in the format of the respective elektron device

all sounds shared are shared via generous licensing terms tbd :slight_smile:

so everyone could grab all the sounds they like most, rating (if necessary) via ā€œlikesā€.

While we all appreciate some new sounds, I also feel this could sidetrack things in terms of what I personally think SSL’s are about. I can imagine what would happen - most folks would just wait for the sound pack to drop, instead of trying to learn how to coax new sounds from the machines themselves. So in a way, wouldn’t that detract from the original idea of the SSL’s? Which I always thought was about getting to know the box deeper…

So while I aint opposing the idea per se, I wouldn’t personally want to prioritize the sound bank aspect too much

Also, the sounds are already there in the sysex data ppl have posted, you dont have to wait… Surely, if you hear a sound you absolutely love, its not too much ask to DL said sysex, load it into your box, find the sound and save it to your plusdrive? All it costs you is time… and the dopamine reward you get for expending some effort for it is greater than downloading a bunch of stuff you later ā€œforgetā€ to even use… (Disclaimer - I am a cynic when it comes to human nature, and believe we all gravitate to the least path of resistance all too easily. Modern conveniences make us lazy and all that)

hmm… I don’t personally feel responsible for what people download and how they are going to use it. if someone instead prefers using the sounds instead of learning from the patches, fine with me. it’s always an option, but, if I may speak for myself, I wouldn’t share those sounds primarily with the goal in mind of expecting everyone to use it in a particular way but rather for having a competitive hobby among sound design nerds, pushing limits, learning from each others, exploring. i feel doing it this way is an even more sound-design centered approach.

1 Like

I love the idea. It would be a nice celebration of the work and the results the SSLs will produce. I also think it would feel like a much more convenient and accessible way of getting your hands on those sounds.

If we should be so lucky as to get Elektron’s attention on this, we would reach out to a lot more people as well.

Off the top of my head, I’m thinking of two issues to consider:

  1. Too many of my sounds are pretty boring in their basic form. It’s when forming part of a pattern with p-locks, FX processing, interaction with other sounds etc I feel that they come alive. I’m worried that when trying to extract a sound from a track I’ll end up with a ā€œstatic sampleā€, if that makes sense. That doesn’t have to be true for everyone though. We probably work in different ways.
  2. (already mentioned by someone else) It’s going to take some effort to compile, sort and curate it all. If we find someone willing to put in the work then that’s great. But we need to grant this person the artistic freedom to curate, delete and alter as they see fit to make a nice and presentable overall package.

I’m not so worried about this taking focus away from our regular SSLs. Saving sounds could be just be a small additional activity when you’re finishing your efforts in an SSL. Go through the patterns you’ve created, save the sounds you like to a separate SSL bank.

Maybe it’s a good idea to find a naming system already now? So we don’t have to go back and edit the names of XXX number of sounds later :slight_smile:

3 Likes

Yes, this is nr 1 problem for me as well, my experience is that the magic lies into the organic interactions between sounds, gain staging, fighting for headroom etc. not all sounds are created equal I guess…

I guess not all machines are made equal as well, and people will be able to extract much more versatile palette from SY Bits for example, which is it’s own synth, compared to some HH machine.

I guess there is also distinction on what kind of material people want to post in the SSLs - if you compose and like to post beats, that’s when FX is crucial, if you just post examples of sounds (how to make a clap or a snap), it’s more connected to the actual engine

1 Like

Yeah, I feel the same.

We don’t have to decide now though. We’ve only just begun so this may develop in new directions. After 20-30 labs we may see things in a different perspective, and other options may surface. It’s a great idea, so let’s just store it in the back of our minds and bring it up again when we’ve come a bit further.

NOTE I’m not meaning to silence the discussion. More thoughts are welcome, as always :slight_smile:

Totally, let’s focus on the labs as is and have this in mind;)

How about an entirely distinct SSL which focuses entirely on creating playable sounds instead of patterns? This would immediately lead to sounds created with the intention of being played, such a thing would be trivial to turn into a sound bank later. It could be a long running SSL just like the ones we have already (ie with no definite closing date)

Maybe its just the way my brain is wired, but this would be a better alternative IMHO than to spend a lot of resources into turning other SSLs into reusable sounds

1 Like

Would a separate running SSL thread for just ST Sounds be okay instead? That’d make it optional for those that want to participate with exporting the sounds.

It also leaves room, without commitment for curation or leaving as is for the curious ST user.

2 Likes

Forgot to reply to this. The SY Chord is my number 1 Syntakt machine :heart: It’s limitless. One of the tracks I’m most proud of was done entirely with SY chord. I’m excited to hear what you all will squeeze out of it :slight_smile:

4 Likes

My personal gripe with the chord machine is the inability to get a tracked analogue filter after it. If the FX track ever gets filter keytracking, I will cry tears of joy

I guess you know about the key tracking on the digital filter… it’s not analog though :slight_smile: So you’re left with p-locking the FX filter cutoff, which is pretty tedious.

About using sysex versus Elektron’s proprietary formats to dump data. I’ve been meaning to address this and add some info in the original post. But I must admit I’m not entirely sure about all the differences. Here’s an attempt at a small write-up. Please correct me if I’ve gotten some of the details wrong, and please add any useful info:

With sysex you can transmit/receive OS files, projects and patterns. You’ll need a sysex tool. Elektron used to offer C6 for this, which was very easy to use. I don’t think it’s available anymore, though you may find it in some old buried corner on elektron.se. There are other alternatives. You can use either the MIDI port or the USB port for sysex. (I’ll add a link if I can find it)

With the proprietary format you can transmit/receive OS files, projects and sounds. You’re locked to using Transfer. Personally I find it very easy to use. You’ll need to use USB as far as I know.

The main drawback to dumping only patterns is that any sound locks will be lost.

Really? I didn’t know this… Is this because sound locks require the sound pool of a project to be configured a certain way, hence requiring the entire project memory? I suppose a pattn only saves the sound pool slot number info on the sound lock trigs…

C6 can be downloaded from archive.org - someone linked to it on this board only a few days ago. You can also use any sysex librarian software, there are plenty out there for every platform (including iOS & Android)

I just tried it to be 100% certain. I exported a pattern with sound locks from one project and imported it to another using C6. It keeps the trigs but not the sounds, they’re just replaced by whatever sound is stored on that track. It just says Ā«sound 4Ā» instead of the sound name if you hold the trig.

The explanation must be that locked sounds are stored in the sound pool, not in the pattern. If it did export the sound pool sounds as well, it would need to correct the links when exporting to the new project. If not, there would be a risk of overwriting sounds in the new project sound pool. At least that’s my guess.

I found a C6 download link on elektron’s home page as well:
https://www.elektron.se/support-downloads/machinedrum

1 Like

Confirms what I thought. Pattn without sound pool data will result in incorrect recall… although there could be a source of happy accidents in there somewhere?

1 Like

Hah, yeah I guess. The cumbersome version of changing kits randomly on an MD/MnM :sunglasses:

New SSL is up here !

2 Likes

I think we’re going to see some amazing takes on this one.

1 Like

What do you think peeps? We’ve done a decent job of crafting sounds, beats and atmospheres from the SY Chord. The thread activity has gone down lately, so maybe it’s time for a new lab?

What machine would you like to explore this time?
Please post your suggestions here :slight_smile:

If you have any other comments or thoughts related to the SSL, they’re always welcome. Please post them here.