Jump to content


  • Content Count

  • Joined

  • Last visited

About Stoney

  • Rank
    Junior Member

Profile Information

  • Gender
  • Location
    Concord, MA, US

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. So f4 is just a constant buried somewhere in the code? What about the natural sign? I can't imagine that it has a purpose, so did it just creep in there as a bug? Here is an image showing the result:
  3. Just wondering about this. Given a pitchless snippet like '(q = = = ) What determines the pitch when auditioned? It's not preferences/audition, which says c4, but it's playing f4. I'm also puzzled by why the notation produced has a natural sign in front of the first note. I'm pretty sure it didn't used to do that. I'm using V2.0.25787 on Catalina. Thanks!
  4. 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!
  5. I'm happy to report that yesterday's release (v 2.025716) works on Catalina. Thanks!
  6. I didn't look closely enough at the system requirements for V2, and have found that it doesn't open any windows on Catalina (10.15.3). I'm aware of the CCL compiler problem, but I thought that had been fixed. Is there an expectation that V2 will run on Catalina soon?
  7. Torsten, that makes sense. Thanks for the clarification!
  8. Wow. Thanks! I didn't realize that computer had "Closed Windows" turned on.
  9. 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.
  10. That's good to know, and is simpler than my current workaround (add a 0 to the front of the list, then drop the leading c4 from the result). Do you consider the inconsistency of the integer-to-pitch results a bug?
  11. 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
  12. This is much nicer now! Is it being too picky of me to ask that the vertical bar at the beginning be returned too?
  13. Sounds like it should be reverted! Thank you.
  14. 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.
  15. Stoney


  • Create New...