Ardour is CPU hungry on Windows 11

Thank you for such a prompt and helpful reply!

  1. I got the wrong impression about whether Ardour is officially supported on Windows machines. Thank you for clearing that up for me.


    It was the dialog in the attached screenshot that comes up during installation that I drew that conclusion (incorrectly) from.

  2. I see what you mean. I do not understand these meters in detail, thus I get your point about the CPU load per plugin comparison. However, when it comes to the overall CPU load percentage, I would assume some level of comparability between two programs posting a CPU load percentage. But perhaps you can help me understand if this is not the case.

  3. When I stated briefly there were too many bugs in 8.8 for me, I may have unintentionally made it sound like the entire program was completely riddled with bugs. Sorry if I did. To be fair, there were two bugs I noticed, and those two rendered the program unusable for me.
    (No visible Start/End markers in Range Markers lane, and No audio on first beat of playback.)

The Ardour team has been great to correspond with! And I did try version 8.9 just today. It has fixed those two bugs, so thank you much!

However, the audio dropouts/artifacts are still happening as they were before. I did take the time to explore different performance settings in the preferences menu, but nothing I tried seemed to help.
I decided to check more accurately the frequency of the dropouts/artifacts, and found them to happen about every 11 seconds of playback. Almost like clockwork. Curious if that information is helpful in determining the cause. Also, when the audio did drop out or make a popping kind of sound I noticed the DSP % read 89-99% then it would gradually work it’s way back down to the 30’s-40’s then in about 11 seconds it would do it all over again.

Again, I want to thank the Ardour team for being so kind and helpful to users of every level.

  1. Forgot that we say that during installation. It is not innacurate, but at one time our official policy was “Windows is not supported”, whereas now it is “We have few resources to support Windows-specific issues when using Ardour”. We should find a better way to express that.

  2. Ardour, for example, as no CPU load meter. We only have a DSP meter, which is an entirely different thing. The DSP meter in Bitwig (for example) measures things differently than Ardour’s does. Etc. etc.

  3. You should try altering Edit > Preferences > Performance > Disk I/O Buffering > Disk I/O Threads to just 1 and see if that makes a difference.

For me, Ardour has run as good as or better than every commercial product I have tried on Windows. (Cubase 12/13 and Bitwig 4/5) Plugin GUI’s can cause any DAW to slow down. The wrong graphics settings for the Windows system can make for a miserable DAW experience. Depending on the plugin, having the GUI open can use a lot of resources. It will help to close the GUI when done.

What I have found is that all the DAW’s are able to handle about the same workload on my system.

Even the commercial DAW’s have bugs, crashes, glitches, and wtf’s.

There are Windows DAW tuning guides available online, if you havent already checked those.

Hopefully this resolves that for you.

Thanks for the input, Schmitty2005. I will say that I have been impressed with Ardour in many ways. It has seemed very solid and well laid out for the most part to me. I switched to Ardour from Studio One because I needed to be able to assign midi notes to channels. It is strange to me that such a simple task cannot be done in Studio One due to the nature of how it handles midi.

I also appreciate the soundfont players included in Ardour.

So, good news! I tried:
“altering Edit > Preferences > Performance > Disk I/O Buffering > Disk I/O Threads to just 1”

Restarted Ardour for the changes to take place. And the entire song played without a single drop out or artifact! Also, I watched the DSP% as the song was playing and never noticed it read above 34%. It stayed around 28-30% most of the time.

Also, the plugin DSP Load has greatly decreased on the Reverb plugin- TENSjr

I will post some screen shots here in case anyone should find them helpful or maybe a good point for teaching (as I do not know exactly what all of these meters are telling me.)


Screenshot 2024-10-10 002216
Screenshot 2024-10-10 002342

Thanks again, Mr. Paul for the helpful guidance!

In the spirit of being pro-active: I did find this in the online Ardour manual…

These gave me at least some indication of how these can be useful.

I’m glad that this helped.

Since this is highly system specific, would you mind to help us out?

How many CPU cores does your system have?
Can you try if changing it to “2” threads also has a significant performance impact?

thanks in advance!

Hey, Robin!
I am running
Windows 11 Home
Version 22H2

Using an Asus ROG laptop
AMD Ryzen 9 4900hs with Radeon graphics 3.00 GHz
NVIDIA Ge Force RTX 2060 with Max-Q design
1TB solid state internal hard drive
40 GB installed RAM

The AMD Ryzen 9 4900hs has 8 cores, 16 threads

Thanks for the suggestion. I did try “changing it to ‘2’ threads”
and playback was as smooth and good as it was when set to ‘1’ thread. Here are some screenshots I took with these new settings that may hopefully be helpful when compared with the ones I posted with the previous settings.


Screenshot 2024-10-10 105657

Thank you for your help!

