KVR Audio

DJErmac · Post by **DJErmac** » Mon May 01, 2017 9:27 pm

BlackWinny wrote:
DJErmac wrote:
kokotte wrote: try the mouse wheel for easy snap value
Thanks, made possible to reach that damn 4.000 !!!

But it's still completely impossible to reach 4.001 on the Frequency from the AM/FM, then 4.002, and so on. I know it's not a major problem, but I find it very frustrating to have values that nobody can reach on a button. And now, I'm very curious to hear what those values sound like : I'm sure they sound awesome !
You're right, it's frustrating, especially to try to reach the perfect sound using the FM modulations.

My problem is that I've found some kind of sweet spot to create some effect I'm after, and was constantly moving away from it everytime I changed the value. So the only thing I could get was : ONE taste of a sweet spot, and no way to see if there was some way to make it sound better or not...

goleat · Post by **goleat** » Mon May 01, 2017 9:31 pm

BlackWinny wrote: When you use 12 instances of the mono Fathom, yes, I have noticed that.

But it's a hassle to map each instance on the keyboard before playing...

I mean sometimes when working with a single instance of Fathom, the synthesizer becomes polyphonic. A fairly nice bug, I suppose it should be the same inconvenience (but in reverse), where users with the polyphonic version of Fathom, sometimes can only play a single note at a time.

FathomSynth · Post by **FathomSynth** » Tue May 02, 2017 3:04 am

Sorry guys, I've been coding all day and lost track of time.
I'll do another read through here tomorrow and list the status of all feature requests.
Most of the stuff above is do-able.

I'm not sure why you are having trouble getting AM Frequency to exactly 4.000.
On that dial the mouse wheel increments by +/- 0.025.
So it will go 3.975, 4.000, 4.025, etc ...
And single clicking will go by 0.001.
Dragging the mouse goes by the smaller increment in this case 0.001,
but you can't predict where dragging will fall in granularity.
You can always drag it close and then click, click, click to the value.
If you don't have a wheel on your mouse, I'm sorry but you really need one.
Each dial is perfectly tuned and that has been solid for over two years.
I've never had a problem with this on any host with any dial,
all the dials use the exact same code.
What host are you using?
If something is different in your host that really does prevent you from hitting 4.000 exactly,
then that is a bug and I will fix it.

Sorry about the FL Studio problem.
If FL studio does sample blocks that are either too small or too large, I can't control that.
I did not have any problem with the massberg frequency dial with those FL settings I tried.
It was super smooth.
Also keep in mind, if it stutters a bit while you are moving the dial just for edits,
this will in no way effect how it sounds when the track is playing or
the dial is modulated.

Clicking on a mod slat will jump to the component panel that holds that dial,
so you can always see what modulates what if any of the names are the same.
If you want the mod slat to change color when you click on the dial that is
the target of that modulation, then that is actually a really good idea,
and I think probably very easy to do.

More details tomorrow.

RPH · Post by **RPH** » Tue May 02, 2017 6:40 am

FathomSynth wrote: I'm not sure why you are having trouble getting AM Frequency to exactly 4.000.
On that dial the mouse wheel increments by +/- 0.025.
So it will go 3.975, 4.000, 4.025, etc ...
And single clicking will go by 0.001.

Yea, that works fine in both Flstudio and Renoise.

FathomSynth wrote: Sorry about the FL Studio problem.
If FL studio does sample blocks that are either too small or too large, I can't control that.
I did not have any problem with the massberg frequency dial with those FL settings I tried.
It was super smooth.
Also keep in mind, if it stutters a bit while you are moving the dial just for edits,
this will in no way effect how it sounds when the track is playing or
the dial is modulated.

No problem, it's just FLstudio acting weird.
Massberg is smooth indeed after changing the settings, and lowering the ASIO buffer length in FLstudio helped with the response while tweaking.

Again, in Renoise all is working great with an even lower ASIO bufferlength ( 256 samples ).

kingtubby · Post by **kingtubby** » Tue May 02, 2017 3:42 pm

FathomSynth wrote: Good news everyone, I found the cause of the start up in monophonic mode bug. The “is poly flag” was initialized after loading the voices, rookie bug. Which is why it happened sometimes and sometimes not. That will be fixed in the next release.

I was one of the people who reported that bug - maybe the only one? - Anyway, just letting you know that it works correctly now

BlackWinny · Post by **BlackWinny** » Tue May 02, 2017 9:29 pm

Everest (Everett, sorry)... is great!

FathomSynth · Post by **FathomSynth** » Tue May 02, 2017 9:35 pm

OK, Thanks! I haven't forgotten about you all, just heavy coding today.
I'll post an update this week on feature request status.
Mostly 1.0.4 will be Wave Morph, but also some fixes.

bungle · Post by **bungle** » Wed May 03, 2017 12:19 pm

Hi Fathomsynth, thinking of getting in on this to show support, I only buy cross platform synths though (my mobile set up is Mac) mac is definitely in its future at some point right ?

FathomSynth · Post by **FathomSynth** » Wed May 03, 2017 4:57 pm

Yes Fathom is coming out for Mac OSX (AU).
Maybe sooner than expected.
I can build AU for Mac now, I just need to run some tests.

I may start asking for some Mac Beta testers soon.
Maybe two week time frame.

Fleer · Post by **Fleer** » Sun May 07, 2017 3:40 am

I'm in for that Mac beta.

FathomSynth · Post by **FathomSynth** » Sun May 07, 2017 6:29 am

OK I will try to get you an advance copy as soon as I can.

FathomSynth · Post by **FathomSynth** » Sun May 07, 2017 9:04 pm

Wave table morph development is going well and will be released in a few days.
Keep in mind it's very deep feature and will require some more testing.

I need a few volunteers for some cutting edge alpha release testing bugs and all.
If you already have a purchase code respond here or the support email for instructions.

Here's a brief preview of what it can do so far.

nordickvr · Post by **nordickvr** » Sun May 07, 2017 10:03 pm

Could you count me in as beta tester too?
Really interested into this project!

RPH · Post by **RPH** » Mon May 08, 2017 8:51 am

FathomSynth wrote: I need a few volunteers for some cutting edge alpha release testing bugs and all.
If you already have a purchase code respond here or the support email for instructions.

Here's a brief preview of what it can do so far.

It sounds really good, excellent stuff.

What do you want tested specifically?
If the alpha release can work next to the current version, i'm sure I can do some testing for you.
Don't want to mess up the presets I made.

FathomSynth · Post by **FathomSynth** » Mon May 08, 2017 1:32 pm

Ok, So "alpha wolves" here's the scoop.
This is the deepest feature I've added in a while so there's a lot of new code.
So I want a few brave testers to bang on it even before a beta release.

No, it will not interfere with your presets, everything is always backwards compatible.
I don't need any specific tests, just use the feature as you would normally for morphing.

The worst that can happen is it will crash your host, so save your work often,
then just report the bugs to me. And thanks to alpha testers help here.
So many ppl have asked for this feature I want to make sure it is solid before the release
and also that I can get it out as quickly as possible as promised.

I'll post info here tomorrow 5/9/17 for the alpha and how to download the alpha.

Fathom Synth Development Thread