Script processors are blank after my last export.

[Chazrox]

@cassettedeath have you opened any of the .xml files to see if anything is still there?

[d.healey]

@cassettedeath which commit of HISE are you using? Do you have a backup?

[cassettedeath]

@d-healey 4.1.0

Unfortunately I don't have a recent enough back up for a couple of important scripts.

[cassettedeath]

@Chazrox Not 100% sure what to look for.

Pretty much all MIDI processors are now just completely blank which is super strange.

[d.healey]

@cassettedeath said in Script processors are blank after my last export.:

4.1.0

If you open the Help menu and click About HISE it will show the exact commit. The version number covers a lot of commits so isn't very precise.

[cassettedeath]

@d-healey When I click show commit on Github it says the application can't be opened

[d.healey]

@cassettedeath That's ok, tell me what the commit hash (the little code thing) is and I can look it up

[cassettedeath]

@d-healey It currently says Load current hash - is it supposed to have a code there?

[d.healey]

@cassettedeath Ah ok, mine's saying the same. Did you build from the develop branch?

[cassettedeath]

@d-healey I'm not quite sure sorry. I usually would just download the zip and build with Xcode.

[d.healey]

@cassettedeath Ok that sounds like you're on the master branch. There were some issues a while back with files being wiped under certain circumstances (you'll find some forum posts about it). These have been fixed so you should move to the develop branch.

[cassettedeath]

@d-healey Oh Jeeze! No good. Thank you for your help

[Orvillain]

Without trying to teach you to suck eggs, if you're not using some sort of version control, you really should. Grab yourself a copy of Fork and a Github account, and commit your project every time you make significant changes.

I've had previous versions of HISE do similar things, where scripts would disappear or be completely empty. Haven't had it happen for a while though. I'm trying to track the develop branch as closely as possible, so I get the most recent fixes and such things.

Anyway, here's the link to Fork:
https://git-fork.com/

[d.healey]

@Orvillain yeah there definitely seems to be a nasty bug in the develop branch, are you able to recreate the issue?

Edit: Ah I was looking at this on my phone and thought you'd just ran into the problem. Carry on.

[Chazrox]

@d-healey damn that thing is going around rn.