Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use a dedicated emacs daemon for playing sounds #31

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

juergenhoetzel
Copy link

I experienced stuttering sound and sometimes the UI was lagging on a slow device. Using a dedicated daemon fixes this issue for me.

Instead of constantly forking of Emacs instances which may result in
Emacs lagging constantly.
@TatriX
Copy link
Owner

TatriX commented Dec 1, 2019

Thanks for the PR!
I'm getting

Error running timer ‘play-sound-file’: (error "No usable sound device driver found")

in the pomidor server.

Also it seems that running server will stay in the background, even if you close *pomidor* buffer or Emacs itself.

I think we can add this as a new function so those who need it can customize pomidor-play-sound-file to use it.

@juergenhoetzel
Copy link
Author

Error running timer ‘play-sound-file’: (error "No usable sound device driver found")

What system do you have? On GNU/Linux Emacs uses alsa and most distributions use a pulseaudio config for alsa:

cat /etc/asound.conf 
# Use PulseAudio by default
pcm.!default {
  type pulse
  fallback "sysdefault"
  hint {
    show on
    description "Default ALSA Output (currently PulseAudio Sound Server)"
  }
}

ctl.!default {
  type pulse
  fallback "sysdefault"
}

# vim:set ft=alsaconf:

and thus has the ability to synchronize multiple playback streams.

in the pomidor server.

Also it seems that running server will stay in the background, even if you close *pomidor* buffer or Emacs itself.

Good catch!

I think we can add this as a new function so those who need it can customize pomidor-play-sound-file to use it.
👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants