KVR Audio

jmg8 · Post by **jmg8** » Thu Jan 04, 2018 4:44 pm

I know I shouldn't really post bug reports here, however.......

Is anyone else getting an instant crash when moving the pattern knob past paradiddle in the random sample and hold modulator?
Happens to me every time, Its has crashed Ableton Live 10, Bitwig 2 and Reaper.

FathomSynth · Post by **FathomSynth** » Thu Jan 04, 2018 5:12 pm

My Goodness, this is Brilliant, I can start advertising on the web site as Windows Multi-Touch Compatible, and list the reasons above.

Yes, you may report bugs here, as a matter of fact I encourage it, that way other users can be made aware.

OK, I'm getting the same problem with the RSH pattern dial. That's an easy fix, and it will go into version 2.1.0 coming out this weekend. (EDIT: FIXED)

maschinelf · Post by **maschinelf** » Thu Jan 04, 2018 5:37 pm

jmg8 wrote:Yes, it works great on a touchscreen. No issues at all. And yes there is multitouch. I was able to move both the XY pads at the same time. All the knobs are big enough for it to not feel clumsy.

Excellent, thanks. I too will use it on an SP4. Going to buy now.

Scrubbing Monkeys · Post by **Scrubbing Monkeys** » Thu Jan 04, 2018 6:13 pm

jmg8 wrote:Yes, it works great on a touchscreen. No issues at all. And yes there is multitouch. I was able to move both the XY pads at the same time. All the knobs are big enough for it to not feel clumsy.

Now Im jealous.

maschinelf · Post by **maschinelf** » Thu Jan 04, 2018 7:28 pm

Yea this really enhances the workflow, especially for a modular synth as there are so many parameters and it gets cumbersome with a midi controller. Not all vsti's support multitouch, falcon does but the knobs and gui are small so it can get fiddly. Sylenth1 does too. NI and u-he plugins do not. Good to know the knobs are big enough for it not to feel clumsy, though I'm not being able to finish the download.

RPH · Post by **RPH** » Thu Jan 04, 2018 7:29 pm

Managed to crash Fathom while switching to RSH pattern "ParaDiddle".
When it happened I was playing a long note and testing the patterns available ( switching live ).
The preset holds two noise sources and two modulators.

Let me know if you need more info.

Cheers,

Rob

FathomSynth · Post by **FathomSynth** » Thu Jan 04, 2018 7:43 pm

RPH, Don't worry, the crash on that RSH Pattern dial was an easy fix, I already fixed it.
The dial index was out of range and was trying to point to a string which did not exist (for sure crash).
The fix will be in the next release this weekend which will be version 2.1.0.

Also, you might be happy to know that for 2.1.0 when you flip through modulators in the existing modulator list it will show the center envelope view, the bottom panel and preview the audio in the processor, then when you hit the OK button it keeps the selected modulator and goes back to the previous view.

So basically you now have audio and visual preview of modulators.

Also, there are 4 new modulation range types including Wagtunes "Multiply Floor", where you can use the multiply range but raise the floor value.

toonertik · Post by **toonertik** » Thu Jan 04, 2018 7:49 pm

FathomSynth wrote:
Also, there are 4 new modulation range types including Wagtunes "Multiply Floor", where you can use the multiply range but raise the floor value.

+1

RPH · Post by **RPH** » Fri Jan 05, 2018 10:38 am

Excellent, looking forward to the update.

I have some feature requests:
- Panning option for the noise source.
- When modulating some parameter, it's difficult to exactly set the range I want.
Example:
I want to modulate note offset at the noise view.
The parameter is set standard to +24, I add a e.g. sequencer and set it to something like subtract.
Say I want to have the range +24 to +12.
I then increase the amount of the modulator, the range visable on the knob i'm modulating i can see but the lower range value is unknown.
I have to guess how much i'm modulating ( red area on the knob ).
So some visual feedback on the knob when changing the modulator amount would be nice.

Fathom-exactranges.jpg

