@VirtualVirgin said in Having issues getting MIDI generated in my plugin to the output:

I will keep trying and see if I can find a particular method that works without crashing.

You can do it the old fashioned way and open the xml in a text editor and cut/paste the modules - keep a backup though in case you mess it up (I always do!)

@Mighty23

You'll need a timestretcher.
These are generally either done using phase vocoding or granular.

It's a trick. Samples naturally are repitched by changing speed. To do otherwise requires a dsp that will create this effect.

@VirtualVirgin said in Having some issues with reordering and naming modules: what am I doing wrong?:

So I am running a test here on naming the MIDI Script Processor modules.

What I see is that naming a new module does not take effect in the Code Editor unless another new module is created.

So here a new MIDI Script Processor module is created and renamed (to "NewName1"), yet only appears in Code Editor as "Script Processor1":
Screenshot 2024-10-25 at 2.44.14 PM.png

Then I do the same and make a "NewName2", and this time the first "Script Processor1" turns into "NewName1", and this "NewName2" does not appear in the Code Editor:
Screenshot 2024-10-25 at 2.44.50 PM.png

And again:
Screenshot 2024-10-25 at 2.45.24 PM.png

So I think the only current solution is to make an extra MIDI Script Processor and keep it blank in order for the other names to take effect in the Code Editor:
Screenshot 2024-10-25 at 2.45.48 PM.png

I think what you are describing here is a well known display "bug2 in that the display does not refresh on your name change.. reload the plugin and it will appear correctly.

@Morphoice You can try one of the commits in the late September, works here.

@treynterrio As @orange says the best method is to gain stage within the fx chain. Test it out and use simple gain nodes when you think it is appropriate. Say you have a waveshaper and the "drive" parameter is adding 12dB of gain, then use a simplegain and offset it by the same amount.

Adding a limiter can help but you should only do this if it is absolutely necessary. There is a really great faust limiter I like to use a lot https://faustlibraries.grame.fr/libs/compressors/#colimiter_1176_r4_stereo

And there is more in the faust library you can try if it doesn't work for you. You could probably get similar results in RNBO but faust is faster to implement and well-researched.

@d-healey said in Alias:

@Sampletekk yes it's normal and annoying, doesn't happen on Sonoma though

Ok, my betatesters wodered why I kept sending the aliases......

Link Preview Image HISE | Audio Modules | Midi Player

A MIDI processor that plays MIDI files.

favicon

(docs.hise.audio)

@orange said in Qt Installer framework:

Personally, I do not see any additional advantage

You only have to learn a single installer platform instead of learning a separate one for each OS. It will also look more similar on each system so a user moving from Windows to Mac for example will get a similar experience on both.

@d-healey ok

@griffinboy I'll try and take a look at it later today if I have a bit of time.

@elemen8t said in Chokegroups for oneshots:

So I guess I will have to split them in order to choke them.

Yeah I think that would be the best way.

@treynterrio said in suddenly problems exporting plugins:

"new"

Ah must be a keyword or something... @Christoph-Hart ?

@mmprod here’s an even better example:

@VirtualVirgin

You could use a panel, or a multi-line label.

Add each line to a variable (use the + operator to stick strings together). Then set the text of the label to this variable.

reg myText = "some text"; myText += " Some more text"; // myText is now "some text Some more text" myLabel.set("text", myText);

@d-healey OK, thank you very much:regional_indicator_symbol_letter_t: :regional_indicator_symbol_letter_h: :regional_indicator_symbol_letter_a: :regional_indicator_symbol_letter_n: :regional_indicator_symbol_letter_k: :regional_indicator_symbol_letter_s:

@j-dennis bump