Fathom Synth Development Thread

[provoc]

provoc, yes you can do exactly what you want, you just have to be aware if which File button you hit.

There are actually two wave tables left and right side, and only one Load and Save button.

To load and save waves to and from the left side table, hit the left side File button.
To load and save waves to and from the right side table, hit the right side File button.

Saving Wave Table Waves 101

For instance, add a new Wave Table oscillator.
Hit left side Parameters button.
Set left side Wave Index to 16 and right side Wave Index to 8.
Hit left side File button and browse to Waves/User.
Click Save (left side wave number 16 is saved to Users folder).
Hit Close.
Hit right side File button.
Hit Save (right side wave number 8 is saved to Users folder).
Hit Close.
Add a Wave Draw oscillator and hit Waves.
Click on Wave 1, then click on Wave 2.
Watch the Wave Draw main graph change from Wave 1 which came from left side wave 16,
to Wave 2 which came from right side wave 8.

I have read the manual and am pretty sure this is exactly what I did in the video I posted other than saving in a different folder location. And just to be sure I just tried again saving under Waves/User and it makes no difference.

You may recall that we went through this process of tooing and froing when I reported the detune settings (FathomVoiceMap.xml) not saving correctly which you eventually tested, confirmed and fixed. So it is probably a good idea to carefully check my video just to be sure even if the end result is that I misunderstood some UI or behavioural intricacy which I will most graciously concede if this turns out to be the case

[FathomSynth]

provoc, Yes you're right.

I went back and watched your video just now and tried it myself and it is malfunctioning as you reported.

Saving the WAV file seems to be stuck on the second table.

This is easily fixed and will go into 2.13.

2.13 will be a quick release coming out shortly since I need to fix the Reaper crash as a top priority plus this problem.

Thanks for reporting it. Sorry I didn't look into it earlier when you first posted.

[BK1]

BK1, Ree, Just wanted to let you know I will be doing what ever it takes to fix this for you.

I really appreciate it! I wasn't worried, but it's always great to know that there are people out there who strive for and offer excellent customer service.

In the mean time I would recommend completely deleting the 32 bit DLL from anywhere on your system and clearing the scan on Reaper

I will try this. Will let you know later today (EST, that is).

Also, I had one customer report recently that if they uninstalled all the Visual Studio C++ redistributables and re-install 2015 and 2017 that it worked. I know that is a lot of trouble, but it has worked in the past.

I didn't uninstal because my Microsoft account won't let me download the VS C++ packages to put them back.

[provoc]

provoc, Yes you're right.

I went back and watched your video just now and tried it myself and it is malfunctioning as you reported.

Saving the WAV file seems to be stuck on the second table.

This is easily fixed and will go into 2.13.

2.13 will be a quick release coming out shortly since I need to fix the Reaper crash as a top priority plus this problem.

Thanks for reporting it. Sorry I didn't look into it earlier when you first posted.

No prob, quite understandable since it is a hectic time with the new release and many reported issues do indeed seem to be RTFM style!

[BlackWinny]

Hello Everett !

What's happening, friend ?

I sent you a question three pages ago (page 160).

viewtopic.php?p=7110448#p7110448

Then a first "bump" :
viewtopic.php?p=7111071#p7111071

Then a second "bump" :
viewtopic.php?p=7111492#p7111492


Then now it is the third "bump".

[FathomSynth]

BlackWinny,

Hi, Sorry I was not trying to ignore you. I saw your bumps but they did not have any text under them and I thought you were bumping the previous post just before the bumps.

To answer your question, upgrades cost $2.50 each (voluntary) and since my software updates sometimes come as quickly as every 2 weeks or on average once a month, the total per year would be around $30.00 which I think is too high for someone who already bought the product.

So I advise that people buy a total of $10.00 per year, which is buying 4 upgrades, and then downloading the others for free.

I'm not suggesting that people buy 4 upgrades all at once since that would be impossible, so there is no option on the page for that.

A couple people have pointed out that this entire system is perhaps a little too complex, but if you read the upgrade page carefully it's really pretty simple, you just buy an upgrade if you feel motivated to do so and if you want to see more features in Fathom.

