Reminder to myself for the next time I look for the setting.

AAX-library- option in vs2022.png

@DanH said in New Repitch Node is causing compile errors:

I was hoping it would effect the incoming audio signal

It does, but it repitches it back to the original samplerate so it's not a "realtime pitch shifter". You can do some cool stuff with it though, mainly allow changing the frequency response of static effects. I've added some docs here:

Link Preview Image HISE | ScriptNode | container.repitch

Processes the internal processing chain with a different sample rate

favicon

(docs.hise.audio)

Here's a example of how to change the frequency response of a filter without changing the filter coefficients (but beware, it produces a noise as soon as you load the snippet!). This can be applied to all kinds of effects, like resonators, convolution reverbs etc...

Note that the frequency response is inverted, but if you put the sound generator in the chain it would be correct.

HiseSnippet 1583.3ocuXsraaaDEcnkG4ZWmlDjftrP.ciCPpAojrdftvN9gREZsihkqQ1ELgbTDgH4vRRYa0hBTfhBj8cU1kuhh1ME4CHcU+A5htqaxeP68xgTjTTV1RnIz.Fbtyi6495LWpNdBctuuvinr5Iib4Dk0ocG4Dzeu9LSGR68IJeD8Ple.2qjTztibY99bChhRgGhBTVcYR3ya2dWlEyQmmHhPNUXpy+JSayfDoc14KMsrZwL3mXZmZ0U2ostvYOgkXHfmBTUhKSe.647iX3xVhRTJdfgYfvqa.Kf6STVdWgwnt8Em6HW+ol9lOyhiCzHcgCRJtkvx.QLJkrWeSKiNw1sOANkNIdgBRuvcoGZZXNVdh23VgSTJYGo8GJKkEdEx.OsKCdSARJofzxRHcaZWcOS2fjYP77gz1NPvoGCb6oghbsDkWS2S.KvIXSa1.dKOXv3MrQMU06WB92897dCczCLENkDNGIB3OxYi6s12s1pq88qUZxo50apygpwSXYw8l5zXj1aVabCmg1Oi6c+RmwrFxGuPv7y5SKd87o5RqN0BENscLCdjKOZ7rSJHQtM3sut89r.FFThjAqyk6EXhvQYe9YPFtLDsJcet+f.gKjimK9AYNBigVrfroSXMTzDf+HSLDCTN9lAiRWiMG4XpyLG65BwaS6XFn2e5XboofQvS8t.iQUl2fdPudb8fD.tLs0SVzxP0qeYHUp+0hJCAchJe8ngkZ8DsLf3ng1sLsfJM..TEEvVhKIeAMI820i6x73mH5XwFsgOy10heLf56W5YVB8AcM+Vd9ZFWIn1EWwF58YNNbK+Eozp3+SzUjiECCLcd9gr.OyK.6EL9t.ItNeuHzg9fkvpJ4XUbLlozk6XDN3egmnI0F6vfI0hmLUA4Q7fyEdCBCPQuSTVQFM7CcxOs2E.7AeOltprBUcS3OxCrrDmumv10LJQNzvBk1QXMxsuvwTGicx0DC9GXKFB5MxB9Bl+ILSKL2u6PefMw3QNcgEGduGl6cjv.dqXKlN3ZG0gEzGqgP9HHgk6so93D2LnMI2ILqDhBcXdv8dxLHDn3AGe4nz6A3zFcIgWMV.mG8IEjHfJud.T7Y.YE2ijAQ2IDQPxwlIKHS56UnrTbfxxDbDPBrDp0hHOBmbJltEVwDTNjCgPRXQNg48bdfeDspCWWFQBcesMPtTnzHbSi8Cn3aROVJVZMDRJuDBj3QPT+PSmHDDyLswqOjcwjx1oa.2EKzRyx1c.+7HMjRJZaqPkGvDGCg7fgABanPJjVjjJFrNU3qCM7fzpjboEd7MSM8hFBvo.piKhuoZeSeWfQY2g.WozyjQBFmbL3WDWbc.vOX.2FFt83BtLd1ho7rEy6YgHaNO6slSOa1rljSgLaUWcmbp9E+4jp9Uu7k+VdUuyOZ+GaKKSZ4w+lgPQ7nIz+OL3pz+a2NuoqNml95g5uzwXkAI24SleeOnr4z2+PH08clpAt7YTP0oOyeJETuGzcwv1uRT8u7I+z+73e822Np7sHtlDhnoPfJoziWP5Filc06j76JKcETpqSa6eJNqNyJFuQzLx6AS3anT+y5kEr2f1S1Kxl3TYup4pnYlfYItolwulvkfmVVlD3.tbZDZRLsHsLdAcp.JH.d.YoCd2EtHub4lMUqtUsxkqTsQ8FaQlr9MMObAxz02cfCphZ3ilVyxpMK2LkxuCs4lMZhO0zZrUE0x0qjGF0pVWqdCs5UTqskViZgvn.8wYRie8adymlg9X4DHrB8yzZjwlKRCEjOujh8uPtDSQNYxoPoZSwqUQUSEM3lMaTsYcUsHuVWagHnOz4Vrp9X7zTaJepWuV0Fk2pQ4qutqh5dbInDK441WDCZJG5pzCbXPCpFjLKkj4hwLoeKM69C9qoPkS14ZQo7peV8uCoTlrAkbGW19DleNNxbd2xMk+BAthnldmAO6jsPUTF5vZKx0tapoBjbJcZ1P5NAu7FCS2RalVCi6LirHDo6JDCrYgeTwh8A+uO9DHaltm3oQMtiF2GDJAHdbB+ExVkdHNtjF4rI821lFlOUWO6QkaikWzMVYQ2X0Eciasnar1htw5K5Fab0aD+QEiHFvrcntuyAxqPUh43vay9OfsHodN

