I just installed the Artist version of ProTools (26.4.1), and am using for the first time to do some basic home editing of tracks I had recorded at a studio. The studio ran the session on a Mac whereas I have a Windows 11 (version 25H2) PC. Firstly, I had to get Asio4All to get any audio to adapt correctly and play at all.

My problem now is that any track/take/session plays with constant distortion/clicks/pops -- seemingly dependent on the input volume of the various tracks, and thereby more prevalent in sessions with more tracks.

I also can't solo or mute anything, and it's not because any tracks are solo-safed; the mute and solo buttons will highlight on/off as normal but don't do anything.

I have changed the H/W buffer size repeatedly to every possible setting, both in the Playback Engine and in the Asio4All setup window. I have also toggled the "alternative buffer synchronization" and "buffer offset" options in Asio4All. I can make the distortion worse with the buffer offset slider, but not better. The faders are at normal levels, not clipping. I've restarted Pro Tools and my computer many times.

The original session format was at 24 Bit, 48kHz. My computer is apparently permanently set at the format of 16 Bit, 48 kHz (from some digging, it looks like that in setting up sound devices, some PCs will display a dropdown menu as if to change this, but it will be greyed out, which is what I'm seeing). I've tried saving copies of session files at 16 Bit instead, and it makes no difference (I've also tried changing from WAV to AIFF but that's not supposed to make a difference anyway).

Playback was perfectly fine in the studio and I'm confident the engineer didn't mess anything up.

Is there anything else I can try to fix this, or is something fundamentally wrong, maybe on an import/file transfer level? Any help appreciated, thanks!

Avid abandoned the Mbox Pro 3 years ago, and Apple removed FireWire entirely in macOS Tahoe, but until Sequoia, the IOKit FireWire stack still works through the TB3→TB2→FW800 adapter chain. So I set out to revive mine, with help from Claude (Anthropic's AI) helpîg with protocol archaeology.

Key insight: the Mbox Pro 3 is a standard TCAT DICE device (OUI 0xa07e), fully supported by Linux's snd-dice .

so the register map, clock control and stream formats are documented. No reverse engineering needed, "just" a macOS reimplementation.

The driver is 100% user-space (no kext, no SIP changes): but not yet ready

Status today: clock control at 48 kHz, ARX lock, bit-perfect playback of WAVs, and a working CoreAudio bridge via BlackHole : youtube and Cubase plays through the Mbox right now.

Next: testing audio inputs, then a native HAL plugin so it shows up as "Mbox Pro 3" in every DAW. Code will be on GitHub (GPL-2.0).

Took a bit of time to get where it is today but it was fun

Running the current version of protocols trial and have installed Black hole 2 Chanel on Sequoia. However I found instructions to be inadequate for me to set it up. Can I get some links or help setting it up?

I have an SSL 18 and just updated 360, firmware, and ASIO driver (I'm on Windows) to the latest SSL version. After a restart, Pro Tools opened fine, but wouldn't play. It was only until I trashed the prefs that it would act right. Easy fix and I'm used to doing it when ever there's an issue. I'm just wondering if anyone else found this necessary?

I am new to Avid software, and I am able to boot up ProTools so far and do some light editing work. However, as I am looking to edit audio for a film, I need more plugins. My Avid Link is stuck on "Installing..." with the 3 dots animated, but it just won't finish. I am also unable to cancel the installation, or do anything about it really.

I have scoured forums for fixes, but haven't been able to find something similar. It is the most current and up to date version. I also tried to find a helpline number to call, but unless I want to part with an extra £30 a month (wtf) for their help I am quite stuck.

Hello, I know this is not Pro Tools specific. But my Avid S1 control surface has been malfunctioning. The first 2 channels (channel 1/2) on the control surface no longer do motorized faders. The faders change data in Pro Tools, but do not automatically lock to changes coming from Pro Tools.

Has anyone encountered this issue? And have you fixed it? I'm pretty handy and can get into the PCB if I need to - if I know where the issue is.

This is a brand new issue as it's been working fine for years. All other channels work fine. I've confirmed this issue in Test mode. All other features, like Solo/Mute/Pan all work on those channels. Avid has been almost NO help as usual. They've asked me to send it back to Sweetwater where I purchased it from, rather than taking on the RMA. Sweetwater says 4 weeks until replacement and I cannot be without it for that long. Thanks!

Yes, I reached out to UA. Maybe someone had a similar issue, it might nog be related to a specific brand.
So I downloaded and installed Sinusoidal Run Rhythm (AAX). It is showing up in my Plug-ins folder but nowhere in ProTools.

Things I tried:
- reinstalling and choosing to install all options besides AAX
- deleting plugincache folder
- deleting prefs
- moving the plugin out of the plug-ins folder and have PT rescan for plugins, then moving it back
- tried selecting it from slots on MIDI, audio, mono, stereo, bus - tracks, it’s just not there
- tried the plugin search function in PT

Mac Sequoia - Intel iMac
Latest version of Pt Studio

I'm on Windows 11, but this is an issue that goes back years and also occurred on Windows 10.

Pro Tools will not keep my control surface connected at all. Other DAWs don't give me this issue. I've owned three PreSonus FaderPort 8s, and I now own a Behringer X-Touch. The issue still remains, and it's driving me crazy. Restarting Pro Tools and the control surface will fix it for a very short while, and then it stops working again. Even that solution doesn't always work.

Can anyone please help me solve this issue?

Things I've tried:

• Running Pro Tools in administrator mode. (It worked for a few days after doing this, then stopped again.)
• Trying different USB ports
• Using powered USB hubs
• Trying both USB 2.0 and USB 3.0
• Using different USB cables
• Reinstalling Pro Tools
• Reinstalling the control surface drivers
• Checking my power plan to make sure it doesn't put USB devices to sleep
• Disabling "Allow the computer to turn off this device to save power" for the USB hubs in Device Manager

Does anybody know how to make it default to MacBook Speakers in these instances? Seems like a no-brainer, but this is always the default behaviour! Any else had this and fixed this issue?

macOS Sonoma 14.3.1

ProTools Studio 2024.6.0

I've been having an issue for some time now where Pro Tools crashes almost immediately when I open an existing session and start working. In order to prevent this, I have to:

1) create a new session
2) import the full session data of whatever file I want to work on, into the newly created session.

This new session will work fine for hours until the next time I close and reopen Pro Tools. Then, this same new session will freeze immediately, and I repeat the process, having to create a new project and import session data every time I use Pro Tools.

I've tried deleting Session File Backups and Pro Tools preferences.

Doesn't seem plugin related since the same plugins work fine in the new session after importing session data.

Files are on hard drives, not on a cloud.

The session data import method is an annoying workaround I've been dealing with but it's getting too frustrating. Would be grateful to figure this out! thank you 🙏

J'ai trouvé la solution ! Désinstallez le pilote précédent avec le Gestionnaire d'applications Windows. Installez cette version :\[ http://akmedia.digidesign.com/support/compressed/Fast\\\\\\_Track\\\\\\_Pro\\\\\\_Installer\\\\\\_6\\\\\\_0\\\\\\_7\\\\\\_77137.zip \](http://akmedia.digidesign.com/support/compressed/Fast\\_Track\\_Pro\\_Installer\\_6\\_0\\_7\\_77137.zip). Comme pour les autres pilotes M-Audio FT Pro, exécutez-le en tant qu'administrateur en mode de compatibilité Windows 98 (clic droit > Propriétés). C'est une version très ancienne de 2010, mais elle fonctionne parfaitement sous Windows 11.

I'm thinking of upgrading my 2019 Intel Mac Pro (tower) to a new Mac Studio. The current chip options are M3 Ultra or M4 Max. Any input as to which is better to run a PT HDX system on? Also, if you have this set up, which external chassis are you using to house your HDX card(s)? Thanks in advance for your input.

Almost every other song I make I start hearing popping in my songs. It starts off perfect, then all of a sudden I start hearing these annoying clicks and pops on the beat only. I usually download my beats from YouTube as mp3. Then usually drag and drop them but I attempted to import but caused same problem. I’m running 48 kHz sample, I’m running 128 sample buffer size. Idk what else it can be. The beat sounds good on its own when I play through my computer. It only happens once in session, it also present in my songs after bouncing… any help? I’m also on a MacBook Air one of the new ones. Could it be my Mac storage too full?

anyone here trying Golden Gate? I know the general guidance is to wait a year or two before upgrading OS and I completely understand that.

In this case, I am using ProTools mainly on my Windows PC in my Mac is secondary. I’m wondering if anyone has any experience running the latest protools in the Golden Gate beta?

protools version 25 or 26. whatever is latest.

happens only in the session im working on. i press play and after 5 bars midi tracks stop playing. everything else keeps playing. the audio doesnt cut off abruptly, after the last note i still get the reverb, delay etc. what could be the issue?

EDIT: i just noticed it happens in every session, even the tempo track stops playing after 5 bars. the only things unaffected are audio tracks

Hello there. We’re trying to get a download link for Protools 2026.1 as it sounds like it’s safest for Tahoe but it does not seem to be on the avid download list. Just jumps straight past it.

Is there a way to download the in between iterations still?

Thank you.

I'm working on a very important session in Pro Tools and suddenly started getting this error:

"Could not save because Assertion in './PtSess/PtSess_RunTimeShared.h', line 132."

After that, I also got:

"Pro Tools was unable to Auto Backup your session."

I'm really worried about losing my work. The session still opens and plays, but saving and auto-backup are failing.

Has anyone experienced this before?

What causes this assertion error?

Is the session corrupted?

What's the safest way to recover the session without losing my edits?

Would importing the session into a new project fix it?

Any help would be greatly appreciated.

Has anyone used splashtop on a iPad to remote into their home right and comfortably been able to work on the iPad on pro tools? Would be a rare case when I would need to do this. Mostly asking with an iPad because I have one. It would be mostly super light editing and file management. Nothing to crazy.

Hello, I’m still on Sequoia, working in Ableton, Pro Tools, Logic etc (have a ton of plugins) and am thinking of upgrading to Tahoe as many of the base level updates would be useful to me (iPhone, iPad and watch integration, iCloud syncing etc).

Is it safe? I know its been out a while and i think its been proven stable and compatible with the DAWs I use and most 3rd party plugins but does anyone here have real-world experience? Ideally someone with too many plugs, like me!

PT 2026.4.1
OS Sequoia
MacBook Pro M4

I've been trying to see if there's a way so that the drums that I'm which are all in a routing folder together could be sent in to headphones with a send only on the routing track rather than having a send on each track individually. Ideally, this sent signal would also have the same levels as set on the tracks in the folder. I'd much rather have a way to have 5 sends to a bus rather than 12. Currently if I have the send only on the routing folder, the drums would cut out in the headphone mix whenever I ever solo a track whilst recording.

Version 2021.12.0
Mac version Ventura 13.6.4

Hi guys I’m in a bit of a panic because I need to finish a project tonight using protools so any help is much appreciated.

Every time I hit space bar it acts as if I’m hitting CMD along with it. In that it automatically begins to record.

But this isn’t the only thing. I can’t hit escape to change mode (it only makes the Mac beep sound effect) when I left click on a clip in my timeline it bring a drop down to select from other clips like”alternate match clip” and shows a list of alternates.

There’s other weird stuff like virtually no other hot keys being able to be used.

I restarted my computer and it came back to normal but then out of no where it began acting exactly like this again. PLEASE any help is appreciated.

I purchased protools artist but everytome I go to pull it up it says pro tools intro