KVR Audio

subterfuge · Post by **subterfuge** » Fri Feb 02, 2018 7:23 pm

I'm on windows 10, but yes, I do have the Fathom.xml in c:\Users\xxx\AppData\Roaming\FathomSynth\Fathom.xml

Here's the data from that file:

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>

<Config>
  <Path>
    <ProgramRoot>D:\Sounds and Samples\Seaweed Audio\Programs</ProgramRoot>
    <Program>D:\Sounds and Samples\Seaweed Audio\Programs\subterfuge</Program>
    <WaveRoot>D:\Sounds and Samples\Seaweed Audio\Programs</WaveRoot>
    <Wave>D:\Sounds and Samples\Seaweed Audio\Programs\User</Wave>
  </Path>
  <Settings GuiSizePixlesPerUnit="16"/>
</Config>

---
edit: That was the hint, it seems every time I open the first instance of FathomSynth, the GuiSizePixlesPerUnit line gets set up as "32" in this xml file. If I change the GUI to eg. small (which I usually use), I do get the smaller GUI and the GuiSizePixlesPerUnit will get changed to "24".

However, when I open another instance, FathomSynth seems to rewrite the size as "32" again. Trying to edit this number even while FathomSynth or the host are not running doesn't help. It will get changed back to "32" when the FathomSynth is opened the next time.

Also, when I have resized FathomSynth once, either typing the size to the title bar or by dragging, I cannot do it again by typing into the title bar, I'll have to drag the corner of the GUI.

FathomSynth · Post by **FathomSynth** » Sat Feb 03, 2018 12:37 am

Subterfuge, OK, I'll run it myself and see if I can get to the bottom of this.

One more thing, this could be important also.
Fathom use to keep Fathom.xml in the same folder as the plugin DLL file Fathom.dll.
Can you check and make sure that this old Fathom.xml is not also there.
If so, delete it, since it should only use the app data version.

OK, I just debug stepped through all the code that sets the size and it is all working perfectly. It is reading the size from the file. And My file location is the same as yours.

I wonder if the host is setting the window size.
Check for a host setting related to this.
Also check if the old Fathom.xml is present in the DLL folder.

Also remind me what host you are using?

subterfuge · Post by **subterfuge** » Sat Feb 03, 2018 2:19 pm

Thanks for studying this further. I'm using Reaper v5.70/x64 on Windows 10 Home x64 system.

There was indeed an older xml file right along the FathomSynth DLL in my VST folder. It seems the last time that file was written over was before the latest FathomSynth versions where the xml was placed into the Users roaming folder. Anyway, removing that file didn't solve the default GUI size issue totally. There is one change in that now I can type the size into the title bar and/or drag the GUI in any order and both ways work all the time.

In Reaper Preferences, Plug-ins, I have "Automatically resize FX windows" set to "up". Only difference when removing that selection or selecting "down" is that the FX window will only show a tiny corner section of the plugin GUI since the window doesn't automatically resize to show the big GUI.

I have to wonder if there really is any solution to this unless something else is changed within FathomSynth? I mean, there seems to be no specific way to set a default value for the GUI? It seems that the new instances of FathomSynth always want to open at medium size (GuiSizePixlesPerUnit="32") and that size will get written to the xml, regardless of what size was there before.

If I already had another FathomSynth instance at small size (GuiSizePixlesPerUnit="24") in Reaper, that specific instance will keep its size, so that will not change. But there is no way to set small as a default size for new instances because whenever a new FathomSynth instance is opened, regardless of what was in the xml file, that will get written over with the medium size setting.

Being able to adjust the GUI size freely is great and all the separate instances do keep their individual sizes like they were set to. But always writing the last adjustment value to the xml file seems to have no effect with the new instances, they will always open at medium size and the xml file will get overwritten to reflect that. On the other hand, if any FathomSynth instance is resized to something else than what I'd like to have as a default, I wouldn't even want the new instance to read the latest value in xml file. That's because resizing would have updated the xml to something else than my preferred default anyway.

teilo · Post by **teilo** » Sat Feb 03, 2018 6:17 pm

I just upgraded to 2.5.0 on Mac. The file browser is now stuck in an empty folder named "Resources" and there is no way to get out of it. The navigation bar on top is missing. I can't access any presets or wave tables.

-------

Not sure what happened here, but I manually edited /Library/Application Support/FathomSynth/Fathom.xml and changed the path. The browser bar came back. I then deleted the file and reloaded Fathom to see what happens when it creates its settings from scratch, and it was still working fine, and properly saved my Program and Waves paths back to Fathom.xml.

I guess it was a fluke.

FathomSynth · Post by **FathomSynth** » Sat Feb 03, 2018 9:50 pm

Teilo, OK, Good News, thanks so much for working on it on your side!

Just a couple questions for my debug records:
What was the last version you used before 2.5?

Be aware the Navigation bar in the left side file window was removed
and moved to the top title bar, and the folder back button moved to the top left.

Also, be aware you can cut and paste your desired browser folder directly into the top path edit box.
That will change the root folder and Fathom will then remember it forever.

