One Synth Challenge #108: Diodow by HrastProgrammer (Schiing Wins!)

[urlwolf]

It works well on tracktion 7 linux, no resize bug.
Any idea how to audition presets fast with keyboard or pressing a 'next' button or something?

[TheNeverScene]

This contraption is wicked good...sorry for the giddiness.

[kokotte]

Each new instance is getting bigger and it no longer will fit on the monitor where I usually put the synth GUI and if it keeps growing as it has it will soon not fit on my largest monitor either.

I noticed this as well. Sigh. It makes every subsequent instance 150% in size compared to the last one ... Oh well. If anyone encounters that problem, remove the "Scale=150" row from the ini file. I'm testing this at the default 100% now.

Also, for all things considered, it might be a good idea to backup the DiodowPatches folder once in a while . As all patches are saved only there, and a single patch is shared between all project files using it... that kind of stuff is good for paranoia (at least for me), hah.

To recap, have all individual Diodow instances use uniquely named patches, save them every time you actually change the patch and wish to keep the changed version, and at the end of the session, drag the DiodowPatches folder somewhere safe so that you can drag them back if something unexpected happens (like, if you forget to rename a patch and happen to write over something that is critical in another project or instance).

you can duplicate the dll, diodow 1, diodow 2...and every instances should load with the right user size.
i do it with tranzistow and it works .

[EvilDragon]

Any idea how to audition presets fast with keyboard or pressing a 'next' button or something?

You can't. But at least in the browser you don't need to double-click to load a preset (like in Roland's f**king plugins!)

[EvilDragon]

you can duplicate the dll, diodow 1, diodow 2...and every instances should load with the right user size.
i do it with tranzistow and it works .

That's a pretty lame workaround... I've reported this to Hrast.

It looks like this doesn't happen when scaling is at default 100, so perhaps use it like that, if possible.

[TheNeverScene]

So, to piece together the patch thing...any instances using a patch are saved in the host as that patch via Diodow's browser. Any variations need to be saved as a separate new patch for any reloads of a project(s) to keep an instance from reverting back to the original patch. Correct? It's like a soft synth with analog patch memory! lol

edit: it looks like Reaper's built in patch saving/default patch setting/project save and reload as vst state works normally.

BTW @Evildragon, it's the Cockos forums I know you from. Go Reaper!

[Frostline]

So, to piece together the patch thing...any instances using a patch are saved in the host as that patch via Diodow's browser. Any variations need to be saved as a separate new patch for any reloads of a project(s) to keep an instance from reverting back to the original patch. Correct? It's like a soft synth with analog patch memory! lol

The part I am not quite figuring out is how to rename a patch prior to saving in the synth.

I open Diodow, press the init button, it loads the init patch.
I make my adjustments so now it sounds like a snare for example.
Pressing save simply overwrites the init patch(without any opportunity to rename it first) so init now sounds like a snare.

Only workaround I have come up with is then going into file browser, navigating to the patch folder, renaming init to snare and then in Diodow loading the snare patch from there so it updates the patch name.
Sometimes it will let me name a new patch if init patch doesn't exist in the patch folder but often it will just create a new init patch which I then have to go rename.

There must be a less tedious way to do this that I am not seeing.

[Guenon]

Right click the save button instead of left click, and it gives you a "save as" dialog.

Yeah it's pretty esoteric

[TheNeverScene]

That's weird, Frostline. Reaper gave me the option to save in whatever folder (ie the Diodow patch folder), as well as just normal Reaper patch saving (did both just to figure out what was not going to work after finally making a patch without user error crashes, but both worked). I saved the init patch in Reaper's "save as default patch" to make any new instances open as init and that worked too.

I didn't have to right click either. Clearly, Reaper is far superior to all other DAWs. LOL. JUST KIDDING!!

edit: ever since, I've had to right click. If I actually right clicked before, that explains a lot. Caveman style til deadline.

[TheNeverScene]

Yeah it's pretty esoteric

When I saw that you suggested this thing and then saw the interface, I realized that this month was a straight set up!

I had to break out my old CRT monitor just to keep the vibe alive haha

Seriously, though....this synth is great. Thank you. Glad I figured out how to properly install it.

[Frostline]

Right click the save button instead of left click, and it gives you a "save as" dialog.

Yeah it's pretty esoteric

Well thanks for that. I don't know why I didn't right click that. I had right clicked the patch name and got an open dialog window, knew I didn't want that and abandoned right clicking anything else.

I'm possibly the only one that didn't quickly figure out another thing too.
The tabs each have two states depending on how many times clicked. I spent 10 minutes trying to find the noise amt setting after I accidently hit the correct tab twice and noise setting was only in the other tab state.

[Guenon]

Also, right clicking the Init button seems to lead to a built-in patch randomizer o_o ...? I have no idea how to use it, precisely. It seems it changes the state of the whole GUI so that you can enter numerical values for the parameters on all different tabs, and when you hit the randomizing button, it generates values for the ones you have singled out like that. Or something... somewhat close to this description

When I saw that you suggested this thing and then saw the interface, I realized that this month was a straight set up!

Hah!

It does seem it might be up my alley, doesn't it?

Well, I'm pretty much jumping into this from zero as most others here, so at least I don't have anything previously stored for this. (Come to think of it, I have never participated in an OSC where my track wasn't the first one I ever did with the chosen synth )

I'll try to cook something up, but I'm still not certain how fully I can throw myself at an OSC this month.

[TheNeverScene]

Me too. Every one of these I've had a go at was a gateway into a pretty incredible synth/developer. Started with Synth1 a while back, then the awesome OBX-d, etc. Every month is some new adventure from absolute nothingness. Everyone always amazes me with what they can pull off with minimal options. Definitely a less is more treasure trove.

[colonp]

Free-running LFO and OSC switches aren't saved in the patch files for me Ableton Live.

[EvilDragon]

Hrast fixed the consecutive GUI resize bug, fixed builds should be up sometime today when he reads the e-mail where I confirm the fix