this post was submitted on 06 Feb 2025
10 points (85.7% liked)

techsupport

2580 readers
20 users here now

The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.

If something works or if you find a solution to your problem let us know it will be greatly apreciated.

Rules: instance rules + stay on topic

Partnered communities:

You Should Know

Reddit

Software gore

Recommendations

founded 2 years ago
MODERATORS
 

Everything is working splendidly, until I start to record Midi or Audio. Then everything freezes. I tried other audio-engines etc but only ALSA works. I also adjusted the buffer size and thereby latency.

Does anybody know what settings might possibly fix this?

Gratful for any and all suggestions no matter how outlandish.

If I could do all my recording on Debian I could ditch the airgapped windows machine I currently use for recording and finally be 100% FOSS.

top 7 comments
sorted by: hot top controversial new old
[–] [email protected] 5 points 20 hours ago

Update: I had a limit for my memory usage set to some default of 4 GiB I increased that to a higher number. This improved but did not resolve the issue in the end.

Anyone reading this here is the guide I followed to do so on a Debian: https://discourse.ardour.org/t/your-system-has-a-limit-to-locked-memory-solution/86813

[–] [email protected] 3 points 22 hours ago (1 children)

Run it in a terminal and pipe the output to a text file.

~/> ardour > output.log

Something like above. That will give you the text output up to the crash and hopefully have useful information like an error code or fault warning.

[–] [email protected] 2 points 21 hours ago (1 children)

Will this work even if it just freezes and technically never really crashes? Thanks this might be the light at the end of the tunnel. Would be grand if that gives the hint on how to make this work!

[–] [email protected] 2 points 8 hours ago

Yes, the output is continuous as it runs and if it crashes it just stops putting out data. The cool thing is you can capture the error codes and back end details so you can often gain an insight to what is failing and why. It may have something like a device not being ready or a library failing to load, but because the range of possible errors is so large the developers may not have a GUI way of showing them. I would recommend taking each of the last few lines one at a time and searching them in your favourite search engine with ardour at the front, like "ardour ERR: glibc not found" or something like that. If someone has the same issue they may have found a solution that works for you.

[–] [email protected] 2 points 20 hours ago (1 children)

The setting that worked for me is "Switch to Bitwig." :D

But seriously, I never got Ardour to work on any OS, and that seriously bums me out. I'd love to be just that much closer to 100% FOSS.

[–] [email protected] 1 points 20 hours ago (1 children)

I can't install any non-free software on this system. I alreay have a fully working daw on my old airgapped windows machine. However I rather not use non-foss software that is why i am bothering with ardour to begin with. Maybe it's time to just get analog hardware (tape recorder etc...)

[–] [email protected] 2 points 14 hours ago* (last edited 13 hours ago)

FWIW, I regularly use a Zoom H8 and do my major editing/mixdown in Tenacity, minor quick stuff directly in the H8. I give Ardour a try every few years, and things are definitely getting better. I just don't have a lot of patience for getting the audio working in Ardour. I still support Ardour because I see that things are improving.

Edit to add: I think it says a lot of good things about the Ardour project that one has to dig a bit to find the donation link. For people who can and want to financially support Ardour, here it is: https://community.ardour.org/donate