but: some other "receiver" then REAKTOR need other DATA-formats, that's the thing, i think...

 

 

and with (send-osc-data) i didn't find a solution for that.... see post...

 

or... 

 

 

 

 

 

 

 

and with (MAKE-SOCKET... ) it was possible

it's seems so, at the moment all my OSC projects are not workiing with 3.0 (polytempo/max-player)...

the (make-socket) seems to be the problem in lispworks

😅

thx for your work - but the ports are always changed to "internal" - but you don't have to try any further, the (score player)-function (OPMO) has the same problem, will certainly be "repaired" sometime...

 

greetings

andré

 

 

thanx, that's great!!!.... there is only one problem (but you don't have to solve it for me): the port/channel-settings are deleted 🙂  so only the internal midiplayer is playing, and no other midi-destinations via preseted port/channels (in the midi-file) are possible...?

 

(i'm working on a generative-live-scoring project (open forms) and with OPMO i can generate/simulate different generative-grammars of my "musical material" (organzied/read as/from an array). so your solution would be very practical to develop and test the "form-grammar" of the work - THANX!!)

this works fine, very useful for me!

 

do you know how to read/play thus from an existing midi-library - with a path, like, perhaps

(push-to-list "/Users/..../Opusmodus/Media/MIDI/Meier/50.mid")

 

 

 

great, i will test it today!!
 

dear ldbeth

 

thanks for the solution - that's great!

 

all the best

andré

dear all,

 

i have a basic lisp-question to FORMAT and i did not find a solution...

 

INPUT

 

(setf alist '((/player "12" 1.0 1.0 1.0)
              (/player "23" 1.0 1.0 1.0)
              (/player "12" 1.0 1.0 1.0)	
              (/player "23" 1.0 1.0 1.0)))

;; with FORMAT to
=> /player "12" 1.0 1.0 1.0, /player "23" 1.0 1.0 1.0, /player "12" 1.0 1.0 1.0, /player "23" 1.0 1.0 1.0

 

by FORMAT 
=> i will save it in a TXT-file on desktop (that works (with-open-file...)), but i have a format-problems with the commatas and the ()

 

thanx for such basic-lisp-help

andré

for me too!

and thx to janusz (and the OPMO-team) for all your work and support! 🙂 

 

dear all

 

i would like to send some specific data via OSC to MAX... 

i can send "something" to max 

 

