@David-Healey Nice! And thank you for putting these resources together, they are an incredible source of info and help for beginners like me, and the wider HISE community.

@David-Healey thanks for replying. I think i sorted it out. After a brief chat with Claude, it said:

This is a known HISE issue related to file locking - something (another program, antivirus, or even HISE itself) is preventing write access to your script files. Here's how to recover:

Immediate Recovery Steps

1. Close HISE completely

2. Check the TempScriptDirectory

Those JS files in Scripts/TempScriptDirectory are actually your current scripts - HISE puts them there when it can't save to the normal location. This is good news - your work exists.

3. Manually restore the scripts
   Navigate to your project's Scripts folder. You should see:

Your normal script files (possibly corrupted/empty)
TempScriptDirectory/ containing the working versions

Copy the files from TempScriptDirectory back to their correct locations:

ScriptProcessors/YourProject/Interface.js (or wherever your interface script lives)
Same for each ScriptFX

4. Check what's locking the files
   Common culprits:

Cloud sync (Dropbox, OneDrive, iCloud) - if your project is in a synced folder, this is very likely the cause
Antivirus scanning the files
Text editor with the JS files still open
Git or other version control

5. Restart HISE and reload

Preventing This in Future

Don't keep projects in cloud-synced folders (or pause sync while working)
Close any text editors that have script files open before saving in HISE
Add your HISE projects folder to antivirus exclusions

I then proceeded to leave all my HISE folders and docs out of syncing with OneDrive, copied all the script files from the temp folders of all my projects, and pasted them into their respective 'normal' project script folders. Seems to be working with both saving and loading now.

@ustk Okay I understand, thanks. Since I'm new to this I just wanted to check what the norms are so I don't do something wrong. I am an advocate of giving credit where credit is due!

@Christoph-Hart That's great, thank you for answering!

@dannytaurus excellent information, thank you for that! I thought though that if I keep using the standard-for-HISE-right-now JUCE 6, then I'd have to re- enable the splash screen? But if i use the new optional JUCE 8, then I don't have to do that.

Also, I'm not actually sure how I switch to using the newly added JUCE 8.....

Hi all, hope everyone is good! Am I completely off the mark thinking that this could be a viable option for releasing closed source plugins?

My thinking is that the HISE license is needed for closed source projects made with HISE, always, no debate... and with the free JUCE starter license you can earn up to 20k annually before having to get a paid license. Now that JUCE 8 doesn't require a splash screen on startup on the free tier, we don't need to mess with the HISE source code to enable it again.

Am I missing something here or could this be an option?

Any clarification on the matter would be greatly appreciated!

@David-Healey Nice! And thank you for putting these resources together, they are an incredible source of info and help for beginners like me, and the wider HISE community.

@dannytaurus really is a good tip! I don't really understand though why it happened all of a sudden now though. It's been baking up and syncing with OneDrive for ages without mishap. Anyway, local backups and external drives from now on. I never liked the cloud!

@David-Healey thanks for replying. I think i sorted it out. After a brief chat with Claude, it said:

This is a known HISE issue related to file locking - something (another program, antivirus, or even HISE itself) is preventing write access to your script files. Here's how to recover:

Immediate Recovery Steps

1. Close HISE completely

2. Check the TempScriptDirectory

Those JS files in Scripts/TempScriptDirectory are actually your current scripts - HISE puts them there when it can't save to the normal location. This is good news - your work exists.

3. Manually restore the scripts
   Navigate to your project's Scripts folder. You should see:

Your normal script files (possibly corrupted/empty)
TempScriptDirectory/ containing the working versions

Copy the files from TempScriptDirectory back to their correct locations:

ScriptProcessors/YourProject/Interface.js (or wherever your interface script lives)
Same for each ScriptFX

4. Check what's locking the files
   Common culprits:

Cloud sync (Dropbox, OneDrive, iCloud) - if your project is in a synced folder, this is very likely the cause
Antivirus scanning the files
Text editor with the JS files still open
Git or other version control

5. Restart HISE and reload

Preventing This in Future

Don't keep projects in cloud-synced folders (or pause sync while working)
Close any text editors that have script files open before saving in HISE
Add your HISE projects folder to antivirus exclusions

I then proceeded to leave all my HISE folders and docs out of syncing with OneDrive, copied all the script files from the temp folders of all my projects, and pasted them into their respective 'normal' project script folders. Seems to be working with both saving and loading now.

Hey all, got a weird error just now when trying to save XMl: 'The embedded script files could not be saved (probably because the file is opened somewhere else). Press OK to show the folder and move it manually'

it just takes me to a folder in scripts folder called TempScriptDirectory containing JS files of my scriptnode FX and interface? It's a pretty important project. Does anyone know what this means or how to fix it?

Im also getting errors now when trying to load a project, it says 'Script not found' 'error loading script interface' (and all my script FX). After I click through the errors, I get to my project but the oninit interface is blank and the console says 'interface: onControl could not be parsed! (And again same for all my script FX)

My module tree and UI appears to be intact and all script FX still have correct routing and what not inside scriptnode, just seems to be effecting scripts?

Does anyone know how to fix this?

Any help would be greatly appreciated!

Merry Christmas and happy holidays to all!

@ustk Okay I understand, thanks. Since I'm new to this I just wanted to check what the norms are so I don't do something wrong. I am an advocate of giving credit where credit is due!

@Christoph-Hart That's great, thank you for answering!

@ustk This Is EXACTLY what I was after. Thanks so much for taking the time to reply. I understood the whole external display buffer thing, I just wasn't aware that you could slap it on a normal panel! That's amazing! The snippet is really straight-forward and holds a wealth of valuable lessons and information for someone like me who's just starting out. It totally makes more sense now!

Would I be able to get your permission to use the snippet in my project that I intend to release (modified to my own project of course)? I'm not really sure how it works with that kind of thing on here when someone helps with code, do I need to ask for permission to use it? And do I have to credit who sent the helpful code/snippet? Also, if someone uploads a 'how-to' video on stuff in HISE, can I follow along with their code and incorporate it into my project? or do I need to ask permission/add credit there also?

@HISEnberg I did not know that. Now I do! Thank you for taking the time to reply!

Hi all! I was just wondering if there is a way to change the colour of the scriptnode fft analyser in a floating tile on the UI? The colour options in the component properties have no effect. (unlike with the standard analyser fx) I'm pretty new to HISE and programming in general so even if there is a way to do it via LAF or something, I'm not sure what to do after I right click on the floating tile with the fft analyser in and clicking "create local LookAndFeel for selection".

Any help would be greatly appreciated!