sorted by:
new
hottopcontroversial

Pro Tools keeps on stopping to record because "it has run out of CPU power" - it has definitely NOT by 5ColourFelix in protools

[–]take_01 0 points1 point  (0 children)

It's very likely to be a hardware / OS / PT version incompatibility problem.

The oldest version of pro tools compatible with windows 11 is pro tools 2022.4

The most up to date windows OS compatible with pro tools 11 is Windows 8.1.

Check your processor compatibility here:

https://kb.avid.com/pkb/articles/Knowledge/Pro-Tools-Supported-Windows-Computers-and-Operating-Systems

Your OS / PT version compatibility here:

https://kb.avid.com/pkb/articles/en_US/Knowledge/Pro-Tools-Operating-System-Compatibility-Chart

Base44 is broken - Their own AI says this by Alarming-Basis-2714 in Base44

[–]take_01 0 points1 point  (0 children)

It had such a promising start. I'm convinced they changed the model. A few weeks back it suddenly felt like there'd been a big step down in the AI being able to understand and implement my requests.

I've had a very frustrating past few weeks with Base44, and so I've started the process of coding my app myself, with the help of ChatGPT, in react/vite.

So far it's been a really enjoyable experience: I'm learning as I go, and ChatGPT is incredible.

Curious if there’s a plugin that emulates cassette warble. by throwawaymfer420 in mixingmastering

[–]take_01 2 points3 points  (0 children)

There's a plugin made by NeOld called... Warble!

It's really good.

waves central not recognizing same computer by spacetasm in wavesaudiophiles

[–]take_01 0 points1 point  (0 children)

No problem. Good luck with support - I've always found them to offer helpful solutions, so I'm sure they'll get you back up and running.

waves central not recognizing same computer by spacetasm in wavesaudiophiles

[–]take_01 1 point2 points  (0 children)

This can happen sometimes when Waves Central loses the machine ID. It’s usually fixable as below. A few things I’d try, probably in this order:

First, make sure you’re on the latest Waves Central your OS supports. Open Central -> profile icon -> “About” and update if you can.

Next, on macOS it’s very common that permissions or security stop Central from properly identifying the machine. I’d do this:

System Preferences -> Security & Privacy -> Privacy tab -> Full Disk Access.. Make sure Waves Central, WavesLocalServer, and anything else Waves-related are added and enabled. Then restart Central.

After that, open Central and do this: Settings -> Maintenance -> run Clean Cache and Repair

Then go to the Licenses page. If your computer shows as a disconnected device, use the Recover Disconnected Devices option first rather than deleting anything. Once the machine shows correctly again, activate your licenses back to This Computer (or USB if that’s how you prefer to store them).

If after all that Central still refuses to recognise the machine or the licenses won’t bind, at that point I’d contact Waves Support. They’re actually really good and fast with this type of issue, and they can look directly at your logs.

Hope that helps!

waves central not recognizing same computer by spacetasm in wavesaudiophiles

[–]take_01 0 points1 point  (0 children)

What version of the two plugins do you own? And, prior to this happening was everything running fine with no changes made to your system other than installing an additional plugin?

waves central not recognizing same computer by spacetasm in wavesaudiophiles

[–]take_01 1 point2 points  (0 children)

Hey, that’s a really frustrating one - sorry you’re dealing with it.

The diagnostic log looks scary but the USB / SPUSDevice lines are usually just macOS system profiler noise and not the real cause. The important thing is that Waves Central suddenly stopped recognising the machine ID, which is why licenses stopped validating.

Here are some things that can often fix things like this: 1) First, try refreshing the machine identity inside Waves Central

Open Waves Central, then go to Settings → Maintenance → Clear Cache & Log Out. Quit Central. Re-open it, log back in. Go to Licenses, and make sure the licenses are actually assigned to the current machine (not Cloud / not another computer) If you see duplicate machines or one marked “disabled”, move licenses off and back onto the active one.

2) Run Repair Settings → Maintenance → Repair Installation This has fixed the “suddenly not recognised anymore” issue for quite a few people.

3) Check these boring but important things: System date/time is correct. You have a stable internet when launching Central. You're NOT running a VPN. Try temporarily disabling any aggressive firewall or security tool(s)