There are 3 exceptions, (1) students who really can not be spending $2.50 on every piece of software since it can add up quickly. (2) If someone honestly thinks Fathom is fine as it is and they do not think continued full time feature development is warrented. (3) Someone who just bought the product recently and obviously should not have to pay for an upgrade until a couple months go buy and there are more features for them.

Rather than creating a techically complex system, I just made the whole thing voluntary and the only complexity is my explanation of it. The simple answer is just follow your own opinion on upgrades.

People who are as desperate as me to see Fathom gain a major position in the market along side Serum, Avenger, Omnisphere etc, are certainly free to buy every upgrade since they are usually once a month and $2.50 is still pretty cheap.

Sometime this year I will be creating an "Elite" version of Fathom which gives the user the ability to design and build their own plugin processors compiled in Visual Studio as a DLL using a provided example and Fathom will load it as an object which appears in the list. This build will also expose all the graphics images so users can completely re-skin the interface. This version will be expensive, around $125.00 and will be only for extreme users and developers. So if you are looking to make a big contribution there will be a chance later this year. You've been with Fathom I think since the very first post, so I'm thankful for your support and there are many users in this category.

Let me know if that answered your question.

[BK1]

In the mean time I would recommend completely deleting the 32 bit DLL from anywhere on your system and clearing the scan on Reaper

I tried deleting the 32 bit DLL, clearing the Reaper VST scan cache, and rescanning, but got the same result - blank black GUI for about 3 seconds then it closes Reaper completely.

[BlackWinny]

BlackWinny,

Hi, Sorry I was not trying to ignore you. I saw your bumps but they did not have any text under them and I thought you were bumping the previous post just before the bumps.

To answer your question, upgrades cost $2.50 each (voluntary) and since my software updates sometimes come as quickly as every 2 weeks or on average once a month, the total per year would be around $30.00 which I think is too high for someone who already bought the product.

So I advise that people buy a total of $10.00 per year, which is buying 4 upgrades, and then downloading the others for free.

I'm not suggesting that people buy 4 upgrades all at once since that would be impossible, so there is no option on the page for that.

A couple people have pointed out that this entire system is perhaps a little too complex, but if you read the upgrade page carefully it's really pretty simple, you just buy an upgrade if you feel motivated to do so and if you want to see more features in Fathom.

There are 3 exceptions, (1) students who really can not be spending $2.50 on every piece of software since it can add up quickly. (2) If someone honestly thinks Fathom is fine as it is and they do not think continued full time feature development is warrented. (3) Someone who just bought the product recently and obviously should not have to pay for an upgrade until a couple months go buy and there are more features for them.

Rather than creating a techically complex system, I just made the whole thing voluntary and the only complexity is my explanation of it. The simple answer is just follow your own opinion on upgrades.

People who are as desperate as me to see Fathom gain a major position in the market along side Serum, Avenger, Omnisphere etc, are certainly free to buy every upgrade since they are usually once a month and $2.50 is still pretty cheap.

Sometime this year I will be creating an "Elite" version of Fathom which gives the user the ability to design and build their own plugin processors compiled in Visual Studio as a DLL using a provided example and Fathom will load it as an object which appears in the list. This build will also expose all the graphics images so users can completely re-skin the interface. This version will be expensive, around $125.00 and will be only for extreme users and developers. So if you are looking to make a big contribution there will be a chance later this year. You've been with Fathom I think since the very first post, so I'm thankful for your support and there are many users in this category.

Let me know if that answered your question.

Hello Everett !

