Unknown Fields

[ashduino101]

Describe the feature

Hello,

If you're interested, I've been working on a 010 editor binary template to help reverse engineer FLP event formats and data structures. I've already added some structures that haven't been implemented in this library yet, so this might be useful to you. The template is available as a GitHub gist.

What version of PyFLP are you using?

Latest source (v2.2.1+)

Screenshots, Additional info

Code of Conduct

• I agree to follow this project's Code of Conduct

[meint52]

Very nice! Im using ImHex since it's free, do you know if there is an easy way to use this template in there?

[demberto]

Nice work, I'll add info about this to the README. Just a small thing I noticed, note size wasn't always 24, I have found FLPs having Note event sizes of a multiple of 16.

Can you give some brief summary of which fields or events you have discovered not present in PyFLP? If its an entirely new event ID can you also add something about it in #34?

[ashduino101]

Very nice! Im using ImHex since it's free, do you know if there is an easy way to use this template in there?

I'm not sure if you can load 010 Editor templates into ImHex, but ImHex looks like it might be a better option for this research, so I might just port it to an ImHex pattern.

Can you give some brief summary of which fields or events you have discovered not present in PyFLP? If its an entirely new event ID can you also add something about it in #34?

Some things I've looked into that aren't in PyFLP:

• Automation -- though a lot of it is still unknown, I've found some of the additional properties as well as LFO
• Remote controllers -- only 1 unknown field left, though some may be mislabeled
• MIDI controllers -- though not in the template yet, I think I've written down some notes on the structure of such events
• Track data -- Completely discovered
• Channel parameters -- added more unknown fields, such as the sampler support for SimSynth and DrumSynth, and used the right type for sample start and end offsets (float64/double, in PyFLP, it's decoded as a couple of uint16s surrounded by unknown fields)
• A couple more wrapper properties -- position & mixer attributes (something that I haven't added to the template yet: bit 3 of the flags is if the window is maximized, which I'm surprised wasn't figured out sooner)

I've also looked into some plugin formats such as 3x OSC and Parametric EQ 2, which might be worth documenting.

In terms of additional events, I haven't really kept track between PyFLP and the template, but there are some additional fields such as Controller Formula (230) and a couple events related to layer channels.

[meint52]

Currently im working on an ImHex pattern. It detects all event fields but it does not ID them yet. Here's the file for it if you want to tinker with it. Just make sure to rename the extention to .hexpat.

flp_structure.txt

[meint52]

By the way, is there a table somewhere with all the known event ID's and what they do?

[ashduino101]

There's the switch-case statement near the top of the template, but not much more than that. I might make a repository to keep track of these things and store the research/templates.

[ashduino101]

I made a repository if you want to submit a pull request with the pattern. Feel free to also submit issues if you find any interesting fields or figure out any events.

[ashduino101]

I've been trying to reverse engineer a couple more plugins over the last couple of hours, and I found something a bit interesting -- Fruity Convolver uses the same structure for envelopes as points stored in regular automation clips. I assume this might be some common structure; if it's completely discovered, it will probably help with other various structures.