Fathom Synth Development Thread
- KVRAF
- 2690 posts since 9 Jul, 2015 from UK
Just testing the new update and have a few things:
1. Still no button highlights, you mentioned they would make it into this build, oh well not a big deal at all. Maybe 2.16?
2. I am getting a lot of stuttering sound when moving the WT index (playing a note and moving control with my mouse)
I don't think it was happening with the previous version (or at least I didn't notice it)
3. The new wavetable graphs look good, but I have a few suggestions:
A. The frequency graph behind it makes it look too cluttered, is there a way to turn that off while in the wavetable graph view?
B. The back two waves have 16 lines. The front large graph has also 16 but it is twice the size, I feel it would look much better with 32 lines. It would make the graph look higher resolution and smoother and would also be fitting with the back graphs being half size and therefore half resolution.
C. And lastly (not important, just a cool idea) Have a colour picker for eack wavetable and the main table blends between them.
For example the left graph could be red and the right graph yellow. Then the large centre graph could be an iterpolated colour of the two. So when the amount parameter is at 50% the graph would be orange.
Not only would this look super cool, it would also be quite intuitive as it would give a very visual way of seeing the morph position between the two waves.
1. Still no button highlights, you mentioned they would make it into this build, oh well not a big deal at all. Maybe 2.16?
2. I am getting a lot of stuttering sound when moving the WT index (playing a note and moving control with my mouse)
I don't think it was happening with the previous version (or at least I didn't notice it)
3. The new wavetable graphs look good, but I have a few suggestions:
A. The frequency graph behind it makes it look too cluttered, is there a way to turn that off while in the wavetable graph view?
B. The back two waves have 16 lines. The front large graph has also 16 but it is twice the size, I feel it would look much better with 32 lines. It would make the graph look higher resolution and smoother and would also be fitting with the back graphs being half size and therefore half resolution.
C. And lastly (not important, just a cool idea) Have a colour picker for eack wavetable and the main table blends between them.
For example the left graph could be red and the right graph yellow. Then the large centre graph could be an iterpolated colour of the two. So when the amount parameter is at 50% the graph would be orange.
Not only would this look super cool, it would also be quite intuitive as it would give a very visual way of seeing the morph position between the two waves.
Jason @ Melda Production
-
- Patchmeister
- 1929 posts since 3 Nov, 2010
This!jmg8 wrote: C. And lastly (not important, just a cool idea) Have a colour picker for eack wavetable and the main table blends between them.
For example the left graph could be red and the right graph yellow. Then the large centre graph could be an iterpolated colour of the two. So when the amount parameter is at 50% the graph would be orange.
Not only would this look super cool, it would also be quite intuitive as it would give a very visual way of seeing the morph position between the two waves.
It's definitely not important but would be VERY Cool!
CHOOSX Remakes on my Youtube Channel
-
- KVRAF
- 2270 posts since 30 Aug, 2004 from Lancaster, UK
Hey, what a great idea!CHOOS wrote:This!jmg8 wrote: C. And lastly (not important, just a cool idea) Have a colour picker for eack wavetable and the main table blends between them.
For example the left graph could be red and the right graph yellow. Then the large centre graph could be an iterpolated colour of the two. So when the amount parameter is at 50% the graph would be orange.
Not only would this look super cool, it would also be quite intuitive as it would give a very visual way of seeing the morph position between the two waves.
It's definitely not important but would be VERY Cool!
Thu Oct 01, 2020 1:15 pm Passing Bye wrote:
"look at SparkySpark's post 4 posts up, let that sink in for a moment"
Go MuLab!
"look at SparkySpark's post 4 posts up, let that sink in for a moment"
Go MuLab!
-
- KVRAF
- Topic Starter
- 1584 posts since 25 Mar, 2017
OK, I'll do it if you send me a case if this ...
You do not have the required permissions to view the files attached to this post.
- KVRAF
- 5544 posts since 26 Apr, 2007 from Noosphere
So the synth is becoming a monster synth. GOOD WORK! Btw, is it possible to make a 2d GUI for the knobs and other things (not the wavatable representation) I'm sure this would give more punch. Just bought it, a bargain. Thank you.
-
- KVRAF
- Topic Starter
- 1584 posts since 25 Mar, 2017
OK, it's time to reveal a secret, and please do not spread this outside this thread.
Fathom's GUI is data driven, meaning you can change the entire interface including all the images without recompiling the DLL.
So at some point I am going to make a Fathom "Elite" version which exposes the technology and mechanism for doing it, then people will be able to re-skin the entire interface to their own liking and even sell their own Fathom skins.
But I warn you, it is going to be expensive, since I'm not going to give away something like this for free.
Also, I'm playing around with the idea of kicking this off with a massive skinning contest similar to BJ's OSC contest, except for UI skinning. It will probably be in 2019 when I have more time from critical feature development, and the first prize is going to be something very serious and significant like a real Moog Voyager. The contest will be world wide, and attract the world's best skinners (people like satYatunes).
But it is just an idea at this point.
Also, be aware that with 2.15 you can save and load all your GUI background selections and colors.
If some of you have already created your own Fathom color schemes you can save them and post the here!
So post your colors below ...
Fathom's GUI is data driven, meaning you can change the entire interface including all the images without recompiling the DLL.
So at some point I am going to make a Fathom "Elite" version which exposes the technology and mechanism for doing it, then people will be able to re-skin the entire interface to their own liking and even sell their own Fathom skins.
But I warn you, it is going to be expensive, since I'm not going to give away something like this for free.
Also, I'm playing around with the idea of kicking this off with a massive skinning contest similar to BJ's OSC contest, except for UI skinning. It will probably be in 2019 when I have more time from critical feature development, and the first prize is going to be something very serious and significant like a real Moog Voyager. The contest will be world wide, and attract the world's best skinners (people like satYatunes).
But it is just an idea at this point.
Also, be aware that with 2.15 you can save and load all your GUI background selections and colors.
If some of you have already created your own Fathom color schemes you can save them and post the here!
-
alexdelosreyes alexdelosreyes https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=186316
- KVRist
- 59 posts since 3 Aug, 2008 from Spain
Fathom is awesome!!! thank you for create it!! Im using it in every song ive made in the last weeks. Lovely synth sound!
with love.
alex.
with love.
alex.
-
- KVRAF
- Topic Starter
- 1584 posts since 25 Mar, 2017
Alex,
Thanks so much! That is great to hear.
Thanks so much! That is great to hear.
-
- KVRer
- 11 posts since 22 May, 2018
Hi Everett,
A clean installation of Fathom (64 bits) seem to crash my FL Studio (64 bits) when browsing to some of the included presets. I'm on Windows 10 (64 bits). Let me know if there is anything I can do to help troubleshot this issue.

A clean installation of Fathom (64 bits) seem to crash my FL Studio (64 bits) when browsing to some of the included presets. I'm on Windows 10 (64 bits). Let me know if there is anything I can do to help troubleshot this issue.

-
- KVRAF
- Topic Starter
- 1584 posts since 25 Mar, 2017
zzz, thanks!
Ikalou, thanks for reporting the issue, I will test it and fix it for 2.16.
But, sorry, I'm not seeing a crash in the video above, what am I missing?
Some of the presets take a long time to load, is that the issue?
Ikalou, thanks for reporting the issue, I will test it and fix it for 2.16.
But, sorry, I'm not seeing a crash in the video above, what am I missing?
Some of the presets take a long time to load, is that the issue?
-
- KVRist
- 73 posts since 23 Jun, 2013 from Seattle, WA
I'm getting similar crashes with preset browsing in Renoise. Windows 10 x64.
The crash happens when switching presets- a new preset is selected (from the browser in my case), and the vst hangs, never moves on to the "loading samples" stage, and crashes the DAW.
I'm also getting the audio stuttering mentioned above while moving knobs. The sound playback will pause briefly until I stop editing values.
Otherwise, I'm liking the workflow for setting up modular patches.
The crash happens when switching presets- a new preset is selected (from the browser in my case), and the vst hangs, never moves on to the "loading samples" stage, and crashes the DAW.
I'm also getting the audio stuttering mentioned above while moving knobs. The sound playback will pause briefly until I stop editing values.
Otherwise, I'm liking the workflow for setting up modular patches.
- KVRAF
- 1685 posts since 3 Aug, 2017 from San Diego, CA
Everett,
I have another bug to report.
Last night I was using the new version in Blue Cat's Patchwork host. Free-resizing the GUI while playing notes on my MIDI controller, the plugin crashed and subsequently crashed Patchwork as well (as is typical in that host). I've been able to reproduce this a couple of times, haven't used in Reaper yet.
I have another bug to report.
Last night I was using the new version in Blue Cat's Patchwork host. Free-resizing the GUI while playing notes on my MIDI controller, the plugin crashed and subsequently crashed Patchwork as well (as is typical in that host). I've been able to reproduce this a couple of times, haven't used in Reaper yet.
-
- KVRAF
- Topic Starter
- 1584 posts since 25 Mar, 2017
OK, I just fixed the preset loading crash, I will issue 2.16 tomorrow.
Tappistry, I'm not getting a crash when I play during resize, can you export the preset and post it here or PM it to me.
Even if it crashes with a lot of presets during resize, just pick the one it happens with most and send it.
Tappistry, I'm not getting a crash when I play during resize, can you export the preset and post it here or PM it to me.
Even if it crashes with a lot of presets during resize, just pick the one it happens with most and send it.
- KVRAF
- 1685 posts since 3 Aug, 2017 from San Diego, CA
So do you mean export an error log or just copy the preset name?FathomSynth wrote:OK, I just fixed the preset loading crash, I will issue 2.16 tomorrow.
Tappistry, I'm not getting a crash when I play during resize, can you export the preset and post it here or PM it to me.
Even if it crashes with a lot of presets during resize, just pick the one it happens with most and send it.
