Bug Reports

Hello all. I’m reaching out here because I don’t know what to do anymore. I am working on a large audio project in Adobe Audition, and as of a week ago the session is no longer opening. When opening the “estimated time remaining” goes down to 10 seconds, but then slowly and indefinitely increases. This also happens with backups and old versions of the project. I have tried restarting my computer, re-installing Audition with the Cleaner Tool, turning off my plug-ins, and checking all the permissions. I had to force quit the application.I will take ANY advice, I’m pretty upset by this. Thank you! I tried to get my system information and the error report but I'm not sure how to upload it.  I'm on a Macbook Pro 2023. Sonoma 14.3Adobe Audition 25.3.0.71      

Hey! I have never had this problem before so this is kinda frustrating. I am currently working on post-conference mix for a church. When I try to export the files to make a final mix, the estimated time goes down and then shoots back up and keeps going up and the progress percentage stops. I have waited and waited but even then it just sits there and stalls. I have used nothing outside of stock plugins and I have even closed all background processes and I still am unable to export or bounce the mix to a new track. I have not seen any documentation to help me. I am using an M1 Macbook Pro and my project is exporting from my external HDD to my local desktop. Please help!

I work with 20-30 minute audio files. The voiceover is good, but somehow audition tends to jumble words within the file? At first I thought my VO artist was making mistakes, or perhaps I was cutting clips wrongly, but I just checked it in an older render and it's Audition ruining my voice over clips. It happens 2-3 times per project, and it also happens retroactively. So I'd have linearly listened to the entire file, confirmed it's okay, press save, and then by the time the final product is ready it turns out Audition changed the audio at minute 2 or something. It jumbles words, mixes them up, etc. It completely destroyed my workflow, taking dozens of hours at this point. Is there any way to fix it? I think I'll downgrade to Audition 24 since I didn't have that much trouble in that version, but I'm quite pissed off such a glaringly obvious bug has been a part of Audition for months (judging by other posts). 

I have my Audition autosave set to every ten minutes in the session folder. I've been working on a multitrack session for a few days. However, after my Macbook restarted itself, I lost a month of work. There were only a handful of auto save files, all of which were from a month ago when I first started working on this project. Is there any way to recover these files? Where did it all go if not in my session folder? How can I prevent this from happening again?

Wonder if anyone is having the same problem as me: I've been recording voiceovers in Audition (25.3) with a buffer of 256 without issues but after updating to Windows 24H2 (I'm on the latest version of Windows 11 home edition), I am getting glitches and random dropouts in my recordings. I record at 24 bit, 48khz, mono. As a workaround, if I increase the buffer in Audition to 1024, the errors disappear,  but I shouldn't have to do this. If I record in REAPER at a 256 buffer, I have no issues...so it 'appears' to be an issue between Audition and the Windows Update. I have raised a ticket with Adobe but I would like to know if anyone else has experienced the same issue and if you've found a solution.  

Estoy trantando de grabar audios con mi interfaz, pero al grabar y luego reproduccir se salta a la reproduccion, no se si grabo asi saltado o esta reproducciendo mal, necesito ayuda comunidad

Hi there!!!In 25.3 version of Premiere Pro I faced a problem. I'm trying to send the sequence to Audition and choose render video as DV Video and it show an error says "Export Error". Latest version when it worked is 25.1. Is this a bug?

For some reason the frequency analysis hold funtion now doesn't work properly with stereo files. If you hold the curves from one stereo file and then try to view the frequency analysis of another stereo file, your two curves turn into one curve that I have no idea what it is. This tool worked fine in Audition 3.0 so I'm not sure how this was missed for all this time.

Hi thereApologies if my post is similar to others in the past. I've been using Audition for a year and it's worked very well. I'm a voiceover artist, usually the maximum I use is 2 tracks in a multitrack session.  Recently my sessions have been plagued by the playhead lagging behind the audio, making it difficult to edit efficiently and costing me time in the process. Audition normally loads fine but within the first few minutes after recording the lagging begins.  Typically my effects rack is EQ, De-Click, De-Mouth, De-Ess, Auto Gate, Compression and a Limiter (The Wall). These have never caused an issue before. Recently I installed a plugin called Supertone Clear which uses machine-learning to seperate room sound from the voice. I imagine this is quite taxing. However, I have tried several scenarios, restarting Audition and the Macbook in turn and removing Supertone Clear from my effects rack and the issue remains. Can anyone help?  🙂ThanksG

