Fathom Synth Development Thread

[Teksonik]

Can someone with an Aftertouch capable controller please check this patch to see if you get errors with AT triggering ?

AT Test 2.zip

Here's an example of what's happening here. Just a few simple notes but when I engage Aftertouch to Vibrato on a note it seems like the Vibrato or AT doesn't "shut off" or disengage. You can hear it pretty clearly in the mp3.....

https://sites.google.com/site/teksonik/ ... ects=0&d=1


I think there's a pretty good chance there is something wrong with the patch but I'm not seeing anything obvious. Just to rule out my controller I tried another VSTi and AT worked as expected.

[Frostline]

Can someone with an Aftertouch capable controller please check this patch to see if you get errors with AT triggering ?

Tried it and it seemed to work ok. MW added vibrato when engaged and vibrato stopped when MW at home position. AT worked the same, when pressed forcefully vibrato was added and vibrato ended when key pressure was relaxed.
While AT engaged and vibrato working adding MW increases vibrato effect (to almost too much really) and either relaxing pressure or returning MW home returns vibrato to normal level and then vibrato ends when both MW and AT are disengaged.
Just out of curiosity why would one want two expression controls to do the same task?
Is it for patch flexibility for users who don't have AT?

[nordickvr]

Can someone with an Aftertouch capable controller please check this patch to see if you get errors with AT triggering ?...

Seems somehow having to do with the env release?
I.g.
I made your preset having no release at all.
Played and sustain C3 with no pressure (no AT).
While sustaining C3, played C4 and add pressure (AT).
Releases C3 before C4.
When playing C3 again, vibrato still there.
Had to play C4 again adding and releasing pressure to stop the vibrato.
Same on your side?

[Teksonik]

Thanks for testing. So it's not something wrong in the patch. For the record I was using Reaper in Win 7 64 bit. I'll keep testing to see if I can figure out what's happening. I'll try it in different DAWs.

The reason I assign both MW and AT to Vibrato is so I can use both hands to play leads and trigger Vibrato with AT or I can just use my right hand to play leads and use the left to ride the Mod Wheel.

I just like my default INIT Patch to have both already enabled. I can always change or reassign them.

Another thing I like to do is assign MW to Glide on synths that allow that connection. Adds a great articulation option.

[Teksonik]

Can someone with an Aftertouch capable controller please check this patch to see if you get errors with AT triggering ?...

Seems somehow having to do with the env release?
I.g.
I made your preset having no release at all.
Played and sustain C3 with no pressure (no AT).
While sustaining C3, played C4 and add pressure (AT).
Releases C3 before C4.
When playing C3 again, vibrato still there.
Had to play C4 again adding and releasing pressure.
Same on your side?

Thanks for testing, I was wondering if the Env was somehow making a difference. It's almost like the ENV is effecting other modulators. I'll try what you mention to see how it goes.......

EDIT: Ah ah I think you're on to something. I removed the Env from the Analog Saw module and the AT "sustain" problem goes away. Somehow it seems like the ENV is causing the Vibrato to sustain. Something I'm doing wrong in the patch I'd guess. Maybe Fathomsynth can give it a look and see what's up.

On another issue sometimes when I go to delete a Modulator it deletes the whole patch....everything in the Matrix and in the Routing Grid....Oscs and all. Anyone else get this ? (Fathom 2.5)

[nordickvr]

...On another issue sometimes when I go to delete a Modulator it deletes the whole patch....everything in the Matrix and in the Routing Grid....Oscs and all. Anyone else get this ? (Fathom 2.5)

I don't know if its what you'r talking about but, I also had problem with it at first.
Taking your patch as an example, if you click the first modulator against the word "Pitch Fine" and delete it,
you'll end up deleting the Oscillator.
Must click the Wave symbol instead before deleting to actually delete the modulator.

[FathomSynth]

OK guys, sorry for they delay.

I'll start with the easy stuff, you have to expand a mod slat to delete a modulation. If you just click on a mod slat without expanding it and you have an object selected in the main view and you hit delete, Fathom will think you want to delete the object. If the object is the only object and it is deleted then it will look like you deleted the entire patch even though you just deleted the object. That's because deleting an object will of course delete all its modulations also.

When you delete something pay attention to exactly what you are going to delete in the warning message at the top.

On the other hand if you had more than one audio object in a patch and they all got deleted, that is for sure a huge horrible bug, so if that happened let me know and I will fix it.

Next, I will try to use both AT and MW on the same modulation and see if it works, and then edit the post here. You should be able to do that. Fathom does not really have a limit on how many modulations are assigned to the same dial, so it should be ok, but I'll try and see.

Next, It sounds like there is some problem in the interaction between a modulation with an Envelope or ADSR and a MIDI control parameter such as AT or MW applied to the same dial, but I could not find a specific description above. If this is the case please post the exact steps and what you are seeing and I will try to fix that.

EDIT: OK, Reporting back. I did not have any trouble with three modulations all on the same dial. First I put an ADSR on the master volume. Next I used Wave Draw with a Filter and selected the Cutoff Frequency. Then I put all three mods on the cutoff. Another ADSR, A MIDI control with 2 Breath, and another MIDI control with 1 Mod Wheel. (I don't have AT on my keyboard). Then I set all three to add. Then in Ableton I made triangles in the mod wheel, and a square wave in the breath. All three ran perfectly without interfering. The MIDI mods did not prevent Fathom from following the second ADSR contour in the cutoff including the release phase. Patch attached.

Make sure to start out with all the mods set to add. If any of them are set to multiply and the signal is zero it will cancel out all the the other mods.

[FathomSynth]

Also, people, Fathom will be starting its first real advertising banner her on KVR shortly.

I need to come up with a catchy slogan in the next day or two for the banner.

Something like ...

"Choose your Dream, Choose your Tools, Trust your Instincts."
"You're an original thinker, Use an original Synth."
"Fathom, Making Perfectionism Affordable."

etc., etc.,

Please post your ideas here.

[Distorted Horizon]

Terror from the deep

[FLWrd]

Unfathomable freedom

[FathomSynth]

Carrieres, I checked out your stuff on sound cloud "Gaz Faktory", very impressive,
especially "Keep You Out".

Is this your stuff or remixes? Amazing synth work. What synth are you using there?
Also, the girls voice is amazing, who is that?

If you end up using Fathom in any of your mixes let me know
and I will link to your sound cloud page from the company web site.

[murnau]

"Fathom, Control Your Creativity."
"Fathom, Diggin' Deeper Can Be Wonderful."
"It's Not Good, It's Fathomastic!"

[Distorted Horizon]

Btw when I play from the low keys with analog saw, I hear some extra.. Sounds like bit reduction. Is it supposed to do that? That really high crackling type of sound?

[FathomSynth]

OK, Some good ideas, keep posting them.

DH, That sounds like a bug. I would expect the problem to be in the higher keys,
when the partials get pushed over 22050 hertz. But the low keys is odd.
The analog low keys seem to be solid for me in Ableton playing manually.

I'm testing the oscillator redesign now, so now would be the time to fix this.

Could you post the patch here, and which host? and which keys? and how are you playing them?

[Distorted Horizon]

OK, Some good ideas, keep posting them.

DH, That sounds like a bug. I would expect the problem to be in the higher keys,
when the partials get pushed over 22050 hertz. But the low keys is odd.
The analog low keys seem to be solid for me in Ableton playing manually.

I'm testing the oscillator redesign now, so now would be the time to fix this.

Could you post the patch here, and which host? and which keys? and how are you playing them?

Easily redone so no need for patch, just add analog saw -> volume to 1.00. From signal flow view volume to 1.00 and velocity to 128. From A0 it's easily heard but lower you go, that whistle sound is more and more obvious. Btw I'm using studio headphones.

Bitwig

No matter how I play, it's audible. Which brings me to, it's quite difficult to try to make a psybass. Single keystroke is snappy but when the sequencer runs 145bpm, the first note from BBB is snappy and rest are a bit muddy and there's some audible crackles or pops. Not quite sure how to describe those And yes, Fathom is on mono and I set an envelope to amp to smoothen attack and release. Also that whistling sound messes a bit. It almost disappeared when I turned spectrum knob to a lower value but sound also became more dull.