This section is currently not maintained if you have bugs to report or feature requests to... well, request. Please try our bug tracker:

Here you will find some plans/suggestions about what could be added to MusE. Feel free to give us an impression on your ideas of what should be added. If you have already implemented your idea and if it's stable it's most likely that we include it into the current development tree for the next release which does not yet have a feature freeze.

But be careful with your modifications to the page, do not change or damage other ideas if you are not sure.

Plans for the coming release(s)

  • Visual metronome
  • Support for external control and feedback equipment
  • Make it easier to setup a basic environment (basically wrt softsynths, possibly just add a shortcut button on the toolbar.)
  • (already implemented) Keyboard shortcut to rec enable the selected track
  • (already implemented) reimplement no-audio backend to use muse as a standalone sequencer
  • (already implemented) Converter for old songs
  • Downmixing to other formats than WAV (should be possible when coming version of libsndfile is released)
  • (already implemented)VST effect plugin support
  • (in the works) add midi in/out indicator
  • (in the works) graphical viewing and editing of automation placed on the tracks.
  • (already implemented) Fix shortcut for moving between markers.
  • (already implemented) Improve import so it puts the wave at the import spot and not at the locator.
  • improve marker editor with various navigation possibilities
  • Feature to grab a bunch of notes from with an midi editor and create a new part from that (probably on the clipboard)
  • RDF support, there is a library for handling LADSPA meta data that would be good to support.
  • Support for grouping in drum editor, explanation from John Check: Just want to clarify. Hihats require monophonic behaviour(as opposed to polyphonic) as stated. When I say groups, generally I mean for convenience, such that port reassignment can be done in bunches. Of these, we can either hardcode some for psuedo-monophony or have a toggle. The grouping itself is more important that monophony. Usage example: Say you're collaborating and the other party uses a whizbang2000 cymbal emulator, which will be in the final product, but it'll be done at your place. On the day of reckoning, the other party brings their WB2k and jacks it in to your system. If we had groups "to port", we only have to make the port reassignment once.
  • (already implemented) Support for DSSI (disposable softsynth interface...if it takes of, that is)

Some wishlist items from Emiliano Grilli:

  • List editor doesn't allow me to insert arbitrary controllers (I would like to create slurs like is described in - but list editor seems not to accept controllers 100 and 101) or there is another way of doing this?
  • MIDI import/export of single tracks: I don't know how much this is diffficult to implement from the programmer point of view, but would definitely be an handy addition.
  • MIDI constraint: it would be cool in the piano roll editor if one can select say a chord or a scale from a drop down box and the relative notes are highlighed (like in jazz++ when you select a chord in the harmony browser) and the new inserted notes "snap" to that notes.
  • MIDI groove templates: I think we lack a facility to define quantization patterns, like you find in cubase for example. I guess this is not easy to do, but is worth the effort, IMHO. With such a tool an user can define a library of quantization patterns that can be exported and shared with other users, and/or included in the next versions of muse.
  • Add a button that tells if midi remote control is active and to enable/disable it.
  • (already implemented) Provide a way to start MusE without relying on Jack (or rather audio, several people have expressed interest in using MusE as a sequencer only).

Here's some information about features available in Sequencer Plus Gold from Dave Phillips

(This information is also available in it's original form from Dave's site.)

Here are the Normal Transforms from Sequencer Plus Gold :

Quantize Transpose Set Pitch Pitch
Super-quantize Harmonic transpose Adjust Quantize Start-time
Quantize duration Inversion Crescendo Velocity Velocity
Set duration Harmonic inversion Set note-off Duration Duration
Adjust duration Map Adjust note-off Modulus Merge
Retrograde Compex Track rebar
Offset Range rebar

And here are the MIDI Transforms:

Retrograde Scale Fill Accelerando
Offset Shift Crescendo Scale
Compex Invert Thin Shift
Map Elim dupes Thin
Map programs Elim dupes
Tap tempo

Edit regions include whole track or group of tracks, individual measures, and individual note, and is not restricted to measure boundaries. Alas, non-contiguous editing is not supported.

The MIDI transforms affect MIDI messages other than note-on and note-off. Sequencer Plus employed a user-designated track for tempo messages, it could be edited like any other track.

The Harmonic Xpos and Invert transforms and the Pitch randomization employ user-defined settings in a Keysig popup.

Sequencer Plus also includes advanced grouping features, multiple track recording, block editing, SMPTE/MTC/MMC support, and much more. Its drawbacks include no Undo/Redo, no graphic controller editing, and no source code. However, it is now being given away by Voyetra.

Plans (which went into) 0.7

The concepts for 0.7 where:

  • main goal for MusE 0.7 is stability.
  • The next is better audio recording / mixing and a more stable interface to software sythesizers.
  • removed score editor; the score editor was never really useful;
  • removed ALSA driver. MusE 0.7 needs JACK for operation.
  • simplified soft synth interface; less real time threads
  • new audio architecture and mixer
  • new handling of midi controller events
Powered by MediaWiki