Audacity records faster [SOLVED]

OK, so that will be using PulseAudio.

Are you using PulseAudio volume control (pavucontrol)? If not, how are you telling PulseAudio to record what is playing from your web browser?

Ok! Just came back from shopping!

Yes, I’m using PulseAudio.

And in PulseAudio I say All streams, All output devices and All input devices.

I’m not on Xubuntu, so you will have to tell me how you do that.

Ok: there we go! This is how I configure Pulse Audio.

The Gui for Pulse audio looks like this (it’s a Catalan interface):

On the first tab I’ve got Playing:

(I choose All input devices)

On the second tab (Recording):

(I choose All streams)

On the third tab (Output devices):

(I choose All output devices)

On the fourth tab (Input devices):

(I choose All input devices)

On the last tab (Settings):

(I choose All streams)

This is how I do it.

(PS Thanks very much for your help and patience. I don’t know much about Audacity and you’re spending a lot of your time on this topic.)

If you actually have permission to do that then you can probably download the generated file from their server (I can do it on Windows but we’re not telling you exactly how to do that). :wink:

The files are 22050 Hz sample rate. Does changing the project rate bottom left of Audacity give more consistent results?

Is your Firefox up to date?


Gale

If you actually have permission to do that then you can probably download the generated file from their server (I can do it on Windows but we’re not telling you exactly how to do that). > :wink:

I think I should say I don’t have explicit permission: as a demo web site, I write the sentences and get the sound of the sentences. I catch them on the fly using Audacity. (I would be much easier to have that sound as a file, but it’s Ok for me!) So I’m a simple user of the site, for educational purposes only :unamused:

The files are 22050 Hz sample rate. Does changing the project rate bottom left of Audacity give more consistent results?

The files are 22050 and I export them as mp3 VBR 9, because for voices the files keep the quality and they become really small. I am no using ogg files because the educational program which manages the sound, text and images, does not accept ogg files.

Mmm… Wait a minute…

Yeah! I have just changed the preferences, closed Audacity and entered again. And the first time I recorded a sound is Ok!
Let me try again if I change the sample rate again to 22050…
Close…
Open…
And it works again!

Let me think… I’m a bit shocked. I’m not really sure if the issue is this sample rate change or that I reconfigured the Pulse Audio settings before…

Anyway: the question is that now it works! Surely you may know why does that happen. I don’t understand at all

Tomorrow it may no work: but as for today, thank you two for your help and your time.
From,
Joan

OK, that’s the “Pulse Audio Volume Control” (pavucontrol).
The second tab (recording) is blank because Audacity is not recording. If you open pavucontrol while Audacity is recording you should see Audacity listed as a recording application, and to record what is playing on the computer it should be set to record from the “monitor” input.
Should you need to refer to it in the future, this is all covered in the manual Audacity Manual

It’s quite likely that it is the sample rate change.
Try it out for a few days and let us know how you get on.

I’m not sure if you are changing the project rate bottom left every time or actually did change it at Default Sample Format in Quality Preferences.

If you are only working with speech audio it will probably be more convenient to make the change in Preferences then for each new project and each time you launch Audacity you will start with 22050 Hz sample rate.


Gale

I’m not sure if you are changing the project rate bottom left every time or actually did change it at Default Sample Format in Quality Preferences.

That’s what I did: if I change directly on the screen, the next time starts with the older sample rate.

If you are only working with speech audio it will probably be more convenient to make the change in Preferences then for each new project and each time you launch Audacity you will start with 22050 Hz sample rate.

Exactly: that’s why I do it that way!

And now… I find that Audacity doesn’t work well again. :frowning:

When I start the program, records too fast (and when I play the sound is too grave and slow).
Then I record again, and works well.

I don’t understand at all. :open_mouth:

Joan

It does happen on Linux sometimes.

When you launch Audacity, do you just click on the Audacity icon or do you click on an Audacity AUP file or WAV file?

What happens if you just click on the Audacity icon then CTRL + P to open Audacity Preferences and then click OK in Preferences (without changing settings from 22050 Hz)? Does it record properly then?

Gale

When you launch Audacity, do you just click on the Audacity icon or do you click on an Audacity AUP file or WAV file?

I usually start by clicking the Audacity icon.

What happens if you just click on the Audacity icon then CTRL + P to open Audacity Preferences and then click OK in Preferences (without changing settings from 22050 Hz)? Does it record properly then?

I have just tried right now. Nope, the first recording doesn’t work. The second does.

After having tried this, I tested it again, looking at the Audacity log:

Audacity starts:

Audacity log:
08:49:13: Audacity 2.0.5
08:49:15: Retrieving FFmpeg library version numbers:
08:49:15: AVCodec version 0x362300 - 54.35.0 (built against 0x362300 - 54.35.0)
08:49:15: AVFormat version 0x361404 - 54.20.4 (built against 0x361404 - 54.20.4)
08:49:15: AVUtil version 0x340300 - 52.3.0 (built against 0x340300 - 52.3.0)

I start recording for the first time (at 08:49:30):
08:49:13: Audacity 2.0.5
08:49:15: Retrieving FFmpeg library version numbers:
08:49:15: AVCodec version 0x362300 - 54.35.0 (built against 0x362300 - 54.35.0)
08:49:15: AVFormat version 0x361404 - 54.20.4 (built against 0x361404 - 54.20.4)
08:49:15: AVUtil version 0x340300 - 52.3.0 (built against 0x340300 - 52.3.0)
08:49:33: Error:Failed to get file system statistics (error 2: El fitxer o directori no existeix)
08:49:33: Error:Failed to get file system statistics (error 2: El fitxer o directori no existeix)
08:49:33: Error:Failed to get file system statistics (error 2: El fitxer o directori no existeix)
08:49:36: Error:Failed to get file system statistics (error 2: El fitxer o directori no existeix) (file or folder don’t exist)

