Linux 2.3.3/2.4-alpa Git/Src/recent builds tested suddenly broken recording

Audacity 3 Help Forum GNU/Linux
1

OK, here the deal. I have used Audacity for years, decades now? Formerly on Windows, and intensively and weekly on linux for the last 5 years.

PROBLEM:

  • Audacity’s recording function is busted. If I hit ‘record’ button. It takes 10 seconds for the timeline to reach 1 second.
  • Audio records and is stored of course 10x as fast as it should be. So ultra-fast.
  • Top end Top end specs, i7 cpu, 32G RAM vs pre-v 2.3 same clean system used on an older system old pentium dual-core with 4G RAM — so not a system issue. nor a latency issue caused by system or hardware!
  • Installing multiple repo pkgs + the current source built clean, results in exact same issue.

Fuller details below. I was forced to join forum and report this and there is nothing more I can do, tried basically everything in options, latency options etc. Finally built clean (all settings and traces on system of course removed) to no avail and now just installed the 2.4-alpha as well, all the same. I update my system of course regularly using Arch, and this is a NEW issue obviously from more recent updates.

I have never had an issue with it before, although it does crash on linux. And on this measure I have tested on current CentOS and various Arch Linux builds on clean, vanilla and refined systems with all options and depends AND on machines from 15 year-old stable PC running old pentium dual-core with 4G ram (and perfectly fine otherwise).

Now in 2020, I have been attempting to use Audacity on a 32G RAM, i7, top end mother-end and for this instance a same and stable, fully featured install of Arch.

I attempted to record off microphone and well as via 3.5 line input. I have always done this and it worked simply using system default audio and ALSA. Simple no problem.

Beyond testing the community and 2 other AUR packages from Arch, which of course should be the most current and offering stable versions for testing, I also just built from scratch Audacity.

Checking version : Audacity 2.4.0-alpha-Apr 21 2020

  • NOTE The same problem here reflects in 4 different installs of 2.3.3!

I also just uninstalled all pulseaudio packages and modules for the heck of it, except for the ALSA-emulator to avoid any issues (I remember like 6 year ago there may have been potential clashes but not in 2020 - should not be any problem at all)

So regardless, pulseaudio has nothing to do with. And I also made sure to test and remove JACK and also to attempt to use ALSO, Pulse, and JACK.

The same problem persists, it cannot be a system audio issue (and again I have YEARS or weekly use, all the same), nor a true latency issue!

I am pasting the build details for your reference.

File Format Support
libmad(MP3 Importing)Enabled
libvorbis(Ogg Vorbis Import and Export)Enabled
libid3tag(ID3 tag support)Enabled
libflac(FLAC import and export)Enabled
libtwolame(MP2 export)Enabled
QuickTime(Import via QuickTime)Disabled
ffmpeg(FFmpeg Import/Export)Enabled
gstreamer(Import via GStreamer)Disabled

Core Libraries
libsoxr(Sample rate conversion)Enabled
PortAudio(Audio playback and recording)v19
wxWidgets(Cross-platform GUI library)3.0.4

Features
Theme(Dark Theme Extras)Disabled
Nyquist(Plug-in support)Enabled
LADSPA(Plug-in support)Enabled
Vamp(Plug-in support)Enabled
Audio Units(Plug-in support)Disabled
VST(Plug-in support)Enabled
LV2(Plug-in support)Enabled
PortMixer(Sound card mixer support)Enabled
SoundTouch(Pitch and Tempo Change support)Enabled
SBSMS(Extreme Pitch and Tempo Change support)Enabled

Build Information
Program build date:Apr 21 2020

Build type:
Release build, 64 bits
Compiler:GCC 9.3.0

