Jump to content


  • Content count

  • Joined

  • Last visited

About EAIP

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender

Recent Profile Visitors

1,330 profile views
  1. Hi, I was wondering how to get an octave treble clef and the correct transposing notation when writing for guitar. At the moment my def-score look like this: (def-score Crossing_Waves (:key-signature 'chromatic :time-signature timesigs :tempo 72 :layout (guitar-layout 'inst)) (inst :length lengths :pitch pitches :velocity dynamics :channel 1 :sound 'gm :sound 'acoustic-guitar-nylon) Notation is in treble clef in one system as it should, but as sounding pitch without the 8 under the treble clef. Kind Regards, Erik
  2. Playback problem

    Sorry about the noise, I've solved the problem! Kind Regards, Erik
  3. Hello, I recently upgraded to Sierra, and somehow the default playback mechanism stopped working. When trying some basic examples in OM there is no sound. Any suggestions as to where to begin troubleshooting? I'm on Version 1.2.22101M. Kind Regards, Erik
  4. Dim al niente

    Hi, The following OMN script gives the notation below. Is it possible to make the diminuendo end with niente as well, while keeping the visual appearance – the length – of the dim? Kind Regards, Erik '(q a4 0< b4 pp> -q)
  5. Hi, In the following code the mf of the first bar won't show up. Any other dynamic symbol in the first bar will work as expected. Are you able to reproduce this on your system? All the best, Erik (setf omn (make-omn :length '((1/8 1/8) (1/2 1/2) (1 1)) :pitch '((g4) (d5) (f5)) :velocity '((mf) (f) (mf)) ) ) => ((e g4 g4) (h d5 f d5) (w f5 mf f5)) ; no dynamic symb in first bar! (setf omn (make-omn :length '((1/8 1/8) (1/2 1/2) (1 1)) :pitch '((g4) (d5) (f5)) :velocity '((pp) (f) (mf)) ) ) => ((e g4 pp g4) (h d5 f d5) (w f5 mf f5)) ; now the dynamic symb shows up in the first bar!
  6. Missing hairpin?

    Ok, thanks, I really appreciate the effort that you put into customer support. I enjoy using OM a lot, it's a fantastic piece of software.
  7. Missing hairpin?

    Thanks for the quick reply, The third suggestion is what comes closest to what I'm looking for, but I want the second hairpin to start immediately on the first note (connected to the mp, not 1 note later). Is that possible? My first hairpin ends on a velocity symbol, I just want it to continue directly: ((e d4 f> > > >) (e d4 mp> > > > pp -)) (Notation from Sibelius). The playback effect of my code works just as intended. /Erik
  8. I've encountered some unexpected behavior of an OMN-script, maybe I'm missing something? The following code gives the intended result: (e d4 mp> > > > pp -) But in the following context using exactly the same OMN-script (second bar) the hairpin won't display: ((e d4 f> > > >) (e d4 mp> > > > pp -)) Both bars playback as intended though. /Erik Opusmodus 1.1.17944 OS X 10.9.5
  9. Yea, I think it could be useful, especially in more elaborate situations where a calculation in one param depends on the result of a calculation in an earlier param. The code in my example above obviously doesn't work, it was only meant to clarify what I'm talking about. :) In my current work for ex, I would like to know how many bars is generated in the :length param and then generate the same amount of bars in the :pitch param. Of course you could do that before make-omn, but it would be really convenient to be able to access the result of an other parameter from within the make-omn.
  10. Hi, A general question: Is there anyway to backward access a parameter within make-omn? (like Pkey within a Pbind in Supercollider) Something like this: (make-omn :length '(e e e e e) :pitch (list (integer-to-pitch (length :length))) ) => (e f4 f4 f4 f4 f4) Allt the best, Erik
  11. Hello, Yes, LENGTH-ADJUST applied to the sum of several bars of length values. Maybe something like the :sum key in GET-SPAN set to t. The optional :type and :position as found in LENGTH-ADJUST would then give the following possible results for :type 'r :position '? start => ((-3/16) (1/32 1/16 3/32) (1/32 1/16 3/32) (1/32 1/16 3/32)) end => ((1/32 1/16 3/32) (1/32 1/16 3/32) (1/32 1/16 3/32)(-3/16)) outer => ((-3/32) (1/32 1/16 3/32) (1/32 1/16 3/32) (1/32 1/16 3/32) (-3/32)) It would be nice to have the possibility to use LENGTH-ADJUST interchangeably on each sublist or on the sum of the sublists. Best regards, Erik
  12. Hi, I have a suggestion regarding LENGTH-ADJUST. When you use the function on a list of lists, each sublist is adjusted accordingly: (length-adjust 3/4 '((1/32 1/16 3/32) (1/32 1/16 3/32) (1/32 1/16 3/32)) :type 'r :position 'e) => ((1/32 1/16 3/32 -9/16) (1/32 1/16 3/32 -9/16) (1/32 1/16 3/32 -9/16)) It would be useful if you also were able to adjust the outermost list, to get the following result: => ((1/32 1/16 3/32) (1/32 1/16 3/32) (1/32 1/16 3/32) (-3/16)) I find the optional arguments type and position really useful, especially with the value '?. Maybe also add an optional key that specifies the list-level to adjust? All the best, Erik
  13. Hi, I noticed this behavior using length-adjust: (length-adjust '3/4 '(-s = = =) :type 'r :position 's) => (-h -s nil nil nil) This works though: (length-adjust '3/4 '(s = = =) :type 'r :position 's) => (-1/2 1/16 1/16 1/16 1/16) and this: (length-adjust '3/4 '(-s s s s) :type 'r :position 's) => (-1/2 -1/16 1/16 1/16 1/16) Seems as if the -s in combination with = causes the problem. I'm still on OM 1.0, maybe this behaves differently in 1.1. All the best, Erik