did have Buster on my RPI4. audacity ran fine. upgraded my system to the new Rasperry PI OS (Bookworm). installed audacity. when I click monitoring the db meters show music. when I press the record button, it all stops; nothing on the monitors, no trace in the windows. no time on the meter. i’ve tried all the available options in the audio setup window. even purged and reinstalled audacity.
got no idea where to go next.
I assume Bookworm is a version of Linux?
There is information about recording streaming audio with Windows/MacOS/Linux here. You may have to install PulseAudio if you don’t have it already but I don’t know if it works on the Raspberry Pi.
Just for information:
“Rasperry PI OS” is a Linux operating system, (previously called “Raspbian”). It is based on the popular “Debian” distribution, and has been customised specifically for Raspberry Pi hardware.
“Bookworm” is the code name for Debian 12 (the latest stable release).
How did you install Audacity, and where did you get it from?
I just did “sudo apt install audacity” - where it pulls from? it is ver 3.2.4, which I think is current.
more confusing info: in monitoring the db meters dance to the music. when I hit record, there is a micro second of monitoring before it all drops dead. if not monitoring and hit record also get a blip on the db meters before it stops. then it looks like I never pressed record.
it acts like there is no path to record.
That will give you the latest official version from the Raspberry PI OS maintainers.
It may be worth checking the “Temporary files directory” is a valid, writeable location.
Note also that Audacity cannot write projects to FAT formatted drives.
I don’t understand “temporary files directory”. where is this and how would I check its validity? is there a setting in audacity that points to the scratch partition. i’ve never looked at the SD card partitions - I have 50gig available disk space.
I wonder if the mirror site apt is pulling from has a broken audacity.
Edit → Preferences → Directories
went there. shows two files: new project 2024-09-28 19-34-32 n-1.aup3unsaved
:new project 2024-09-32 19-34-32 n1.aup3unsaved-wal
audacity seems to create files even if it won’t open/write to them.
Current version is 3.6.4 here.
You can check the format of the disks connected to the computer with this command in a terminal:
lsblk -f
i’m going to be on the road for the next week, so I won’t be able work on this problem.
i’m thinking of loading snapd so I can get a release from audacity.
as for disk format, raspberry pi os creates a fat boot sector and the rest of the SD card is ext4 - or this is what i’ve read. not sure bookworm plays like this.
EXT4 is OK for Audacity projects. It is just FAT formatted drives that are a problem.
(The problem is that FAT is an ancient file system that does not support certain kinds of access that are required for SQLite database files, and an Audacity “.AUP3” file is an SQLite database).
You don’t need snapd.
Official Audacity releases for Linux are “AppImage” files, and are available from the Audacity website: https://www.audacityteam.org/
back on this project.
is it possible the the 64bit version of audacity doesn’t like the armV7 32 bit processor in my pi? I checked what I had before I upgraded the OS and it was audacity 2.2.2 - a 32 bit app.