Just checking before updating Scriptnode...

[SteveRiggs]

Hi all,

Just checking before I take the day off to update to the latest scriptnode version of HISE on the Mac...

...is the latest scriptnode version all working perfectly and stable?

I'm also wondering if there have been any project breaking changes since the ancient scriptnode version that I'm still using? (11th Dec 2019)

Thanks in advance

Here's my current version:

[ustk]

@SteveRiggs Stable, yes it is. As for the compatibility, I'd say no if you have DSP networks. This is what happened to me, but I will have to recreate everything in the next version anyway... But for regular use, I don't think there are incompatibilities. My advice is to keep a backup of both the old Hise and the project when you make a big step until you have all of it working

[SteveRiggs]

@ustk

Thanks. I do have a lot of DSP networks in active projects that are 99% finished. Having to re create them all at this point could put me back a while.

The only reason I'm updating is because the 11th Dec 2019 version was missing a bit of code so the EQ curves don't recall in exported plugins when the project is closed and reopened inside a DAW. Thats the only thing I need really at the moment, so if the DSP stuff is all broken do you think it would be a safer option for now to just update to the version after mine where the missing bit of code was added and just use that one?

[ustk]

@SteveRiggs yeah definitely, if you go to the last version I'm 99% sure you'll break your DSP. It's broken at the moment, I mean, more than it was at this date. The only chance to release a DSP-based plugin is to wait for the new version. So be safe and choose just the update you need ;)

[SteveRiggs]

@ustk Cheers mate. You probably just saved me a huge headache

[d.healey]

@ustk said in Just checking before updating Scriptnode...:

My advice is to keep a backup of both the old Hise and the project

Or use git...

[SteveRiggs]

@d-healey I actually watched a few of your videos on git last night to try and work it all out. Seems like a must have. I'll set it all up as soon as these last niggling jobs are out of the way.

I was going to ask actually (probably a dumb question, but I haven't used it yet)...

When you pull a new version of HISE from git with the latest fixes, does it overwrite the compiled version and just work, or do you have to recompile it again for the new fixes to be applied?

[ustk]

@d-healey Absolutely, but in this case, I personally like to keep an old copy of the project folder so I can quickly make some tests if I need to modify the XML for instance. It helped me last time when I lost my DSP with the new version. But your totally right, everything can be done with git ;)

[d.healey]

@SteveRiggs

When you pull a new version of HISE from git with the latest fixes, does it overwrite the compiled version and just work, or do you have to recompile it again for the new fixes to be applied?

Git is a version control system, it doesn't recompile HISE for you. When you fetch from github, git will attempt to combine all of your files with the latest changes it finds on github. Occasionally there are merge issues but if you're not editing the HISE source code on your system it shouldn't be a problem for you. Once you've completed the fetch request your local copy of the source code should be the same as the one on github. If you need to go to a different version you just need to go a git checkout to change version. If you want to switch branch or create a new branch you can also use the git checkout command.

@ustk

but in this case, I personally like to keep an old copy of the project folder

But git does keep your old copies. Just make a new branch to do your testing.

[SteveRiggs]

@d-healey Ok brilliant. Thanks!