@Sawatakashi I can't get you a far advanced response, but basically yes, you'll have to go C++ and probably a SIMD integration regarding the efficiency.

But yeah that's probably how I'd do it, not knowing if there's a better (and accessible) method.

Since a C++ node gives you access to Hise API, Juce API, and any third party library you'll want to import, Hise won't be the bottleneck.

@Lindon Thanks for pointing that out. It was a typo. Corrected it.

@duma Impossible to say without seeing your project.

@Christoph-Hart it appears for some reasons (intended?) the affine transform line was commented out.
Was it a mistake or intentional I don't know, so I've made a PR anyway...

It is to be noted that the drawAction forces the scale to true so we always end up in the else branch of the PostGraphicsRenderer. Therefore the AffineTransform is necessary...

@David-Healey ok that makes sense. Thanks

@Christoph-Hart

Thanks
I'll hold off for a bit then,
until you've finished that!

@David-Healey I just forgot the stage of setting the permissions with your provided code "chmod -R 755" before packaging

@David-Healey
All right, thank you for your input! :-)

@griffinboy said in LFO Phase Control - Now shifts phase in realtime:

@Orvillain

Me as well, I've got a few.

I used fixed point math for all LFOs now.
You can get really cheap phase manipulation and implicit wrapping

Ahhh interesting. Mine is not using fixed point math, and actually looking at the code, I've just spotted a few areas where I can make them cheaper! Ahhhh... to the Trello board.......

@YOKAN said in Questions about Profesionnal Virtual Drums for metal with Hise:

I'm really sorry for my poor English, I hope that you will understand what I try to mean.

Your English is fine.

With the MIDI map the only problem I see is if you want to insert a new item, let's say Tom5: 44 you then have to renumber all of the others. If it was an array you could just insert the new value and the indexes would still all line up.

@David-Healey 😆 Oh well. Success here anyways, thanks for the help

@David-Healey Ah yes I've got it. So encode to .hxi > export HR1, then I need to use installExpansionFromPackage that's accessible from a button or something in the UI that'll unpack the HXI and samples. thanks!

@dannytaurus I've added a PR for the slider mod value -> https://github.com/christophhart/HISE/pull/858

Now it would be cool to have it modifiable live from the settings extra definitions but I don't know how to do it...

@Christoph-Hart
I tested it and both the compilation of a VST instrument and the compilation of DSP networks work perfectly. Thank you very much! :-) I will test the compilation of an AU instrument in the next few days and give feedback.

There is another bug:
When I want to create a new project and that project already exists in the folder where I want to create the project, HISE simply crashes without an error message.

@Christoph-Hart Have you had a chance to look at this? The last fix doesn't seem to have worked. Maybe it's something simple?

@clevername27 but 2 of the three reasons don't require a custom crash report (no crash => nothing to report. Running under debugger => even better diagnostics) and you're deliberately introducing the first reason with your custom crash handler :)

@Avián ..and remember the pixel width and height ratios are different on Mac (square) and Windows(not square)

@clevername27 said in WhiteBox Packages Nightmare on Sonoma:

@Lindon Your installer is dope, and very cool.

why thanks. I built it because Sample based instruments of any sophistication will need a whole bunch of different data to be stored in different places:

The plugin in its correct folder (white box and package builder are good at this bit) The "app data folder" - for stuff like meta data The presets folder - which is in the AppData folder the Expansions folder - ditto above the sample data folder - and its friend the LinkFile which needs completing...

In a "just open one thing once and get it all done" approach the "commercial" installers are not really set up to do this stuff without learning a whole bunch of scripting(and really why should they be...) so building my own was the only option.

@dannytaurus This is 100% true. Our data and research show that music producers prefer interactive chord tools to chord packs. Chord packs are considered lazy.

What we've seen with AI is companies like Lemonaide training their models to let users generate chords with a single click, but these models take a long time to train.

Our approach is quite different. We want to use AI to help producers learn music theory as they produce.

Thanks!