We think you deserve tools that work perfectly and have the most features as they can right from the start, and that’s why we really need to push AUv3 to Audulus 4.Īnd don’t worry - it will be in the initial 4.0 version! This isn’t vaporware - we currently have it running on our iOS devices, and it works, but it’s missing features and has some bugs that need to be worked out. It’s so valuable to have your input, and so many of the modules in the released version of Audulus and the upcoming reface are really a collaborative effort with all of you.
We’re so thankful and proud of the usergroup we’ve developed here at the forum. There will be so many new features to Audulus 4 that even if we released AUv3 for Audulus 3, you’d still want to buy 4 (if just for the MIDI out alone). The longer we work on improving 3, the longer 4 is delayed.
The fact is though, it’s time to switch gears to work on Audulus 4. Since the initial release of Audulus 3, we’ve delivered many new features that users have wanted, including multichannel audio, SVG support, a huge library of modules ( not to mention the new redesign still forthcoming), and more. I know this must be disappointing to people who were hoping to see it in Audulus 3, and I know the more cynical response might be that we’re delaying it to incentivize people to buy Audulus 4 instead, but that is simply not true.Īudulus 3 has gotten more and more significant updates than pretty much any music app out there. We had already made the decision to delay MIDI out until Audulus 4, which would have meant the MIDI AUv3 effect would have been released then anyway too. We’ve been beta testing Audulus AUv3 for iOS and have run into a significant number of problems that must be fixed - enough that it warrants delaying it until the release of Audulus 4.Īudulus is uniquely difficult to fit into the AUv3 format, and we want to make sure that the release of the AUv3 is perfect out of the box, rather than half-working with the promise to improve it later.
0 kommentar(er)
