@David-Healey Well so an SDK downgrade would be the best thing to test, at least to see if the process is the good one

@Lindon I guess you meant 2.8.0...

Can your mac support a more recent OS?

Can you try downgrading the SDK?

@dannytaurus Oh nice one!

@resonant Thanks! Yes that was one of the ideas with extended parameter ranges compared to original Pultec.
One of the most interesting modulation is the envelope, which is nice when you want to tame the loudest parts or on the contrary to make them crunchier.

@Lindon Perhaps because I filtered with the search bar...

Yup this xcode project:

@ustk I've built both architectures:

@Lindon Perhaps a version compatibility issue, I'm running 2.6.1 without any issue.

@Chazrox Claude can self install/link with hise. It analyses the REST API and the CLI structure of Hise and can pul git, install, link, test, until ready for running...
That being said, it's always better to understand what it does...

The new one is finally here :)

https://www.studio427audio.com/product-rust-eq-le-bleu-vst-plugin/

@dannytaurus Yeah for all those DSP stuff and for creating presets as well.

The panel transition was existing way before I used Claude but I was lacking the reordering menu, they were just simple buttons.

@David-Healey

• For annoying and long tasks on the UI for instance. I've just made a re-ordering panel that is nice and smooth.
• For helping me to improve DSP too, and to catch issues I haven't anticipated.
• Sketch new designs quickly
• ...

I was doing the same through the REST API, but without having bugs though...
I switched to the CLI as well

@David-Healey That's where I use it (the blank part above it the bottom of my property editor)
But it's now back, I just needed to remove it and re-insert, probably a compromised window XML...

As the title say:

@Chazrox I thought I fixed it about 2 weeks ago. It was a line that was already there so I simply uncommented it and it was working nicely in Hise. But I suspected it made my plugin unstable/causing crash, so I just went back a step.

I'm not 100% sure it was the real cause, but since the line was commented, I think @Christoph-Hart had a good reason...

Why not just verify if it's on the disk or not and pull it from the server?
Assuming plugins are connect to the internet for your license system in the first place...

EDIT: or even simpler, pull it at the same time you pull the plugin's license...

@Lindon Yup that's because it needs to be thought more as "container" rather than strictly "installer". PKG or ZIP are containers so -> notarisation

4 over 4, that's enough stats for me

@David-Healey yup me too, I will just hold this a wee bit if somebody sees it differently

Currently, when we enable midi learn from right-click -> Learn MIDI CC, we can actually learn multiple CCs (the last one isn't replaced as it is reflected in the MIDI learn panel).

In the dropdown, only the last one is showing, but all previous CCs are still functional until you remove the last CC. Then they all disappear at once.

So something is off. Should we able to only learn/assign ONLY one CC, or should we keep the multi-CC capability and reflect this in the dropdown menu as well?

To me, there's no point in having multiple CCs for one slider, because you get jumping values as soon as you touch a different controller... But, that's just me...

I am in the middle of making a PR for this, so I'd need your opinion guys

SOLUTIONS:

1. Keep only one:

• Easy, just replace the last attributed CC with the new one

2. Keep multiple:

• I would then:
  -> Tick them all in the Assign MIDI CC sub-menu
  -> Expose all "Remove CC#"
  -> Add a "Remove All CC"