I recently tried to open an old multitrack file only to find it was empty.  I opened up the file in notepad and I found that all the parts of the file that refer to the files used in the project, were missing.  This is very odd because when I saved the file, they were actual functioning files with no data missing.  Not only this, but the automatic Audition backups were also empty.  I don't know what kind of bug has destroyed some of my old project file but it sucks to have to redo the whole project. I tried to attach one of the sesx files but it would'n't let me

I am working to launch the trailer for a podcast and, before doing so, went into the Metadata window to add relevant ID3 tags. Everything adjusts correctly and saves accurately to the new mp3 EXCEPT the Recording Date. The default Recording Date on this file is, oddly, Dec 1, 2011 at 7:09:39 PM. I recorded this in May 2025, first opened Audition in 2023, and my iMac is 2013...so I am really at a loss as to why Dec 1, 2011. Anyway, no matter what I try (adjusting the information around what is there, fully deleting and then typing in the correct date with and without time, saving as .wav first, looking for software updates, rebooting my iMac, etc) the saved mp3 always shows a Recording Date of 2011. I've also several times seen it change back to 2011 after I've updated to 2025, as I edit another criteria. File I'm working with is a mp3. I have also tried working with the original sesx with same results. Adobe Audition 2025 (up to date). OS Sequoia 15.5. Date & Time on my i

Audition is running very slowly, taking up to a minute to do a simple merge clips, the beachball rolling on every action.  It's enough to kill the creativity and destroy the smooth workflow I count on.  I am working on a very fast computer with plenty of space -- a Mac Studio M1 Max Model 13,1, an Apple M1 Max chip, 10 cores, 64gb memory and 2TB of internal storage with 1.41 TB used.  I am auto-updated, currently running OS 15.1 Sequoia.  The project and all files are located on an external LaCie 8TB drive with 4.4 TB free.  I am running Audition 25.3.0.71.Any thoughts?  I have heard I should locate my project and all files on the internal HD and just use the La Cie for storage... Thanks. Rob

Hola a todos, tengo este problema: Adobe Audition no está reproduciendo ningún archivo.  Cuando cargo un archivo de sonido dentro de Audition, no lo reproduce. Tampoco en el modo multipista. No hace nada, ni siquiera obtengo un mensaje de error. Simplemente no reproduce. No entiendo qué le pasa.

Please tell me I'm doing something wrong. I have been working professionally with Audition for around 10 years. I am used to having multiple tracks with multiple VST's activated with multiple bus tracks.I HAVE NEVER HAD A LAG PROBLEM.  I used to work on an even slower system and zero issues.  It's always been fast for me. Recently I am working on an animation and using Audition for the animatic sound.  Everything is fine UNTIL I literally used one bus and slapped on only two instances of Fab Filter Q and C.  This happens whenever I use Bus tracks or use more than one VST on a track.. even when I pre-render tracks. It lags up the whole project. My system: 64gb ddr5 6000 corsair vengeance memintel I7 14700RTX 4070 Super5tb of HDD space all samsung evo SSDRME Babyface pro USB Interface Is there something up with the New version of Auition?  Is there a problem with the i7 14th gen ?  I have issues with ZERO other pr

Hello, Last week I edited some videos with the same configuration with no issue. Today, my eardrums get blown out by my video's audio being 100x the volume it's supposed to be, I've been scouring the internet for a few hours and the only solution that has worked for me was to revert to an older 2024 version of the software. Will there be a better solution to this moving forward?  2024 Audition vs latest version Audition Waiting impatiently to hear something back. With tinnitus,Martin

I'm using a PC running Windows 10 Pro (will be updating to 11 at some point soon). Using Audition version 25.3.0.71 (a fresh update).When I load up a session file, or open a new session file, playback (either via spacebar or mouseclick on "play" button) will not play. It responds my un-highlighting the tracks - indicating that the input has been received - but I cannot figure out why the multitrack is not playing back.

