Tried on Linux Mint, no problems here, even after decreasing and increasing the slider number. They all work within the range of -12 to 12. (latest commit)

@DanH I have not, but there are plenty of others who have.

@DanH exporting this on a more recent commit seems to fix the issue :crossed_fingers:

@orange thanks

@lalalandsynth Same Here
I also experiences another bug:

I connected the Clock ramp node to a table,
after choosing another multiple Value, for example, X3, it starts from the middle of the table, and not from start.

@fotisandstuff is the key/note number 89? I had a similar thing a while back that comes and goes, pretty sure my midi keyboard is haunted 🙂

Link Preview Image Cursed note 89

Had this popup a few times over the last few weeks. I think it has something to do with the arpeggiator, I don't remember the first few times, but just today...

favicon

Forum (forum.hise.audio)

@d-healey Ah yes, I sneaked that one in a few commits ago. The problem with declaring var statements in an inline function is that they pollute the global scope which leads to all kinds of weird issues and there is no reasonable use case where you would want to declare a var instead of a local variable in an inline function.

@Christoph-Hart It works, thanks! :)

i notice the user audio module opens the correct folder when you right click on it. whats the line of code that tells it what directory to open for that specific module? it might hold the key to my original question

edit: on Windows {AUDIO_FILES} works just fine. so i guess a better question is why it no work for mac? lol

another edit: well holy cheeseballs. im an idiot. problem solved. i was using the string that was generated by saving the preset in the compiled plugin manually and it contained the line data="filename". changing that to fileName="{AUDIO_FILES}didthetrick.wav"/> . thanks for the help @Christoph-Hart @d-healey @Lindon

@ulrik It's working by now!

The tempo is usually stored in the DAW project so not sure whether this is important for the development process (In a standalone project the last BPM is stored in the GeneralSettings.xml file).

@d-healey Right, I somehow missed that.

Thank you for your assistance.

Circling back around to this issue as this still happens on all of my builds. Would love to get some help on this one.
Overwriting an existing preset will crash my plugs.

When I debug the standalone version on PC, I get the following;

Test Debug.exe!juce::MessageManager::callFunctionOnMessageThread(void *(*)(void *) func, void * parameter) Line 176 Test Debug.exe!juce::Component::runModalLoop() Line 1746 Test Debug.exe!hise::PresetHandler::showYesNoWindow(const juce::String & title, const juce::String & message, hise::PresetHandler::IconType type) Line 682 Test Debug.exe!hise::UserPresetHelpers::saveUserPreset(hise::ModulatorSynthChain * chain, const juce::String & targetFile, juce::NotificationType notify) Line 61 Test Debug.exe!hise::ScriptingApi::Engine::saveUserPreset(juce::var presetName) Line 2251 Test Debug.exe!hise::ScriptingApi::Engine::Wrapper::saveUserPreset(hise::ApiClass * m, juce::var value1) Line 859 Test Debug.exe!hise::ApiClass::callFunction(int index, juce::var * args, int numArgs) Line 366 Test Debug.exe!hise::HiseJavascriptEngine::RootObject::ApiCall::getResult(const hise::HiseJavascriptEngine::RootObject::Scope & s) Line 140 Test Debug.exe!hise::HiseJavascriptEngine::RootObject::Expression::perform(const hise::HiseJavascriptEngine::RootObject::Scope & s, juce::var * __formal) Line 633 Test Debug.exe!hise::HiseJavascriptEngine::RootObject::BlockStatement::perform(const hise::HiseJavascriptEngine::RootObject::Scope & s, juce::var * returnedValue) Line 52 Test Debug.exe!hise::HiseJavascriptEngine::RootObject::FunctionObject::invoke(const hise::HiseJavascriptEngine::RootObject::Scope & s, const juce::var::NativeFunctionArgs & args) Line 560 Test Debug.exe!hise::HiseJavascriptEngine::callExternalFunctionRaw(juce::var function, const juce::var::NativeFunctionArgs & args) Line 413 Test Debug.exe!hise::HiseJavascriptEngine::callExternalFunction(juce::var function, const juce::var::NativeFunctionArgs & args, juce::Result * result, bool allowMessageThread) Line 449 Test Debug.exe!hise::WeakCallbackHolder::CallableObject::call(hise::HiseJavascriptEngine * engine, const juce::var::NativeFunctionArgs & args, juce::var * returnValue) Line 904 Test Debug.exe!hise::WeakCallbackHolder::operator()(hise::JavascriptProcessor * p) Line 738 [External Code] Test Debug.exe!hise::JavascriptThreadPool::Task::callWithResult() Line 2012 Test Debug.exe!hise::SuspendHelpers::Suspended<hise::JavascriptThreadPool::Task,hise::SuspendHelpers::FreeTicket>::call() Line 221 Test Debug.exe!hise::JavascriptThreadPool::executeQueue(const hise::JavascriptThreadPool::Task::Type & t, juce::Array<juce::WeakReference<hise::JavascriptProcessor,juce::ReferenceCountedObject>,juce::DummyCriticalSection,0> & pendingCompilations) Line 1866 Test Debug.exe!hise::JavascriptThreadPool::executeQueue(const hise::JavascriptThreadPool::Task::Type & t, juce::Array<juce::WeakReference<hise::JavascriptProcessor,juce::ReferenceCountedObject>,juce::DummyCriticalSection,0> & pendingCompilations) Line 1876 Test Debug.exe!hise::JavascriptThreadPool::run() Line 1931 Test Debug.exe!juce::Thread::threadEntryPoint() Line 96 Test Debug.exe!juce::juce_threadEntryPoint(void * userData) Line 119 Test Debug.exe!juce::threadEntryProc(void * userData) Line 66 Test Debug.exe!thread_start<unsigned int (__cdecl*)(void *),1>(void * const parameter) Line 97 [External Code]

@d-healey I could not recreate the behavior in a Content.createLocalLoockAndFeel()

I spoke too soon, some errors you can not recover from. Some syntax errors are fine, but when something really does not work, laf will not recover. Looks like if I do actual runtime errors that are syntactically correct the laf reverts to something older, and does not try to recompile the laf function until reload.

@Christoph-Hart I believe this affecting SNEX nodes as well.

EDIT:
scratch that. My ProcessFrame code was commented out. Still not working on analyzer nodes though

@Soundavid this works incredibly well, thanks for sharing