• SONAR
  • CbB First Impressions (p.8)
2018/04/22 19:27:20
bapu
Ya 
2018/04/22 21:44:53
paulo
Blades
I don't know if this addresses the sampletank issue, but as someone who has at least partially moved over to studio one, which does not see 32 plugins, and as one who only owned sampletank 2.5, I have installed the sampletank 3 free version that is made for importing other libraries (I think it's called custom shop) and successfully read in all of my sampletank and sonic synth 2 libraries (a non destructive, converted duplicate) and it works great in both Splat and studio one. I have cbb installed, so I can definitely check there as well, though I am nearly certain it works there. And it has a better gui with a scroll wheel that actually works.

Does that help at all?



I guess I could try that if/when the new version offers a more significant incentive than it does at the moment. I'm more concerned with Miroslav than Sampletank tbh, so I'm not sure if that would work the same - I think I read somewhere that it doesn't, but it's worth bearing in mind. Thanks for the suggestion.
2018/04/23 15:34:35
RexRed
The problem I see with revamping Sonitus is that, it has already been done in many cases. I think the best thing would be to take the best of these devices and try and add all the various features to one device that does it all. A device that has real-time spectrum analysis, side chains, tons of presets, there are so many devices that only have a part of the whole picture. Make one mother of all l reverb units and incorporate the best features. One Reverb, One Eq and One Compressor, One stereo widener with several visualizations, One multi-band compressor, transient editor make them useable on both track and master bus. Rather than redundant products that each do different things, have one product for each that does everything and keep expanding on them with new iterations. I think of Wave brand plugins and they have so much redundancy and talk about old interfaces, most of the devices have no real-time spectrum analysis. Some multi-track visualizations with color taps for each track would be nice too.
 
The problems seems that just adding a giant reverb app would require adding a CPU and memory hog to each track.
 
Perhaps if there was a way to shut off main features so you only load the parts resident that you need might be a way of minimizing the load.
 
It is easy to get lost in a myriad of redundant plugins, we are better served by a focus on making certain plugins as full featured as possible while still keeping them modular. 
 
A prime example are the two compressors in prochannel. Why two? It would be easy to combine all the features of both into one. Make the one switchable for mastering or tracking.
 
Furthermore, the prochannel EQ, why even have that when there is the LP EQ that is much more full featured? Make the LP EQ modular where you can shut off certain features so it can be used for both tracking or mastering. Then there is only one global EQ to worry about developing. Make it smart so if you insert it into a track it switches to simple mode and if you insert it into a master bus it switches to full-featured mode.
My point is cut out the redundancy.
 
Waves plugins are a prime example, how many different EQs and compressors do they have (over a thousand)? Do they really each have a different signature and colorization? Or is that just a bunch of hype and bragging rights? In my experience an EQ is an EQ. I might be wrong about this but a cheap EQ in the right hands with the right pair of ears can go a long way. Generally I rely on the spectrum analysis and my ears they all seem to do basically the same thing. 
 
There are some plugins that have neat features so add them to the main plugin of this type. Stop making redundant plugins. Make a well focused and comprehensive suite to rule them all, build them into the prochannel.
2018/04/23 16:08:25
mettelus
The only downside to such is the CPU hit for installing the "be all, end all" monster on every FX point. Sort of like dropping Ozone into ever bin. Modularity is nice, which is the concept to the Ozone Advanced, but they are still sequentially chained and can get a mess if isolating bands for certain chains (signal path can be a nightmare if you leave the linear chain concept). Melda's MXXX boasts light weight CPU hits, but I have not stress tested that, and is probably the epitome of modularization in a plug-in.

Bottom line is that 3rd party options exist today that are already top shelf. Cakewalk would be in a tail chase with this, and focus should be as a host. Conversely, some of the exceptional VST coders would not even consider making a host.
2018/04/23 16:46:11
chris.r
Noooooooooooo!! don't get rid of the QuadQurve.... it's excellent.
 
 
:)
2018/04/23 16:59:48
michaelhanson
chris.r
Noooooooooooo!! don't get rid of the QuadQurve.... it's excellent.
 
 
:)


+1000 !!!!
2018/04/23 17:08:27
wetdentist
i have switched over to CbB & love it.  however, when i need to dither down to 16 bit audio, i go back to SPLAT so that i can use the Powr-3 dithering option.
2018/04/23 18:11:52
Muziekschuur at home
Why does Rapture Pro run in demo mode in Sonar Bandlab? 
2018/04/24 03:48:03
RexRed
I use quadcurve for every track but if it were to be switched out for the LP EQ and if the LP EQ had a convenient low bandwidth switch (which I think it already does), I think I would be better served. LP EQ is a better product and if any EQ plugin designed for Cakewalk should be further developed it should be there... Also, with the intel I9 that I have, I am not really worried about reaching the ceiling of my processor by adding CPU hog plugins. My most complex songs barely even move the indicator lights on all 12 cores. Load balancing works really fantastic! It is nice to see that plug-in load balancing made it into CbB... :)
2018/04/24 05:10:03
Kamikaze
The vast majority of Sonar and Bandlab users will not be n I9's, and this wn't change for a long time. 
 
 
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account