Zynaptiq Releases UNVEIL v1.5: De-Reverberation for VST, RTAS, AAX on Mac & Windows
Hey all,
we're glad to announce that version 1.5 of our de-reverberator and signal focusing processor UNVEIL is available now! This is a free update for users of version 1.0x - the v1.0x plug-in will detect the update automatically & allow you to download it.
UNVEIL is a unique processor that allows attenuating or boosting reverb components within a mixed signal of any channel count, including mono sources, without messing with dynamics or signal phase. This allows cleaning up dialog and production sound for post-pro in a previously impossible way. It also allows you make music signals become more transparent or more laid back. It achieves this by using artificial intelligence based pattern recognition and de-mixing. Sounds like rocket science? That's exactly what it is For more info, please check out the product website and our demonstration videos.
What's new in v1.5:
Now supports AU (32/64bit), RTAS, AAX Native and VST 2.4 (32/64bit) on MacOS X.
Now supports RTAS, AAX Native and VST 2.4 (32bit) on Windows.
AudioSuite support in ProTools 10 via AAX plug-in.
New preset management functionality accessible from within the plug-in GUI allows user presets to be used across all plug-in formats on all platforms.
New multi-mono capability in Logic Pro 9.x to allow for individual settings for channels in multi-channel/surround scenarios (note: obviously, there's also multi-mono support in RTAS and AAX).
New authorization app for more streamlined user experience.
Completely re-designed automation system for improved automation workflow.
New factory presets.
New option to enter values numerically by double-clicking controls.
Windows VST 2.4 x64 will be added as a free update as soon as it's ready.
UV v1.5 is available now at USD/EUR 399 (the EUR price is inclusive of 19% VAT so these two numbers are actually pretty close to each other), and free trial versions will be available later today or tomorrow.
And what's more...we offer a discount to Gearslutz members until December 1st, 2012 ... PM me for details
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.
Trying it out - so far really impressed but I have one complaint with the demo.
You're a little over-protective to not cause people (me) to be annoyed. The demo times out after 10 minutes AND you can't save AND there is a dialog box that pops up up every minute or so to tell you it's a demo (in pro tools at least) which kills the audio and you have to wait for the plugin to come back up to speed... the first 2 are fine (10 min, can't save) but could you please get rid of the additional pop-up it completely kills the learning and adjusting of the parameters!
I love the knob/lever concept in the GUI wish all knobs on plugs did this!
Thanks.
__________________ - "You only have a certain amount of headroom with Pro Tools... if you start pushing it a little bit too hard it's starts squawking like a chicken, if you go too low, it starts squawkin', you have to work within a certain realm otherwise you get zapped either way!" - Tad Donley (2006) -
Unfortunately this Plugin seems to be totally unusable for me.
First off, it's only 32 bit and it crashes the Cubase 6.5 VST bridge when loading the plugin.
I managed to open it with JBridge but at low buffer size it overloads my CPU.
1 Plugin on 1 audiotrack! I usually run shitloads of plugs and samples...
I increased buffer size to the max but it still stutters hopelessly... too bad!
Not gonna be able to check it out!
Trying it out - so far really impressed but I have one complaint with the demo.
You're a little over-protective to not cause people (me) to be annoyed. The demo times out after 10 minutes AND you can't save AND there is a dialog box that pops up up every minute or so to tell you it's a demo (in pro tools at least) which kills the audio and you have to wait for the plugin to come back up to speed...
Sorry for that, we don't mean to annoy anybody! Actually, I hate any form of copy protection, I'd prefer there being none whatsoever, unfortunately the world requires us to have it.
The thing is that the demo does not expire after x days *and* is otherwise fully functional, hence we need to make up for that.
But the nag screen is supposed to be there every 3 minutes, not every minute. Are you sure it is actually 1 minute? If so, that sounds like a bug and we should be fixing it ASAP.
First off, it's only 32 bit and it crashes the Cubase 6.5 VST bridge when loading the plugin.
I managed to open it with JBridge but at low buffer size it overloads my CPU.
1 Plugin on 1 audiotrack! I usually run shitloads of plugs and samples...
I increased buffer size to the max but it still stutters hopelessly... too bad!
Not gonna be able to check it out!
Sorry to hear you're having trouble!
Please note that x64 operation is not supported in v1.5.0, this includes bridging 32bit into a 64bit host. x64 native versions will be around in a little while.
The CPU load is expected to be crazy at low buffer sizes. We recommend a buffer setting of 1024 samples or more. This is because UNVEIL needs to look at 4096 samples of audio before it can do what it does, so if it needs to work with a shorter buffer size it needs to effectively "work overtime".
There are highly complex mathematics involved in making real-time reverb recognition and de-mixing possible *at all* - this is quite literally rocket science! - so a certain amount of CPU load is fully expected. One mono or stereo instance shouldn't bring a modern CPU to it's knees, however. It is probably related to the currently unsupported bridging you're doing.
For example on my 2.8gHz Xeon MacPro I can run about 5 channels of UNVEIL on one core at 44.1kHz.
What are the specs on your machine? At which sample rate was your test scenario?
At any rate, I would presume that the x64 native VST will solve these issues for you!
Please note that x64 operation is not supported in v1.5.0, this includes bridging 32bit into a 64bit host. x64 native versions will be around in a little while.
The CPU load is expected to be crazy at low buffer sizes. We recommend a buffer setting of 1024 samples or more. This is because UNVEIL needs to look at 4096 samples of audio before it can do what it does, so if it needs to work with a shorter buffer size it needs to effectively "work overtime".
There are highly complex mathematics involved in making real-time reverb recognition and de-mixing possible *at all* - this is quite literally rocket science! - so a certain amount of CPU load is fully expected. One mono or stereo instance shouldn't bring a modern CPU to it's knees, however. It is probably related to the currently unsupported bridging you're doing.
For example on my 2.8gHz Xeon MacPro I can run about 5 channels of UNVEIL on one core at 44.1kHz.
What are the specs on your machine? At which sample rate was your test scenario?
At any rate, I would presume that the x64 native VST will solve these issues for you!
Best,
Denis
Hi Denis, an x64 version would be great, that would probably solve my issues.
Your plugin is probably too much for the bridging vst technology.
I've been trying it on a quad core i7 with 8 GB RAM, most settings optimized for audio so I guess that should work usually.
I went up to 2048 for buffer size as that is the max I can choose for the FF800 at 96 KHz.
Sorry for that, we don't mean to annoy anybody! Actually, I hate any form of copy protection, I'd prefer there being none whatsoever, unfortunately the world requires us to have it.
The thing is that the demo does not expire after x days *and* is otherwise fully functional, hence we need to make up for that.
But the nag screen is supposed to be there every 3 minutes, not every minute. Are you sure it is actually 1 minute? If so, that sounds like a bug and we should be fixing it ASAP.
You might be correct - may not be exactly a minute (sorry just frustrated) I've actually never seen a nag screen before in any other plugin... ever! Flux has the same type of demo, do does 2c and others in that they don't expire, but do time out and you can't save which seems to be enough.
Either way - great plug, I'll try to makeup my mind between the nags
You could always process the individual track and then move on to free up cpu couldn't you? I don't really think its for mixing with other plugins all the time if your computer is struggling.
For example - grab a file. . . ooops too much of the room. Add the plugin.Tone the room down to taste , bounce down - save - carry on with the mix.
Of course, the plug is challenging in terms of cost so I'd like to also use it to mix in channel groups can 'be an idea.
The way I mix do not like to bounce audio of the process, you lose the ability to mix variables in.
I was satisfied with what he does but rightly as you say it is actually designed for the purpose of mastering and generally restoring audio.
The CPU load is strongly influenced by two factors: I/O buffer size and sample rate.
WRT to I/O buffer size: we recommend using 1024 samples or more (ideally it'd be 4096 samples as that is the internal buffer size of UV). Shorter buffers increase the CPU load significantly. This is due to the fact that the algorithm needs to look at a certain amount of signal to be able to determine what's reverb and what isn't. So when the I/O buffer is shorter than that, UV needs to process stuff in parallel, increasing the load on the CPU.
Sample rate: well, this one is kind of obvious; more data, more calculations.
Sorry for that, we don't mean to annoy anybody! Actually, I hate any form of copy protection, I'd prefer there being none whatsoever, unfortunately the world requires us to have it.
The thing is that the demo does not expire after x days *and* is otherwise fully functional, hence we need to make up for that.
Look, I mean no offence but your logic is completely twisted. It has been shown time and time again that a too restricted and annoying demo only makes you suffer less sales. Even with your unique tool, if the demo annoys me enough I will NOT support you and purchase the program. Why? First of all it annoys me and I can't be bothered to figure out if I need the program or not. Second, it makes me doubt YOUR ability to run a successful company thus meaning you might go bankrupt soon and I loose an investment in the plugin.
It just doesn't make ANY sense to have such a restricted demo. Just look at 2CAudio and how their crazily restricted demo (silence every 5 minutes or so) got a massive backlash. They made it more lenient and suddenly people actually bothered to test the plugin thoroughly and sing it's praises. Before that there was very little feedback, just a lot of annoyed potential customers.
Many other companies have had the same issues. Tone2 comes to mind as well. All of them that changed for a more humane demo restriction benefited from good user feedback on the actual plugin. The ones that didn't? Well we don't hear from them any more..
Please, I beg you, for your OWN sake, think this through VERY carefully. A person who starts "abusing" the plugin demo for their own gain would never purchase the thing to begin with. No professional person in their right mind uses a demo for rendering short snippets of audio or uses it in a project. They need it? They buy it. It's really as simple as that.
Actually, your restrictive demo WILL promote piracy of your plugins. People will start suggesting downloading a pirated copy instead of the legitimate demo just to test the friggin plugin! (this has happened to other companies before!).
Don't be stupid. Be smart. Make a demo that can actually be demoed properly!
Wow, That's one of the most hardcore self-serving rants I've heard in a long time. And I've heard some self-serving rants on this site because this site is filled with a lot of entitled mofos, but yeah, that one was pretty bad.
I have no problem demoing it like it is. I would say that if you want to have the nag screen every 3 minutes, there's no reason to have to reload the plugin after 10.
Now the VSTi OP-X Pro - that Oberheim VSTi? That's one of the most pathetic ones I've dealt with. Silence every 4 seconds or so. On a synth plug in. That's pretty bad so if you want to rant, you should go rant on that one because that demo is unplayable. This one - Three minutes between nags? Not bad at all.
I'm happy that there's no time limit on the demo because I'm still testing it on stuff to see how much it will benefit me at the moment, so I'm happy that I can take my time.
I wouldn't worry about cracks. The type of people who crack plugs or use cracked plugs aren't intelligent enough to know what to do with a plug this specialized.
Regards,
Frank
__________________
My equipment: A Commodore 64, 2 1541 Disk Drives, Dr T's Music Studio and a Casiotone CT-460.
Never listen to opinions regarding gear. For every 50 nobodies on Gearslutz that say a piece of gear doesn't sound good enough to cut it, I know at least one somebody who is cutting it in NYC with that piece of gear.
Wow, That's one of the most hardcore self-serving rants I've heard in a long time. And I've heard some self-serving rants on this site because this site is filled with a lot of entitled mofos, but yeah, that one was pretty bad.
Oh shut up. I'm using these tools for WORK. I don't have time to give a severely crippled demo any time.
And you call it self entitled??? I actually wrote my post because I CARE about the company creating these unique plugins. I actually took time to write exactly why a severely crippled demo makes absolutely no sense at all.
It's very obvious that you yourself have not a single clue on how to sell stuff so I wont even try to convince you why a crippled demo is a bad idea. There's enough data with a simple google search that shows you just how bad it is for your business to cripple something down to the annoyance level.
Why am I even typing this here? Such a waste of time..
If you can't hear in a three minute stretch of audio if this plug in is doing something beneficial to your track or not, you're probably not the kind of professional people should be working with anyway.
Please calm down guys. No need to have a go at each other. For what it is worth I agree with bmanic and his post is not self serving. He is a knowledgable professoonal who makes a valid point that may actually help the developer in the long run if they listen.
I may actually buy this product. Fits a particular need I have perfectly