Universal Music Exchange Medium (UMEM) Code

Exerpt from the specification:

A text document is then created in which data pertaining to and describing a particular set of domains, features, and characteristics is recorded in a form that shows this data structure by way of tags similar to those used in a typical markup language 505. This document is then encoded using 2D encoding or other high-density optically scannable coding technology 506. A visual, physical manifestation of this code is then printed and attached to or printed directly on a physical object, such as a piece of sheet music, a diskette, a compressor/limiter, a pair of headphones, an instrument, a microphone, an ID card, etc., 507. The code is then at some later time scanned and decoded 508. Decoding can be accomplished by the same device or by some other device than that which includes the scanner. The decoded information is then imported directly into a database configured to access the data contained in each node of the document per the UMEM data structure as manifested in the document, edited with text editor software, printed for human reading, or otherwise accessed, manipulated, distributed, or utilized 509.

FIG. 51 depicts a chart of example domains into which a musical performance can be separated. FIG. 52 depicts an example breakdown of features into which a particular domain, namely, that of a composition, can be separated.

FIG. 53 depicts example characteristics that can be treated as data objects pertaining to a particular feature of a particular domain, namely, the legal parameters pertaining to a composition, so as to create a structured form document that serves to enable the remainder of the UMEM invention. Every feature should contain at least one data object or be omitted. Identifying these characteristics and underlying data structures and assembling them for use in a single common exchange medium establishes a lingua franca for substantially all the music industry.

FIG. 54 depicts a piece of sheet music 540 upon which has been printed a 2D code 541 in which is encoded a UMEM document, an example excerpt from which document appears in FIG. 55. Note that the example excerpt 551 includes a container field tag (“<Melody>”) that denotes that the following information is not in human readable form but is a MIDI sequence. Thus, certain software applications ignore all data within the “<melody>” node, while other applications, such as a MIDI sequencer configured to import UMEM documents, import the data in the melody node as a standard MIDI file so that it can be played back for a person wishing to learn the depicted composition.

Other information that can be included in the UMEM document to be attached to sheet music includes: recommended scene profile records that can be directly imported into a scenes database in a configuration device, recommended type of sensor for use with the song, audio file samples of famous recordings of the song, guitar tablature, alternate arrangements, etc. In this way, printed sheet music becomes a medium for quick configuration of the controller devices depicted herein as well as rapid dissemination of new controller scenes, MIDI sequences, training materials, etc.

FIG. 56 depicts the back of a guitar 560 upon which has been applied a UMEM code 561. FIG. 57 depicts an example excerpt from the UMEM document encoded in this UMEM code 561, whereby product specifications directly from the manufacturer are made instantly available upon scanning and decoding. No reference to an external database or manual is needed.

FIG. 58 depicts a UMEM personal ID card 580 that includes both basic human-readable text information, such as the musician’s name, as well as a UMEM code 581 through which additional information pertaining to the individual, from professional associations to musical aptitudes, can be gained upon scanning and decoding. FIG. 59 depicts an example excerpt from the UMEM document encoded in this UMEM code 581.

FIG. 60 presents a schematic diagram of the relationship between a configuration device 600 that is a mixing board, similar to the configuration device 121 in FIG. 12A, and a variety of the other devices that form a part of the present system. Data exchange links described earlier between the mixing board 600 and such devices as controllers, signal processors, instruments, P.A. equipment, etc., are present. Additionally, however, the depicted configuration device 600 is also linked to acquire information by way of an external code scanner 601 configured to read 2D UMEM codes. Through this UMEM scanner 601, all manner of specification information regarding the various devices to be used in a musical performance can be input into the configuration device 600 and displayed and manipulated through the touch screen displays 602 associated with each channel in the mixing board 600. Thus, a sound engineer can have the actual specs of the given guitar or microphone being fed into a given channel of the mixing board directly in front of him while mixing. As discussed in more detail below, a large variety of data processing opportunities are made possible by making all this information available in a single structured form to a single configuration device, thereby making the job of a sound engineer much easier to perform. Moreover, by scanning the UMEM codes contained in or on other depicted objects, the sound engineer can also view acquired data pertaining to a wide variety of other factors in the musical performance, including factors which are typically not under the control of the mixing board, such as information pertaining to the musicians performing, the compositions being performed, the venue in which the performance is taking place, and the light show equipment. Access to such information also significantly facilitates effective management of the performance by a sound engineer or other behind-the-scenes personnel. For instance, an engineer can follow along in a song by displaying the lyrics in the master display 603 once the lyrics have been downloaded into the configuration device 600 by way of the UMEM scanner from the sheet music so that he does not miss any cues.

FIG. 61 depicts a schematic diagram of a single, simple, illustrative process by which the unique capabilities of the guitar docking station and the UMEM can be advantageously deployed. A piece of sheet music 610 bearing a UMEM code is scanned using a scanner 611 equipped to decode UMEM codes as well to produce a graphical image file such as a JPEG or GIF file. These files, both the image file and the decoded UMEM document, are transferred to a configuration device 612 such as a handheld or tablet PC. The UMEM document may be imported directly into a database in the configuration device, with data being mapped to fields identified by UMEM tags. Files in the configuration device can be edited, transferred, etc., as needed.

The user transfers the files to the guitar docking station 613, where sheet music image files or the UMEM-derived database record pertaining to the given composition can be viewed via flat-panel display 614. Data from the UMEM document now in the docking station can be used to trigger a metronome at a specified beats-per-minute rate, to play the MIDI sequence from the “<melody>” node in the UMEM-document, etc.

During performance, an instrument-mounted controller 615 equipped with page-turner buttons, including a “last page” button 621 and a “next page” button 622 in FIG. 62, is used to transmit control information to the guitar docking station so that the musician can navigate through the pages of scanned sheet music.

The UMEM makes possible entire new businesses, recording and engineering techniques, forms of publication, and applications of technology. An additional example is illustrative.

For instance, referring to FIG. 63, EQ settings applied to a given singer’s voice by a particular engineer during a particular performance are documented in a UMEM document, a code manifestation of this document applied to an identification card for said singer (e.g., FIG. 58), and then this code is instantly recalled later by an engineer using a configuration device with a graphic equalizer configured to import EQ settings under the UMEM 631.

Then, the characteristics of a particular microphone, as published by the manufacturer and manifested in a code applied directly to the microphone itself, are imported into the same device by way of UMEM 632.

Known equalization problems and suggestions associated with a particular venue (concert hall, nightclub, etc.), e.g., a particular sound frequency that tends to feedback in the given venue, are then documented in a UMEM document kept on file at the venue (similar to ID card for individuals) and then imported into the same configuration device via UMEM scanning and decoding of the document 633.

back to Automatic Identification | Data Capture