@pcs800 Sorry, haven't read the whole thread but have you tried with the HISE source on C: drive? Just to rule out anything related to different drives and unexpected paths

@d-healey Yeah, it's quite different to what I'm used to in Ruby and Rails.

@d-healey It would be even better if instead of this:

OSC1.setAttribute(OSC1.VoiceLimit, value);

we could do this:

OSC1.VoiceLimit = value;

but I'm guessing that's too dynamic (or something) for C++?

Just my 2¢ - you can see which commits are passing or failing CI on GitHub. It's probably a good idea not to try building from one of the commits that's failing for your OS (Mac/Win).

@HISEnberg Might be an idea to wait and see how the Azure system rolls out.

Sounds like they'll open it up more over time.

@Chazrox Perfect! Thanks

@d-healey Is there any documentation for the six frame method?

Just saw RNBO 1.4.0 adds a new export target called Minimal Export for C++.

Might this be useful for adding RNBO to HISE in a simpler way?

From Cycling 74:

Minimal Export

A heavily reduced, engine-less C++ code export that is targeted to enable RNBO to run on small “bare metal” targets like Arduino Giga, Electrosmith Daisy and similar.

Here is the documentation: https://rnbo.cycling74.com/learn/minimal-export

Comes with these example projects:

• RNBO Minimal Export for Bare Metal Targets: https://github.com/Cycling74/rnbo.example.baremetal
• Example of how to use RNBO code on the Arduino GIGA R1: https://github.com/Cycling74/rnbo.example.giga
• Example of how to use RNBO code on the Daisy Audio Platform: https://github.com/Cycling74/rnbo.example.daisy

Enables the adaption of the Electrosmith oopsy platform for RNBO which is currently in beta testing: https://github.com/Cycling74/oopsy/tree/stb/RNBO

@d-healey In my experience, traditionally the term 'encode' means to convert from L/R to M/S and the term 'decode' means to convert from M/S to L/R.

So maybe it's the names of the modules that are wrong? Although I doubt that will get updated for legacy reasons.

Still confusing though!

@Chazrox said in Slider issue:

@pcs800 Did u look into LAF for this? You can animate that slider cap still image with this easily. Lets say in your case you have the slider cap and the background image… import both images into your LAF function, draw the background image as still, then animate only the slider cap for current value. Its 2 parts (images) and 0 frames.

Start with a vertical slider, create a Laf, import your two images then use g.drawImage to use your images in your LAF. Im on my phone right now so when I get on the computer I can show you an example. It's pretty friggin simple.

Definitely this

@pcs800 Sounds like you might be making it a lot harder than it needs to be.

@d-healey said in HISE Meet Up:

@Christoph-Hart said in HISE Meet Up:

a new AHDSR envelope with loop mode & draggable curves

Noice! Release curve editable?

Double fingers-crossed for this!

I'm using a vertical slider as a volume fader.

I want to use a custom image for the fader cap but making a filmstrip seems a bit wasteful of both time and plugin resources.

How do I implement a simple static fader cap image at the 'movement' point of the slider?

I feel like this is going to be either [1] using LAF to draw the fader cap image at the value point, or [2] using CSS to draw the fader cap as a background image in one of the slider's pseudo elements - but I genuinely have no idea how to look this up in the docs or the API reference.

+1 here too

@Chazrox said in Chord Player Inversions || Help with Indexing!:

I also got midi out to DAW working as CHORDS or ARP mode! yee!

Looks cool!

Since compiling as MIDI FX is currently not working (as I understand it), are you planning on releasing this as an instrument instead?

Trying to understand how that would work in various DAWs. I'm assuming you're taking a MIDI input from the DAW (either from a connected controller or a MIDI clip in the DAW), then outputting MIDI from your instrument plugin that is meant to play another instrument plugin?

Routing like that is easy in Reaper but other DAWs seem less flexible (I'm looking at you, Logic).

@Elezeid said in Memory leak with Engine.loadAudioFilesIntoPool:

Engine.loadAudioFilesIntoPool();

Are you sure you aren't calling this function anywhere else in your code?

@Mickolos Other than the incorrect regex, your code seems have a couple of other problems:

1. You put all knobs into 'comps' but then later loop through 'knobs', which is not defined in your code.
2. You create a look and feel called 'ValueLAF', then later assign one called 'knb_LAF', which is not defined in your code.

I realise these might be copy/paste inconsistencies and your code is actually correct. But just wanted to point it out.

@Mickolos You're missing the * in your regex.

Instead of
const comps = Content.getAllComponents("^.(Knob|Button).$");
use
const comps = Content.getAllComponents("^.*(Knob|Button).*$");

The dot is looking for exactly one character. The * modifies that to look for any number of characters, including zero.

The way you had it will only match components that have exactly one character before the word and one character after the word, like 1Knob1 or ZButtonZ.

If in doubt, use a regex tester like regex101.com. Put the regex in the top text field then add some example component names including wrong ones, to see which ones the regex matches.

The next image shows that the only ones matched by your original regex are the last two.

The next image shows that with the extra * in the regex, ALL the names are matched.

@Christoph-Hart Nevermind, found this post https://forum.hise.audio/topic/1259/ahdsr-release-curve?_=1749402810437

Still, would be lovely to have release curve for AHDSR, if it's doable.

@Christoph-Hart That would be perfect if I could adjust the release curve - is that possible?

@d-healey RAM, I think. Swap and Memory Pressure go off the charts in Activity Monitor.

My Mac is basically unusable for the whole hour that it's compiling.