[Solved] Anyone got some python that plain texts repatch files?

[Billy+]

Have anyone got a python script that can produce plain text version of repatch files?

I would like to be able to produce old school patch sheets from patch files.

[dioxide]

I think repatch files are plain old XML so if you open them you'll be able to read everything.

[Enlightenspeed]

Have anyone got a python script that can produce plain text version of repatch files?

I would like to be able to produce old school patch sheets from patch files.

Two questions mate.

Why do you need a Python script for this, when you can open .repatch files in most text editors?
What is an old school patch sheet, and what would you use it for?

Just trying to get an idea for the motivation behind the request.

Cheers,
Brian

[Billy+]

Didn't know you could, hadn't tried and an old school repatch sheet / recall sheet to you can view the setting without having to look at the individual parameters without having to look at every knob slider button etc.

But dioxide answered a few days ago I just haven't had time to actually check, not that I don't believe the response. I just assumed the files would be something other than plain txt / xml.

[DaveyG]

It's always worth opening any file in a text editor and also trying to open it in 7-Zip. Increasingly config and data files are zipped/compressed text/XML files but with a different extension. If you ever open a file in a text editor and the first two chars are "PK" then it's a zip file.

[Enlightenspeed]

an old school repatch sheet / recall sheet to you can view the setting without having to look at the individual parameters without having to look at every knob slider button etc.

Still a bit baffled tbh

Is this for live work then? So you can tell from like a spreadsheet or something which patches have, as an example, filters set to LP24 with the freq down low so you can do a kind of morph between the two?

Is it that sort of idea?

Cheers,
Brian

[Billy+]

Recall sheet

IMG_1649.JPG (100.83 KiB) Viewed 1750 times

just makes it a bit easier to try out similar patches on alternate synths.

[Billy+]

Still a bit baffled tbh

Is this for live work then? So you can tell from like a spreadsheet or something which patches have, as an example, filters set to LP24 with the freq down low so you can do a kind of morph between the two?

Is it that sort of idea?

Cheers,
Brian

But that is an interesting idea.

I'm also have an interest in creating some repatch files but that's another story.. especially if they are xml based.

[eXode]

Recall sheet IMG_1649.JPG just makes it a bit easier to try out similar patches on alternate synths.

Is that one of the Brian Eno patches for the DX7?

[Billy+]

Recall sheet IMG_1649.JPG just makes it a bit easier to try out similar patches on alternate synths.

Is that one of the Brian Eno patches for the DX7?

Well spotted eXode

[Billy+]

Actually I just checked a few repatch files and the strings are encoded in some way! So you can't actually read the values just the names.

[buddard]

Actually I just checked a few repatch files and the strings are encoded in some way! So you can't actually read the values just the names.

Each character in the string is represented in hexadecimal format (2 digits per character).
So the string "Hello" will be displayed as 48656C6C6F.
This is in order to store all strings in a 100% safe way, since many ASCII values don't represent visible characters.

[Billy+]

Actually I just checked a few repatch files and the strings are encoded in some way! So you can't actually read the values just the names.

Each character in the string is represented in hexadecimal format (2 digits per character).
So the string "Hello" will be displayed as 48656C6C6F.
This is in order to store all strings in a 100% safe way, since many ASCII values don't represent visible characters.

Thanks, that will save some time.

5468616e6b732042756464617264