opmo

Thank you for the offer, I will let you know when we are close to the date (version 2.0). If you have any specific ideas - must be part or the pitch notation c4 cs4 c4+ c4- c4++ but all this is not decided yet - please send them directly to me.

Thanks for the typos and errors, just doing the corrections :-)

Thanks marqrdt for the trace.

We can use microtones in Opusmodus but they are not a part of notation. The microtonality need to work with OMN and MIDI. To implement true microtonal system we need to make first the split of midi changes to be able to play microtonal chords: (q c4+f4- pp arco d4 e4+) This is how the microtone will be coded in OMN. The example above would need a minimum 2 midi channels.

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.

Here is a simple example which illustrate the :add keyword: (tonality-map '(major :root c4 :closest down) '(c4 cs4 d4 eb4 e4 f4 g4)) => (c4 c4 d4 d4 e4 f4 g4) (tonality-map '(major :root c4 :add 3 :closest down) '(c4 cs4 d4 eb4 e4 f4 g4)) => (c4 c4 d4 eb4 e4 f4 g4)Adding the :closest keyword will stop the possible pick between the two possibilities: c4 or d4

Dear madrqdt, please send me the output of the Console.app to info@opusmodus.com Howto: /Application/Utilities/Console maybe this will give us some useful information. 1. Open the Console app 2. Open Opusmodus app 3. Select all the dx86cl64 lines and send it to me by email - info@opusmodus.com

This can take up to 24 hours.

All the Sound-Set files you will find in the Utilities, Library panel on the right, it is the 6th button L. You might need to explore more the Utilities panels, were you should find answers (examples) to many questions. Of course you can add your own sound set files into the /Opusmodus/Def-Libraries/Def-Sound-Sets folder. All files found there, will load on startup.

