KVR Audio

pekbro · Post by **pekbro** » Mon Oct 13, 2025 12:07 am

lol I never even saw that there was a version number anywhere, I just figured I had the latest version since the new features were there. This is something the dev should probably address.

*I guess it doesn't matter, long as everyone spots it.

ess_m · Post by **ess_m** » Mon Oct 13, 2025 11:56 am

It shows the version for two seconds when you open the plugin editor for the first time in a session (per instance), I could extend it to four if that helps, heh. :–)
Personally I dislike when plugins constantly shows the version number, this isn't information I need more than once.

MrJubbly · Post by **MrJubbly** » Mon Oct 13, 2025 1:22 pm

I personally prefer it when plugins always display the full version / revision and plugin format, clearly visible to the end user.

Even better when no menu diving / about screens are involved. u-he do this the best, imho. Makes it simple, fast and clear to the user exactly which variant they are using at any given moment

I get that you're going for the minimalist look, but that only works up to the point where functionality/ information is not impacted. It's even possible for a UI to become too streamlined.

For the record, I did spot the fade out at the top right corner, but it was too quick for me to notice what it was. So it's probably better to place it in a menu, if you don't want it congesting the main UI.

nanostream · Post by **nanostream** » Mon Oct 13, 2025 2:56 pm

I for one am glad that Fors software keeps the UI/UX nice and simple. Details like the version number add nothing to the product, would be an unnecessary distraction and are rarely needed anyway, imo.

MrJubbly · Post by **MrJubbly** » Mon Oct 13, 2025 4:41 pm

nanostream wrote: Mon Oct 13, 2025 2:56 pm I for one am glad that Fors software keeps the UI/UX nice and simple. Details like the version number add nothing to the product, would be an unnecessary distraction and are rarely needed anyway, imo.

Do you own any u-he products? If so, do you also find that information being displayed distracting when you use them?

It needent be anything overtly bothersome. Just easily accessible information whenever required.

krankyone · Post by **krankyone** » Mon Oct 13, 2025 4:56 pm

A basic interface design principle is to make the most used items the most visible, and bury least used items in submenus/tabs, etc. Version number is not very important. But as I posted earlier, I was trying to debug why Pivot VST3 was not being listed in Bitwig 6 browser. I tried 1.2 vs. 1.2.1 but wasn't even sure which one Bitwig was seeing. Really just an edge case. I wasted too much time on it, but I can be like a dog with a bone somtimes

nanostream · Post by **nanostream** » Mon Oct 13, 2025 5:16 pm

MrJubbly wrote: Mon Oct 13, 2025 4:41 pm Do you own any u-he products? If so, do you also find that information being displayed distracting when you use them?

It needent be anything overtly bothersome. Just easily accessible information whenever required.

No, but I honestly don’t get why Phaseplant f.e. feels it’s so incredibly important to display the version number at all times. I really don’t see any benefit. It’s just noise, and yeah, I think it’s distracting and bad design (I’ll survive though

)

We simply might have different needs or workflows. I’m fine with the precise version number tucked away in some about screen or wherever, as I very rarely need it.

MrJubbly · Post by **MrJubbly** » Mon Oct 13, 2025 6:34 pm

nanostream wrote: Mon Oct 13, 2025 5:16 pm
MrJubbly wrote: Mon Oct 13, 2025 4:41 pm No, but I honestly don’t get why Phaseplant f.e. feels it’s so incredibly important to display the version number at all times. I really don’t see any benefit. It’s just noise, and yeah, I think it’s distracting and bad design (I’ll survive though )

We simply might have different needs or workflows. I’m fine with the precise version number tucked away in some about screen or wherever, as I very rarely need it.

I suspect I update my plugins more frequently than you might. As I often run updates to the latest version for many of my plugins (I have a lot). I also very often submit bug reports for those plugins to the developers, as and when I discover them. And I beta test some software also.

So for those like myself who do this sort of thing regularly, it becomes quite significant to easily discern exactly which version(s) and format(s), the bug(s) relate to, as that is the first thing the developer will ask, if not already stated within the bug reports. i.e. When I discover a bug for a particular version and format, I will usually also test the bug again on the other available formats and previous version(s) (if available), to help the developer identify and narrow down when the bug was introduced.

pekbro · Post by **pekbro** » Mon Oct 13, 2025 7:25 pm

I think it should at least show when you want, maybe after clicking on the spot, having to reload the thing just to display the version seems a bit of a poor way of doing it.

ess_m · Post by **ess_m** » Tue Oct 14, 2025 3:55 pm

Must be doing something right when the biggest contention is the version display

But in any case, noted!

MrJubbly · Post by **MrJubbly** » Tue Oct 14, 2025 4:28 pm

ess_m wrote: Tue Oct 14, 2025 3:55 pm Must be doing something right when the biggest contention is the version display
But in any case, noted!

We're all just here to help.

nanostream · Post by **nanostream** » Tue Oct 14, 2025 6:01 pm

ess_m wrote: Tue Oct 14, 2025 3:55 pm Must be doing something right when the biggest contention is the version display

Indeed, the update is great!

I’m loving the new filters — Pivot is a capable Karplus Strong synth now, ha — and especially the MPE integration. It has replaced Glänta as my „simple“ go-to FM synth already, but now it can get even more complex at a moments notice without compromising its accessibility. Brilliant.

I hope it’s a smash hit, so we can see more Fors VST/AU/CLAP plugins in the future.

ess_m · Post by **ess_m** » Mon Oct 20, 2025 3:05 pm

nanostream wrote: Tue Oct 14, 2025 6:01 pm I hope it’s a smash hit, so we can see more Fors VST/AU/CLAP plugins in the future.

Thank you, much appreciated! All good so far.
Hoping with a few more plugin releases under our belt we can tackle larger projects without too much stress.

In other news, just updated Pivot to 1.22 – thanks for all the feedback here!

I added the much requested global/initial scale feature, you can now define the initial size from the Scale menu. Also, I removed the version pop-up and put the version number in the interface (Plus) menu instead. You can now always peek at the version, and it's never distracting – everybody wins!

noiseresearch · Post by **noiseresearch** » Mon Oct 20, 2025 3:25 pm

ess_m wrote: Mon Oct 20, 2025 3:05 pm
nanostream wrote: Tue Oct 14, 2025 6:01 pm I hope it’s a smash hit, so we can see more Fors VST/AU/CLAP plugins in the future.
Thank you, much appreciated! All good so far.
Hoping with a few more plugin releases under our belt we can tackle larger projects without too much stress.

In other news, just updated Pivot to 1.22 – thanks for all the feedback here!

I added the much requested global/initial scale feature, you can now define the initial size from the Scale menu. Also, I removed the version pop-up and put the version number in the interface (Plus) menu instead. You can now always peek at the version, and it's never distracting – everybody wins!

Bold question but any chance for a Max MSP version of Pivot? Would love to see a tight Live/Push integration. However your devices are great anyway!

ess_m · Post by **ess_m** » Mon Oct 20, 2025 3:49 pm

noiseresearch wrote: Mon Oct 20, 2025 3:25 pm Bold question but any chance for a Max MSP version of Pivot? Would love to see a tight Live/Push integration. However your devices are great anyway!

No, but I'm working on a Max for Live device that hosts Pivot and maps it to Push nicely. Won't work on Push 3 Standalone though, naturally.

FORS - Pivot (Paid & Free version)