#1
|
|||
|
|||
![]()
Pro: http://files.five12.com/NumerologyPro-4.2-Build183.dmg
SE: http://files.five12.com/NumerologySE-4.2-Build183.dmg RELEASE NOTES: Numerology 4.2 Build 183 - Fixes an issue on OS X Mojave that could cause a crash on startup. |
#2
|
|||
|
|||
![]()
Hi Jim, thanks for this. Just checking in to say ..... seems to finally be ok here in Cubase VST (v10.0.30) / Mojave again. I've missed the VST so much!
John |
#3
|
|||
|
|||
![]()
Excellent-- thanks for the report!
Cheers, Jim |
#4
|
|||
|
|||
![]()
Hi Jim,
I’m still getting a crash on load in Cubase. I’ve trashed the preferences and reinstalled the VST after restarting my computer. Any suggestions? Thank you! |
#5
|
|||
|
|||
![]() Quote:
Thanks! Jim |
#6
|
|||
|
|||
![]()
Hi Jim, sorry to be the bearer of bad news - but of course I spoke too soon here, Cubase 10.0.30 is right now very unstable if I activate the VST on the iMac machine. I'll try on the other machine later.
Basically what I see is that when Numerology VST is installed it is usually blacklisted. If I re-enable it from the plug in manager, Cubase crashes almost every time I try to open a file dialogue or load a project (for example when clicking 'open other' from Hub, or 'Save As'). The plug in does not have to be loaded in a project to get this result. Re-scanning resulting in a Blacklisting, or moving the numerologyVST out of the VST folder fixes it. Multiple reboots, updated all other plug ins, temporarily removed all other plug ins (especially Lexicon LXP which has caused me problems with heavily loaded projects before), but the only 'fix' I can find is to blacklist or remove numerology VST. Anything left to try? Or anything I can do that would help you? John ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- Edit - just managed to get it (temporarily?) working by manually moving Numerology VST back into the VST folder and running another plug in scan. This time (unlike earlier today!), doing this didn't result in a blacklisting and Cubase appears ok (for now). Is there some issue that can usually (but not always) result in a Cubase blacklisting that triggers crashes? Whatever it is seems to persist after the blacklisted version is re-enabled via the Plug-in Manager. No idea on how Cubase caches any of this stuff. I'll let you know if I manage to work anything else out! Last edited by blackdoors; 08-02-2019 at 04:19 AM. |
#7
|
|||
|
|||
![]()
Hi all!
I updated too my app to see if there’s any change in my MIDI related problems. Unfortunately no. I still get timing issues when I hit start and also crashes. I don’t know for sure but these issues became more frequent somewhere in OS X and/or Numerology updates. I remember that earlier N behaved much more stable. I use N standalone with external MIDI gear. I can live with this situation but I hope that future will bring us more stability... |
#8
|
|||
|
|||
![]() Quote:
Cheers, Jim |
#9
|
|||
|
|||
![]() Quote:
Do Cubase crash logs help you too? (I am not clear that Cubase makes a crash log in these sudden crashes but would like to help if I can!) John |
#10
|
|||
|
|||
![]() Quote:
Quote:
Cheers, Jim |
![]() |
Thread Tools | |
Display Modes | |
|
|