Just Solve the File Format Problem - User contributions [en]

Citation File Format

2023-07-31T16:14:18Z

Azertus: add stub

{{FormatInfo
|subcat=Bibliographic data
|extensions={{ext|cff}}
|released=2017
}}
'''CFF''' (Citation File Format) is a [[YAML]] based file format for citing software, which is both human and machine readable. The specification of the file format is being maintained on GitHub. The canonical filename of a CFF file is CITATION.cff.

== Links ==
* [https://github.com/citation-file-format/citation-file-format GitHub specification]

DICOM

2022-07-26T18:44:08Z

Azertus: /* Links */ add blog post link

{{FormatInfo
|subcat=Health and Medicine
|extensions={{ext|dcm}}, {{ext|dic}}, {{noext}}, others
|mimetypes={{mimetype|application/dicom}}, {{mimetype|image/dicom-rle}}
|pronom={{PRONOM|fmt/574}}
|kaitai struct=dicom
|released=1985
}}
'''DICOM''' (Digital Imaging and Communications in Medicine) is far and away the most widely-used (and probably the oldest) electronic file format in medical imaging. Nearly every device that acquires medical images – ultrasound, CT, PET, and MRI – acquires DICOM images in normal operation. There's a [http://medical.nema.org/standard.html 20-part specification] detailing the file format and its ecosystem. The IANA has assigned TCP and UDP port 104 to DICOM-related traffic.

It's kind of a big deal.

However, as with any sufficiently-adopted standard, there are splinter factions. The most common format is 2-dimensional images or "slices" that can be formed into a 3-dimensional image; however, some manufacturers have extended the standard to save 3 or even 4-dimensional images in a "mosaic" format.

The earliest versions of the standard were known as ACR/NEMA, after the American College of Radiology and National Electrical Manufacturers Association.

== Format ==
While there are many complications involved in decoding a DICOM file, fundamentally it is simply a sequence of data blocks called ''attributes'' or ''elements''. Each attribute contains a 16-bit ''group number'' and a 16-bit ''element number'', conventionally written in hexadecimal and separated with a comma, e.g. "(0028,0011)".

=== Standard attributes ===

If an attribute's group number is even, then it is a standard attribute defined in the DICOM specification, and the group and element number together uniquely identify the meaning of the attribute.

=== Private attributes ===

If the group number is odd, then it is a ''private'' attribute, and it will have been preceded by a special attribute supplying a "private creator" identification string. A private attribute is uniquely identified by the combination of its creator identifier, group number, and the ''low byte'' of its element number.

Some examples of creator identifiers are <code>GEMS_IMAG_01</code> and <code>Philips Imaging DD 001</code>. An identifier is usually specific to a manufacturer of medical equipment, not to a particular medical device. Unfortunately, instead of having one specification per manufacturer, private attributes are usually only documented in device-specific "DICOM Conformance Statements", which list only the attributes used by that one device.

Examples of DICOM Conformance Statements (search the documents for "private creator"):
* [http://www.gehealthcare.com/usen/interoperability/dicom/products/ct_dicom.html GE Healthcare CT DICOM Conformance Statements]
* [http://www.healthcare.philips.com/main/about/Connectivity/dicom_statements/mri_statements.wpd Philips MRI DICOM Conformance Statements]

Compilations:
* http://svn.sourceforge.jp/svnroot/pgctn/pgctn/trunk/main_tree/dicomviewer/univiewer/dcmdict.txt

== Types of DICOM files ==

=== Little-endian vs. big-endian ===
A DICOM file may use either little-endian or big-endian [[Endianness|byte order]] for certain representations of numbers. Little-endian is more common.

=== Explicit VR vs. Implicit VR ===
A DICOM file may use either ''Explicit VR'' or ''Implicit VR'' format. VR stands for ''Value Representation''.

''Explicit VR'' means that each attribute has its data type stored in the file.

''Implicit VR'' means that the attribute types are not stored in the file. The decoder will have to use a data dictionary of its own to figure them out.

=== With header vs. Without header ===
When stored on disk, DICOM files are supposed to begin with a header, though not all of them do. Files with a header are sometimes called '''Part 10''' files.

When a header is present, the file begins with a 128-byte preamble that is usually set to all zero bytes, but which may be used for application-specific purposes. The next 4 bytes are the ASCII signature "DICM". Following the signature is a set of "Group 2" attributes, in little-endian, explicit-VR format. After the Group 2 attributes is the main part of the file, using the format given by the Transfer Syntax UID (0002,0010) attribute. ("Transfer Syntax" is the DICOM term for "file format".)

Files without a header ''usually'' use Implicit VR, little-endian format.

=== Modality ===
One of the most important attributes in a DICOM file is ''Modality'' (0008,0060). It indicates the type of data stored in the file, and often corresponds to the type of machine that created the file. For example, a modality of "MR" means MRI, and "US" means ultrasound. Different modalities have different required attributes, and may have different conventions for how to display images contained in the file, etc.

== Identifiers ==
The most common filename extension is '''.dcm'''. Not all DICOM files have a filename extension.

== Identification ==
DICOM files with a header have the ASCII signature "<code>DICM</code>" at byte offset 128.

Files without a header cannot be readily identified, though many begin with bytes <code>08 00 ?? 00</code>.

== Image formats ==
If a DICOM file contains image data, it contains either a single image, or a video clip (usually composed of multiple still images all having the same size and color format). There is an extension called [[Papyrus (DICOM extension)|Papyrus]] that can store multiple different images in a single file.

The image format is determined by attribute (0002,0010): Transfer Syntax UID. If there is no such attribute, the image is uncompressed. Defined formats include:
* [[Run-length encoding]]: UID 1.2.840.10008.1.2.5
* [[DEFLATE]]: UID 1.2.840.10008.1.2.1.99
* [[JPEG]] (lossy): UID 1.2.840.10008.1.2.4.50, etc.
* [[Lossless JPEG (original)|Lossless JPEG]]: UID 1.2.840.10008.1.2.4.57, etc.
* [[JPEG-LS]]: UID 1.2.840.10008.1.2.4.80 and .81
* [[JPEG 2000]]: UID 1.2.840.10008.1.2.4.90, etc.
* [[MPEG-2]]: UID 1.2.840.10008.1.2.4.100, etc.
* [[H.264|MPEG-4 AVC/H.264]]: UID 1.2.840.10008.1.2.4.102, etc.

== Specifications ==
* [http://medical.nema.org/standard.html The DICOM Standard]

== Software ==
Software that reads DICOM files is pretty much everywhere. Most neuroimaging analysis packages have some way of importing DICOMs and turning them in to a higher-dimensional file; open-source stand-alone libraries abound, as well.

* [http://www.pydicom.org/ Pydicom]
* [http://www.cabiatl.com/mricro/mricron/dcm2nii.html dcm2nii]
* [http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page Grassroots DICOM]
* [http://www.healthcare.philips.com/main/about/connectivity/ Philips DICOM Viewer] For Microsoft Windows. Linked to in the sidebar of pages such as this one.
* [[ImageMagick]] (read-only)
* [[XnView]]
* [http://snisurset.net/code/abydos/ abydos]

== Sample files ==
* [http://www.aycan.de/lp/sample-dicom-images.html Examples of DICOM images]
* https://telparia.com/fileFormatSamples/image/dicom/

== Links ==
* [http://medical.nema.org/ DICOM home page]
* [[Wikipedia:DICOM|Wikipedia article]]
* [http://www.textfiles.com/programming/FORMATS/acr-nema.txt A little bit of discussion]
* [https://orthanc.chu.ulg.ac.be/book/dicom-guide.html Understanding DICOM with Orthanc], "a gentle, informal, high-level introduction to DICOM"
* [https://www.vladsiv.com/dicom-file-format-basics/ DICOM File Format Basics]

[[Category:Scientific Data formats]]
[[Category:Graphics]]

Vim script

2022-07-22T12:43:41Z

Azertus: add vim9 script

{{DISPLAYTITLE:vim script}}
{{FormatInfo
|formattype=Languages
|subcat=Programming Languages
|extensions={{ext|vim}}
}}
'''vim script''' (or vimscript) is the scripting language for the vim text editor. A backwards-incompatible version, vim9 script or vim9script, was released in June 2022 [https://www.vim.org/vim90.php].

== Documentation ==
* [http://vimdoc.sourceforge.net/htmldoc/usr_41.html vim documentation]

== Examples ==
* [http://www.vim.org/scripts/ Some vim scripts]

== Links ==
* [http://www.vim.org/ Official vim site]
* [https://groups.google.com/g/vim_announce/c/2XYAoPL2sqg vim9 script announcement]
* [https://www.vim.org/vim90.php vim9 script release]

M4

2022-07-22T12:35:51Z

Azertus: add sample files

{{FormatInfo
|formattype=Languages
|subcat=Programming Languages
|extensions={{ext|m4}}
|released=1977
}}
'''M4''' is a general-purpose macro processing language. It is probably most often encountered in the context of configuring ''sendmail'' or [[Autotools|autoconf]], both of which use it to generate their inscrutable native configuration files.

== Software ==
* [http://www.gnu.org/software/m4/m4.html GNU M4]

== Sample files ==
* https://telparia.com/fileFormatSamples/text/m4/

== Resources ==
* [[Wikipedia:M4_%28computer_language%29|Wikipedia article]]
* [http://mbreen.com/m4.html Notes on the M4 Macro Language]

ID3

2022-06-08T14:42:39Z

Azertus: add link

{{FormatInfo
|formattype=electronic
|subcat=Metadata
|extensions={{ext|mp3}}, others
|locfdd={{LoCFDD|fdd000106}}, {{LoCFDD|fdd000107}}, {{LoCFDD|fdd000108}}
|released=1996
}}
'''ID3''', or '''ID3 tag''', is a metadata format, mainly used in [[MP3]] audio files. It stores information such as the song title, artist, and album.

Although designed for use with (and named after) MP3, ID3 is sometimes used with other audio formats. This can be done in two fundamental ways:
* Embedding the ID3 data inside the file, in a manner appropriate for that audio format. For example, [https://samples.libav.org/asf-wmv/wma_with_cover_art/wma_with_ID3_APIC.wma here] is a [[WMA]] file containing ID3 data.
* Prepending and/or appending the ID3 data to the file, MP3-style. This practice is not necessarily approved by any standard, but it has been done, for example with [[Ogg]] and [[FLAC]]. Here, the tail is wagging the dog, and ID3 can be thought of as a container format for an arbitrary audio format.

== Format details ==
There are two major versions. ID3v1 defines a fixed-length data block that is always placed at the end of the file. ID3v2, which has very little in common with ID3v1, defines a block with variable-length frames and allows more flexibility and verbosity. ID3v2 data usually appears at the beginning of the file. It is possible, and common, for a file to have both ID3v1 and ID3v2 metadata.

As of 2017, there are three versions of ID3v2 to be aware of: v2.2.x, v2.3.x, and v2.4.x. These formats have some critical differences, and are definitely ''not'' compatible with each other.

== Identification ==
For an MP3 file with an ID3v1 tag, ASCII "{{magic|TAG}}" appears beginning 128 bytes from the end of the file.

An MP3 file with an ID3v2 tag usually begins with ASCII "{{magic|ID3}}".

Alternatively, the signature "{{magic|3DI}}" could appear 10 bytes from the ''end'' of the file, or 138 bytes from the end of the file if there is also an ID3v1 tag. This is much less likely.

There are other (rare) ways to use ID3v2, not covered by the above identification logic.

=== How to skip past an ID3v2 segment ===
To identify an audio file's format, it is best to skip past any ID3v2 segment at the beginning of the file before looking for a magic signature, and not just assume that ID3 implies MP3. Unfortunately, doing so is not trivial. Here is an attempt to summarize the algorithm:
* Let OFFSET = 0.
* Read and remember the first 10 bytes of the file.
* If bytes 0-2 are not ASCII "ID3", stop. An ID3v2 segment is not present.
* Let OFFSET = 10 (for the 10-byte header).
* Decode bytes 6-9 as a 32-bit "synchsafe int" (refer to any ID3v2 spec). Let OFFSET = OFFSET + this decoded int.
* If the 0x10 bit of byte 5 is set, let OFFSET = OFFSET + 10 (for the footer).
OFFSET is now the file offset of the payload audio data.

== Specifications ==
* [http://id3.org/Developer%20Information ID3.org Developer Information]
** [http://id3.org/ID3v1 ID3v1]
** [http://id3.org/id3v2-00 ID3v2.2.0]
** ID3v2.3.0: [http://id3.org/d3v2.3.0 Plain text] · [http://id3.org/id3v2.3.0 HTML]
** ID3v2.4.0: [http://id3.org/id3v2.4.0-structure Main Structure] · [http://id3.org/id3v2.4.0-frames Native Frames]
* [http://id3lib.sourceforge.net/id3/id3v2-00.txt ID3 tag version 2] (Another copy of v2.2.0)
* [http://mpgedit.org/mpgedit/mpeg_format/mpeghdr.htm#MPEGTAG MPEG Audio Tag ID3v1]
* [http://wiki.hydrogenaud.io/index.php?title=ID3v1 Hydrogenaudio Knowledgebase: ID3v1]
* [http://wiki.hydrogenaud.io/index.php?title=ID3v1.1 Hydrogenaudio Knowledgebase: ID3v1.1]
* [http://wiki.hydrogenaud.io/index.php?title=ID3v2 Hydrogenaudio Knowledgebase: ID3v2]

== Software ==
* [http://id3lib.sourceforge.net/ id3lib]
* [http://taglib.github.com/ TagLib]
* [https://www.logipole.com/metadata++-en.htm Metadata++]

''[Ed. note: There are many utilities that can read and write ID3 tags, including Windows Explorer to some extent. We suggest searching the web.]''

== Resources ==
* [http://id3.org/ ID3.org]
* [[Wikipedia:ID3|Wikipedia article]]
* [http://www.codinghorror.com/blog/2006/08/a-spec-tacular-failure.html Coding Horror: A Spec-tacular Failure]
* [https://underjord.io/id3-specification-and-speculation.html What ID3v2 could have been]

[[Category:Audio and Music]]

SAS

2018-09-19T16:11:43Z

Azertus: add lead

{{FormatInfo
|formattype=electronic
|subcat=Scientific Data formats
|extensions={{ext|sas}}, {{ext|sas7dat}}, {{ext|sas7bdat}}, others
|pronom={{PRONOM|fmt/1015}}, {{PRONOM|fmt/1016}}, others
}}

SAS (Statistical Analysis System) is a scientific statistical software package. SAS files contain data and descriptions.

Some of the software's files are:

'''.sas7dat''',

'''.sas''' sas program file.

A full table of SAS files can be found on the [http://v8doc.sas.com/sashtml/win/z1iles.htm official documentation].

Info on deciphering one version was available [http://cybertiggyr.com/ff0/ here] (dead link, Sep 2018).

Cubase

2018-09-19T15:52:17Z

Azertus: mv link and mv headings one level down

{{FormatInfo
|formattype=electronic
|subcat=Audio and Music
|extensions={{ext|all}}, {{ext|arr}}, {{ext|cpr}}, {{ext|npr}}
}}

==Overview==
Cubase is a music software product developed by German musical software and equipment company Steinberg for music recording, arranging and editing as part of a Digital Audio Workstation. It is one of the oldest DAWs to still enjoy widespread use. The first version, which ran on the Atari ST computer and recorded via MIDI only, was released in 1989.

In January 2003, Steinberg was acquired by U.S. firm Pinnacle Systems, within which it operated as an independent company before being sold to Yamaha Corporation in December, 2004.

On January 17, 2011, Steinberg announced that the new version, Cubase 6, was ready and officially shipping. The many new features[1] include: multitrack drum editing and quantizing, multitake comping, advanced tempo detection, drum replacement and VST instruments such as Halion Sonic SE and LoopMash 2. This version also supports 64-bit technology under Mac OS X and Windows 7.

==Versions==
* Cubase 1.0 Atari (April 1989, 1990)
* Cubase 2.0 Atari
* Cubase Audio
* Cubase 3.0 Atari
* Cubase for Windows
* Cubase Score for Windows
* Cubase 2.8 for Windows
* Cubase Audio 1.6 Windows
* Cubase Audio 3.0 TDM for Macintosh
* Cubase Audio XT 3.0
* Cubase Score 3.0
* Cubase VST3.0 Macintosh
* Cubase VST3.5 Windows
* Cubase VST3.5.5
* Cubase VST24 3.6
* Cubase VST24 3.7
* Cubase VST24 4.0 Macintosh
* Cubase VST24 4.1 Macintosh
* Cubase VST32 5.0
* Cubase VST32 5.1
* Cubase SX1.0/Cubase SL1.0
* Cubase SX 2.0/Cubase SL2.0
* Cubase SX 3.0
* Cubase SX3.1
* Cubase 4.0
* Cubase 4.1
* Cubase 4.5
* Cubase 5.0
* Cubase 5.1
* Cubase 5.5
* Cubase 6.0
* Cubase 6.5

==File Formats==

From Cubase 1.0 (1989) to Cubase VST 5.1 (2001) the file format used by Cubase was .all (Cubase song) and .arr (Cubase arrangement) files. It was only possible to open files on a Cubase version identical or newer than the version that saved the file. The upgrade to a new version of Cubase was not a big issue.

Starting with Cubase SX 1.0 (2002) the file format was changed to .cpr (Cubase Project File) and .npr (Nuendo Project File). It is possible to open files on a newer and, in some cases, the older version. For example a file saved in SX2 will open in SX3 and work perfectly, if the VST set is the same. There have also been reports, that a project from SX3 will open in SX2[citation needed].
Cubase SX 1.0 was the first Cubase version not to open Cubase VST songs and projects. Cubase SX 1.0 allows you to import VST projects and save them in the new *.cpr format. However the import feature doesn't work very well.

Cubase SX 3.1.1 (2005) was still able to import Cubase VST songs, but with many limitations.

Some of the important data not imported from Cubase VST songs:

* tempo
* some tracks parts
* mute/un-mute track option

Cubase 4 was the first Cubase version not to support the import of Cubase VST songs and projects. To give the ability to import older Cubase VST projects and songs Steinberg decided to make the previous Cubase SX3 and Cubase SL3 versions available as a download.[2][3] But, because of the limited import capability of Cubase SX, Cubase 4 users are forced to use Cubase VST to work on old

Cubase VST files or to manually export single tracks and then create a new project in Cubase 4.[3]

It has also been reported, that there are backward compatibility issues between different Cubase versions using the *.cpr format.[3]

* [[ALL]] - A [[STEINBERG]] [[CUBASE]] VST file for saving songs (pre 2002).
* [[ARR]] - A [[STEINBERG]] [[CUBASE]] VST file for saving arrangements (pre 2002).
* [[CPR]] - A [[STEINBERG]] [[CUBASE]] SX file for saving projects (2002 - ).
* [[NPR]] - A [[STEINBERG]] [[NUENDO]] file for saving arrangements (2002 - ).

== Links and References ==
* [http://en.wikipedia.org/wiki/Steinberg_Cubase Wikipedia]

AutoCAD Slide

2018-09-19T15:48:28Z

Azertus: rm sp

{{FormatInfo
|formattype=electronic
|subcat=Graphics
|extensions={{ext|sld}}
|pronom={{PRONOM|x-fmt/105}}
}}
An '''AutoCAD Slide''' (or '''Autodesk Slide''') is a screen image from Autodesk/[[AutoCAD]] saved by the MSLIDE command and read by the VSLIDE command. It consists of a header followed by records specifying vector graphics.

See also [[AutoCAD Slide Library]].

== Identification ==
A Slide file begins with ASCII "{{magic|AutoCAD Slide}}", followed by {{magic|0x0d 0x0a 0x1a 0x00}}.

== Format info ==
* [http://www.autodesk.com/techpubs/autocad/acadr14/dxf/slide_file_format_al_u05_b.htm Slide file format]

== Software ==
* [[Netpbm]]: ppmtoacad, sldtoppm

== Other links ==
* [http://docs.autodesk.com/ACD/2010/ENU/AutoCAD%202010%20User%20Documentation/index.html?url=WS73099cc142f4875513fb5cd10c4aa30d6b-7fff.htm,topicNumber=d0e396445 Overview of slides]

[[Category:Autodesk]]

Arts & Letters clip art library

2018-09-19T13:48:51Z

Azertus: replace HTML entities

{{FormatInfo
|formattype=electronic
|subcat=Graphics
|extensions={{ext|yal}}
}}
'''Arts & Letters clip art library''' is a multi-image vector graphics format associated with the ''Arts & Letters'' drawing application.

Although ''Arts & Letters'' has existed since at least the early 1990s, it is hard to find any information about this file format.

== Sample files ==
* [http://cd.textfiles.com/warbirds/ Warbirds CD] → [http://cd.textfiles.com/warbirds/draw/instcust/ draw/instcust/], etc.

== Links ==
* [http://www.arts-letters.com/ Arts & Letters website]

ATASCII

2018-09-19T13:48:02Z

Azertus: ce

{{FormatInfo
|formattype=electronic
|subcat=Character encoding
}}
__NOTOC__
'''ATASCII''' is an eight-bit encoding that was used on Atari computers. It uses most, but not all, of the [[ASCII]] printing characters; codes 7B through 7F are different. The characters with the high bit set (80 through FF) are, with some exceptions, inverse video versions of the same code ANDed with 7F. There have been a number of programs to portray ATASCII on modern operating systems, as well as fonts designed from the originals.

== Documentation ==

* [http://www.faqs.org/faqs/atari-8-bit/faq/section-62.html#b Atari 8-bit FAQ] - What is the ATASCII Character Set?
* [http://en.wikipedia.org/wiki/ATASCII Wikipedia entry on ATASCII]
* [http://spriteshack.com/?p=353 SpriteShack: Using ATASCII in Games]
* [http://www.atarimagazines.com/compute/issue70/113_1_INSIGHT_Atari.php Atari Character Codes] from Computer Magazine Issue #70
* [http://archive.org/details/analog-computing-magazine-31 Issue of Analog Computing Magazine (#31)] covering ATASCII Animations
* [http://www.atariarchives.org/basicxl/showpage.php?page=363 Process of typing in ATASCII on an Atari computer]
* [http://archive.org/details/bitsavers_atari40080mputerTechnicalReferenceNotes1982_20170986 Atari technical manual] - Lots of tech details about Atari 400/800 (including character code info)

== Code Tables ==

* [http://www.atariarchives.org/mapping/appendix10.php Code table]
* {{AtariForumWiki|The_Atari_character_set|The Atari Character Set page at Atari-Forum.com}}
* [http://joyfulcoder.net/atascii/ Joyful Coder ATASCII Map]
* [http://atariwiki.strotmann.de/wiki/Wiki.jsp?page=Atari%20ATASCII%20Table ATASCII map in PDF]

== Programs ==

* [http://sourceforge.net/projects/atascii/ Atari ATASCII Viewer (Java)] on Sourceforge. Last updated in 2001.
* [http://www.leehanken.pwp.blueyonder.co.uk/atascii/ ATASCII View] Windows program for viewing ATASCII characters
* [http://www.vitoco.cl/atari/atasciiprinter.html Web-based ATASCII Printer]
* [http://xent.com/~bsittler/atascii.ti Terminfo for ATASCII]
* [http://syncterm.bbsdev.net/ Syncterm Software] - Terminal program for Windows that supports ATASCII
* [http://joyfulcoder.com/memopad/ Memo Pad], a windows memo pad for ATASCII characters
* [http://bf.amfband.com/bffiles.html File directory containing two ATASCII Telnet Clients for Windows]
* http://ape.dyndns.org:8083/ABBUC/379/IBM2A.C IBM2A.C - Program to make "best guess" conversion from ATASCII to IBM PC Characters (1993)

== Video ==

* [https://vimeo.com/343238 Display of ATASCII on a 40h light panel] (Video)
* [http://www.youtube.com/watch?v=16CSYOBqdqQ ATARI BBS SIM (850 Express)] Video of a simulation of dialing an Atari BBS
* [http://www.youtube.com/watch?v=NKv6_f5ucMw ATARI TOONS "Aliens"]
* [http://www.youtube.com/watch?v=VHUl7WnJqwE ATARI TOONS "Trek"]
* [http://t3xtm0.de/?p=10194 Video of an ATASCII award-winning animation from 1986]

== Fonts ==

* [http://members.bitstream.net/marksim/atarimac/fonts.html Atari Classic truetype fonts]
* [http://user.xmission.com/~trevin/atari/atari.html TrueType Font of ATASCII Characters]

[[Category:Atari computers]]

SmartCode

2017-01-20T13:08:20Z

Azertus: ce

{{FormatInfo
|formattype=physical
|subcat=Bar codes
}}

'''SmartCode''' appears not to be an actual distinct bar code symbology, but rather a particular type of data and/or proprietary manner of creating/reading it, that has been promoted for use in consumer offerings. It uses [[QR code]]s or [[Code 39]].

== Links ==
* [http://www.drbsystems.com/public/products/smartcodes/index.cfm Official page]

Magnetic tape

2016-12-06T19:27:59Z

Azertus: add NT cassette format; see [[wikipedia:NT (cassette)]|]

{{FormatInfo
|formattype=physical
|thiscat=Magnetic tape
}}
'''Magnetic tape''' was for a long time a popular medium for audio recording and data storage. A number of different formats existed.

* [[Audio Cassette]] (includes uses as computer data storage medium)
* [[Digital Audio Tape]]
* [[Digital Compact Cassette]]
* [[Elcaset]]
* [[Endless-loop tape cartridge]]
** [[4-Track]]
** [[8-Track]]
** [[Echo-matic]] (Cousino tape cartridge)
** [[Orrtronics 8-Track]]
* [[Jingle Card Cassette]]
** [[SONIFEX]]
* [[Linear Tape File System]]
* [[Magnetic tape data storage]]
* [[NT]] cassette (Scoopman)
* [[Open Reel Audiotape]]
* [[Pocket Rockers]]
* [[Videotape]]
** [[Open Reel Videotape]]
** [[Video Cassette]]

== Links ==
* [http://archive.org/details/bitsavers_memorextapediaUndertheMicroscopeOct68_10523866 Magnetic Recording Media Under the Microscope (October 1968)]
* [http://hackaday.com/2014/02/08/building-a-tape-recorder-in-1949/ Building A Tape Recorder In 1949]
* [http://crawford.com/format-obsolescence-an-urgent-crisis/ Format Obsolescence: An Urgent Crisis]