search

m0j0hn / editor-on-fire

Automatically exported from code.google.com/p/editor-on-fire
Other
0 stars 0 forks source link

Export Chart As XML for Use In Other Rhythm Games #259

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Thought it would be neat to support exporting a song chart in a text-based 
format that can help people making rhythm games make use of EOF's syncing 
abilities. I have already used something like this for a prototype rhythm game 
of my own. I think it would be useful to others looking to make rhythm games.

Original issue reported on code.google.com by xander4j...@yahoo.com on 1 Dec 2012 at 5:43

GoogleCodeExporter commented 8 years ago 
Sounds fine to me.  If it was just export, it would be extremely easy to throw 
together.  Importing the format would take some more effort.  Let me know if 
you come up with some prototype formatting, I can give it a look.  XML is 
probably a pretty suitable format, each note can have an entry specifying 
position, length, gems present, and any special statuses.  There are tons of 
statuses though, so it would probably have to just specify a STATUSNAME="1" for 
the statuses that are present for the note, otherwise there would be dozens of 
STATUSNAME="0" entries for each note that would just bloat up the file size.

Original comment by raynebc on 3 Dec 2012 at 4:40

GoogleCodeExporter commented 8 years ago 
I am looking into suitable formats. I am kind of reluctant to use XML since it, 
being a markup format, is not intended for such a purpose. I am going to look 
into YAML and see where that leads me.

Import of this type of file is not going to be a priority. The person that 
exports this type of file also has the .eof file to work with. If a person 
makes content for game in this format and they intend someone else to be able 
to modify their work, they can distribute the .eof project file as well.

Original comment by xander4j...@yahoo.com on 3 Dec 2012 at 6:14

GoogleCodeExporter commented 8 years ago 
I wrote a bunch of XML parsing functions to support Rocksmith's XML format, in 
case this helps with deciding what type of format to go with.

Original comment by raynebc on 25 Apr 2014 at 10:49

GoogleCodeExporter commented 8 years ago 
I've changed my mind on this feature. I have a library in the works called 
Rhythm Toolkit which will allow importing, modifying, and exporting 
audio-synced event data. It will primarily be a MIDI importer/exporter library 
with utilities for adding, editing, and removing events. It could easily have 
support for importing and exporting of other formats as well, if that kind of 
functionality is desired.

It currently imports MIDI files and stores the information in a convenient data 
structure with real-time information along with the original MIDI timing 
information. Editing and exporting will be fairly easy to implement using a few 
utility functions. I'm not focused on that at the moment, though.

I think it makes more sense in the long run to do this instead of creating a 
new format. The thing I wanted to do was to have a way to get sync information 
from EOF to whatever project I am working on that requires it. MIDI is not 
ideal, but it is a nice standard and this library will hide the complexity of 
dealing with the format.

This library will be open source, but I want to finalize the API before I 
release it into the wild.

Original comment by xander4j...@yahoo.com on 27 Apr 2014 at 3:21

GoogleCodeExporter commented 8 years ago

Original comment by xander4j...@yahoo.com on 19 Aug 2014 at 3:41