btw, for the most part, ot-tools-io doesn’t translate data to human interpretable values. quite a few fields will need translating from “octatrack data representation” to “human representation” downstream.
i thought of spending a while creating enums for absolutely everything, but that’s a lot of work for what i was planning to use this for. so i’ve not been planning on doing “human interpretable data values” as a priority.
You are right, my bad ^^ Project sent to you in pm
Sure thing no worries, I did some processing to display some of the pattern details in a human-readable way
No problem at all, I believe it’s the role of the UI to handle this conversion in any way needed. Having the raw data available is perfect and allows for flexibility
very interested in this project, and its amazing to see it coming together so fast!
on v0.1.12,i had success opening all of my projects except one where i got:
Error loading project: Failed to read project file: ProjectParse(InvalidValue(MidiChannel))
Thanks for your interest @vasmarg138 ! Feel free to further test and provide feedback
It’s going quick at the moment because most of the work has already been done in @dijksterhuis 's library - which, without a doubt, took months of work to get where it’s at. All credits goes to him
It was a backup template project file outside of a set, not sure if that matters. PROJECT VERSION 17 ----- OS_VERSION R0167 1.31
btw, huge respect to you for your hard work as well, didnt mean to belittle your part when i talked about realization speed before, just the UI’s very active development
Let us know how that goes @Wick ! Keep in mind that if any projects were saved with an older OT firmware, you’ll have to re-save them before opening them up with the app
You were right, it was not master time signature (which actually does not exist, only pattern time signatures exist afaik - global to pattern or per track) but metronome time signature
My bad, I updated label like so:
I also fixed labels in Patterns section that way (and at a few other places):
I have started looking into that: notes were indeed not displayed correctly. I fixed half issues about it, need some more time to polish it but it’s coming.
I found a little bug, when selecting a step with parameter locks, the same p-lock information is also displayed under every other track, which is a PITA when scrolling thru multiple patterns/tracks.