opmo

This is how all functions work - with span or trim build in.

I will make the octave-map function work with octaves numbers as well. (octave-map '(c3 cs3 e5 f5 fs6 g5 gs4 a4 as3 b3) '(c3 d3 e3 f3 g4 f4 e4 d4 c4 cs4)) => (c3 d3 e5 f5 g6 f5 e4 d4 c3 cs3) (octave-map '(3 3 5 5 6 5 4 4 3 3) '(c3 d3 e3 f3 g4 f4 e4 d4 c4 cs4)) => (c3 d3 e5 f5 g6 f5 e4 d4 c3 cs3)

At the moment you can't convert musicxml file into omn score. But it is in our TODO list.

I have some idea how we could do that - possibly next week.

It is a new function which generate a variations of a given score or section. The function has around 20 keywords and is not yet ready for release.

Variations on "Webern Variationen Fuer Klavier Op.27, I" (2019) by JP Instrument: VSL Steinway D

Dear Timothy, Lets delete some folders and files from the Library folder. 1. Quit app. 2. Go to Library/Preferences folder and delete the com.opusmodus.Opusmodus.plist file: 3. Go to Library/Caches folder and delete the com.opusmodus.Opusmodus folder: 4. Start Opusmodus app 5. Create a new workspace Let me know if the app is still crashing. best, Janusz P.S. To play with the CLM please use the CLM.opmo file which you find in the Library panel '3. HowTo Score/Sound Synthesis' folder: As well the 3 files in '5. Sound Synthesis' folder: The CLM folder should not be used. There are some clm instruments which may course crash. With the time we will add more clm instruments with OMN form.

What macOS you are running. What course the crash ie. closing a window, evaluation etc... I need more information in order to reproduce the crash.

Whats new in version 1.3 Compatibility with macOS Mojave 
macOS 10.14 Dark Mode 
CLM added
 OSC added 
MIDI player improvements New functions: binary-to-attribute merge-attributes circle-pitch-plot
 circle-rhythm-plot xy-plot pcs-rhythm
 edit-events find-max-span fit-to-span
 gen-osc-data
 osc-thread 
stop-osc-threads Enhancements and fixes: quantizer returns now the count of given length-notes single-events returns given type don't join dissimilar rests fixed rest grouping fixed tied 8va or 8vb tuplets Installation: There are some changes to the Opusmodus user system folder. Before opening the new application you need to delete the old Opusmodus folder. Make sure you save your personal files (scores, docs etc...) before. A good solution is to rename the Opusmodus folder first and then compress it. After you have deleted the Opusmodus user folder you can start the new application. At the start Opusmodus will ask you for permission to create a new user folder in your home directory, if you don’t see a window for it, it means the old folder is still on your computer. Make sure the new Opusmodus folder is installed in your home directory. New Opusmodus folder: Upgrade: Opusmodus 1.3 requires a new serial number to run. When purchasing upgrade 1.3 the current user will need to provide an Opusmodus 1.2 serial number. After the confirmation which takes a few seconds only, you will be redirected to the purchase page. Following the purchase a new serial number will be sent to you by email. Happy New Year 2019 Yours, Janusz Podrazik

Delete the source code of the DOUBLE function from the 'User Source.opmo' file.

Just delete the function double for the Opusmodus Extensions folder, the function is just an example.

The function name length-rest-weight has changed to length-weight. I fixed the score of above as well.

This will be fixed in ver. 1.3

The midi channels should to be the same in each score.

You will find the answer in the Stephane score "DseExta.opmo" in the 4. Score Examples/Strings and Piano.

GEN-AMBITUS-SERIES - expanding and narrowing

OSC is build in version 1.3

I would need a few examples, input and output to see how could this work in our system.

Upgrade/crossgrade from Symbolic Composer to Opusmodus is the price of the academic licence.

(setf sequence '((t s t) (3q 3e_s. t) (5h 5h 5q_7q 7q 7q 7q 7q 7q 7q_5q 5h 5h) (t s._3e 3q))) (gen-retrograde sequence) => ((t s t) (t s._3e 3q) (5h 5h 5q_7q 7q 7q 7q 7q 7q 7q_5q 5h 5h) (3q 3e_s. t)) best, JP

Will be fixed in the next update. The problem not the ratios but the tied lengths. What we need to do is to reverse the order of tied lengths: 5q_7q = 7q_5q

With EDIT-EVENT (ver1.3) function you will be able to edit any parameter in any given bar: (edit-event '( (0 0 '(pitch-transpose 12 x) :pitch) (0 2 '(chord-inversion 2 x) :pitch) (0 3 '(pitch-variant x :variant 'i) :pitch) (2 1 '(chord-inversion 1 x) :pitch) (2 2 '(chord-inversion 1 (pitch-transpose 12 x)) :pitch) (3 1 '(chord-inversion 1 (pitch-transpose 12 x)) :pitch) (3 2 '(chord-inversion 2 x) :pitch) (3 3 '(chord-inversion 2 x) :pitch) (3 5 '(chord-inversion 4 x) :pitch) (3 6 'g3e4c5 :pitch) ) '((e c2 c3e3g3 c3e3g3 c3e3g3) (e f2 c3f3a3 c3f3a3 c3f3a3) (e e2 e3g3c4 e3g3c4 e3g3c4) (e gs2 e3b3 e3b3 e3b3 g2 d3g3b3 d3g3b3 d3g3b3))) => ((e c3 mf c3e3g3 g3c4e4 c3gs2f2) (e f2 c3f3a3 c3f3a3 c3f3a3) (e e2 mf g3c4e4 g4c5e5 e3g3c4) (e gs2 mf b4e5 e4b4 e4b4 g2 g4b4d5 g3e4c5 d3g3b3))

Will look into it.

There are limitation with text attributes in the music-xml script espacially with more than two layers. Chord symbols are manly for popular music and should not me proceed if you wish to display them in the score.

The chord symbols are fixed. You find the list of chord symbols in the chord-library doc. (setf harmpath '((h (b3 maj7) (d3 7)) (h (g3 maj7) (bb3 7)) (h (eb3 maj7) (eb3 maj7)) (h (a3 m7) (d3 7)) (h (g3 maj7) (bb3 7)) (h (eb3 maj7) (gb3 7)) (h (b3 maj7) (b3 maj7)) (h (f3 m7) (bb3 7)) (h (eb3 maj7) (eb3 maj7)) (h (a3 m7) (d3 7)) (h (g3 maj7) (g3 maj7)) (h (cs3 m7) (fs3 7)) (h (b3 maj7) (b3 maj7)) (h (f3 m7) (bb3 7)) (h (eb maj7) (eb maj7)) (h (cs3 m7) (fs3 7))) My display: