Jump to content

KoreyCreative

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by KoreyCreative

  1. I would be very worried. https://blog.native-instruments.com/native-instruments-brand-news/ We’re working towards a future where you can: Use one unified login for your accounts across our brands, so you don’t have to remember multiple sets of login details Utilize Native Access as the preferred destination for installing and authenticating a broader range of products, reducing the need for multiple product installation tools Get access to one Customer Care center to get the support you need, across all product lines Visit a one-stop Shop and discover all the products across our brands, including all your loyalty offers and upgrades in one place Explore more tightly connected experiences and technologies across our products Honestly, I don't know where to voice concerns about this. This will cripple my usage of Plugin Alliance if they put them in that dumb a s s Native Access program. Side topic, why do these forums censor and/ or block the word a s s, like wtf space karens, grow up.
  2. Yep, You're absolutely correct. The developers have also done heavy work for Steinberg as to why Studio One is similar to Cubase.
  3. Oh no, not a problem. I see the confusion here and it's already been addressed so no need to delve more into it. Yeah, Presonus aren't at all good at updating and/ or fixing bugs. I think it's because everything coded is outsourced. Every Time I've contacted support it's always the same. Thanks for the steps on recreating the bug. I've sent this to the development team and you should see it in the patch notes at some point bla bla bla. It took a year for the side-chain compensation bug to get fixed. From Studio One 5.0 to 5.2.1 that bug was just there, mad that sucked. Like Studio One 4 was a tank, never had issues, but then someone just started killing what made Studio One great. I honestly have no nope in Studio One now since Presonus merged with Fender. I could be wrong, but I've completed a Studio One survey recently and one of the questions was quite odd. The survey was asking about how you use Studio One and what main features do you use, but then suddenly asked, " Do you use a Fender Guitar" LOL. If I didn't have access to Sample One for a sampler, I think I honestly would be using Native Instruments Battery 4. It works and gets the job done.
  4. Hello Esteban Villanova I've used Native Instruments Battery, Kontakt 5, 6 and 7, Presonus Impact, Impact XT, Sample One, Loopmasters Loopcloud 4, 5, 6, FL Studio, ADSR Player, Waves CR8 and I've found Presonus Impact XT and/ or Sample One (Studio One 5) to work better for my workflow. I personally didn't like Ableton, Cubase and the last time I used Reason was back in 2007 and never tried Digital Performer. Each their own I always say. I'm not in the music production to be brand loyal, just in it to make music. Whatever gets the job done, works for me. I don't doubt that Presonus Studio One's Sample One could have bugs as I've noticed them in the past, but can't think of any that affect me personally at the moment.
  5. I use Sample One and Impact XT from Studio One 5.6 professional. I also use loopcloud 4 (it's old), but allows me to find samples with ease and drag and drop into the DAW.
  6. Hello, Ohh, my bad. My reply wasn't a message of intent, but my opinion as to why I don't use Waves CR8. You stated your opinion, just sharing mine.
  7. To each their own, but I absolutely won't use a sampler that uses 1GB (plus) of RAM per-intense. Just sets up issues down the road when opening old projects. I have 32GB in my W11 machine and still wouldn't use it. It's an unnecessary use of system resources. Waves audio has the money to fix it, but the issue could be they're trying to pay the developers $29.99... Okay, weak sarcasm at Waves, but still the plugin in my eyes shouldn't use 1GB of RAM. Normally I wouldn't care about the updating process for a virtual plugin, but with Waves plugins being directly linked to an update service model, I'm very cautious of what I use in productions.
  8. I wasn't aware of this, thanks for sharing. Yeah with how poorly Spitfire treated Christian Henson with this, I'm for sure doing a chargeback on my card and looking at different sample companies altogether.
  9. Funny, but also a really good question. Once I found out it was using that 1GB RAM per-instance, I messaged Waves audio and they stated it was "by-design". I immediately uninstalled and stated on their forums it was my opinion their design was terrible.
×
×
  • Create New...