I always use the modern setting, really opens the track up and adds that extra bit of character and 3d-ness. I used to use the Slate a lot but I prefer the CTC-1 to be honest. I am very curious about the Fat Channel stuff but it is pretty pricey to buy the bundles outright.
if you already own Gold like I do, there really is no point since anything else I would want is not in the program. I looked at the Waves Flex program and well. I hear great things about it and I am hoping it could help with my constant obsessing over getting new plugins knowing I am already spending money every month on plugins already. probably me "overcooking" it but that seemed to be the only way I could actually tell any difference between using it or not.Ĭurious about people's thoughts on the Slate program in general as well if anyone would like to share. seemed to always just completely collapse my stereo field.
I have Waves NLS and when the mood strikes I use that over Console Shaper because my limited playing-around with C.S. Has anyone compared their VCC to the Console Shaper and would like to share their thoughts? I know they function differently (plugin vs integrated into the mix engine) but the VCC seems to get a lot of praise. But then we host a huge range of third-party plugins if you want to use them.I'm kinda on the fence and waffling back and forth about doing the Slate Everything Bundle subscription for $15 a month.
SLATE VCC ON MIXBUS FULL
This is why we provide a full suite of mixing tools inside Mixbus, so you don't need to use plugins.
SLATE VCC ON MIXBUS SOFTWARE
It's worth noting that no other software industry ( video-editing, image-editing, web-design, whatever ) allows this kind of cross-host, cross-platform plugin concept. The drawback is that this limits the number of plugins to a much smaller choice, limits freeware/educational developers, and (in general) they cost more. ProTools users have a kind of advantage here, because ProTools recently ditched all the old plugin frameworks and demanded that all their plugins use the new AAX format, which has much tighter rules. So we only make changes if we can determine "for sure" that we are not following the published spec and/or industry-accepted practices. Similarly, if we change our code/compiler to accommodate a specific plugin, it could affect thousands of other plugins that we know work. You can't expect plugin manufacturers to change their ways for us, because if they make any changes, it could affect hundreds or thousands of users on other DAWs. Many plugin developers know these details, but some don't. This means that, if an application loads 2 plugins, and they both have a function called "ShowWindow()" then it is undefined which function will get used, and hilarity/calamity ensues. Specifically, the "Cocoa" framework which is used to open plugins uses a single namespace. Some OS's, like newer Mac, are actually plugin-antagonistic. Plugins that failed horribly in your other DAW might work great in Mixbus. This is true of any DAW, not just Mixbus. MOST will work but you'll have to test on your system. For these reasons, it is not practical to expect every third-party plugins to work. Furthermore, every plugin wants to "push the envelope" and push the formats to the very limits of what they were design to do. It is (unfortunately) left up to the developers to guess which compiler, libraries, features and functions they should implement in their plugins. However there are many variables ( such as compiler versions and libraries ) which are not defined by the specification. We do our best to follow the VST/AudioUnit specifications. LOADS BUT DOES NO PASS FX THRU, DRY SIGNAL ONLY Antares AVOX Evo Vocal Toolkit
SLATE VCC ON MIXBUS PSP
Nealrly The Entire PSP Suite (~30 plug-ins) WORKS Spitfire Audio Orchestral Grand Piano WORKS IK Multimedia - effects and samplers As I test each plugin I will mark it (or its manufacturer group) as WORKS.
0 kommentar(er)
