-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Features #1
Comments
What do you think of implementing a General MIDI export? |
It isn't really useful and doesn't really serve the purpose of this editor. The primary goal of this editor is to directly edit/export *.asm song files for immediate use in a pokecrystal-based project. So that you can press "Save" in Crystal Tracker and immediately run MIDI editors exist for creating MIDI files. |
Ah, I understand. What about implementing a "traditional tracker" view? I.e OpenMPT, Furnace, etc |
There are several problems with trying to imagine this working with a traditional tracker view. The Pokemon song data format is not well suited for it. Most fundamentally is that in Pokemon, the song channels are completely independent from each other. One channel can loop a small pattern many times while another channel plays a long sequence of all unique notes. It's also possible for a channel's entire body to be much shorter than another channel's body (ie, the short channel may fully repeat many times in the time that it takes the longer channel to play once). In fact, the channels are so independent that there is no requirement that all the channels loop back to the start at the same point in time -- or that they even loop back to the same point at the beginning. So the concept of a "row" can't really apply here in the way that it would need to for a traditional tracker view to be effective. |
@duckiedev It would be possible but my preference is to keep the list of toggles pretty modest, and I prefer the current behavior of just pitches over pitches+octaves. |
Trackers such as Klystrack and Goattracker 2 support different pattern length/count per channel, so that block could be overcome. |
I'm afraid you've missed the point. I'm saying the entire concept of "patterns", the "order", and a "row" are not applicable here. The channels each have their own independent speed ("ticks per row"), which can change arbitrarily. They each have independent "loops", and "subroutines", and "loops nested inside of subroutines", and "subroutines nested inside of loops", and independent total durations, and independent "starting points" to loop back to at the end. They have no clear and obvious points of separation between so-called "patterns". Each channel is just a massive sequence of commands+notes. The channels are so utterly desynced from each other that many, many sacrifices would have to be made to create anything resembling a tracker view; to the point that it would be barely any better than a text editor. The amount of effort to create a GUI for such a view is very obviously not worth it. You could imagine an *.asm song file that is so well structured that it uses a bunch of subroutines (the "patterns") and uses a long list of calls (the "order") to arrange the subroutines, but this editor seeks to support all valid pokecrystal *.asm song files. |
The text was updated successfully, but these errors were encountered: