6 Dec
2006
6 Dec
'06
5:22 p.m.
On 12/6/06, Chuck Guzis <cclist at sydex.com> wrote:
On 6 Dec 2006 at 14:24, John R. wrote:
Yeah I guess one way is the "embedded systems" approach and the other
is a desktop approach. For archival purpose I think your idea is
better. For daily use (the SVD is a "peripheral" that travels between
machines) I think the decoded data is probably better.
On the desktop I expect you still wouldn't store the raw data, but
pipe to a filter that decodes it and store that.
-- John.
A good start:
http://www.thesvd.com/SVD/
Thanks for the link!
An interesting idea. If my mind isn't playing tricks on me, there
also was a similar commercial device for the PeeCee sometime during
the 80's. Freakishly expensive, even for then.
The SVD widget appears to store decoded data (256KB SRAM), which
means it has to know something about the system it's working with. I
haven't looked at the firmware listing yet, so I'm fuzzy on details.
Is it better to store undecoded data streams (like a Catweasel) or
the decoded data? My inclination is to deal with raw track data
without attempting to interpret it. Requires quite a bit more memory
to store data, but has fewer limitations.