Fathom Synth Development Thread

[] Peter:H []

I l-o-v-e it!

Here's just two presets from a second collection I have started...
@Everett - After you got enough sleep, I would love to discuss some things.

For all new fans to Fathom, who have grabbed Fathom recently and skimmed thru the presets.
You might have come across some weird once from me in Folder: Programs\International\PeterH
For Instance the patches "kYbernetik 1" - "kYbernetik 4"...
How to use them:
1. Load all 4 together
2. Play one after the other begining with "kYbernetik 1" ending in "kYbernetik 4"
3. Play them with a rather low note, F0 or something
4. Try a bit...after a while it should spell out the word "kybernetik" (this is the german pronunciation of the english word "cybernetic")
It's just an experiment for how you can make wavetables "speak" It's a bit harder in fathom then in some other WT only synths, but as you see it's possible.
I have used these in my OSC track which you can find on the "artist" page on the Fathom web site...

[ree]

The latest version of Fathom synth seems to crash both of my hosts: Reaper 5.92 and Blue Cat Patchwork 2.2. This happens with Mono or Pro. I'm running Windows 10 x64, and I also made sure to install the Visual C++ Redist listed the manual.

Is there any way I can generate some sort of a crash log for you from the plugin?

I am having the same issue in Reaper and also in Reason.

I purchased during the sale because I could get the free mono version to run on FL Studio 20 and liked it even though it did not run in Reaper or Reason. I followed all the instructions for Windows 10 and for Reaper and FL studio interfaces and I have all the Microsoft Visual C++ distribs from 2005, 2008, 2010, 2012, 2013, 2017, both 32 an 64 bits.


In the pro version
I am running the latest versions of Windows 10, FL Studio 20, Reaper, Reason 10. I also tried in Ableton Live 9 lite.

FL Studio 20: runs fine
Ableton Live 9 Lite: runs fine
Reason 10.1 crashes when loading instrument
Reaper v5.92/x64 black screen when trying to load instrument, then freezes and crashes on own after a long time or if stuck requires reboot of computer.

I will be happy to provide additional information to the developer.

[FathomSynth]

Are you running the MD build or the MT build?

Hover your mouse over "FATHOM" in the top left corner, the MD build will say:
"VERSION 2.12.0 Pro MD 64"

The MT statically linked build will say
"VERSION 2.12.0 Pro MT 64"

If you have not tried the MT build yet please try it, that usually works for Windows 10.
I will PM you the download link now.

If not I will need to create you a new build using Visual Studio 2017.

[glokraw]

I have reaper 5.92 running in linux by way of
wine. Fathom works OK, but in one of my
setups, it failed from Program Files\VstPlugins,
but worked from

C:\Users\Public\Documents\VstPlugins\Fathom

U-he recommend this path to minimize weirdness
on the m-soft side of the moon. Pretty easy to move
the folder and do a clear-cache-rescan to test
Good luck
----------------------------------------------------------
feature request:
have the 4 versions present their unique
name to vsthosts, I have four Fathom.dlls
in Reaper plugin browser,
one mono, and your trio with work-around versions.
One of these is much faster on gui drawing,
than the others, so it might help new customers
desiring to remove the ones least suited to their situation,
if the MD, MT and mono appeared in names in the names
listed in their daw plugin browser.
I love that I discovered
the speedy one

Cheers

[FathomSynth]

OK, Good idea.

But which one is fastest and by how much?

[benheman]

Working great on Mac High Sierra!...So far!!

[benheman]

That is the Pro version.

[FathomSynth]

I would expect the HS build to be fastest for the GUI.
Some of the loops used by the GUI graphs are SIMD Vectorized in the HS build.

[glokraw]

OK, Good idea.

But which one is fastest and by how much?

In my case, it's the MT. Wine is set to report/behave
as Windows 7.

