Problem :(((

[yall]

hello there is a small problem. I spent a lot of time creating in instrument except that following an update I lost all my files. I only have the vst3 and the samples left. I could redo everything but since there was a lot of line of code I didn't want to know if it was possible from the vst3 to recover my lines of code?

[d.healey]

@yall

it was possible from the vst3 to recover my lines of code?

Sorry this isn't possible.

Now is a good time to start backing up and using git.

[yall]

@d-healey

[orange]

@yall
Use GitHub Desktop app. It's extremely simple to make backups and control the version/update of your software.

[d.healey]

Git isn't so good for binary files (you don't want to be tracking GB of samples with git).

You should also setup an automated backup (backup locally and remotely).

I use Vorta + BorgBase.

[yall]

@d-healey I use a personal physical server except that it hasn't recorded anything. the disk was full. I thought it was more or less possible to decompile a vst. hackers do it well on cracks ^^ well me the only thing I can hack is my coffee maker

[orange]

@d-healey

I didn't suggest Github for the binary backups.

Since the source code is gone also in this situation, Github is the way to hold the source code forever.

I use Nas device for the big bulk of files.

[ustk]

@yall @orange I have a RAID backup system too. Although I would say that it is safer to also have an online backup of binaries and big files. It is rare and I hope it'll never happen, but a fire in the studio, or "just" a robbery, and you lose more than you want... I'm especially thinking about samples (which isn't my case yet so Git + local RAID is enough for me atm).

[d.healey]

@yall said in Problem :(((:

I thought it was more or less possible to decompile a vst. hackers do it well on cracks ^^ well me the only thing I can hack is my coffee maker

Sure, but assembly code isn't that useful to non hackers :)

[yall]

@d-healey so i just tried something ^^ I opened my vst3 in notepad. I was able to recover 90% of the code. a little messy and missing stuff but i can build on that in the meantime.

[ustk]

@yall I'm amazed!
I didn't know we could access the whole scripting this way... I can't believe my eyes :astonished_face:

Nice for you!

[lalalandsynth]

@yall when i try that with my plugin i just get garbage...vst2 though ?

[yall]

@ustk not the whole. but there are a lot of things to recover

[yall]

@lalalandsynth normally you have a lot of lines on the notepad. approach the end you will see clear lines or do ctrl+h . search for example the word Gain. you will find a line that corresponds to your gain.
I use vst3

[orange]

@yall said in Problem :(((:

@d-healey so i just tried something ^^ I opened my vst3 in notepad. I was able to recover 90% of the code. a little messy and missing stuff but i can build on that in the meantime.

Really? Some part of the source code can be viewed with a notepad? WTF

[Christoph Hart]

Are you sure? The script files are not encrypted but they are compressed before being embedded in the binary so they shouldn‘t be readable without some trivial decompression.

[ustk]

@Christoph-Hart I've tried it myself, I can see my code...

EDIT: Might not be my code in fact, I need to look further... And it looks scambled anyway

	/* SETTERS */

	inmerTime, timeSigValArray[timeSigEnum] * 1/BPS);
	tBpm() : internalBPM;
		BPS = BPM / 60.0;
	rnEnum            = 0;
	reg bypass            = [127, 127];
	const var StepNoteList       
	reg internalBPM             = 150.0;
	reg BPM imeSigs = ["1/2", "1/2T", "1/4","1/4T","1/8","1/8Trn;
		
		local dataToRemove = ModData.getFromConrce(objToRemove))
		{
			_removeEnvelope(objTo
		
		_addFromObject(newObj);
		
		modStoata.env1.remove(modToRemove);
		ModData.env2.remo))
		{	
			newMod = modTarget.addStaticGlobalMssage("Invalid mod " + modName, false);
	 dTarget =   ModData.getDestinationModule(destinIndnewMod.Hold, HoldKnob2.getValue());
				noMode, 32);
				break;
			}
			case 2: 
			{
= "Env 1" && tName == "Cutoff 1") ModData.addFilteal modName = "__" + tName + "Env" + envIndex;
		
		if(targetName == "Tune 1")
		{
			mod.setIntPanel("ModStorage", 0, 0);
	modStorage.set("sne Shaper", "OSC3 Sine Shaper",
								  
									  "Phaser 1", "Phaser 2", "Phaser 3",
			"Env 2", "Velocity", "LFO/Seq 3", "Env 3", "Random      [Synth.getEffect("OSC1 Polyshaper"), 0],
	 ], // Phase 1 Modulation
	   fined, 2], // Filter 2 Env Dec
	    "OSC3 Synth AHDSR"), 3], // AHDSR 1 Sustain
	    DSR"), 4], // AHDSR 1 Release
	   up"), 2 ], // Tune 3

[Christoph Hart]

WHAT THE ... This is scripting code from Hexeract! How on earth can it end up in your binary? I just checked a current project and it also contains these scripting lines.

But I might have an idea what's going on here: I've "trained" the zstd compressor with some scripting code (you can give it some text and it tries to create a dictionary from the most used words which vastly increases the compression ratio for small files and I might have used some scripts from Hexeract as training data as it will pickup all keywords and API methods). But I had no idea that it just stores the dictionary input so this is really funny...

So it's either that or we're doomed and it's a sign from a higher religious entity that we can't leave the past behind...

[orange]

@Christoph-Hart That could be the reason of the Light speed hacking of our software.

So maybe it is time to make everything obfuscated (if it is possible) and prevent this from now on...

[yall]

@orange it's often the dumbest people who make great discoveries lol