@d-healey I just delete the script node and I can see now works , but I will made more test on diferents Daw-s and I will be back with more info , tank you a lot , you save me

@d-healey I didn’t try this …. just now I will try and come back with news , thanks a lot

@d-healey any help , please. Maybe you have an ideea about what happen with these errors , thank you

Hi everyone,
We’re having ongoing issues with a new plugin created in HISE on Mac. Here’s a detailed summary:
What we’ve tried / observations:

The plugin works fine as VST3 in FL Studio and other DAWs.
The AU version compiles successfully in HISE, notarized and signed, but:
In Logic Pro, the plugin appears in the Plugin Manager but is marked as Not Compatible.

Trying to add it to a track either doesn’t show it or shows an exclamation mark.
In GarageBand, the plugin is visible but doesn’t open properly.

AU validation (auval -v aumu Blkn Sjce) passes, but when opening the plugin, these errors appear:
"error at node wet_path1 can't create node with factory path container.chain"
"The audio buffer size should be multiple of 8. Please adjust audio settings"

On VST3, the "error at node wet_path1" also appears, but clicking OK allows it to work — indicating the node initialization issue persists.

We have checked all Info.plist fields (type, subtype, manufacturer, CFBundleIdentifier, CFBundleVersion, etc.), rebuilt, signed, notarized, cleared DAW caches, rescanned, etc.
We are at a point where we feel like we’re going in circles.

We’ll attach screenshots from FL Studio showing the VST3 node errors and from Logic Pro showing the AU compatibility issue.

Question:

Has anyone encountered similar AU/VST3 node initialization problems with HISE plugins on Mac?

How do you handle wet_path1 or similar chain errors so that AU works properly in Logic/GarageBand?

Any guidance would be greatly appreciated!

Hi everyone,

I'm trying to understand how pitch wheel modulation works. When I create it inside HISE, everything seems to work correctly.

However, when I export it as a VSTi plugin and load it into a DAW (I'm using FL Studio), the pitch wheel modulation no longer functions.

Is there a way to control the pitch wheel using a Slider instead? That way, users could use the mouse to control it, or map the slider to a MIDI CC via MIDI Learn. Would that be a valid workaround?

I’m still a beginner and trying to figure out how these things work, so I apologize if this is a basic question. Any help or explanation would be greatly appreciated!

Thanks in advance!

@DanH

Link BufferStop

@DanH

Thank you very much, yes, I’ve seen those examples :)

My problem is that I want to create Glide/Slide effects on sounds generated from ScriptFX, not from the synth node script. I made a mistake;

I built this synth in FX and I can’t manage to move it to the synth script node (actually, when I move it there, it doesn’t work correctly).

That’s why I’m trying to create a slide/glide effect in ScriptNodeFX.

I saw something similar to glide in the bufferstop example and I tried to use CHATGPT for this, but it’s quite difficult because I’m a beginner at coding :)

I’m trying to solve an issue. I’m attempting to create a Glide/Slide effect in ScriptNodeFX. (with SNEX)

To be honest, I’m not very skilled at coding, so I’ve made something with ChatGPT. I want to implement this effect in ScriptNodeFX because I created a synth in FX, but I can't control the pitch and slide.

At first, I managed to create a pitchbend, but there is a significant delay in the sound when I press a MIDI key.

Do you think there are other possible solutions?
Thanks!

@d-healey The problem was that, thank you very much for your help!

@d-healey That's a good point. I'll check the folder permissions and make sure everything is set correctly.

Thanks for the suggestion!

@d-healey Do you think there's anything I can do to fix this issue?

@d-healey It seems that the build worked fine when I manually opened the Juicer file in Projucer, launched Xcode, and built the project manually. It successfully compiled the files.

This suggests that the issue might be related to the automated build process or setup.

@d-healey Thhe version of Xcode is 16.2, and yes, I have installed xcpretty. OSX :sequoia 15.2

@d-healey said in Issue with Plugin Export in HISE on macOS:

You're trying to compile an FX plugin? Did you select to use VST3 and did you extract the VST3 SDK?

Yes, I am trying to export an FX plugin, and I have also tried the VST export. I extracted the SDK zip file into the "Tools" folder as instructed in the documentation.

@d-healey Yes, I have compiled HISE from source.

Would you have any suggestions on what I can try next to resolve the issue?

Thanks!

Hello everyone,
I’m facing an issue when trying to export a plugin in HISE and I’m not sure how to resolve it. I’m new to macOS and I’m a bit confused about what steps I need to take. Just to mention, I don't have IPP (Intel Performance Primitives) installed on my Mac, and I haven’t been able to install it yet. Could this be the cause of the problem?
I’ll leave the error message here so you can have a look at it. Thanks in advance for any help!

Last login: Sun Dec 29 23:40:09 on ttys000
/Users/toni/Desktop/Proiecte\ Hise/Test\ VST/testVST/Binaries/batchCompileOSX ; exit;
toni@MacBook-Air-Chircu ~ % /Users/toni/Desktop/Proiecte\ Hise/Test\ VST/testVST/Binaries/batchCompileOSX ; exit;
/Users/toni/Desktop/Proiecte Hise/Test VST/testVST/Binaries/batchCompileOSX: line 3: 3716 Killed: 9 "/Users/toni/Hise/HISE-develop/tools/Projucer/Projucer.app/Contents/MacOS/Projucer" --resave AutogeneratedProject.jucer
Compiling FX plugin testVST ...
2024-12-29 23:49:56.563 xcodebuild[3717:95453] Writing error result bundle to /var/folders/2q/vm9bh_tj1n193j83wczcmblh0000gn/T/ResultBundle_2024-29-12_23-49-0056.xcresult
xcodebuild: error: 'Builds/MacOSX/testVST.xcodeproj' does not exist.

Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Proces finalizat]

Hello everyone!

I need some guidance on the process of preparing a plugin for end users. Specifically, I'd like to know:

-What files need to be included for the user after completing a plugin?

-Where should these files be installed to ensure the plugin functions correctly?

Additionally, are there any notable differences in the installation process between macOS and Windows?

Your expertise would be greatly appreciated!

@HISEnberg Thank you very much for your help, indeed the problem was the space after "Jucelay." Have a wonderful day!

@d-healey no , for windows

@d-healey In the past, I successfully exported a few ideas, and they worked. But now, I’m getting this error, and I haven’t made any changes.