Fathom Synth Development Thread

[AmbieticA]

@AmbientivA, thanks for posting. This looks and sounds great. I like the idea of synth programming as composition. I look forward to exploring more of your programs.

I like the idea of synth programming as composition also. Probably why Fathom is so attractive to me.

Would be cool to beam it through a projector
to the wall seen from the keyboard players location
Or beam it on a ceiling at a party as a random arp
played Fathom's greatest hits
Nice audio/video, AmbieticA!

Thanks guys, I've actually never thought of it as "synth programming as composition", but your right. What a concept! I actually thought of it as "wouldn't it be great if I can combine all of the necessary sonic elements for a cinematic scene within one sound". But I guess that's the same thing now that I think about it

And glokraw wow, I just pictured being in a planetarium like structure watching wavetables morph through space in the dome above. That would be so super cool!

[FathomSynth]

ADSR release phase should never click, please post the preset and I will debug.

Edited modulators always stay in the list after you save and load a preset, as long as you edited something and as long as you don't delete them, I just tried it myself to make sure. If they are gone then you must have deleted them accidentally somehow.

[RPH]

It's the decay stage, not release stage, that's causing the clicks. You have the preset because it's the one you helped me with the filter report I made. The ADSR was only inserted, not changed in any way.
To be sure I'll make a new preset and insert an ADSR to check if it's not something else. I'll let you know later today.

The only thing I do is save the preset, close the DAW. A few days later start my DAW, load up Fathom and the preset and check the edited modulators.
I have no reason to delete the edited modulators. My impression is Fathom "forgets" there were edited modulators from the last time it was used.

[FathomSynth]

Post the preset anyway, I don't think I saved the old one and also it was not clicking for me.

Are the edited modulators being deleted the one's in the list on the left or the right.

The left is the edited modulators catagory in the audio units window and the ones on the right are listed in the matrix when a modulation slat is expanded. Which ones are being forgotten? Also, is the edited modulators or the file modulators.

That's weird I just tested it and when I save a preset, delete Fathom, and load the preset, the edited modulators are there. I will try it again just using the host.

I'm almost certain this works because often my sound designers hand in presets where the edited unused modulators have not been deleted and I have to go in and delete them. Strange.

OK, I just loaded up my Ableton and opened Fathom to recreate your problem and I have a full list of edited modulators in both lists.

Maybe you better make a video of what you are talking about, I've never seen edited modulators get deleted between sessions and I use Fathom constantly for the demos.

fathom edited modulators.jpg

[RPH]

Post the preset anyway, I don't think I saved the old one and also it was not clicking for me.

Think i'm going crazy, today the clicks are gone in the preset. ADSR seems fine now..really weird.
Maybe it somehow initialized wrong?

Are the edited modulators being deleted the one's in the list on the left or the right.

The edited modulators are gone on the left side. I uploaded the preset for you.
http://rhmodules.nl/temp/sineorgan.zip

When I create a new preset, save it, close the DAW and reopen it, load up Fathom the new preset it seems to be fine.
I do see the edited modulator on the left side.

I'll keep an eye out for this stuff, when it happens again I'll create a video.

[SoundPorn]

Clicks could be ur host buffer?

[RPH]

Maybe, am using Renoise DAW with buffersize set to 512 (11.6 ms ).
Asio driver from Behringer U-PHORIA UMC404HD audio-interface.

[glokraw]

I'm assuming an envelope/filter related click would happen
almost every time the audio of a consistant frequency passed through it.
System performance clicks are responding to all
the crap that runs at startup, or when it feels like it,
and the moshpit of system services are doing who-knows-what
and who-knows-when which is why some people
use stripped down systems or totally separate computer systems
where relatively few processes can interrupt the daw and it's audio.

I think BlackViper still have detailed guides
on safely controlling the background activities that generate
noisy interruptions. Sweetwater also have something,
less detailed, but more to the musicians mindset, maybe
other guides out there as well.

If I had a dollar for every time my neck crackled and popped
while editing audio, (wild-goose-chase )
I'd be in the Marketplace forum, instead of here

[AmbieticA]

Clicks could be ur host buffer?

Exactly what my problem was before I adjusted. I sent a preset to support, and he said "not happening here". So I troubleshot. I used an alternate method of loading Fathom. SAVIHost - Standalone Vsti Host instead of Reaper. It uses way less resources than any DAW. (for those who've never tried it: http://www.hermannseib.com/english/savihost.htm ). And all of the "snap, crackle, pops" vanished. So I ended up tweeking the craziness out of Reaper, and BAM, problem solved. As for disappearing modulators. That's never happened to me. I am also starting to exclusively name the edited modulators so I can actually find what I'm looking for later.

[BBFG#]

Been using Savi-host for years, but just got an email for this from Tone 2:
https://www.tone2.com/nanohost.html

Just changed my desktop uses to it and it does seem to be an improvement. Plugins are booting faster and the program changes are quicker in it too.

[AmbieticA]

Been using Savi-host for years, but just got an email for this from Tone 2:
https://www.tone2.com/nanohost.html

Just changed my desktop uses to it and it does seem to be an improvement. Plugins are booting faster and the program changes are quicker in it too.

Oh man this works even better! I just tried it. Nanohost is so accurate that both the Fathom and Nanohost CPU usage was spot on. It also seems to use even less resources than Savi-host, so far. Thanks for sharing that BBFG#!

[RPH]

I tried nanohost as well, works great indeed.
Normally I use Renoise because then I can use my computer keyboard to have an easy way to play some notes while designing.
For nanohost I have to grab a MIDI keyboard, but maybe (while thinking about it) I can use a virtual keyboard application and send the MIDI info to nanohost.

[glokraw]

Been using Savi-host for years, but just got an email for this from Tone 2:
https://www.tone2.com/nanohost.html

Thanks for sharing the link. Already used and productive!
A standalone Fathom with a recorder is great for using
with the UNO hardware arpeggiator.
Thanks Tone2 for the free quality software!
Cheers

[zzz00m]

NI Komplete Kontrol is now a free plugin host, that runs as a standalone app, or as a plugin itself. It also does not require a dedicated NI controller. https://www.native-instruments.com/en/p ... e-kontrol/

It's available as part of the free Komplete Start bundle.
https://www.native-instruments.com/en/p ... ete-start/

I tried Fathom in standalone KK instead of my DAW, and noticed reduced resource usage.

Another plus is that you can add FX plugins to the signal chain following an instrument, so KK works great as a standalone instrument + effects host.

And the Fathom UI resize controls/commands work well within the KK host, at least on my computer.

Map any Fathom synth parameters to a MIDI controller. In KK, there are initially only some generic controls "Prmt0, Prmtr1, Prmtr2, etc." shown for Fathom. If those are connected to some automation parameters in the synth, by clicking on the name of a dial or toggle in Fathom, then they are exposed to the host, and updated in the KK plugin control panel view. So then it is possible to use the MIDI learn in KK to assign your MIDI controller CC's to them.

[perpetual3]

Hey all,

I just purchased the 2.31 update and I can’t get the zip file to decompress: MAC OS 10.14.2, MBP13 2.9i7 2012.

Anybody else see this?