@Chazrox Your namespace has the same name as your variable, that will cause an issue

@HISEnberg Hi, finally I've gotten back to you now. Thanks so much!

I don't know if I need to change something inside the HISE or JUCE project first.
After testing it again, I found that I got some errors about "MD_DynamicRelease" issues as I exported the AAX directly from HISE. So I re-exported it by opening the autogenerated project from Juce. I fixed from "MD_DynamicRelease" to "MT_StaticRelease" in Visual Studio 2022. Then it seemed to build successfully. Now the Pro Tools DEV detected the plugin.

But I wonder if there's a way I can directly export AAX from HISE.

When I do it on my MacBook, I find I meet the other problem. (AAX SDK 2.4.1, HISE 4.1.0, M4, Xcode 16.1, sequoia)
I can only compile the ARM version for the AAX plugin in Xcode, which warned me I could not compile the universal AAX for both Intel and ARM MAC.

Big thanks again, I believe that you must have experience with it.

@d-healey Ah, I'm sorry! I reloaded the snippet to see if that would work and all of the .js includes then said "embedded" at the top so I was assuming somehow the snippet export catches all of the .js files and "embeds" them into the snippet.

I'll take a look at the project later and figure out how to send you all of the relevant files.
Cooking dinner for the fam at the moment.

Thanks for your help :)

@HISEnberg said in FFT Analyser Path - Need help drawing the magnitude to height:

does that just mean the Synth.deferCallbacks(true), or are you referring to the specific script?

Interface script should always be deferred. Included scripts are just part of interface so they inherit from it.
Scripts that are dealing with midi/audio shouldn't be deferred

@DanH You mean more or less like this correct?

Screenshot 2025-05-12 at 4.37.10 PM.png

You could accomplish it with a simple delay and modulating the delay time. @griffinboy is correct though, reading papers and checking some repos is the way to go here. My example is more or less just a theoretic flanger but doesn't match the performance of what you may find from people who have done actual research on the topic.

But you can try this:

import("stdfaust.lib"); // UI maxdelay = 0.5; delaytime = hslider("delay [ms]", 5.0, 0.0, 20.0, 0.01); //Add si.smooth(0.99) for interploation here if you want feedback = hslider("feedback", 0.5, 0, 0.99, 0.01); mix = hslider("mix", 0.5, 0, 1.00, 0.01); // State variables SR = ma.SR; maxdlsamps = int(maxdelay * SR); delaysamps = int(delaytime / 1000 * SR); // Dleay delayedSignal(x) = fb ~ de.fdelay(maxdlsamps, delaysamps) with { fb(y) = x + y * feedback; }; modDelay(x) = (1-mix)*x + mix*delayedSignal(x); // Stereo process = modDelay, modDelay;

@pcs800 said in Buffer warning when plugin runs:

@DanH Worked perfectly, thanks!

I think this warning message was added for a good purpose.

If I remember correctly, it was added because of problems in FL Studio. So, the problem is solved by adjusting the BufferSize. It might be better if it remains IMHO.

@Lindon cool, got that working. So where do you put the Arp midi processor and how do you set it to a specific midi channel?

@Kunal-Babbar said in FREEMIUM MODEL:

Hello, I am looking for someone who can help me create a freemium version of my plugin :D

If you are comfortable and open to work, please contact me at Kunal@sauceaudio.com or WhatsApp me on +919711192750.

Obviously the project is paid and timeline is 7 days :D

Best
Kunal

Ok everyone - if you are thinking of taking this give me a chat-based shout.

@Christoph-Hart @HISEnberg Good examples, thanks.

@VirtualVirgin That would be awesome. It looks like it would serve a very similar purpose. I want to create a MIDI drum rack and route the MIDI outputs to individual tracks in the DAW. If in a couple days you are still struggling with this I would be happy to contribute (currently working on something else), so just keep me updated and thanks for your input!

@Christoph-Hart fifteen minutes in, but there's still hope 🐷

@Christoph-Hart said in Parallel Threaded Voices in Hise?:

If your synth is able to max out a single core it won‘t work in a musical context anyway

Maybe I phrased it a little wrong, I'm talking about SIMD.
Many synths for example use SIMD for batching unison voices, or voices in general, or left right channels even, and processing them in parallel. This is common, no?

I was talking about parallelism rather than just threading.

@d-healey Wonderful I'll see if I can rewrite with just the File (System) APIs in that case! Luckily for me these are "universal settings" so they should be applied cross each instance of the plugin.

@Christoph-Hart that would be super cool and flexible I think!

@Christoph-Hart
All right. Thanks for the explanation! :-)

@HISEnberg It's really nice of you.

@DanH you need to use the filters to get the best out of it, and use quotation marks in your search terms if you want an exact match.

@Lindon said in Logic Pro crash when playing MIDI:

They execute in a top down order - so your instruments onNote first then down thru the tree...

I think we can't be 100% certain about this. Since they are running on two different threads, the one on the audio thread will have priority.

@Sampletekk said in Logic Pro crash when playing MIDI:

If so, should the code that was in the "On Note" callback in the Interface script, go into the "On Note" callback in the new "Script Processor1"?

As Lindon says, it depends on the code. But if the code is affecting Messages then yes. If the code is updating or changing things on the UI then no.