During the last few weeks we have done extensive stress testing of ACE. ACE has received some treatment to become V1.3 - it's got a new "filter reset" parameter on the tweak page for those who need a "digital" filter behaviour to accompany VCO reset. We've also defused a few possible issues with multicore processing when changing a preset happens at the time of processing audio and vice versa.
We hope to post an ACE 1.3 release candidate next week, with final installers and information. We would like to send out a newsletter then and hint at Bazille public beta testing (starting as of now).
ACE2352Win.zip, Bazille2352Win.zip, Diva2352Win.zip, Filterscape2352Win.zip, MFM22352Win.zip, Podolski2352Win.zip,
Satin2352Win.zip, TripleCheese2352Win.zip, Uhbik2352Win.zip, Zebra22352Win.zip
ACE2352Mac.zip, Bazille2352Mac.zip, Diva2352Mac.zip, Filterscape2352Mac.zip, MFM22352Mac.zip, Podolski2352Mac.zip,
Satin2352Mac.zip TripleCheese2352Mac.zip, Uhbik2352Mac.zip, Zebra22352Mac.zip
Changes since 2242
- completely redone Mac Installers - check for completeness, file permissions, proper update behaviour
- fixed UI freeze with 32-bit Carbon UIs on Mavericks
- separated AAX 32/64 bit on Win installers, added proper install path
- Added choice of gamma adjustments to GUI editor (brightness control)
- Antialiasing on GUI fonts can now be turned off
- added VST3 ReadMes to installers, made VST3 install optional (off by default)
- added module name to VST2 parameter list (check if existing automation is affected)
- fixed Win Click-Thru bug, possible also "two clicks needed to close window"
- improved font rendering on Windows
- fixed "u-he menu" on TripleCheese preset folders
- fixed snapshot step indicators in Filterscapes
- fixed missing preset name in VST2
- removed useless "panned BPs" mode form FilterscapeVA
- fixed swapped Delay times in ZebraCM
- improved error message ("Error 3") on Win
- fixed Diva Waveform Slider offset
- switched text drawing to CoreText on Mac (removes special character issue in Satin)
- fixed "apostrophy bug" in Preset Descriptions
- fixed text abbreviation bug on Win
- Zebras - Osc Phase now defaults to 50.00
- fixed negative smoothing bug in Filterscape StepSeq
- fixed installers for 32-bit Windows (hopefully, again)
- fixed line style wires being cut off in scaled UIs (Win only)
- improved voice stealing behaviour (less clicky)
- fixed legato modes
- fixed slow UI loading times
- fixed a lot of pops, thumps, nasty noises and critical sound bugs in ACE
- improved oscilloscope modes
- added 200 HS presets to ACE (will also add preset list and extra zip shortly)
- added "reset filter" feature in ACE Circuit Bending section
- fixed few issues that could cause silence or noise with multicore turned on
- fixed missing button graphic in ACE
- fixed missing lock function on tuning files etc.
- hiding cables now while NagScreen is visible
- made Gate fade quicker as VCA
- made new font compromise on Windows
- added Bazille Installers
- put correct version numbers in Mac installers
Note: For full information on Bazille, there'll be a dedicated thread.
Important Note for ACE users: If you upgrade ACE from a version prior to 1.2 then you might have to re-assign parameters in track automation. Read more
Important Note for Satin users: If you update Satin from a version prior to 1.1.1 then you can't easily "go back" because presets saved with the new version don't open in older versions. Please back up your projects with Satin before you update, then restore them if you need to go back to Satin 1.1 or 1.0 (which we hope you don't have to)
Note for TDZ users: Updating ZebraHZ takes a bit more work than just upload an automatically generated zip. We'll post an update once the major issues are confirmed to be fixed, and we'll announce this here.
some more background info:
A few months ago we decided to drastically shorten the time between development stages and public deployment. So now, when we've worked through a bunch of feature requests and bugfixes, we post the absolute latest and freshest versions here, in public. This way we hope to catch bugs and issues much quicker than in usual development cycles. We also hope to provide quick fixes and workarounds whenever people experience problems with our official release versions.
Is it dangerous to install these version? - Yes, they obviously have beta status and they're not tried and tested broadly. But: They are as good as a freshly released software can be and they fix a lot of issues that are still present in the official versions.
Here comes the gist: We release these shortly after changes were made. Thus, whenever a bug is reported, chances are good that it occurs in a part that a developer has just touched. So the developer needs less time to understand the issue and fix it. Therefore, the software ultimately becomes better in shorter time than it would be possible with, say, annual updates.
Thus, the more people who install and use these versions, there more stable it gets