all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: joakim@verona.se
To: andersvi@notam02.no
Cc: emacs-devel@gnu.org
Subject: Re: Sound in Emacs
Date: Thu, 06 Oct 2011 09:31:39 +0200	[thread overview]
Message-ID: <m3vcs2k23o.fsf@chopper.vpn.verona.se> (raw)
In-Reply-To: <8762k2iov8.fsf@notam02.no> (andersvi@notam02.no's message of "Thu, 06 Oct 2011 09:02:51 +0200")

andersvi@notam02.no writes:

>     L> If you're in a dired buffer, you can hit RET to see images, but
>     L> sound files aren't as available.  Wouldn't it be nice if you hit
>     L> RET on an .mp3 file, and Emacs pops up a waveform buffer and
>     L> starts playing the file?  And you can skip around in the
>     L> song/podcast...
>
> Possibly the closest you get atm is setting up Snd
> (https://ccrma.stanford.edu/software/snd/) as an inferior scheme
> process, and control it from emacs via existing major or minor-modes, or
> build further to integrate more tightly into eg. dired.  Everything in
> Snd is controllable and accessible from a running scheme.
>
> Linking in libsndfile, which is rather x-plattform i beleive, would
> provide builtin access for reading (and writing) the various sound-file
> formats around.
>
> A project id like to get going is setting up a database type app for
> sound - something similar to various photo-managers - where info from a
> sound gets stored and managed - diskfile, region, format, tags and
> metadata of all sorts - - and made available through a general
> interface.  Send a query to find certain regions from some files, and
> ask a running sound-editor to show them.  Edit them, update metadata
> info, headers etc. on a set of matches (ie. add a tag or similar) etc.
>
> Ideally an interchange format (SDIF?) would make exported data usable by
> all sorts of clients, import into your DAW, export a region into a
> soundeditor and get the edited version back w. updated metadata...
>
> Emacs would be an ideal environment to access all this.

I'm very interested in this sort of thing also. I suppose it's off topic
for this thread though. Anyway, briefly, my conclusion is the same as
yours. All filetypes can be meta tagged the same way technically. then
you need a common storage(I've been experimenting with rdf indexing on
top of xattrs) and indeed Emacs is ideal for large scale tagging.

>
> -anders
>

-- 
Joakim Verona



  reply	other threads:[~2011-10-06  7:31 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 [this message]
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

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=m3vcs2k23o.fsf@chopper.vpn.verona.se \
    --to=joakim@verona.se \
    --cc=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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.