Unified module data representation
messmerd opened this issue · comments
In order to reduce complexity and duplicate code, increase the ease of implementing support for new modules, and remove an unnecessary step in the conversion process, as much module data as possible should be represented in a form which is module-agnostic.
This data should include:
- Orders
- Patterns
- Rows
- Notes
- ...
In addition, there should be a common interface for accessing this information about a module regardless of its type (DMF, MOD, XM, etc.)