Saike's workshop [ JSFX | Synth | Creative FX | Nonlinear Filters ]

[sai'ke]

Originally Posted by Cosmic

Dum Drums in AWESOME!!!!!!!!

Also..it is by far the best looking plugin Ive ever seen and the way it wobbles when you hit a drum. INCREDIBLE!

Thanks you so much man. These are beautiful instruments you are making

In fact I'm gonna do a whole EP with just your instruments ..and reasamplomatic

<3

Originally Posted by danerius

This sounds so amazing saike. Big, big, big, big thanks

Dont know if its just me not getting it but the only midi to audio that is making sounds is the kick. Ive tried reassigning and assigning the sounds to midi keys but nothing works?

Best regards /Bo

Is it possible you enabled multi-out by accident? Multi-out gives each sound their own channel (sending the kick to channel 1-2, snare to 3-4 ... etc).

Click the button "MUL" to enable/disable this mode.

Originally Posted by juan_r

I wonder: what are the 4 small squares (macropixels?) under the pads?
Maybe a tooltip could be appropriate?

They are options for that particular drum sound. Just different synthesis algorithms for that particular drum sound. I'll add a little info for it.

[TonE]

Originally Posted by juan_r

Could you please link the jsfx (and maybe your presets in the Stash)?

One technique, typing in google: "euclidean rhythm jsfx"
would give the results.

Anyway:
https://forum.cockos.com/showthread.php?t=94325

Searching in stash for "Euklid" gives:
https://stash.reaper.fm/browse.php?q=Euklid&x=0&y=0
Direct link:
https://stash.reaper.fm/v/37847/vst-Euklid.ini

[TonE]

Midi mappings should not be part of presets, imo. Not sure what other users think? At least in my case I do not want to change the mappings that often, after finding one working set. Thus all the presets from other users (with a different mapping) should be later usable here as well.
While testing around, I saw mappings changed as well, maybe this is only due to alpha state, and was not intended functionality. Perfect otherwise, as always and used to from master saike! Multi-out is also perfect, thanks a lot for the turbo implementation.

[juan_r]

@TonE Thanks for doing my homework
Seriously, it's for future searchers

BTW On the mapping you're spot on, I think.
Mappings belong in some control section, independent from sound data.

@Saike Ah, I see.
The effect of algorithm choice is fairly variable from sound to sound.
Thanks for the info!

[danerius]

Originally Posted by sai'ke

<3
Is it possible you enabled multi-out by accident? Multi-out gives each sound their own channel (sending the kick to channel 1-2, snare to 3-4 ... etc).

Click the button "MUL" to enable/disable this mode.

Yep. That was it. Thanks saike

[sai'ke]

Originally Posted by TonE

Midi mappings should not be part of presets, imo. Not sure what other users think? At least in my case I do not want to change the mappings that often, after finding one working set. Thus all the presets from other users (with a different mapping) should be later usable here as well.

Originally Posted by juan_r

BTW On the mapping you're spot on, I think.
Mappings belong in some control section, independent from sound data.

I agree and I would have preferred it that way, but I see no sensible way of achieving that within the confines of JSFX.

Ideally, what I'd want is for the controller mapping to be part of the project. But as far as I know, JSFX does not really have access to ext state.

That leaves the option of storing it in a different file on the path (but that makes the mappings global, which imo is more undesirable than part of the preset).

What I could do is add a copy/paste thing to the mapping, so that at least it would make it easier to copy the mapping from one preset to another, and then you could just fairly easily make copies of a preset with a different mapping.

[juan_r]

Just a wild hypothesis, but there could be mapping-only presets (with some out-of-range placeholder for sound data) and sound-only presets (with some out-of-range placeholder for mapping data). But maybe this gets ugly.

On the other hand, your copy-paste workaround might be a sensible solution, not too hard to implement.

Of course, the only judge of that is... you, Saike!

[IXix]

Originally Posted by sai'ke

Ideally, what I'd want is for the controller mapping to be part of the project. But as far as I know, JSFX does not really have access to ext state.

You can load data from a text file in the data resources folder, using a file slider. If you did that then the mapping would be stored in the project/preset but changing to another would be very easy.

[Tapio]

Will you make your incredible Filther resizable at some point? It's pretty small on 2k or 4k. Thx

Originally Posted by TonE

Of course. There are 3 solutions, I know, 2 jsfx, 1 vst from pure data.

Thanks, very helpful, using https://patchstorage.com/euklid/ with big pleasure now.

[sai'ke]

Originally Posted by IXix

You can load data from a text file in the data resources folder, using a file slider. If you did that then the mapping would be stored in the project/preset but changing to another would be very easy.

On the one hand I like that idea. But on the other, one would have to remember to copy that file when migrating to a different system. I quite like having the preset be self contained. But perhaps there is a good middle ground to be found. Maybe a combination of both. Store it in the preset in its entirety, but allow a few layouts to be saved in a separate file.

Originally Posted by Tapio

Will you make your incredible Filther resizable at some point? It's pretty small on 2k or 4k. Thx

Are you on 3.14? To me it looks workable on 4K? You can also add 20% extra size by double clicking the fan on the top left. I just made a few minor adjustments to make some of the font rendering look a bit better on higher dpi screens in 3.15. This is what it is supposed to look like with the extra 20%: https://i.imgur.com/WgYcO0I.png

If you want it to rescale continuously, uncomment the line (in 3.15):

// retina_scaling = min(gfx_w/1135, gfx_h/785);

[TonE]

Regarding preset saving mechanism I have two ideas.

1. UX gets another additional button "GM", when pressed input will be mapped to GM (General Midi) mapping. Thus this mapping can be used as 'standard mapping' among all users, in case you do not like the original mapping, included in the preset.

2. Using a second jsfx which is auto-preloaded to DD-Drums, similarly as done for hackey trackey for the midi input stuff. Maybe a similar strategy could be useful here. All the preset saving/loading job would be delegated to this 'worker jsfx'.

Apart from these suggestions, I also like keeping a little chaos in the music making process, leading to potential happy accidents, when using others mappings with their sounds, together with your programmed note patterns. I had already such nice accidents. And in case you want to switch to your mapping, it is not difficult to click quickly your main notes. The UX is done very well, and quick! Most elegant I could see so far, very direct. No 'visual' noise.

Dear saike, keep up your great work, hope above ideas are maybe interesting to some degree. GM button could be extended over time to alternative 'standard' mappings, via a right click menu... My preferred mapping would be probably anyway GM mapping, as most compatible with rest of midi drums world.

[Tapio]

Originally Posted by sai'ke

You can also add 20% extra size by double clicking the fan on the top left. I just made a few minor adjustments to make some of the font rendering look a bit better on higher dpi screens in 3.15. This is what it is supposed to look like with the extra 20%: https://i.imgur.com/WgYcO0I.png

Hi, thx, what is the fan on the top left? Yes, 3.15 and said line was already uncommented. The UI does not scale with Reapers window btw., see screenshot. https://imgur.com/aioMCMA I was wrong it's not 2k, but 1440p here.
EDIT: I found the top left click area. It's invisible for me, maybe visible in a totally dark room. Thx, this +20% extra is OK for me.

[EpicSounds]

Gave DD-101 a try on my last stream and just published that section as a separate video

https://youtu.be/jZVZ1FAtot4

I had a lot of fun with it.

Curious what you plan to change or add to take this out of Alpha state

[sai'ke]

Originally Posted by EpicSounds

Gave DD-101 a try on my last stream and just published that section as a separate video

https://youtu.be/jZVZ1FAtot4

I had a lot of fun with it.

Curious what you plan to change or add to take this out of Alpha state

Hey man! Thanks for the kind words and the awesome video!

Not sure yet. Any specific thing you were thinking of?

One thing I added recently (after watching your video actually) is the ability to set the parameters for the open and closed hihat independently (and not have them voice steal from eachother). The little tab on the bottom left of the open hihat controls enabled/disables linking.

I might add a few more kit options (maybe to round them all out to 4), but I need to find a solid chunk of time to do it. That doesn't necessarily block alpha though. And maybe a few more customization controls.

[Wayne Kerr]

Hey Saike, I seem to have some problems with Partials. I've used it for some time now but suddenly it crashes Reaper when inserting a new instance on a track, giving a Runtime Error message. Projects with the plugin already in them are actually working fine. The problem only happens when loading a new instance, 100% of the time. I tried reinstalling it but the problem still persists. Any ideas what might cause this issue? I'm running the newest versions of both Reaper and ReaPack.

[sai'ke]

Originally Posted by Wayne Kerr

Hey Saike, I seem to have some problems with Partials. I've used it for some time now but suddenly it crashes Reaper when inserting a new instance on a track, giving a Runtime Error message. Projects with the plugin already in them are actually working fine. The problem only happens when loading a new instance, 100% of the time. I tried reinstalling it but the problem still persists. Any ideas what might cause this issue? I'm running the newest versions of both Reaper and ReaPack.

Hey, sorry this is happening to you. Partials shouldn't be able to cause a runtime error since REAPER's JSFX interpreter should be handling all the risky type of operations.

That said, maybe we can narrow down what might be happening.

By latest version, do you mean the latest stable REAPER versions, right? That is 6.83 and not a dev version.

If so, is it possible to cook it down to an example that only uses JSFX instances (removing all other plugins from a copy of the project)? This is to exclude the possibility that another plugin might be causing the issue and to attempt getting me a reproducible example to test with.

[Wayne Kerr]

Yeah, this is a weird one, since the projects with other plugins and Partials open up normally (even with other 3rd party vst, clap, etc. plugins).

Yes, I'm running the stable 6.83

The specific conditions of the crash are:
1. I open up a new project
2. load up Partials (loads normally)
3. insert a midi item
4. try opening the item in editor
5. crash

Opening a midi item in order to edit it, crashes reaper but ONLY when Partials is loaded up on that track. That's why I'm writing to you specifically, since I have never had a problem with other plugins and the conditions are oddly specific. Other plugins that you made also work with no problems, it's a Partials specific thing....

I've just tested a use case, that didn't crash. I inserted a midi item, loaded SEQS, AND THEN Partials, which results in everything working fine.

It just makes no sense ??

EDIT:
Just did another test, opening up a new instance of Partials on an empty track immediately crashes Reaper (regardless of the track having a midi item or not), but putting a random plugin in front of Partials before loading Partials results in everything working fine.

[sai'ke]

I first tried to reproduce it on the latest REAPER for a while, but wasn't able to.

So I asked around a bit and from what I gathered REAPER doesn't use C++ exceptions (the image you posted suggests that the crash is a C++ exception).

But that leaves as only option that there must still be another plugin that crashes.

Is there anything else that you may have running as a plugin by default for a new project that you know of? It would have to be a binary plugin (like a VST or extension rather than a JSFX or lua script).

[sai'ke]

Added two small new features to Yutani. The first is the option to change the envelope shape a bit. The second is a stack of saturating allpass filters with feedback at the end of the chain to smear the sound a bit.

Two short demos here:
https://github.com/JoepVanlier/Audio...ed_yutani2.mp3 (briefly dry, then enabling the allpass stack, automating envelope shape a bit as well)
https://github.com/JoepVanlier/Audio...filthy_yut.mp3 (only with)

[sai'ke]

Small additions to Yutani:

- Text entry for some of the knobs (note only numeric values, not measures). Note that some of the non-labelled settings are in % (morph for instance).
- Allow increasing the range of the bonus oscillators to enable making chordey sounds.



Allows you to quickly make pads like these:

https://github.com/JoepVanlier/Audio.../thick_yut.mp3

Also working on a new preset pack to show off some of the new sonic options.

[TonE]

Dear saike, thanks for the updates, The chordey examples sound great. Like it is now a new synth, not only for leads and basslines. Together with DD-101 we have all sound types, drums, bass, melody, now even chords. Cool, thanks a lot friend. Time to update and test!

[Wayne Kerr]

Originally Posted by sai'ke

I first tried to reproduce it on the latest REAPER for a while, but wasn't able to.

So I asked around a bit and from what I gathered REAPER doesn't use C++ exceptions (the image you posted suggests that the crash is a C++ exception).

But that leaves as only option that there must still be another plugin that crashes.

Is there anything else that you may have running as a plugin by default for a new project that you know of? It would have to be a binary plugin (like a VST or extension rather than a JSFX or lua script).

Thanks for taking your time, so far I haven't found the culprit yet. I'll try digging around and see if I can fix it. I'm trying to avoid a fresh Reaper install but maybe I'll try that when I have the time.

[sai'ke]

Originally Posted by Wayne Kerr

Thanks for taking your time, so far I haven't found the culprit yet. I'll try digging around and see if I can fix it. I'm trying to avoid a fresh Reaper install but maybe I'll try that when I have the time.

Yeah, sorry I couldn't be of more help. It can be a pain to find the culprit with these things.

[glitched]

RE: SEQS
I get a large DC offset when using "record sample" with "play sample." When I deactivate "play sample," the offset goes away. Including a DC offset filter after SEQS solves the problem.

Here's a link to the presets .ini: https://www.dropbox.com/scl/fi/lson8...8hedby18w&dl=0

The preset in question is "error."

EDIT:
The offset is actually rather small, but with extreme compression settings (later in the FX chain), it can get crazy. So, yeah, actually not a big deal, but let me know if you are seeing the same thing.

Reaper 7.02.

[TonE]

Dear saike, all sequencers containing probability (arp and SEQS, maybe DD-101 as well) could add "trigger conditions" as well (as known from some Elektron hardware devices). See (free) ChanceMachine vst here: https://forum.cockos.com/showpost.ph...7&postcount=11
Github c++ source code for ChanceMachine is available in above link.

Probabilty + trigger conditions together are quite useful, powerful and leading to interesting variations even within short 1 bar patterns.

Summary of suggestions:
- arp + probabilty + trigger conditions
- seqs + probability + trigger conditions
- dd-101 + probability + trigger conditions

- jsfx ChanceMachine, if not too difficult as well

[sai'ke]

Originally Posted by glitched

RE: SEQS
I get a large DC offset when using "record sample" with "play sample." When I deactivate "play sample," the offset goes away. Including a DC offset filter after SEQS solves the problem.

Here's a link to the presets .ini: https://www.dropbox.com/scl/fi/lson8...8hedby18w&dl=0

The preset in question is "error."

EDIT:
The offset is actually rather small, but with extreme compression settings (later in the FX chain), it can get crazy. So, yeah, actually not a big deal, but let me know if you are seeing the same thing.

Reaper 7.02.

Thanks for the report! I'll look into it next time I get the chance.

Originally Posted by TonE

Dear saike, all sequencers containing probability (arp and SEQS, maybe DD-101 as well) could add "trigger conditions" as well (as known from some Elektron hardware devices). See (free) ChanceMachine vst here: https://forum.cockos.com/showpost.ph...7&postcount=11
Github c++ source code for ChanceMachine is available in above link.

I'll think about it. It seems like something that might make sense in the context of arp and seqs, but I'd have to find a way to unobtrusively build it in.

Updates
For those of you that are sick of the default oscillator shapes in Yutani, I added some basic wavetable functionality.


You basically set the oscillator to WT, then drag in a sample. By default, it expects wavetables to be samples where each oscillation is 2048 samples long and it loads the first 8 frames.


If your sample is not of a format of 2048 samples per cycle, it is recommended to enable the pitch button. This will attempt to detect the pitch of the sample and load it correctly.

You can link the wavetable position to MIDI velocity, mod wheel and/or the "free LFO" (bottom left).

I also added a few extra presets that demonstrate the new features (the allpass stack, the semitone polyphony options, the wavetables and shape parameters).

Here are some audio examples of me just randomly dinking around with it:

A few lighter patches:
https://github.com/JoepVanlier/Audio.../something.mp3

Cheesy old synth-inspired things:
https://github.com/JoepVanlier/Audio...ool_yutani.mp3

Some more aggressive stuff:
https://github.com/JoepVanlier/Audio...t_wt_test3.mp3

Do note that this is all still in beta. Good luck.

[Cosmic]

Holy mackeral!! Nice one man!

[juan_r]

Sai'ke is the man.

[Vagelis]

Yutani is such a beast, Lately I've been using it with the new FX container feedback, and injected Yutani as a source. I really like the noise types, I made some kick ass physical modelling sounds. Thanks Saike!

It would be nice to know, what inharmonicity does? Combined with the above it was such a killer combo! I was thinking to try replicating it in my hardware synth if I knew what's behind

Also thanks for the wavetable OSC, it's great

[todd_r]

Originally Posted by sai'ke

For those of you that are sick of the default oscillator shapes in Yutani, I added some basic wavetable functionality.

Amazing!! Thanks Sai'ke!

Originally Posted by Vagelis

've been using it with the new FX container feedback, and injected Yutani as a source. I really like the noise types, I made some kick ass physical modelling sounds..

Intriguing! Feel free to share lol

[Vagelis]

Originally Posted by todd_r

Intriguing! Feel free to share lol

Of course Saved an example project with a simple loop and Yutani in the container. The delay after Yutani feeds back to it self, then the feedback goes through eq (you can shape it with LP/HP filters). At the end there's a limiter and a channel mapper downmixer to adjust the feedback amount (channel 3-4)

https://mega.nz/file/QV4FXIDZ#XkUzal...6QfKRLI1i2fMzs

And there was a discussion about container feedback with some examples here:
https://forum.cockos.com/showthread.php?t=283409

[glitched]

Originally Posted by sai'ke

Thanks for the report! I'll look into it next time I get the chance.

Great!
Also found this one a while back:

SEQS glitches up (in a bad way) when probability is introduced to a "record sample" lane.

Having multiple "play sample" triggers when one of the recording trigs is as above causes Reaper to mute the track.

Simple test:
1) Place a trigger anywhere on "record sample" lane. (Enable the lane, obviously.)
2) Change the probability to anything but 100%
UI of the Record Sample lane changes to all filled blocks. This is not expected.
3) Now, enable the Play Sample lane and put some trigs there using the "randomize" function. At best, the audio coming through will merely clip, but...
4) On the sample play lane, change the probability of a trig to anything but 100%. Reaper should auto-mute.

I discovered these bugs as I was using the "randomize" function on the sample lanes, then messing around with probability of the active steps.

Love your plugins. Best regards.

[todd_r]

Originally Posted by Vagelis

Of course Saved an example project with a simple loop and Yutani in the container. The delay after Yutani feeds back to it self, then the feedback goes through eq (you can shape it with LP/HP filters). At the end there's a limiter and a channel mapper downmixer to adjust the feedback amount (channel 3-4)

https://mega.nz/file/QV4FXIDZ#XkUzal...6QfKRLI1i2fMzs

And there was a discussion about container feedback with some examples here:
https://forum.cockos.com/showthread.php?t=283409

Ah brilliant thanks! I'll have a look through, I missed the whole feedback with containers thing

[juan_r]

Maybe Yutani and Dum Drums could be tagged as instruments? And Partials too?

Originally Posted by souk21

I think you might have missed this
From v6.74:

EDIT - Synced ReaPack and found your instruments tagged. Maybe it's just a nitpick, but it does feel good. Thanks, @Saike!

[sai'ke]

Originally Posted by glitched

RE: SEQS
I get a large DC offset when using "record sample" with "play sample." When I deactivate "play sample," the offset goes away. Including a DC offset filter after SEQS solves the problem.

Here's a link to the presets .ini: https://www.dropbox.com/scl/fi/lson8...8hedby18w&dl=0

The preset in question is "error."

EDIT:
The offset is actually rather small, but with extreme compression settings (later in the FX chain), it can get crazy. So, yeah, actually not a big deal, but let me know if you are seeing the same thing.

Reaper 7.02.

Fixed in v0.125! Thank you for the report. Was a matter of not setting the fadeout all the way to zero when playback was stopped.

Originally Posted by Cosmic

Holy mackeral!! Nice one man!

Thank you!

Originally Posted by Vagelis

It would be nice to know, what inharmonicity does?

Inharmonicity applies a frequency shifter while playing the synth note at a compensated pitch to make sure the fundamental still ends up on the old location.

Originally Posted by glitched

Great!
Also found this one a while back:

SEQS glitches up (in a bad way) when probability is introduced to a "record sample" lane.

Having multiple "play sample" triggers when one of the recording trigs is as above causes Reaper to mute the track.

Simple test:
1) Place a trigger anywhere on "record sample" lane. (Enable the lane, obviously.)
2) Change the probability to anything but 100%
UI of the Record Sample lane changes to all filled blocks. This is not expected.
3) Now, enable the Play Sample lane and put some trigs there using the "randomize" function. At best, the audio coming through will merely clip, but...
4) On the sample play lane, change the probability of a trig to anything but 100%. Reaper should auto-mute.

I discovered these bugs as I was using the "randomize" function on the sample lanes, then messing around with probability of the active steps.

Love your plugins. Best regards.

Hah, that was a fun one. Fixed in v0.124 and newer, thank you for the report.

Originally Posted by juan_r

Maybe Yutani and Dum Drums could be tagged as instruments? And Partials too?

EDIT - Synced ReaPack and found your instruments tagged. Maybe it's just a nitpick, but it does feel good. Thanks, @Saike!

Ghehe, yeah, I did it. When the backlog is still big I usually hold off posting until I have some more things

I had actually seen that thread you referenced before and intended to do it, but then forgot about it again, so thanks for the reminder!

[sai'ke]

Added a few more very filthy filters to Yutani and FM Filter 2. These guys like being overdriven hard. Here you can hear me really leaning into the overdrive and messing with some FM / LFOs:
https://github.com/JoepVanlier/Audio...utani/wild.mp3

Here is without ravager:
https://github.com/JoepVanlier/Audio...no_ravager.mp3

With less resonance, they can also result in a very glue-like saturation effect. First is a linear filter, then I enable the new filter (the two pole variant):
https://github.com/JoepVanlier/Audio...x_material.mp3

[glitched]

Originally Posted by sai'ke

Fixed in v0.125! Thank you for the report. Was a matter of not setting the fadeout all the way to zero when playback was stopped.
...
Hah, that was a fun one. Fixed in v0.124 and newer, thank you for the report.

I appreciate these bug fixes. Now I can go wild with randomize without having to worry about SEQ crashing.

Great plugin, even at this stage.

[TonE]

Originally Posted by glitched

Great plugin, even at this stage.

saike's betas are others finals of the finals.

[Ears]

I was wondering what your next plugin would be.. Dum Drums is awesome, UI/sound. I love to feed it through FM filter 2 and Amaranth and get weird. One of these days I'll figure out how to bridge my weird creations together and make a track out of them..

Yutani update is awesome too. How challenging would it be to add microtonal support? I've been connecting a few of my synths to Oddsounds MTS-ESP Mini, and wondered if it would be possible with Yutani. Unless I missed it and Yutani can already load alternate tuning files?

Maybe useful to you, maybe not:
https://oddsound.com/usingmtsesp.php
https://oddsound.com/devs.php

Thanks for making my days more fun Sai'ke.

[Ears]

Originally Posted by sai'ke

Added a few more very filthy filters to Yutani and FM Filter 2. These guys like being overdriven hard. Here you can hear me really leaning into the overdrive and messing with some FM / LFOs:
https://github.com/JoepVanlier/Audio...utani/wild.mp3

This is very cool.