All you have to do is get the UAD2's control software to generate you a web link file, which you can then open on any Internet—capable machine. You then download a single authorisation file no matter how many plug—ins you have authorised , transfer that back to the studio machine and drag it onto the control software's desktop icon.
However, this only needs doing once, no matter how many UAD cards you add to your system, and until the end of Universal Audio will transfer any UAD1 plug—in authorisations to UAD2 free of charge. In the Version 5. Pro Tools users will have to wait for their RTAS format, as this isn't yet officially supported, although Universal Audio imply that you may be able to use a limited number of UAD2 plug—ins in Pro Tools if you keep your audio hardware driver's buffer size above samples. For trademark reasons, the guitar amp modelling plug—in Nigel will not be available at all for UAD2, so Universal Audio are currently investigating new guitar—oriented effects possibilities to fill the gap in the product line.
The interface of the control software offers two separate windows, either or both of which can be set to float on top of any other active applications.
In addition, if you've not yet authorised a particular plug—in, you can directly enable that plug—in's 14—day free trial, which starts straight away and allows you to get a feel for which plug—ins you like the sound of before shelling out. One of the cornerstones of Universal Audio's brief for the the new card was that any session with UAD plug—ins should load regardless of which hardware was powering the plug—ins assuming, of course, that there is enough DSP power and the relevant plug—ins are authorised. Although this certainly makes project loading smoother, the down side is that you can't run a plug—in on both cards at the same time, so if you nominate, say, all your s to run on an existing UAD1 and run out of horsepower, you can't simply pop a couple more instances onto a new UAD2 — you have to migrate all the UAD1 instances to UAD2.
Even assuming that this kind of plug—in assignment migration works flawlessly I didn't have access to a UAD1 in the review system to check it out in practice , I reckon most people would get pretty sick of switching plug—in card assignments to accommodate the differing plug—in demands of different projects, and would just use their UAD1 for specific plug—ins where the limitation of constraining their usage to the UAD1's capabilities would be negligible.
Given the leap in processing power that the UAD2 represents, it's not surprising that the plug—in counts advertised on the Universal Audio site are pretty mind—boggling. With a single Quad card, for example, you can run 72 stereo Fairchild compressors, certainly more than any of us are likely to see in hardware form in our lifetimes!
In addition, the new card also offers a special Live Track switch for each plug—in instance, which allows that plug—in to override the system latency and achieve a much lower processing delay for the purposes of live software monitoring. The down side is that your host CPU performance is effectively reduced for each plug—in in Live Track mode, although you don't have to switch all your UAD plug—in instances to Live Track to get the monitoring latency improvements, only those on the live—monitored track, in downstream buses, or in send—effect configurations.
A selection of plug—ins running in Cubase — the hardware equivalents of this little lot alone would far surpass the price of the UAD2 Quad. Working with the latest version of Cubase, I found the Quad card did indeed deliver the plug—in counts Universal Audio have justifiably been bragging about, but only at higher latencies.
For example, the much—trumpeted Nevana setup comprising the filter, EQ and compression blocks of Neve 88RS plug—ins was pushing Cubase's ASIO meter into the red and glitching even at a buffer size of samples, only running stably at At samples I had to reduce the plug—in count to 80 to banish the glitches, while at samples I had to bring it down to around 30 to keep the audio clean. Oddly enough, even when the Cubase ASIO meter was indicating a constant percent load for plug—ins at a buffer size of samples, Windows Task Manager reported only 40 percent host processor usage, fairly evenly split between the four cores of my Phenom CPU, which makes me suspect that some transmission bottleneck is occurring between the card and the host PC.
Searching a few forums turned up a number of other early users who seemed to be encountering similar problems in different sequencers such as Sonar and Logic, so I decided to contact Universal Audio directly for some input on this issue. Their response was to confirm my own experiences that host processor load is both proportional to plug—in count and inversely proportionate to buffer size, and also to say that the v5.
Their recommendation was that users continue to operate with high buffer sizes for mixing work, to maximise plug—in counts. However, my fairly powerful quad—core PC was registering roughly 25 percent on the Cubase ASIO meter for a single UAD2 card running the Nevana setup, even at the highest possible —sample buffer size. If this kind of figure scales up proportionally for multi—card systems, then you may have to be running a fairly rocket—powered computer to access the full power of the new UAD2 platform without glitches, even if you only use powered plug—ins.
Again, though, I wasn't able to test this in practice, with only a single review unit. Furthermore, the Live Track mode puts considerable extra strain on the CPU, thereby limiting your plug—in count further.
For example, even at a buffer size of samples the Nevana setup maxed out Cubase's ASIO meter the moment I switched even one of the plug—ins to Live Track, while the 3—4 percent ASIO—meter load of a single Neve plug—in at a buffer size of samples jumped to around 18 percent when the plug—in was switched to Live Track. Certainly, Live Track does significantly improve monitoring latency in sensitive situations such as vocal overdubbing, where it justifies the extra processing load, but even without it the UAD2 latency seemed small enough to me that I reckon a lot of recording musicians will simply work without Live Track most of the time.
As we were going to press, v5. However, the flip side of this uncertainty is that purchasers can't really know what kind of low—latency performance to expect on their system without installing the card and putting it through its paces, by which time they've already parted with their cash. Compatible with macOS Sierra? Thx in advance ;. UAD stuff works perfectly fine on my macbook with sierra.
It connects to my Twin Duo right away. I haven't noticed any other issues with plugins. Using vst is never a bad idea! And yes 32 Lives does work! BD, what is the version of 32 lives?
Well, this would have been heful as a warning email from UA, instead of the constant reminders that I am running out of time to take advantage of this or that discount on this or that plug in which I already have. Locked out of my system because no one tipped me off, save this site. This is exactly why I think it's important that people regularly voice their gripes about Apple's annual OS policy and how it is effecting your software. Sure nobody likes to hear whining on forums, or sending disgruntled support emails but the reality is that issues like this are only going to become more regular in the future.
I personally think the whole industry is moving into seriously bad territory. Apple forces annual OS updates, developers try and keep up, and stop supporting previous OS's much quicker than they once did. IMO this is a scorched earth approach, and I don't see this heading anywhere but straight to hell I don't see good things ahead when everyone's running around trying to serve Apple when in reality they should be putting them in check Not true!
This upgrade "catastrophe"your experiencing is expected behavior between OS and 3rd party software developers. It is true that Apple releases OS updates more frequently, but that's only because technology as a whole is progressing faster with demand and expectations of more features. Often, developers are invited to beta testing phases and provided with appropriate developer tools to facilitate updating their software for the new OS environment ahead of time. However, due to time, resources and changes that occur during beta testing phases which are heavily communicated to developers btw , 3rd party software developers often choose not to develop during the beta test phases.
Therefore, if YOU rely on 3rd party software, it's YOUR responsibility to check the support page of the software developer software you rely on. Also, to address your other point, it is customary for a 3rd party software developers to only code and develop software for the latest and recent past version of the OS because it would take too much time to recode and develop updates as new features are introduced.
If they did code to all the historic versions of OS, it would take a lot of valuable time and resources as they add new features to their software. So, the moral is, it's important to also try and keep your OS up to date if you want to experience new features from your 3rd party software. TL:DR - Check 3rd party software support site before updating. Welcome to computer-based audio recording guys! This isn't necessarily Apple's fault, and expected behavior when updating into a major OS.
So, on launch day of an OS, you usually want to check any 3rd party software developers website to assure compatibility before updating. Make this a routine when doing a major OS upgrade. I think their answer on their site to sierra compatibility is lame. They still have the line about pre release and beta. We are in fact talking about bit processing. Sorry, folks. You still have to rely on good microphones and good mic placement. And lastly, you need top-of-the-line mixing and mastering effects. It can also enable computers to crunch twice the data per clock cycle, which can dramatically speed up numeric calculations and other tasks.
Leopard is also a bit operating system. This will show you what applications are running on your Mac under the Process Name column. Find your DAW application on this list and then look on the far right where you should see the Kind category column. One of the greatest advantages of using a bit version of Windows is the ability to access physical memory RAM that is above the 4-gigabyte GB range.
Many people are under the impression that a bit OS will make their the new bit updates for Mac and Windows OS and host applications and exactly what it is (See the UAD-2 DSP Accelerator Cards and the UAD Powered Plug-Ins-!). When UAD software is installed, UAD plug-ins are copied to the VST (64bit) Mac. VST /Library/Audio/Plug-Ins/VST/Powered Plug-Ins.
Note: This physical memory is not addressable by bit versions of Windows Vista. This feature of the bit versions of Windows is a welcome improvement for those who want to use large VI Virtual Instrument libraries, which take advantage of the larger memory sizes.