Five12.net -- Online Forum for the Numerology Music Sequencer

Five12.net -- Online Forum for the Numerology Music Sequencer (http://www.five12.net/index.php)
-   Five12 News (http://www.five12.net/forumdisplay.php?f=2)
-   -   Numerology 4.2 Build 183 (http://www.five12.net/showthread.php?t=3719)

jim 07-08-2019 10:42 PM

Numerology 4.2 Build 183
 
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.

blackdoors 07-20-2019 02:01 PM

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

jim 07-23-2019 06:28 PM

Excellent-- thanks for the report!

Cheers,
Jim

nefastis 07-29-2019 02:16 AM

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!

jim 07-31-2019 12:04 PM

Quote:

Originally Posted by nefastis (Post 17631)
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!

Do me a big favor and email me the last few crash logs for Cubase. They should be in ~/Library/Logs/Diagnostic Reports. Option-click the "Go" menu in Finder to see the Library dir.

Thanks!
Jim

blackdoors 08-02-2019 03:54 AM

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!

PLaine 08-03-2019 09:41 AM

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...

jim 08-03-2019 08:26 PM

Quote:

Originally Posted by PLaine (Post 17656)
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...

I've got a couple days this coming week set aside for N4 support, will look at both this and the Cubase thing. If you haven't yet, do me a favor and use the "Contact Five12" item in the Numerology menu to report a bug -- that will upload the always-useful crash reports.

Cheers,
Jim

blackdoors 08-04-2019 12:19 PM

Quote:

Originally Posted by jim (Post 17662)
I've got a couple days this coming week set aside for N4 support, will look at both this and the Cubase thing. If you haven't yet, do me a favor and use the "Contact Five12" item in the Numerology menu to report a bug -- that will upload the always-useful crash reports.

Cheers,
Jim

No problem, does this method work if it's relating to crashes of Cubase when arsing from the VST?

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

jim 08-05-2019 12:59 PM

Quote:

Originally Posted by blackdoors (Post 17664)
No problem, does this method work if it's relating to crashes of Cubase when arsing from the VST?

Yes -- OS X will generate a crash report that will indicate where in the code the crash happened.

Quote:

Originally Posted by blackdoors (Post 17664)
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!)

Yes. -- Actually OS X makes the crash log and stores them in ~/Library/Logs/DiagnosticReports. The "report bug" feature in Numerology will search for any crash logs where Numerology was involved and upload them to the Five12 server. It is a bit easier for me to work with logs that are on the server as I have a script there to process them for easier analysis, but sending them via email is also handy in case the report tool misses them somehow. The email also serves as an extra reminder to look at them.

Cheers,
Jim

blackdoors 08-05-2019 04:54 PM

No prob, I will mail a couple from the other day.

No idea why it sometimes makes a log and sometimes not, but I can send what I have.

John

jim 08-10-2019 12:39 PM

Quote:

Originally Posted by blackdoors (Post 17669)
No prob, I will mail a couple from the other day.

No idea why it sometimes makes a log and sometimes not, but I can send what I have.

John

Thanks -- much appreciated!

Jim

PLaine 08-31-2019 06:12 PM

Hi Jim!

A little more about my MIDI related problems which came up in somewhere in Mac OS / Numerology development:

It seems quite obvious that those MIDI timing / crashing problems does NOT occur if I use same projects ReWire mode in Logic. For example now I found out that one of my older Numerology songs started behave badly in some point of the song structure: in this case I hear hanging MIDI notes. Like others, same project can crash too. But if I use it with ReWire mode in Logic it seems to run flawlessly. Does this give any new hint what's the problem in standalone mode? In Logic MIDI sync is made with Logic's sync and its destinations. While being total novice I have a feeling that problem somehow related to MIDI sync. As I said earlier, nowadays Numerology project (when you hit "play") usually starts with MIDI mess, it's 1-3 seconds out of time and then it gets it right. This wasn't there earlier (year or two ago). And crashes are more frequent too.

Is there something I can do to help this out?

EDIT: Trying to edit or work with this old Numerology song almost every time makes standalone app to crash very soon. On the other hand, just playing it provokes crashes much less frequently. Fortunately I have this workaround at the moment: I can work with it in Logic with ReWire.

jim 09-09-2019 06:57 PM

Quote:

Originally Posted by PLaine (Post 17694)
Hi Jim!

A little more about my MIDI related problems which came up in somewhere in Mac OS / Numerology development:

It seems quite obvious that those MIDI timing / crashing problems does NOT occur if I use same projects ReWire mode in Logic. For example now I found out that one of my older Numerology songs started behave badly in some point of the song structure: in this case I hear hanging MIDI notes. Like others, same project can crash too. But if I use it with ReWire mode in Logic it seems to run flawlessly. Does this give any new hint what's the problem in standalone mode? In Logic MIDI sync is made with Logic's sync and its destinations. While being total novice I have a feeling that problem somehow related to MIDI sync. As I said earlier, nowadays Numerology project (when you hit "play") usually starts with MIDI mess, it's 1-3 seconds out of time and then it gets it right. This wasn't there earlier (year or two ago). And crashes are more frequent too.

Is there something I can do to help this out?

EDIT: Trying to edit or work with this old Numerology song almost every time makes standalone app to crash very soon. On the other hand, just playing it provokes crashes much less frequently. Fortunately I have this workaround at the moment: I can work with it in Logic with ReWire.

Email me a copy of the project -- I want to check the structure to see if the MIDI setup in the project causes a bottleneck somewhere. jim (at) five12 (dot) com.

Thanks,
Jim

malephonk 09-27-2019 02:31 PM

Somehow with Mojave 10.14.6 .. if I try to enter the preferences .. Numerology Pro 4 immediately crashes.

crash report has been send.

hope there will be a fix or is version 5 top priority now?

all the best
m.

jim 09-28-2019 12:54 PM

Quote:

Originally Posted by malephonk (Post 17734)
Somehow with Mojave 10.14.6 .. if I try to enter the preferences .. Numerology Pro 4 immediately crashes.

crash report has been send.

Thanks for the report. Send an email to jim (at) five12.com and I will get you the fix build -- there are a couple more tweaks I want to make before putting it online.

Cheers,
Jim


All times are GMT -6. The time now is 11:35 AM.

Powered by vBulletin® Version 3.8.1
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.