but i would go as far as saying i'll never give that company another cent.
even the several waves plugins i own go unused due to hard feelings.
it's taken me just over 20 years of using plugins to end up with a palette of colours i'm pretty happy with... companies who make all these NFR restrictions, and companies with convoluted authorisation and transfer systems - I don't care how good you are at coding, you eat balls and you f**king SUCK.
I think I've spent enough money to be allowed a little attitude leeway.
thousands of dollars of software devalued and not for resale. by design. ass munchers.
plexuss wrote: ↑Mon Oct 07, 2019 4:01 amThis is excellent advice. Learn to know when you are better off using something you know vs trying to work with something that isn't working out. then go back and do test sessions with the tools that were challenging and try and figure them out. sometimes you find tools that just dont work for you and can eliminated. as a side note, but relevant, this is why I personally prefer a flexible transfer policy over NFR (and high transfer fees) because it takes me time to determine if I'll use a tool on an ongoing basis. I dont often buy NFR tools unless I fully expect to not sell it or sell it for a large loss as with high transfer fees. This is why I no longer find myself buying Waves products anymore.jochicago wrote: ↑Sun Oct 06, 2019 4:40 pm I said this in a different conversation, but I think the trick is to separate plugin exploration from actual music making time.
So to learn and explore set up a test session and have fun with plugins. But when you are making music, decide upfront to only use stuff you already know. This allows you to move at good pace and get things done, without letting plugin experimentation and paralysis take over.