Hello.
Recently, I installed in my pc Linux Mint 17 KDE (before, I was use Linux Mint 13 Mate and with this distribution and desktop, any problem with audacity), well, I don’t know the reasson but, I opne Audacity, I made some record and when click in play, the velocity play always is to top. I view in config, play velocity is in 1, but audacity play in other velocity. I change the velocity, but audacity play in other velocity.
When I try 3,4 o 5 times to made some change for try if I can solved this issue, audacity not respond and I need brute close.
Since my post, I made some tests, I have more information about this:
My computer:
I have a internal sound card in my motherboard, but in this moment, I don’t have any connected to this sound card.
And I have a hdmi sound by graphic card.
In this moment, I use this hdmi por for sounds.
My problem, only appears when I record a sound and play this sound but if a save this sound, close Audacity, open Audacity and the record sound, any problem.
But if I record a sound and click in play, the speed play its top, and if in the moment that play the sound with this wrong speed I click in stop, or pause or other buttom its when Audacity crash.
I view that, If in Playback device I select a HDA Nvidia HDMI 0(hw:1,3) I don’t have any problem, but I don’t have any sound, but in the Playback level appears that I have sound but I don’t have any sound in my computer.
The same if I select in Playback device HDA Ati SB: ALC889 Digital (hw0,1) (this is my sound card of my motherboard).
The same with other options except with “Default” or with “Pulse” with this 2 options, I have sound but I have the problem indicate in this thread.
I update Audacity by the daily ppa for if some update resolved the issue, but continue with the same problem.
Do you mean the speed is too fast? Do you need to change the speed? You can play and stop at normal speed using SPACE (Space Bar).
This is expected if you start and stop playback very quickly or hold down SPACE or the Play or Stop button. It is a problem between Pulse and Audacity. Try launching Audacity from the Terminal by opening the Terminal, typing this:
env PULSE_LATENCY_MSEC=30 audacity
then hit ENTER on your keyboard. This should prevent the crashes and may fix the playback being too fast with the normal Play button or SPACE.
I don’t understand very well the question, but yes I referrer a Transcription Toolbar of speed play.
Do you mean the speed is too fast? Do you need to change the speed? You can play and stop at normal speed using SPACE (Space Bar).
Yes, I’m mean the speed si too fast but in the Transcription Toolbar of speed appears a 1 value of speed and I click in play in the “normal” buttom, not in the speed buttom play.
I don’t know if I can play and stop at normal speed using SPACE when I have this problems.
No, I don’t start and stop playback very quickly.
In the first click to play, I have the problem with speed play.
Try launching Audacity from the Terminal by opening the Terminal, typing this:
env PULSE_LATENCY_MSEC=30 audacity
>
> then hit ENTER on your keyboard. This should prevent the crashes and may fix the playback being too fast with the normal Play button or SPACE.
I try with this by Terminal one time, I think that, opening by Terminal my problem dissapears, works well.
I paste that appears in Terminal:
```text
(process:14762): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised
(process:14762): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
(process:14762): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised
(process:14762): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
bt_audio_service_open: connect() failed: Conexión rehusada (111)
bt_audio_service_open: connect() failed: Conexión rehusada (111)
bt_audio_service_open: connect() failed: Conexión rehusada (111)
bt_audio_service_open: connect() failed: Conexión rehusada (111)
Cannot connect to server socket err = No existe el archivo o el directorio
Cannot connect to server request channel
jack server is not running or cannot be started
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4611
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4611
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4611
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4611
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4611
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
Do you get those messages without playing audio, or also when playing?
And do you get those same messages if you just type “audacity” at the terminal, without the env command?
If the audio playback is still a problem, you could try increasing “Audio to buffer” in the Audacity “Recording Preferences”. That setting affects playback too.
Also you may find that if you choose the “dmix” device for playback that the audible problems do not occur.
Its strange, the test I made today, I don’t have this error message, with typing “audacity” at the terminal and without the env command.
If the audio playback is still a problem, you could try increasing “Audio to buffer” in the Audacity “Recording Preferences”. That setting affects playback too.
Ok, you refer at latency?
Also you may find that if you choose the “dmix” device for playback that the audible problems do not occur.
Ok.
When I have more tests and information, I post.
