From: erik quanstrom <quanstro@quanstro.net>
To: conor.williams@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] music storage
Date: Mon, 9 Dec 2013 01:38:32 -0500 [thread overview]
Message-ID: <839950cb8f31b583d75f42a8bf94c96d@mikro> (raw)
In-Reply-To: <CAL6pNZ_jmKO8Exvh4pWA1R5CdTKSeiU3Y9Wur0Of5oZgo-b06Q@mail.gmail.com>
> why didn't Erik rip to Mp3, i what I mean... an album is typically 50MB as
> opposed to 650MB
i can answer that. i wanted full quality, and 150G is less than 15% of the
space i've got. i've got a pair of by the time i run out, i'll have more space.
my srx presents a lun that the fs uses entirely for media. it's backed by
a pair of enterprise 1T drives in raid 1. the low iops of these drives is
not a problem since the bitrate of audio is low by modern standards,
and the stream is largely sequential.
> just downloading a torrent with the mp3's seems simpler
> than swapping cd's. :)
non legal is a non option for me.
but even if it were, one can use the "never underestimate the bandwidth
of a station wagon full of 9 track tapes" principle. it only took 6-8 hrs
of bad cycles, as sam calls them, to get the bulk of these disks loaded.
with my network connection it would have been ~10 days of torture.
> he is refering to play(1) command in 9front which does
> recognize the following audio formats:
backscatter from another list? who is "he" and who refered
to play before?
anyway, that brings up another advantage of pcm:
cat *.pcm > /dev/audio
- erik
next prev parent reply other threads:[~2013-12-09 6:38 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 0:30 erik quanstrom
2013-12-09 0:39 ` Jacob Todd
2013-12-09 1:40 ` Conor Williams
2013-12-09 2:44 ` cinap_lenrek
2013-12-09 3:53 ` Conor Williams
2013-12-09 3:59 ` Jacob Todd
2013-12-09 3:59 ` Jacob Todd
2013-12-09 4:11 ` Conor Williams
2013-12-09 4:16 ` andrey mirtchovski
2013-12-09 4:37 ` Conor Williams
2013-12-09 4:50 ` andrey mirtchovski
2013-12-09 4:57 ` Conor Williams
2013-12-09 6:38 ` erik quanstrom [this message]
2013-12-09 7:14 ` cinap_lenrek
2013-12-09 4:12 ` cinap_lenrek
2013-12-09 20:52 ` Steve Simon
2013-12-09 21:04 ` Steven Stallion
2013-12-09 22:13 ` Conor Williams
2013-12-09 22:18 ` Steven Stallion
2013-12-09 22:53 ` Conor Williams
2013-12-09 23:18 ` erik quanstrom
2013-12-09 23:37 ` Conor Williams
2013-12-09 22:39 ` erik quanstrom
2013-12-09 22:51 ` Conor Williams
2013-12-09 22:55 ` Skip Tavakkolian
2013-12-09 23:09 ` Bruce Ellis
2013-12-09 23:19 ` Conor Williams
2013-12-09 23:25 ` Bruce Ellis
2013-12-09 23:33 ` Jeff Sickel
2013-12-10 0:18 ` Matthew Veety
2013-12-09 22:49 ` erik quanstrom
2013-12-10 0:20 ` erik quanstrom
2013-12-10 0:24 ` Devon H. O'Dell
2013-12-10 0:26 ` Lee Fallat
2013-12-10 1:40 ` Steve Simon
2013-12-10 1:39 ` Steve Simon
2013-12-10 1:52 ` erik quanstrom
2013-12-10 2:22 ` Bruce Ellis
2013-12-10 2:42 ` erik quanstrom
2013-12-10 3:14 ` Bruce Ellis
2013-12-10 3:26 ` andrey mirtchovski
2013-12-10 3:32 ` Bruce Ellis
2013-12-10 11:24 ` Nicolas Bercher
2013-12-10 3:39 ` erik quanstrom
2013-12-10 3:54 ` andrey mirtchovski
2013-12-10 3:57 ` Bruce Ellis
2013-12-10 11:33 ` Aram Hăvărneanu
2013-12-10 2:35 Winston Kodogo
2013-12-10 5:44 ` Conor Williams
2013-12-10 6:46 ` Jeff Sickel
2013-12-10 7:09 ` Conor Williams
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=839950cb8f31b583d75f42a8bf94c96d@mikro \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=conor.williams@gmail.com \
/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).