|
| quote: | Originally posted by DJ RANN
Eric, when you get a moment, could you put up a mini review with all the pros and cons. After switching to mac, I miss of lot of my PC VSTs and this seems like it could do the trick. |
Sure.
Pros:
- Basically just a computer in a box, is not limited to just manufacturers plugins in the same way as a WAVES APA box is. Runs a customized version of Linux with WINE.
- Can run a maximum of 16 VST instruments and 57 effects plugins, assuming you don't max out the CPU.
- Cross-grade available for plugins you already own.
- Most unsupported plugins will work if they adhere to the Windows VST 2.0 standard.
- Audio and MIDI data can be transferred over a standard Gigabit ethernet.
- Includes the Uniwire plugin which allows you to use any plugin or effect on the box just like a standard VST instrument or effect including full delay compensation just like any other native plug.
- Has separate MIDI In/Out/Thru and unbalanced audio outs so it can be used in the same manner as a hardware synth
- Support S/PDIF and ADAT digital audio
- Extremely stable.
- Has a dedicated user interface that can be accessed from a different workstation via VNC remote control software OR can plug in a standard monitor/keyboard and mouse.
- List of supported plugins is huge and from well-respected manufacturers. NI, PSP, CamelAudio, Sonalksis, Big Fish Audio, and loads more. NI support in particular is extensive.
- All processing is done on the box. The only overhead on the host DAW is passing network packets back and forth to the unit. A trivial task for most workstations.
- Nearly all the available power in the machine is available for your instruments and effects. Since Linux is such low consumer of computer resources, you have 98+% of your resources available for processing tasks, where as on some Windows computers anywhere from 5-10% of the available resources is taken up just running the operating system and various services, depending on how powerful the machine is and what is running on it. In addition, a lot of services take up CPU temporarily running scheduled tasks and background processes, such as Windows Update checking for updates or Antivirus software performing a check. With the Receptor you know the only tasks running are a very basic operating system. Its not constantly performing background tasks.
Cons:
- Automation of plugin parameters must be done with MIDI CC commands.
- List of supported plugins does not always include the latest versions. Until recently, there was only support for previous generation NI plugins. FM7 vs. FM8, Absynth 3 vs. 4, etc. Direct Install has made the current versions of these plugins available.
- Not every plugin with every manufacturer is "officially" supported. For example, only Albino, Blue and Predator are supported from the Rob Papen family, however, there are loads of people who have installed "unsupported" plugins with success.
- Requires an elevated level of technical understanding about computers and networking because loading software on the unit requires you to mount the drive from the network and drag files to it. Not terribly difficult for most of us, but may intimidate some.
- iLok copy protection scheme. This can be a bit fiddly if you are not used to it and you must unplug the iLok from the unit and plug it into another computer to get the iLok authorizations on to the key, then plug it back into the Receptor. Again, not a huge deal, but a bit more hassle than a native plugin.
- Learning curve is a bit steep. I spent a good bit of time trying to figure out how to do one thing or another. The workflow of using the unit is not always real intuitive, but a quick look at the manual will usually tell you what you need to know.
- Expensive.
All in all, it fills a huge need for me personally, mainly because I run nearly all software, and I hate to have to freeze things because I'm always making a change here and there. Even with a Quad Core Mac, it is still fairly easy to max out the CPU's when you get multiple instances of CPU hungry plugins running. NI stuff, Sculpture, Waves plugs and Space Designer are just a few examples of plugins that can eat up a ton of resources, but I use them a lot because they sound good. This is especially a problem towards the end of the track creation process where you have the most stuff running.
In addition, the ability to run those Windows only VST's is a huge advantage for a Mac user, where as users with Windows PC's do not have this problem.
So I hope this helps out. Feel free to PM me if you have any other questions or need any help!
|