With the other builds, there is a noticeable lag
as the loading sound, and samples in some cases,
arrive in a few seconds, as compared to about 1 second,
as one would hope. (it's an i7 2600, at 3.4 ghz)

I checked, after reading another linux customers report of
slow sound loading, figuring it might be normal for
a powerful instrument with visual waveforms,
some needed linux optimizing, or both.
Cheers

[glokraw]

I loaded windows 7, and in reaper 5.92, none of the Fathom logos
show an HS version, but two show the MT.
The files do exist in the Fathom folder, and each is a different size.
The same folder is in wine, and the same reaper version,
and I do get accurate logo text for each build, HS included.
Strange goings on

Using the 'A Walk In The Park' preset from the Ambition folder
highlights the loading speed differences.

Another request, I was enjoying the instrument for quite some
time before I read that there was a logo on the gui
It's nice enough that it need not be hidden in
the shadows up there Same for the top row widgets
when they are innactive.
Cheers

[mevla]

That's an excellent synth. I use it in Linux (Linux Mint 18 KDE with Bitwig, via wine-staging and linvst). Works quite well. There are some things to improve such as CPU consumption for pads and missing VST parameters to the host, but no show stoppers at all. The EQ sliders are lacking in response when dragged but again, not that much of a big deal.

EDIT: BTW, when I say 'Linux' I also mean in comparison to all other Windows synths UI and CPU consumption running with the exact same setup. Eg. Synthmaster2, Go2, Synplant, Phonec2, Aparillo, Factory, Sytrus.

Great synth. Great sounds. Excellent UI. Kudos for the work ! May you reach success.

Cheers.

[FathomSynth]

The Fathom Friday sale is now over on the company web site and Shopify but we will be leaving the price at $11.00 for any late comers one extra day Sunday on KVR.

Friday and Saturday had the highest sale record yet since Fathom was released. Thank you to all our new Pro users and everyone who purchased the 2.12 upgrade!

Performance has been solid across all new users except two issues on Reaper and Reason. These were most likely caused by the massive new massive GUI running on 4 GB of Ram.

I will be issuing a quick release early this coming week with a memory light version for use on 32 bit systems and Windows systems with 4 GB of RAM, stay tuned here for details.

I will also be reviewing the last few pages of this thread for any issues. If your issue is not resolved quickly or you don't hear from me by Monday please email me again so I can make sure nothing is overlooked, and to make sure your fix goes into the quick 2.13 release.

[Scrubbing Monkeys]

I purchased The latest pro version yesterday and the whole process was quick and painless. I am a big fan of the original GUI, but I do like some of the new options. Everything seems stable after a few hours.


Reaper 5.91 on win 7 ( MT build.....I think????)

I played around with some of the new settings ......buffer/ interpolation/detune.....that I would expect to have cpu cycle impact. I didn't really notice change in sound or cpu. I was using a fairly simple patch that was hitting around 20% with 5 keys pressed.

Disclaimer!!!! I haven't read the new manual YET. I am going to guess I am missing a step..... like.... close gui or some other simple obvious proceedure.

All in all. A great realease.

Thanks again.

[provoc]

I seem to have found a bug related to .wav file saving. Not sure if this is new to 2.12 since I had not tried this before until I saw the "save WAV audio files" setting in the new settings screen and thought ok let’s see how this works

The problem is that after importing a folder of WAV files into a wavetable using Load All and then saving some individual waves, the *.wave.xml files save fine but the accompanying .WAV files do not match the saved wave indexes.

I recorded a screen capture so you can see exactly what I did in Windows 10 using the 64bit pro HS build of 2.12 and latest Reaper x64. At the end I dragged the saved "Single Cycle Raw.WAVs" into Reaper to confirm they are not correct (the other two variations are basically the same .. i.e. wrong wave).

http://www.users.on.net/~provoc/FathomWAVsaveBug.mp4

(NOTE: playing the above link in chrome treats it as audio only so you might need to download and view in VLC or similar although opening link in a new tab seems to work here!)

Cheers,

provoc

[BK1]

I am trying to run Fathom in Reaper 5.92 on Win10 / i5 machine with 8 Gb RAM and every time I try to put Fathom on a track it immediately shuts down Reaper.

The pre-update version seemed to work fine, and 8 Gb should be enough to run this, so I'm not sure what's going on.

Will the memory-light release next week still be full-featured?