opmo

New:Don't deselect text on Evaluate Expression - selected snippets or expression will stay selected after evaluation.

There is no ebook version for this book.

The first thing you need to do is to create a source file (.opmo or .lisp). Give the file a name eg. Custom functions.opmo. This file will now be the source file for your functions, make sure the functions are working and that there are no errors. Save the file into the ~/Opusmodus/Extensions folder. The next step is to document the functions that you have created. Go to the ~/Opusmodus/System Library folder and create a new folder for example Custom Function. This folder is where you will place your (TextEdit) .rtfd system library documents (the best way to create a new document is to copy the contents of one of the System Library’s documents and paste it into the newly created .rtfd file). Now replace the function name i.e. variables, values etc… with your own examples and documentation. Each function must have its own document. Place the documents into the ~/Opusmodus/System Library/Custom Function folder. The last step is to create a new file that must be named contents.opmo and place it into the same folder. The form of the contents.opmo file should be written as follows: ;;; Custom functions (foo1 "here you write short note about the foo1 function") (foo2 "here you write short note about the foo2 function") The next time you start the application you should be able to use and see your function documents in the ’System Library’ utilities panel.

GEN-LOOP (macro) produces some warnings therefore is better to use GEN-EVAL (function). (gen-eval 4 '(rnd-sample 4 '(1 2 3 4 5))) But you can use GEN-LOOP as well :-) (gen-loop 4 (rnd-sample 4 '(1 2 3 4 5)))

Not at all.

Opusmodus 1.1.17350 has addressed and fixed the problem.

New: Additional 'Meter' option to MIDI to Score dialog window. 'Meter' set to NONE will create just one OMN list for each instrument - without bar lines. This option will help you to get the original performance from a MIDI file into an OMN script (especially MIDI files with many overlapping notes crossing the bar lines).

The docs are protected but you can change the font size for a particular doc with contextual menu... for the time of the display.

Congratulation, the first score in a new system is always the most difficult. Great work and great sound.

Please send the score and the midi file to me by email directly.

Please send me the midi file and the score there file is producing.

Fix to french contextual menu. New: Hertz conversion functions and HARMONIC-SERIES - with thanks to Alain Jacomet. Minor document corrections.

The Z length symbol is valid OMN symbol and it is part of the grammar. I will add a document for the Z length soon and will explain how it works. Thank you for remained me.

Here it is: (setf pitch (integer-to-pitch '(0 1 2 3))) (tonality-map '(major :root c4 :shift t) pitch) => (c4 d4 e4 f4) (tonality-map '(natural-minor :root c4 :shift t) pitch) => (c4 d4 eb4 f4)

Thank you Alain for the harmonic series function, I will add them to the forthcoming update with some extended functionality. At the moment I am playing with the spectral composition tools and the missing Hertz conversion tools have been added to Opusmodus already.

First form with value and length-note alignment: 52 (rnd-sample 100 '(23 45 12 89 94 2 57 21)) cc 52, a loop, with each value aligning to a length-note. Second form with length span: 9 '((4 1) (3 1/2) (65 1/2)) cc 9, value 4, length span 1 cc 9, value 3, length span 1/2 cc 9, value 65, length span 1/2 51 (:asc 34 127 1/32 5) cc 51, ascending from 34 to 127 with a resolution of 1/32 length in a span of 5/1

Explanation 45 '((78 1/2) (3 3) (32 1/2)) cc 45 with value 78 with a 1/2 length span. cc 45 with value 3 with a 3/1 length span. cc 45 with value 32 with a 1/2 length span. I am preparing a new document which will explain the controller syntax with new a function GEN-CONTROLLER.

You find all the answers in the HOWTO SCORE documents. Please check the 'Controllers 1.opmo' and 'Controllers 2.opmo' document.

Possibly in version 1.2 Achim Bornhoeft as well has suggest the same thing.

Update 1.1.17262 - MAKE-OMN now correctly handles plists with :rest-articulation.

Thank you Stephane, great work.

In this expression we have crescendo from pp to ff - grammar wise the OMN is correct, therefore there should be no error and I don'e see any. (setf piano-rh '((s f5 ffff t e4 = = = = s f4 pp t f3 <) (t f3 < t f4 < t f4 < e f3 < trem) (e g2 ff s f5 ppp s g6 sfz stacc f3 mp))) I have no idea where the error is coming form as we do not have any diminuendos (>) in the expression above. Is it possible you evaluate some other expression?

I can't reproduce any of that. Please give me a call on Skype. Name: opusmodus

The expression is correct and I don't see any error in notation or audition. (setf piano-rh '((s f5 ffff t e4 = = = = s f4 pp t f3 <) (t f3 < t f4 < t f4 < e f3 < trem) (e g2 ff s f5 ppp s g6 sfz stacc f3 mp))) You could test the expression with midi-display. Test: 1. Addition the expression (snippet). 2. Notation snippet. 3. Choose 'Last Score-> Play' from the Tools menu or ⌃⌥⌘P as for this: '((s f5 ffff t e4 = = = = s f4 pp t f3 >) (t f3 > t f4 > t f4 > e f3 > trem) (e g2 ff s f5 ppp s g6 sfz stacc f3 mp)) Attempt to diminuendo from pp to ff make no sense. The composer need to take care of that, naturally Try this: '((s f5 ffff t e4 = = = = s f4 pp t f3 >) (t f3 > t f4 > t f4 > e f3 ppp trem) (e g2 ff s f5 ppp s g6 sfz stacc f3 mp))

Thank you for the report. Investigating.