excln / bmsone Goto Github PK

• One has to delete and insert many bar lines to change measure in the current version.
• Easier bar line editing functionality for measure changes is desired.

• The current BmsONE cannot even interpret bmson with stop events correctly.

When I click to add a new BPM event, the toolbar to input new BPM does not appear as it should, based on the instructions of the official website:

"To edit BPM events, click on the lane next to measures bar. After placing or selecting a BPM event, a small tool bar to input BPM appears."

Currently it just places a BPM event with the same value as the initial BPM.

• The application sometimes crashes when opening another bmson, previewing a sound channels, editing events, or undo/redoing.

Currently BmsONE only allows bar divisions from a pre-defined list.
However when creating note patterns for songs with irregular timing (such as 5th, 96th, etc), it becomes very difficult to place notes accurately.
Being able to input custom bar divison would easily solve this problem.

Same implementation as discussed a few months ago.
I've put up a summary of the discussion and the implementation here: bemusic/bmson-spec#9

• Edit BGA events
• Preview BGA

A tool that lets you click+drag the cursor on the grid to place notes on every grid.
This is helpful if a sound channel is using a constant 16th arpeggio. Having to click for every single note is very tedious, click+drag is far more convenient.

BmsONE 0.1.5 crashes when you remove a keysound while it's playing back and it's on the key lane.
This doesn't happen to keysounds located on a BGM lane.

The easiest way to reproduce it is to create/edit a note on a key lane (which will play it back), then remove it during the playback. This consistently causes a crash.

Copy, paste and cut functions for better chart creation workflow.

• The current version does not load all sound data in the memory because of capacity restriction.
  • So waveform drawing is performed with cache, which contains complicated asynchronous processing and possibly a lot of bugs.
  • Sound note and channel previewing makes disk I/O.
  • The mixed sound data of a whole song is cached (called master cache), which is updated incrementally when sound notes are edited.
• For 64bit platforms, more powerful and smooth sound data processing will be possible if all sound data is loaded in the memory.
  • For example, flexible multi-channel previewing will be possible.
  • All kinds of previews will not make disk I/O.

Allow import of MIDI scores to a specified sound channel to automatically place slice notes, similar to BMHelper's "leave MIDI sequence as is"
This would be very helpful so that people do not have to figure out the positions of each sound, even more so for songs with irregular timing (such as songs with heavy piano usage)