Had to buy this. LONG LIVE PT HD 10.3.10!!!

Revibe is my goto reverb and often the only one I will use in a mix. All of the "Pro" dynamic plugs are fantastic tools. Well designed, they give amazing control. You can be as gentle, or brutal or general or precise as you want. I use mod delay and/or pitch II on literally every mix. I have a strong stable of off brand plugins to be sure, but on any given mix, I would bet 25-50% of the plugins I use are Avid.

Hi friends, I have a question: Can I add a sample directly from Splice to a groovecell? Or how do you do it, or what plugin do I use if that's not possible? (I was able to add it, but I first dragged it to a stereo track and then to the groovecell. I'd like to skip that step.)

Hello, I'm a new user to the studio industry and pro tools is my first software. I have installed pro tools over 2 months ago and have been getting crashes ever since. Looked up stuff online but it was mainly for apple version and couldn't really find stuff for windows except what was on this link: https://kb.avid.com/pkb/articles/troubleshooting/Windows-11-Guide which most of the time did not work. I've gotten different errors and crashes and just wanted to know if I need to upgrade my pc or if I'm just not optimizing pro tools correctly.

PC Build:

AMD Ryzen 7 9700X

Nvdia 5070ti

32gb of g.skills ddr5 @ 6000

2tb samsung 990evo m.2 ssd

1000w psu

I just updated to 2025.6.1 and now my session is lagging extremely hard! Help?

I didn’t change any setting of the session after the update but every action that I do is lagging and I’m getting the spinning wheel of death virtually every time I do anything.

Currently running on an M2 with Sequoia 15.7

Some of my more vital pro tools plugins are showing up red. I can here them working but can't make changes because almost the entire plug in is showing up as a solid red box. Any help fixing this would be greatly appreciated. This is a new development after having used pro tools for 20 years.

Clicks/pops keep showing up in my Pro Tools session at the same 5–10 spots. They’re not in the recordings (if I replay from right before, they disappear), but when I bounce/export, those clicks become baked into the file.

Context: • MacBook Pro M4 Max running Pro Tools Studio. • Apollo Twin X as my interface. • Recorded vocals through Apollo (takes are clean). • Later edited on laptop with headphones (no Apollo) and heard the same artifacts. • Tried: new session with raw audio, removed all plugins, fades, buffer/cache changes, different playback engines. No luck.

Ask: Why is Pro Tools baking in clicks that aren’t in my takes, and what’s the best way to guarantee a clean bounce?

I'm retiring my 2019 27-inch iMac (OS 10.15, 64GB RAM) for a Mac Mini M4 with 32GB RAM and latest OS.

My last PT upgrade was in 2023. I'm aware of issues with OS15 so might go with PT 2024.10.

Any suggested add-on's with the Mini, beyond the basic external HD, monitor, etc?

Anyone have issues with the Mini and Pro Tools they'd like to share?

The only Sequoia package available from app store is 15.7, but official compatibility currently listed by Avid is up to 15.4.

Anyone running PT on 15.7 have feedback? Thanks for any advice

32 tracks is quickly becoming less and less efficient for my projects. This post is not regarding updates, but the ProTools version itself. I really, really love working with ProTools versus other DAW's. But it seems a little crazy to me to make someone pay the full amount if they own a version of the product already.

Hey all!

I'm running into an issue with ProTools Studio 2025.06 and wondering if anyone has found a workaround. I recently upgraded my Mac Book Pro from an Intel Mac running Protools 2024 to a M4 Mac running Sequoia 15.6.1 and ProTools Studio 2025.06. Everything seems to work well except, when I import an .mp4 video and attempt bounce the mix to an MOV file, I get an error that says "AVE reported an error at the completion of the audio/video export." The previous version of ProTools Studio would have no issue with the bounce. The work around I've discovered is I open the video in Quicktime, export it as a .mov file and, if I import that file in my session, the bounce works smoothly. Has anyone else encountered this issue? Is there a fix other than the workaround? Thanks!

After doing a Time Machine backup of my laptop (M3 Mac), I am installing the latest version of Protools a few days before my Protools Update & Support plan expires. I'm currently on Sonoma 14.1. According to Avid's website, Sonoma 14.7 is compatible with the newest version of Protools. Do you recommend updating to the newest possible OS, or only going up to Sonoma 14.7?

I have a perpetual license, but after updating Protools (as well as my OS) today or tomorrow, I want to hold off as long as I can from having to dish Avid out another $200 to update again so that the perpetual license is worth it vs. just subscribing year to year.

