Jump to content
Sign in to follow this  
trpthawaii

Crashes under OS 10.15 Catalina

Recommended Posts

I recently updated my MacBook Pro to Catalina OS.  Now,  OpusModus just crashes upon startup.  Is OpusModus Catalina compatible? If so,  what do you recommend? Reinstall? 

Share this post


Link to post
Share on other sites

Opusmodus software is not supported under macOS 10.15.

Please do not install macOS 10.15 if you are using Opusmodus.

We are currently conducting tests to offer full compatibility as soon as possible after the official release.

Share this post


Link to post
Share on other sites

Oops.  That explains my troubles.  I'll be waiting anxiously for the next update. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Similar Topics

    • By neuronsong
      I'm thinking of purchasing opusmodus and I'd like to take advantage of the current sale price. However, it is the case I am running the Catalina Beta on the laptop I'd like to use primarily to run the software. I've downloaded the trial version... but it does not seem to be working properly on Catalina. How soon do you think you'll be supporting Catalina?
    • By loopyc
      Hi, I am happily exploring the demo of Opusmodus and have come across some specific? issues to my machine set-up (Mac Pro Mid 2009/OSX 10.9.5).
       
      1- I use a program called 'Total Spaces2' to organize separate desktops. This is the first time it's default key commands of Command 1~9 have caused a problem but when I try to use the Opusmodus key commands for 'Snippet' auditioning, etc ('command' + 1~9) it triggers a TotalSpaces2 desktop change instead. As I use TotalSpaces2 99.9% of my day and have long term muscle memory for it's assignments, I need a way to have different key commands for the 'Snippet' auditioning if possible? Is there a Opusmodus preference file I can alter?? (I don't see anything in the 'Editor Commands' if that is the normal place for making/changing assignments).
       
      2- I am unable to stop normal 'Audition' operation? Using 'command .'  and command ,' or the 'Tools' menu versions of 'Interrupt' or 'Break' ALWAYS creates a 'Beachball of Death' and either an app crash or freeze requiring 'force quit'. I have crash reports if you want to give me the desired address to use to report. If I audition to the MIDI player then 'space bar' works as expected to start/stop, but 'Audition' and 'Audition/Notation' processes seem to have no way to be stopped other than finding a new code excerpt to send to 'Audition' process to override current 'Audition'.
       
      3- I also had repeatable crashes when attempting to audition a list created by the 'permute n' function. I used 'permute n 8'...which is 40320 permutations I believe, so I realize this is a large amount of data. I was able to produce the integer data in the 'Listener', used 'copy/paste' to transfer to a list for processing by 'Integer-to-pitch', then used that data (again from 'Listener' via 'command E' to insert into my score as a pitch variable's list' It is THEN, when I try to evaluate/audition my score's omn sequences that Opusmodus just outright crashes. If there a known virtual memory  limit involved here? I can produce this list as either integers or converted to pitches, and copy/paste both within and to external apps (like text editor 'Text Wrangler') but cannot evaluate/audition or create MIDI from the data. It is a time consuming operation so i know it's a immense data set, but was surprised that instead of just taking a long time it completely  crashes program? Crash report also available upon request. I have 2 x 2.66 GHz Quad-Core Intel Xeon with 16 GB 1066 MHz DDR3 ECC. FWIW, I SUCCESSFULLY used above process/score document to do 'permute n 5', permute n 6', and 'permute n 7'...so it was that jump from 5040 events (n 7) to 40320 that hits some sort of virtual memory wall?
       
      Update: As a test, I was able to use 'TextMechanic' online permutation generator to produce a permutation of 8 items, copy/paste into 'Text Wrangler' (to massage format), and then paste into Intermorphic's 'Noatikl''s 'Pattern' Voice (which interprets integers 1~8 as relative intervals) and was able to successfully convert with 'MIDI Cooker' offline feature. All steps did exhibit long processing times in between steps but DID eventually create a MIDI file...so the large amount of data in memory alone isn't the issue (or wasn't with these particular apps).
       
      4- In the 'Introduction to Opusmodus', it states:
       
      "The tutorial resources can be accessed from within Opusmodus itself. You’ll find Quick Start, a guide providing the necessary basics. Then there is Stages: a 30-part collection of score-scripts and text commentaries designed to be opened simultaneously. Both these are available as a download: a PDF file formatted as a printable A4 book."
       
      I have located the 'Quick Start' PDF, but would really like the 'Stages' as 'nightstand' material (in my case my iPad ;-)), but only see the individual rtfd's for 'Stages' as opposed to the above referenced 'Both these are available as a download: a PDF file formatted as a printable A4 book."
       
      Update: I have since created my own PDF of 'Stages', so unless there is a version that includes the actual score information as examples within the textual narrative then I'm good :)
       
       
      In closing, a Opusmodus purchase is definitely in my future, the online documentation and program organization is a real resource to opening up this composing approach, I am truly excited about the seemingly endless possibilities Opusmodus will provide for a very long time ;-)
       
      Thanks in advance
       
      One final note, a small typo I stumbled across in 'Interval-Row-Invert'...the word ''two' instead of 'row'? (see attached)

    • By loopyc
      In cutting and pasting various examples to play/learn in the demo, I keep having full on crashes of Opusmodus. Here is one partial example:
       
      Process:         dx86cl64 [23214]
      Path:            /Applications/Opusmodus.app/Contents/MacOS/dx86cl64
      Identifier:      com.opusmodus.Opusmodus
      Version:         1.2.22559M (???)
      Code Type:       X86-64 (Native)
      Parent Process:  launchd [203]
      Responsible:     dx86cl64 [23214]
      User ID:         501
      Date/Time:       2017-11-06 16:44:45.541 -0800
      OS Version:      Mac OS X 10.9.5 (13F1911)
      Report Version:  11
      Anonymous UUID:  39614AC9-7EC1-8B08-095E-FBB03C0F32A2
      Sleep/Wake UUID: 0B42E315-D1F9-46AB-99C0-4038549CFD6A
      Crashed Thread:  13
      Exception Type:  EXC_BAD_ACCESS (SIGBUS)
      Exception Codes: KERN_PROTECTION_FAILURE at 0x000000002d415ff8
      VM Regions Near 0x2d415ff8:
          dylib (reserved)       000000002cb20000-000000002d415000 [ 9172K] rw-/rwx SM=NUL  reserved VM address space (unallocated)
      --> shared memory          000000002d415000-000000002d416000 [    4K] r-x/rwx SM=ZER  
          VM_ALLOCATE            000000002d416000-000000002d630000 [ 2152K] rwx/rwx SM=COW  
       
      Here is the score that causes it:
       
      (setf pitches (gen-repeat 1024 '(c3 cs3 d3 ds3 e3 f3 fs3 g3 gs3 a3 as3 b3)))
      (setf transposed-pitches (gen-repeat 5 (pitch-transpose -12 pitches)))
      (setf lengthsa (span pitches (gen-length-cartesian 1 1 'm 'n 4 '(2 3) '(13 4) '(1 2 3 4 5 6))))
      (setf lengthsb (span pitches (gen-length-cartesian 1 1 'm 'n 4 '(2 3) '(13 4) '(6 5 4 3 2 1))))
      (setf lengths-rests1 (length-weight lengthsa :weight '(3 1) :seed 1))
      (setf lengths-rests2 (length-weight lengthsb :weight '(5 1) :seed 2))
      (setf pitches-rgrade (gen-retrograde pitches))
       
       
       
      (setf piano-righthand
            (make-omn
             :length lengths-rests1
             :pitch pitches-rgrade
             :velocity'(mf mp)))
       
      (setf piano-lefthand
            (make-omn
             :length lengths-rests2
             :pitch transposed-pitches
             :velocity '(mp mf f)))
       
      (setf timesigs (get-time-signature lengths-rests1))
       
      (def-score Stage-4
                 (:key-signature 'chromatic
                  :time-signature '(5 8)
                  :tempo 128
                  :layout (piano-layout 'piano-rh 'piano-lh))
        
        (piano-rh
         :omn piano-righthand
         :channel 1
         :sound 'gm
         :program 'acoustic-grand-piano)
        
        (piano-lh
         :omn piano-lefthand)
       
      When I 'Evaluate All' for above, I get (excerpted for pertinent step):
       
      2 > make-omn
      2 > make-omn
      > Error: Stack overflow on value stack.
      > While executing: (:internal f flatten), in process Listener-1(5).
       
      If I try changing parameters (like either the lefthand velocity count or the 'even/odd' nature of the 'gen-repeat' value) and 'Evaluate All' again, then I get a full app quit with the crash report at top of this post.
       
      If I restart Opusmodus I can variously change the 'gen-repeat' integer to 256 (always successful with all other code exactly the same) and only sometimes 512 (if done immediately after a fresh start) to finally be able to 'Evaluate and Display MIDI' and thus export MIDI. I was trying to get a overall longer 'master' file for later variations in editing the MIDI, but it seems my thinking of just doubling this gen-repeat number would work? Also, many of my attempts to change the numbers involved 'gen-length-cartesian' lines also cause these 'VM errors?? 
       
      I am really just trying things out at tis point (these are really 'scratch/throwaway files just to test possible workflows), so no ONE instance of inserting an inappropriate variable range concerns me, but having this 'VM' type of crash over many DIFFERENT functions and files seems like there is something going on where memory allocation is not functioning correctly? In other words, over different scores and functions I am continually crashing and seeing references to VM allocation in the resulting crash report. Is this what should happen (I would expect an error in 'Listener', not a full crash)?? I have 16 gigs RAM and over 100 GB free system disk.
       
      Full crash reports can be sent if you provide a desired/proper address that you would like me to use. 
       
      Thanks in advance
×
×
  • Create New...