PDA

View Full Version : Numerology 3.1 Build 44


jim
08-03-2011, 11:47 AM
A few updates on the Launchpad mapping, and a bunch o fixes. Also, this build of the VST should load on 10.5/Intel, but you will probably need to do some juggling: In Live, I had to reboot, turn VST hosting off, and re-scan the plugin dirs.

PRO: http://www.five12.com/NumerologyPro-3.1-Build44.dmg
SE: http://www.five12.com/NumerologySE-3.1-Build44.dmg


New Stuff:

Interval Seq / Launchpad : Octave-setting now works. It acually will work for any "CV Sequencer" when the range is set to one of the semitone ranges: +/- 12, 24, 48. You have to live with a major mode scale for the sequence itself, but you can override it with the quantizer in the NoteGen or the CustomScale module.

Fixes & Updates:

- PolyNote / Launchpad : changed 'erase' mode to actually erase notes instead of just muting them.
- DrumSeq / Launchpad : tweak recording algorithm to avoid flamming.
- AU : Fixed a 'race condition' when running in Logic that could cause various problems (crashing, UIs not
opening) when closing one project and opening another.
- AU/VST : Restore the 'edit run mode' buttons (the little 'E' buttons) on all the NoteSequencers.
- VST : Fixed a problem handling sample files loaded from the Stack Library
- VST : Fixed a problem where the UI would not open properly in Ableton if the VST is 'turned off'.
- Fixed a race-condition on save & quit in App and ReWire modes.
- When importing a stack from the StackLibrary, where the stack originted in the N3 AU or VST, the Stack In and Out
modules now have proper I/O connections.
- Fixed a problem whereby projects with LFO modules would auto-trigger the transport when loading projects, which
could then cause further problems...
- Fixed an edit window resize issue with Camel Audio Alchemy.
- Fixed an inssue with Camel Audio Alchemy related to loading new 'skins'.
- Shift-Tab now properly cycles endlessly between the rack, tracks, and mixer panels.
- Fixed a missing image (MailIcon) on the VST.
- Numerology now remembers where you last saved a project when it is restarted.
- Updated the PingPong delay with the 'tenth millis' fix
- Fixed a problem whereby "Demo Mute" would happen in trial mode.
- Fixed a problem where the "Free Trial : X Days Left" message was not showing up properly in the AU/VST
- Added field type and length validation to the User Feedback dialog.
- Improved the labeling of the fields in the User Feedback dialog.
- Fixed a module-naming issue with the ButtonBox and AudioMixer modules.
- Number Box : is now much better at handling '-'.
- Number Box : the backspace key now works.

rattlework
08-03-2011, 12:58 PM
Thanks Jim I now have the VST working in OSX 10.5.7.

rattlework
08-03-2011, 02:44 PM
Jim, I just tried to load the AU of Numerology and now that crashes live 8.2.2. I rebooted and turned off the VST plugins but the AU still crashes live.

jim
08-03-2011, 04:16 PM
Jim, I just tried to load the AU of Numerology and now that crashes live 8.2.2. I rebooted and turned off the VST plugins but the AU still crashes live.

Send me your crash logs... (jim (at) five12 (dot) com)

Thanks,
Jim

Sifaka
08-04-2011, 06:43 AM
Jim, I just tried to load the AU of Numerology and now that crashes live 8.2.2. I rebooted and turned off the VST plugins but the AU still crashes live.

Why don't you use the vst in live ? It's got zero latency.

rattlework
08-04-2011, 02:40 PM
How to I get to my crash logs? Also the vst still has latency for me. Are there some settings I not aware of?

jim
08-04-2011, 03:08 PM
How to I get to my crash logs?

They're in <your home dir>/Library/Logs/Diagnostic Reports
(before 10.6.4 or so, look in <your home dir>/Library/Logs/Crash Reporter).

Logs for Ableton Live will be named something like Live_<datestamp>.<machine name>.crash

Select all the crash logs you have, or at least the last 4-5, right-click, choose 'compress', then email me the resulting .zip file. Many thanks -- though as Sifaka mentioned, the VST is now the recommended option for Ableton...

Also the vst still has latency for me. Are there some settings I not aware of?

No special settings -- the VST generates MIDI through the VST plugin API, then it is up to the host to route it properly. If you are using external synths, you'll still get latency -- in that case use track delays to compensate. If you're seeing latency within a project, then the best way to track down what is happening would be for you to email me the project.

Cheers,
Jim

verstaerker
08-04-2011, 04:02 PM
mmh...
am i the only one having this issue with the VST that the H.Sync syncs wrong when running Audio @ 96 kHz?

the AU runs fine

jim
08-04-2011, 06:34 PM
mmh...
am i the only one having this issue with the VST that the H.Sync syncs wrong when running Audio @ 96 kHz?

the AU runs fine

Hang on, I'm on it...

Jim

jim
08-04-2011, 08:29 PM
mmh...
am i the only one having this issue with the VST that the H.Sync syncs wrong when running Audio @ 96 kHz?


Fix in for the next build (#45), out tomorrow...

Cheers,
Jim

TNT
08-06-2011, 01:12 AM
Thanks Jim for this update. The clock offset is so pretty cool. :D