opmo

Love the power here

You can define any attributes with DEF-SOUND-SET.

This need to be done is OM and musicxml level. Simply adding them to the user attribute list won't work. The ped and ped1 attributes are working. I will add the missing pedals, half-ped, sost-ped and una-corda soon after we make the display working.

Yes you can.

Every layout from the "Instrument Layout Presets" document can be used in the DEF-INSTRUMENT-SET function i.e., PS.

To get a final score in OM we use DEF-SCORE instance. The PS (preview score) function should be seen as a snippet (momentaufnahme). To add all the options etc... to PS would defeat the primary idea.

half-ped was not a part of the musicxml, therefore is not implemented in OM. ped1 is sustain for one event only.

Just use single instruments or clef's names. As for :rh, :lh (specifically) I could add this to the layout system.

New release soon. New symbol * (pedal note or pedal point) added to the counterpoint dictum: ;; Patterns (setf p1 '(q c4 ds5 d4 eb3) p2 '(e c4 cs4 d4 ds4 e4 f4 fs4 g4) p3 '(q g4 c5 e ds4 d3 ds4 c4) p4 '(5q d2 cs3 - g4 - 3q c3 - fs3 q f4 e3) ) ;; Counterpoint, methods and polyphony (counterpoint (list p1 p2 p3 p4) '(((- 1 2 3) :methods (- i r -)) ((- 4 3 *) :methods (- ri - -)) ((4 * * *) :methods (r - - -)) ((1 * 2 3) :methods (- - i -)) ((* * * *) :methods (- - - -))) :global-methods '((fl) (t12 cl) (hn) (t-12 vc)) :global-polyphony '(7 p) :iterate t :index 'vox) ;; Tempo (setf tempo-changes (gen-tempo '(44 72) '(1 2) vox1 :seed 34)) ;; Preview Score (ps 'gm :fl (list vox1) :cl (list vox2) :hn (list vox3) :vc (list vox4) :tempo tempo-changes ) best wishes, Janusz

I do like the concept of moving the sequence to the first argument.

More important you can apply the the unfold method to a specific bar or even to an event in a given bar number: Method applied to entire sequence: (unfold 'name 'method sequence) Method1 applied to 2nd bar only: (unfold 'name '((method1 2) method2) sequence) Method1 applied to the 3rd event in the 1st bar: (unfold 'name '((method1 1 3) method2) sequence) Examples: (setf mat '((s c4 d4 e4 f4 g4) (s c4 d4 e4 f4 g4) (s c4 d4 e4 f4 g4))) (unfold 'om 't7 mat) => ((s g4 a4 b4 c5 d5) (s g4 a4 b4 c5 d5) (s g4 a4 b4 c5 d5)) (unfold 'om '((t-12 1 3) (t-1 2) (r 3)) mat) => ((s c4 mf d4 e3 f4 g4) (s b3 cs4 eb4 e4 fs4) (s g4 f4 e4 d4 c4)) (unfold 'om '? mat) => ((s c4 d4 e4 f4 g4) (s g4 a4 bb4 c5 d5) (s c4 bb3 gs3 g3 f3)) Why so may users do not read/examine the function documentation.

I discovered that the default :key-signature in PS function is set to (C Major) - this is why we get the rewrite. I will change the default to 'chromatic.

(ambitus-filter '(-11 21) '((q c4ds3 e c4 c1 q d5 g9) (q c4 e d6 d6 d6 d6 c8 q d5 g9))) ((q c4ds3 e c4 - q d5 -) (q c4 -he q d5 -)) (ambitus-filter '(-11 21) '((q c4ds3 e c4 c1 q d5 g9) (q c4 e d6 d6 d6 d6 c8 q d5 g9)) :remain t) => ((-q. e c1 -q g9) (-q e d6 d6 d6 d6 c8 -q g9)) This example should help you howto to make a split.

It is not interpretation this is how the system translate integers 0 1 2 3 4 5 6 7 8 9 10 11 = c, cs d eb, e, f, fs, g gs, a, bb b. Opusmodus is not trying to interpreted archaic systems of the past (tonalities, Major, Minor etc...). You can apply them of course but it requires a different perspective. If expression (w e1 f1 gb1 e1 f1 gb1 ab1 b1) is composer intend then you will get the exact notation. For example PS function will modify the pitch names (Preview Score), the DEF-SCORE instance will not. Note: If expression is modified the system will result in default pitch names.

This is correct. any process of pitches will end with: c, cs d eb, e, f, fs, g gs, a, bb b

Me too, but this need to be addressed with Sibelius developers.

This is an old Sibelius bug with clefs.

Please make documentation for it, then we can add the chord list into the system and not Libraries.

5, 7 min is not acceptable Please send me the entier file with all the chords (compressed by email) and I will have a look.

If this library is quite big would be better to do that with table and not with functions - just with results (values). The values (chords) are fixed therefore: (setf c7mt7 '(c4 e4 g4 b4)) (setf c7mt5 '(b3 c4 e4 g4)) (setf c7mt3 '(g3 b3 c4 e4)) (setf c7mt1 '(e3 g3 b3 c4)) (setf db7mt7 '(cs4 f4 gs4 c5)) (setf db7mt5 '(c4 cs4 f4 gs4)) (setf db7mt3 '(gs3 c4 cs4 f4)) (setf db7mt1 '(f3 gs3 c4 cs4)) or (setf c7mt7 'c4e4g4b4) (setf c7mt5 'b3c4e4g4) (setf c7mt3 'g3b3c4e4) (setf c7mt1 'e3g3b3c4) (setf db7mt7 'cs4f4gs4c5) (setf db7mt5 'c4cs4f4gs4) (setf db7mt3 'gs3c4cs4f4) (setf db7mt1 'f3gs3c4cs4)

Maybe you should compile the file first and place the .dx64fsl file into the Extensions folder - for faster load.