Live data from Hacker News

Show HN: Onhold – Play sounds while and after shell jobs complete

github.com

11–16 of 16 posts

Re: Show HN: Onhold – Play sounds while and after shell jobs complete

#11
Here's what I'd love to have: an ambience. Turning metrics like CPU, memory, IO and network loads into subtle sounds. Some more important background jobs execution into more distinct, but still somewhat subtle sound.

Basically, like the bridge of Enterprise D[0] (or its main engineering[1]).

The reasoning here is to recreate the experience of "feeling" the machine. Like drivers do with their cars. Like we could do in the past with HDD sounds, and now sometimes with fan noise[2].

Last time I mentioned it publicly, someone told me they use widgets with resource usage graphs for that purpose. I've started using them too, but I noticed that I generally don't look at them. Even semi-transparent, they're mostly just a blob of color that occasionally obstructs some UI I need to interact with. But sound is a separate channel, and easier to process subconsciously.

Anyone knows of tooling relevant to implement this idea?

--

[0] - https://www.youtube.com/watch?v=XajaCX88NnU

[1] - https://www.youtube.com/watch?v=GwLsBldD9kQ

[2] - During a recent debugging session, I accidentally gained some insight about the problem by noticing the fan is making less noise than it should during certain tests.

Re: Show HN: Onhold – Play sounds while and after shell jobs complete

#12
post #6

To ring terminal bell after running process > Ctrl+g # (^g) Or any of: > tput bel > echo -n -a "\a" > echo $'\a'

+1 for tput bel. I like it because it's memorable. I have it aliased on the end of my unit / integration tests. It's nice for long running processes.

Re: Show HN: Onhold – Play sounds while and after shell jobs complete

#13
post #6

To ring terminal bell after running process > Ctrl+g # (^g) Or any of: > tput bel > echo -n -a "\a" > echo $'\a'

On MacOS instead of tput bel I use: `say "finished"` (or something)

For non-Mac users: `say` will activate a voice saying some text

Re: Show HN: Onhold – Play sounds while and after shell jobs complete

#14

Here's what I'd love to have: an ambience . Turning metrics like CPU, memory, IO and network loads into subtle sounds. Some more important background jobs execution into more distinct, but still somewhat subtle sound. Basically, like the bridge of Enterprise D[0] (or its main engineering[1]). The reasoning here is to recreate the experience of "feeling" the machine. Like drivers do with their cars. Like we could do i…

Interesting idea! I found Peep[1], but seems the links are dead. Still, that led me to [2] and then [3], though none implement exactly that approach.

[1] https://www.usenix.org/legacy/publications/library/proceedin...

[2] https://sonification.de/handbook/chapters/chapter18/

[3] https://github.com/dbermbach/audiocues

Re: Show HN: Onhold – Play sounds while and after shell jobs complete

#15
Here's what I did to make sound come after a command:

  import os
  from random import seed
  from random import random
  seed(a=None)
  def rnd():
          return 200 + (random() * (2100 - 200))
  duration = 0.5
  freq = rnd()
  os.system('play -nq -t alsa synth {} sine {}'.format(duration, freq))
The only requirements are python and sox[0].

Used like this:

  mycommand && python3 sound.py
--

[0] - https://manpages.debian.org/jessie/sox/play.1.en.html

Re: Show HN: Onhold – Play sounds while and after shell jobs complete

#16

Here's what I'd love to have: an ambience . Turning metrics like CPU, memory, IO and network loads into subtle sounds. Some more important background jobs execution into more distinct, but still somewhat subtle sound. Basically, like the bridge of Enterprise D[0] (or its main engineering[1]). The reasoning here is to recreate the experience of "feeling" the machine. Like drivers do with their cars. Like we could do i…

There was a wonderful project "choir.io" that did exactly this: https://news.ycombinator.com/item?id=6220740

I got early access and wired it into our software, which essentially processed streams of various events. And you could get a sense for when the pace picked up, or something unusual was happening more often than normal. Sadly the project was shut down at some point.

Post reply on HN