#199998
thinking about doing it in rust, though i have to look into what languages have what libraries for audio and ui/graphics
#200012
didn't think about fm but if there's a need for it, it shouldn't be too complicated to add
microtuning is something i'll have to think about more, i really want to make a flexible system, maybe even something that could take in basic math expressions for frequency ratio calculation
macros will very likely be implemented, i've thought of doing stuff like triggering an entire sub-pattern for one channel with an effect command (fitting more stuff into one row, or applying something to each note) (this would be a good reason to bring the polyphony limit up to a larger number like 512 or 1024 - i brought that idea up in the discord during the initial convo and people felt like those numbers were very high)
also going back to microtuning - i've thought of using a regular int for the note (in a pattern), with 0 denoting the root pitch of a sample, but when i considered that multi-sample instruments are also something that will definitely happen, i'm not sure how exactly the note values will be stored (i'm not a huge fan of the notation idea since it could complicate things like switching between tunings or even transposition); maybe ditching the idea of a root pitch is better with the large range that 16 bit ints give, and just letting the sample rate option of a sample be related to some constant note (a4? c5? this is complicated)
#200014
thanks! i'll definitely have to check out that thread and give an update about how i feel about all of those features (very likely that i'll agree to implementing them all)
#200022
as i mentioned a bit earlier, macros will likely be implemented, so no need to worry about that one
text-based file format could happen, probably with an external tool (still developed by the same dev team!) - it would unfortunately be something that would come later, since while serializing the data isn't difficult, parsing it back into the regular format could have its own set of challenges
compressed format could also be done, it's probably as simple as just compressing the whole file with zlib
dsp effects.. this is one thing i was worrying about a lot - i know basic effects like the ones openmpt has by default could be implemented, but i wouldn't expect vst support - it's a topic i know nothing about from the technical side, and i'm worried about having to deal with things like licenses - i've seen that distribution of vst plugins requires getting a license, not sure about just implementing support for them; also, i would like this tracker to be cross-platform, which might not be great for vst support; i think it's best to consider it as something that could be added post-release, if we figure out how to do it well without making compromises to the experience users would get on different platforms
tempo will be stored as a 32 bit decimal number (float/fixed point, undecided), which means you can go ham with the tempos :3
the options of ticks per row and rows per beat are also currently undecided, we'll pick the one that seems more flexible (or offer support for both as a module-wide setting like openmpt does)