Hello,I just began using a new Surface Pro 11 with an ARM Snapdragon processor, and see that several Adobe apps are not yet compatible. I downloaded the Beta version of InDesign, but I do not see any information about Audition. Will Audition be compatible sometime soon?I use Audition frequently and cannot access it on my new Surface Pro 11. This is very frustrating.

I don't know how to put it better, but in essence I'm automating an effect (a frequency shifter) in a multitrack project. It starts neutral and slides down in the middle of a clip. Simple as that.When I hit play, I can hear it correctly, but if I play it again, Audition doesn't recognize the automation is back in neutral position, so it plays from lower than neutral and slowly "adjusts" itself when the automation slides down. Even if I add a bunch of keyframes before the sound plays to try to jolt it into place. It ONLY works when I have the effect open for editing, so I can see the parameter changing with the automation. As soon as I close it, it goes back to being "lazy". Oh and it also affects the result when exporting. Anything in settings I can change even if it consumes more resources? This is pretty annoying.

Using version 25.2.0.123 of Adobe Audition, when trying to Extract Audio From CD I now get this crash error:Adobe Audition.exe has encountered a problem and needs to close.Then it closes.So I can't extract from a CD anymore.I've been using this feature for many years with no problem but something seems to have gone amiss in the latest version.Kind regardsPhilphil.lentz@gmail.com

Since the new Version of Audition, theres a weird bug. If you Record an Audio file then try to delete everything and Mark everything, it doesn't show, that it has been deleted even though it was. I always have to delete like 90% and then the last 10% to be able to see the deletion. Its really confusing when recording, please Adobe try to fix this issue.  Normally if I record, then mark everything and then delete, the normal red line occurs and shows the empty track directly.

loud click on session at 4:54 on recording. Not on inserted track. deleted inserted track and click still there.deleted entire session and started over. click at same time on new session

The program is running very slowly on various simple tasks -- merging clips, importing a file, moving clips, cutting and pasting -- the beach call starts spinning and the tinyest task takes several minutes.  Have tried deleting backups, closing all other apps, watching Activity Monitor, shutdown and restart.  Problem persists, seems worse later in the day.  It's getting impossible to maintain a smooth workflow.  Thanks Rob Working on Audition 2025 Version 25.2.0.123Also tried Beta Build 25.2.0.117 (February 24 2025 05.59.34) My current machine stats: Mac Studio (2022)Apple M1 Max64 GB MemoryMac OS Sequoia. Version 15.4.1 (24E263)Storage  461.89 GB available of 2 TB External Storage  LaCie. 8 TB.    3.66 TB on disk  

Self-explanatory by title: Adobe Audition crashes putting video on timeline if Video Winow on another monitor.I can import the video into the project, but it kept crashing on my laptop. I ahad the project on my NAS and loaded it up on my Desktop  to finish up edits. It hung and crashed the project. After trying a couiple more times, I built the project from scratch. No problems importing audio files, of course. There was no problem importing a video file. It appeared as if it wre trying to load, but hung instead, no matter how long I waited, Audition would no longer respond, and I had to terminate the process.I tested on local hard drive, instad of NAS. I tested with various videos ( .mp4's ) ... same indication.Finally, I thought I'd reset my workspace. Whenever the Video Window is on the same monitor as the main application window, no problem. When I move the Video window to another monitor, it plays. But if the Video Window is on the other monitor and I try to place it on

When I was in the adobe audition 25.2.0.123 as well as the previous version, when I used the vst3 plug-in (here I'm citing the voice de noise in the izotope rx 11 advanced), the window did not render the effects interface correctly, showing only parts. It may be a compatibility issue, it may be a plug - in vendor issue, it may be an Audtion issue, but for the user experience, it is the presence of a bug. Let adobe audit and add - on vendors start with the end and create a strong user experience for users that is your core competencies.

A bug exists in Adobe Audit 25.2.0.123, in waveform mode, when I deleted the waveform in front of the audio, the marker in the back did not follow the move forward, which did not exist in the previous version.