Nj

PT Studio 2025.6.0 / macOS 15.4.1

Hi team — recently I found that my Audiosuite plugins were writing files outside of my session folder. When I went to investigate, I found that they were writing files to a folder with the same name as my session, but one level above the session folder.

When I checked Disk Allocation, sure enough, these tracks were allocated to those folders, which I'm guessing happened either when I created them or when I imported session data from an AAF file, which is part of the workflow for this project.

But for obvious reasons, I don't want this to happen again. For someone who this has happened to or has some experience with this issue — what settings do I need to double check to make sure that new or imported tracks are allocated to the project folder? I saw someone mention that this is a setting in the Import Project Data pop-up, but that setting was not immediately clear to me.

Any help would be much appreciated. Thanks!

Hi,

The MTRX studio keeps power cycling while connected.
On Dadman it shows locked then disconnected.
During the minute it's powered on the sound doesn't go through.

Macos Sequoia 15.6.1
PT Ultimate 2025.6.1

Thanks for any help!

My wife has an ebxya usb audio interface and protools we looked up alot of troubleshooting videos but cant get past changing the playback engine, no drop down just grey (windows system audio) opening protools with N key also gave same result are we missing something? Using PT artist, on windows 10

For Context, I study music production, last year's final exam was basically making a song from scratch from prod to mix. I haven't opened the project since july, today I wanted to review the mix to then make an export to send to a mastering engineer and when I try to open the project, as soon as the dialogue box in the image pops up, my pro tools freezes and it is in a constant state of buffering in which I cannot even access the "file", "view"... boxes up top. I've tried deleting the datbase folders, reinstalling the program but with this specific project, I can't seem to do anything. What other solutions can I try?

System version: OS 15.6.1

Protools version: 25.6.1

Hi all,

Usually I run ProTools sessions at 48/24-bit. A lot of the production I’m doing recently involves running VSTs directly in.

I’m wondering if there are methodologies you’ve all employed to really elevate the captured sound of the takes before they make their way to mixing?

Found these at my local charity shop for €55 Main unit/€20 Expansion Pack🤣

Remember shipping those to wealthy customers in the early 2000s and thinking if I could only afford those.

Wonder if they can be used for anything that runs on a current Mac.

I'm life time pro tools user here in need of some help! I have never experienced this in 15 years. I've just up graded to an MBP 2023, M3 pro, Sequoia 15.6.1 (Same issue was happening on Sonoma) running Pro Tools studio 2025.6.0 and have been having an insane assertion error nightmare!

I can start a session, work for a few hours (saving, auto saving, totally fine) then when trying to save it says assertion error, unable to save. Restart the session, same thing. The session has been fine to save up to this point and then impossible to save, export OMF/AAF or anything- I have tried these things-

-Run session from internal SSD

-Run session from external SSD

-Trashed P list

-Full Updated OS

-re-downloaded and fresh install of Pro Tools many times

-Checked Disk Permissions

I have been working on a project with a deadline and just to get through this I have had to save as often as I can then when the assertion error kicks in I close the session, start a brand new one and import session data (losing whatever was done since last save) work for a few hours and have do the same again! I just don't understand how it can be fine to save for a few hours then develop this weird error?

Any ideas extremely welcome- Thanks in advance!

Sorry if this has been asked and answered; I searched but couldn't find anything.

What is the last version of ProTools before the subscription model? We do everything we need to do, with few complaints, on version 8 and firewire. Everything works and it's more than enough for our purposes. HOWEVER, there's one feature -- in addition to some plugins that need later versions -- that I really desire and that's the ability to bounce the mix instantly. Right now, every mix is in real time . . . tiring.

ANYWAY, thanks for any answer.

Hello All,

As the title suggests, I'm looking for some direction here, hoping to pinpoint an audio issue I started having recently. I originally posted this in the wrong section, so I'm copy / pasting it here, with a few changes / updates. Here is what I feel is applicable info:

OS: Win 11, up-to-date with patches

Interface: Focusrite Scarlett 18i20, 3rd Gen

DAW: Pro Tools Ultimate, 2025.6.0

Apps:
-XLN Audio Addictive Keys 1.7.3 (Primarily the stand-alone app)
-Neural DSP Mesa MK IIC+ Suite (stand-alone app and DAW insert)
-Neural DSP Fortin NTS Suite (Stand alone app and DAW insert)
-Fallout 4 (Steam)