Say while setting the mod amount next to the knob value a second value in e.g. red is showing the lower range being set.
For other parameters basicly the same, like setting the LFO range for the cutoff or so.

jmg8 · Post by **jmg8** » Fri Jan 05, 2018 11:25 am

I would like to be able to text input the modulators ranges. It's a little fiddly to try and move the dial until it lands on or close to what value we want. Sometimes it is done by ear and feel, but other times we already know a specific value that we wish to modulate to/from and it would be nice to just quickly type it in.

Is this possible?

FathomSynth · Post by **FathomSynth** » Fri Jan 05, 2018 2:10 pm

RPH, jmg8, Yes, all those features could be added.

I agree, it would be very useful to have a more exact way of setting the effect modulation range of the parameter. And to show that more clearly, especially since a specific mod range of say 0.250 could have different ranges on different dials.

That will not be in the next release, but I'll try for the one after.

jmg8 · Post by **jmg8** » Fri Jan 05, 2018 2:44 pm

Lovely stuff, thanks!

FathomSynth · Post by **FathomSynth** » Fri Jan 05, 2018 5:05 pm

Folks, I need some help from my Mac Users.

There were 4 problems reported on the Mac in 2.0.
I'm new to using the Mac and these problems have not been resolved because everything
works fine for me on my Mac running OSX 10.11 and I am not able to recreate the problems.

Mac users please take a look at these issues and offer suggestions, if you have seen this before.

****************************************
AU validation fails on Logic Pro X
Reported by Danny

TESTING OPEN TIMES:
COLD:2018-01-02 12:22:05.291 auvaltool[526:d07] 12:22:05.290 ERROR:
[0x7fff72449310] >compload> AudioComponentPluginLoader.cpp:678:
ResolveFactoryFunction: CFBundle 0x7fb4fbe046f0 </Library/Audio/Plug-Ins/Components/Fathom.component>
(bundle, not loaded): cannot load bundle:
The bundle ‚Äö√Ñ√∫Fathom‚Äö√Ñ√π couldn‚Äö√Ñ√¥t be loaded.
FATAL ERROR: OpenAComponent: result: -1,0xFFFFFFFF

I use Logic Pro to test on Mac and it always validates.
Does anyone recognize this validation problem and know what is actually failing.
It says it can't load the bundle but all the previous tests pass, how is that possible?

****************************************
Fathom will not load as AUI in any host.
Reported by iU running OS X 10.9.5.

AUI will not load in any hosts, VSTI is not even seen.

Fathom is built as an AU and VST, not as "AUI" or "VSTI".
Does anyone who uses a Mac know if the reason he can't scan the plugin
is because he is trying to load an AU as an AUI?

****************************************
Loading presets fails using host Numerology on OSX 10.11.5
Reported by jue.

I can run Numerology on my Mac but I'm not having any trouble loading presets.
Everything works perfectly for me with Numerology.
Anyone else using Numerology experiencing the same problem.

****************************************
A problem was also reported with Cubase on Mac OSX.

Fathom crashed CuBase if a Fathom presets is loaded using Media Bay instead of Fathom.
I'm still trying to recreate this problem on my Mac
but the CuBase download assistant will not install.

Is anyone using CuBase on Mac able to load Fathom presets from Media Bay
instead of using the Fathom browser?

nordickvr · Post by **nordickvr** » Fri Jan 05, 2018 5:46 pm

Under OS X 10.11.6 Logic 10.3.3.

AU validation fails on Logic Pro X

No problem with validation.

Fathom will not load as AUI in any host.

I don't know about those "I" plug-in version.
Never saw/used it.

Loading presets fails using host Numerology on OSX 10.11.5

Where you taking about Fathom's own browser or Numerology's one?
Anyway, both work here.

..problem using Cubase on Mac OSX.

I don't use Cubase.

Sorry, I really would have liked being more helpful.

FathomSynth · Post by **FathomSynth** » Fri Jan 05, 2018 5:58 pm

Actually that is very helpful! Thanks!

I really want to have all the Mac issues resolved for Sunday's release of 2.1

Fathom Synth Development Thread