From: "Charles H Sauer (he/him)" <sauer@technologists.com>
To: coff@tuhs.org
Subject: [COFF] Re: reading historic magnetic tapes
Date: Sat, 28 Jan 2023 14:17:30 -0600 [thread overview]
Message-ID: <9274d976-dad7-06af-b546-23d4091f7ed4@technologists.com> (raw)
In-Reply-To: <6778F07B-DD74-4F04-A877-7D3751E96317@quintile.net>
This seems COFF, not TUHS, and mostly not digital...
I have many 4mm DAT cartridges from 20-30 years ago. Every now and then
I will access one. So far I've yet to see evidence of the media degrading.
On 1/28/2023 4:12 AM, Steve Simon wrote:
> baking old, badly stored magnetic tapes prior to reading them is a common practice.
For the last year+ I have been digitizing selected audio tapes made in
the 70s at AWHQ
(https://en.wikipedia.org/wiki/Armadillo_World_Headquarters). The ones
I've been working with are 1/4" on 10.5" reels. A printed inventory I
was given says "bake" next to almost all of the items, but so far, after
processing roughly 40 reels, I've yet to find one that seemed to need
"baking" (actually, "baking" is a bit overstated, in that best practice
is to raise temperature to roughly 150F --
https://www.radioworld.com/industry/baking-magnetic-recording-tape).
For now, I'm not able to share those AWHQ recordings, but I can share
other recordings I made in the 60s and 70s at
https://technologists.com/60sN70s/. In all those reels, many of which
are cheap, unbranded tape, I didn't find any that seemed to me to need
baking.
Charlie
--
voice: +1.512.784.7526 e-mail: sauer@technologists.com
fax: +1.512.346.5240 Web: https://technologists.com/sauer/
Facebook/Google/LinkedIn/Twitter: CharlesHSauer
prev parent reply other threads:[~2023-01-28 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6778F07B-DD74-4F04-A877-7D3751E96317@quintile.net>
[not found] ` <1595e77d-697c-b2e8-5aff-fe63c92f4747@ucsb.edu>
2023-01-28 20:12 ` [COFF] Re: [TUHS] " Michael Kjörling
2023-01-28 20:17 ` Charles H Sauer (he/him) [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9274d976-dad7-06af-b546-23d4091f7ed4@technologists.com \
--to=sauer@technologists.com \
--cc=coff@tuhs.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.
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).