www.naimaudio.com
- 2 -
24
th
April 2008
2.3 Multi Discs
Albums may be part of a multiple disc set
2.4 Data Tracks
Albums may contain material additional to playable
music – data tracks etc.
2.5 Metadata isn’t always correct
Integrity of data is paramount. Mistakes in data entry
mean that user-submitted databases are not generally
reliable.
3. Requirements
The requirements for a reliable database from which to
identify ripped CDs are summarised below:
3.1
Correctly identifying and allowing free searching
within ARTIST, ALBUM, GENRE, SONG CDs.
3.2
This is adequately covered by the available
commercial databases with one important shortcoming.
Unless the data is edited or subject to some verification
process the shortcoming the incorrect metadata could be
displayed, resulting in end-user frustration.
3.3
Correctly identifying and allowing free searching
within Compilation CDs, including virtually all Classical
and many Jazz CDs.
3.4
There are several types of compilation disc to be
found in a typical CD collection, including:
Classical Same
composer,
various works, various
artists
Classical Same orchestra or artists, various
composers, various types of music
Classical
Same type of music, various composers,
various artists.
Sampler
Various unrelated tracks, various unrelated
artists.
Sampler
Same artists, re-allocation of tracks from
other releases
Sampler
Same record label but various artists and
tracks
3.5
Correctly identifying and allowing free searching
within multiple disc sets. Providing that there is sufficient
cross checking and binding of discs in a multi-disc set
then the situation is as above. Multiple discs can be
combined into a single playing experience using the
server Create Playlist function.
4. The Naim Solution
The solution devised by Naim is creating a database
internal to the server populated by data from AMG
among other databases, with sophisticated internal
processing of the downloaded database entries.
AMG provide data at both Album and Track level.
Importantly the database is manually edited: from both
submissions from Record Companies and from User
Submissions, manual database editing creates a master
database, which initially promises to meet the specific
requirements of Naim as below.
Additionally the database is configured by Naim to be
self-optimising and various user tools as detailed in
section 4 ensure a comfortable user experience. The full
amount of AMG metadata is actually downloaded:
nothing is discarded. This gives scope for additional
functionality in response to market sentiment.
The basic engine for the Naim Hard Disc Player and
Music Servers is provided by Digital Fidelity and is
based around a powerful XML database application.
Further specialised functions ensure that the sound
quality achieved is well in advance of industry standards.
5. The Naim Extended Music Database
Correctly creating a database that will be effective for
Compilation CDs requires that the search fields operate
at both ALBUM level and at TRACK level.
The search fields proposed in the Naim Music Server
and Hard Disc Player are: -
ALBUM LEVEL
Album Title
Album Artist 1
Album Artist 2
Album Genre
TRACK LEVEL
Track Title
Work
Track Artist 1
Track Artist 2
Track Artist 3
Track Artist 4
The concept of Artist includes:
Artist or Group or Soloist or Conductor
Composer
Orchestra or Group
Naim introduces the concept of PEOPLE for all Artists,
Composers etc, to avoid users having to manage failed
searches due to incorrect recollection of the precise
Artist attribute.
There is therefore within The Naim servers and Naim
Hard Disc Players the concept of PEOPLE SEARCH.
ALBUM LEVEL
DISPLAY
SEARCH
TITLE Y
Y
ARTIST NAME
Y
Y
PERFORMER /
ORCHESTRA
Y Y
PEOPLE
SEARCH
GENRE Y Y
COVER ART
Y
TRACK LEVEL
TRACK COUNT
DISPLAY
SEARCH
TRACK TITLE
Y
Y
WORK / PIECE /
MOVEMENT
Y Y
COMPOSER Y
Y
PERFORMER /
SOLOIST
Y Y
CONDUCTOR Y
Y
PEOPLE
SEARCH
