Happy new year everyone! Just dropping by with the first official build of OctaLib! As promised, it includes the following:
View bank details (occupied patterns, part names)
Bank swap functionality
Known issues:
The project must be fully saved before OctaLib will load it (i.e. both .strd and .work files must exist)
OctaLib currently only supports Windows. I’m looking for somebody who can help maintain a Mac version (or sufficient donations to help cover the expense of me doing this)
Let me know if you run into any issues (either here, or via GitHub Issues)
The current version displays the state of the .strd files, which won’t exist until the project has been saved. In the future I may look at reading both sets of files, and offering a way to toggle between them, but for now it’s simpler just to read one set, and I (somewhat arbitrarily) chose .strd. If this is problematic for anyone, I can easily change it, though I do think it should be a best practice to save before using this tool anyway.
My understanding is that a sync only needs to be done when removing the CF card, but I’ve not been able to find any real detail about what it actually does.
This differs from my experience: I have not synced once since buying my OT, yet .strd files exist for every project and appear to correctly represent the state of the project as of the last time I saved.
Copying banks (patterns+parts) between projects would enable me to live my dreams, and others too I’d say (to perform with all my best beats in one project without spending days copying files manually) So cool to see this even talked about
Storing them in a library would even be more sweet. I’d love to be able to compile new sets from the library. The other tool we don’t mention had that capability.
Then, we have PART information. 8 x PART (might be related to quick reloading?
Yep, first four part blocks are UNSAVED state (i.e. little asterisk on the part display in the part edit menu). Next four are the SAVED state.
From what I’ve worked out, specific SAVED part is written over the respective UNSAVED on a part reload. And the opposite happens when saving (UNSAVED writes over SAVED).
SYNC definitely writes to the .work files. Pretty sure project save writes to the project.strd. i’ve been using sync + .work files pretty much exclusively with mapping out the underling data structures).
The .work and .strd files are exactly the same data structures from what I recall. They’re just saved/loaded at different times.
Just to make it fun – I seem to remember the arr??.strd files are not saved when saving a project. They’re saved when saving the arrangement. But I might be wrong.