Fathom Synth Development Thread

[tonedef71]

Cannot get reaper to register the 2.8 64-bit versions - standard or Win10 builds. 32-bit OK. The MT build will load though. So, something again in the c++ redists is causing issues somewhere ...

I have these redists ...

2017 (x64)
2015 (x64)
2015 (x86)
2013 (x64)
2013 (x86)
2010 (x64)
2008 (x64)
2008 (x86)
2005 (x64) ver 8.0.61000
2005 (x64) ver 8.0.50727.42 *
2005 ver 8.0.61000
2005 ver 8.0.50727.42 *

I'll get rid of the older 2005 versions (*) and see if that helps - nope, no dice.

db

I wonder if we need to additionally have all of the x86 versions of these libraries installed alongside of the x64 versions. Perhaps there is some interaction with a 32-bit process that is dependent on the 32-bit version of a Microsoft Visual C++ library.

[Frostline]

I have these redists ...

I don't see 2012 in your list.
That was the one that was keeping Fathom MD x64 and Windows 10 versions of 2.71 from working for me. Adding 2012 and they worked.
When 2.8 came out the main dll loaded just fine without any issue for me.

[progtronic]

Progtronic, I was not planning on adding a Legato glide mode. But I am planning (soon) on adding a new bar to all tlhe envelopes in addition to the note off bar, which will be “The Glide Start Bar”. This will give you the ability to have a slow attack when you start a fresh new note that is not touched by a preceeding note, but when you play a glide adjacent note the envelope starts at the glide start bar wherever you want so the slow attack is not repeated. This will get rid of the “Thwaaaaap” in the middle of your smooth melodies!

Really not the same thing.. but I'll take it.

A true Monophonic mode would add the ability to patch particular styles of sounds.. like 303 emulation and a lot vintage mono synth stuff, in general.

While you're under the hood, adding envelope functionality.. consider adding modulation access to various ADSR elements as well. So, that individual modulation assignments can be patched to things like attack rate, decay peak level and rate, sustain level.. and release rate.

These are just a few features I'm used to having access to, with almost all the synth vst's I've used.. and it really feels incomplete, when I can't tweak something that I feel is very basic.

Anyway, I realize your plate is totally full regarding all this stuff.. you're doing an awesome job updating and keeping up with the community in general. Hope you consider some of these kinds of additions in the future though.

[doctorbob]

@Frostline - I've added the 2012 redist and yes, it all now works (standard and win10 versions) ... thanks.

What a tangled web ms weaves ...

dB

[Frostline]

Probably not bugs, but issues that maybe could be improved.

[provoc]

Provoc, No sorry, I did not fix the save default detune problem for 2.8. I was not able to make it happen on my system. If I hit save default it saves it OK here.

Sorry to ask, but could you post the steps again here, to make it happen, and your OS and DAW.

Looks like I can't link to a specific post here but my last post on page 107 of this thread has the screen cap video showing the steps to reproduce in Reaper/Windows 10x64 (you might need to right click the link and open in new tab to get it to play).

Cheers,

provoc

[FathomSynth]

So what is the definitive list of VS C++ Redist that need to be preset for everything to validate in Windows 10?

I want to update the manual.

I've sort of been keeping track but it looks like some of you may know for sure from testing it.

[tonedef71]

So what is the definitive list of VS C++ Redist that need to be preset for everything to validate in Windows 10?

I want to update the manual.

I've sort of been keeping track but it looks like some of you may know for sure from testing it.

It looks like it might be the 64-bit builds for versions 2012 (VC++ 11.0.xxxxx) and 2017 (VC++ 14.10.xxxxx) .

[Frostline]

So what is the definitive list of VS C++ Redist that need to be preset for everything to validate in Windows 10?

For me it was
More than what tonedef71 listed but less than drBob.
I'm running Win 10 Home. Maybe Win10 Pro is different?
Willing to delete some to test if you like.

Also, can confirm provoc's saving detune default issue.

[provoc]

Also, can confirm provoc's saving detune default issue.

Thanks for the confirmation, glad it is not just me!

[tonedef71]

For me it was

Interesting. Your 2017 runtime is build version 14.12.xxxxx; mine is build version 14.10.xxxxx. Apparently, the latest build version of a VC++ runtime is not necessary to get the Fathom plugin up and running, but I wonder if there are various nuances between the different versions of the runtime that manifest themselves as different behaviors which are only reproducible by folks using the exact same build versions.

[FathomSynth]

Yes, the provoc detune default issue is a bug, it's happening for me also.
I'll fix this for the next release.

[surreal]

I have these redists ...

I don't see 2012 in your list.
That was the one that was keeping Fathom MD x64 and Windows 10 versions of 2.71 from working for me. Adding 2012 and they worked.
When 2.8 came out the main dll loaded just fine without any issue for me.

Where can we get these redistribute versions?

[doctorbob]

Hi

2012

https://www.microsoft.com/en-gb/downloa ... x?id=30679

General list

https://support.microsoft.com/en-gb/hel ... -downloads

HTH

dB

[FathomSynth]

I have a couple questions myself about the VS C++ redist's.

It sounds like only the 2012 and 2017 are really necessary in Windows 10.

What about the 2015? Did that one end up not being a factor?

Also, is 2017 necessary for Windows 7 or just the 2012?