Jump to content

Stoney

Members
  • Posts

    28
  • Joined

  • Last visited

Posts posted by Stoney

  1. The brand-new Big-Sur Opusmodus 2.2 won't launch. Instead, I get an alert that it's "damaged", and buttons Cancel and Move to Trash. I DL'd it twice, tossed the prefs, cache, and Opusmodus folder, restarted Mac. No go.

     

    Unlike the previous version, the .dmg is named only "Opusmodus", rather than Opusmodus_Big-Sur". I'm wondering if the wrong installer was connected to the Big Sur download button.

     

    I reinstalled V2.1.26285, and it works fine.

     

    Any ideas?

  2. Is there a way to move an activation of OpusModus to another computer temporarily? I'm about to leave for a week vacation, and would like to be able to use OM on my laptop during that time. I have it activated on two other Macs now, but would like to deactivate one so that I can activate it on my laptop.

    I guess this isn't a problem this time, since the demo is for 30 days. I'll just use that this time.

     

    I appreciate the long demo time!

     

  3. In the video "Opusmodus Parametric Composition" by Jorvd, from 2019-12, at 11:10, he demonstrates using harmonic-path to combine a melody and chords. I entered this code to match the video, and it didn't work for me. Here's what he showed:

    (setf chords '(c3g3c4ds4 gs2f3c4d4 c3g3c4ds4 gs2f3c4d4
                   c3g3c4ds4 d3g3b3f4 c3g3c4g4 d3f3c4gs4
                   ds3g3c4g4 cs3g3as3f4 ds3a3c4fs4 fs3a3c4ds4
                   c3g3c4ds4 g2g3b3d4 gs2f3c4d4 b2d3f4
                   c3g3c4ds4 f3gs3c4d4 g2g3b3d4 c3ds3g3ds4
                   as2e3g3g4 f2f3c4gs4 g2g3b3d4 cs3g3as3f4
                   b2g3d4g4 c3g3c4ds4 f3gs3c4f4 g2g3b3d4
                   gs2ds3c4gs4 gs2ds3c4gs4 as2as3d4f4 ds3as3ds4g4
                   d3f3b3f4 c3g3c4e4 f3gs3c4f4 g2g3c4ds4
                   g2g3b3d4 c3ds3g3c4 c3ds3g3c4))
    
    (setf instrument1 (gen-repeat (length chords) '(s g4c4 c4 g4e4 g4 d4 c4 g4f4 g4)))
    
    (setf instrument1.map1 (harmonic-path chords instrument1 :type '> :octave 'path))
    

    It seems that instrument1 needs to have the melody nested one level in order to make the result work, like this:

    (setf instrument1 (gen-repeat (length chords) '((s g4c4 c4 g4e4 g4 d4 c4 g4f4 g4))))
    

    It looks like something changes in gen-repeat, or possibly harmonic-path since December, or am I missing something? Thanks for any insights!

  4. I've been playing around with Rangarajan's "Constraint Programming with Screamer" file, and ran across what looks like a bug.

     

    The program generates this chord sequence (which I assigned to chords-1):

    (setf chords-1 '((h. c3e3g3 ff -q) (h. d3f3a3 ff -q) (h. g3b3d4 ff -q) (h. a3c4e4 ff -q) (h. e3g3b3 ff -q) (h. g3b3d4 ff -q) (h. a3c4e4 ff -q) (h. c3e3g3 ff -q)))
     

    If I just cmd-1 on that, it displays and plays just fine. If I evaluate this, though:

    (ps 'gm :treble chords-1 :time-signature '(4 4) :tempo 120)

     

    I get this mess:

    625534283_Chordmess.png.51d4de61651e6064196db68588d2388f.png

    It plays one chord (or rather, discord).

     

    This seems ok:

    (get-time-signature chords-1)
    => ((4 4 8))

     

    This looks ok:

    (disassemble-omn chords-1)
    => (:length ((3/4 -1/4) (3/4 -1/4) (3/4 -1/4) (3/4 -1/4) (3/4 -1/4) (3/4 -1/4) (3/4 -1/4) (3/4 -1/4)) :pitch ((c3e3g3) (d3f3a3) (g3b3d4) (a3c4e4) (e3g3b3) (g3b3d4) (a3c4e4) (c3e3g3)) :velocity ((ff) (ff) (ff) (ff) (ff) (ff) (ff) (ff)) :articulation ((-) (-) (-) (-) (-) (-) (-) (-)))

     

    What's going on here?

     

    Thanks!

  5. In the Editor Commands window (Help -> Editor Commands), the description text in the bottom panel is black on a very dark gray background (dark mode). I have to select the text to read it.

     

    Also, when you open a Help panel (the floating panel you get when you click on a function in the rightmost panel) and select some text in it, then click outside that panel, the text reverts to its unselected color, but the selection highlight is almost the same color, so it becomes unreadable.

     

    I'm using V2.0.25787 on Catalina 10.15.5.

  6. On May 9, I got an email from Opusmodus announcing V2.0.25750, with a bug fix. I currently have 2.025716 (on Mac Catalina). I've checked for updates in OM several times since then, but it always says that I'm up to date. Is there a problem in the update system? Thanks!

  7. It would be great if the File / Open Recent... list was sub-divided into .opmows files and everything else. It would also be very convenient if, when Opusmodus starts, it re-opened any .opmows files that were open when it last quit, but lacking that, having a separate section for them in Open Recent... would provide quick access to what I've been working on. As-is, any .opmows file tends to fall off the list when I open enough other files.

  8. I just discovered that (from the doc for integer-to-pitch)

    (integer-to-pitch '((-2 -1) 0 (1 2)))
    => (bb3b3 c4 cs4d4)

    but

    (integer-to-pitch '((-2 -1) (0 2) (1 2)))
    => ((bb3 b3) (c4 d4) (cs4 d4))

     

    Unless at least one element is not a sublist, it fails to make chords. This seems inconsistent, and probably a bug.

    This is in Opusmodus Version 1.3.24962

  9. I've attached two screenshots showing how Figure 10 in "1st Element - Length.rtfd" looks, compared to the example copied to the left pane and evaluated using Tools / Snippet / OMN Notation.

     

    I would much prefer the appearance of the tutorial example, without the horizontal line, to what I get when I render it. Is there a problem with my setup, a bug, or has an aesthetic decision been made here that didn't get reflected in the doc?

     

    I'm using OM Version 1.3.24952 on MacOSX 10.14.6.

     

    Thanks for any insights.

    Screen Shot 2019-08-19 at 9.31.12 PM.png

    Screen Shot 2019-08-19 at 9.31.03 PM.png

  10. I just installed V 1.3.24409, and am getting some errors on startup. The first one is an alert that says:

    "Error in Hemlock command processing. There is no applicable method for the generic function: #<STANDARD-GENERIC-FUNCTION ENSURE-COMPOSER-PANE #x302001D4373F> when called with arguments: ("/Users/<my username>/Documents/Opusmodus/Extensions/Load CLM Instruments.lisp" #<OM-LAYOUT-CONTROLLER <OMLayoutController: 0x134880> (#x134880)>).

     

    After I dismiss that, a window opens that says: Error: File #P"clm:instruments;" does not exist.
    > While executing: clm-user-ins-path, in process Opusmodus Extension Initialization(6).

    and then the error recovery options.

     

    I have deleted both the ~/Documents/Opusmodus and ~/.opusmodus folders, deleted the prefs file, and searched for any other opusmodus folders, so I'm confident that it's clean. I then reinstalled the newly DL'd Opusmodus, launched it, entered my serial #, and created a new Opusmodus folder. This didn't help.

     

    The file ~/Documents/Opusmodus/Extensions/Load CLM Instruments.lisp exists and looks unremarkable.  ~/Documents/Opusmodus/CLM/instruments exists and contains a bunch of .ins files.

     

    Before I DL'd the new version, I launched the previous version 1.3.24303 and got that same error window complaining about not finding clm:instruments. I am unaware of anything changing on my Mac that might have broken this recently. I'm running Mojave 10.14.2 on an iMac (Retina 5K, 27-inch, Late 2014).

     

    The Quick Start Workspace loads and plays anyway.

     

    Any ideas about how to fix this?

×
×
  • Create New...

Important Information

Terms of Use Privacy Policy