Fathom Synth Development Thread

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
Fathom Synth$32.00Buy

Post

FathomSynth wrote:The normal pitch bend range for a hardware pitch wheel is 24 semitones or 2 octaves? Really?

Every keyboard I've ever had if you peg the pitch wheel and it goes up a half step.

I can easily change the master pitch to be 1 or 2 octaves,
but then everyone who already has their host automation of that dial set assuming it is 2 semitones,
will have their song break when they use the new release.

So it's too risky. Sorry, I wish I had known that or I could have made it 2 octaves to begin with.

EDIT: Now the master pitch bend dial range in semitones can be set per Fathom track.
The bend range has to be variable, the default should remain of course where it is. Don't change that!
The pitch bend as midi value does not define the range, it simply has a resolution of 14 bit.
A standard keyboard has a pitch wheel, you would not want to have that bending more than 2 half steps. I play an expressive controller, I move my finger across a range of up to two octaves... (comparing to any of those a keyboard is deadly boring)
But you seem to have found a solution, I am curious...

Post

In 2.10.5 you can set the master pitch bend dial range to any number of semitones you want 0 - 48.

It is remembered on that track when the project is reloaded or the preset is saved.

And it can be different on each track and different between presets.

See the user guide last section 15 Settings.

Right now it is a command line setting, but in the future I will be adding a global settings panel.

Post

Version 2.10.7 Officially Released :phew:

https://www.fathomsynth.com/updates

Post

Thank you!

I was looking for some insight into an issue I'm having mapping parameters in Bitwig. Often parameters don't show up in Bitwig's controller assignment list when I click on a parameter. I'd say most of the time. And when I find a parameter that Bitwig detects, I have to click on the name of the parameter and not on the dial. Are there reasons why so many parameters don't show up in Bitwig? I can outline what I'm doing if you'd like. Was thinking is may be a known thing?

To add, I haven't experience this before at all with any other VST. Reaktor ensembles often don't have their parameters show up either but sometimes you can correct this by sorting and compressing parameter IDs.

thanks for any info on this!

Post

kiilmaster: In order to show parameter for automation in host you have to enable it first in Fathom by cliking on name field for desired automation targed. Name will become white and parameter can be listed in daw for automation. At first it may look like useless feature but actually it is very handy because you will see only parameters you wish to automate instead of full list. Finding needed parameter is much easier this way.

Post

TrojakEW wrote:kiilmaster: In order to show parameter for automation in host you have to enable it first in Fathom by cliking on name field for desired automation targed. Name will become white and parameter can be listed in daw for automation. At first it may look like useless feature but actually it is very handy because you will see only parameters you wish to automate instead of full list. Finding needed parameter is much easier this way.
Thank you TrojakEW! I see how that works now. In Bitwig, I click the name, it goes in the list, then click the dial and it pops to the top as I would expect. Kinda like this way! Eliminates potential clutter.

Post

Yes, what he said.

I guess it's a sign of success when a user can explain something better than I can. It's true, all the audio units are dynamic so the host parameter list would be more than 64 unless there was a way to select which one's you want.

Post

FathomSynth wrote:Yes, what he said.

I guess it's a sign of success when a user can explain something better than I can. It's true, all the audio units are dynamic so the host parameter list would be more than 64 unless there was a way to select which one's you want.
Yeh, though Bitwig is really good about popping the parameter to the top of the list for easy access whenever its touched, so for me it just makes it a 2 step process, rather than just one click. I click on the name, it puts it in the list, I click on the dial (or the parameter in Bitwig's list) and it pops it to the top. Rather than, click on dial and it pops to the list and on top. :) hard to put into words... I'm happy either way.

Post

FathomSynth wrote:Version 2.10.7 Officially Released :phew:

https://www.fathomsynth.com/updates
Testing the pitch bend range setting. The way how it is described in the manual, does not seem to work, or I did not understand how it should be done.

What I did: for testing, I open for example the FM-Suspense preset. Then I go into the naming field and add set pitchrange=24 so that the name now is "FM-Suspense set pitchrange =24".
That does not change the pitch bend range! It remains where it was before.
I guess I did not understand how it was meant to be set...

Post

Tj Shredder wrote:[

What I did: for testing, I open for example the FM-Suspense preset. Then I go into the naming field and add set pitchrange=24 so that the name now is "FM-Suspense set pitchrange =24".
Don't add it to the existing name in the naming field.
Empty the naming field, then type in set pitchrange=24 so it is in the naming field by itself then hit enter.
Win10 x64, Reaper 6.XX x64, i5-3330, 8gb ram, GTX-970, UC-33, Panorama P4, Wharfedale Diamond 8.2 and JVC HA-RX700

Post

Just tried, the name stays, but the pitch bend range did not change at all... Its still as before. Both methods seem to be wrong...

Adding setting which do not need an additional UI element that way might be a smart idea, but I see also, to the right of the name field, just above the Modulation Matrix, there is an unused area where I could imagine to place a text field for exactly that purpose. This would have the advantage, that you would see, that this parameter has a new setting...

Post

At the very top click on the program name edit box.
The entire program name will be highlighted for editing.
Hit backspace or delete to (temporarily) get rid of the program name.
Type "set pitchrange=24" (without the quotes).
Make sure there is no space before or after the "=".
Hit Return.
Then the master pitch dial range will change to +/- 24.

Sorry, this is a strange way to do it, but I will be adding a real settings page soon.

Post

That is exactly what I did in the second round, but it did not change the range. Maybe its just on the Mac version notworking?

Post

Tj Shredder wrote:Just tried, the name stays, but the pitch bend range did not change at all... Its still as before. Both methods seem to be wrong...
.
Seems to work here Reaper 5.78 Windows 10.
Are you assigning the pitchwheel(or whatever you are using) to the master pitch control on the front panel?

Win10 x64, Reaper 6.XX x64, i5-3330, 8gb ram, GTX-970, UC-33, Panorama P4, Wharfedale Diamond 8.2 and JVC HA-RX700

Post

I just tried it in both PC and Mac and it works.
The range on the dial changes, remember it is only the master pitch dial, not the oscillator pitch.
When you say "not working" what exactly is happening?

Post Reply

Return to “Instruments”