[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: arsclist record archive (data, sound or both?)
Steve, where does the 1 MB per sound file come from? I presume you mean
nine minutes of music. That's 9/80 of a 640 MB CD, or 71.11 MB. So what
sort of compression are you using? Using 8:1 MP3 compression, this is 8.89
MB, but since it's mono, it's 4.44 MB. So what's your reasoning?
While you're at it, where did the two million 78s come from? I think you
can figure out an approximate total of Victors from Mike Sherman's _The
Collector's Guide to Victor Records_ and perhaps extrapolate to the number
of total 78s from all record labels.
By the way, I added (rounding to the nearest million) the total number of
Victor records sold from page 169 of the book:
1900-10 42 m.
1911-23 334 m.
1924-41 388 m.
Total 1900-42 764 m.
I wonder how many record titles *and* record sales were classical and what
it was for other labels.
Frank
On 2002-12-11, stevenc@xxxxxxxxxxxxxx opined [message unchanged below]:
>
> ----- Original Message -----
> From: "Premise Checker" <checker@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> To: <ARSCLIST@xxxxxxxxxxxxxxxx>
> Sent: Wednesday, December 11, 2002 6:17 PM
> Subject: Re: arsclist record archive (data, sound or both?)
>
>
> > How do you figure 4 TB?
> Figure 2,000,000 78's (my estimate of the number produced). Figure two
> sides per 78 (true in most cases). Figure about 1MB per mono sound file
> (I may have the only stereo 78, a test, ever pressed?). Multiply the above.
> The fact that a terabyte is slightly larger than 1,000,000,000,000 bytes,
> and the allowance for SF discs, will allow room if I've underestimated.
> Now, I've seen 160GB hard drives for sale for around Cdn$300...chain
> about 25 of those in a RAID setup, and there's your archive!
> As far as copyright problems, two considerations...
> 1) If this were done by a library (or presumably a school), there would be
> no for-profit use involved, although the ability for clients to obtain
> copies
> might have to be restricted...just like library books.
> 2) Here in Canada, the last 78 will be p.d. as far as the recording is
> concerned in just over eight years (end of 2010).
> ...stevenc
> > Since a GB is now around one dollar, we're talking
> > about $4K, not quite pocket change but neither a fortune. Wait ten years
> > and it will be a tenth as much. Keyboarding and programming are the big
> > expenses.
> >
> > Frank
> >
> > On 2002-12-11, stevenc@xxxxxxxxxxxxxx opined [message unchanged below]:
> >
> > > As I understand it, most of the "archives" mentioned in this thread are
> > > essentially on-line catalogs of library holdings (I could be
> wrong)...and
> > > as such they will only contain non-commercial recordings and alternate
> > > takes, especially unissued ones, if these are among the library
> holdings.
> > >
> > > My long-term solution, of course, is the creation of a sort of ultimate
> > > data archive...a database covering every known sound recording (or
> > > even every known 78rpm [+/-] sound recording) with as much
> > > information as is known on each. I think this is what the creators of
> > > AVRL had in mind.
> > >
> > > However, a simpler and easier temporary project might be an
> > > "archive of archives"...that is, a listing of all digital, particularly
> > > internet-accessible, archives concerning either 78rpm or all
> > > sound recordings held or compiled by different individuals or
> > > institutions, along with URL's and information on the accessiblity
> > > (private or public? cost? hardware/software requirements? etc.)
> > > of these archives. This could then be rewritten in HTML and
> > > posted to, or linked to, discographic sites. This way we (and,
> > > for some on the list, our clients) would know where to find any
> > > information we might seek (assuming it is web-accessible).
> > >
> > > There are still problems, of course...two of these are the various
> > > formats used to create the archival files and the accuracy of the
> > > data therein. I am hoping to see the first taken up by ARSC (in
> > > fact, have suggested this as a program subject to Sam B. for the
> > > next ARSC), since it is an area where standardization would help;
> > > the second simply requires proofreading and correction (if
> > > possible).
> > >
> > > In any case, we now have the technology to create a practical
> > > archive of information and make it available. It might, in fact, be
> > > feasible to archive digital versions of the actual sound of the
> > > recordings (I figure around 4TB of storage would be needed).
> > > Who is going to do it, and how, remains to be seen...
> > > Steven C. Barr
> > > ----- Original Message -----
> > > From: "joe@xxxxxxxxxxx" <sergei01@xxxxxxxxxxxxx>
> > > To: <ARSCLIST@xxxxxxxxxxxxxxxx>
> > > Sent: Wednesday, December 11, 2002 1:18 PM
> > > Subject: Re: arsclist record archive
> > >
> > >
> > > > Does it also catalog non-commercial recordings such as air checks,
> > > > transcriptions, alternate takes?
> > > see above...
> > > -
> > > For subscription instructions, see the ARSC home page
> > > http://www.arsc-audio.org/arsclist.html
> > > Copyright of individual posting is owned by the author of the posting
> and
> > > permission to re-transmit or publish a post must be secured
> > > from the author of the post.
> > >
> > >
> >
> > -
> > For subscription instructions, see the ARSC home page
> > http://www.arsc-audio.org/arsclist.html
> > Copyright of individual posting is owned by the author of the posting and
> > permission to re-transmit or publish a post must be secured
> > from the author of the post.
> >
>
> -
> For subscription instructions, see the ARSC home page
> http://www.arsc-audio.org/arsclist.html
> Copyright of individual posting is owned by the author of the posting and
> permission to re-transmit or publish a post must be secured
> from the author of the post.
>
>
-
For subscription instructions, see the ARSC home page
http://www.arsc-audio.org/arsclist.html
Copyright of individual posting is owned by the author of the posting and
permission to re-transmit or publish a post must be secured
from the author of the post.