Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I've almost finished a rewrite of the drummap-handling (right now only for
omuse, but putting it into unstable muse shouldn't be a big problem, I hope).
Inkey & outkey-mappings seem to work fine, but unfortunately the new way of
dealing with drummaps breaks backwards compatibility a bit. I'm therefore
interested in hearing what you ppl have to say about this before commiting it
anywhere. Should this fix only be applied to the unstable version of muse, or
even to the stable version as well?
Since the new deal is to store the notes and their pitches with respect to the
index in the list with instruments, the problem you'll have when opening a
song with drummaps is that they were stored with respect to the e-note. That
usually started at pitch 35 or something, and now they'll start at 1. This
means that you'll have to set up the drummaps over again and prefereably move
the instruments up to the top in the window (since they've probably been
moved down a bit, since 35 now means y-order 35). This is a bit of work, but
not impossible to fix, since the song is still possible to load.
Will this create a lot of trouble for you ppl? Would it be better to put up
patches for omuse and let people who prefer the new way download and patch up
Werner, I've noticed that it's a bit difficult right now to open songs made
with omuse in muse. Is this something that will be fixed sometime far away in
the future, or will muse and omuse projects not be compatible with each
other? Will there be different versions of .med-files (noticed that
.med-files created with both muse and omuse say muse-version 1.0)?