Yes, it answers. I simply misinterpreted the text : being very involved in two other activities currently (reasons why I couldn't take part to these new beta tests) I haven't been able to read all the exchanges in the most recent posts... and when I have read this text "If Fathom is your primary soft synth you should be contributing about $10.00 per Year or purchase 4 upgrades. If you use Fathom regularly but not as your main synth you should be contributing about $5.00 per Year or 2 upgrades." I of course interpreted it as possible options for the user to pay these $10 or $5 in advance. Simply. That's why I was very troubled because precisely it is something that I would have done: pay in advance for 2 or even 4 upgrades (and perhaps even more). And I'm bloody sure that many people may interpret (and yet have interpreted) these two sentences the same way if they don't know the existence of this current thread (not everybody is KVRian in the world), because it is the obvious sense of these two sentences.

And worse... they use the term "you should" while "you could" is probably better to express a possibility rather than a sort of constraint (I know that it's not, but grammatically...).

So I highly invite you to remove these two sentences... or even better : to turn them another way to avoid this obvious interpretation. You were someone who discover this Updates page for the first time and coming to it without having sent there by KVR but from elsewhere or you were someone coming actually from KVR but without having read this thread or all the most current posts (as it is my case) you would read these two sentences exactly as I have read them. Because it is what they say. I think especially to the users who are not at all KVRian users, a situation even worse, meaning people who don't even have the least reason to know the existence of this forum and this current thread and what is written in.

What these two sentences seem to be saying (and it is actually what they say), it is that the user may pay in advance $5 or $10 if he wants to do that way. And then... he searches and searches and searches where are these options. In vain. It would be way better to write something in the kind of "Each upgrade which contains new features costing $2.50 you may expect an expense of around $7.50/$10.00 per year if you are an intensive user wanting to upgrade each time, and you may expect an expense of around $2.50/$5.00 per year if you are just an occasional user who doesn't need or want to follow in real time each upgrade but prefers to get about one out of two for example."

It is much, much, much more clear. Don't you think so ?


Friendly!
Jacques

[FathomSynth]

I see your point. I will change the text to "a total of" so it is more clear that we are talking about a total contribution, not all at once.

However, "should" is exactly the word I intended, it is about half way between "must" and "could".

For instance, you don't have to brush your teeth every day, but you "should" brush your teeth every day. You don't have to buy Fathom upgrades, but you "should" buy Fathom upgrades,

"Could" implies there is a possibility, but no particular reason to do so, for instance the designers of Sylenth "could" give me the algorithm for their zero delay filter, but it would not be true that they "should" give me the algorithm to their zero delay filter.

[thesuzukimethod]

Everett

I think you're onto a cool model for persistent support. Kind of a mix between a tip jar and a subscription (or Patreon style) support.

I think your "use case" examples (that you've given in the thread) help explain how this works in practice, so people can see where they fit in the typology of user types. (regular, occasional, etc), and I think this also helps you sell the idea of your synth (and support) as once a potential buyer realizes there will be more updates than they are expected to pay for, it becomes more clear.

you also might find some super fans that buy every update!

[FathomSynth]

thesuzuki, hi, thanks, it's working well so far.

Actually I've been pleasantly surprised almost everyone is buying the updates. I guess since $2.50 is almost free. But it adds up quickly with all the users world wide.

My plan is to buy a dedicated Mac OSX machine and a dedicated Windows 10 machine.

[Tj Shredder]

As I am an OS X user, my advice for such a machine, get a used one which would be able to run El Capitan (10.11) and install both El Capitan and the newest whatever OS X in two partitions. I think a lot of users will stick to El Capitan as long as possible for the same reason Snow Leopard survived pretty long. Apple is good at breaking new grounds and abandoning old technologies fast, which very often breaks running systems. I always have to tell my clients "do not upgrade if your system runs smoothly!" Of course there will be a time when new toys will require an upgrade, but usually long after the initial release of the system has been debugged by the early adopters...
If Fathom runs on older and newer systems its perfect...
Install Teamviewer, and if you run into problems, I most likely can help out...

[FathomSynth]

TJ, OK, good idea. I'm going to get a cheap Mac but I would prefer a new one since I'll be using it for builds and I don't want to inherit any problems.

2.13 BETA

If anyone else had a crash problem with Reaper in Windows 10, I have placed the 2.13 beta up on the web site:
https://www.fathomsynth.com/updates

This is the first Fathom built using the latest Visual Studio 2017 so it should have all the correct code for Windows 10. In the future I will be updating all the builds to use VS 2017.

[jmg8]

Sometime this year I will be creating an "Elite" version of Fathom which gives the user the ability to design and build their own plugin processors compiled in Visual Studio as a DLL using a provided example and Fathom will load it as an object which appears in the list. This build will also expose all the graphics images so users can completely re-skin the interface. This version will be expensive, around $125.00 and will be only for extreme users and developers. So if you are looking to make a big contribution there will be a chance later this year.

So, will this be a way to make and sell my own VSTs?

[RPH]

No, to add your own DSP code to Fathom as an generator or FX component.