Jump to content

Timothy Rolls

core_group_3
  • Content Count

    5
  • Joined

  • Last visited

About Timothy Rolls

  • Rank
    core_member_rank_1

core_pfieldgroups_2

  • Gender
    Male
  • Location
    Hays, KS

Recent Profile Visitors

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

  1. Janusz, That seems to have fixed it! Thanks for the help. Sincerely, Tim
  2. Thanks Janusz, I am running the latest update of Mojave on a 2016 MacBook pro with 8 gig ram and a 2.9 GHz i9 processor. The program just shuts down, I get a "send to apple?" message, and I can see the data in when I expand it, but I cannot find the crash log to send along to you. I was able to work on it last night for a half hour without it crashing. After Julio's message, I installed it on my iMac and it hasn't crashed. On the MacBook Pro, I didn't necessarily have to do anything. it would crash even if just sitting there. As I said before, I had been trying the CLM stuff, but then it also crashed when I reopened after a restart and tried working on a simple file from scratch. I'm wondering if there is a conflict on this computer, the only difference between this and my iMac, is a few fewer apps, and the laptop has Dorico on it (and the Steinberg e-Licenser). There are no other apps on the laptop that aren't on the desktop. I don't know if any of this is helpful, but if you have any other questions or suggestions, I appreciate it. Best, Tim
  3. Happy new year, all! I upgraded to 1.3 this morning, following the instructions and removing the folder before the upgrade. All went well with the installation, but after about 5 minutes of running it would crash. An additional problem: I cannot find a crash log where MacOS usually keeps it. I initially thought it was a problem with CLM, as I had been investigating that, but then I restarted the computer and opened Opusmodus and it crashed again while working on a new file. Anyone have any ideas about what the potential problem could be, or at least where the crash log would be? Normally I find them in ~/logs/DiagnosticReports, but I don't see one there. Thank you all for any advice. Regards, Tim
  4. Thanks, Janusz. That seems to have also fixed the other problem with my spectral libraries as well. Although, I am a bit confused because I don't ever remember creating a function, let alone one called double, since it seems to be a reserved keyword in so many languages. Anyway, thanks for the help on that. I'm up and running again. Best, Tim
  5. I'm hoping someone on the forum can help me with this. Since the last update, on my laptop I am unable to use any of my spectral libraries I've created. The tbn-cs one that comes in the app still works, just the ones that I created are not found. I try recreating them and they seem to recreate fine, but after I restart Opusmodus, they still cannot be found. When I check my spectral-data/data and spectral-data/partials, I do see all the necessary files I have created. I think that is happening on my desktop machine, but I can't get to it right now to be sure (I think it was on the desktop that I first found my libraries not being found). However, on both machines, when I first start Opusmodus, I get the following error: > Error: The function double is predefined by Opusmodus. > While executing: ccl::cerror-if-redefine-om, in process Opusmodus Extension Initialization(5). > Type cmd-/ to continue, cmd-. to abort, cmd-\ for a list of available restarts. > If continued: Replace the definition of double. > Type :? for other options. Afterwards, everything not related to my spectral libraries has seemed to run fine. I have not created any extensions, and I cannot find in any of my work where I might have tried to define something as double. I've tried reinstalling Opusmodus and it is not changing anything. Does anyone have any ideas short of reinstalling OSX? I suppose that's a possibility, but I don't want to have to try that till there is no other choice. Thanks. Regards, Tim
  6. Timothy Rolls

    Timothy Rolls

×
×
  • Create New...