@Christoph-Hart Yes just made that mistake 😆

@iamlamprey

oh sorry this was already reported: https://forum.hise.audio/topic/8837/two-uncaught-exceptions-in-samplemaps-to-wavetable-converter

small necro to report that there's a leading slash issue which can only be mitigated by setBaseURL

35dd898e-aac5-4c93-8883-d43f11969774-image.png

@aaronventure You might be right, but in that case it must be default because I haven't changed it on my system.

@Christoph-Hart ah ok, gotcha!

@Christoph-Hart I disabled everything in my plugin other than the main declarations, paths, and LAF.
I even disabled fonts, synth defer callbacks. I have nothing else to disable.

There are 2 issues.

One has something to do with one of my scripts, resulting in onNoteOn not working and the expanding panel not expanding. I'll get to that in a little bit.

The second issue has to do with Pro Tools not displaying anything that is painted using paths. It displays simple elements created using the paint routine but no SVG paths. My previous version of plugin didn't use any paths, hence the reason why it displays ok in PT.

When I use your test script to repaint everything, after a few seconds, all elements show up. So, my conclusion is that there is a bug with painting SVG paths in PT on init.

Can you replicate this issue on your end?

@Christoph-Hart yup, thank you!

@Christoph-Hart said in New Dispatcher Issues:

I vaguely remember that there was an issue with the changed function not doing anything in the onInit callback.

Aha yes, I brought that up a couple of weeks ago. Ok so now I will remove the useless call to changed and the warnings will go away.

@bendurso Yeah it's the same thing I think. As the poster said the previously mentioned method of implementing the solution messed up his git versioning so he came up with an alternative way of doing it. It's the same fix just a different way of applying the change. So presumably it still has the same issue.

@arashiyama Build the develop branch

Actually, no, it just gets stuck after a while when the parameters are linked to scriptnode controls at the top. @Christoph-Hart help!

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 | Docs

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