@d-healey thanks, I’ll have a look

@teamallnighter What HISE are you running?

@alobassmann is GainEditor.cpp the Simple Gain effect?

@Christoph-Hart is there any chance to consider a feature where we can do a forever-export of a Faust file to a .cpp file that we can just save and forget about it? Then we can just plug it into any future project and it loads as a node with parameters (like it does when you compile it right now)?

I created some modules that are decently simple, do what I want them to do and sound great - I would be very happy if they kept doing that forever, wherever I pull the project on, without having to worry about the correct version of Faust being installed, about recompiling the entire networks and making sure it's all well when first pulling on a new system etc.

@d-healey see my other post - I cant even get to any code I've written for FAUST as HISE says Im still on the old version.

@d-healey I managed to bypass it by manually setting <ExportSetup value="Yes"/> in compilerSettings.xml

I just noticed a fix to the midi keyboard has been pushed, does it solve this?

For Reaper, you can change shortcut behaviour.

1 -For plugins you can send all keyboard input to the plugin ( this is done by FX menu.)

2- You can set the shortcut scope to global, normal and global+text field (this is done by actions - edit shortcut )

@bendurso I can't remember. It's been years since I dealt with sample libraries.

@Christoph-Hart said in Monlith reference sample start/end screwed up:

just check the monolithoffset property for differences between the two.

Running into issues with this again. One thing I noticed is I have a sample map, which was previously saved as its own monolith, contains monolith offset values, but when I redirect the sample map to another monolith, these offsets don't change. Should they?

Is it a case that both sample maps need to have the same mapping but the properties of the zones can be different?

@Christoph-Hart that's still hardcoded and all the node instances of that file will share the seed

but you have me an idea to just link the random node from scriptnode into the faust parameter, so that'll work as the random node gets instanced on startup

@d-healey Alright these are fixed now.

@HISEnberg I know. I'm just reporting this issue in the Hise GUI.

@Noahdeetz

I have gone down this route once more, and so I will be testing this again soon,
but this time I am using a peak meter node as the Display Buffer.

So far it's working, but I haven't compiled it yet.

The advantage of using a Display Buffer over a Global Cable is that the Display Buffer has memory of past events (within the buffer). This can be useful if you need to access this data, for instance if you wanted to calculate RMS or other loudness calculations, or if you want to draw a graph that follows the volume over time.