m0j0hn / editor-on-fire

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

Improve BRE functionality #237

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
As requested here:
http://www.fretsonfire.net/forums/viewtopic.php?f=11&t=32725&p=578104#p578102

I agree that this could made easier if notes authored in the BRE tab are 
automatically made 5 note chords.  This would probably be as easy as updating 
the note creation logic to force a 5 lane bitmask if the BRE difficulty is 
active, and updating the fixup logic to force all notes in the BRE difficulty 
to be 5 note chords.

It could also be useful to automatically prompt the user if a BRE phrase in 
PART DRUMS is a drum roll or a BRE, or make it a toggle-able option that is 
stored as a phrase status flag.  During MIDI export, the appropriate big rock 
ending text event will be exported.  This would be an improvement not only 
because it's easier for the user, but it would allow for BRE's to be authored 
when they don't start exactly on a beat marker.

It might even be worth adding 2D and 3D rendering of BRE phrases.  At least for 
drum rolls, it will make it easier to keep track of them during the authoring 
process.  All of the 2D fretboard area is currently allocating for displaying 
trill/tremolo, star power and overdrive phrases, but the unused background area 
of the editor window could be rendered in a color other than gray (render 
before the fretboard is drawn so that it is visible in the fretboard area where 
possible).

The 3D rendering could be made to resemble Rock Band or FoFiX.  BREs have 
phrase rendering in all 5 lanes, and drum rolls have a light colored fret board.

I have uncommitted additions to EOF's manual for creating big rock endings and 
drum rolls that will be added soon, but new documentation would be needed to 
accommodate for any above-mentioned improvements added.

Original issue reported on code.google.com by raynebc on 12 Feb 2011 at 9:46

GoogleCodeExporter commented 9 years ago
Google Code glitched and double posted this issue.

Original comment by raynebc on 13 Feb 2011 at 3:25