KVR Audio

XeonKnight · Post by **XeonKnight** » Tue Feb 06, 2018 9:13 pm

Guenon wrote:"Level" is the actual oscillator level (and "Sample Level" is the level of sample playback if you have a sample loaded). Balance 1-2 and 3-4 set the balance between filters 1 and 2, and between filters 3 and 4 (how much of the signal is being routed from a particular osc to corresponding filters). Note that filters have their own "Level" parameter, so if you are routing a signal from the oscillator(s) to more than filter number 1, make sure you don't have the other filters set to zero level.

Awesome Guenon, thanks for the brilliant explanation!

XeonKnight · Post by **XeonKnight** » Tue Feb 06, 2018 9:14 pm

schiing wrote:
Lempface wrote:I'm having trouble with the OSC mixer. I don't understand the "Level" "Sample Level" and "Balance 1-2", but I can still get a blend of OSC 1 and 2. I haven't been able to get anything sound out of OSC 3 and 4 though, what am I missing and how do the level and balance work?
Ahem, I made a visual representation as Guenon explained. Might as well post it - adjust this slider, and you'll get the sound for OSC 3+4...

Untitled 11.jpg

Thanks for taking the time!

XeonKnight · Post by **XeonKnight** » Tue Feb 06, 2018 9:20 pm

wagtunes wrote:
Lempface wrote:I'm having trouble with the OSC mixer. I don't understand the "Level" "Sample Level" and "Balance 1-2", but I can still get a blend of OSC 1 and 2. I haven't been able to get anything sound out of OSC 3 and 4 though, what am I missing and how do the level and balance work?
By default, the filters for OSC 2-4 are off so you won't get any sound for those oscillators unless you turn the filter levels up. The exception is if you move the balance of osc 2 to the center, in which case it will partially run through filter 1 which is open by default.

The sample level controls the volume of the sample if you use a sample.

Level controls the volume of the regular oscillator wave.

Balance 1-2 and 3-4 controls how much of each oscillator goes through each filter.

Y'all quick to the draw, but thank you wag.

mostlyjustj · Post by **mostlyjustj** » Wed Feb 07, 2018 5:04 am

kokotte wrote:Some snare, could be good with some post proc and a synth :

Thanks so much kokotte for these....your Snare2 sound has boosted the sound of the arrangement I've got going on here

functionform · Post by **functionform** » Wed Feb 07, 2018 7:40 am

Can someone explain the envelopes? I don't understand why this configuration produces the envelope I expect. Basically, Env4 is functioning as I gate, ok. Env2 is modulating is modulation Osc 4 level, but I don't even have Attack configuered? Not sure I get the concept of stages here. Doesn't seem like a typical ADSR envelope to me.

toonertik · Post by **toonertik** » Wed Feb 07, 2018 8:43 am

functionform wrote:Can someone explain the envelopes? I don't understand why this configuration produces the envelope I expect. Basically, Env4 is functioning as I gate, ok. Env2 is modulating is modulation Osc 4 level, but I don't even have Attack configuered? Not sure I get the concept of stages here. Doesn't seem like a typical ADSR envelope to me.

Yes, a bit confusing at first, though I did discover one could make the Env do a rise and fall.. a kinda looping...
Then Evil Dragon brought some explanation a few pages back (which I copied for reference... Here is E_D's comment
Diodow envs>> by Evil Dragon.

Regarding the envelopes, by default (if you start from Init patch) they are already set up as ADSR, so all you need to touch is: Time0 (Attack), Time1 (Decay), Level1 (Sustain) and Time4 (Release).

Adjusting the curvature: next to the looping dropdown menus (0-4), first one is for attack stage, second one is for decay stage, last one is for release stage.

Regarding the looping: The first stage (Time/Level0) is already accounted for, so setting Stage0 [A] as the first looping stage will get you exactly that: initial attack stage will finish and loop back to Level0 (which is the same level it has arrived to from the initial attack stage!) at Time0, which means you basically get a sustain level until you release the key. This is why Stage1 [D] is there - so it goes to Level1 at Time1 when envelope arrived to Level0. Then Stage2 [2] is there twice to basically create our sustain loop. Note if you change Level2, you will basically get a rising/falling sustain (performed at Time2) like in u-he synths.

This arrangement will produce an infinite loop... in the looping section.
0>> Stage0(A)
1>> Stage1(D)
2>> Stage3
3>> Stage2(S)
4>> Stage3
The only way OUT I have found is to change 2>> Stage3 to Stop/End, still exploring the possibilities! ... mad but fun>>

EvilDragon · Post by **EvilDragon** » Wed Feb 07, 2018 8:47 am

Yes. That section (slots 0-4) are for looping the envelope, not for configuring which stages will play and which won't.

toonertik · Post by **toonertik** » Wed Feb 07, 2018 9:08 am

Hi E_D...
any suggestions as how to break_out of the above "loop" ..
what I am trying to achieve is a rhythmic loop while key_held and stops on key_release?
BTW... loading Single_cycle wavs into the sample_Player and looping turns that section into a kinda oscillator..
both this and the monster big_brother are really quite amazing synths for the sound_designer...

I just kick my ass for not downloading Diodow when I saw it ages ago... must have been the gui that put me off.... silly mistake>>>
now I have the colours tamed and no lime_green all good...

So thankx for all the help you have provided on this and the monster... yet to tame that beasty

EvilDragon · Post by **EvilDragon** » Wed Feb 07, 2018 9:32 am

Hey what's with all the underlines?

Unfortunately in Diodow you cannot tempo-sync envelopes, but you can loop them however you want. You would just go through the segments in order then loop back to the segment you want to loop from. Here's an example, try applying it to filter cutoff:

schiing · Post by **schiing** » Wed Feb 07, 2018 9:48 am

schiing wrote:Emboldened by my relative success, I'm now attempting a flex-a-tone, of all things.

Well, that wasn't so hard.

Ladies and gentlemen (are there ever ladies in this forum?) - care for some flex-a-tone? Just because I think every song with respect for itself should have at least one flex-a-tone hit. Best served in the C3-G-3 area with heavy mod wheeling.

http://terjefjelde.com/music/TF-Flexatone.hp

Volume might be a bit low - I always end up mixing at a ridiculously low levels.

And, now, for the vibraslap!

Taron · Post by **Taron** » Wed Feb 07, 2018 11:23 am

Oh, man, so many posts... I hope, I don't warm up "old news" with this one:
- After loading back a song into MULAB, the last presets also overwrites the previous preset, making the last two the same. Very annoying!
- Reading the Manual brought up one big revelation: Create a Diodow.ini file in the same folder as the DLL and write into it:
[Editor]
Automation=1

After that you activate automation. Why he made it an option is truly weird to me, but there it is! And it works fabulously in MuLab, including automating the FixedFrq for Sync!!!

EvilDragon · Post by **EvilDragon** » Wed Feb 07, 2018 11:38 am

Taron wrote:- After loading back a song into MULAB, the last presets also overwrites the previous preset, making the last two the same. Very annoying!

Can you explain this in a bit more detail? I noticed no such thing in Reaper.

BTW be careful with automation, it is known to crash depending on which parameters get automated. Save often! Automation is an option because the developer himself is not using it at all - just uses MIDI CCs.

zarf · Post by **zarf** » Wed Feb 07, 2018 11:49 am

Taron wrote:Oh, man, so many posts... I hope, I don't warm up "old news" with this one:
- After loading back a song into MULAB, the last presets also overwrites the previous preset, making the last two the same. Very annoying!

Did you see Guenon's post on page 7

Guenon wrote:Hah, yepp. Again to recap, for anyone tuning in, the most important thing: in every individual instance of the synth, save the patch using a unique filename. Do this instead of having a bunch of "init" patches while you're editing -- or having otherwise identically named patches, in duplicated synth instances for example.

As long as you keep the names unique right off the bat, and save your changed patches (i.e. when ever you change a patch and wish to keep the changed version, save it as such), you're golden.

Remembering this, I haven't encountered any mixed patches or parameter weirdness all day at this end (using Live). Still keeping backups of a couple of generations of the patches, though, to be sure . After getting used to that archaic type of patch handling, and using in-plugin MIDI CC assignments for parameter control, it's pretty much about exploring this thing and its character.

Taron · Post by **Taron** » Wed Feb 07, 2018 11:52 am

Yeah, I finally read through the whole developer page. I'm a little distracted still- for some reason. Funny times.

AAHHh, uhhh, ehhh.... that's really shitty... it doesn't save Host internal FXPs??? Instead it secretly saves files? That would be pretty aweful indeed.

That may explain the last patch overwriting the last instance's patch. Pffff.... ok. Nice to be forced to finally save my patches, I guess, haha...

ckoe · Post by **ckoe** » Wed Feb 07, 2018 12:11 pm

This month I pause. This synth is to strange for me.

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