@JulesV My solution is to use a flag. If the plugin is being initialized, load a specific preset that has my settings. if the plugin isn't being initialized, it doesn't do anything special.

@JulesV I ended up using a script that checks a flag if the plugin has been initialized or not. something like:

const var ProtoolsParameterFixer = Engine.createTimerObject();
const var InitialState0 = Content.getComponent("InitialState0");

inline function InitializeState()
{
	if(InitialState0.getValue() == 1)
	{
		Engine.loadUserPreset("/Factory Reset.preset");
		InitialState0.setValue(0);
	}


}

ProtoolsParameterFixer.setTimerCallback(function()
{
	InitializeState();
	this.stopTimer();
});

ProtoolsParameterFixer.startTimer(200);

@Lindon I've used iLok on 4 of my plugins. Just wrapping, not fusion. Totally doable, but you'll be editing the HISE source to implant the code.

I'm using Voicemeeter Banana for this

@dannytaurus said in Taking my Mailing list seriously, so a first question....:

What are everyone's feelings on how many emails to send per week/month?

I think frequency matters way less than intent and value. As long as the email is useful or interesting, you can send a lot. Plenty of companies send emails every day because… it works. But spammy “BUY NOW / 50% OFF / LAST CHANCE” emails every other day is a good way to make people lose interest.
Our weekly “New Monday” blog gets great engagement because it’s not a sales pitch. Luke does a great job at giving you a new perspective on how to think about sound.
https://korneffaudio.com/blog/
Most of our email automation revolves around how to get the most out of a new product. Give them tips and tricks, as well as real life uses. We'll occasionally throw in an upsell, but those are secondary.
In our marketing meetings, we always ask ourselves "would I open this email?". Most of the time people unsubscribe because the email stopped being worth their time.

I'm using the same as @David-Healey FluentCRM and Amazon SES

@David-Healey Congrats!

I can't seem to make this repo public for some reason, but here's the download link:
https://dankorneff.com/wp-update-server/packages/korneff-jwt-auth.zip

@David-Healey they didn't seem interested, so I'm maintaining my own fork. Maybe you can strip the update from my repo and make a PR?

@ustk I ended up fixing the issue in the JWT wordpress plugin.
I was having issues with special characters as well

I'm using Activity Watch to track time on an app.
ActivityWatch - Open-source time tracker https://share.google/Edb7SuzvFWQrHf5ZR

Maybe you can borrow some code

@bendurso I can't quite remember. Reading the post it seems to be related to how my webserver was redirecting the traffic. I'll take a look in the AM to see where I left off

@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.

@d-healey said in Linux vs ThirdParty Nodes:

If you delete the one in your .config folder I don't think it will change anything.

Is there any reason that HISE creates an additional folder .hise in the first place?
If AppData = ~/Application Support = .config, and HISE stores its program junk in AppData (Win) and ~/Application Support (MacOS), why doesn't it use .config on Linux for consistency?

@d-healey in my distro this is also the equivalent of app data.
Not sure why both get auto-generated

@iamlamprey I remember somewhere that the configuration exists in 2 different places for some reason. You might be editing the wrong one.

I’m running into a crash on Linux that I’ve traced to hise::GlobalServer::WebThread, and I’m wondering if anyone else has seen this before. The plugin runs perfectly in Linux Standalone and Reaper. Windows/macOS is fine on all DAWS.
In Bitwig on Linux, the VST3 loads fine… but crashes when HISE’s WebThread attempts to download & parse JSON (update check, preset manifest, UI image metadata, etc.)

When the crash happens, the backtrace lands here:

juce::JSON::parse()
juce::JSONParser::throwError()
hise::GlobalServer::WebThread::run()
abort()

@d-healey have you encountered this before?

I have something similar happen in Cubase. Haven't had a chance to investigate yet.

@Christoph-Hart said in Unlocker - How to use?:

you can implement your own server database that handles this

yeah... at the end of the day, I created a whole License Manager wordpress plugin that communicates with the plugins.

@DanH @Christoph-Hart
What OS are you testing on? I have a user on Yosemite 10.10.5 that's getting a "Status 0" reply from our server, but can login/activate/deactivate my older plugs. Thinking maybe something with a recent commit.
Might be related?