From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] playing music (was RSA)
Date: Mon, 31 Jan 2005 12:59:10 -0500 [thread overview]
Message-ID: <ee9e417a050131095943de3e54@mail.gmail.com> (raw)
In-Reply-To: <200501311101.j0VB16Z05598@zamenhof.cs.utwente.nl>
> maybe also sape's playlist server could be used
> (although there are some differences in the
> operations allowed on the playlist, I think)
> such that essentially (some version of) acme Juke
> would just be an alternative to sape's juke gui?
doing that is possible, but it would be a different program.
the one neat thing about ajuke (and acd before it) is that
the acme buffer *is* the playlist. when it's time to
move to the next song, ajuke just looks at the window
text to figure out what was playing and what to play
next.
so editing the playlist is very familiar -- it's no different
from editing text files.
> On the sun I have named pipe's /tmp/dev/audio and /tmp/dev/volume
> and two small programs, one to read audio bytes from /tmp/dev/audio
> and shuttle them to the real sun audio device, and another one
i did that for a while, but on my linux only one app can
have the sound card open at a time, so it got annoying
killing it off and restarting it. this way ajuke can take
care of closing the audio device when it is paused or stopped.
either way the code has to be written.
russ
next prev parent reply other threads:[~2005-01-31 17:59 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-06 21:47 [9fans] RSA + OAEP padding Paul Lalonde
2004-11-06 21:58 ` andrey mirtchovski
2004-11-06 22:01 ` boyd, rounin
2004-11-06 22:13 ` andrey mirtchovski
2004-11-06 22:37 ` Axel Belinfante
2004-11-06 22:56 ` Russ Cox
2004-11-06 23:00 ` boyd, rounin
2004-11-06 23:14 ` andrey mirtchovski
2004-11-07 0:35 ` Christopher Nielsen
2005-01-31 7:03 ` [9fans] playing music (was RSA) Russ Cox
2005-01-31 7:59 ` Kenji Okamoto
2005-01-31 8:05 ` Russ Cox
2005-01-31 8:08 ` Kenji Okamoto
2005-01-31 8:32 ` Russ Cox
2005-01-31 8:41 ` Kenji Okamoto
2005-01-31 11:01 ` Axel Belinfante
2005-01-31 17:59 ` Russ Cox [this message]
2005-01-31 20:07 ` Tim Newsham
2005-01-31 20:21 ` Russ Cox
2005-01-31 20:30 ` rog
2005-01-31 14:45 ` Sape Mullender
2005-01-31 10:56 ` Axel Belinfante
2005-02-02 9:18 ` Kenji Okamoto
2005-02-03 7:54 ` Kenji Okamoto
2005-02-03 8:00 ` boyd, rounin
2005-02-03 9:06 ` Kenji Okamoto
2005-02-03 9:16 ` boyd, rounin
2005-02-03 15:28 ` Sape Mullender
2005-02-04 1:08 ` Kenji Okamoto
2005-02-04 1:17 ` boyd, rounin
2005-02-04 1:20 ` Kenji Okamoto
2005-02-04 1:24 ` boyd, rounin
2005-02-04 1:27 ` Kenji Okamoto
2005-02-04 1:36 ` boyd, rounin
2005-05-07 8:59 ` Ralph Corderoy
2005-05-07 12:57 ` Russ Cox
2005-02-04 9:59 ` Steve Simon
2005-02-04 1:19 ` boyd, rounin
2005-02-04 1:22 ` bs
2005-02-04 13:24 ` Sape Mullender
2005-02-07 2:35 ` Kenji Okamoto
2005-01-31 16:28 ` rog
2005-01-31 17:18 ` Russ Cox
2004-11-07 2:48 ` [9fans] RSA + OAEP padding William Josephson
2004-11-07 5:17 ` Paul Lalonde
2004-11-07 8:12 ` [9fans] venti httpaddr arisawa
2004-11-07 15:40 ` Russ Cox
2004-11-07 22:58 ` arisawa
2005-02-04 2:01 [9fans] playing music (was RSA) YAMANASHI Takeshi
2005-02-04 9:33 ` C H Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee9e417a050131095943de3e54@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).