@tomekslesicki Ah good catch, this slipped in when I was refactoring some of the complex data code (in particular the filter coefficient management across DLL boundaries). Should be fixed now.

@pirilon The sustain state should switch when sending values > 64, so it should work with continuous pedals. What happens if you print out the controller value in the onControllerCallback()?

@Christoph-Hart Thanks for the clarification! I've been having some issues getting Scriptnode networks working in the compiled Rhapsody plugin but I'll try again today and see if I can figure out why it's doing what it's doing, otherwise I'll just keep the current setup

@d-healey Hmmm. This guy seems to think it's possible https://forums.steinberg.net/t/no-program-changes-in-vst3-regrettable-decision/122202

Looks like this is the solution @Christoph-Hart https://forums.steinberg.net/t/midi-program-change/201860

@Christoph-Hart Is this possibly still affecting the convolution reverb settings? I'm seeing identical behavior where values are retained but visually not recalled.

Edit - to be more specific, the Wet Level, Dry Level, High Cut, and Damping seem to be the culprits.

@iamlamprey you can now build with debug symbols right from HISE.

@d-healey it will be a learning curve for me. no problem for now it works like a charm on Windows, and Ubuntu 22

@Christoph-Hart Yes to both. I just pulled in your changes and those errors are now gone. I'm still getting a crash with segmentation fault though so time for me to dust of my debugger and find out what's going on.

Also regarding the Global MPE mod, this bug is still there - https://forum.hise.audio/topic/8486/bug-global-mpe-intensity-range?_=1702818146707

Bump bump

@d-healey that 🤦 should go one the t-shirt...

@Christoph-Hart If you tell me what the flag is and how to set it I will send you $10 tip in PayPal...

@Christoph-Hart any luck?

@d-healey Hmm, it didn't work. However, I just realized that I only needed to trigger the ComboIndex, and it worked (as you mentioned initially). Thank you :)

inline function oncmbPolyShape2Control(component, value) { Polyshape2.setAttribute(Polyshape2.Mode, ComboIndex[value - 1]); }