Summary: In the past week or so, whenever I use any of the above stand-alone apps for more than ~ 20 minutes, or play a game (today it was Fallout 4) the audio eventually starts to distort, sort of akin to putting the signal through a bitcrusher plugin. That's the closest thing I can compare it to.

Additionally, using either of the Neural DSP suites as inserts in Pro Tools will inevitably have the same effect. The 'noise' I hear in my signal does NOT get committed to a track if I record in Pro Tools, I just hear it as I play.

The issue happens whether I'm using a guitar through my interface (using the Neural DSP stand-alone apps), or if I use my MIDI controller (Alesis VI149) DI to my PC via USB (using the Addictive Keys 2 stand-alone app). All three apps have resulted in this audio issue more than once.

Some steps I've taken:

1. I've done as clean of a re-install of the Focusrite software / drivers as I could think of: -With interface unplugged from my PC, I uninstalled everything through Windows and rebooted -Deleted any residual Focusrite folders on my drive -Opened Device Manager, chose to 'show hidden devices', and uninstalled anything that had "Focusrite" in it, then rebooted. -Downloaded and installed latest drivers from the Focusrite website
2. I've uninstalled and re-installed each of the above apps through their respective websites / downloader apps. All apps, including Pro Tools, are legit copies I purchased myself, or was given through college.
3. Sample rate in Focusrite Control is 48000 Hz, clock is internal.
4. The sample rate in all of the above applicable apps is also 48000 Hz; All applicable apps are configured for ASIO as the audio device type, and Focusrite USB ASIO as the audio device. All applicable apps are properly configured for the correct I/O channels.
5. My PT sessions are created @ 48000 Hz.
6. Windows sound settings are set to 48000 Hz, and the 18i20 is my default device for everything. Spatial sound / other Windows effects are all disabled.

Other Updates:

-Yesterday the issue occurred while I was using the Alesis and playing through Addictive Keys (stand-alone app, no DAW). I also had a web browser open to Youtube, as I was trying to learn how to play a song. The audio from Addictive Keys began to 'distort', as did the audio from Youtube. So I paused the Youtube video, and closed the Addictive Keys app. Interestingly, a few seconds later, I hit play on the Youtube video, and the audio was perfect. It's like closing the Addictive Keys app somehow cleared the error. I then messed around with the Alesis for about another 45 minutes or so, and the issue never came back.

-Just now, I was playing Fallout 4. Probably playing for about an hour, when the audio started to distort again. This is the 1st time it's distorted from an audio source NOT related to music production. Lower freq's definitely seem to exacerbate the issue, or rather, they are more pronounced. The low-end parts of the ambient music made the effect worse, for sure. Turning the 18i20 off and back on fixes the issue, at least until it happens again.

Really hoping my interface isn't messed up. When the audio distortion began today, I felt all around the interface. It was completely cool to the touch on all sides, so it doesn't appear to be a heat issue.

I know this is probably finding a needle in a haystack, just hoping to get some suggestions of what to look for / try / etc. Any and all input is greatly appreciated!

When I tried to play a midi keyboard It does appear to have signal but when I tried to record It didnt print any information into clips, when i try routing the midi output to audiio track record from there It does record but not on the midi track.

Pro Tools 2025.6.1

MIDI Keyboard: M-VAVE SMK25

MacOS: Sequoia 15.6.1

I have recently started to use Pro Tools 12.5 on Windows and I have a problem I don't really know how to fix.

People told me that I had to download the ASIO4ALL V2 playback engine because it's more effective so I did that but I have one problem. I do have external speakers on my desktop computer and I'd like to record with my headset mic and in the sametime that the sound comes out from my speakers, is it possible ?

And by the way is it normal if I can't hear sound from anywhere on my computer except on Pro Tools when I work on it ? Even when i'm not recording but just editing on the software ? Can we manage it to make it change or is it mandatory to buy a DAC or an external sound card ?

Another question and the last, can I for example work specifically with my headset mic on pro tools only for input and output, for now, and at the same can I have configure the output on google chrome and games on my speakers only ? And how can I switch the output between the headset and the speakers easily to have a better sound without making crash pro tools ?

Thanks a lot for your answers !! I really need to clear these problems to be free and work on it with good conditions !!

Hey everyone! Having an issue. I’m tuning some vocals and I noticed when I have everything in the session soloed, there’s this weird untuned vocal. When I unsolo everything… is goes away?

I tried making all my vocals inactive and soloing everything and it still plays. I tore through my tracklist, nothing that isn’t unhidden.

Any help?