Subterfuge, Good News for you also, I'm able to recreate your problem with Reaper.
This will make it a a lot easier to fix, I'll keep you posted.

FathomSynth · Post by **FathomSynth** » Sun Feb 04, 2018 12:04 am

Subterfuge, I found the problem and fixed it.

I sent you a PM with a direct download link for the fix.

The fix will also be in version 2.6 for everyone using Reaper.

Also I would recommend going into Reaper, Options, Preferences.
Select Plug-ins. At the top next to "Automatically resize FX windows.
Check both up and down.

teilo · Post by **teilo** » Sun Feb 04, 2018 1:02 am

FathomSynth wrote:Just a couple questions for my debug records:
What was the last version you used before 2.5?

Be aware the Navigation bar in the left side file window was removed
and moved to the top title bar, and the folder back button moved to the top left.

I was on 2.4 before. This was the VST, in Bitwig 2.4 beta 2. I wish I had taken a screenshot. But the file browser panel was flush with the top and left of the Fathom window, with no navigation on either the top or the side. The entire title bar was missing while in the browser.

subterfuge · Post by **subterfuge** » Sun Feb 04, 2018 10:09 pm

FathomSynth wrote:Subterfuge, I found the problem and fixed it.
I sent you a PM with a direct download link for the fix.
The fix will also be in version 2.6 for everyone using Reaper.

Wow, great, thank you Everett! On a quick test here, this works now! Whatever size I try, that size is used by every instance and keeps, even after restart...until the next resizing, of course. Thanks again, very nice work there.

Scrubbing Monkeys · Post by **Scrubbing Monkeys** » Mon Feb 05, 2018 4:56 pm

I just uploaded a video showing how to create a split.

I will be doing part two for this soon which will show some different uses of the keyboard tracking modulator.

RPH · Post by **RPH** » Mon Feb 05, 2018 6:57 pm

Nice video, keyboard tracking is indeed powerful.
Another easy way to split at the correct point is to copy the keytracking modulator, then do the opposite.

The keyboard tracking modulator lacks a range indication, when I tried it had to check my host to see which octaves I was actually manipulating.
@Everett: could you add that at some point?

Scrubbing Monkeys · Post by **Scrubbing Monkeys** » Tue Feb 06, 2018 10:11 am

RPH wrote:Nice video, keyboard tracking is indeed powerful.
Another easy way to split at the correct point is to copy the keytracking modulator, then do the opposite.

Thats a good use of the mod copy feature. Thanks

FathomSynth · Post by **FathomSynth** » Tue Feb 06, 2018 12:44 pm

SM, Another great video. You really make it look easy in this one, great job.
I updated the web site tutorial page to include all your recent tutorial videos.
https://www.fathomsynth.com/tutorials/

RPH, yes, that's a good idea, I added it to the feature list.

Scrubbing Monkeys · Post by **Scrubbing Monkeys** » Tue Feb 06, 2018 7:01 pm

FathomSynth wrote:SM, Another great video. You really make it look easy in this one, great job.
I updated the web site tutorial page to include all your recent tutorial videos.
https://www.fathomsynth.com/tutorials/

RPH, yes, that's a good idea, I added it to the feature list.

Glad you enjoyed it.

it would have been easier if I had I thought about that mod copy feature. I also just recently fiqured out how to do screen capture and voice over simultaineously without latency. So maybe the videos can become a little more fluid. If I can stay out of my own way.

FathomSynth · Post by **FathomSynth** » Thu Feb 08, 2018 5:43 pm

Yeah, that last video looked really smooth. 720 resolution looks great.

At some point it would be great to have a video on how to make your own waveforms, covering the various segment options, exponential, bezier and sin wave, since that is one of the features not very many synths have. We could call it "How to create your own Analog Waveforms" since you can use the sin wave accelerator to mimic voltage ring. But just an idea, "hehe"

The next release will fix the CPU problem when the partials go too high.

Scrubbing Monkeys · Post by **Scrubbing Monkeys** » Thu Feb 08, 2018 6:18 pm

FathomSynth wrote:Yeah, that last video looked really smooth. 720 resolution looks great.

At some point it would be great to have a video on how to make your own waveforms, covering the various segment options, exponential, bezier and sin wave, since that is one of the features not very many synths have. We could call it "How to create your own Analog Waveforms" since you can use the sin wave accelerator to mimic voltage ring. But just an idea, "hehe"

The next release will fix the CPU problem when the partials go too high.

I can do that.

I have two more in the works now. I will make it number three.

Funny, I thought the quality was just as good as the previous which were also 720. This one was only 15mb where as the others were 200 mb or so. I know they were longer but thats a big difference.

This time I rendered from Reaper and converted in VLC. Before I was using Shotcut to convert Similar settings though.

Honestly, I must have NO idea what I am doing when it comes to video rendering. Hell, the original render from Reaper on a 10 min video is almost 3 gig sometimes. I have tried and continue to try and figure it out. I must be getting closer, because a 5 min video that looks halfway decent at 15 mb is very doable for my internet bandwidth.

Fathom Synth Development Thread