(defparameter max '(127.0.0.1 7500)) ;; that works

 

SEND data to MAX

and i would like to send the following seq to MAX by OSC 

/player "12" 1.0 1.0 1.0
 

but how to do it / format it in OMPO?

 

;; data should be "113" 1 1. 25000  => but how to "format"? -> see the MAX form
;; ???
(send-osc-data (create-osc-thread "player" max) data)

 

/player is sended but not the rest of teh sequence 

 

 

here is a screenshot from MAX, it worked with an external library (in CCL) but i would like to do it "directly" in OPMO.

 

 

in MAX, that's what i'm sending - for example - as an internal test

 

 

thanx for some help...!!

andré

"Wow, this is really disappointing. It is again showing how poor the company behind OM communicates. It seems not necassary to have an official announcement placed at the day people can use the new version. Is it too much to ask for an update note on the official webpage?" 

 

Om-Chanting on "Baroque 415Hz" could help

i don't know your datas, but.... perhaps....

 

(omn-to-measure (make-omn
                 :pitch (filter-repeat 1 (rnd-order (omn :pitch seq)))
                 :length (gen-repeat 24 tr)                                  
                 :span :length)
                '(4/4))

 

 

(filter-repeat 1 for4 :type :pitch)

Quote

Seriously? This is a one-man operation doing a major port of the software, not only to support a new hardware architecture, but also, as part of that, to completely swap out the underlying runtime backend. Give the guy a break, his job is hard enough without entitled people badgering him to get it done yesterday and criticizing his very efforts to communicate progress (before that, the criticism was that there wasn't any communication about it). What's "really going on"? Alien abduction? Coup attempt? Let the dev do his work.

yes! agree with you, just let the developer(s) work instead of making a .... here. janusz is doing a great job!!

 

no "virtualization", 

just tried it at my own risk - doesn't work well - but I have a version on my Intel Mac and can wait 🙂 

I'm testing (for fun) the M2 with opusmodus (intel, a little wobbly on silicon) - of course I still have a copy on my intel-mac, just for fun!

 

but the combination is really good. I calculate/play something in OPUSMODUS, sending by OSC to MAX/MSP and further to ABLETON LIVE; as a heavy test, the same thing in parallel to REAPER. everything with different plugins. no jerks, no glitches. That will be really great, this combination - when OPMO officially runs on silicon!

 

then PROCESSING can also run in parallel 😄

 

@opmo: thx a lot for all the special functions you have coded for me/us over the last few years, very specific/individual solutions for me, my work!!

 

 

 

 

Didn't you read this (the compatibility) when you made the update, bought a new computer? I always check that - always. Also with MaxMsp, Avid Sibelius, Pro Tools ...

 

 

 

SIBELIUS

i think AVID SIBELIUS is not yet officially ready for VENTURA either, and M1 only under the Rosetta 2 translation layer.

 

macOS 11 (Big Sur), OS12 (Monterey) and M1 Support for Avid Products

AVID.SECURE.FORCE.COM

 

Music notation software, macOS Ventura, and Apple Silicon [updated] - Scoring Notes

WWW.SCORINGNOTES.COM

---

How Sibelius, Finale, Dorico, MuseScore, and Notion are faring on Apple's Ventura operating system and Apple Silicon-powered hardware.

 

some tests/ideas

i think you should code it yourself, then you'll get what you want 😄

 

greetings

andré

 

 

an example with 2 pitches = 2 intervals, with microtonal quantification

 

(sort-asc
 (remove-duplicates
  (pitch-melodize
   (append
    (gen-summationsakkord '(3 5) :typ 'ks :gedachter-grundton 'db0 :quant nil)
    (gen-summationsakkord '(5 7) :typ 'ks :gedachter-grundton 'db0 :quant nil)))))

(sort-asc
 (remove-duplicates
  (pitch-melodize
   (append
    (gen-summationsakkord '(3 5) :typ 'gs :gedachter-grundton 'db0 :quant nil)
    (gen-summationsakkord '(5 7) :typ 'gs :gedachter-grundton 'db0 :quant nil)))))

 

 

here ist some code to generate "Summationsakkorde" (CLAUS KüHNL)... have a look to the PDF...

(from the book "Claus Kühnl: Beiträge zu einer HArmonielehre 2000" Friedrich Hofmeister Musikverlag. p.42+)

 

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;


(defun gen-summationsakkord (primaerint &key (n 10)(typ 'ks) (gedachter-grundton 'c0) (quant 1/2) (chord t))
  (let ((partial-reihe (hertz-to-pitch (harmonics gedachter-grundton 100 :type :hertz) :quantize quant))
        (partial-liste
        (remove-duplicates
          (append primaerint 
                  (list (sum primaerint))
                  (loop repeat n
                    with k-int = (sum primaerint)
                    with g-int = (sum primaerint)
                    with a = (first primaerint)
                    with b = (second primaerint)
                    
                    collect 
                    (cond ((equal typ 'ks)
                           (setf k-int (+ (car primaerint) k-int)))
                          ((equal typ 'gs)
                           (setf g-int (+ (second primaerint) g-int)))
                          ((equal typ 'fibo)
                           (shiftf a b (+ a b)))))))))
    
    (if (null chord) 
      (position-filter (x-b partial-liste 1) partial-reihe)
      (chordize (position-filter (x-b partial-liste 1) partial-reihe)))))

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

(gen-summationsakkord '(2 3) :typ 'ks :gedachter-grundton 'c2)
(gen-summationsakkord '(2 3) :typ 'gs :gedachter-grundton 'c2)
(gen-summationsakkord '(2 3) :typ 'fibo :gedachter-grundton 'c2)


(gen-summationsakkord '(2 3) :typ 'ks :gedachter-grundton 'c2 :quant nil)

(gen-summationsakkord '(3 4) :typ 'ks :gedachter-grundton 'f1)
(gen-summationsakkord '(3 4) :typ 'gs :gedachter-grundton 'f1)
(gen-summationsakkord '(3 4) :typ 'fibo :gedachter-grundton 'f1)

 

Doc - 03.08.2022 - 20-41.pdf

 

in general: you have to define exactly what you want (in a limited number of cases), if you change your idea along the way, you have to adapt the CODE again...

look at the CODE, and the EVENT etc...

 

 

;; you have to define al longer length-value in EVENT: (* 4 1/8) = 1/2 => in EVENT '(h c4e4g4b4 mf ten)

(setf event '(h c4e4g4b4 mf ten))
(gen-arpeggio* event :rhy '(1/8) :offset nil)  

 

here's a correction (bug) and a variant:

okay... you want to "sum" the rests in a sequence 0, 2 ,3, 4 ...  by -1/24 rhy. (a special version)

so i have to code this case as option. take the new version and use :offset 1

 

(defun gen-arpeggio* (event &key (rhy'(1/28)) (legato nil) (offset nil))
  (let* ((pitches (melodize (omn :pitch event)))
         (length (car (omn :length event)))
         (velo (car (omn :velocity event)))
         (art (car (omn :articulation event)))
         (rhy (gen-repeat 10 rhy))

         (arpeggio-voices (loop repeat (length pitches)
                            for i from 0 to (1- (length pitches))
                            for j in pitches
                            for rhy in rhy
                            collect (if (= i 0)
                                      (length-adjust length (list rhy j velo art))
										 (length-adjust length (append (gen-length (if (null offset)
                                                                                    (list i)
                                                                                    (list (+ i offset)))
                                                                                    (* -1 rhy)) (list rhy) (list j) 
                                                                      (list velo) (list art)))))))
    (assign-variable 'voice 
                     (if (null legato)
                       arpeggio-voices
                       (loop for x in arpeggio-voices
                         collect (length-legato x))))))
    

(setf event '(q c4e4g4b4 mf ten))

;;; now it works correct
(gen-arpeggio* event :rhy '(1/8 1/12 1/16 1/20))

(list voice1)
(list voice2)
(list voice3)
(list voice4)


;;; what makes intuitiv sense (old version/result)
(gen-arpeggio* event :rhy '(1/24) :offset nil)
;; with OFFSET nil: the rests at the beginning are: 
;; * 0 rhy
;; * 1 rhy
;; * 2 rhy
;; * 3 rhy

(list voice1)
(list voice2)
(list voice3)
(list voice4)


;;; what are you looking for...
(gen-arpeggio* event :rhy '(1/24) :offset 1)
;; with OFFSET 1: the rests at the beginning are: 
;; * 0 rhy
;; * 2 rhy
;; * 3 rhy
;; * 4 rhy

(list voice1)
(list voice2)
(list voice3)
(list voice4)

 

 

you're welcome!