One Synth Challenge #109: Fathom Synth by Seaweed Audio (mmGhost wins!)

[TheNeverScene]

Yeah Generaldiomedes, I agree. My wallet flew open when I heard the detuned unison. He looks pretty active as far as working out the bugs on the Fathom forum, so hopefully it just gets better. Nice to get into the modular thing as well.

[FathomSynth]

Hello Everyone! Everett here from Fathom Synth.

Sorry, I did not check the end of this thread before to see if there were questions. I'll check it every day now during the contest.

You can report bugs here or in the Fathom thread.

fathom.png

Everyone can use the full polyphonic version of Fathom for OSC.
PM Brian or Myself to get the link.

The full version also comes with over 300 presets and 200 waveforms. You can also import single cycle WAV from libraries such as AKWF or Galbanum, and of course just draw your own.

Version 2.8.0 will be released Monday, with the following fixes:

Fixed Bug 0082 Aliasing on high notes if waveform is modulated.
Fixed Bug 0083 Low notes missing when too close together.
Fixed Bug 0085 Pitch note ADSR dropping at end of note.
Fixed Bug 0087 Aliasing occurs while moving the partials dial.
Fixed Bug 0088 Wave table oscillator inconsistant volume if skip cycle enabled.
Fixed Bug 0086 Copy components sometimes disappear.
Fixed Bug 0090 Chorus cuts in and out after note volume ADSR.
Fixed Bug 0091 Allow single cycle wav import in mono version.
Fixed Bug 0092 No warning message if attempt to save wave in mono version.
Fixed Bug 0093 Crash if load wave table with less than 16 waves.
Fixed Bug 0094 Wave table index dial manual entry is off by one.

It generally performs much better so you will definitely want the new release.

http://www.fathomsynth.com

[Tj Shredder]

Does that mean there is a difference between the osc and the payed version? (Except for the limited license) I still don't get it.

[satYatunes]

You can freeze tracks in Reaper.

hahah... yes, I am aware of that, although I prefer to render tracks... (also as Everett has pointed out, Fathom can still remain in memory in some situations).
my question is more to do with rules, if I remember correctly, we can't render tracks to use in say Mixbus for final mixing.

You are right, you cannot use any other software/DAW to process the rendered tracks further. For example, mixing and mastering. It's mentioned in the rules.
I wasn't aware that Fathom still remains in memory. In that case freezing tracks will not help reduce the load either. I believe rendering the track and bringing it back as wav file is fine as long as you don't process the wav track any further. Confirm with BJ though.

[TheNeverScene]

Ah, I see that in the rules.

I think I read a post that if you close and reopen the project after freezing, Fathom's memory is cleared.

[] Peter:H []

Again - What about "sampling"

Find attached my Wavetable with 2048 samples per slots, fathoms factory only uses 1024 per slot. 2048 samples per slot giving a total of 32Kb for all 16 slots: In my experiment I've used the sample "Thorn" of my track "Ephemeral Thorn" (check out on soundcloud), just split up and handcrafted into a fathom wavetable xml file. And you find attached an simple patch using the wavetable.

Why 2048 samples? Just do the maths yourself, it's the samples for a single cycle at 44Khz and a F# played...don't remember the exact low octave...so, you have the most original sound for the patch at some low F/F# just try on your keyboard.

Question: If nobody objects, I will use patches made this way in my submission.

[FathomSynth]

No difference between the OSC download and the Pro version. They are one and the same.

Trying to use the Mono version for the contest would be pretty restrictive,
so I thought it best that every one have access to the Pro version.

The only difference with buying it is that you get a password for all future upgrades.

If someone needs access to the alternate builds send me a PM.

[Scrubbing Monkeys]

@Toonertik, I think the rendering restriction is more geared towards one shots to cut and paste as a track in order to avoid things such as drift, etc. Rendering the track as the synth produced it and then mixing it down as a whole in some other fashion is allowed.

From past discussions, I think this is correct. That way we all had to wrestle trying to make a consistant kick for example. I dont think one shots are needed with Fathom. Maybe tha Analog saw oscillator drifts. Not sure. Everything else seems to be DCO.

[TheNeverScene]

@Toonertik, I think the rendering restriction is more geared towards one shots to cut and paste as a track in order to avoid things such as drift, etc. Rendering the track as the synth produced it and then mixing it down as a whole in some other fashion is allowed.

From past discussions, I think this is correct. That way we all had to wrestle trying to make a consistant kick for example. I dont think one shots are needed with Fathom. Maybe tha Analog saw oscillator drifts. Not sure. Everything else seems to be DCO.

I thought so too, but Toonertik and satYatunes are correct. It's in the rules towards the bottom.

[functionform]

Really need wavetable import clarification, yes or no?

Very excited for Mondays release as well.

[ontrackp]

Again - What about "sampling"

Find attached my Wavetable with 2048 samples per slots, fathoms factory only uses 1024 per slot. 2048 samples per slot giving a total of 32Kb for all 16 slots: In my experiment I've used the sample "Thorn" of my track "Ephemeral Thorn" (check out on soundcloud), just split up and handcrafted into a fathom wavetable xml file. And you find attached an simple patch using the wavetable.

Why 2048 samples? Just do the maths yourself, it's the samples for a single cycle at 44Khz and a F# played...don't remember the exact low octave...so, you have the most original sound for the patch at some low F/F# just try on your keyboard.

Question: If nobody objects, I will use patches made this way in my submission.

I don't object. If having different sound sources in wavetables floats your boat.... I say, go for it! Creativity comes from the soul, not from having more samples per slot!

[Carl_saved]

Thanks for the tips in this forum. Just installed the 64 bit version of my host, and it is SO much more stable with Fathom! (I think this is because Fathom is the most memory consuming synth I have used so far).
Also, like Peter:H I have built a custom wavetable. Curious what you guys will come up with this round
The price pool looks like they want some epic tracks made with Fathom!!

[functionform]

Edit: nvm probably should take a break. over doing it and losing my mind.

[FathomSynth]

Yeah, sorry about the memory. 16K samples per wave is a little bit insane.
Maybe I can create the settings page before the end of OSC, so wave size is settable.
Also could make using Bicubic Spline for sample interpolation instead of Linear settable.

Also, special surprise, 2.8 will include the first bank of 30 presets from "Solidtrax".
They are a pro sound design team from the Netherlands,
same guys who did some of the actual VPS Avenger factory banks.

Here's one of their presets...

[] Peter:H []

Yeah, sorry about the memory. 16K samples per wave is a little insane.
Maybe I can create the settings page before the end of OSC, so wave size is settable.
Also could make using Bicubic Spline for sample interpolation instead of Linear settable.

It is a little insane, yes, it is.
I mean if you do the maths then 2048 samples per single-cycle wav means, 44100 / 2049 cycles per second, i.e. 21,533203125 Hz...16k samples means 8 times more or 44.1 / 16 something around 3 Hz. Which midi note would that be to reproduce the single-cycle wav 1:1? I bet there is none that represents 3 Hz

What would be really helpfull is a "sample import and patch setup" function. Please check out Tone2 Icarus for that type of functions...