From: andersvi@notam02.no
To: emacs-devel@gnu.org
Subject: Re: Sound in Emacs
Date: Thu, 06 Oct 2011 18:42:28 +0200 [thread overview]
Message-ID: <8739f6gjgr.fsf@notam02.no> (raw)
In-Reply-To: FED27AE1BEA240ABB127DE5B0962FBBC@us.oracle.com
>>>>> "D" == Drew Adams <drew.adams@oracle.com> writes:
D> No doubt it does not correspond to everything you both are
D> envisioning, but Bookmark+ lets you easily register (aka
D> "bookmark") any type of file, associate metatdata with it, tag it
D> in various ways and access it using tag set operations, attach
D> any additional code to its activation (aka "jumping to it"),
D> group it in various ways with other files (e.g. a playlist), and
D> so on.
Looks great. Indeed, if Lars' initial suggestion of linking in native
'sound'-support to emacs Bookmark+ (or similar) would come quite far.
D> (Not sure what you meant by "regions", but you can also bookmark
D> specific regions of text files.
This is perhaps more for people working with sound in analytical or
creative contexts, ie. composers or researchers etc. Most sounds in
these working-contexts are typically contained in recorded (or
processed) files, any one file containing several 'regions' -
start-time, duration, channel-index... - one would want to look up
separately without necessary splicing each region out as one soundfile.
D> Alternatively, you can perhaps leverage Org mode's features
D> involving metadata and tagging - dunno.
I think someone made a snd-interface for org-babel. These are nice
places to start.
D> And then there is Stefan's Music Player Daemon (MPD) - dunno
D> about that either, but it sounds like it employs an actual
D> "database" (unlike Bookmark+ (and Org, I imagine), which holds
D> the metadata in plain text files).
Storage isnt a problem as such. Any efficient db system, say mysql,
would work great. Typically sound-collections (in the contexts
mentioned above) grow large, and often are kept on separate
mount-points, and special sound-disks. Looking up a db-server, perhaps
as an option, would be a bonus.
prev parent reply other threads:[~2011-10-06 16:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 19:46 Sound in Emacs Lars Magne Ingebrigtsen
2011-10-03 19:50 ` Julien Danjou
2011-10-03 21:04 ` joakim
2011-10-04 7:01 ` Jan D.
2011-10-04 22:53 ` Tim Cross
2011-10-05 0:23 ` Lars Ingebrigtsen
2011-10-05 0:41 ` chad
2011-10-05 1:26 ` Stephen J. Turnbull
2011-10-08 14:22 ` Thien-Thi Nguyen
2011-10-04 23:44 ` Óscar Fuentes
2011-10-06 7:02 ` andersvi
2011-10-06 7:31 ` joakim
2011-10-06 9:17 ` andersvi
2011-10-06 10:22 ` joakim
2011-10-06 13:29 ` Drew Adams
2011-10-06 15:37 ` Nix
2011-10-06 15:44 ` Drew Adams
2011-10-06 16:54 ` Stefan Monnier
2011-10-06 18:27 ` Nix
2011-10-06 16:42 ` andersvi [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8739f6gjgr.fsf@notam02.no \
--to=andersvi@notam02.no \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).