@Dan-Korneff said in Replacing the LinkOSX file:

@orange ok! That's where we need to look. Check the permissions of the file that was previously installed. Who has what permissions when you right click on the file and hit "get info"?

This happen even on an admin account. I think since there is a file, Whitebox doesn't overwrite it.

@DanH said in Replacing the LinkOSX file:

@Dan-Korneff I use a pre-install script to remove any files / folders before installing new ones

That did the trick, Thank you! So for this purpose, first a Pre-Install script to remove the file:

#!/bin/sh rm -rf $HOME/Library/Application\ Support/MYCOMPANY/PLUGIN/LinkOSX exit 0

Then the Post-Install script to replace it:

#!/bin/sh sudo -u $USER mkdir -p $HOME/Library/Application\ Support/MyCompany/TestPlugin/ /usr/bin/rsync -avurpE --remove-source-files /Library/Application\ Support/MyCompany/TestPlugin/ $HOME/Library/Application\ Support/MyCompany/TestPlugin/ sudo find $HOME/Library/Application\ Support/MyCompany/ -type d -user root -exec sudo chown -R $USER: {} + rm -rf /Library/Application\ Support/MyCompany exit 0

@toxonic this has been reported before

@DanH ok great :thumbs_up:

@lalalandsynth Yes the low pass might have a error margin that is relevant in a pitch context (it usually stops smoothing at a difference of ~-80dB but this might be a audible error when you map 0...1 to a 20kHz range.

The linear mode should be fine though.

@MikeB said in A few questions of understanding:

If I have almost 100 knobs (in different panels) that should all look the same, a global LAF is better, isn't it?

If they all look the same and all have the same colours then it doesn't matter. I'd still go with local so that I had control over individual knobs and so it didn't make the HISE UI knobs look weird, but it really doesn't matter.

With a local LAF, I would need an additional 5-10 scripts for each knob for the individual LAF.

You can use the same local LAF object for multiple controls. I put almost all my laf in a single file. See this as an example.

all declarations in one script?
Does it make sense to collect all component declarations in an external script "declarations.js" or better in different scripts at the beginning of the respective function?

As I mentioned I put almost all my laf functions in a single file. I put component declarations into separate files, each with their own namespace. So if I have a set of controls all relating to a mic mixer, then they go in Mixer.js with the namespace Mixer.

@d-healey Ah ok, great ! Thanks

@Lindon

Brilliant thanks

@Christoph-Hart would you have time to look into this soon you think? :)

@Christoph-Hart @d-healey Thank you for the information - all set. I'm running it under Rosetta, and it's fine.

@DabDab @Matt_SF
Thank you, guys!!!

I'm assuming this hasn't been added to Hise at all?

@lalalandsynth said in Polyphonic midi effects? Pitch drift:

@Straticah osc 2.png

This random thing is stepped though , what would be more suitable would be super slow smoothed noise or something.

set the smoothing as high as possible, you can set the tempo programmatically to something really really slow...

@d-healey I think you are right. I managed to solve the problem this way:

I created a folder in "Applications" where I moved both my HISE folder and my Project Folder. I created a root user and logged into it (https://support.apple.com/en-us/HT204012) I exported my vst.

It worked fine but instead of having an exported vst file in my project's folder I found there a copy of it. I clicked to show info of this file and it said the original VST is located here: /private/var/root/Library/Audio/Plug-Ins/VST3/"my plugin name".vst3

Screenshot 2022-11-30 at 14.58.15.png

So I used that one and inserted to where all my other VSTs are and it worked fine.

use the templates with the soft_bypass setups.

@d-healey I will find it - thank you

@Jlev777 Make sure to set the correct path here.
path.png

@Sounddiy Latest develop branch (https://github.com/christophhart/HISE/commits/develop)

@d-healey I know

It is a mix of your's, others and peharps mine :)

@Straticah On a typical vintage synth there would be 2 typical scenarios.

One envelope - you can select if its for both filter and vca and if you would want the volume to be unaffected you would set the "volume/vca" to gate mode.
Then the "volume" is just on and off and the envelope shapes the filter but not the volume.

2 Envelopes , one for VCA and one for filter , which would give you what you have now.

So to have the second envelope no affect the first one , you would just not use a second one and use the first one for both OR, have a GATE setting where the VCA is on/off and the filter envelope takes care of things ,BUT then when you let go of the key there is no release.

@orange they are universal binaries. seems only related to logic - will try to get more info.
found this on the Juce forum:
https://forum.juce.com/t/macos-ventura-13-0-problems/53624