Please check the sound set GM file. The program numbers are 0-based. (def-score ancient (:key-signature '(c maj) :time-signature '((9 8 1) (6 4 1) (9 8 1)) :tempo 40) (oben :omn oben :channel 1 :sound 'gm :program 0) (unten :omn unten :channel 2 :sound 'gm :program 'acoustic-grand-piano))

The other way would be to create your own sound set with attributes pr0 ... pr127 and use the attribute direct in the OMN form list as if there were articulations. Example: ;; Patches, keyswitches and controllers change events. (def-sound-set VSL-Prepared-Piano :programs (:group Main pr0 (cc101 0) ;chain pr1 (cc101 15) ;double-screw pr2 (cc101 29) ;harmoinic pr3 (cc101 43) ;harmoinic-secco pr4 (cc101 57) ;foil pr5 (cc101 71) ;glass pr6 (cc101 85) ;stick pr7 (cc101 99) ;stick-roll pr8 (cc101 113) ;glissandi ) :controllers (:group Default-Settings Pitch 0 Velocity-XF 2 Volume 7 Pan 10 Expression 11 Reverb-Dry/Wet 14 Reverb-On/Off 15 Slot-XF 20 Start-Scaler 21 Master-Attack 22 Master-Release 23 Master-Filter 24 Delay-Scaler 25 Tuning-Scaler 26 Humanize 27 Velocity-XF-On-Off 28 Rsamp-On-Off 29 Dynamics-Scaler 30 :group Pedal Ped 64 Sost-Ped 66 Una-Corda 67 :group Matrix cc101 101 ) ) The OMN form: '((s cs5 p pr0 g6 mp pr6 mf pr6 -) (s cs5 f pr5 e g3 ff pr5 s p pr5) (s cs5 mp pr0 g6 mf pr6 f pr6 -) (-s cs5 ff pr0 e g3 p pr5) (s g3 mp pr5 - e cs5 mf pr0) (s g6 f pr6 ff pr6 e cs5 p pr0) (s g3 mp pr5 mf pr5 e cs5 f pr0) (s g6 ff pr6 p pr6 cs5 mp pr0 g3 mf pr5) (e g3 f pr5 s cs5 ff pr0 g6 p pr6) (e g6 mp pr6 -s cs5 mf pr0) (e g3 f pr5 -s g3 ff pr5) (s cs5 p pr0 e g6 mp pr6 s mf pr6))

Of course you could use a list of program changes: :program '(1 2 3 4 5 6 7 8 9 10 11) Here each pitch will be played by a different program.

GM sound set with program 71 (clarinet) (setf clr '((e c4 ppp< leg d4 < leg e4 < leg f4 < leg g4 < leg a4 < leg b4 < leg c5 ff) ((stacc e c4 ppp d4 < e4 < f4 < g4 < a4 < b4 < c5 ff)) ((leg e c4 ppp d4 e4 < f4 g4 a4 b4 c5 ff)))) (def-score cresc (:key-signature '(c maj) :time-signature '(8 8) :tempo '(q 120) :layout '(:treble inst)) (inst :omn clr :channel 1 :sound 'gm :program 71) )

Yes, both ways will work.

To find out the midi ports setup of your system, please evaluate the (midi-destinations) function: (midi-destinations) => ((0 . "Bus 1") (1 . "Bus 2") (2 . "Bus 3") (3 . "Bus 4") (4 . "Bus 5") (5 . "Bus 6") (6 . "Bus 7") (7 . "Bus 8") (8 . "Bus 9") (9 . "Bus 10") (10 . "Bus 11") (11 . "Bus 12") (12 . "Bus 13") (13 . "Bus 14") (14 . "Bus 15") (15 . "Bus 16") (16 . "Session 1") (17 . "Keyboard") (18 . "MIDI OUT") (19 . "UM-ONE")) There are two possible ways to assign a port. One is with the port number and the other is with the port name (a string). (instrument :omn omn-form :port 0 :channel 1 :sound 'reaktor :program 1) now with a string: (instrument :omn omn-form :port "Bus 1" :channel 1 :sound 'reaktor :program 1

Thank you very much for a detailed report. Lets see if there any error messages in Console.app /Application/Utilities/Console maybe this will give us some useful information. 1. Open the Console app 2. Open Opusmodus app 3. Select all the dx86cl64 lines and send it to me by email - info@opusmodus.com Thank you for your time and your help.

You could do something like that: (gen-filter-change (rnd-sample 24 '(gs4 e4 d4 c4 c4 a4 fs4)) '(1/16 1/2 1/4 1/4) '(pp ff mf))or (gen-loop 12 (gen-filter-change (rnd-order '(gs4 e4 d4 c4 c4 a4 fs4)) '(1/16 1/2 1/4 1/4) '(pp ff mf)))etc...

Using PERMUTE function here, is not what you should do. Seven elements to permute will produce overload or will take looooong time.

The warnings from cdb-open are expected. They are not causing the application to fail to launch. Here are some suggestions: You could open the /Applications/Utilities/System Information.app, choose Save... from the File menu and attach the output file here. Maybe something there would provide a hint about what is going wrong. Have you create a new account on your system, and trying using Opusmodus.app from the new account. If you download Clozure CL.app from the Mac App Store, does that work?

We need backtrace from the AltConsole. Could you download the new version 1.0.15670 and check again, this time with AltConsole. The direction 'Howto' you fined in the previous post.

Thank you, this will help.

Opusmodus ver. 1.0.15670 is ready for download. I have added AltConsole application to the system which should help us to find the problem with the installation. 1. Open Opusmodus 2. Look for AltConsole application in your Dock. 3. Click on it. 4. type :b 5. then press the return key Copy the content of the window and send it to me. This way we might find the problem why you can't install the software.

One other possibility would be to do this: 1. open a terminal window 2. cd /Applications/Opusmodus.app/Contents/MacOS 3. ./dx86cl64 then copy the output of the terminal window and send it to me.

Thank you for the post and successful installation on Mac Pro running Yosemite. austinkool94, could you tell on what mac (model) you tried to make the installation? What OS version you are using 10.10 or 10.10.1 What I will make update to Opusmodus and will add a console, this way I hope we will see some kind of error message in it.

Very strange, this is the first time we hear about this kind of problem. I will ask my colleagues to hear what they think about this.