Jump to content

Extending OMN?

Recommended Posts

Dear developers,

Following up with my previous post: more generally, can users extend the OMN language, or is this planned in future?

After all, it is impossible for a software designer to add every idiosyncratic music notation option some composer may be using (or which has been used in the past), but ideally (power-) users would be able to extend the language according to their needs. You are probably knowing better than me all those special notations that you are not yet supporting, and likely understand the need easily.

Particular important would be additional expressions. Users would likely need to define some mapping to the equivalent MusicXML markup.

I understand that adding such feature could be very tricky, just asking :-) At least adding free user-expression text might not be hard. 





Link to post
Share on other sites

The conversion from OMN to Music XML is quite complex and adding any new symbol require lot of work. Keep in mind that every attributes need to work with MIDI and notation.

The good news is that many attributes will be added soon.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Topics

    • By torstenanders
      Is there a way a way to extend an existing library? For example, for a specific composition I may want to collect a library of rhythms, melodic fragments etc., to arrange and transform these later with existing library features. Is it possible to by and by extend a library so that instead of, say, defining
      (setf rhythm1 (length-divide 1 3 '(q)))  
      I instead may write something like
      (setf (library 'new-piece 'rhythms 'rhythm1) (length-divide 1 3 '(q)))  
      Asked differently: what is the internal data structure of the existing library feature(s)? Is it possible to get access to that data for user-defined functions etc.?
      Also, is it possible to export an existing library into a file?
      BTW: Why are all these quotes necessary in calls to functions like library and many others -- why is the function library not a macro instead (only at the top-most level of course as syntactic sugar, I am certainly not suggesting to have macros instead of functions in principle).
      Thank you very much!
  • Create New...