Also, in case this is of interest, here is the Ardour Log:
2024-10-10T14:21:32 [INFO]: Scanning folders for bundled LV2s: C:\Program Files\Ardour8\lib\ardour8\LV2
2024-10-10T14:21:33 [WARNING]: VST3<C:\Program Files\Common Files\VST3\Plugins.VST.NDI.Input.vst3>: Invalid VST3 Module Path: ‘’
2024-10-10T14:21:33 [WARNING]: VST3<C:\Program Files\Common Files\VST3\Plugins.VST.NDI.Output.vst3>: Invalid VST3 Module Path: ‘’
2024-10-10T14:21:33 [WARNING]: VST3<C:\Program Files (x86)\Common Files\VST3\Plugins.VST.NDI.Input.vst3>: Invalid VST3 Module Path: ‘’
2024-10-10T14:21:33 [WARNING]: VST3<C:\Program Files (x86)\Common Files\VST3\Plugins.VST.NDI.Output.vst3>: Invalid VST3 Module Path: ‘’
2024-10-10T14:21:34 [INFO]: xjadeo version: 0.8.14
2024-10-10T14:21:34 [INFO]: harvid version: 901
2024-10-10T14:21:35 [INFO]: Loading menus from C:\Program Files\Ardour8\share\ardour8\ardour.menus
2024-10-10T14:21:40 [INFO]: Loading user ui scripts file C:\Users\littl\AppData\Local\Ardour8\ui_scripts
2024-10-10T14:21:40 [INFO]: Loading plugin order file C:\Users\littl\AppData\Local\Ardour8\plugin_metadata\plugin_order
2024-10-10T14:21:43 [ERROR]: Butler read ahead failure on dstream auditioner
2024-10-10T14:21:44 [INFO]: Loading history from C:\Users\littl\Documents\Ardour Projects\We Salute You\We Salute You.history

The thing I am curious about is this line:
2024-10-10T14:21:43 [ERROR]: Butler read ahead failure on dstream auditioner

Yes, I’m also using Win11 and IdeaCentre All In One from Lenovo and faced the same problem as you. I made the same adjustments and they really helped. In fact, Ardour works better for me on Windows than on Linux, which could be due to many reasons, such as the fact that on Linux I use several plugins designed for Windows using Carla.

Thanks for the feedback.

We did indeed have issues with disk I/O thread priorities.
Those are now fixed since Ardour 8.10.

Thanks for the fix! I downloaded Ardour 8.10 and all seems to be working correctly thus far.

So I decided to do a comparison between Ardour, Studio One, and Cubase.
Please note that my understanding is the only DAW in this comparison that is available for free is Ardour, so I would not judge Ardour harshly for poor performance in comparisons with paid (rather expensive) DAWs.

I wanted to know which DAW would handle large audio track count projects better on my system.
I took 20 Wav files from a project I worked on (the drums were on a single stereo track, otherwise this project would have been about 28 tracks).
I loaded those 20 WAV files into each DAW and began organizing and duplicating those 20 tracks until I could find the limits of each system.

Here are my observations

Time to load 44.1kHz files into the 48kHz project I created

Ardour: 2 minutes and 20 seconds (converted files to 48kHz)

Cubase: 13 seconds (converted files to 48kHz)

Studio One: 1 second? It was instant, but I don’t think it converted the files to 48kHz.

Duplicating tracks:

Ardour: Can create multiple duplicates at one time, but when I selected all 20 files and specified duplicate 19 times Ardour crashed.
I backed off to duplicating 20 files at 2 times each time.
When I reached 180 tracks Ardour would crash if I tried to duplicate all 20 tracks even a single time, so I began duplicating 4 tracks at a time. I reached 204 tracks total with successful playback and navigation, but when I opened the mixer during playback Ardour crashed. This crash was repeated. So I decided I had reached a workable limit and should back off on track count to be able to use Ardour. This was all without Plugins or FX. Just simple WAV files with fader adjustments on the mixer.

Cubase: Can only create one set of duplicates at one time, but the newly created duplicates remain selected each time and it is quick and easy to create another set with the already selected tracks. Reached 600 tracks without any issues duplicating all 20 tracks each time. Playback and navigation were snappy and perfect. Not a problem. Mixer opened during playback very quickly and without a hitch. I decided to stop at 600 tracks.

Studio One: Can only create one set of duplicates at one time, and the newly created duplicates do not remain selected each time so it takes a little more time to create another set of duplicates. Reached 600 tracks without any issues duplicating all 20 tracks each time. Playback and navigation were decent enough. Some slight delays now and then when navigating through song during playback. Sometimes a few of the tracks would begin playing before the rest joined in. Mixer would open during playback, but it did take a moment. It all worked fine, but not as snappy and smooth as Cubase. I decided to stop at 600 tracks.

Organization of tracks and mixer

Ardour: No folders on the edit screen (I love being able to organize tracks into folders when working with large track counts.)
Mixer view allows me hide or make visible whole track groups with a single click (which is handy). So long as I have set up track groups well this is workable. I did find that of the 3 DAWs Ardour was the most difficult and tedious when trying to organize the tracks. Also, only two options for mixer track width. And these must be adjusted one by one per track.

