@Dan-Korneff said in Linux vs ThirdParty Nodes:

@d-healey Exported plugins store their data (presets, documentation, etc.. ) in .config within the Company subfolder. Just like the structure on MacOS and Win. I just don't understand why it would be different for Linux.

Yep that's true. It's just HISE itself that stores it in the home folder. According to the Filesystem Hierarchy Standard dumping them in the home folder is acceptable.

However the XDG Base Directory Spec recommends a .config folder.

It's a mess. I'd prefer it to all be in .config too. Maybe we can put it to a vote.

nevermind i found it

@ulrik Good to know that. Thanks!

@Lindon Perfect! Thanks!😀

@d-healey thank you so much😁

@ILIAM Most of the docs are available as markdown files

https://github.com/christophhart/hise_documentation

You can also pass in specific urls, but the results are a bit hit and miss.

@ulrik sorry its definitely user error, something in my project preventing ANY nodes from compiling not just this one. mysterious smh lol. this works fine in an empty project.

@d-healey I followed this method . Everything is working on my end except for one thing: the installer always shows 0 KB for the size of my data package. The samples are over 2GB but appears as 0 KB on the installer

@dannytaurus yes, if the menu list is longer than the ui it will be drawn outside of it, like in your image.

@Lindon nope that aint it...something else is broken...

and its a line in my code..so that is the solution... just need to refer to Globals explicitly

@Chazrox 😹

@dannytaurus said in Scheduled knob task after initialization:

@JulesV Interesting! What's the use case for this, if you don't mind me asking?

It can actually be used for other purposes.

But in my case, I'm actually using it for a bug workaround. When I buld a complex custom node with 23 parameters and use it in HardcodedFX, I noticed that in one parameter, the knob, wasn't getting its value during plugin initialization.

However, after init, when the knob is tweaked, the value is updated. That's why I chose this method. Creating a custom node with fewer parameters isn't a problem, by the way. As the number of parameters increases in custom nodes, the problems increase.

@lijas90 I usually chuck an Audio Loop Player in the module tree because it allows drag and drop of audio files to test with.

@Elisee18 I have an old video showing a method of doing this (it requires scripting)

https://youtu.be/_s7LTRz8pEc

@Ajak said in Modules Not Nesting In Containers:

the windows are driving me mad

You can build out your module tree in the sidebar, you don't need to open the windowed view.

@pcs800 well 95 samples would make hardly any difference at all... whats the measured latency of your plugin?

oh hang on youve already said:

95.9ms, that's great. But how do I get the plugin to report that to the daw?

Go read what @ustk said above.....

@d-healey Ah!! Well that can't be good. Sorry about the speakers. I'll have a read of the documentation and get to grips with scriptnode first, I've taken up more than enough of your time. Thank you very much for all your help.