When preparing the final bits of an upcoming plug-in release, other research and prototyping typically has already been done for other potentially upcoming projects. This usually is the time when the decision is made about the next project and the new plug-in gets outlined and planned in detail. In this case it was around 9 month ago in August 2009 when FerricTDS (our entry for the KVR DC ’09) finally went into the late beta testing stage. Since quite some time I had in my mind to improve the “Nasty” plug-in series package but to that time it had become finally clear that the next step would be to put it into one single and consistent “console strip” style plug-in. [Read more…]
The public beta for the upcoming FerricTDS 1.5 has been closed today – thanks for all the contributions! A final version will be released here somewhere in March.
I’m currently preparing the bits for the upcoming FerricTDS beta test. Since this beta is going to be public nobody needs to apply for joining the party, just come back here during the next days or so, pick up a copy and have a ride with it (and give feedback of course). The version number jumps from 1.0.2 straight to 1.5 which indicates some vast improvements under the hood. I’m already really excited about this one.
I do need some more testers with SSE1 compatible systems (e.g. old AMD Athlon series) – if you can perform some tests for me with a prepared Density mkII version please drop me a short comment here with your email.
Just a short update on whats going on with some already reported issues concerning Density mkII (released around two weeks ago):
- There will be a SSE1 compatible version
- The CPU spiking “denormal” issues and heavy CPU loads are already fixed
- A fix for the loading issues in Wavelab is currently under investigation and test
- Some crash reports will be further investigated
The current plan is to release a 2.0.1 bugfix release to end of September containing whats fixed and stable then.
While working on the Density overall re-design I was working extensively on the audio engine as well but just for one single reason: The one thing I was missing in the original design was to have some more “responsive” gain riding possibilities but without the usual tradeoff of introducing more distortion or compromising the transparency. And (unsurprisingly) that turned out to be not that easy.
Most people have no idea where probably most “development time” is actually spent: it’s in the audio listening tests and not the coding.
Some time ago I’ve become part of a music project which is heading more towards the dancefloor compatible side of electronica. We are currently testing Ableton Live and thinking about switching over to use it as the main production tool. I’m undecided yet. What do you think about Live – is this really the ultimate solution for electronic based music production? What are the known drawbacks?
for development and testing purposes I need some further raw and unprocessed good made recording samples (short loops / snippets are ok). Mainly drums, bass or vocal stuff.
Just drop a note here if you want to support me.
Thanks in advance!