@d-healey said in Linux standalone instrument application and settings folder locations:

/home/.config is a folder. . on GNU/Linux means the folder is a hidden folder. The default vst folder is /home/.vst or /home/.vst3/ and LV2 plugins go in /home/.lv2`. I'm pretty sure most users are familiar with this.

Windows and (especially) MacOS like to tell users what to do, GNU/Linux is a little more flexible generally, depending on the distro and desktop environment.

Okay, that´s a big part of why a lot of people choose Linux instead of the others. That´s a part of the platform and most experienced users or intermediate will handle that fine. The obviousness/strictness of a mac is a big part of why an answer can be found almost anywhere. And having rules for it is a big part of a platform. Nevertheless, freedom is in the whole Linux air. To be respected.

You can download an installer I created here to try it out.

Will do! Thanks a lot for the info.

This info should really go in the docs. The paths on Linux is an essential part of docs. One fine day. Perhaps I´ll get there first, you never know.

@Lindon said in Standalone app icon:

@andioak -- no don't do this. Inserting your own icons in a mac build will cause it to fail to notarize (well that's my experience anyway,,).

Aha, thanks for that caveat! :) So if i´m deadly serious about rez-snaz I gotta go into the hise source and add some if:s. Not sure that the amazing feeling seeing my logo in 8k instead of 4k is worth that atm. But one fine day, it shall shine.

@dustbro thank you , but it look like my filmstrip doesn't have middle :D

@d-healey Thanks for the verification!

@D-Williams23 put a simple gain after the filter...

@Natanr https://en.wikipedia.org/wiki/Regular_expression

@d-healey 😎 No more git to sync/update between machines...

@DanH Yes it is weird... Apparently, it comes from the release and retrigger combo. If you put the release at zero it's kind of better, but set it above and the retrigger makes a weird click noise... @Christoph-Hart ?

Agreed !

This is needed , as it stands you cannot select a preset to save over , as soon as you click it , it loads.
You should be able to load preset 1 , select preset 3 and save over it .

@Christoph-Hart
Working!
Thanks!

Thanks both!

@ustk in fact I can do it perfectly from the code but as I assigned about thirty buttons from the property interface, I didn't want to redo everything. I would have thought there would be a solution.
I just thought, what if I want to retrieve the value of the button but from the effect and not from the button c is possible?

yes I only want a single label, indeed it will display the last selected button but that does not pose a problem for me.
the solution to recover the value from the effect can be done

@Christoph-Hart Link is dead.

Its been some time now since my last post.. Someone must know...?
I can't figure it out...
Could some one please take a minute to have a look at the script?
Thanks

@D-Williams23 No problem!

About editing the C++ though. I've been learning it lately, is it worth going in there and trying to figure that out? Do you know which folder has that particular file?

You can find the file and the header file here: HISE/hi_components/plugin_components/PresetBrowserComponents.cpp

@Christoph-Hart If not too much of a pain, is there a possibility to open other files such as .cpp or .h in a ScriptEditor tab?
If the code editor improves, I could be cool not having to rely on third party editors anymore, just sayin'...

iiuc mdaLimiter.cpp swaps attack and release param indices, which probably needs to be reflected in MdaEffectWrapper.h

also, the desmos plots below show mappings from unity range to the synthesis range (equations taken from mdaLimiter.cpp). the release nonlinearity / black curve looks kind of suspicious to me. haven't analyzed the actual dsp algorithm though, so maybe it is just fine.

https://www.desmos.com/calculator/gkttms7sbn

@ustk no ahah that’s why it was not working! Thanks a lot!

I've just updated the jucer template output by HISE to include the path to the SDK3 folder inside the JUCE directory by default when exporting a VST3 plugin. This will avoid users having to copy files over to the version inside the tools/SDK folder and you won't have to worry about adding the path to the jucer project manually.

I've also enabled bigobj by default on VS17 and improved the naming of some of the output binaries (doesn't make a different most of the time but stops me getting confused writing my exporter app trying to keep track of all the different variations of binary name)

@Christoph-Hart I've made a pull request to scriptnode for these changes, thanks.