Filterscape 1.5.0 public preview 14785

[tasmaniandevil]

Ok so I tried both the VST3 and CLAP. Seems the VST3 does not respond to per note anything, right?

As mentioned in the first post of the thread, note expressions have been implemented in CLAP!
We don't have note expression support in VST2 and VST3.

... and then modulated notes with Bitwig's timbre expression. But while this did not move the filter knob, it also was not per note, the filter modulation effected all notes playing at the same time. Is this expected?

It's not supposed to move the parameter on the plugin's GUI when using note expressions.

But you are right, something seems wrong when using the Timbre note expression.
We'll look into it next week.

[D Halgren]

I've been trying to get per note modulation of the VA filter using timbre in Bitwig, and not been successful. Using the CLAP version, which defaults to MPE, MIDI channel set to same, I have tried both the Expression modulator from Bitwig and Modulator A set to CC74. Neither seems to work. I have also tried turning MPE off and setting the channel to 1. Per note pitch is working fine. Am I misunderstanding something?

Have you set CTRL A as a modulation source to any target in FilterscapeVA?

The Timbre Note Expression in Bitwig (which actually maps to CLAP's Note Expression called "Brightness") does not do anything in our software by default, unlike Pitch, Pan or Volume. Instead, it is works as if the MIDI CC assigned to CTRL A (as set in our MIDI Preferences) was sent. Unike the MIDI CC though it is evaluated per Note.

In short: You might need to assign CTRL A to modulated Cutoff or something in FilterscapeVA.

Yes, I set CTRL A to CC74 and modulated the filter cutoff with it. It was not per note.

[D Halgren]

I've been trying to get per note modulation of the VA filter using timbre in Bitwig, and not been successful. Using the CLAP version, which defaults to MPE, MIDI channel set to same, I have tried both the Expression modulator from Bitwig and Modulator A set to CC74. Neither seems to work. I have also tried turning MPE off and setting the channel to 1. Per note pitch is working fine. Am I misunderstanding something?

Have you set CTRL A as a modulation source to any target in FilterscapeVA?

The Timbre Note Expression in Bitwig (which actually maps to CLAP's Note Expression called "Brightness") does not do anything in our software by default, unlike Pitch, Pan or Volume. Instead, it is works as if the MIDI CC assigned to CTRL A (as set in our MIDI Preferences) was sent. Unike the MIDI CC though it is evaluated per Note.

In short: You might need to assign CTRL A to modulated Cutoff or something in FilterscapeVA.

Yes, I set CTRL A to CC74 and modulated the filter cutoff with it. It was not per note.

I also tried it with pressure. Same results, no per note modulation.

[Echoes in the Attic]

Ok so I tried both the VST3 and CLAP. Seems the VST3 does not respond to per note anything, right?

As mentioned in the first post of the thread, note expressions have been implemented in CLAP!
We don't have note expression support in VST2 and VST3.

... and then modulated notes with Bitwig's timbre expression. But while this did not move the filter knob, it also was not per note, the filter modulation effected all notes playing at the same time. Is this expected?

It's not supposed to move the parameter on the plugin's GUI when using note expressions.

But you are right, something seems wrong when using the Timbre note expression.
We'll look into it next week.

Yes you indicated under the clap section that note expressions were implemented instead of CLAP per note modulations but not say it was CLAP only. And given that note expressions are used in vst3 and you did not have a vst3 section, it was a fair confirmation. But thanks for confirming.

And I know it's not supposed to move the slider, that was an indication of expected behavior, but the actual results were more like it was just globally automated.

[krans]

About your existing licenses:

The license system of Filterscape has been updated.
This means whenever you start Filterscape, it will display a reminder that the license needs to get updated.
For the moment, simply click that message away. Your existing license will continue to function.
Once the Filterscape update is officially released, you will be able to request a new license through the My Licences form on the website.
There is no need to try this now, as it will only send you your old license.

In order to avoid upgrade issues and to get the presets right, I deleted my old Filterscape before installing v1.5.
Unfortunately this gives me the Demo/License popup window everytime I launch the plugin. But entering my license doesn't work, I'm not able to register it, so I get the demo noise even though I have a license.
Is there a way to fix this without reinstaling the old version?

[Hanz Meyzer]

Oh very nice!

[pdxindy]

Couple more sounds from F-VA

https://dandelionaudio.com/sound/F-VA-32.mp3
https://dandelionaudio.com/sound/F-VA-39.mp3

[Matnids]

I’m very interested in Filterscape, looks amazing, and was wondering if the price will change when the new version is officially out or if there will be some kind of introprice?

[anttimaatteri]

damn. where can i preorder^^
im obsessed
no, i correct
i am POSSESSED

//and just in that moment my live11 crashed with a shutdown^^

[pdxindy]

damn. where can i preorder^^

Just buy Filterscape... this update, whenever officially released, is free for all existing Filterscape owners.

[tasmaniandevil]

Unfortunately this gives me the Demo/License popup window everytime I launch the plugin. But entering my license doesn't work, I'm not able to register it, so I get the demo noise even though I have a license.
Is there a way to fix this without reinstaling the old version?

Old licenses will still work, it might be a typo or some other glitch.
Please contact our support so we can help you with this.

https://u-he.com/support/#contact

[Hanz Meyzer]

I have some suggestions regarding the FilterscapeVA:

- Maybe the EQ Q-factor could be changed with the two fingers scroll gesture using an magic trackpad (so scrollwheel I guess)? It's a bit annoying to press a modifier only to change the Q, IMHO. If this does not work great with a steppy scrollwheel, this could be optional.

- The scroll gesture on a slider could do fine movements instead, not simply the same movement. For example 0.25 stepping.

- The ringmod maximum volume seems to be way too loud, maybe it should sound as loud as the other oscs? Or is this intended for a specific purpose?

- Maybe the pitch range could be extended from -48 to 48 for sync mode? Or at least some base pitch parameter per OSC?

- I kind of miss stereo stuff on OSC level, OSC panning, or unison. Urs said in that interview that the filter path is full stereo, but I guess this is a mono structure, correct? Was thinking about setting an eq band to L or R only, or having panning per band and such stuff Anyway, it is great already without stereo.

- What about importing wavetables from Zebra?

[pdxindy]

I have some suggestions regarding the FilterscapeVA:

- Maybe the EQ Q-factor could be changed with the two fingers scroll gesture using an magic trackpad (so scrollwheel I guess)?

Scrollwheel and two finger trackpad scrolling both work here...

[pdxindy]

- The ringmod maximum volume seems to be way too loud, maybe it should sound as loud as the other oscs? Or is this intended for a specific purpose?

Not every Osc combo ends up loud so I'm glad for the extra level.

[Hanz Meyzer]

I have some suggestions regarding the FilterscapeVA:

- Maybe the EQ Q-factor could be changed with the two fingers scroll gesture using an magic trackpad (so scrollwheel I guess)?

Scrollwheel and two finger trackpad scrolling both work here...

What exactly works over there? When you move the pointer over a eq band handle and then use 2 finger scroll wheel gesture on your mac, it changes the Q factor? What system exactly do you have?

Here on my M1pro monterey 12.6.1, it neither works on the internal trackpad nor the external bluetooth magic trackpad. But of course scrolling pages works elsewhere normally.