Jump to content

NagyMusic

Members
  • Posts

    99
  • Joined

  • Last visited

Posts posted by NagyMusic

  1. What is the main difference between pitch-repeat2 and pitch-repeat3 functions? 

     

    I'm testing various examples and notice that the first two parameters in pitch-repeat2 are low and high integers; in pitch-repeat3 there's only one parameter, count, which can be expressed as a single digit or a list. When the count is represented as a list, it produces a similar output of randomized high and low counts, similar to pitch-repeat2.

     

    Any other comparison observations or differences between these two functions?  Thank you!

  2. I'm studying the pitch-segment-variant and noticing when the :segment argument includes a list, it doesn't seem to generate but the number of segments represented by the first digit in the list.

     

    (setf bach (attribute-series '(leg 8)
                                 '((s g2 d3 b3 a3 b3 d3 b3 d3) (g2 d3 b3 a3 b3 d3 b3 d3))))

     

    (pitch-segment-variant
     bach :size '((20) (30) (40) (100)) :segment '(1 2)
     :position '? :variant '? :transpose '((0) (6)) :initial t)
    => ((s g2 leg d3 leg b3 leg a3 leg b3 leg d3 leg b3 leg d3) (s a3 leg b3 leg) (s g2 leg d3 leg b3 leg a3 leg b3 leg d3 leg b3 leg d3) (s f4 leg f4 leg))

     

    However, when the :segment argument calls for the same number of segments, those are generated correctly:

     

    (pitch-segment-variant
     bach :size '((20) (30) (40) (100)) :segment '(2)
     :position '? :variant '? :transpose '((0) (6)) :initial t)
    => ((s g2 leg d3 leg b3 leg a3 leg b3 leg d3 leg b3 leg d3) (s d3 leg b3 leg) (s b3 leg a3 leg) (s g2 leg d3 leg b3 leg a3 leg b3 leg d3 leg b3 leg d3) (s f4 leg f4 leg) (s gs3 leg f4 leg))

     

    I expected the :segment '(1 2) [randomly] to alternate between 1 and 2 segments. Could anyone explain why that is not the case? Thank you!

  3. A quick comment on my post earlier post.

     

    When using the attribute-series function, the last dyad is not omitted, and the ped marking is attached and displayed correctly if there's a rest in the last measure. However, when there's no rest at the end of the last measure, the ped marking is not attached.

     

     

    (setf mat '((q c4 e3e4) (q g3 c3c4 h e4) (q c4 g4 e4e5)))
    (attribute-series '((- 1) (ped 2) (ped 4) (ped 2)) mat)
    => ((q c4 mf e3e4 ped) (q g3 c3c4 ped h e4 ped) (q c4 ped g4 e4e5))
    
    (setf mat.r '((q c4 e3e4) (q g3 c3c4 h e4) (q c4 g4 e4e5 -q)))
    (attribute-series '((- 1) (ped 2) (ped 4) (ped 2)) mat.r)
    => ((q c4 mf e3e4 ped) (q g3 c3c4 ped h e4 ped) (q c4 ped g4 e4e5 ped -))

     

  4. There appears to be an issue in omitting dyads (chords) in the notation viewer when attaching attribute 'ped, as in this example:

     '((q c4 e3e4 ped) (q g3 c3c4 ped h e4 ped) (q  c4 ped g4 e4e5 ped))

    Similar issues occur when using the attribute-series function:

    (setf mat '((q c4 e3e4) (q g3 c3c4 h e4) (q c4 g4 e4e5)))
    (attribute-series '((- 1) (ped 2) (ped 4) (ped 1))  mat)

     

  5. I was able to attach the pedal to every measure:
     
    (setf mat '((q c4 e3e4) (q g3 c3c4 h e4) (q c4 g4 e4e5)))
    (setf counts-notes (get-count (omn :pitch mat)))
    (setf att (gen-repeat (length counts-notes) '(ped)))
    (setf ped-series (mclist att counts-notes))
    (setf mat-ped (attribute-series ped-series mat))

     

    I still can't figure out how to filter the particular notes (only two-note octaves - chords?) I want to attach the attribute too. Thanks again!

     

  6. I have two brief examples taken from a piano piece.

     

    In the first one, I'd like to attach the piano pedal marking on every octave, hold it and reattach at the next octave.

     

    (setf ex1 '((-q a2a1 a2a1) (-q a3a2) (-wq q b2b1) (-wq q b2b1) (-q a2a1 - g3g2) (-q f3f2 a2a1) (q f3f2) (q f2f1) (-wq q f3f2) (-q g2g1) (-q g2g1 - g2g1) (-q f2f1 e3e2) (-q f2f1 d3d2) (-w q d3d2)))

     

    In the second, I'd like to attach the piano pedal on every octave - not single pitches - and hold it until the next octave appears, and reattach it again.

     

    (setf ex2 '((-q) (q g4 mp -) (q a4 mp - a4a3) (q cs4 mp - cs4cs3 -) (q f4 mp - f4f3) (q f4 mp - f4f3 -) (q e4 mp - e4 - e4) (-q) (q d4 mp - d4 -) (q e4 mp - e4e3) (q fs4 mp -) (q b4 mp - b4b3) (q b4 mp - b4 -) (q g4 mp - g4g3)))

     

    Would anyone be willing to show me how to do that? Many thanks!

  7. Would it be possible to revise the pitch-variation function so that one can use lists of parameter values also for the repeat and step values? I noticed the functions accepts lists only with the size parameter.

     

    Thanks again!

  8. I'd like to know why I can't seem to process this list of chords using the pitch-variation function.

     

    Thank you!

     

    (setf chords '((h a2a3c4 c4a3a3) (h d4f3g2 f4g3d4) (h e4c4a3 c3a3e4) (h d3a3f4 w f4d4a3) (h e2e3g3 g3e4e4) (h a3f4e4 f2e3a3) (h e4g3b3 b3e3g2) (h a2d3fs2 w fs2a2e2) (h a2e3c4 c4a3e4) (h e4g3b3 b3e3g2) (h f2e3a3 a3f4e4) (h e4e4g3 w g3e3e2) (h d3a3f4 f4d4a3) (h e4c4a3 c3a3e4) (h b2a3d4 d4b3a3) (h a3a3c4 w c4a3a2)))
    
    (pitch-variation 0 1 7 chords
                     :type '? :seed 23)

     

  9. Thank you! I appreciate you pointing me in the right direction. The issue was with the triplet: enclosing it into a parenthesis helped. 

     

    (setf elvis (gen-repeat 2 
                '((h f4 c5)
                 (h f4 -q e g4 a4)
                 (h bb4 a4)
                 (h g4 -q -e c4)
                 (h d4 e4)
                 (h f4 (3h g4 a4 bb4))
                 (h a4 g4 w f4)
    )))

     

  10. I'm studying the Orchestral Example code from Opusmodus documentation. After changing the original melodic source (setf solo => setf elvis), compiling solovar1 and solovar2 functions produce error messages more than half the time. Does anyone know how to fix that? Thank you!

     

    ;;; MELODY
    ;; Basic melodic material                  
    (setf elvis (gen-repeat 2 
                '((h f4 c5)
                 (h f4 -q e g4 a4)
                 (h bb4 a4)
                 (h g4 -q -e c4)
                 (h d4 e4)
                 (h f4 3h g4 a4 bb4)
                 (h a4 g4 w f4)
    )))
    (setf frag1 (gen-loop 14 (list (rnd-pick '(2 3 1 4)) (rnd-pick '(2 3)))))
    (setf frag2 (gen-loop 14 (list (rnd-pick '(2 3 1 4)) (rnd-pick '(2 3)))))
    ;; Melodic variations
    (setf solovar1 (gen-fragment frag1 elvis))
    (setf solovar2 (gen-fragment frag2 elvis))

     

    Here's one of the error messages: 

    Error: Function nthcdr expected a non-negative integer, got -1.
      1 (abort) Return to top loop level 0.
    Type :b for backtrace or :c <option number> to proceed.
    Type :bug-form "<subject>" for a bug report template or :? for other options.

     

  11. Thanks for the quick reply and advice.

     

    I'm fine using PS for quick preview with GM instruments. I'd just like to know why I couldn't use PS with ports now. Could I have the wrong setup? I remember it worked before. Also, is it necessary to include a :port line within the PS block?

     

    I have created my def-instrument-set for logic (see attached). The file is in Def-Libraries => Def-Instrument-Sets directory. 

     

    Thanks again!

    logic.lisp

  12. I just started working with Opusmodus 3 and noticed that preview score playback might work differently, at least on my end. 

     

    Using the custom sound sets via Logic works when evaluating individual code snippets and def-score blocks. However, when evaluating ps blocks in the same context produces this error message:

     

    OM 8 > audition-musicxml-omn-snippet
    Error: OMN Parse Error: fail
      1 (abort) Return to top loop level 0.
    Type :b for backtrace or :c <option number> to proceed.
    Type :bug-form "<subject>" for a bug report template or :? for other options.

     

    I attached the screenshots of Opusmodus Audition Preferences and a code excerpt. I have a custom logic.lisp file in Def-Instrument-Sets folder, which I thing it's fine given that the snippet and def-score playback work just fine. I'd gladly provide more information if needed.

     

    Thank you for your help.

     

    Zvony

    Screenshot 2022-12-20 at 9.31.20 AM.png

    Screenshot 2022-12-20 at 9.31.39 AM.png

×
×
  • Create New...

Important Information

Terms of Use Privacy Policy