faun2500 wrote:And that is why I'm not touching it!
Sorry, I know we are all for supporting each other and the dev's but I feel this is their job to do this and I am waiting for that!
I guess I will see which dev is quick to respond and update their programs. This will influence the purchase of future libraries for me.
It truly is easy and safe. Just make a backup of your very small Neb program folder and patch away. The very few that didn't work for me were actually one's that already had the features that I was trying to add, like the HP sidechain on a few compressors. And while I understand your hesitation, I personally still feel that their time is better spent doing the things that we CAN'T do ourselves, like develope more cool and amazing sounding libraries. If these libraries cost much more, I would expect more from them. But if you do the math and figure out how much these devs actually make for their time, you may see that we are already getting an incredible bargain. I for one am glad that I took the 10 minutes it took for me to patch ALL of my preamp libraries and ALL of my compressor libraries and now have better functionality for zero additional money! I like that!
Thanks again Giancarlo and any other Acustica dev, by the way!!
it's safe. to be sure, you probably should go ahead and back up any n2ps you are going to patch first. those files are small so it's absolutely no deal at all to copy all of those to someplace safe, then patch away. with backups the risk is pretty much 0.
the only issue with gdrv, in my opinion, is that it makes it tempting to keep raising gain until you get nasty distortion from overloading nebula- unless you have neb's built in over protection turned on. that distortion can seem to just come out of nowhere (after you pass highest point that was actually sampled).
one thing i think it SHOULD do, is put to rest any complaints about certain programs/sets not being released with the 18DBFS=0vu standard (or any other). for people who batch process stuff before mixing and rely on that standard, what they can do with anything they have/want to use that doesn't use that standard, is adjust gdrv to their taste with that effect- using their EARS. then when they get a good result with audio going in at the levels they intend to use when batch processing, they can just save that preset. so now whenever they do batch, they've personally 'calibrated' that preset to the level that sounded best to them earlier....
i also have to say that richie43 has a great point about people doing things that they can do, leaving devs to spend their time elsewhere like developing new ideas. i say this even though i personally have made an effort to (slowly) go back and update most of my older stuff to include things like gdrv. that's just my personal choice to do that, and i probably won't do that every time some new thing like this comes out. there are always plenty of other things to do as a developer, and a lot of those things are more time consuming than using a simple patch like this, and may actually make new progress in other directions.
these small patches are simple to apply, but for the devs it becomes more of a task to update a whole back catalog when there is always a full plate of other things to do.