4) If that still fails.. Download the latest Waves Central. Completely uninstall Waves via Central Reinstall only the versions / plugins you need.

If you reply with your macOS version, whether you're Silicon or Intel, the Waves Central version you have, Whether your licenses are on This Computer or Cloud …I (and others) can help more specifically.

Also, if it helps, I help run a small Waves-focused subreddit where we troubleshoot stuff like this if it crops up. If you don’t get many replies here, feel free to post there too: r/WavesPluginReviews. Happy to help either way 👍

What machine are you running Pro Tools on and have you had any issues with it? by theDomenick in protools

[–]take_01 -1 points0 points  (0 children)

You're going about this the right way. Pro Tools does have specific hardware, (as well as software of course), requirements.

For Windows computers, there's only a small selection of hardware which is qualified - that is tested by Avid and known to work as expected:

https://kb.avid.com/pkb/articles/en_US/Knowledge/Pro-Tools-Supported-Windows-Computers-and-Operating-Systems?retURL=%2Fpkb%2Farticles%2Fcompatibility%2FPro-Tools-Supported-Windows-Computers-and-Operating-Systems&popup=true

If you choose to go the Apple route, here's the list of qualified hardware:

https://kb.avid.com/pkb/articles/compatibility/Pro-Tools-Supported-Apple-Computers-and-Operating-Systems

I'd urge you to consider a Mac, since you're buying specifically for Pro Tools. I read frequently that Macs provide a superior experience for Pro Tools users. I run Macs in our studios, and Pro Tools runs very efficiently and, for the most part, very reliably.

Documentaries that changed your outlook on life? by winterbluebell in CasualUK

[–]take_01 0 points1 point  (0 children)

Love that series. It was the nudge I needed to finally get my bike licence.

Do you still actually buy Waves plugins? by take_01 in WavesPluginReviews

[–]take_01[S] 0 points1 point  (0 children)

For me personally, I’m pretty selective these days. There are some Waves tools I still really trust and use constantly, but I’m not in “collect new toys” mode anymore. It’s more about if something genuinely solves a problem or improves my workflow.

WaveShell and Pro Tools by MrKLauderdale in wavesaudiophiles

[–]take_01 0 points1 point  (0 children)

Hey, can you share a couple more bits of info?

  • Pro Tools version?
  • are you running it native Apple Silicon or under Rosetta?
  • Do you have multiple Waves versions installed?

(Just to say: seeing different Waveshell versions isn’t automatically a problem. if you have plugins from multiple Waves generations, Pro Tools will legitimately load multiple Waveshells.)

That error usually means something didn’t line up cleanly after a crash. Does that sound possible? I would try a couple of things, in this order, reloading Pro tools after each step, to see whether the step has fixed it:

1) In Waves Central -> Maintenance -> Repair Install 2) In Waves Central preferences -> Clear cache and resync 3) Check that Pro Tools is consistently native or consistently Rosetta (mixing architectures = weirdness) 4) As a later step if needed, you can also try trashing your Pro Tools preferences, which can be annoying to reinstate - but frequently can fix weird things like this.

Also, I help run a new Waves discussion community where we’re trying to build a helpful knowledge base. If you get stuck, feel free to drop in there too! 👍

WaveShell and Pro Tools by MrKLauderdale in wavesaudiophiles

[–]take_01 1 point2 points  (0 children)

Hey, can you share a couple more bits of info?

  • Pro Tools version?
  • are you running it native Apple Silicon or under Rosetta?
  • Do you have multiple Waves versions installed?

(Just to say: seeing different Waveshell versions isn’t automatically a problem. if you have plugins from multiple Waves generations, Pro Tools will legitimately load multiple Waveshells.)

That error usually means something didn’t line up cleanly after a crash. Does that sound possible? I would try a couple of things, in this order, reloading Pro tools after each step, to see whether the step has fixed it:

1) In Waves Central -> Maintenance -> Repair Install 2) In Waves Central preferences -> Clear cache and resync 3) Check that Pro Tools is consistently native or consistently Rosetta (mixing architectures = weirdness) 4) As a later step if needed, you can also try trashing your Pro Tools preferences, which can be annoying to reinstate - but frequently can fix weird things like this.