Until I stop recording.
The next time I record, nothing else is added to the Audacity log.

I don’t understand all the reasons that message occurs, but I know it can relate to file/path name tests as well as disk space tests. I have occasionally seen that message appear when there are dropouts in a recording Recording stops, happens with cracks and hiccups, so it can indicate recording problems.

Have you tried initialising audacity.cfg? Quit Audacity then open ~/.audacity-data/audacity.cfg in your favourite text editor and follow Audacity Manual. This will reset Default Sample Rate to 44100 Hz but setting it to 22050 Hz is not always helping.

How much of a nuisance is this, versus doing R and SPACE first time you launch Audacity? There are lots of alternatives, like working out how to download the files, recording with a loopback cable (if you have stereo line-in) then choosing the (hw) input instead of pulse, or seeing if your audio device can be configured to default to 22050 Hz. That probably means messing with ALSA configuration files, and you would not want to do it if you ever use the computer to play music.

You could also try reinstalling pulseaudio.

By the way on Ubuntu 13.10 I don’t have CubebUtils Firefox audio callback driver as a playback device in pavucontrol when playing a phrase on acapela-group. It just says “audio stream” with Firefox icon. And I don’t have your recording speed problem or log messages even when recording at 44100 Hz, using Audacity 2.1.0-alpha.


Gale

Have you tried initialising audacity.cfg? Quit Audacity then open ~/.audacity-data/audacity.cfg in your favourite text editor

Aha! It had to be that!

I made it simpler: I renamed the audacity.cfg, for if…

Started again and… worked.

Then I went to Preferences, turned to 22050 Hz, quit, started again and worked!

Then I went to Preferences again, Devices and turned to Mono. Quitted, and worked again as I started Audacity.

You were right! And I can’t be more thankful!

You should win a trophy for you knowledge, your patience and your perseverance!

Thanks so much for your help!

Joan

PS: How can I edit the title so that I can write solved in it?

OK, but you may find that setting Default Sample Rate 22050 Hz isn’t necessary - it “shouldn’t” be necessary.

Have the log errors about file system statistics disappeared when you first record in an Audacity session?

When resetting .cfg helps, it’s rarely clear in what way it helps. If you still have the renamed audacity.cfg, feel free to attach it and we can have a look.

Press the Edit button in your first message and add [SOLVED] to the end. But I would wait a while to make sure it really is solved.


Gale

Have the log errors about file system statistics disappeared when you first record in an Audacity session?

Er… No! :blush:

If you still have the renamed audacity.cfg, feel free to attach it and we can have a look.

Ok! Here it goes!
(It didn’t let me send the file with a cfg extension. I changed it to txt)

Press the Edit button in your first message and add [SOLVED] to the end. But I would wait a while to make sure it really is solved.

Yes, that will be wiser. I’ll wait…
audacity.txt (3.62 KB)

Thanks. I don’t see much unusual there. You had Default Sample Format on 16-bit, whereas the shipped default is 32-bit float.

You had redundant settings for a now removed feature that cached audio data in RAM. It’s not very likely that redundant setting affects recordings.

Gale

However, it sounds ok, now…
:neutral_face: :wink: :slight_smile: :stuck_out_tongue: :smiley: :laughing:

(That’s why I’m happy
-Clap along if you feel what happiness is to you…-)

I asked for help to a friend, and he told me something like this:

This issue is related to the audio speed recording.
First, you can take a look at the quality in PulseAudio:

pacmd list-sinks |grep sample

The answer should be something like:

sample spec: s16le 2ch 44100Hz

In case you haven’t got this speed in Audacity, you can edit the Pulseaudio configuration file:

gksu gedit /etc/pulse/daemon.conf

and edit the line

; default-sample-rate = 44100

You can modify this line and remove the first semicolon. As you can see, these are the default values for Pulseaudio.

If the speed is the same in both programs, you shouldn’t have any problem in audio recording.[/color]

Well, that is the answer he gave me. I suppose it’s in the same direction as you suggested: (change the speed to 44100Hz…)

I leave the comment for if it is of some help to anyone.

Yours,
Joan

Thanks for posting that.

Yes that is the configuration file I meant, if you choose the pulse or default device to record from.

If you had chosen the (hw) device to record from, it’s possible the problem may not have happened. The problem is seemingly that pulse can’t always cope with resampling the 22050 Hz file to 44100 Hz somewhere along the line, even if Audacity project rate is 22050 Hz.

So the theory would be that if you edited the /etc/pulse/daemon.conf file to:

default-sample-rate = 22050

and restarted the computer then pacmd list-sinks |grep sample would show

sample spec: s16le 2ch 22050Hz

and there should not (I think) be any resampling going on anywhere.

However since you have a low sample rate file it’s not recommended to set your pulse device to such a low default. Sometimes audio devices on Linux default to 48000 Hz and if that was the case and the file was 44100 Hz then changing the pulse default to 44100 Hz might help any speed problems that occurred in the recording.


Gale

I can’t say anything but: Thanks, thanks thanks to you all.

Joan