hello Denis Goekdag, since I was the one to guess the closest release date, should't I get rewarded? :-) I was only off by 2 days.
Actually, the *release* date (not announcement date) was the thing in question, which is Nov 15th -- two people guessed Nov 5th, so they'd be closest if I didn't miss a post (which I may have as my brain is still in full jet-lag mode). But hey, we'll simply regard announcement date as well as the release date to be relevant ;-)
You could avoid hitting refresh on this thread all day by following us on Twitter or subscribing to the RSS feed on the front page of our website so you'll automatically be notified once it's up.
While it proved too tricky to come up with another official "intro" discount, there IS a special discount for you Slutz until December 1st, 2012
PM me for details.
The lucky winners of the "guess the date" will receive their discount codes in addition to the aforementioned Slutz-discount.
But please do allow me to get some sleep before I send out the goodies
Good news: we've been able to add AudioSuite to the AAX as well. With UV being rather CPU-heavy, this should be a headache-saver.
Trial versions will be available tomorrow or Saturday at the latest - we decided to implement a little convenience improvement to the demo last minute.
Unfortunately Win VST x64 is not yet in there - we've been running the x64 *plug-ins* successfully for over a month but there's still an issue with the x64 copy protection How I wish that C/P wasn't needed at all...Of course this will be added as a free update ASAP.
So just to be explicit, *right now* UV supports:
Mac AU (32/64)
Mac RTAS
Mac AAX Native + AS
Mac VST 2.4 (32/64)
Win RTAS
Win AAX Native + AS
Win VST 2.4 (32)
As a heads-up to those of you who grab this immediately and can't be bothered to read the manual: make sure you set your I/O buffers higher than you would otherwise do as short I/O buffer sizes increase the CPU hit of UV. We recommend 1024 samples or more. And another heads-up: in PT, dual mono is more CPU efficient than a stereo instance as multi-mono use allows PT to distribute the channels across CPU cores.
Now let me go listen to what the pillow's saying
Cheers,
Denis
Last edited by Denis Goekdag; 17th November 2012 at 05:13 PM..
Reason: clarification stuff
Excellent. But my Mac isn't online so I can't use the autoupdater, and I'd like to get the VST version as I'm likely to do more work with UV on my PC. How does one go about making that happen?
While it proved too tricky to come up with another official "intro" discount, there IS a special discount for you Slutz
PM me for details.
The lucky winners of the "guess the date" will receive their discount codes in addition to the aforementioned Slutz-discount.
But please do allow me to get some sleep before I send out the goodies
Good news: we've been able to add AudioSuite to the AAX as well. With UV being rather CPU-heavy, this should be a headache-saver.
Trial versions will be available tomorrow or Saturday at the latest - we decided to implement a little convenience improvement to the demo last minute.
Unfortunately Win VST x64 is not yet in there - we've been running the x64 *plug-ins* successfully for over a month but there's still an issue with the x64 copy protection How I wish that C/P wasn't needed at all...Of course this will be added as a free update ASAP.
So just to be explicit, *right now* UV supports:
Mac AU (32/64)
Mac RTAS
Mac AAX Native + AS
Mac VST 2.4 (32/64)
Win RTAS
Win AAX Native + AS
Win VST 2.4 (32)
As a heads-up to those of you who grab this immediately and can't be bothered to read the manual: make sure you set your I/O buffers higher than you would otherwise do as short I/O buffer sizes increase the CPU hit of UV. We recommend 1024 samples or more. And another heads-up: in PT, dual mono is more CPU efficient than a stereo instance as multi-mono use allows PT to distribute the channels across CPU cores.
Now let me go listen to what the pillow's saying
Cheers,
Denis
Will the AU-version automatically update to AAX? Or how does this work?
Will the AU-version automatically update to AAX? Or how does this work?
Yes, the AU checks for updates once in a while if it has web access. If you don't want to wait for that (it doesn't do it very often as we don't like software doing stuff behind the scenes) -- write me an email referencing your order number & I'll provide you a DL URL
Yes, the AU checks for updates once in a while if it has web access. If you don't want to wait for that (it doesn't do it very often as we don't like software doing stuff behind the scenes) -- write me an email referencing your order number & I'll provide you a DL URL
You could avoid hitting refresh on this thread all day by following us on Twitter or subscribing to the RSS feed on the front page of our website so you'll automatically be notified once it's up.
-d
BTW: I did follow on twitter but the news wasn't mentioned. Luckily found this thread.
Please note: as UNVEIL uses a lot of CPU, please have a look at the FAQ with regard to CPU load optimization strategies. Most notable: a) use large buffer sizes and b) use multi-mono instead of stereo instances in ProTools.
Denis,
I just wanted to let you know I've loaded the VST version on the Fairlight and so far no issues. Since the CC-1 card offloads VST chores from the CPU, I haven't seen CPU usage issues. So far, I'm just rendering clips, and not patching it to a channel for real time processing. I need to look though the manual to know what the heck I'm doing, but in the couple files I processed, the results were subtle but effective.
Thanks for all your efforts!
Denis,
I just wanted to let you know I've loaded the VST version on the Fairlight and so far no issues. Since the CC-1 card offloads VST chores from the CPU, I haven't seen CPU usage issues. So far, I'm just rendering clips, and not patching it to a channel for real time processing. I need to look though the manual to know what the heck I'm doing, but in the couple files I processed, the results were subtle but effective.
Thanks for all your efforts!
Thanks for the report Bill. Was wondering how it would do on Fairlight.
New Reply 
Facebook
Twitter
LinkedIn
Actually, the *release* date (not announcement date) was the thing in question, which is Nov 15th -- two people guessed Nov 5th, so they'd be closest if I didn't miss a post (which I may have as my brain is still in full jet-lag mode). But hey, we'll simply regard announcement date as well as the release date to be relevant ;-)
How I wish that C/P wasn't needed at all...Of course this will be added as a free update ASAP.