Simple problem. Irregardless of audio devices or soundcards, or system or versions from 2.3.3 to this quick latest install (specs same in all and working prior last tested not too long ago with no changes to system otherwise.

Lastly, any healp appreciated. At this point I just have to say, especially noting some other issues quickly on boards, there’s a major problem now with Audacity and something has been massively screwed up.

If I get feedback sooner than later, I will test to and report back asap.

2

OK, here the deal. I have used Audacity for years, decades now? Formerly on Windows, and intensively and weekly on linux for the last 5 years.

PROBLEM:

  • Audacity’s recording function is busted. If I hit ‘record’ button. It takes 10 seconds for the timeline to reach 1 second.
  • Audio records and is stored of course 10x as fast as it should be. So ultra-fast.
  • Top end Top end specs, i7 cpu, 32G RAM vs pre-v 2.3 same clean system used on an older system old pentium dual-core with 4G RAM — so not a system issue. nor a latency issue caused by system or hardware!
  • Installing multiple repo pkgs + the current source built clean, results in exact same issue.

Fuller details below. I was forced to join forum and report this and there is nothing more I can do, tried basically everything in options, latency options etc. Finally built clean (all settings and traces on system of course removed) to no avail and now just installed the 2.4-alpha as well, all the same. I update my system of course regularly using Arch, and this is a NEW issue obviously from more recent updates.

I have never had an issue with it before, although it does crash on linux. And on this measure I have tested on current CentOS and various Arch Linux builds on clean, vanilla and refined systems with all options and depends AND on machines from 15 year-old stable PC running old pentium dual-core with 4G ram (and perfectly fine otherwise).

Now in 2020, I have been attempting to use Audacity on a 32G RAM, i7, top end mother-end and for this instance a same and stable, fully featured install of Arch.

I attempted to record off microphone and well as via 3.5 line input. I have always done this and it worked simply using system default audio and ALSA. Simple no problem.

Beyond testing the community and 2 other AUR packages from Arch, which of course should be the most current and offering stable versions for testing, I also just built from scratch Audacity.

Checking version : Audacity 2.4.0-alpha-Apr 21 2020

  • NOTE The same problem here reflects in 4 different installs of 2.3.3!

I also just uninstalled all pulseaudio packages and modules for the heck of it, except for the ALSA-emulator to avoid any issues (I remember like 6 year ago there may have been potential clashes but not in 2020 - should not be any problem at all)

So regardless, pulseaudio has nothing to do with. And I also made sure to test and remove JACK and also to attempt to use ALSO, Pulse, and JACK.

The same problem persists, it cannot be a system audio issue (and again I have YEARS or weekly use, all the same), nor a true latency issue!

I am pasting the build details for your reference.

File Format Support
libmad(MP3 Importing)Enabled
libvorbis(Ogg Vorbis Import and Export)Enabled
libid3tag(ID3 tag support)Enabled
libflac(FLAC import and export)Enabled
libtwolame(MP2 export)Enabled
QuickTime(Import via QuickTime)Disabled
ffmpeg(FFmpeg Import/Export)Enabled
gstreamer(Import via GStreamer)Disabled

Core Libraries
libsoxr(Sample rate conversion)Enabled
PortAudio(Audio playback and recording)v19
wxWidgets(Cross-platform GUI library)3.0.4

Features
Theme(Dark Theme Extras)Disabled
Nyquist(Plug-in support)Enabled
LADSPA(Plug-in support)Enabled
Vamp(Plug-in support)Enabled
Audio Units(Plug-in support)Disabled
VST(Plug-in support)Enabled
LV2(Plug-in support)Enabled
PortMixer(Sound card mixer support)Enabled
SoundTouch(Pitch and Tempo Change support)Enabled
SBSMS(Extreme Pitch and Tempo Change support)Enabled

Build Information
Program build date:Apr 21 2020

Build type:
Release build, 64 bits
Compiler:GCC 9.3.0

Simple problem. Irregardless of audio devices or soundcards, or system or versions from 2.3.3 to this quick latest install (specs same in all and working prior last tested not too long ago with no changes to system otherwise.

Lastly, any help appreciated. At this point I just have to say, especially noting some other issues quickly on boards, there’s a major problem now with Audacity and something has been massively screwed up.

If I get feedback sooner than later, I will test to and report back asap.

3

@MOD - sorry looks like I posted this twice, correctly spelling in post title… you can delete this post and leave the other!

PS. It would be nice to have some editing ability, even if only 20-30 minutes to edit/correct out post or even delete. (A good idea imo to have a little trust in users, not like someone is going to take time in life to register and vandalize a board on this type of thing :slight_smile:)

4

Unfortunately, because this is such a busy forum, we get a lot of spammers trying to sneak their way in. One of their favorite tricks is to send an innocuous post, then come back and edit it 20 minutes later. With only a handful of regular contributors to maintain a safe forum for all, it has proved necessary to restrict what new forum users can do.

Note that there is a “Preview” button so that you can check your post before sending it.


UPDATE: I’ve just found your duplicate topic and merged it with this one.

5

If that were actually the case, it wouldn’t work for anyone. What you actually mean is that it isn’t working for you :wink:

Your post is quite long, so I’ll be a few minutes going through it to see if I can make any helpful suggestions.

6

As an update, I am looking into possible motherboard issues, as that is from my perspective the only element different, thus correction, it could be related to motherboard? I have experienced this issue on a popular (otherwise very nice) MSI “gaming motherboard” mid-to-higher end model 2019.

It is the one hardware component that could be a factor. Hard to believe, but honestly who the heck knows. I’ll digress on my speculations here and just consider it a possbility.

If anyone has any thoughts regarding very specific steps to take in attempt to resolve issue, please do reply. I will try them out.

As of now I decided first to literally

  • investigate all matters related to motherboard, check bios, for updates etc.
  • uninstall and completely re-install all audio and re-install only ALSA and vanilla basic, delete audacity-settings and retest.
7

Are you using Wayland?
Audacity does not fully support Wayland, so if you are, try logging out and then log back in to an Xorg session.

8

Nope very vanilla Arch using all X. Nothing experimental All basic and see my message regarding system.

In fact the only thing on it for a desktop environment is tint2 and openbox, common apps, ALSA.

And yes, I don’t wish to waste anybody’s time. After 15+ hours of scratching my head, messing around, re-setup on basic audio, and off course rebooting (not just logging out but shutting down and reiniting the system etc) I took the steps to investigate before posting.

But I am investigating the motherboard - it’s a MSI MPG 2390 Gaming Edge AC board… only thing I can think of.

I will report back after I do the steps I posted about a couple posts ago

9

If you don’t have PulseAudio, be very careful to ensure that some other app isn’t grabbing access to the sound card. Very few sound cards these days have hardware mixing, so multi-client support with plain ALSA is generally very poor.

10

Read my initial post - I did of course have Pulse installed. ALSA + ALSA Pulse comopnent, Pulse (and many compnents), and even JACK. I only got rid of Pulse for testing.

But good note I will make sure to verify no other audio components are running.

Anyway, got to spend time investigating the board, and last resort clean house of audio, reset and reboot again…

11

And Steve, it’s not an input issue regarding input not being recognized or captured. Input is captured by audacity and written to timeline.

I have verified that no other running audio devices etc were running…

ISSUE
If I hit record, the the cursor/line on timeline travels very slow, where it take 10 seconds to reach the 1 second marker! Inputs work and records data to timeline which results then of sound 10x to fast! Multiple builds test 2.3.3-2.4.0-alpha

So a bizarre issue indeed… stay tuned.

Old hardware with same exact system OS specs was a 15-year old pentium dual-core with 4G - no problems.
New hardware with same exact system OS specs is a fast i7 cpu with 32G ram, high-end, etc - problems.

Same issue occurred before rebuilding clean to 2.4.0 today.

ISSUE
If I hit record, the the cursor/line on timeline travels very slow, where it take 10 seconds to reach the 1 second marker! Inputs work and records data to timeline which results then of sound 10x to fast! Multiple builds test 2.3.3-2.4.0-alpha

Brutal flaw, rendering recording busted.

Sidenote: previous issues fro, 2.3.3 you might want to call for testing reports:

  • Audacity still crashes periodically especially if you have rough 2 hours of audio via 20 tracks (for a firm example). This happens I assume as some processing from basic editing or cursor movement is still active when user clicks around. I thought this was due to older antiquated system but it’s not as my system tested recently is ultra-top end and powered. Linux builds - I know this happens on Arch and CentOS.
12

If I hit record, the the cursor/line on timeline travels very slow, where it take 10 seconds to reach the 1 second marker!

And PS. Yes this started happening out the blue. And yes, while someone else is not necessarily experiencing my exact problem (nor I have I in past), others have obviously reported recording issues and I am just trying to help. The odds are if it happened to me on a very basic X system, and as a longtime experienced user and admin, then it will probably happen to someone else. And don’t assume they are going to take the time or bother signing up on a forum to report it. But I hope I, we, whoever can and will document such issues when encountered — the role of a support forum.

Just trying to help. Not making this issue up. Something obviously is very wrong when sound is being recorded 1 sec per every 10 seconds on an otherwise very basic Arch system running X and all audio options.

Note: The physical timeline in audacity is takes 10 seconds to hit the 1 second mark. My system resources are insane and barely used with multiple cores 32G ram, i7. I use conky to monitor resource usage easily in tandem with monitoring program. Theres barely a tick of resource usage of course. etc etc. So not shooting blanks at the sky.

Again stay tuned. My previous tasklist is rational.

13

UPDATE (one final one and test to follow)

@MOD - ideally it would be useful perhaps to retitle thread,
“[SOLVED] Recording issue, timeline recording/lagging 10 seconds behind”

because -a- it happened -b- it might just happen to someone else

I just solved the issue BY…

But I had to do perform the following. Or rather finally did the following and now it works, regarding timeline issue OK.

So now it’s working properly. However, I tried with many attempts of uninstalls, only removing home settings for audacity, and without manual removal of root files of remaining audacity files to NO SUCCESS.

And PS. I have another system, an actual separate machine running same Arch type of arch build still running v2.3.3 without they issue. I know I have also ran v2.3 with input recording I thought at it worked.

So I have no idea why this really happened. Issue occured suprisingly and was only resolved after much p.i.t.r.a attempts:

  • uninstalled audacity. manually deleted all settings in home as well as some leftover odd files in root (i don’t think should have been there? this is a question, i know i said ‘why is that here’ AFTER uninstall and then going to bin, usr folder etc - can’t remember specifics)
  • i then uninstalled pulseaudio
  • then installed v2.4.0 [this probably could have been v2.3.3 as well, doubt there is a difference now]
  • then another clean system reboot.

so certain conditions of the process are clear to me. but i am going to verify and test one more thing…

i am going to now reinstall pulseaudio and a plethora of associated packages i had before. reboot and test. and just see what happens.

but seriously i uninstalled and tested various builds and manually made sure to even delete audacity settings in user home folder. it was only after the above and clearing root level files that it finally resolved the issue.

one more post and then i have done my duty here…

14

OK I have an ABSOLUTE FACT. I just reinstalled Pulseaudio and now have the following list of components installed.

I just quickly installed a laundry list of pulse packages and the issue is back!

I uninstalled pulse [+ clear old files, reinstall process, see previous] and no issues. At first and from prior experience (years ago with some odd app) I suspected it might be pulse. But longstory short I removed it and problem persisted after reboot, something I cannot explain, without exact re-testing and I have no time for that.

Some other package install may have installed one of these causing conflict with audio recording. As a testing note. I may have not had all these installed before, I just opened up a pkg-manager searched and installed a slew + obviously I had one of these installed before causing the exact same conflict.

But the good news is that one of these packages used with pulse has caused this odd problem of the timeline moving 10 seconds per 1 second of realtime in recording process:
pulseaudio
pulseaudio-alsa
pulseaudio-bluetooth
pulseaudio-equalizer
pulseaudio-equalizer-ladspa
pulseaudio-jack
pulseaudio-lirc
pulseaudio-qt
pulseaudio-zeroconf
pulseeffects
pulsemixer
libcanberra-pulse (probably just installed this irrelevant, i know)
libao
pamixer
pavucontrol

What I had installed (I know I left these actually installed) - noconflict
apulse
lib32-libpulse
libpulse

OK, since I spent far too much time already on this. I might uninstall some obvious unneccesary packages and report back now to target a more refined list towards the culprit!

15

SOLUTION:

I isolated the culprit to one package.

pulseaudio-alsa

ALSA configuration for PulseAudio

Note this has been recommended with pulseadio install/uninstall INCORRECTLY [as a default] in repo as quote,

“pulseaudio optionally requires pulseaudio-alsa: pulseaudio configuration (recommended)”

Further, regarding Audacity AFTER uninstall of this component that you must delete your audacity-data folder in users’ home folder. If not, you will receive an error message in Audacity “Error opening recording device” / “Error Code -9997”

Finally you must reboot your system (not just logout/in) but re-init your system.

PROBLEM-SOLVED. Hope this helps someone out there.

PS. AUDACITY WISHLIST: Crashes on linux irregardless of system and hardware specs are persistent and too regular. The ‘recover projects’ always works and recovers just fine. However at this point, it’s just expected that Audacity will 90% of time crash if working beyond one humble file and for less than 15 minutes. Just an FYI wish :exclamation: