OK, 2.13.2 is out.
This fixes the Reaper crash in Windows 10.
Go to the upgrades page:
https://www.fathomsynth.com/updates
Under "Windows 10 VS 2017" and download 2.13.2.
Please report back if it fixes your Reaper crash.
I will wait to make the full 2.14 release until I hear back from you.
Fathom Synth Development Thread
-
- KVRAF
- Topic Starter
- 1584 posts since 25 Mar, 2017
-
- KVRAF
- 11162 posts since 16 Mar, 2003 from Porto - Portugal
It did, but I'm in Windows 7. I will try in Windows 10 and will let you know.FathomSynth wrote: Tappestry, Fmr, I think you said 2.13 Beta fixed the crash for you.
There is also two outstanding bugs from direct email: Studio One (Dan), Cakewalk (Kevin).
EDIT: Tested in Windows 10, with REAPER 5.90. Everything worked like a charm. I used the latest Beta build (2.13.2).
What I did:
1. Used the folder from the 2.12 update Full (have no older files in there).
2. Use JUST ONE DLL. In this case, I used the one named Fathom.dll
I loaded the instrument in a new project file and played directly in real time, changing presets, for a while. No problems
Since this is the same machine where I experienced the crashes with version 2.12 (in Windows 7, solved with the use of the MT version, and now gone with this new version) I guess whatever was conflicting with Fathom and REAPER is now solved.
Fernando (FMR)
-
- KVRAF
- Topic Starter
- 1584 posts since 25 Mar, 2017
OK, Good news, looks like it is fixed.
The bug was a race condition in Fathom's GUI memory handler. Reaper does a strange thing where it tells the plugin to open the GUI, then it quickly deletes the GUI and creates it again. Fathom had a bug where it sent a message to the processor to destroy all gui memory, if the Hold GUI toggle was disabled, and by the time the processor destroyed the pointer to the gui the next gui Editor was using a deallocated pointer, and bang, crash. Anyway, it's fixed now.
The bug was a race condition in Fathom's GUI memory handler. Reaper does a strange thing where it tells the plugin to open the GUI, then it quickly deletes the GUI and creates it again. Fathom had a bug where it sent a message to the processor to destroy all gui memory, if the Hold GUI toggle was disabled, and by the time the processor destroyed the pointer to the gui the next gui Editor was using a deallocated pointer, and bang, crash. Anyway, it's fixed now.
-
- KVRian
- 1134 posts since 22 Aug, 2004 from Edge City, the Low Country
Hi Everett. Z. here ..
I am very happy to report that, after changing the 'HoldGUI' value, the original FathomSynth Pro 2.12.0 MD 32 (32 bit) is working fine with VSTHost, Mulab and Reaper!
Also, no performance problems on my old computer (dual core)
Before that it was crashing all mentioned hosts, DAW's ..
So, thank you for the solution!
-
- KVRAF
- Topic Starter
- 1584 posts since 25 Mar, 2017
Ree, Zee, Thanks for reporting back. Good news.
This is interesting, new virtual analog demo song by Scrubbing Monkeys.https://www.fathomsynth.com/home/#/listen/
Check it out, he used the virtual analog filters and modulated the saw tooth using the wave table oscillator to simulate random analog voltage jitter. It a pretty cool song. See if you can tell which track is the Moog and which is Diva (just kidding all the tracks are Fathom).
Also "Fathom Friday" is on for tomorrow.-
- KVRAF
- Topic Starter
- 1584 posts since 25 Mar, 2017
No, that is not fixed.
Please make a recording and send it to me.
Include your system specs, which OS, Windows 32/64, Windows 7/10, Mac OSX?
When exactly does it drop out audio, what were you doing?
Only when you move dials, or all the time.
How many tracks of Fathom push it to that point, one, or many?
What does the CPU meter at top say when it happens?
If it happens on a particular preset tell me the preset.
If it happens on your edits save the preset and send it.
Thanks for reporting this, but I will need this info to solve the problem.
Sorry for all the questions, but audio drop outs are serious and I normally fix those problems as a first priority. We have a lot of FL users and no one has reported any issues in the last few releases (unless of course you posted before and I missed it). So please send the info so we can make sure everything is clean for all FL users. Be aware also that if the reason is you have 37 tracks of Fathom each with 8 oscillators running on a 32 bit machine with a 1.9 GHz processor then of course there won't be much I can do.
Also FL uses small block sizes which will cause distorted audio unless you change the plugin block setting on FL. And there is a section in the manual for FL users.
Please make a recording and send it to me.
Include your system specs, which OS, Windows 32/64, Windows 7/10, Mac OSX?
When exactly does it drop out audio, what were you doing?
Only when you move dials, or all the time.
How many tracks of Fathom push it to that point, one, or many?
What does the CPU meter at top say when it happens?
If it happens on a particular preset tell me the preset.
If it happens on your edits save the preset and send it.
Thanks for reporting this, but I will need this info to solve the problem.
Sorry for all the questions, but audio drop outs are serious and I normally fix those problems as a first priority. We have a lot of FL users and no one has reported any issues in the last few releases (unless of course you posted before and I missed it). So please send the info so we can make sure everything is clean for all FL users. Be aware also that if the reason is you have 37 tracks of Fathom each with 8 oscillators running on a 32 bit machine with a 1.9 GHz processor then of course there won't be much I can do.
Also FL uses small block sizes which will cause distorted audio unless you change the plugin block setting on FL. And there is a section in the manual for FL users.
-
- KVRAF
- 6078 posts since 27 Jul, 2001 from Tarpon Springs, Florida, USA
I bought Fathom on 1-2018.
I opened it and on the upper left it states Version 2.3.0 when I hover on "Fathom"
Tried to find where to click to update and to find the Fathom license and other pertinent info but was not successful.
Do I have Fathom Pro?
What am I overlooking?
BTW the multi-touch seems to work just fine.
I opened it and on the upper left it states Version 2.3.0 when I hover on "Fathom"
Tried to find where to click to update and to find the Fathom license and other pertinent info but was not successful.
Do I have Fathom Pro?
What am I overlooking?
BTW the multi-touch seems to work just fine.
My Studio: viewtopic.php?f=4&t=7760&p=7777146#p7777146
-
- KVRAF
- Topic Starter
- 1584 posts since 25 Mar, 2017
You can always get the latest software upgrade here:
https://www.fathomsynth.com/updates
But I would wait a couple hours, I'm just about to release 2.14 which has some important fixes.
https://www.fathomsynth.com/updates
But I would wait a couple hours, I'm just about to release 2.14 which has some important fixes.
-
- KVRist
- 462 posts since 2 Jun, 2015 from Belgrade, Serbia
I like the idea of this synth - a lot!
But I just can't get it to work in REAPER (tried everything I could think of), so it's a show stopper for now.
But I just can't get it to work in REAPER (tried everything I could think of), so it's a show stopper for now.
-
- KVRAF
- 6078 posts since 27 Jul, 2001 from Tarpon Springs, Florida, USA
How did I end up with Fathom 2.3.0?FathomSynth wrote:You can always get the latest software upgrade here:
https://www.fathomsynth.com/updates
But I would wait a couple hours, I'm just about to release 2.14 which has some important fixes.
Is this the Fathom Pro?
Where do I find the Fathom Credits, the update button and license info?
Clicking on the "Fathom button does not give any info.
When I hove on "Fathom" i get Version 2.3.0
My Studio: viewtopic.php?f=4&t=7760&p=7777146#p7777146
-
- KVRAF
- Topic Starter
- 1584 posts since 25 Mar, 2017
Ghost Dog, I have to agree, not working in Reaper is a show stopper for me also.
I'm building 2.14 now, it will be out in a couple hours, and fixes the Reaper crash.
The download page has the fix in 2.13.2 under "Windows 10 VS 2017" 2.13.2 BETA.
https://www.fathomsynth.com/updates
Use that until I get the full version out.
Also, is it crashing for you, or just not scanning?
Kalamata Kid, You have a very old version from earlier this year, but yes it was Pro, otherwise it would say Mono.
You can always get the latest software upgrades here:
https://www.fathomsynth.com/updates
But wait a couple hours because 2.14 is just about to be released.
Sorry, the Fathom interface is not fancy enough to tell you that you need updates or where to get them,
all my time is put into the audio engine. You should check the upgrades page every couple weeks to check for upgrades,
since I release them very regularly.
I'm building 2.14 now, it will be out in a couple hours, and fixes the Reaper crash.
The download page has the fix in 2.13.2 under "Windows 10 VS 2017" 2.13.2 BETA.
https://www.fathomsynth.com/updates
Use that until I get the full version out.
Also, is it crashing for you, or just not scanning?
Kalamata Kid, You have a very old version from earlier this year, but yes it was Pro, otherwise it would say Mono.
You can always get the latest software upgrades here:
https://www.fathomsynth.com/updates
But wait a couple hours because 2.14 is just about to be released.
Sorry, the Fathom interface is not fancy enough to tell you that you need updates or where to get them,
all my time is put into the audio engine. You should check the upgrades page every couple weeks to check for upgrades,
since I release them very regularly.
-
- KVRist
- 462 posts since 2 Jun, 2015 from Belgrade, Serbia
No, no, you're the dev, you don't have the privilege to give up on it!FathomSynth wrote:Ghost Dog, I have to agree, not working in Reaper is a show stopper for me also ....
The zip file has a password?!FathomSynth wrote:.... The download page has the fix in 2.13.2 under "Windows 10 VS 2017" 2.13.2 BETA.
https://www.fathomsynth.com/updates
Use that until I get the full version out ....