Filterscape 1.5 RC1 revision 14837

[tasmaniandevil]

Hi all,

we're on the final stretch, the Filterscape 1.5 update is almost ready for release.

As usual, we are posting a first release candidate (RC) prior to the actual release.
We are aiming for a release in early September, if all goes well.

Please let us know should you notice anything odd or outright buggy (about Filterscape, not about the world in general).

You can grab and test the RC1 (revision 14837) right here:

Filterscape 1.5 RC1 14837 Mac
Filterscape 1.5 RC1 14837 Windows
Filterscape 1.5 RC1 14837 Linux

Windows and Linux users, please delete the factory library presets before installing the RC, as the library has undergone some more refinements since the first public preview version.

Here's an overview of the issues fixed since the first public preview, revision 14785:

* Windows: Fixed some issues with dialogs looking odd when using Windows system scaling
* Linux: Dialogs now stay in front of the plugin GUI
* CLAP: Timbre Note Expression behaviour improved
* CLAP: GUI elements sometimes didn't update on preset switch
* CLAP: menu parameters sometimes changed despite being locked
* MTS-ESP: Tuning was sometimes wrong when using the arpeggiator
* Clipper and locked parameters are no longer influenced by the randomize feature
* Fixed an audio issue when deactivating filter 2 in FSFX
* Factory presets updated once again
* User guide updated

Known Issues:

* CLAP: locking untouched but randomized parameters resets them to default value (Bitwig only)

For a complete changelog covering all changes since the last release version 1.4.1 (revision 3898), please visit the first public preview thread: viewtopic.php?p=8720994#p8720994

Cheers,
Tas

[zvenx]

Thanks Tas et al.
rsp

[Andreya_Autumn]

Great job. Thanks!

* Fixed an audio issue when deactivating filter 2 in FSFX

What was the issue if I may ask?

[tasmaniandevil]

What was the issue if I may ask?

Under some circumstances, there was a sine like tone heard, sounded like some kind of feedback, when filter 2 was switched off. It only ever happened in Reaper over here.

[Qhohi]

Thanks for all the fixes!

I wonder if its technically possible to implements antialiasing for the EQ curves sometime in the future? (2.0 maybe)?
They do look a bit pixelated when compared to something like FabFilter Pro-Q.

EDIT: Just noticed it does depend on scaling how pixelated they look.

[Urs]

The EQ curves are antialiased. Would you mind sending us a screenshot where they are not antialiased?

[Qhohi]

The EQ curves are antialiased. Would you mind sending us a screenshot where they are not antialiased?

I've send an e-mail to the support address with screenshots attached.

[Andreya_Autumn]

What was the issue if I may ask?

Under some circumstances, there was a sine like tone heard, sounded like some kind of feedback, when filter 2 was switched off. It only ever happened in Reaper over here.

Right. Do I understand correctly then, that the difference in bypassed behavior between filter 1&2 is intentional? That is, the fact that one of them throughputs dry signal when turned off, and the other outputs silence? Felt rather counterintuitive in my opinion.

[Urs]

What was the issue if I may ask?

Under some circumstances, there was a sine like tone heard, sounded like some kind of feedback, when filter 2 was switched off. It only ever happened in Reaper over here.

Right. Do I understand correctly then, that the difference in bypassed behavior between filter 1&2 is intentional? That is, the fact that one of them throughputs dry signal when turned off, and the other outputs silence? Felt rather counterintuitive in my opinion.

To be honest here, this issue did occur to us during our intensive work over the past few months. It did not occur to me when I initially developed Filterscape in 2004

We however decided to not change the behaviour as we wanted to keep Filterscape backwards compatible.

I do not know of a good way to improve consistency at the moment, but we're open for suggestions which we'd consider for future updates.

[Andreya_Autumn]

To be honest here, this issue did occur to us during our intensive work over the past few months. It did not occur to me when I initially developed Filterscape in 2004

We however decided to not change the behaviour as we wanted to keep Filterscape backwards compatible.

I do not know of a good way to improve consistency at the moment, but we're open for suggestions which we'd consider for future updates.

Right! So this isn't a new, separate plugin ID? Or is it?

In some routings, a mix dial can effectively become a volume control for filter 1 (with filter 2 bypassed), and changing that in an update could make a previously saved project/preset sound very different.

If this is the same plugin ID, then indeed backwards compatibility is key. Maybe leave it then, it's not a super big deal. If this is a new separate plugin ID (I think it is, no?), it's more about forwards compatibility if you will. If so, perhaps consider adressing before proper release, to avoid the breaking change in a future update.

If you do end up changing it, making both filters behave like filter 1 when bypassed would make most sense I think. That would be consistent with the delays behavior as well, making them all the same. If a user wants to silence the output of filter 2 this can still be achieved by keeping it on and closing the cutoff.

No idea how big a code change is required to do this, of course. And you could reasonably say it's a pretty small deal. But if it's not too hard to do it'd be good to get into the release in my perception.

Either way. Thanks again for all your work on this!

[Urs]

It is the same plug-in ID, Filterscape 1.5 is fully backwards compatible with V1.0.

[Andreya_Autumn]

Ah ok! I didn't expect so. Making it more consistent requires the breaking change then. Oh well. Not a super big deal.

[Dirkitator]

Hi, I would like to see a button to unlock the random function. No parameter is affected by the random button. Only when I unlock a parameter is it affected. I rarely want to randomise many parameters. Most of the time it's just a few.

[exmatproton]

Awesome plugins.

1 thing though; the synth and Filterscape run @ 60 to 80 fps where as the Q6 variant is running @ 15 to 30 fps..
Not sure if this is intended. Issue starts @ 130% size (and higher)

VST2, 3 (didn't try CLAP), Windows 11. All plugins @ 150% size

[tasmaniandevil]

1 thing though; the synth and Filterscape run @ 60 to 80 fps where as the Q6 variant is running @ 15 to 30 fps..

The plugins all run at the refresh rate of the display they are on. So if your display runs at 60Hz, that's what the plugins will choose.
How do you determine that Q6 runs at 15Hz on your display?