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

[auditor]

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.

[auditor]

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.

[auditor]

@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 )

[steve]

PS. It would be nice to have some editing ability, even if only 20-30 minutes to edit/correct out post or even delete.

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.

[steve]

Audacity's recording function is busted

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

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

[auditor]

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.

[steve]

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.

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.

[auditor]

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

[steve]

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

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.

[auditor]

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..