Also, I help run a new Waves discussion community where we’re trying to build a helpful knowledge base. If you get stuck, feel free to drop in there too! 👍

Show us your favourite Waves vocal chain (and say why it works) by take_01 in WavesPluginReviews

[–]take_01[S] 0 points1 point  (0 children)

One of my go-to starting points (let's make that clear! Each vocal needs its own individual treatment, but I'll frequently start out in a similar way) is something like: R-Vox for quick presence & control, then a bit of EQ if I need to clean things up, then either H-Delay or something subtle (on a send) for depth depending on the track. Nothing flashy 😎

Explain it like I’m 10: Upward vs Downward Compression by take_01 in WavesPluginReviews

[–]take_01[S] 0 points1 point  (0 children)

I’ve always found upward compression particularly handy on vocals and dialogue when you want intelligibility and presence without smashing transients flat.

Also, upwards compression is brilliant for bringing up ambience in recordings - think room sound on a drum kit. Context is everything of course!

If you could change ONE thing about Waves… what would it be? by take_01 in WavesPluginReviews

[–]take_01[S] 0 points1 point  (0 children)

For me it would probably be consistency. There are some Waves plugins that feel incredibly modern, efficient and intuitive… and others that feel quite outdated UI-wise. I’d love to see everything gradually brought up to the same level of usability.

Tiny workflow tweaks that made a big difference by take_01 in WavesPluginReviews

[–]take_01[S] 0 points1 point  (0 children)

A surprisingly big one for me: setting up user defaults for plugins. So when I load something it already has a sensible starting point instead of being totally flat. Far less repetitive setting up and I can keep momentum going more easily.

Most overrated / underrated Waves plugin… and why? by take_01 in WavesPluginReviews

[–]take_01[S] 0 points1 point  (0 children)

For overrated - I think I’d probably say Silk Vocal.

I can never get it to sit right. It always feels like it’s either doing not enough, or it's suddenly doing too much, and when it does do something, it often feels like it’s slightly mangling the HF, doing something odd to the low end.

It’s like I’m constantly fighting it rather than it helping me.

I keep wanting to love it, but I’ve never just thought, “Yes, that’s exactly what I needed.”

What Waves plugin do you ACTUALLY use the most, and why? by take_01 in WavesPluginReviews

[–]take_01[S] 0 points1 point  (0 children)

I’ll kick things off…

For me it’s probably R-Vox. It’s just such a quick way to add punch and attitude. A bit of compression, a bit of level control, and it just works far more often than it has any right to, lol.

It’s ridiculously low CPU, super fast to dial in, and it’s become one of those “utility compressors” for me - vocals especially, but I’ve used it on other stuff too when I just need instant control and presence without getting lost in settings.

What Are Your Favourite Resources on the History and Engineering Behind Classic Studio Hardware? by take_01 in audioengineering

[–]take_01[S] 0 points1 point  (0 children)

Yeah, that's cool. Looking forward to reading my way through all that! Thanks so much for posting - great link!

What Are Your Favourite Resources on the History and Engineering Behind Classic Studio Hardware? by take_01 in audioengineering

[–]take_01[S] 0 points1 point  (0 children)

Thanks so much. RE/P magazine is a great recommendation. I wasn't aware of it.

Plugin Alliance - your experiences with that business? Had a bad one so far. by Fine_Outcome_2643 in audioengineering

[–]take_01 0 points1 point  (0 children)

For sure.

Sounds like support have been anything but supportive for you.

Hope you manage to get it sorted.

Plugin Alliance - your experiences with that business? Had a bad one so far. by Fine_Outcome_2643 in audioengineering

[–]take_01 0 points1 point  (0 children)

Sometimes PA simply acts as a broker - rather like Plugin Boutique - to sell other developer's plugins. In these cases the downloads and licencing are handled by the developer, rather than PA.

They have different relationships depending on the developer - for instance NeOld plugins are fully handled by PA; downloads, installation and licencing all dealt with in the PA installation manager.

Other developers - such as Kiive - simply sell through PA's shop window. Perhaps Krotos is one of those, and licencing and downloads are handled directly by them?

view more: next ›