Let's Decode a VST

Re:Let's Decode a VST by djaychela on Saturday June 13, 2020 @02:34AM (#23507327)

Has anyone got some similar info for sylenth 1? I have a lot of patch backs for it, but they are not ordered in what I would consider a sensible way - random distributions of different types of patch in a bank. I extracted loads of them and sorted them into folders, but what I want to do is then put them back into banks (such as a bass bank, etc), but there's no way to do this quickly in sylenth other than to load them all in manually and then save the bank.

I can't make sense of the data in existing individual patches or banks (I did some single value changes and resaved and the file was completely different), so it's probably above my pay grade, but if anyone has some ideas they would be appreciated.

(I'm a simple amateur python programmer, for the record)

[ Parent | on HN ]

Re:Let's Decode a VST by akully on Saturday June 13, 2020 @02:50PM (#23511685)

I used the same approach: turn knob, save, see what the bytes look like.

For one of the Reason instruments that I was thinking of decoding, I encountered a similar problem. Even saving the same patch with different filenames resulted in different looking bytes.

This is outside my own scope but try graphing these patch files out, color coding and seeing what patterns you can notice.

[ Parent | on HN ]