|
|
Post by Ačāla on Jan 3, 2016 21:07:16 GMT
|
|
|
|
Post by djlastnight on Jan 3, 2016 21:42:31 GMT
I'm not a charter, but this work deserves a +1 karma!
|
|
|
|
Post by Ačāla on Jan 3, 2016 21:56:28 GMT
djlastnight Thank you! But I didn't write this for karma.
|
|
|
|
Post by raynebc on Jan 3, 2016 23:37:02 GMT
I'm a bit confused by the claim that .chart files have a technical capacity to store more possible notations than a MIDI could. Can you elaborate on this? Either format could support a higher number of new features than any one game could feasibly make use of. Phase Shift's Sysex message system could theoretically support an indefinite number of features (well into the billions).
The document seems to give the impression that a chart author would have to maintain multiple versions of a chart to work with different games. It's also worth mentioning that EOF has user preferences to automatically create multiple different MIDI files during save, that automatically filter out features that different games don't support (such as a Rock Band Network version that leaves out all Sysex notations that will work perfectly fine in FoFiX).
|
|
|
|
Post by Ačāla on Jan 4, 2016 1:29:47 GMT
Right, so let's just separate this out. Makes it easier on me, for once. I'm a bit confused by the claim that .chart files have a technical capacity to store more possible notations than a MIDI could. Can you elaborate on this...? Maybe next time you'd considering leaving it at the question? Adding more to the point just makes it rhetorical (like this one). ...Either format could support a higher number of new features than any one game could feasibly make use of. Phase Shift's Sysex message system could theoretically support an indefinite number of features (well into the billions). I understand that, full well. Though you may recall I also noted that a .Chart is literally a placeholder. .Charts are only there until the game, or in your case, program, decodes it, and makes it into what the game can actually use. Literally, charts are just numbers and words. As a result, text-based is superior to byte-based. At least, that's what I understand about computation. I could be completely wrong, though.The document seems to give the impression that a chart author would have to maintain multiple versions of a chart to work with different games. It's also worth mentioning that EOF has user preferences to automatically create multiple different MIDI files during save, that automatically filter out features that different games don't support (such as a Rock Band Network version that leaves out all Sysex notations that will work perfectly fine in FoFiX). I will admit, as a human who wrote this, I have a bias toward things, and against others. Also, I have yet to find the function that places the file as a GH3/GH2/KH compatible .Chart. If it does, in fact, exist, I simply never found it. But to answer this "question," we must first understand that GH3 can do things that GH2 cannot. Hence, if a .Chart is used for both, much like the different variations of .Mid that you spoke of, the base chart is, in fact, identical. Just with some minor variations. Forced Ho/Po/S would be the main one, of course. I am, of course, only human. If I didn't answer your question quite accurately, please let me know. I will update this guide if I am proven to be wrong in anything. |
|
|
|
Post by raynebc on Jan 4, 2016 5:28:00 GMT
A MIDI file could just as easily use text based instructions with text events. The chart format is quite similar to a MIDI file that has been written in text form, all the way down to the MIDI style timing. It doesn't mean that a text only format has any major exclusive benefit just because it's more human readable in its raw format.
|
|
|
|
Post by Ačāla on Jan 4, 2016 7:12:04 GMT
On that front, I see the two are so close that they are just mirror images of one another. Just Midi has more defined, as nobody (to my knowledge) has done anything on Pro Guitar, Pro Drums, or even Vocals, for .Chart. There's probably more that nobody's done, but that's not the point. The only thing I can say .Chart does superior, with this knowledge, is zero-sustain. Midi has a bare minimum of one (according to EoF), but .Chart can literally have zero. Though that probably makes absolutely no difference, outside of FoF/FoFiX. Which uses .Mid, from the old RB1/RB2 standards.
|
|
|
|
Post by raynebc on Jan 4, 2016 16:11:22 GMT
MIDI files can be encoded with zero length notes, but I doubt that is commonly done and I don't know if it actually violates any rules of the MIDI specification. I'm sure at the very least it could cause some MIDI editors to throw up when they try to load such a MIDI.
|
|
|
|
Post by Ačāla on Feb 29, 2016 2:28:53 GMT
Version 1.008 is now up.
|
|
|
|
Post by Ačāla on May 16, 2017 5:09:51 GMT
Posted update 1.009.
|
|