Cubase: Organizing tracks in Cubase is easy because of folders in the editor and groups or VCA’s in the mixer. Channel search capabilities make it easy to find and select a channel you are looking for. And the track visibility options make it quick and easy to find what you are looking for in the mixer. Quick and easy mixer channel width resizing for all channels at once, and multiple widths are available. I think Cubase is my favorite mixer of the 3 DAWs.

Studio One: I think I like Studio One best for really quick organization of large projects.
Channel search options allow quick visibility of only the name you type into the search bar, which made my job easy since I had multiples of 30 tracks that started with the same name. I could very quickly select a group of tracks and pack them into a folder, then I could select “add VCA to folder” and my mixer was organized very quickly.
The mixer has two channel width options that effect all channels at once with a single click. One setting is super skinny with good metering, which is great for getting fader levels quickly and maximizing how many channels are in view. The other setting is good for seeing everything going on on each channel.

Project Startup times
After creating and organizing these huge projects I was curious how much time it would take to launch each program and load the project.

Ardour: Track count: 204 tracks.
Time to launch software and load project: 39 seconds.

Cubase: Track count: 600 tracks. (Not counting Folders and VCA’s)
Time to launch software and load project: 21 seconds.

Studio One: Track count: 600 tracks. (Not counting Folders and VCA’s)
Time to launch software and load project: 25 seconds.

Conclusion:
In this experiment my choice would be Cubase, followed closely by Studio One. I would not use Ardour for large projects if I don’t have to.
I have consistently found Ardour to be less capable on my system for handling large projects. This experiment is just one (extreme) example that used no plugins nor effects of any kind in order to level the playing field. I do however feel that Ardour is a very capable DAW and commend the developers for their hard work.

Purpose:

  1. To inform the friendly team at Ardour of my findings in case they find this kind of information useful.

  2. To inform other consumers like myself who may be researching this topic.

  3. To follow up on what I am finding since I opened this discussion in the first place.

Input and advice is much appreciated!

3 Likes

This is a fantastic post in some ways. If some of those crashes can be repeated it could result in several good efficient bug reports to fix in Ardour.

I will say for the record I have definitely worked with 100+ track sessions in Ardour before, though it has been some time. Anecdotal evidence and all.

Folder Tracks has been on the punch list for a long time, and work was even started on it, but it turned much more difficult than expected and petered out some time ago. I agree it would be nice to have that sort of functionality again though (One of the thing I think Logic got right). I also like the idea of the search functionality, but not sure how to implement it well within Ardour.

And one final note, you can change the algorithm used to convert audio files in Ardour to speed up the import if needed. I prefer to take my time early on but it is possible.

 Seablade

Like windows specific issue as mentioned by John What is the better OS for Ardour, Win or Linux - #6 by John_E

On Linux I can easily use over 1000 tracks.

Then again a crash report might shed some light. you can find those in %localappdata%\Ardour8\CrashLogs\ - see also https://ardour.org/debugging_ardour

That’s what I do in Ardour. being able to just draw group-tabs is very efficient, and then right-click … assign to VCA or subgroup-bus. You can then “spill” groups to filter the view.

Thanks for the replies! I hope Ardour continues to get better and better!

1 Like

In fact, Reaper, for example, has become very popular, especially among Windows users. It has a reputation for being lightweight and has a low CPU load. I have been using Reaper for many years and it has always been as reliable as the toilet on a train.

Reaper vs Ardour detailed comparison as of 2024 - Slant

The trouble with this sort of comparison is the pool of users contributing to it is biased, unless you limit it to people who have actively used both.

For example, I come across people who recommend Reaper all the time. I would estimate that 90% of these people have never tried another DAW.

I suspect the rankings in this is almost entirely based on the DAWs that people have used, rather than what is actually better.

Personally, I have little interest in popularity contests.

What is probably more notable is that, of the people who have expressed an opinion, the percentage of people who voted thumbs-up vs thumbs-down for the two applications is approximately the same, although Ardour is slightly better (86% give Ardour thumbs up vs 84% with Reaper).

Also, some of the comments in the pros/cons are objectively wrong.

Cheers,

Keith

3 Likes

I don’t doubt that Reaper is a great DAW. In fact, I have come to understand that it is a very powerful DAW. Thanks for your input. However, I do feel that the “information” on slant.co is unreliable.
For instance, Reaper was voted #2 in “Best Free Daw”

But Reaper is not a free DAW.

2 Likes

I think we should stress here that the information is not only unreliable but also outdated and simply wrong or even ridiculous. Let’s see the cons list: „ Relies on JACK”, „Pre-built releases are paid and the only way to get the program for free is to build it yourself”, „Too many plugins”. :slight_smile:

That’s really funny. Ardour has many cons of course, but literary none is listed there.

2 Likes

That is indeed true. I echo your thoughts. BandLab’s Cakewalk has also become a popular DAW, and it is also free. I also find it quite fulfilling. My curiosity to understand and delve into the workings of different software compels me to try different DAWs from time to time. For me, it’s like trying different cuisines or musical styles. In the same way, when I buy a car, I always choose a different brand each time, eager to explore the different features of different models, regardless of the quality of my previous vehicle. :blue_car: :red_car: :racing_car: