JP2001249669A - Semiconductor memory card, reproducing device, recording device, reproducing method, recording method, and computer-readable recording medium. - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a semiconductor memory card permitting to reduce a time for creating an image to be allocated to each of music contents in the case of creating a music album comprising plural music contents. SOLUTION: Plural AOB files and plural POB files are stored in the semiconductor memory card, and Default-Playlist information and Playlist information indicate in what order AOB to be stored in the plural AOB files are reproduced. DPLGI includes TKI-POB-SRP for specifying at least one POB to be displayed during a time zone for reproducing AOB according to the order specified by the Default-Playlist information, and TKGI includes DPLI-POB-SRP for specifying at least one POB file to be displayed during a reproduction period for reproducing a specific AOB during the above time zone.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a semiconductor memory card for storing audio data, still picture data, and control data, a reproducing apparatus, a recording apparatus, a reproducing method, a recording method, and a computer-readable recording medium. In content distribution services such as music distribution, audio data, image data,
The present invention relates to an improvement in storing control data.

[0002]

2. Description of the Related Art Electronic music distribution, which enables purchase of music content on the Internet, can be a catalyst for activating the music market. is there. The semiconductor memory card described above is a portable recording medium suitable for storing and carrying music content purchased from electronic music distribution, and its demand is expected to increase dramatically in the future.

[0003] Music contents include not only music reproduction but also "media mix" type music contents that can display images related to the music together with the music reproduction. The image showing the lyrics and the background image are recorded together with the karaoke music on the recording medium,
“Karaoke software”, which displays lyrics when playing karaoke music, is a typical music content of the “media mix” type. To consider the further development of electronic music distribution in the future, media mix type music We must also consider the realization of content distribution and sales. Along with this, a more specific study is also required on a storage method for storing “media mix” type music content in a semiconductor memory card.

[0004] The following describes how a "media mix" type music content is stored in a recording medium such as a CD, that is, a conventional audio data-image data storage method in a recording medium.
In order to perform music reproduction and image display, the conventional "media mix" type music content uses multiplexed data obtained by multiplexing audio data of music and image data indicating lyrics and a background image on a recording medium. Thus, the reproduction of the audio data and the display of the image data are both performed. CD-Gra is used for recording media that realized image display while reproducing audio data by multiplexing.
There is something called phics (subcode Graphics). One unit of multiplexing in this CD-Graphics consists of a 16-bit main code and a sub-code. Audio data is allocated to the 16-bit main code, and image data such as lyrics and background images are allocated to the sub-code. ing.
When the reproduction of any of the music contents recorded on the CD-Graphics is started, the audio data assigned to the 16-bit main code is sequentially reproduced, and the image data assigned to the sub-code is sequentially displayed. .

[0005]

However, if a music album composed of a plurality of music contents is to be produced in accordance with the above-described audio data-image data multiplexing method, an image is provided uniformly for each music content. That is, the conventional multiplexing method of audio data and image data requires that at least one image is assigned to each music content, so that the creator is troublesome in producing such an image. .

However, with regard to music albums of artists with high reputation, consumers who are provided with different images for each music content will be welcomed by consumers, and sales of music albums are expected to be enormous. It is likely that such effort and expense will be rewarded. Conversely, with regard to music albums of less popular artists, even if different images are provided for each music content, consumers' reactions will be slow and it is not expected that the sales of music albums will be large, It is likely that costs will not be rewarded.

Whether the effort and expense required for image production are rewarded or not is clear that the drop between a high-profile music album and a low-profile music album is sharp, but the conventional audio data-image data The multiplexing method has been unsatisfactory for the producer in this point because it is required to assign at least one image to each music content regardless of the artist's name recognition and the expected number of sales.

An object of the present invention is to provide a semiconductor memory card capable of reducing the time and effort required to produce an image to be assigned to each music content when producing a music album including a plurality of music contents.

[0009]

Considering the music content and the image to be displayed, it is indispensable to provide different lyrics for the music content for each music content. In some cases, a background image to be displayed when a plurality of music contents are reproduced may be shared. For example, if multiple music contents are written, composed, and sung by the same person,
By displaying a common photograph of the person as a background image when playing the plurality of music contents,
A method of storing audio data (audio objects) and image data (still image objects), which saves a maker's work, is conceivable.

In order to achieve the above object by sharing image data (still picture objects) between a plurality of music contents, a semiconductor memory card according to the present invention comprises an audio sequence including a plurality of audio objects and a plurality of still pictures. A picture object, one or more pieces of reproduction path information indicating the order in which the plurality of audio objects included in the audio sequence are reproduced, and a plurality of audios using the reproduction order indicated by the one or more pieces of reproduction path information. When the objects are reproduced, first pointer information, which is information for specifying one or more still image objects to be displayed together with the reproduction path information, and a specific one of the plurality of audio objects. One or more audio objects that should only be displayed during the It is characterized in that it stores second pointer information as information for designating the upper still image object in association with the specific audio object.

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of a semiconductor memory card (flash memory card) will be described with reference to the drawings. In addition, each of the following sentences is given a classification number having the following system at the beginning of the sentence.

The number of digits of the {x1-x2_x3-x4} classification number means the hierarchical depth of the item. Specifically, x1
Is the figure number cited in the description. Since the figures attached to this specification are numbered in the order cited in the specification, the order of the figure numbers is almost the same as the order of the description. x2 indicates the order of description when the description is made with reference to the diagram shown in x1. x3 indicates the figure number of the explanatory diagram when citing the explanatory diagram in order to explain the components of x2 in more detail, and x4 indicates the order of the description when referring to the diagram illustrated by x3. Is shown.

(First Embodiment) {1-1_2} External Shape of Flash Memory Card 31 First, the external shape of the flash memory card 31 will be described. FIG. 1 is a diagram showing a shape when the flash memory card 31 is viewed from above, and FIG. 2 is a diagram showing a structure when the flash memory card 31 is viewed from below. As shown in FIGS. 1 and 2, the size of the flash memory card 31 is about 32.0 mm in length and about 24.0 mm in width.
mm and a thickness of about 2.0 mm, and is large enough to be gripped with a fingertip (size of stamp size). Nine connectors for connection to devices are provided on the lower surface, and a protect switch 32 that allows the operator to set whether to allow or prohibit overwriting of stored contents is provided on the side surface. Have been.

{3-1} Physical Structure of Flash Memory Card 31 FIG. 3 shows a semiconductor memory card (hereinafter referred to as
FIG. 2 is a diagram showing a hierarchical structure of a flash memory card 31). As shown in the figure, the hierarchical structure of the flash memory card 31 is the same as the hierarchical structure of a DVD (Digital Video Disc) in that it has a physical layer, a file system layer, and an application layer. The physical structure is very different.

{3-2} Physical Structure of Flash Memory Card 31 First, the physical layer of the flash memory card 31 will be described. The flash memory is composed of a plurality of sectors, each of which stores 512 bytes of digital data. For example, in the case of a 64MByte type flash memory card 31, its memory capacity is 67108864 (= 64 × 1024 × 1024)
Bytes, and the number of valid sectors at this time is 131072 (= 6710
8864/512). Further, by subtracting the number of alternative sectors for error from this effective sector, the number of remaining effective sectors is
128,000, and various data will be recorded here.

{3-2_4A-1} Three areas in the physical layer The areas composed of these effective sectors are shown in FIG.
Three areas are provided. FIG. 4A is a diagram showing a “system area”, a “protect area”, and a “user data area” provided in the physical layer of the flash memory card 31. Hereinafter, these three areas will be described.

The "user data area" is an area in which a device connected to the flash memory card 31 can freely write various data and can freely read data. The internal area is defined by a file system. Is managed. The “system area” is an area in which a media ID having a unique value for each of the flash memory cards 31 is stored. While the user data area is writable, the system area is read-only and the media ID stored here cannot be rewritten.

The "protect area" is an area in which data can be written, like the user data area. The difference from the user data area is that, in the user data area, data can be freely read and written, while in the protected area, a device connected to the flash memory card 31 and
Reading and writing can be performed only when the validity of the flash memory card 31 with each other is confirmed. That is, only when mutual authentication between the device connected to the flash memory card 31 and the flash memory card 31 is successful, reading and writing is performed. It is possible.

{3-2_4A-2} Usage of Three Areas in Physical Layer When a device connected to the flash memory card 31 writes data to the flash memory card 31, it depends on the necessity of copyright protection of the data. , These three areas are utilized. Here, when writing data that requires copyright protection to the flash memory card 31, the data is stored in the user data area after being encrypted using a predetermined encryption key (called FileKey). This File
The Key can be freely set by the copyright holder. Even with this key alone, the copyright of the data is protected, but in order to further ensure the security, the FileKey itself used for this encryption is also encrypted. When encrypting FileKey itself, any value obtained by applying the media ID stored in the system area to a predetermined arithmetic expression is used as the key, and the protected area is the arbitrary value. Stores the FileKey encrypted using. Data that requires copyright protection is encrypted using a predetermined FileKey, and the FileKey itself is also encrypted using a value based on the media ID. Infringement becomes extremely difficult.

{3-2_4B-1} Outline of File System The configuration of the physical layer of the flash memory card 31 is as described above, and it can be seen that the copyright protection has been improved. Next, the configuration of the file system layer existing on the physical layer will be described. The file system layer of the DVD is a UDF (universal disk format) file system, whereas the file system layer of the flash memory card 31 is a FAT type file system (FAT: F
ile Allocation Table, ISO / IEC 9293), which is different from DVD.

FIG. 4B is a diagram showing the structure of the protect area and the user data area in the file system layer. In FIG. 4B, the protected area and the user data area in the file system include a “partition boot sector”, a “file allocation table (FAT)”, a “root directory entry”,
It is clear from this figure that the "data area" is included, and the protect area and the user data area have the same configuration. FIG. 5 is a diagram showing details of these file system configurations. Hereinafter, the configuration of the user data area will be described with reference to FIGS.

{3-2_4B-2} Partition Boot Sector A “partition boot sector” is a flash memory card 31 loaded in a general-purpose personal computer.
When the flash memory card 31 is allocated to the boot disk of the operating system of the general-purpose personal computer, this is a sector in which the general-purpose personal computer refers to when booting.

{3-2_4B-3_5} Data Area The “data area” is an area that is accessed by a device connected to the flash memory card 31 with a cluster as a minimum unit. Since the sector size of the flash memory card 31 is 512 bytes and the cluster size is 16 Kbytes, the file system layer has a size of 3 Kbytes.
Data is read and written using two sectors as one unit. The reason for setting the cluster size to 16 Kbytes is as follows. That is, when writing data to the flash memory card 31,
Must be erased once, and then the data must be written. In the flash memory card 31, the size at which such data can be erased is 16 Kbytes, so by setting the cluster size to this erasable size,
Data writing is preferably performed. FIG.
Indicate a plurality of clusters 002, 003, 004, 005,... Included in the data area. The numbers 002, 003, 004, 005, 006, 007, 008,... In the figure indicate the cluster numbers in hexadecimal notation of three digits assigned to identify each cluster. Since access to the data area is performed using a cluster as a minimum unit, the internal position of the data area is specified using these cluster numbers.

{3-2_4B-4_5} File Allocation Table “File Allocation Table” is based on ISO / IEC 9293
Has a file system structure compliant with
Consists of FAT value. Each FAT value is associated with each cluster, and indicates which cluster should be read next when the corresponding cluster is read. 5 indicate a plurality of FAT values 002, 003, 004, 005,... Included in the file allocation table. The numerical value “002, 003, 004, 005...” Assigned to this FAT value indicates to which cluster each FAT value is associated, that is, each FAT value.
Indicates the cluster number of the cluster to which the value is associated.

{3-2_4B-5_5-1} Root directory entry The “root directory entry” is information indicating what files exist in the root directory. Specifically, the root directory entry contains the "file name" of the existing file, the "extension" of the file, the "file attribute", the "update time and date" of the file, and the file Is described as "the first cluster number of the file."

{3-2_4B-5_5-2} Directory entry of subdirectory Information about files in the root directory is as follows:
Although described in this root directory entry, information about subdirectories is not described in this root directory entry. A directory entry for a subdirectory is created in the data area. The SD_Audio directory entry described in the data area of FIG. 5 is an example of a directory entry for a subdirectory. Like the root directory entry, the SD_Audio directory entry has a “file name” of a file existing in the subdirectory. The "extension" of the file, the "file attribute", the "update time and date" of the file, and the "first cluster number of the file" in which the head of the file is stored are described.

{3-2_4B-5_6-1} AOB File Storage Method Here, when storing a file called AOB001.SA1 in the SD_Audio directory, how AOB001.SA1 is stored, that is, a file storage method Will be described with reference to FIG. As described above, since the minimum access unit of the data area is a cluster, AOB001.SA1 must be stored in the data area with the cluster size as the minimum unit. AOB001.SA1 is first divided into cluster sizes,
Written to each cluster. FIG. 6 is a diagram assuming a state in which AOB001.SA1 is divided into five parts according to the cluster size, and each divided part is stored in clusters 003, 004, 005, 00A, and 00C.

{3-2_4B-5_7-1} Storage method of AOB file When AOB001.SA1 is divided and stored, the directory entry and file allocation table must be set as shown in FIG. FIG. 7 is a diagram showing a setting example of a directory entry and a file allocation table when AOB001.SA1 is recorded in a plurality of clusters. In this figure, when the head of AOB001.SA1 is recorded in the cluster 003, the “first cluster number” in the SD_Audio directory entry describes the cluster number 003 of the cluster in which the head is stored. . Hereafter, it can be seen that the subsequent part of AOB001.SA1 is stored in cluster 004 and cluster 005. FAT value 003 (004) corresponds to cluster 003 storing the beginning of AOB001.SA1,
This FAT value indicates the cluster 004 that stores the subsequent part of the AOB file. Also, the clusters 004 and 005 that store the succeeding part have a FAT value of 00.
4 (005) and FAT value 005 (00A) correspond to this, and indicate the cluster 005,00A that stores the next succeeding part of the AOB file.

If the cluster numbers described in these FAT values are sequentially read as indicated by arrows fk1, fk2, fk3, fk4, fk5,..., All the divided portions of AOB001.SA1 can be read. . From the above description, it can be seen that the data area of the flash memory card 31 is accessed using the cluster as the minimum unit, and that each cluster is associated with a FAT value. A cluster storing the end of the AOB file (cluster 00C in the example of FIG. 7)
Is described with a cluster number "FFF" indicating that the cluster stores the last part of the file.

Now, the description of the file system of the flash memory card 31 of the present invention has been completed.
The configuration of the application layer existing on the file system described above will be described. {3-3} Overview of application layer in flash memory card 31
This is as described in FIG. As shown by a broken line PN1 in FIG. 3, the application layer in the flash memory card 31 is composed of presentation data and navigation data for controlling reproduction of the presentation data.

As shown by a broken line PN2 in the figure, the presentation data includes an audio object group (AOB group) obtained by encoding audio data such as music, and the navigation data includes a playlist manager. (PlaylistManager (PLMG)),
Track Manager (TKMG). {3-3_8A, B-1} Directory structure FIGS. 8A and 8B show what kind of data is stored in the user data area and the protection area in the file system layer when these two data are stored in the application layer. FIG. 4 is a diagram illustrating a directory configuration and what files are created under the directory; “SD_AUDIO.PLM” and “SD_AUDIO.TKM” in this figure are files that contain navigation data such as playlist manager (PlaylistManager (PLMG)) and track manager (Track Manager (TKMG)).
1, AOB002.SA1, AOB003.SA1, AOB004.SA1, ...
Is a file (hereinafter, referred to as an AOB file) storing audio objects that are presentation data.

The extension "SA" in "AOB0xx.SA1"
Abbreviation of “Secure Audio”, and these stored contents indicate that copyright protection is necessary. (Note that FIG. 8A shows only eight AOB files. This is only an example, and the SD_Audio directory can store up to 999 AOB files.) When the presentation data needs copyright protection, a subdirectory named SD_Audio directory is provided in the protected area, and an encryption key storage file AOBSA1.KEY is created under the SD_Audio directory. FIG. 8B is a diagram showing an encryption key storage file AOBSA1.KEY stored under SD_Audio. In the encryption key storage file AOBSA1.KEY, FileKey # 1 to # 8 which are encryption key strings in which a plurality of encryption keys FileKey are arranged in a predetermined order.
Is stored.

In electronic music distribution, the server computer of the music company uses SD_Audio shown in FIGS. 8A and 8B.
When the consumer issues a purchase request for the music content, the SD_Audio directory is compressed and encrypted, and then the SD_Audio directory owned by the consumer who issued the purchase request is transferred via the public network. To send. When the consumer's computer receives the SD_Audio directory, it decrypts the directory and decompresses the directory to obtain an SD_Audio directory. (Including all networks open to the public, such as wireless communication networks represented by mobile phones.) The AOB file may be downloaded from a server computer of a music company, and the computer owned by the consumer may create the SD_Audio directory shown in FIGS. 8A and 8B in the flash memory card 31.

{3-3_9-1} Correspondence between AOBSA1.KEY and AOB file FIG. 9 is a diagram showing the correspondence between AOBSA1.KEY under SD_Audio and AOB files. In this figure, the Fi used to encrypt the encrypted file in the user data area
leKey is stored in the encryption key storage file corresponding to the protected area.

The encrypted AOB file and the encryption key storage file have a correspondence relationship based on the following certain rules (1), (2), and (3). (1) The encryption key storage file is located in the same directory name as the directory in which the encrypted file is stored. In the user data area of FIG. 9, the AOB file is arranged in the SD_Audio directory, and the encryption key storage file is also arranged in the SD_Audio directory, which indicates that the file is arranged according to this rule. .

(2) The encryption key storage file is given a file name obtained by combining the first three characters of the file name of the AOB file in the data area with a predetermined extension ".key". If the file name of the AOB file is “AOB001.SA1”, the encryption key storage file contains the first three characters “AOB”, “SA1”, and the extension “.key” as shown by arrows nk1 and nk2. "AOBSA1.KEY" is added.

(3) In the file name of the AOB file, the serial number indicating the position of the Filekey corresponding to the audio object in the encryption key string in the encryption key storage file, that is, the order of the corresponding FileKey. A number is assigned. “File Key Entry # 1, # 2, # 3... # 8” in the encryption key storage file in FIG. 9 indicates the head position of the area where each FileKey in the encryption key storage file is stored. . On the other hand, the file names of AOB files are "001", "00"
2 "," 003 "," 004 ", etc. The serial numbers in these AOB files indicate the position of the corresponding FileKey in the encryption key sequence, so that each AOB Fil used to encrypt the file
eKey has the same serial number as “File Key Entr.
y ”. Arrows AK1, AK2, AK3 in FIG.
Indicates the correspondence between the AOB file and the FileKey. That is,
AOB001.SA1 in the user data area is “File Key Ent.
ry # 1 '' and AOB00
2.SA1 is the FileKe stored after “FileKey Entry # 2”
y, AOB003.SA1 indicates that it corresponds to FileKey stored after “File Key Entry # 3”. As can be seen from (3) above, the FileKey used to encrypt the AOB file
Are different for each file, and are different from the “File Key” having the same serial number as “001”, “002”, “003”, “004” embedded in the file name. Entry ”. Each AOB file is encrypted using a different FileKey, so even if the encryption key for a particular AOB file is exposed,
Other AOB files cannot be decrypted using the exposed FileKey. As a result, it is possible to minimize the damage caused by exposing the FileKey when encrypting the AOB file.

{3-3_10-1} Internal Configuration of AOB File Next, the internal configuration of the AOB file will be described. FIG.
0 is a diagram hierarchically showing the data structure of the AOB file. The first row in the figure shows an AOB file, and the second row shows an AOB. The third row shows AOB_BLOCK, the fourth row shows AOB_ELEMENT, and the fifth row shows AOB_FRAME.

"AOB_FRAME" in the fifth row of FIG.
Is the smallest unit that composes the AOB, and includes the ADTS header and ADT
It consists of audio data in S (Audio Data Transport Stream) format. ADTS format audio data is MPEG
16K encoded in 2-AAC [Low Complexity Profile]
It is stream data reproduced at a transmission speed of bps to 144 Kbps. (Note that PCs recorded on existing compact discs
Since the transmission speed of the M data is 1.5 Mbps, it can be seen that the transmission speed is much lower than that of the PCM data. ). These AOB_
The data structure of the FRAME sequence is the same as the audio frame sequence included in the audio data transport distributed by electronic music distribution. That is, the audio data transport stream to be stored as the AOB_FRAME sequence is encoded by MPEG2-ACC and further transmitted in an encrypted state over the public network and transmitted to the consumer. The AOB file stores the audio data transport stream transmitted in such a manner as an AOB_FRAME column.

{3-3_10-1_11} About MPEG2-AAC For details of MPEG2-AAC, see ISO / IEC 13818-7: 1997 (E).
Information technology-Generic coding of moving
pictures and associated audio information- Part7
Please refer to Advanced Audio Coding (AAC). It should be noted here that the AOB is compressed by the MPEG2-AAC method in which the parameter table described in ISO / IEC13818-7 is restricted as shown in FIG. 11A. . FIG.
FIG. 1A is a diagram showing a parameter table described in ISO / IEC13818-7, in which a Parameter column, a Value column, a Comm
It consists of a comment column indicating the contents of the ent column.

The parameter field “profile” is defined in ISO / IEC 138
Indicates that the LC-profile restrictions specified in 38-7 are applied. Parameter field "sampling_frequency # ind
ex '' is `` 48kHz, 44.1kHz, 32kHz, 24kHz, 22.05kHz, 16kHz
z "indicates that a sampling frequency is applied. Parameter column “number_of_data_block_in_fram”
“e” indicates that it is set to 1header / 1raw_data_block.

Although AOB_FRAME has been described as being encoded by the MPEG-AAC method, AOB_FRAME is
G-Layer3 (MP3) method, Windows (registered trademark) M
media may be encoded by other encoding schemes such as WMA scheme. In this case, instead of the parameters shown in FIG. 11A, the parameters shown in FIG. You must use a table.

{3-3_10-2_12} Configuration of AOB_FRAME “AOB_FRAME” includes audio data coded under the above restrictions, and the data length of the audio data included in AOB_FRAME has a reproduction time of 20 millimeters. It is just data that can be seconds. However, since the MPEG2-AAC method is a variable length encoding method, the data length of audio data included in each AOB_FRAME differs for each AOB_FRAME. Hereinafter, the configuration of the AOB_FRAME will be described in detail with reference to FIG. The first row in the figure is AOB_FRAME
The second row shows how each part of AOB_FRAME is encrypted. Referring to the second row, it can be seen that the ADTS header is a non-encrypted part, that is, not encrypted. The audio data includes both an encrypted part and an unencrypted part. The encrypted part is a plurality of 8-byte encrypted data. The 8-byte encrypted data is 6
It is generated by encrypting 4-bit original data using a 56-bit FileKey. The non-encrypted portion is left unencrypted because the data is less than 64 bits when the encryption is performed in 64-bit units.

The third row shows the contents of the ADTS header which is an unencrypted part. The ADTS header is 7 bytes, with a 12-bit sync word (set as FFF),
The data length of audio data included in the same AOB_FRAME and a sampling frequency for encoding the audio data are described. {3-3_10-3_13} AOB_FRAME byte length setting FIG. 13 shows the AOB_FR of each of the three AOB_FRAMEs.
FIG. 3 is a diagram illustrating how the byte length of audio data in AME is set. In the figure, AOB_FRAM
The data length of audio data # 1 included in E # 1 is x1, AOB
The data length of audio data # 2 included in _FRAME # 2 is x
2.The data length of audio data # 3 included in AOB_FRAME # 3 is x3. x1 is described, the data length x2 is described in the ADTS header included in AOB_FRAME # 2, and the data length x3 is described in the ADTS header included in AOB_FRAME # 3. The audio data itself is encrypted, but the ADTS header itself is not encrypted, so if you read the data length of the audio data from the ADTS header in each AOB_FRAME, You can learn. This concludes the description of AOB_FRAME.

{3-3_10-4} AOB_ELEMENT Next, the AOB_ELEMENT located at the fourth row in FIG.
Will be described. “AOB_ELEMENT” is a set of a plurality of continuous AOB_FRAMEs. Here, how many AOBs
Whether _FRAME is included in AOB_ELEMENT changes according to the setting of sampling_frequency_index shown in FIG. 11A and the encoding method. That is, AOB included in AOB_ELEMENT
The number of _FRAMEs is the number of AOB_FRAMEs included in the AOB_ELEMENT.
Is determined to be approximately 2 seconds, and the number of reproductions differs depending on the sampling frequency and the encoding method.

[3-3_10-5_14} AO included in AOB_ELEMENT
B_FRAME Number FIG. 14 is a diagram showing the correspondence between sampling_frequency and the number of AOB_FRAMEs included in the AOB_ELEMENT. In this drawing, N indicates the playback period of AOB_ELEMENT in seconds, and is "2" if the encoding system is MPEG-AAC. Also, if sampling_frequency is 48kHz, AOB_ELEMENT
Contains 94 (= 47 × 2) frames.
If ng_frequency is 44.1kHz, the number of frames included in the AOB_ELEMENT is 86 (= 43 × 2) and sampling_frequency is
At 32kHz, the number of frames included in the AOB_ELEMENT is
If 64 (= 32 × 2) and sampling_frequency is 24 kHz, the number of frames is 48 (= 24 × 2) and sampling_frequency is
If 22.05 kHz, the number of frames included in the AOB_ELEMENT is 44 (= 22 × 2), and if the sampling_frequency is 16 kHz, the number of frames included in the AOB_ELEMENT is 32 (= 16 × 2)
Individual. However, if you edit the AOB by splitting it, A
The number of AOB_FRAMEs in the first and last AOB_ELEMENT of the OB is shown in FIG.
May be less than the number.

The AOB_ELEMENT is not given any special information such as a header, but instead has its data length indicated in the time search table. {3-3_10-6_15} Example of time length of AOB_ELEMENT and AOB_FRAME FIG. 15 is a diagram illustrating an example of the time length of AOB_ELEMENT and the time length of AOB_FRAME. The first row of the figure shows a plurality of AOB_BL
The second row shows the arrangement of a plurality of AOB_ELEMENTs. The third row shows the arrangement of a plurality of AOB_FRAMEs.

Referring to this figure, AOB_ELEMENT is about 2.0
AOB_FRAME in this figure
Corresponds to a playback time length of 20 msec. AO
The character string “TMSRT_entry” attached to each B_ELEMENT indicates that the data length of each AOB_ELEMENT is described in the time search table. TM like this
By performing forward search playback and reverse search playback with reference to the SRT_entry, intermittent playback of, for example, skipping 2.0 seconds and playing back for 240 milliseconds can be realized.

{3-3_10-7} About AOB_BLOCK The explanation of AOB_ELEMENT is completed above, and then AOB_E
The AOB_BLOCK located at the upper level of the LEMENT, that is, the third row in the data structure of the AOB file in FIG. 10 will be described. 'AOB_BLOCK' is a valid AOB_ELEMENT
Area, and there is one in the AOB file. A
OB_ELEMENT corresponds to a playback time of 2 seconds, whereas AOB_BLOCK corresponds to a playback time with an upper limit of 8.4 minutes of playback time. The reason that each AOB is limited to the 8.4 minute playback time is to limit the size of the time search table to 504 bytes or less by limiting the number of AOB_ELEMENTs included in the AOB_BLOCK.

{3-3_10-8} Time Search Table Suppression Hereinafter, the reason why the time search table can be suppressed by limiting the reproduction time will be described in detail. When performing forward search playback and reverse search playback, “2 second skip 240 ms playback” is performed, in which reading for 2 seconds is skipped and playback is performed for 240 ms. When skipping the time length of 2 seconds like this, in principle, AOB_FRAM
It is sufficient to sequentially refer to the data length indicated in the ADTS header of E. In this case, 100 AOB_FRAMEs (= 2 seconds / 20 ms) to skip the time interval of 2 seconds
Must be sequentially detected, and an extra processing load is imposed on the reproducing apparatus. In order to reduce such processing load, the read destination address at the interval of 2 seconds is described in the time search table, and when the forward search reproduction and the reverse search reproduction are ordered, the reproducing apparatus refers to them. Just fine. That is,
The time search table contains information for calculating the read destination address two seconds ahead and four seconds ahead, specifically, each AOB_ELEMEN
The data length of T is described in advance, and the reproducing apparatus may perform forward search reproduction / reverse search reproduction with reference to the data length. Consider the data length equivalent to 2 seconds. The bit rate at the time of audio data reproduction is 16 Kbps to 144 Kbps as described above.
, The data length reproduced every 2 seconds is 4
Kbyte (= 16 Kbps × 2/8) to 36 Kbyte (= 144 Kbps × 2/8).

If the data length per 2 seconds is 4 Kbytes to 36 Kbytes, the data length of the entry in the time search table for describing the data length of audio data requires 2 bytes (16 bits). This is because if a 16-bit length is assigned to an entry, a numerical value of 0 to 64 KByte can be described. On the other hand, considering the case where the total data size of the time search table is limited to, for example, 504 bytes (this is the data size of TKTMSRT described later), the entries to be provided in this time search table are 252 (= 504 / 2) must be limited to individual. As described above, since the entry is provided every two seconds, the reproduction time corresponding to 252 entries is 504 seconds (= 2 seconds × 252), and is 8 minutes 24 seconds (= 8.4 minutes). By limiting the playback time in AOB_BLOCK to 8.4 minutes or less, the data size of the time search table can be 504 bytes or less.

{3-3_10-9} AOB The AOB_BLOCK has been described above, and then the AOB will be described. The AOB located in the second row of FIG.
This is an area where an invalid area is added before and after _BLOCK.
There is one in the file. This invalid area is the AO
This area is stored in the same cluster as B_BLOCK and is read / written together with the AOB_BLOCK. In the AOB, what part corresponds to the AOB_BLOCK is specified by a BIT included in the navigation data (the details will be described later).

As described above, it has been clarified what data is stored in each AOB file. Subsequently, FIG.
The following describes what is reproduced by reading the AOB and AOB_BLOCK included in the eight AOB files shown in FIG. {3-3_10-10_16} FIG. 16 shows the AOB
It shows what kind of playback content is played by successively playing back each AOB and AOB_BLOCK recorded in the file. The first row shows the 8 in the user data area.
One AOB file is shown, and the second row shows eight AOBs recorded in each AOB file. The third row shows eight AOB_BLOCKs included in each AOB.

The fifth row shows a title composed of five content parts. The five content divisions are SongA and Song
Each of the five songs B, SongC, SongD, and SongE is shown, and the title indicates a music album composed of these five songs (contents). Dashed lines AS1, AS2, AS3 ... AS7, AS8
Indicates the correspondence between the divided portions of the music album and AOB_BLOCK, and the fourth row indicates in what unit the fifth level music album is divided.

Referring to these broken lines, the AOB_Block included in each AOB # 1 is a tune reproduced in 6.1 minutes.
(SongA), the AOB_Block included in each AOB # 2 is a song played in 3.3 minutes (SongB), and the AOB_Block included in each AOB # 3 is a song played in 5.5 minutes (Son
gC). As described above, AOB001.SA1 to AOB003.SA1 are
It turns out that each corresponds to an independent song. The sixth row shows a track sequence including Tracks A to E. TrackA ~ E are SongA, SongB, SongC,
It corresponds to each of the five songs, SongD and SongE, and is treated as one independent playback unit.

On the other hand, AOB # 4 is the head of a song (SongD) reproduced in a time of 30.6 minutes, and is reproduced in a reproduction time of 8.4 minutes. AOB_BLOC included in AOB # 5 and AOB # 6
K is the middle part of SongD, the playback time is 8.4 minutes, AOB
AOB_BLOCK included in # 7 is the terminal part of SongD, and 5.
It is played with a playback time of 4 minutes. A song having a playback time of 30.6 minutes is (8.4 minutes +8.4 minutes +8.4 minutes +5.4 minutes)
It can be seen that it is divided in units of (minutes) and included in each AOB. As can be understood from this figure, all the songs included in the AOB file are included in the playback time length of 8.4 minutes or less.

As described above, it has been clarified that the data size of the time search table associated with each AOB is also limited by limiting the playback time length of the AOB. Next, navigation data including the time search table will be described. {3-3_8A, B-2} The navigation data is “SD_Audio.PL
M ”and“ SD_Audio.TKM ”as described above. File "SD_Audio.PLM"
Contains the playlist manager (Playlistmanager), and the file "SD_Audio.TKM" contains the track manager
(TrackManager).

As described in the description of the presentation data, a plurality of AOB files include coded AOBs. How long these AOBs are played back, and whether each AOB is There is no description of the title of the song and the name of the composer. On the other hand, since a plurality of AOBs are only recorded in a plurality of AOB files, there is no description of the order in which they are reproduced. The track manager and the playlist manager are provided to notify such information to the playback device.

Here, the track manager indicates the correspondence between the AOBs recorded in the AOB file and the tracks, and how long the playback time of these AOBs is. And includes a plurality of track management information indicating various information such as who the composer is. A track is a playback unit meaningful to the user. When a music work is to be stored in the flash memory card 31, a track corresponds to a song, and a reading book is to be stored in the flash memory card 31 ( A reading book is not a book but a document work expressed by a read-out voice). If the book genre is used, a track corresponds to a chapter / section of a sentence. The track manager is provided for managing a plurality of AOBs recorded in a plurality of AOB files as a set of tracks.

[0060] A playlist defines a plurality of playback orders of tracks, and the playlist manager includes a plurality of such playlists. Or later,
The track manager will be described with reference to the drawings. {17-1_18} Detailed Configuration of Playlistmanager and TrackManager FIG. 17 shows Playlistmanager and TrackManager in the embodiment.
FIG. 18 is a diagram in which the configuration of the Manager is detailed in stages.
FIG. 4 is a diagram showing the sizes of PlayListManager and TrackManager. That is, in the figure, the logical format located on the right is a detailed version of the logical format located on the left, and the dashed line indicates that the logical format on the right is within the logical format on the left. It clarifies which part of has been refined.

According to such notation, Tr in FIG.
Referring to the configuration of the ackManager, the TrackManager shows the Track Information (TKI
Abbreviated) # 1, # 2, # 3, # 4,... #N. These TKIs are AO
This is information for managing the AOB recorded in the B file as a track, and corresponds to each AOB file.

Referring to FIG. 17, each TKI has a Track_General_Informatin (TKG
I), Track_Text in which text information unique to TKI is described
_Infomation_Data_Area (TKTXTI_DA), Track_Time_Serch_Table (TKTMSRT) which has the role of time search table
It turns out that it consists of. Referring to FIG. 18, the TKI itself has a fixed size (1024 bytes), and the TKGI and TKTXTI_DA
Is a fixed length of 512 bytes in total. TKTMS
RT also has a fixed length of 512 bytes. In TrackManager, up to 999 TKIs can be set.

This TKTMSRT has TMSRT_Header and TMSRT_etry # 1, # 2, # 3,... #
It turns out that it consists of n. {17-2_19} Interaction between TKI and AOB File and AOB FIG. 19 is a diagram showing the interrelation between the TKI shown in FIG. 17 and the AOB file and AOB shown in FIG. The square in the first row in FIG. 19 is a track sequence including Tracks A to E, and the square in the second row in FIG.
The kManager is shown, and the third and fourth rows show the eight AOB files shown in FIG. The eight frames in the fifth row are 8
Shows one AOB. These eight AOB files include the eight AOBs shown in FIG. 16, and include TrackA, Trac
A music album containing kB, TrackC, TrackD, and TrackE is formed. The second row shows eight TKIs. Numerical values "1", "2", "3", "4" given to these TKIs are serial numbers for identifying each TKI, and each TKI has the same serial number 0.
.. Are associated with AOB files to which 01, 002, 003, 004, 005,... With this in mind, referring to FIG. 19, TKI # 1 corresponds to AOB001.SA1 and TKI # 2 corresponds to AOB0.
02.SA1, TKI # 3 correspond to AOB003.SA1, and TKI # 4 corresponds to AOB004.SA1 (arrows TA1, TA2, TA3,
TA4 ... indicates which AOB file each TKI corresponds to. ). As described above, each TKI has a one-to-one correspondence with the AOB recorded in each AOB file.
In the KI, information specific to the AOB can be described in detail.

{17-3_20} Data structure of TKTMSRT As information unique to the AOB included in the AOB file,
First, TKTMSRT will be described. FIG.
FIG. 8 is a diagram showing a detailed data structure of TKTMSRT shown in FIG. The time search table header (TMS
The detailed data structure of (RT_Header) is shown. FIG.
, The data size of the time search table header is 8 bytes, TMSRT_ID (0th to 1st byte), reserved (2nd to 3rd byte), Total T
It has three fields, MSRT_entry_Number (4th to 7th bytes). TMSRT_ID contains TMSRT
An ID that can uniquely identify is described. 『Total TMSRT_en
In “try Number”, the total number of TMSRT_entry in the TMSRT is described.

{17-3_21-1} Specific Example of TKTMSRT Next, TKTMSRT will be described in more detail. FIG.
FIG. 3 is a diagram showing an example of TKTMSRT. AOB is shown on the left side of the figure, and TKTMSRT is shown on the right side. AO on the left side of the figure
B includes a plurality of AOB_ELEMENT # 1, # 2, # 3,... #N, and occupies a plurality of areas AR1, AR2, AR3,. In the figure, `` 0 '', `` 32000 '', `` 64200 '', `` 9700
Numerical values such as “0”, “1203400”, and “1240000” are the occupied areas AR1 of each AOB_ELEMENT from the beginning of AOB_BLOCK included in AOB.
Indicates the relative address of AR2, AR3, ARn-1, ARn. AOB_ELE
MENT # 2 indicates that it is recorded at a position separated by "32000" from the head of AOB_BLOCK. AOB_ELEMENT # 3 is A
OB_BLOCK AOB at a position separated by "64200" from the beginning
_ELEMENT # n-1 indicates that the data is recorded at a position separated by "1203400" from the head of AOB_BLOCK.

It should be noted that the interval between the start addresses of the occupied areas is not a fixed value, that is, the occupied areas of each AOB_ELEMENT occupy a plurality of clusters of different sizes. The size of each occupation area is different because the code allocation in each AOB_FRAME is variable length. Since the occupied size of each AOB_ELEMENT is different, when jumping to the beginning of each AOB_ELEMENT,
It is necessary to instruct the playback apparatus in advance where the OB_ELEMENT exists in the AOB. With this purpose,
A plurality of TMSRT_entry are described. Arrows RT1, RT2, RT3
・ ・ ・ ・ ・ ・ RTn-1 and RTn are the occupied area AR of each of these AOB_ELEMENTs
1, AR2, AR3 ... ARn-1, ARn, TMSRT_entry # 1, TMSRT_e
ntry # 2, TMSRT_entry # 3 ... TMSRT_entry # n-1, TMSRT_e
Indicates the correspondence with ntry # n. That is, the size of the occupied area AR1 of AOB_ELEMENT # 1 occupies the TMSRT.
_entry # 1 and the size of the occupied areas AR2 and AR3 of AOB_ELEMENT # 2 and AOB_ELEMENT # 3 are described in TMSRT_entry # 2 and TMSRT_entry # 3.

Here, the occupied area AR1 starts from the beginning of the AOB.
AOB_ELEMENT # 2 occupies up to the beginning "32000",
TMSRT_entry # 1 is described as 32000 (= 32000-0) and occupied area
AR2 starts with AOB_ELEME from the beginning "32000" of AOB_ELEMENT # 1.
TMSRT_ent because it occupies up to the head "64200" of NT # 2
ry # 2 is described as "32200 (= 64200-32000)", occupied area AR3
Is AOB_ELEMENT # from the beginning "64200" of AOB_ELEMENT # 3
TMSRT_entry #
3 is 32800 (= 97000-64200), occupied area ARn-1 is AOB_E
TMSRT_entry # n-1 because it occupies from the beginning "1203400" of LEMENT # n-1 to the beginning "1240000" of AOB_ELEMENT # n
Is described as "36600 (= 1240000-1203400)".

{17-3_21-2} TKTMSRT reading method As described above, it can be seen that the data size of AOB_ELEMENT is described in the time search table. Meanwhile, AO
As described in the description of B_ELEMENT, the data length of each AOB_BLOCK is determined so that the playback time is within 8.4 minutes, so the total number of AOB_ELEMENTs contained in one AOB is
(252 pieces shown in FIG. 20). AOB_ELEME
Since the number of NTs is suppressed to a predetermined number or less, the total number of TMSRT_entries corresponding to the AOB_ELEMENT is also equal to or less than a predetermined number, and the data size of TKTMSRT including these is also equal to or less than a predetermined size. Since the size of TKTMSRT has been suppressed, the playback device can read and use the TKI as follows.

When an AOB is read and its reproduction is started, the corresponding TKI is read and stored in the memory. Thereafter, the TKI is stored in the memory while the reproduction of the AOB is continued. When the reproduction of the AOB is completed, the subsequent AOB is read, and when the reproduction is started, the corresponding TKI is read, and the TKI previously stored in the memory is newly read. Overwrite using the issued TKI. Thereafter, the TKI is stored in the memory while the reproduction of the AOB is continued.

If the reading of the TKI and the storing in the memory are performed in this manner, the forward search reproduction and the reverse search can be performed only by reading the necessary TKI, even if the amount of memory installed in the reproducing apparatus is small. Special reproduction such as reproduction can be performed. In this embodiment, the data length from the start address of one AOB_ELEMENT to the start address of the next AOB_ELEMENT is described as TMSRT_entry.
, The relative address from the beginning to the beginning of each AOB_ELEMENT may be described.

{17-3_21-3} Specifying Cluster Containing AOB_ELEMENT Finally, referring to TKTMSRT, how to read an arbitrary AOB_ELEMENT will be described. Each AOB_ELEMEN
When reading the AOB_ELEMENT # y located at the y-th position from the beginning in the AOB with reference to TKTMSRT in which the size of T is described, find the cluster u that satisfies the following {Formula 1}, and offset from the beginning of the cluster u What is necessary is just to read after v. ｛Formula 1｝ Cluster u = (sum of TMSRT_entry from AOB_ELEMENT # 1 to AOB_ELEMENT # y-1 + DATA_Offset) / cluster size offset v = (sum of TMSRT_entry from AOB_ELEMENT # 1 to AOB_ELEMENT # y-1 + DATA_Offset) mod When the cluster size is c = a mod b, c indicates the remainder when a is divided by b, and DATA_Offset is information described in BIT, which will be described later.

{17-4} TKTXTI_DA This concludes the description of the time search map (TKTMSRT). Next, the Track Text Information Data Area (TKTXTI_DA) described in the upper part of TTKMSRT in FIG. 17 will be described. Track Text Information Data Area (T
KTXTI_DA) describes text information indicating an artist name, an album name, an arranger name, a producer name, and the like. This area is reserved even when no text data exists.

{17-5} TKGI Next, TKGI in the upper part of TKTXTI_DA will be described.
In FIG. 17, the TKGI of the TKI is a TKI identifier “TKI_ID”, a TKI number “TKIN”,
TKI size "TKI_SZ", link pointer to next TKI "TKI_LNK_PTR", block attribute "TKI_BLK_ATR", playback time "TKI_PB_TM", TKI audio attribute "TKI_AOB_AT"
It can be seen that a series of information such as "R", "ISRC", and block information "BIT" is recorded. (In this figure, some fields are omitted for simplicity.) There.)

{17-5_22-1} TKGI Hereinafter, a detailed configuration of the TKGI will be described with reference to FIG. The difference between this figure and FIG. 17 is that TK shown in FIG.
The data structure of the GI is arranged on the left side of the figure, and “TKI_BLK_ATR”, “TKI_AOB_
The point is that the bit configurations of “ATR” and “ISRC” are arranged on the right side in the figure.

{17-5_22-2} TKI_ID In “TKI_ID”, an ID (a 2-byte code “A4” in the present embodiment) that can uniquely identify TKI is described. {17-5_22-3} About TKIN "TKIN" describes a TKI number in the range of 1 to 999. In addition, this TKI number is described in TKIN of other TKI
Must not overlap with TKI number. As such a TKIN, the order of TKI in TrackManager, that is, TrackMana
Describe the position of TKI in ger. In the figure, for TKI # 1, the TKI number is described as "1", for TKI # 2, the TKI number is described as "2", and for TKI # 3, the TKI number is described as "3".

{17-5_22-4} TKI_SZ In “TKI_SZ”, the data size of TKI is described in units of bytes. In FIG. 22, since the data size of the TKI is defined as 1024 bytes, it is described as 1024 bytes in the present embodiment. {17-5_22-5} Regarding TKI_LNK_PTR “TKI_LNK_PTR” describes the TKIN of the TKI to which the TKI is linked. Here, the correspondence between TKIs will be described.

When a track is composed of a plurality of AOBs and these are recorded in a plurality of AOB files, a plurality of TKIs associated with the plurality of AOB files manage the track as one. Will be. When a plurality of TKIs are integrated as described above, it is necessary to indicate which TKI corresponds to an AOB file following the AOB file corresponding to the TKI. TKI_LNK_PTR is
Used for describing TKIN for TKI following KI.

{17-5_22-6_19} TKI_LNK_PTR Hereinafter, in the eight TKIs shown in FIG. 19, the TKI_LNK_PTR
The following describes how is set. In TKI # 1 to TKI # 3 and TKI # 8 forming one track, the T
KI_LNK_PTR is not set, but the four A that make up TrackD
TKI # 4, TKI # 5, TKI # 6, and TKI # 7 corresponding to OB files
Each TKI_LNK_PTR is set to point to the next TKI_LNK_PTR. That is, as indicated by arrows TL4, TL5, and TL6, TKI # 4
TKI_LNK_PTR indicates TKI # 5, and TKI_LNK of TKI # 5
_PTR indicates TKI # 6, and TKI_LNK_PTR of TKI # 6 indicates TKI # 7. These all constitute TrackD. These TKI_LNKs in the TKI associated with the four AOB files
By referring to the _PTR, four TKIs, TKI # 4 to TKI # 7,
It can be seen that KI and the four AOB files AOB004.SA1 to AOB007.SA1 together constitute TrackD.

{17-5_22-7} Regarding TKI_BLK_ATR “TKI_BLK_ATR” describes the attributes of TKI. In FIG. 22, the frame drawn from the TKI_BLK_ATR by a broken line shows the bit configuration of the TKI_BLK_ATR. In the figure, TKI_BLK_ATR is 16 bits, and bits b3 to b15 are reserved for future expansion. Attributes of TKI are described using three bits from bit numbers b2 to b0.

When TKI is used and one TKI is included in one track, a value of “000b” is described in TKI_BLK_ATR (hereinafter, this setting is referred to as “Track”). T
KI is used, one track includes multiple TKIs,
If the TKI is the first one, TKI_BLK_ATR contains "001"
b "is described. (Hereafter, this setting is referred to as" Head_of_Trac
k]. ). When TKI is used and one track is composed of a plurality of TKIs, and the TKI is in the middle, a value of “010b” is described in TKI_BLK_ATR (hereinafter, referred to as “TKI_BLK_ATR”).
This setting is called “Midpoint_of_Track”). When TKI is used and one track is composed of a plurality of TKIs, and the TKI is at the end, a value of “011b” is described in TKI_BLK_ATR (hereinafter, this setting is referred to as “End_of_Track”). . If TKI is not used and there is TKI area,
That is, in the case of a deleted TKI, a value of “100b” is described (hereinafter, this setting is referred to as “Unused”). TKI
Is unused and there is no TKI area, that is, if the TKI is in the initial state, the value of “101b” is described.

{17-5_22-8_19} Example of setting TKI_BLK_ATR In an example of FIG. 19, TKI_BLK_A for each TKI
The following describes how TR is set. each
Referring to TKI_BLK_ATR in TKI, TKI # 1 (AOB001.
SA1), TKI # 2 (AOB002.SA1), TKI # 3 (AOB003.SA1), T
The four sets KI # 8 (AOB008.SA1) correspond to independent tracks, so TKI # 1, TKI # 2, TK
TKI_BLK_ATR of I # 3 and TKI # 8 is set to “Track”.

TKI_BLK_ATR in TKI # 4 is “Head_of_Tr
ack "and TKI_BLK_ATR in TKI # 7 is" End_o
f_Track ”, and TKI # 5 and TKI # 6 are set as“ Midpoint_of_Track ”. This means that TKI # 4 (AOB004.SA1), which has a corresponding relationship with TKI # 4, has TKI # 5 (AOB005.
SA1) and TKI # 6 (AOB006.SA1)
TKI # 7 (AOB007.SA1), which has a correspondence with TKI # 7, means the end of the track.

As described above, according to the description of TKI_BLK_ATR in each TKI, if a set of TKIs (AOB files) is classified,
It can be seen that TKI # 1 (AOB001.SA1) forms the first track (TrackA). It can be seen that TKI # 2 (AOB002.SA1) forms the second track (TrackB), and TKI # 3 (AOB003.SA1) forms the third track (TrackC). TKI # 4 (AOB
004.SA1) constitutes the head of the fourth track (TrackD), and is TKI # 5 (AOB005.SA1) and TKI # 6 (AOB006.SA1).
Constitutes the middle part of TrackD, and TKI # 7 (AOB007.SA
It can be seen that 1) forms the terminal part of TrackD. T
It can be seen that KI # 8 (AOB008.SA1) independently constitutes the end of the fifth TrackE.

{17-5_22-9} TKI_PB_TM [TKI_PB_TM] describes the playback time of a track (song) composed of AOBs recorded in an AOB file corresponding to TKI. When a track is composed of a plurality of TKIs, the playback time of the entire track is described in TKI_PB_TM for the first TKI. In the second and subsequent TKIs,
The playback time of the AOB corresponding to each TKI is described.

{17-5_22-10} Regarding TKI_AOB_ATR In “TKI_AOB_ATR”, the AOB recorded in the AOB file corresponding to TKI is transferred at what sampling frequency and at what bit rate. For example, encoding conditions for generating an AOB, such as the number of channels and the number of channels, are described. "TKI_AOB_
A frame drawn by a broken line from “ATR” indicates the bit configuration of TKI_AOB_ATR. In the figure, TKI_AOB_ATR has 20 bits, and a coding mode is described in a field from bit number b16 to bit number b19. MPEG-2
If encoded with AAC (with ADTS header), the value of "0000b" is encoded with MPEG-layer3 (MP3), and the value of "0001b" is encoded with Windows Media Aud
When encoded by io (WMA), "0010b" is described.

The bit rate is described in the fields from bit number b15 to bit number b8. MPEG-2 AAC
(with ADTS header), the value of "16" to "72", and when encoded with MPEG1-layer3 (MP3), the value of "16" to "96" MPEG2-layer3
(MP3) "16" to "80" when encoded in LSF
Is encoded by Windows Media Audio (WMA), values of "8" to "16" are described.

The sampling frequency is described in bit numbers b7 to b4. "0000b" for 48kHz,
"0001b" for 44.1kHz, "0010b" for 32kHz, 24kHz
A value of "0011b" is described for z, a value of "0100b" for 22.05 kHz, and a value of "0101b" for 16 kHz. The field from bit number b3 to bit number b1 describes the number of channels. In the case of 1ch (mono), "000b" is described. 2ch (s
In the case of "tereo", "001b" is described.

The areas of bit numbers b31 to b20 and bit number b0 are reserved for future expansion. {17-5_22-11} About ISRC “ISRC” includes ISRC (International Stan
dard Recording Code) is described. A frame drawn by a broken line from “ISRC” in FIG. 22 indicates the content of ISRC. As shown in this frame, the ISRC is composed of 10 bytes, and a recording-item code (# 12) is described in a field from bit number b4 to bit number b7, and the bit number is
Recording cod in fields from b8 to bit number b11
e / Recording-item code (# 11) is described.

Recording fields (ISRC # 10, # 9, # 8) are described in the fields from bit number b12 to bit number b23. Year-of-Recording codes (ISRC # 6, # 7) are described in fields from bit number b24 to bit number b31.
Thereafter, the fields from bit number b32 to bit number b37, the fields from bit number b40 to bit number b45, and the fields from bit number b48 to bit number b53 contain the First Owner Code (ISRC # 3, # 4, # 5 ) Is described.
In the fields from bit number b56 to bit number b61, and the fields from bit number b64 to bit number b69,
Country code (ISRC # 1, # 2, # 3) is described. Bit number
In the field of b79, a 1-bit validity flag is described. For details on ISRC, see ISO3901: 1986.
'' Documentation-International Standard Recording
Code (ISRC) ''.

{17-5_22-12_23A-1} BIT The "block information table (BIT)" is a table for managing AOB_BLOCK. FIGS. 23A and 23B are diagrams illustrating a detailed configuration of the BIT. As shown in FIG.
T is DATA_OFFS occupying the 60th to 63rd bytes
ET field, SZ_DATA field occupying the 64th to 67th bytes, TMSRTE_Ns field occupying the 68th to 71st bytes, and 73th to 73rd bytes
FNs_1st_TMSRTE field occupying the byte and 74
FNs_Last_TMSRTE occupying bytes from byte 75
Field and occupies bytes 76 to 77
It consists of an FNs_Middle_TMSRTE field and a TIME_LENGTH field occupying the 78th to 79th bytes. Hereinafter, each component will be described.

{17-5_22-12_23A-2} DATA_Offset [DATA_OFFSET] describes the relative address from the cluster boundary to the head of each AOB_BLOCK in byte units. This represents how many invalid areas exist between AOB and AOB_BLOCK. If the music stored in the flash memory card 31 as the AOB is music that has been air-checked and recorded, and a disc jockey voice is mixed in the intro part of the music, BIT
By setting DATA_Offset in, the unnecessary sound can be excluded from AOB_BLOCK so as not to be reproduced.

{17-5_22-12_23A-3} Regarding SZ_DATA [SZ_DATA] describes the data length of each AOB_BLOCK in byte units. The value obtained by adding SZ_DATA and DATA_Offset
By subtracting from the file size (an integral multiple of the cluster size) containing the AOB, the size of the invalid area following the AOB_BLOCK can be obtained.

{17-5_22-12_23A-4} TMSRTE_Ns “TMSRTE_Ns” includes TMSRT_entr included in each AOB_BLOCK.
The total number of y is described. {17-5_22-12_23A-5} 『FNs_1st
_TMSRTE, FNs_Last_TMSRTE, FNs_Middle_TMSRT
Regarding “E”, “FNs_1st_TMSRTE” describes the number of AOB_FRAMEs included in the AOB_ELEMENT positioned at the head of the AOB_BLOCK.

In “FNs_Last_TMSRTE”, the number of AOB_FRAMEs included in the last AOB_ELEMENT of AOB_BLOCK is described. "FNs_Middle_TMSRTE" contains the first and last AOB
AOB_ELEMENT excluding _ELEMENT, that is, the number of AOB_FRAMEs included in AOB_ELEMENT located in the middle part of AOB_BLOCK is described.

“TIME_LENGTH” is a field that describes the playback period of AOB_ELEMENT with a time accuracy on the order of milliseconds in the format shown in FIG. FIG.
As shown in (c), the TIME_LENGTH field is 16 bits long, and the encoding method is MPEG-AAC or MPEG-Layer.
In the case of the three methods, since the playback period of the AOB_ELEMENT is 2 seconds, a value of 2000 is described in TIME_LENGTH.

{17-5_22-13_23B} FIG. 23 (b) shows the FNs_Mi
It is a figure which shows how many AOB_FRAME is stored in ddle_TMSRTE. This figure is similar to FIG. 14, and the sampling_frequency and
The correspondence with the number of AOB_FRAMEs included in the AOB_ELEMENT in the middle part is shown. Sampling_frequency in this figure and
The correspondence with the number of frames included in the AOB_ELEMENT is exactly the same as in FIG. 14, and it can be seen that the number differs according to the sampling frequency. "FNs_1st_TMSRT
E "and" FNs_Last_TMSRTE "
The number of frames is set to the same as the number of frames in `` FNs_Middle_TMSRTE '' in principle, but when setting an invalid area in AOB_ELEMENT located at the beginning or end of AOB_BLOCK,
"FNs_1st_TMSRTE" and "FNs_Last_TMSRTE" are
_Middle_TMSRTE ”.

{17-5_22-14_24} Storage Example of AOB_ELEMENT FIG. 24 is a diagram showing clusters 007 to 00E in which AOBs including AOB_ELEMENT # 1 to # 4 are stored. How the BIT is set when the AOB is stored as shown in FIG. 24 will be described. These clusters
AOB_ELEMENT # 1 to AOB stored in 007 to cluster 00E
Each of _ELEMENT # 4 is provided with a triangular flag symbol, which indicates that TMSRT_entry included in TKI is set in each of AOB_ELEMENT # 1 to AOB_ELEMENT # 4.

At this time, the leading end of AOB_ELEMENT # 1 at the leading end of AOB is stored in cluster 007, and the trailing end of AOB_ELEMENT # 4 at the end of AOB is stored in cluster 00E. AOB_ELEMENT # 1 ~ # 4 is in the middle of cluster 007
It occupies md0 to md4 in the middle of cluster 00E. SZ_DATA in BIT is AOB_ELEMENT # 1 to A as shown by arrow sd1.
It indicates to the end of OB_ELEMENT # 4, cluster 007,
The areas ud0 and ud1 in the area within 00E and not occupied by the AOB_ELEMENT are not specified.

On the other hand, AOB is an area in cluster 007 and cluster 00E, and is AOB_ELEMENT # 1, AOB_ELEMEN.
Also includes parts ud0 and ud1 not occupied by T # 4. DATA_Offset in the BIT indicates the data length of the unoccupied portion ud0, that is, the relative value from the beginning of the cluster 007 to the beginning of AOB_ELEMENT # 1. AOB_ELEM in this figure
ENT # 1 is in the middle of cluster 007 from md0 in the middle of cluster 007
Occupies up to md1. The AOB_ELEMENT # 1 does not occupy the entire cluster 008, but is occupied by AOB_ELEMENT # 2 after the end. AOB_ELEMENT # 4
Occupies the middle part md3 of the cluster 00C to the middle part md4 of the cluster 00E. AOB_ELEMENT like this
It can be seen that there is something recorded so as to straddle the boundary of the cluster. That is, AOB_ELEMENT is
It is recorded irrespective of the boundaries of the cluster. “FNs_1st_TMSRTE” in the BIT indicates the number of AOB_ELEMENT # 1 frames in the clusters 007 to 008, and “FNs_Last_TMSRTE” in the BIT indicates
It shows the number of frames of AOB_ELEMENT # 4 in cluster 00E.

As described above, each AOB_ELEMENT is freely arranged irrespective of the boundary of the cluster, and the BIT manages the offset from the cluster boundary to the AOB_ELEMENT and the number of frames for each AOB_ELEMENT. . {17-5_22-14_25} How to Use Number of Frames for Each AOB_ELEMENT How the number of frames for each AOB_ELEMENT described in 1 BIT is used will be described below. First, the number of frames described in the BIT is determined by setting the elapsed playback time to 2
This is used when performing forward search reproduction and reverse search reproduction in which the data is skipped for seconds and reproduced for 240 milliseconds.

FIG. 25 shows a case where forward search reproduction is performed from AOB_FRAME # x in an arbitrary AOB_ELEMENT # y in the AOB.
FIG. 11 is a diagram illustrating how to set AOB_FRAME # x + 1 to be reproduced next. This figure shows the AOB included in AOB_ELEMENT # y
FIG. 11 is a diagram drawn on the assumption that a forward search reproduction is instructed at the time point when _FRAME # x is reproduced. In the figure, t is a predetermined intermittent playback time (= 240 milliseconds), f
(t) is the number of frames corresponding to the intermittent playback time, the intermittent skip time skip_time is the length of time to skip when performing intermittent playback (in this case, 2 seconds), and the intermittent skip time sk
Let f (skip_time) be the number of frames corresponding to ip_time.
Here, the intermittent reproduction is performed by repeating the following procedure.

Referring to TMSRT_entry described in TKTMSRT, jump to the head of the flag (AOB_ELEMENT). Play for 240 milliseconds Jump to the beginning of the next flag (AOB_ELEMENT). In the present embodiment, a method for realizing more accurate intermittent reproduction, in which reproduction is performed for 240 milliseconds, a jump to a position two seconds later is performed, and reproduction is performed for 240 milliseconds, will be described.

[0103] From AOB_FRAME # x included in AOB_ELEMENT # y, AOB_FRAME # x + 1 2 seconds + 240 milliseconds later is AOB_ELEMENT #
Should be in y + 1. AOB_FRAM after 2 seconds + 240 ms
When specifying E # x + 1, the start address of the next AOB_ELEMENT # y + 1 can be calculated immediately by reading out TMSRT_entry in TKTMSRT.
The number of AOB_FRAMEs existing from the start address of ELEMENT # y + 1 to AOB_FRAME # x + 1 cannot be known only by TMSRT_entry. To calculate such AOB_FRAME number, AOB_FRAME
From the sum of #x, which indicates the position of RAME # x from the beginning of AOB_ELEMENT # y, f (t), and f (skip_time), AOB_EL
It is necessary to obtain by subtracting the total number of frames included in EMENT # y. So, the next AOB_ELEMENT # y + 1
In order to easily calculate the relative frame position of AOB_FRAME # x + 1 in, the BIT is set to “FNs_1st_
TMSRTE, FNs_Middle_TMSRTE, FNs_Last_TMSRT
E ”is described.

{17-5_22-15_26A} Usage of number of frames for each AOB_ELEMENT 2 The number of frames described in BIT is secondly a function of starting reproduction from an arbitrary reproduction time (time search function) It is used when executing. FIG. 26A is a diagram showing how, when an arbitrary reproduction start time is designated, AOB_ELEMENT and AOB_FRAME corresponding to the designated time are specified.

When an arbitrary time is specified and the reproduction is instructed, assuming that the specified reproduction time is Jmp_Entry (seconds), an AOB_ELEMENT # y satisfying the following expression and an AOB_FRAME position x
What is necessary is just to start reproduction. << Equation 2 >> Jmp_Entry (sec) = (FNs_1st_TMSRTE + FNs_middle_TMSRTE
× y + x) × 20msec These “FNs_1st_TMSRTE” and “FNs_Middle_TMSRTE”
Are described in the BIT. If AOB_ELEMENT # y and AOB_FRAME # x are calculated by applying these to {Equation 2}, the AOB is referred to the TKTMSRT corresponding to this AOB, and the y + 2nd in the AOB , The search for AOB_FRAME # x is started from this start address, and when the x-th AOB_FRAME is searched, the reproduction is started from the x-th AOB_FRAME. This allows Jmp_E
Playback can be started from the time specified by ntry (seconds).

At this time, the ADTS header portion of the AOB file is not searched, and the AOB_TTSRT_entry in the TKTMSRT
Since the search only needs to be performed in ELEMENT units, the playback position corresponding to the designated playback time can be found at high speed. Similarly, when the time search function is executed on a track consisting of multiple AOBs and Jmp_Entry (seconds) is specified,
AOB_ELEMENT # y that satisfies the following {Formula 3} and AOB_FRAME
What is necessary is to calculate #x. {Equation 3} Jmp_Entry (seconds) = total playback time from AOB # 1 to AOB # n
+ (FNs_1st_TMSRTE (# n + 1) + FNs_middle_TMSRTE (# n + 1) ・ y +
x) ・ 20msec Here, the total of the playback time of AOB from AOB # 1 to AOB # n is
It is as follows. Total playback time from AOB # 1 to AOB # n = ("FNs_1st_TMS
RTE ''(# 1) + `` FNs_Middle_TMSRTE ''(# 1) ・ (TMSRT_entry number
# 1-2) + `` FNs_Last_TMSRTE ''(# 1) + `` FNs_1st_TMSRTE ''
(# 2) + `` FNs_Middle_TMSRTE ''(# 2) ・ TMSRT_entry number # 2-2) +
`` FNs_Last_TMSRTE ''(# 2) + `` FNs_1st_TMSRTE ''(# 3) +
`` FNs_Middle_TMSRTE ''(# 3) ・ TMSRT_entry number # 3-2) + `` FNs
_Last_TMSRTE ''(# 3) ・ ・ ・ ・ ・ ・ ・ ・ ・ + `` FNs_1st_TMSRTE ''(#
n) + `` FNs_Middle_TMSRTE ''(#n) ・ TMSRT_entry number # n-2) +
AOB # n, AOB_ELEMENT # y, AOB_FRAME # that satisfies Formula 3
When x is calculated, the search for AOB_FRAME # x is started from the address located at y + 2nd AOB_ELEMENT # y + 2 with reference to TKTMSRT corresponding to this AOB # n + 1, and the xth AOB_FRAME Is searched, playback is started from the x-th AOB_FRAME.

{17-5_22-16_27A, B} AOB file and TKI
Having explained all the information included in the TKI, if some tracks were deleted (case 1), if some tracks were deleted and a new track was recorded (case 2),
How to update TKI when combining any two of multiple tracks into one track (case 3), splitting one track and obtaining two tracks (case 4) Will be described.

First, the case where some tracks have been deleted (case 1) will be described. FIGS. 27A and 27B
Is a diagram assuming that a track is deleted. This figure shows the TrackManager shown in FIG. 19, and it is assumed that the operator desires to delete TrackB in this figure. AOB corresponding to this TrackB is AOB002.SA
AOB002.SA1 is deleted, and TKI_BLK of TKI # 2 is deleted because it is recorded in 1 and it is associated with TKI # 2.
_ATR is set to "Unused". FIG. 27B shows a state in which AOB002.SA1 has been deleted and TKI_BLK_ATR of TKI # 2 has been set to "Unused". Since AOB002.SA1 has been deleted,
The area occupied by AOB002.SA1 in the data area is released to a free area. At the same time, in TrackManager, it can be seen that TKI_BLK_ATR of TKI # 2 is set to “Unused”.

{17-5_22-17_28A, B} TKI allocation for recording a new AOB file Following recording of a new track after some tracks have been deleted (case
2) will be described. FIG. 28A is a diagram showing the TrackManager after a track has been deleted a plurality of times. In this figure, multiple tracks have been deleted and these are
2. If TKI # 4, TKI # 5, TKI # 7, and TKI # 8 are associated, TKI_BLK_ATR of these TKIs is set to "Unused". Deletion of AOB files is performed in the same way as normal files, but TrackManager uses the corresponding TKI's TKI_B
The deletion process is completed only by setting LK_ATR to “Unused”. Then, as shown in this figure, the “Unused” TKI
Will appear on the TrackManager in a worm-like manner.

FIG. 28B is a diagram showing how the writing is performed when a new TKI or AOB file is written in the presence of an “Unused” TKI. Here, it is assumed that a track composed of four AOBs is to be written. Here, which empty TKI is allocated to the recording of the AOB is determined by DPL_TK_SRP to be described later, or an arbitrary TKI is allocated. The four AOBs
Are assigned to TKI # 2, TKI # 4, TKI # 7, and TKI # 8 set to "Unused" in the TrackManager.

Since these four AOBs constitute one track, TKI_BLK_ATR for TKI # 2 is changed to “Head_o
f_Track ”and TKI_BLK_ATR for TKI # 4 and TKI # 7 to“ Midpoint_of_Track ”and TKI_BLK_AT for TKI # 8
R is set to “End_of_Track”. Track TrackD
The four TKI # 2, TKI # 4, TKI # 7, and TKI # 8 that make up each TKI
_LNK_PTR is the next TKI_LNK_PT that makes up track TrackD
It is set to indicate R. That is, arrows TL2, TL4, T
As shown in L7, TKI_LNK_PTR of TKI # 2 indicates TKI # 4, TKI_LNK_PTR of TKI # 4 indicates TKI # 7, and TKI_LN of TKI # 7
K_PTR indicates TKI # 8.

Thereafter, four files AOB002.SA1, A4 having the same number as each of TKI # 2, TKI # 4, TKI # 7, and TKI # 8
OB004.SA1, AOB007.SA1, and AOB008.SA1 are created, and the four AOBs that make up TrackD are recorded in these four files. With the settings of TKI_BLK_ATR and TKI_LNK_PTR, the fourth track TrackD is set to TKI # 2, TKI # 4, TKI # 7,
It will be managed using TKI # 8.

As described above, the flash memory card 3
When writing a new track to TrackMan
It can be seen that the TKI set to “Unused” in the ager is assigned to the TKI for the track to be newly recorded. {17-5_22-18_29A, B} T when combining two tracks
KI setting Next, how to update TKI when integrating tracks (case 3) will be described.

FIGS. 29A and 29B are diagrams showing how the TKI is set when two tracks are integrated into one. FIG. 29A shows the TrackM shown in FIG.
It is the same as anager, and in FIG.
It is assumed that the operator desires an editing operation of integrating TrackE into one track. These TrackC, Trac
The AOB corresponding to kE is recorded in AOB003.SA1 and AOB008.SA1, and they are associated with TKI # 3 and TKI # 8, so TKI_BLK_ATR of these TKI # 3 and TKI # 8 is rewritten. Is FIG. 29B is a diagram showing the TKI after rewriting TKI_BLK_ATR. In the figure, TKI_3 and TKI_8 TKI_
Although BLK_ATR is described as Track, in FIG. 29B, TKI_BLK_ATR of TKI # 3 is rewritten to “Head_of_Track”, and TKI_BLK_ATR of TKI # 8 is rewritten to “End_of_Track”. As described above, by rewriting TKI_BLK_ATR, TKI # 3, TKI # 8, and the corresponding AO
B003.SA1 and AOB008.SA1 are handled as one track called TrackC. In addition, TKI_LNK_PTR of TKI # 3 is rewritten so as to indicate TKI # 8 as a link destination.

It should be noted here that TKI_BLK_ATR of TKI was rewritten, but the process of integrating AOB003.SA1 and AOB008.SA1 was not performed. Because these AOB files are encrypted with different FileKeys, when they are integrated into one, the decryption-encryption that decrypts the encrypted AOB file and encrypts it again It is necessary to perform these two processes for each AOB file, and a large processing load is required. The AOB file after integration is one FileKey
This is because the copyright protection is weakened compared to before the integration.

In addition, although the TKI is originally determined not to increase the size of TKTMSRT, if it is integrated into one in the editing operation, the size of the TKI after integration may be too large. Because. As described above, the integrated editing of tracks in this embodiment is performed by AO
It can be seen that it is realized only by changing the attribute of TKI_BLK_ATR while maintaining the encryption of the B file.

{17-5_22-18_29A, B-1_30, 31} Conditions to be Satisfied When Tracks are Integrated Track integration is realized by changing the attribute of TKI_BLK_ATR as described above. For the integration, it is required that the AOB included in the track to be integrated satisfies the following conditions. The first condition is that the AOB included in the following track and the AOB included in the preceding track have the same audio attribute (audio coding mode, bit rate, sampling frequency, number of channels). . this is,
If the audio attributes of the AOBs differ between the preceding and following AOBs, the playback device needs to reset the operation of the decoder once, which makes it difficult to play back two consecutive AOBs seamlessly (without interruption). .

The second condition is that in a track obtained after integration, the number of AOB_FRAMEs is “FNs_Middle_TMSRT”.
That is, three or more AOBs consisting of only AOB_ELEMENTs less than "E" are not consecutive. AOB is 2 depending on whether at least one of the AOB_ELEMENTs has the same number of AOB_FRAMEs as the number of frames specified in “FNs_Middle_TMSRTE”.
Are classified into two types. The first type of AOB is "FN
A of the same number as the number of frames specified in "s_Middle_TMSRTE"
An AOB that has at least one AOB_ELEMENT with an OB_FRAME, and a second type of AOB is `` FNs_Middle_TM
AOB that does not have any AOB_ELEMENT that has the same number of AOB_FRAMEs as the number of frames specified in “SRTE”.
That is, the AOB_ELEMENT in the second type of AOB is less than the number of frames specified in “FNs_Middle_TMSRTE”, and the second condition described above is a type 2 AOB
It is forbidden that three or more consecutive. The reasons for the prohibition are as follows. That is, when sequentially reading out the AOBs, the buffer in the playback device has a sufficient number of AOB_FRAMs.
Although it is desirable that the AOB is filled with E, if the Type 2 AOB is continuous, the buffer in the playback device is set to AOB_FRAME
Can not be satisfied. Then, the buffer in the playback device underflows, and the continuity of AOB playback cannot be maintained. To avoid such underflow, the second condition prohibits three or more consecutive Type 2 AOBs.

FIG. 30A shows an AOB of Type 1 and FIG.
0 (b) is a diagram showing an AOB of Type2. FIG. 30 (b)
AOB in is composed of only two or less AOB_ELEMENTs, and those two or less AOB_ELEMENTs are "FNs_Middle_TMSRTE"
Does not have the AOB_FRAME shown in
Describes only FNs_1st_TMSRTE. ). 『FNs_Mi
Since it is a requirement of Type 2 AOB that the AOB_FRAME shown in “ddle_TMSRTE” is not provided, even an AOB constituted by only one AOB_FRAME is classified as a Type 2 AOB.

FIG. 31 (a) shows Type1 + Type2 + Type2 + T
FIG. 11 is a diagram showing a case where a plurality of tracks are integrated into one by combining ype1. In this case, since three consecutive Type 2 AOBs are avoided, they are integrated into one track. FIG. 31B shows Type1 + Type2 + Type2.
It is a figure which shows the case where a plurality of tracks are integrated into one by the combination of + Type2 + Type1. In this case, the Type 2 AOB
Because they are three in a row, it is forbidden to combine them into one track.

{17-5_22-18_29A, B-1_32} Type1, Type2
According to the track integration shown in FIG. 31 (a), when the end of the preceding track is Type 1, this track is a track having a Type 2 AOB at the beginning or a head. To
It can be integrated with trucks with Type 1 AOBs.
FIG. 32A shows a Type 1 AOB at the end of the preceding track.
FIG. 11 is a diagram illustrating an arrangement pattern in which Type 1 AOBs are arranged at the beginning of a subsequent track. FIG. 32
(B) is a diagram showing an arrangement pattern in which a Type 1 AOB is provided at the end of a preceding track and a Type 2 AOB is provided at the beginning of a following track. These are all conditions
Since it meets 2, it can be integrated into one track.

The end of the preceding track is Type2,
If a Type1 AOB is located immediately before Type2,
This track can be integrated with a track having a Type 1 head or a Type 2 AOB disposed immediately after the Type 1 AOB. FIG. 32 (c)
FIG. 4 is a diagram showing an arrangement pattern in which AOBs are arranged in the order of Type 1 and Type 2 at the end of a preceding track, and AOBs of Type 1 are arranged at the head of a following track. FIG. 32 (d)
FIG. 11 is a diagram showing an arrangement pattern in which AOBs are arranged in the order of Type1 and Type2 at the end of a preceding track, and AOBs of Type2 and Type1 are arranged at the beginning of a following track. These too
Since condition 2 is satisfied, it can be integrated into one track.

The end of the preceding track is Type2,
If a Type2 AOB is placed immediately before that Type2,
This track can be integrated with a track having a Type 1 AOB at the beginning. FIG. 32E is a diagram showing an arrangement pattern in which Type2 and Type2 AOBs are arranged at the end of the preceding track, and Type1 AOBs are arranged at the beginning of the succeeding track. Since this also satisfies condition 2, it can be integrated into one track. As described above, in merging tracks, it is determined in advance whether two tracks to be merged satisfy the above two conditions,
Only when it is determined that these two conditions are satisfied, the two tracks are integrated into one.

Next, updating of the TKI when the track is divided (case 4) will be described. {17-5_22-19_33A, B} TKI setting for dividing a track FIGS. 33A and 33B are diagrams assuming a case where one track is divided into two tracks. Tr in this figure
The ackManager is the same as the TrackManager shown in FIG. 27, and in this figure, it is assumed that the operator wants to edit TrackC into two tracks, TrackC-TrackF. When trying to divide TrackC into TrackC-TrackF, AOB002.SA1 corresponding to TrackF is generated. In FIG. 33 (a), TKI # 2 is set to “Unused”, and as a result of division, as shown in FIG. 33 (b), “Unused”
TKI # 2 set to AOB002.SA
Assigned to 1.

{17-5_22-19_33A, B-1_34A, B} Update of directory entry and FAT value When AOB003.SA1 is divided and AOB002.SA1 is generated, the directory entry and FAT value must be updated. No. How to update these directory entries and FAT values will be described below. FIG. 34 (a)
FIG. 14 is a diagram showing how an SD_Audio directory entry for an SD_Audio directory to which AOB003.SA1 belongs is described before division. AOB003.S
A1 is divided into a plurality of clusters 007,008,009,00A ...
・ It shall be stored in 00D and 00E. In this case, the “file first cluster number” of AOB003.SA1 in the directory entry is described as “007”, and the FAT value 007,00 corresponding to the cluster 007,008,009,00A... 00D.
8,009,00A ... 00D is (008), (009), (00A) ...
(00D) and (00E).

In this state, the latter half of AOB003.SA1 is divided.
To obtain AOB002.SA1, the “file name”, “file extension”, and “file first cluster number” for AOB002.SA1 are added to the SD_Audio directory entry. FIG. 34B shows AOB003.SA1 after division.
FIG. 11 is a diagram showing how an SD_Audio directory entry for the SD_Audio directory to which the “.” Belongs is described.

The cluster 00F in the figure stores a copy of the contents of the cluster 00B including the division boundary specified by the operator. The divided part following the divided part of AOB002.SA1 stored in the cluster 00B is stored in the clusters 00C, 00D, 00E and thereafter. Since the first part of AOB002.SA1 is stored in cluster 00F and the remaining part is stored in clusters 00C, 00D, 00E and thereafter, AOB002.SA1
The “file first cluster number” for 1 describes the cluster number 00F indicating the cluster 00F.
FAT value 00F, 00C, 00 associated with 00F, 00C, 00D, 00E
D, 00E describes (00C), (00D), (00E).

{17-5_22-19_33A, B-2_35A, B} Setting of information element in TKI By updating the above directory entry and FAT value,
After obtaining OB002.SA1, how to set information elements in TKI for AOB002.SA1 will be described. When generating a TKI for a divided track, the information elements of the TKI should be copied and inherited from those described in the original TKI (1), and should be updated based on the original TKI There are two types of things that must not be done (2). The former corresponds to TKTXTI_DA, ISRC, and the latter corresponds to BI
T, TTKMSRT and other remaining components. Since both of these exist, in the present embodiment, when generating the TKI for the divided track, the TKI of the division source is copied.
Then, a new TKI template is created, TTKMSRT and BIT included in the template are divided and updated, and the remaining information elements are updated.

FIG. 35A is a diagram assuming a case where an AOB is divided by an arbitrary AOB_FRAME. In the figure, the first row shows four AOB_ELEMENTs, AOB_ELEMENT # 1 and AOB_ELE.
Indicates MENT # 2, AOB_ELEMENT # 3, AOB_ELEMENT # 4. these
The data length of each of the four AOB_ELEMENTs is four TMSRTs
_entry # k-1, # k, # k + 1, # k + 2 (here k = 2) TKTM
Set to SRT. In this figure, if the division boundary bd1 is set in AOB_ELEMENT # 2, AOB_ELEMENT
# 2 is divided into an area composed of frames before the division boundary bd1 and an area composed of frames behind the division boundary bd1. In FIG. 35B, the AOB is divided in the middle of AOB_ELEMENT # 2, and two AOBs AOB # 1 and AOB # 2 are obtained.
It is a figure showing the state where was obtained.

{17-5_22-19_33A, B-3_36} Setting of BIT FIG. 36 is a diagram showing how the BIT is set when the AOB is divided as shown in FIG. . The AOB shown in FIG. 35 is divided at the division boundary bd1,
AOB # 1 obtained by the division is AOB_ELEMENT # 1 and AO_ELEMENT # 1.
Contains two AOB_ELEMENTs called B_ELEMENT # 2, where AOB # 2 is
AOB_ELEMENT # 1, AOB_ELEMENT # 2, AOB_ELEMENT # 3
You can see that it contains two AOB_ELEMENTs.

Each of these AOB_ELEMENTs is also provided with a triangular flag-shaped symbol.
Indicates that TMSRT_entry included in TKI corresponding to AOB is set. First, AOB # 1 obtained by division
Will be described. AOB_ELEMENT # 1, AO included in AOB # 1
Since B_ELEMENT # 2 occupies cluster 007 to cluster 00A, AOB # 1 is treated with cluster 007 to cluster 00A as one unit. Where AOB_ELEMENT # 2 in AOB # 1
Does not occupy the end of cluster 00A,
SZ_DATA for AOB # 1 is shifted from area md0 to cluster 0
This indicates the data length up to the division boundary bd1 at 0A. AOB # 1's "FNs_1st_TMSRTE" is the same as before splitting, but AOB # 1's "FNs_Last_TMSRTE" is AOB_ELEMENT #
2 in that the number of frames from the head before division to the division boundary bd1 is indicated.

Subsequently, AOB # 2 obtained by the division will be described. AOB_ELEMENT # 1, AOB_ELEMEN included in AOB # 2
T # 2 and AOB_ELEMENT # 3 occupy clusters 00B to 00F. Cluster 00F is a cluster that stores a copy of the contents of cluster 00A. (The reason for storing a copy of cluster 00A in cluster 00F is that cluster 00A
Is occupied by AOB_ELEMENT # 2 of AOB # 1, so
AOB_E that is different from this cluster in AOB # 2
This is because it is necessary to assign to LEMENT # 1. ).

AOB_ELEMENT # 1 in AOB # 2 is a cluster
SZ_DATA for AOB # 2 is not occupied from the top of cluster 00B, but is occupied from the beginning of cluster 00B.
This indicates the sum of the data length up to the middle part in E and the data length occupied by AOB_ELEMENT # 1 in cluster 00F.

The cluster 00A stored in the cluster 00F
AOB_1's AOB_ELEMENT # 2 is recorded in the copy of AOB # 1, and the portion occupied by AOB_1's AOB_ELEMENT # 2 must be excluded from AOB # 2.
DATA_Offset for AOB # 1 in cluster 00F
The size occupied by AOB_ELEMENT # 2 is set.

As can be seen from this figure, in the AOB division, only the AOB_ELEMENT including the division boundary is divided into two, and the AOB_ELEMENT before and after the division boundary is not changed from the one before the division. Understand. Therefore, AOB #
2's FNs_Last_TMSRTE is set to the same value as AOB_ELEMENT # 4's FNs_Last_TMSRTE before splitting, and AOB # 2's
“s_1st_TMSRTE” is set to the number of frames included in AOB_ELEMENT # 1 of AOB # 2, that is, the end portion after the division boundary in AOB_ELEMENT # 2 before division.

{17-5_22-19_33A, B-4_37} Setting of BIT FIG. 37 is a diagram more specifically showing how the BIT changes before and after division. The BIT on the left side of FIG. 37 shows a setting example of the BIT before division. BIT before splitting tracks
Means that Data_Offset is set to X, SZ_DATA is "52428",
TMSRTE_Ns is set to “n”. It can be seen that FNs_1st_TMSRTE is set to “80 frames”, FNs_Middle_TMSRTE is set to “94 frames”, and FNs_Last_TMSRTE is set to “50 frames”.

The right side of FIG. 37 shows the BIT settings for the two tracks after division. When the AOB corresponding to this BIT is divided as shown in FIG. 35A, the Data_Offset is set to the same value “x” as before the division in the BIT of the first track, but the SZ_DATA is extended to the division point bd1. Is updated to the data length "Q", and TMSRTE_Ns contains the first TMSRT_entr
It is updated to “k” which is the number of TMSRT_entry from y to the k-th TMSRT_entry. FNs_1st_TMSRTE and FNs_Middl
e_TMSRTE is set to 80,94 frames as before, but the last AOB_ELEM of the AOB on the first track after division
Since ENT includes p AOB_FRAMEs in FIG. 35A, FNs_Last_TMSRTE is set to “p frame”.

In the BIT of the second track, Data_Offset is set to R, SZ_DATA is set to the original SZ # DATA52428—the data length “Q” from the division point bd1, and TMSRTE_Ns is set to n−k + 1 (k This is a number obtained by adding nk, which is the number of TMSRT_entries from the TMSRT_entry to the nth TMSRT_entry, and 1 which is the number of the kth TMSRT_entry newly added for division.) FNs_Middle_TMSRTE and FNs_Las
The t_TMSRTE is set to 94,50 frames as before the division, but the first AOB_ELEM of the AOB on the second track after the division
Since ENT contains 94-p AOB_FRAMEs, FNs_
1st_TMSRTE is set to “94-p frame”.

{17-5_22-19_33A, B-5_38} Setting of BIT FIG. 38 is a diagram showing TTKMSRT after division. First TMSRT
Is as follows. TMSRT on the first track is from the beginning of the TMSRT of the AOB before division to the k-th entry
(TMSRT_entry # 1 to TMSRT_entry # k). It should be noted here that AOB_ELEMENT # k including the division boundary only includes an area, and thus the k-th entry includes only the data size of a portion corresponding to this area. 2
TMSRT of track is n from the k-th entry before division
It includes (TMSRT_entry # k to TMSRT_entry # n) up to the third entry. Note that AOB_ELEMEN with split boundaries
Since T # k only includes the area on the second track,
The k-th entry before the division includes only the data size of a portion corresponding to this area.

If the TKI is copied and the TTKMSRT and BIT are divided and updated, and the remaining information elements are updated, the TKI for the new track obtained by the division can be obtained. As in the case of integration, the encrypted AOB file remains encrypted without being decrypted
Tracks corresponding to AOB files can be split into two. Since decryption and re-encryption are not involved in AOB file division, it can be seen that the processing load when dividing tracks is reduced. As a result, the track can be edited even when the processing performance of the playback device is low.

The description of the TKI has been completed. Next, the playlist will be described. {17-6} Playlistmanager The Playlistmanager shown in FIG.
As shown in, PlaylistManager_Info for managing a playlist stored in the flash memory card 31
rmation (PLMGI) and Default_Playlist_Informa that manages all tracks stored in the flash memory card 31
tion (DPLI) and PlaylistInformation (PLI) # 1, # 2, # 3, # 4,
.. #N, and the Default_Playlist information includes Default_Playlist_Gener as shown by a dashed leader line h6.
al_Information (DPLGI), Default_Playlist_Track_Serch
_Pointer (DPL_TK_SRP) # 1, # 2, # 3, # 4,... #M. Each PLI includes Playlist_General_Information (PLGI), Playlist_
Track_Serch_Pointer (PL_TK_SRP) # 1, # 2, # 3, # 4,... #M.

Here, Default_Playlist information and PlayList
The difference from the information is explained. Default_Playlist
The information is required to specify all tracks, whereas the PlayList information does not have such a duty, and an arbitrary track may be specified. For this reason, the user generates PlayList information that designates only his / her favorite track and stores the PlayList information in the flash memory card 31.
The playback device automatically generates PlayList information that designates only a track of a predetermined genre among a plurality of tracks stored in the flash memory card 31.
It is suitable for use in storing in

{17-7_18} Number of Play Lists and Data Size Referring to FIG. 18, the maximum number of play lists is 99. Also, Playlist Manager Information (PLMGI) and Def
The ault Playlist Information (DPLI) has a fixed length of 2560 bytes in total. Playlist Information (PLI) also has a fixed length of 512 bytes. DPL_TK_SRP included in Default_Playlist information includes DPL_TK_ATR and DPL_TKIN. On the other hand, PL_TK_SRP included in PlayList information is P
Contains only L_TKIN. These DPL_TK_ATR, DPL_TKI
N, PL_TKIN has the format shown in FIG.

{17-8_39-1} Format of DPL_TK_SRP FIG. 39A shows the format of DPL_TK_SRP. In FIG. 39 (a), DPL_TK_SRP describes DPL_TKIN in the 0th to 9th bits, DPL_TK_ATR in the 13th to 15th bits, and reserves 10th to 12th bits. Reserved.

Next, a TKI number is described in DPL_TKIN occupying the field from the 0th bit to the 9th bit.
By describing the TKI number here, the TKI can be specified. {17-9_39B} Format of PL_TK_SRP FIG. 39 (b) is a diagram showing the format of PL_TK_SRP. PL_TK_SRP has a field from the 0th bit to the 9th bit, and PL_TKIN, that is, a TKI number is described here.

{17-8_39A-2} Configuration of DPL_TK_ATR Dashed arrows h51 and h52 from “DPL_TK_ATR” in FIG.
An example of DPL_TK_ATR setting is shown in the frame drawn in.
As can be understood from the description in this frame, the setting of DPL_TK_ATR for DPL_TK_SRP is based on TKI_BLK_A for TKI.
Same as TR setting, "Track", "Head_of_Trac"
k "," Midpoint_of_Track ", or" End_of_Track ".

More specifically, when the TKI specified by TKIN is in use and an audio object corresponding to one track is recorded in an AOB file corresponding to the TKI (“TKI_BLK_ATR of TKI” Track ”), DPL
_TK_ATR is set to the value of "000b". If the TKI specified by TKIN is in use and the AOB file corresponding to the TKI contains an audio object corresponding to only the beginning of the track (“Head_of_Track” in TKI_BLK_ATR of TKI), DPL_TK_ATR is “ 001b "is set.

The TKI specified by TKIN is in use,
When the AOB file corresponding to the TKI contains an audio object corresponding to only the middle part of the track (“Midpoint_of_Trac” in TKI_BLK_ATR of TKI)
k "), and the value of" 010b "is set in DPL_TK_ATR. TKIN
The TKI specified in is used and corresponds to the TKI
When the AOB file contains an audio object corresponding to only the end of the track (TKI's TKI_BLK
"End_of_Track" in _ATR) and "0" in DPL_TK_ATR
11b "is set.

The TKI specified by TKIN is unused, and TKI
When only the KI area is reserved, that is, when the TKI is a deleted TKI (“Unuse” in TKI_BLK_ATR of TKI)
d ”), the value of“ 100b ”is set. T specified by TKIN
When the KI is unused and the TKI area is not secured, that is, when the TKI is in the initial state, the value of “101b” is set.

“DPL_TK_SRP” has a correspondence with any one of a plurality of TKIs by describing the TKI number in DPL_TKIN. The order of DPL_TK_SRP in the Default_Playlist information indicates the order of the AOB (AOB file) corresponding to the TKI having a correspondence with DPL_TK_SRP. By these things, Default_Play
The order of DPL_TK_SRP in the list information defines the order in which a plurality of tracks are reproduced, that is, the order in which the tracks are reproduced.

{17-9_40-1} Default_Playlist information, TK
FIG. 40 is a diagram showing the interrelationship between Default_Playlist information, TKI, and AOB file. The second, third, and fourth tiers in the figure are the same as the first, second, and third tiers in FIG. 19, and show a TrackManager including eight TKIs and eight AOB files. . What is different from FIG.
The point is that a rectangular frame indicating Playlist information is described.
The eight small frames included in the first stage frame are Default_Playlis
Indicates eight DPL_TK_SRPs included in the t information. The upper part of these small frames shows DPL_TK_ATR, and the lower part shows DPL_TKIN.

Referring to the arrows DT1, DT2, DT3, DT4,... In this figure, a correspondence is established between DPL_TK_SRP # 1 and TKI # 1, and DPL_TK_SRP # 2 and TKI # 2, DPL_T
It can be seen that the correspondence is established between K_SRP # 3 and TKI # 3, and between DPL_TK_SRP # 4 and TKI # 4. Furthermore, each
If you refer to DPL_TK_ATR in DPL_TK_SRP, DPL_TK_S
RP # 1, DPL_TK_SRP # 2, DPL_TK_SRP # 3, and DPL_TK_SRP # 8 are all set to Track. That is, DPL_TK_SRP # 1 → T
KI # 1 (AOB001.SA1), DPL_TK_SRP # 2 → TKI # 2 (AOB002.SA
1), DPL_TK_SRP # 3 → TKI # 3 (AOB003.SA1), DPL_TK_SRP
The four sets # 8 → TKI # 8 (AOB008.SA1) correspond to independent tracks.

DPL_TK_SRP # 4, DPL_TK_SRP # 5, DPL_TK_SRP
DPL_TK_ATR of # 6 and DPL_TK_SRP # 7 is not set to Track, and DPL_TK_ATR of DPL_TK_SRP # 4 is "Head_of_Tr
ack "and DPL_TK_ATR in DPL_TK_SRP # 7 is set to" End_of_Track ", and DPL_TK_SRP # 5 and DPL_TK_SRP # 6 are set to" Midpoint_of_Track ". This means that TKI # has a corresponding relationship with DPL_TK_SRP # 4.
4 (AOB004.SA1) is the beginning of the track and DPL_TK_
TKI # 5 (AOB005.SA1) and T, which have a corresponding relationship with SRP # 5, # 6
KI # 6 (AOB006.SA1) is the middle part of the track and DPL_TK_S
TKI # 7 (AOB007.SA1), which has a correspondence with RP # 7, means the end of the track.

[0154] The order of DPL_TK_SRP in the DefaultPlaylist indicates in what order the AOBs associated with each TKI are reproduced. DPL in DefaultPlaylist of this figure
_TK_SRP # 1, # 2, # 3, # 4 ... # 8 DPL_TKIN is TKI # 1, # 2, #
3, # 4 ... # 8 is shown, so arrows (1) (2) (3) (4) ...
-As shown in (8), AOB001.SA1 corresponding to TKI # 1 is played first, AOB002.SA1 corresponding to TKI # 2 is played second, and TKI # 3
AOB003.SA1 corresponding to 3rd, AOB00 corresponding to TKI # 4
4. SA1 will be played fourth.

{17-10_41} DefaultPlaylist, PlayList
Information Setting Example FIG. 41 is a diagram showing a setting example of DefaultPlaylist and PlayList information in the same notation as FIG. In the figure, the first square indicates the Default_Playlist information, and the second square indicates the PlayList information. The small frame included in DefaultPlaylist is DefaultPlayli
The eight DPL_TK_SRPs included in the st are shown, and the small frames included in the PlayList information indicate three or four PL_TK_SRPs. TKIN of each DPL_TK_SRP included in Default_Playlist information of this figure
Are the same as those in FIG. However, it is understood that the setting of TKIN of PL_TK_SRP included in the PlayList information is completely different from that of DPL_TK_SRP.

{17-10_42} Correspondence between DPL_TK_SRP and TKI FIG. 42 shows DPL_TK_SRP and TK using the same notation as FIG.
It is a figure which shows the correspondence with I. In FIG. 42, Playlist # 1
Consists of PL_TK_SRP # 1, # 2, # 3. PL_TK_SRP # 1 of these
PL_TKIN is described as # 3, and PL_TK_SRP # 2 PL_TKI
Since N is described as # 1 and PL_TKIN of PL_TK_SRP # 3 is described as # 2, when playing a track using PlayList information # 1, multiple tracks as shown by arrows (11), (12), and (13) AOB is AOB # 3, #
They are played in the order of # 1, # 2.

[0157] Playlist # 2 is composed of PL_TK_SRP # 1, # 2 and # 3. Among these, PL_TKIN of PL_TK_SRP # 1 is described as # 8, and PL_TKIN of PL_TK_SRP # 2, # 3 is described as # 3, # 1, so when playing a track using PlayList information # 2, As shown by arrows (21), (22), and (23), a plurality of AOBs are AOB # 8, #
Playback is performed in the order of 3, # 1, that is, in an order completely different from that of Playlist # 1.

[0158] Playlist # 3 is composed of PL_TK_SRP # 1, # 2, # 3 and # 4. Of these, PL_TKIN of PL_TK_SRP # 1, # 2, # 3, # 4 is # 8, #
Since # 4, # 3, and # 1 are described, when a track is reproduced using PlayList information # 3, AOBs are reproduced in the following reproduction order. First, AOB # 8 constituting TrackE is reproduced as shown by arrow (31), and AOB # 4, AOB # 5, AOB # 6, AOB # 7 constituting TrackD are reproduced as shown by arrow (32). Then it is played back. Then, as indicated by arrows (33) and (34), TrackC and Trac
The playback is performed in the order of AOB # 3 and AOB # 1 constituting kA. Note that if the track is composed of multiple TKIs, the PL_TK_SRP entry contains
The point is that only the first TKI number is described. Specifically, DPL_TK_SRP in Default_Playlist information
Are the four TKIs for TrackD, TKI # 4, TKI # 5, and TK
I # 6 and TKI # 7 were specified, but PL in PlayList information
_TK_SRP does not need to specify those four TKIs. Pla
This means that PL_TK_SRP # 2 of ylist # 3 specifies only TKI # 4 among TKI # 4 to TKI # 7.

On the other hand, DPLI including a plurality of DPL_TK_SRPs is 1
It has a data size that can fit in a sector, and
Resident on. Therefore, when playing each track based on the Playlist, the DPL_T
By referring to K_SRP, each TKI can be searched at high speed. That is, in order to reproduce a TKI (AOB) using the PL_TK_SRP in which only the first TKI number among a plurality of TKIs is described, a RAM is generated based on the TKI described in the PL_TK_SRP.
The DPL_TK_SRP resident above is searched to determine whether or not the track is composed of a plurality of TKIs. Multiple T
If it is composed of KIs, it goes through the procedure of reproducing all the corresponding TKIs (AOBs).

As described above, the PlayListManager contains Defau
If ltPlaylist and a plurality of PlayList information are described, and if different playback orders are described in DPL_TK_SRP and DPL_TKIN and PL_TKIN of PL_TK_SRP,
B are reproduced in different reproduction orders. If reproduced in a completely different reproduction order, the operator can use the flash memory card 31 as if a plurality of music albums were stored.

It should be noted that, of DPL_TK_SRP and TKI, all of which are associated with an AOB file, DPL_TK_
SRP data size is small (only 2 bytes), TKI
Is that the data size is large (sometimes 1024 bytes). Changing the order of the TKIs in the TrackManager causes a lot of access to the flash memory card 31, but changing the order of the DPL_TK_SRP in the Default_Playlist information and the PlayList information does not increase the access to the flash memory card 31 so much. In view of this point, while editing the navigation data, the order of DPL_TK_SRP in the DefaultPlaylist is actively changed according to the editing operation, while the Trac
The order of TKIs in kManager is kept constant regardless of the editing operation.

{17-9_40-2_43A, B} Rearranging the order of DPL_TK_SRP Next, how the editing operation of changing the playback order of tracks by replacing the order of DPL_TK_SRP in the Default_Playlist information will be described.
FIGS. 43A and 43B are diagrams assuming that the order of the tracks is changed. DPL_TK in FIG. 43 (a)
The settings of _SRP and TKI are the same as in FIG. FIG.
In (a), DPL_TKIN in DPL_TK_SRP # 3 is TKI #
3, DPL_TKIN in DPL_TK_SRP # 8 was set to TKI # 8, but in this state, DPL_TK_SRP # 3 enclosed by a thick frame
And the order of DPL_TK_SRP # 8. FIG. 43 (b)
In (1), (2), (3), (4), (5), (6), (7), and (8), the reproduction order of the tracks after the order is changed. With this in mind,
The playback order in FIG. 43 (a) is TrackA, TrackB, Tr
ackC, TrackD, and TrackE, as shown in FIG.
In Default_Playlist information, DPL_TK_SRP # 3, DPL_TK_SRP
Since the order of DPL_TKIN for # 8 has been changed, Tr
Playback is performed in the order of ackA, TrackB, TrackE, TrackD, and TrackC. In this way, by changing the order of DPL_TK_SRP in the Default_Playlist information, the order of playing tracks can be easily changed.

As described above, the editing operation of changing a track is performed. As in the case of TKI, when some tracks are deleted (case 1), a new track is recorded after some tracks are deleted. In the case (case 2), when combining any two of the tracks into one track (case 3), and when dividing one track to obtain two tracks (case 4), DPL_TK_SRP and TKI Describe how it is updated.

{17-9_40-3_44A, B} When deleting tracks First, when some tracks are deleted (case 1)
Will be described. FIGS. 44 (a) and (b) show DPL_TK_SRP # 2 and TKI # 2 of the DefaultPlaylist shown in FIG.
DefaultPlaylist, TrackManager, AOB
FIG. 7 is a diagram showing how a file is updated. FIG. 44 has the same parts as FIG. 27 cited in the description of the deletion of the TKI. That is, the second, third, and fourth stages in FIG. 44 are the same as those in FIG. The difference is that Default_Playlist information including a plurality of DPL_TK_SRPs is described in the first row as in FIG. Track consisting of DPL_TK_SRP # 2 → TKI # 2 (AOB002.SA1) surrounded by a thick frame in FIG.
It is assumed that B has been deleted by the user. In this case, Default_P
DPL_TK_SRP # 2 is deleted in laylist information,
_TK_SRP # 3 to DPL_TK_SRP # 8 are moved up one by one so as to fill the fields occupied by DPL_TK_SRP # 2. Thus, the order of each DPL_TK_SRP is moved up, and the last DPL_TK_SRP # 8 is set to “Unused”. On the other hand, as described with reference to FIGS. 27A and 27B, the TKI is only set to “Unused”, and the TKI # 2 is not moved. AOB002.SA1
Is deleted. For DPL_TK_SRP, the order was advanced, but for TKI, the order was not advanced.
DPL_TKIN in L_TK_SRP has been updated. That is, the DPL_TKIN of the new DPL_TK_SRP # 2 is as shown by the arrow DT11.
Indicates TKI # 3, and DPL_TKIN of DPL_TK_SRP # 3 is arrow D
TKI # 4 as shown in T12, DPL_TKIN of DPL_TK_SRP # 4 is TK
DPL_TKIN of I # 5 and DPL_TK_SRP # 5 indicates TKI # 6, respectively. Furthermore, DPL_TK_SRP # 8 set to "Unused"
DPL_TKIN indicates that TKI # 2 set to “Unused” is set as indicated by arrow DT13.

When a track is deleted, the in-use DPL_TK_SRP is moved to the top, but it is found that the corresponding TKI is set to unused while maintaining the original arrangement. As described above, since the arrangement of the TKI is fixed before and after editing, the processing load associated with the editing process can be reduced. {17-9_40-4_45A, B} Assignment of TKI when recording track Next, a case where a new track is recorded after some tracks have been deleted (case 2) will be described. FIG.
(A), (b) is a diagram showing how an “Unused” TKI and DPL_TK_SRP exist, and when writing a new TKI, DPL_TK_SRP, the writing is performed. In FIGS. 45A and 45B, “Unused”
When the case where a new TKI is assigned to the TKI is described, the TKI has the same portions as those of FIGS. 28A and 28B cited. That is, the second, third, and fourth stages in FIGS. 45A and 45B are the same as the first, second, and third stages in FIGS. 28A and 28B. The difference is that the first DP in FIG.
The point is that Default_Playlist information composed of L_TK_SRP is described. In FIG. 45A, DPL_TK_SRP # 4 to DP
L_TK_SRP # 8 is “Unused”, while TKI # 2, TKI # 4, TKI # 5, TKI # 7, and TKI # 8 are “Uused” as shown in FIG.
nused ”. In TrackManager, "U
Despite the fact that the TKI of "nused" exists in a worm-like manner, De
DPL_TK_SRP of "Unused" is summarized in fault_Playlist information as described above.
This is because DPL_TK_SRP other than “Unused” is carried forward, whereas TKI does not carry such forward.

Here, it is assumed that TrackD composed of four AOBs is to be written. The TKI for each of the four AOBs is written in the TrackManager to each of TKI # 2, TKI # 4, TKI # 7, and TKI # 8 set to "Unused". On the other hand, DPL_TK for these four AOBs
_SRP is DPL_TK_SRP # 4 ~ in Default_Playlist information.
Written to DPL_TK_SRP # 7. Since these four AOBs constitute one track, DPL_TK_ATR for DPL_TK_SRP # 4 is "Head_of_Track" and DPL_TK_SRP # 5, DPL_TK_SRP # 5
DPL_TK_ATR for PL_TK_SRP # 6 is “Midpoint_of_Tra
ck) and DPL_TK_ATR for DPL_TK_SRP # 7 is `` End_of
_Track ”is set.

DPL_TKIN for DPL_TK_SRP # 4 is
TKI # 2 is set and DPL_TKIN for DPL_TK_SRP # 5 is T
DPL_TKIN for KI # 4, DPL_TK_SRP # 6 is TKI # 7, DPL_T
DPL_TKIN for K_SRP # 7 is set to TKI # 8.
With the above DPL_TKIN and DPL_TK_ATR settings, TKI #
2, TKI # 4, TKI # 7, and TKI # 8 are managed as the fourth track TrackD.

In the above processing, the writing of “Unused” to the TKI has been performed, but TKI # 1, TKI # 2, TKI # 3,
Regarding KI # 4, no change was made in FIG.
Is the same as {17-9_40-5_46A, B} When combining tracks (case 3) Default_Pla when combining tracks (case 3)
Update of ylist information will be described. FIG. 46 (a),
(B) is a diagram assuming a case where tracks are integrated. This figure has the same parts as those in FIGS. 29A and 29B cited when the TKI integration processing is described. That is, FIG.
The second, third and fourth stages in (a) and (b) are shown in FIG.
9 (a) and 9 (b) are the same as the first and second stages. The difference is that in FIGS. 46 (a) and (b), Default_
Playlist information is described and DPL_TK included in it
_SRP # 8 is set to "Unused", and
d ”has a correspondence with TKI # 2 set in“ d ”. In this figure, when the track integration processing as shown in FIG. 29 is performed on the AOB file and the TKI,
Shift the contents of DPL_TK_SRP # 3 to DPL_TK_SRP # 6 one by one, and replace the description contents of DPL_TK_SRP # 7 enclosed by a thick frame with DPL_TK_SRP
Copy to # 3. For TKI, the same update processing as in the case shown in FIG. 29 is performed.

{17-9_40-6_47A, B} Track division (case
4) When the track is divided (case 4), the Default_Pla
Update of ylist information will be described. FIG. 47 (a),
(B) is a diagram assuming a case where a track is divided. This drawing has the same portions as those in FIGS. 33A and 33B cited when describing the division processing for TKI. That is, the second stage and the third stage in FIG.
It is the same as the first stage and the second stage in (a) and (b). The difference is that in FIGS. 47 (a) and (b), Default_Pl
aylist information is described and DPL_TK_S included in it
RP # 8 is set to "Unused" and also "Unused"
This is a point that has a correspondence with TKI # 2 set in the TKI # 2. In this state, as in the case of FIG. 33, if TKI # 3 and AOB003.SA1 surrounded by a thick frame are to be divided into two,
The order of DPL_TK_SRP # 3 to DPL_TK_SRP # 7 is moved down one by one, and DPL_TK of "Unused" in Default_Playlist information
Move _SRP to DPL_TK_SRP # 3. DPL_TK_SRP after moving
TKI # 2 obtained by the division is associated with # 3. T
AOB002.SA1 associated with KI # 2 is originally AOB003.S
Although the latter part of A1 is stored, DPL_TK_SRP # 2 exists before DPL_TK_SRP # 3 corresponding to TKI # 2, and this DPL_TK_SRP # 2 corresponds to TKI # 2-AOB002.SA1. It is attached. That is, AOB002.SA1 and AOB003.SA1 store the latter half and the former half of the original AOB003.SA1,
DPL_TK_SRP # 2 and DPL_TK_SRP # 3 that specify these are
Since the playback order is set to play these AOB files in the order of AOB003.SA1, AOB002.SA1, the original AO
The latter part and the former part of B003.SA1 are reproduced in the order of the former part and the latter part according to the reproduction order specification of DPL_TK_SRP.

{17-9_40-8} Application of Editing Process By combining the above four editing operations, the operator can perform various editing operations. That is, when a disc jockey announcement is included at the beginning of a certain track, and it is desired to delete the announcement, the announcement division is performed as one track in the above-described track division processing, and then the track is deleted. For example, only the disc jockey announcement can be partially deleted.

The navigation data has been described above.
A reproduction device configured to reproduce presentation data will be described. {48-1} Appearance of playback device FIG. 48 shows a flash memory card 3 according to this embodiment.
FIG. 1 is a diagram showing a portable playback device for No. 1; In the figure, the playback device has an insertion slot into which the flash memory card 31 is inserted, a key panel for receiving key operations such as playback, forward search playback, reverse search playback, fast forward, rewind, and stop from the operator. , A liquid crystal display, and has the same appearance as a normal portable audio device. The key panel includes a Playlist key to accept playlist / track selection, a "| <<key" to accept a skip to the beginning of the track, a ">>|" key to accept a skip to the beginning of the next track, fast forward, and roll. ">>key","<<key" for accepting return, forward search playback, and reverse search playback, and Display key for accepting an operation to display a still image when a still image is stored in the flash memory card 31 It has a Rec key that accepts recording operations from the operator, an Audio key that accepts Stereo / Monoral selection from the operator, a sampling frequency selection from the operator, a Mark key that accepts bookmark designation, an Edit key that accepts track editing, and title input. .

{48-2} Improvements in the portable playback device of the flash memory card 31 The difference between the portable playback device of the flash memory card 31 and the ordinary portable audio device is the following improvements (1) to (1).
(4). That is, the default_Playlist information, P
In order to accept layList information and track designation, the LCD display shall display a list of playlists and tracks (1), and any of the playlists or tracks displayed in such a manner. Key is assigned to specify the file as a playback target or edit target (2), and as the track progresses,
The LCD display shows the elapsed playback time of the track (3), and has a jog dial that is used to set the playback start time when performing a time search function or split editing (4). It is.

{48-2_49_50} Details of Improvement (2) Details of the improvement (2) are as follows. FIG. 49 is a diagram illustrating an example of the display content of the liquid crystal display when a playlist is selected, and FIG. 50 is a diagram illustrating an example of the display content of the liquid crystal display when a track is selected. . "DEFAULTPLAYLIST" and "PLA" in Fig. 49
YLIST # 1, PLAYLIST # 2, PLAYLIST # 3, PLAYLIST #
"4" indicates a default playlist stored in the flash memory card 31 and A indicating four playlists.
An SCII string. Also, “TRAC” in FIG.
K # 1, TRACK # 2, TRACK # 3, TRACK # 4, TRACK # 5
Is an ASCII character string indicating five tracks whose reproduction order is specified in the default playlist stored in the flash memory card 31. 49 and 50
In (a), these hatched play lists and tracks indicate that they are designated as playback targets or editing targets. In this way, a list of tracks whose playback order is defined in the playlist is displayed on the liquid crystal display, and when the TRACK # 1 is designated as a playback target and the >> | key is pressed, FIG. 50 (b) As shown in the table, TRACK # 2 below the plurality of tracks listed is specified as a playback target. When the >> | key is pressed in a state where TRACK # 2 is designated as a playback target, a lower row of the plurality of tracks listed as shown in FIG.
TRACK # 3 is specified as a playback target. When the | << key is pressed in a state where TRACK # 3 is designated as a playback target, TRACK # 2, which is one level higher than the track to be played, is displayed as shown in FIG. Is specified. As described above, any one of the tracks is selected as a reproduction target in response to the pressing of the >> | key or the | << key. When the play key is pressed as shown in (1), the reproduction of the track is started, and when the Edit key is pressed, the track is designated as an edit target.

{48-3_51} Details of improvement (4) Next, details of the improvement (4) will be described. FIG.
It is a figure showing an example of operation of a jog dial. The rotation operation by the operator is received by the jog dial, and the elapsed playback time displayed on the liquid crystal display is increased or decreased according to the rotation amount. For example, as shown in FIG. 51A, it is assumed that the reproduction start time is displayed as “00:00:20” on the liquid crystal display. In this case, as shown in FIG. 51B, assuming that the jog dial is rotated counterclockwise, the reproduction start time is reduced to "00:00:10" according to the amount of rotation. As shown in FIG. 51 (c), if the jog dial is rotated clockwise,
The playback start time increases according to the rotation amount, and becomes "00:00:
30].

The reason for increasing or decreasing the reproduction time is to specify an arbitrary reproduction time in the track. If the jog dial is rotated, an arbitrary reproduction time is specified and the reproduction key is pressed. {Formula 2}
The AOB is reproduced from the position specified according to {Equation 3}. Also, in the division editing, the jog dial is used to fine-tune the division boundary when specifying an arbitrary reproduction start time as the division boundary.

{52-1} Internal Configuration of Playback Apparatus Next, the internal configuration of the playback apparatus will be described. FIG.
FIG. 3 is a diagram showing an internal configuration of a playback device. In the figure, the playback device includes a card connector 1 for connecting a flash memory card 31, a user interface unit 2 connected to a key panel and a jog dial, and a RAM 3
A ROM 4, a liquid crystal display 5 having a playlist, a list display frame for displaying tracks, and a playback elapsed time frame for displaying playback elapsed time, an LCD driver 6 for driving the liquid crystal display, and an AOB file. Different
A descrambler 7 for decrypting the AOB_FRAME using the FileKey, and if the descrambler 7 descrambles the AOB_FRAME, the AOB_FRAME is decrypted by referring to the ADTS header of the AOB_FRAME. AAC decoder 8 for obtaining PCM data, and AAC decoder 8
And a D / A converter 9 for D / A converting PCM data obtained by decoding the data to a speaker via a headphone terminal, and a CPU 10 for performing an integration process in the playback device. As can be seen from this hardware configuration, the present playback device has no new configuration for processing TrackManager and Default_Playlist information. TrackManager, Defa
ult_Playlist information is provided for processing
These are a DPLI resident area 11, a PLI storage area 12, a TKI storage area 13, a FileKey storage area 14, a double buffer 15 secured in the RAM 3, and a reproduction control program and an edit control program stored in the ROM 4.

{52-2} DPLI resident area 11 The DPLI resident area 11 is connected to the card connector 1 and read out from the flash memory card 31 by Default_Play.
This area is reserved to make list information resident. {52_12} PLI storage area 12 The PLI storage area 12 is an area reserved for storing PlayList information selected and reproduced by the operator.

{52-3} TKI storage area 13 The TKI storage area 13 includes a plurality of TKIs included in the TrackManager.
Of the T corresponding to the AOB file to be played,
This area is reserved for storing only KI and has a data size of one TKI. {52-4} FileKey storage area 14 FileKey storage area 14 is AOBSA1.KE in the protection area.
This is an area reserved for storing only the FileKey corresponding to the AOB file to be reproduced among the plurality of FileKeys included in Y.

{52-5} Double buffer 15 The double buffer 15 performs input processing of sequentially inputting and storing cluster data (data stored per cluster) read from the flash memory card 31, and storing AOB_FRAM from encrypted cluster data
This is an input / output buffer used when performing an output process of reading E and sequentially outputting it to the descrambler 7 in parallel. The double buffer 15 sequentially releases the areas occupied by the clusters that have been output as AOB_FRAME into free areas, and secures an area for using the free areas for storing newly read clusters, that is, a ring reservation. A cyclic area is secured using a pointer.

{52-5_53_54A, B} Input / Output in Double Buffer 15 FIG. 53 is a diagram showing how data input / output in double buffer 15 is performed. FIG. 54 (a),
FIG. 3B is a diagram showing how a cyclic area is secured using a ring pointer. In these figures, the arrow pointing to the lower left indicates a pointer for the write destination address of the cluster data, that is, a write destination pointer. The arrow pointing to the upper left indicates a pointer to the read destination address of the cluster data, that is, a read destination pointer. These pointers are used as ring pointers.

{54-6_53} Flash memory card 31
Is connected to the card connector 1, the cluster data in the user data area of the flash memory card 31 is read from the flash memory card 31 as shown by arrows w1 and w2. The read cluster data is stored in the double buffer 15 as the write destination pointers WP1,
The data is sequentially stored at the position indicated by WP2.

{52-7_54A} Of the AOB_FRAMEs included in the cluster data stored in this way, the AOB_FR existing at the position indicated by the read destination pointer
AME is sequentially de-decoded as indicated by arrows r1, r2, r3, r4, r5 ...
Output to the scrambler 7. Here, the cluster data 002 and 003 are stored in the double buffer 15,
When the read destination indicated by the read destination pointer moves as shown in FIG.
Since all the AOB_FRAMEs included in the cluster 002 have been read, a new cluster 004 is read and the area occupied by the cluster 002 is overwritten as indicated by an arrow w6 in FIG.

{52-8_54B} Also, when the read destination indicated by the read destination pointer moves as indicated by and reaches, the AOB_FRAME included in the cluster 003 has been completely read. Read cluster 005 to
As shown by an arrow w7 in FIG. 54B, the area occupied by the cluster 003 is overwritten. AOB_FRAM as above
The output of E and the overwriting of the cluster data are repeated many times, and AOB_FRAME included in the AOB file is sequentially output to the descrambler 7 and the AAC decoder 8.

{52-9_55 to 58} Reproduction Control Program Stored in ROM 4 Next, the reproduction control program stored in ROM 4 will be described. FIG. 55 is a flowchart showing the processing procedure of the AOB file reading processing.
7, FIG. 58 is a flowchart showing the processing procedure of the AOB_FRAME output processing.

{52-9_55-1} In these flowcharts, the variable w is a variable indicating each of the plurality of DPL_TK_SRPs, and the variable z is the respective AOB files, the corresponding TKIs, and the This is a variable for uniquely indicating the AOB to be executed. The variable y is a variable for indicating each AOB_ELEMENT included in the AOB # z indicated by the variable z, and the variable x is an AO indicated by the variable y.
This variable indicates each AOB_FRAME included in B_ELEMENT # y. First, the procedure of the AOB file reading process will be described with reference to FIG.

{52-9_55-2} In step S1, the CPU 1
0 reads out the PlayListManager and sets Default_Playlist
Information and PlayList information are displayed in a list. In step S2, the CPU 10 waits for designation of whether to reproduce the AOB according to the Default_Playlist information or the PlayList information. Here, if Default_Playlist information is specified, the process proceeds from step S2 to step S3 to initialize a variable w (# w ← 1), and in step S4, the DPL_TKIN associated with DPL_TK_SRP # w in the Default_Playlist information Identify the specified TKI # z and TKI only the TKI # z
The data is read out to the storage area 13. Then, in step S5, an AOB file #z having the same number as TKI # z is specified.
With the above procedure, the AOB file to be played is finally specified. The identified AOB file is
Since the AOB file has been encrypted, the processing of steps S6 and S7 is performed to decrypt the AOB file. That is, in step S6, the protection area is accessed, and the AOB file #
Read FileKey # z stored in File Key Entry # z having the same number as z. In step S7, the CPU 10
Sets FileKey # z in the descrambler 7. With this setting, the FileKey is set in the descrambler 7, and thereafter, if the AOB_FRAMEs included in the AOB file are sequentially input to the descrambler 7, the AOB_FRAMEs are sequentially reproduced.

{52-9_55-3} Thereafter, each cluster storing the AOB file is sequentially read. Step S8
Then, the “file first cluster number” for the AOB file #z in the directory entry is specified, and the CPU 10 reads the data stored in the cluster from the flash memory card 31 in step S9. In step S10, it is determined whether or not the cluster number is described as FFF in the FAT value.
If the value is other than FFF, the data stored in the cluster specified by the FAT value is read in step S11. After such reading, the process proceeds to step S10. Here, when data stored in any cluster is read and a FAT value associated with that cluster is referenced, as long as any cluster number other than FFF is described in the FAT value, Steps S10 to S11 are repeatedly performed. As a result, the FA
The clusters indicated by the T value are sequentially read. If the cluster number is described as FFF in the FAT value, all the clusters constituting the AOB file #z have been read out, so that the steps S10 to S
It moves to 12.

{52-9_55-4} In step S12, the CPU
10 determines whether the variable #w matches the total number of DPL_TK_SRP. If they do not match, the process proceeds to step S13, and after incrementing the variable #w (# w ← # w + 1), the process proceeds to step S4. In step S4, Default_Pl
The TKI # z specified by the DPL_TKIN # w of the DPL_TK_SRP # w in the aylist information is specified, and only the TKI # z is read out to the TKI storage area 13. At this time, the TKI used up to that time is stored in the TKI storage area 13, but the CPU 1
0 overwrites the TKI already stored in the TKI storage area 13 using the newly read TKI. Due to such overwriting, only the latest TKI is stored in the TKI storage area 13. When the TKI is overwritten in this way, the processing of steps S5 to S12 is repeated for the AOB file #z. The processing of steps S5 to S12 is repeated, and all the steps included in the Default_Playlist information are
If the TKI and AOB files corresponding to DPL_TK_SRP are read, the variable #w matches the total number of DPL_TK_SRP, step S12 becomes Yes, and this flowchart ends.

{52-9_56_57_58} AOB_FRAME output processing In parallel with the AOB file reading processing, the CPU 10 sets the AOB_FR in accordance with the flowcharts of FIGS. 56, 57 and 58.
Perform AME output processing. Play_ti
me is a variable indicating the elapsed time of reproduction, that is, the reproduction elapsed time, and the time in the time display frame of the liquid crystal display 5 is rewritten in accordance with the update of the play_time. The play_data is the data length reproduced so far.

{52-9_56-1} In step S21, C
The PU 10 monitors whether the cluster data for the AOB file #z has been accumulated in the double buffer 15. Unless cluster data is accumulated, step S21 is repeated. If cluster data is accumulated, #x and #y are initialized in step S22 (# x ← 1, #y
← 1) Then, in step S23, the AOB file
In the cluster for #z, BIT # z included in TKI # z
AOB_FRAM in AOB_ELEMENT # y from Data_Offset onward
Detect E # x. Here, 7 bytes from SZ_DATA are assumed to be occupied by the ADTS header, the ADTS header is referred to, the data length indicated in the ADTS header is analyzed as the audio data of the main unit, and the ADTS header is analyzed. And the audio data of the main unit, and outputs the data to the descrambler 7. If the AOB_FRAME is decrypted by the descrambler 7 and decrypted by the AAC decoder 8, it will be reproduced as audio.

{52-9_56-2} After the detection, in step S24, AOB_FRAME # x is output to the descrambler 7, and in step S25, the playback elapsed time play_time is set to AOB_F.
The playback time corresponding to RAME # x is incremented, and the number of played data play_data is incremented by the number of data corresponding to AOB_FRAME # x. Here, since the playback time length of AOB_FRAME is 20 msec, 20 msec is added to the playback elapsed time play_time.

If the first AOB_FRAME is output to the descrambler 7, the AOB of the AOB_FRAME # x is
Referring to the DTS header, it specifies where the next AOB_FRAME exists. In step S27, the variable #x is incremented (# x ← # x + 1), and the next AOB_FRAME is changed to AOB_FRAME.
#x. In step S28, AOB_FRAME # x is input to the descrambler 7. Then, in step S29, play_time is incremented by the reproduction time corresponding to AOB_FRAME # x, and play_data is incremented by the number of data corresponding to AOB_FRAME # x. AOB_FRAME #
After incrementing x, in step S30 the CPU
10 judges whether #x has reached “FNs_1st_TMSRTE”. If #x does not reach "FNs_1st_TMSRTE", in step S31, it is determined whether any key other than the Play key has been pressed, and then the process proceeds to step S26. After that, until #x reaches “FNs_1st_TMSRTE” or Pl
Steps S26 to S26 until a key other than the ay key is pressed.
The process of step S31 is repeatedly performed. Play here
When a key other than the key is pressed, the process of this flowchart ends, and a process corresponding to the pressed key is performed. If the pressed key is the stop key, the reproduction process is stopped, and if the pressed key is the pause key, the reproduction is paused.

{52-9_57-1} On the other hand, #x is "FNs_1st_TMSRT
If "E" has been reached, step S30 becomes Yes and FIG.
The process moves to step S32. In the process from step S26 to step S30, all AOB_FRAMEs included in the AOB_ELEMENT have been input to the descrambler 7,
Step S to shift the processing target to the next AOB_ELEMENT
At # 32, #y is incremented and #x is initialized (# y ← # y + 1, # x ← 1).

Thereafter, in step S33, TKTMSRT
And calculate the start address of AOB_ELEMENT # y. Thereafter, a process including steps S34 to S42 is performed. It can be said that the processing of steps S34 to S42 is the same as the processing of steps S24 to S31 in that AOB_FRAME included in AOB_ELEMENT is read out one after another. The difference from the processing of step S24 to step S31 is that the end condition of the loop process in the latter is that #x reaches “FNs_1st_TMSRTE”, whereas the end condition of the loop process in the former is that “#N is“ FNs_Middle_TMSRTE ”. Is reached. #
x reaches “FNs_Middle_TMSRTE”, and step S34 to
When the loop processing including step S42 ends, step S41 becomes Yes and the process moves to step S43.
In step S43, the CPU 10 increments #y and initializes #x (# y ← # y + 1, # x ← 1). Thereafter, in step S44, the variable y is set to TMSRT_ of TKI # z.
It is determined whether a value equal to (TotalTMSRT_entry_Number-1) in the Header has been reached. #y is (TotalTMSRT_entry_Numb
er-1), AOB_ELEMENT # y is still the last AO
Since B_ELEMENT has not been reached, the process proceeds from step S44 to step S32, and the process proceeds to step S3.
Steps S2 to S42 are continuously performed. #y is (Total
TMSRT_entry_Number-1), the last AOB_ELEME
It is considered that the reading process of the AOB_FRAME has been completed up to the AOB_ELEMENT immediately before the NT, so the step S44 is YES.
Then, the flow shifts to step S45 in FIG.

{52-9_57-2} The processing from step S45 to step S54 is performed for a plurality of As contained in the last AOB_ELEMENT.
It can be said that the processing is the same as the processing in steps S33 to S42 described above in that the processing is to read OB_FRAME respectively. The difference is that the loop processing in steps S33 to S42 differs from the loop processing in step S41.
While #x reached “FNs_Middle_TMSRTE” was the condition for terminating the loop processing, in step S53,
The fact that #x is "FNs_Last_TMSRTE" and that Play_data indicating the data size read so far reaches SZ_DATA is the condition for ending the loop processing.

Until the condition of step S53 is satisfied, the processing of steps S49 to S54 is repeatedly performed, and if this condition is satisfied, step S53 returns to Ye.
In step s, the process proceeds to step S55. Step S5
In step 5, the CPU 10 increments #z and proceeds to step S21 (# z ← # z + 1), and waits for the next AOB file to be stored in the double buffer 15. If accumulated, the process proceeds from step S21 to step S22,
The processing of steps S22 to S54 is repeated for the next AOB file. That is, the next DPL_TK_SRP
Specify the TKI specified by DPL_TKIN, and AOB file corresponding to the TKI, that is, AO with the same number as TKI
Identify the B file. Then, access the protected area, specify the FileKey having the same number as the TKI in the encryption key storage file, read the FileKey, set the FileKey in the descrambler, and then set the same number as the TKI. AOB_FR included in AOB file with
AME is read out and played back sequentially.

{52-9_57-3_59} Update of Playback Elapsed Time FIG. 59 is a diagram showing how the playback elapsed time displayed in the time display frame of the liquid crystal display 5 increases as the variable Play_Time is updated. is there. In this figure (a), the playback elapsed time is 00: 00: 00.000, but when the playback of AOB_FRAME # 1 ends, the playback elapsed time indicates the time length of AOB_FRAME2.
0msec is added and updated to 00: 00: 00.020. AOB
At the time when the playback of _FRAME # 2 ends, AOB_
AOB of 00: 00: 00.040 is added to the time length of 20msec of FRAME, and AOB
When playback of _FRAME # 6 ends, the playback elapsed time is 00: 0
It turns out that it is 0: 00.120.

The whole of the AOB_FRAME output processing has been described above.
As described above, in step S31 of this flowchart, when a key other than the Play key is pressed, the processing of this flowchart is interrupted as described above, and there is a pause key and a stop key as such keys other than the Play key. Has already been explained, but in addition to the pause and stop keys,
Even when a key for causing the playback apparatus to perform the trick play is pressed, the processing of the flowcharts in FIGS. 56, 57, and 58 is interrupted, and the processing corresponding to the pressed key is executed. Thereafter, the time search function is executed by operating the jog dial after the >> key is pressed and the forward search playback is executed and the jog dial is operated after the pause key or the stop key is pressed. CPU when
The ten processing procedures will be described.

{52-10_60} Forward Search Reproduction FIG. 60 is a flowchart showing a processing procedure of the CPU 10 when performing forward search reproduction. The >> key is depressed by the operator, and step S3 in FIGS.
1. This flowchart is executed by the CPU 10 when the results of steps 1, 42 and 54 are YES.

In step S61, the CPU 10 sets AOB_E
From AOB_FRAME # x of LEMENT # y to x + f (t) -1 are input to the descrambler 7. Here, “t” is the intermittent playback time, and f (t) is the number of frames corresponding to the intermittent playback time, d
Assuming that (t) is the number of data corresponding to the intermittent playback time, in step S62, play_time indicating the elapsed playback time and play_data indicating the number of played data are replaced by t: intermittent playback time, f
(t): Update based on the number of frames corresponding to the intermittent playback time, d (t): Update based on the number of data corresponding to the intermittent playback time (x ← x + f
(t), play_time ← play_time + t, play_data ← play_data +
d (t) Generally, the intermittent playback time is 240 milliseconds (12 AOB_
FRAME playback time length). ).

{52-10_60-1_61A, B} FIG. 61 (a)
(B) is a diagram showing a state in which the reproduction elapsed time is incremented during forward search reproduction. FIG.
1 (a) indicates the initial state of the playback elapsed time, and indicates that the playback point is AOB_FRAME # 1 of AOB_ELEMENT # 51.
It can be seen that the playback elapsed time in this case is 00: 00: 01.000. Here, the first to twelfth AOB_FRAMEs are input to the descrambler 7 as the intermittent playback time,
When 240 milliseconds, which is the time length of 1AOB_FRAME, is added to the playback elapsed time, the playback elapsed time becomes 00: 00: 01.240 as shown in FIG. 61 (b).

{52-10_60-2} After updating these, in step S63, the CPU 10
Compare the size of _FRAME # x with the total number of frames of AOB_ELEMENT # y, and find that AOB_FRAME # x after increment is
Determine if it exists in #y. Specifically, the number of frames of AOB_ELEMENT located at the beginning of AOB is “FNs_1st_TMSRT
E '' and the number of frames in the middle is `` FNs_Middle_TM
SRTE ", and the last frame number is" FNs_Last_TMSRT "
E ”, the determination is made by comparing these with AOB_FRAME # x. If AOB_FRAME # x after update
If does not exist in AOB_ELEMENT, step S64
It is determined whether there is an AOB_ELEMENT following AOB_ELEMENT # y in. Where AOB_ELEMENT # y is the last AOB_ELE
MENT, and if there is no following AOB_ELEMENT,
Step S64 results in No, and the process of this flowchart ends. However, if there is a subsequent AOB_ELEMENT, in step S65, AOB_FRAME # x to AOB_ELEMENT # y
In step S66, and #y in step S66.
Is updated (y ← y + 1) to convert the AOB_FRAME # x into the frame position of the AOB_FRAME in the subsequent AOB_ELEMENT # y. If the updated AOB_FRAME # x exists in the AOB_ELEMENT, these steps S65 to S6
Skip to step S67 and proceed to step S67.

{52-10_60-3} Subsequently, AOB_FRAME # x, playback elapsed time play_time, and the number of played data play_data are updated according to the intermittent skip interval. Here, the time corresponding to the intermittent skip interval is skip_time (2 seconds), and the number of frames corresponding to the intermittent skip interval skip_time is f (skip_
time), the number of data equivalent to the intermittent skip interval skip_time
If d (skip_time) is set, in step S67, AOB_FRAME # x, playback elapsed time play_time, and played data count play_data are updated using these (x ← x + f (skip_tim
e), play_time ← play_time + skip_time, play_data ← play_
data + d (skip_time)).

{52-10_60-4_61C} As shown in FIG. 61 (c), AOB_FRAM indicating the frame position in AOB_ELEMENT # 51
It is assumed that the intermittent skip interval is added to E # x. If #x after this addition exceeds the number of frames of AOB_ELEMENT # 51, AO
AOB_FRAME # x is converted to a frame position in AOB_ELEMENT # 52 by updating B_ELEMENT to the next AOB_ELEMENT and subtracting the number of frames of AOB_ELEMENT # 51 from #x after addition. In this case, AOB_ELEMENT # y is AOB_ELE
MENT # 52, and the playback elapsed time is 2.000 at 00: 00: 01.240
Is added to obtain 00: 00: 03.240. AOB_FRAM
E # x is AOB_FRAME # 62 in AOB_ELEMENT # 52 (= (3240ms
ec-2000msec) / 20msec).

{52-10_60-5_61 (d)} Thereafter, AOB_ELEMEN
If AOB_FRAME # 62 in T # 52 is input to the descrambler 7, the playback elapsed time becomes as shown in FIG.
By adding 0.240 to 00: 00: 03.240, 00:00:03.
It will be 480. If the update according to the intermittent skip time is performed in step S67, steps S68 to S
Step 71 is performed. This step S68 to step S7
The processing of 1 is the same as the processing of steps S63 to S66, and it is determined whether or not the AOB_FRAME after adding the number of frames corresponding to the intermittent skip interval skip_time exists in the AOB_ELEMENT # y. If so, set the next AOB_ELEMENT to AOB_ELEMENT # y and AOB_FR
Converts AME # x to a new AOB_ELEMENT # y frame position.

If AOB_FRAME # x and AOB_ELEMENT # y are incremented according to the intermittent playback time and the intermittent skip time, in step S72, the CPU 10 proceeds to TTKMSRT.
The AOB_FRAME # x is detected by calculating the start address of the AOB_ELEMENT # y by referring to FIG. 4 and starting the search of the ADTS header from the start address in the AOB_ELEMENT # y in step S73. Then, Step S74
In step S61, it is determined whether a key other than the forward skip key has been pressed.
From AOB_FRAME # x of ENT # y to x + f (t) -1 are input to the descrambler 7, and the processes of steps S62 to S73 are repeated.

In the above processing, AOB_FRAME # x, AOB_ELEME
NT # y is incremented, and the playback position advances.
Thereafter, if the reproduction key is pressed by the operator, step S74 is No, and the processing of this flowchart ends. {52-11} Execution of time search function The processing when the time search function is executed will be described. A list of tracks in the Default_Playlist information is displayed, and designation of an arbitrary track is accepted. When a track is specified and the jog dial is operated, the reproduction start time is updated. When the play key is pressed after the play start time has increased or decreased, the time specified for that play
(Seconds). On the other hand, if the specified track is
It is determined whether it consists of B or a single AOB. single
AOB_ELEMENT # y that satisfies {Formula 2} if it consists of AOBs
And AOB_FRAME # x. AOB that satisfies {Formula 2}
If _ELEMENT # y and AOB_FRAME # x are calculated, in the TKTMSRT corresponding to this AOB, from the address located at y + 2, start searching for AOB_FRAME # x, and if x-th AOB_FRAME is searched, this Playback starts from the x-th AOB_FRAME.

{52-12} When a plurality of AOBs are included, AOB # n, AOB_ELEMENT # y, and AOB_FRAME # x that satisfy {Equation 3} are calculated. AOB # n, AOB_ELEMENT # satisfying {Formula 3}
y, if AOB_FRAME # x is calculated, T corresponding to this AOB # n
In KTMSRT, AOB starts from the address located at y + 2
The search for _FRAME # x is started, and when the x-th AOB_FRAME is searched, the reproduction is started from the x-th AOB_FRAME.

Subsequently, FNs_1st_TMSRTE in BIT is 80 frames, FNs_Last_TMSRTE is 50 frames, and FNs_Mid
A case in which reproduction is started from an arbitrary reproduction time in an AOB in which dle_TMSRTE is 94 frames will be described. {52-13_62A, B} Here, as a specific example of the case where the time search function is performed, the AOB_ELEMENT to start playback when the playback start time is specified by the jog dial,
A description will be given of how to specify a frame position at which reproduction is to be started. FIG. 62 is a diagram showing a specific example when the time search function is performed. Here, FIG.
As shown in the figure, in the state where the playback device is gripped and a certain AOB is designated as a playback target, with the right thumb,
The jog dial is rotated, and playback start time = 0
It is assumed that 0: 04: 40.000 (= 280.00sec) is specified. If the BIT in the TKI for this AOB has the content shown in FIG. 62B, the reproduction start time = 00: 04: 40.000 (= 280.00 sec)
Is applied to {Equation 2}, 280 sec = (FNs_1st_TMSRTE + FNs_middle_TMSRTE · y + x) × 20 msec = (80 + 94 · 148 + 8) × 20 msec, so that AOB_ELEMENT # y, AOB_F
As RAME # x, AOB_FRAME of y = 148, x = 8 is obtained.

Since y = 148 is specified as above, the entry address of y + 2nd AOB_ELEMENT # 150 (= 148 + 2) is set to T.
From the KTMSRT, from the eighth AOB_FRAME from here,
When playback starts, playback elapsed time = 00: 04: 40.000 (= 280.
00sec), the reproduction can be started. When the Play key is pressed over {52-14_63_64_65},
The description of the processing contents of the CPU 10 is finished. Next, the editing control program stored in the ROM will be described. This editing control program is executed when the Edit key is pressed, and FIG. 63, FIG. 64, and FIG. 65 show the processing procedure. Hereinafter, the processing content of the editing control program will be described with reference to these flowcharts.

{52-14_63-1} Edit control program When the Edit key is pressed, a dialogue for presenting to the operator which of typical edit operations such as deletion, division, and integration is to be performed in step S101 in FIG. The screen is displayed, and thereafter, in step S102, it is determined whether or not processing for the interactive screen has been designated. Here, in the operation of the interactive screen, the >> | key and the | << key are used as keys for receiving the up / down cursor operation, ie, up / down cursor keys. When the deletion process is specified, the process proceeds to a loop process including steps S103 and S104. In step S103, it is determined whether the >> | key or | << key has been pressed, and in step S104, it is determined whether the edit key has been pressed. If the >> |, | << keys are pressed, the process moves from step S103 to step S105, and the designated track is designated as an editing target. On the other hand, if the edit key is pressed, it is determined that the track to be deleted is specified, and the processing shown in FIG. 44 is performed, and the TKI_BLK_ATR of the TKI for the specified track is set to "Unus
ed ”to delete the specified track.

{52-14_63-2} Integrated Editing Processing When integrated editing is specified, the flow shifts from step S102 to a loop processing consisting of steps S107 to S109. In the loop processing including steps S107 to S109, the press of the >> | key, the | << key, and the press of the edit key are accepted. If the >> ||, | << keys are pressed, the process moves from step S107 to step S110, and the designated track is highlighted. If the edit key is pressed, step S108 is Yes
And the process moves to step S111. Step S11
In step 1, the track designated by the cursor key is designated as an edit target, and the process again proceeds to the loop processing including steps S107 to S109.

When the editing target of the second track is specified,
Step S109 becomes Yes, and it moves to step S112. In step S112, the preceding track,
By referring to the TKI BIT for the following track, the AOB located at the end and the beginning of both tracks
(If AOBs are also placed before and after, A
It is determined whether the type of (OB) is Type1 or Type2.

If the type of each AOB has been determined, it is determined in step S113 which of the arrangement patterns shown in the arrangement image of each type of AOB corresponds. It corresponds to any of the arrangement patterns in FIGS.
If it is clear that three Type2AOBs do not continue even after the integration, the preceding track and the subsequent track are integrated into one track in step S115. That is, the operation shown in FIG. 46 is performed on the TKI and DPL_TK_SRP associated with these, and the TKI_BLK_ATR of the TKI is rewritten to integrate the plurality of tracks selected as the operation target into one track. FIG.
If none of the arrangement patterns (a) to (d) applies and three AOBs of Type 2 continue after integration, there is a possibility that underflow may occur in the integrated track in step S114. Is displayed and the integration process is interrupted.

{52-14_64-1} Track division processing When a track division is specified, the flow shifts from step S102 to a loop processing consisting of steps S116 to S117. In the loop processing including steps S116 to S117, the press of the >> | key, the | << key, and the press of the edit key are accepted. If the >> ||, | << keys are pressed, the process moves from step S116 to step S118, and the designated track is designated as an editing target.
If the edit key is depressed, step S117 becomes Yes and the process moves to step S119. In step S119, the track designated by the cursor key is designated as an edit target. Thereafter, in step S120, reproduction of the track designated to be divided is started, and in step S1
At 21, the press of the Mark key is accepted. When the Mark key is pressed, the reproduction of the track is temporarily stopped, and the process proceeds to a loop process including steps S122 to S123. In step S122, a rotation operation on the jog dial is received, and when the rotation operation is performed on the jog dial, the reproduction start time is increased or decreased in step S124 according to the rotation operation. After that, the process returns to the loop process including steps S122 to S123. If the edit key is pressed in a state where the reproduction start time is increased or decreased by the rotation operation, step S123 is performed.
Then, the process shifts to step S125, and in step S125, the reproduction time during which the edit key is pressed is designated as a division boundary (note that an undo function (cancellation of editing) is possible when designating the division boundary). Thereafter, in step S126, the processing described in FIG.
Tracks are divided by updating LI and TKI.

{52-14_65-1} Playlist Setting / Editing Process When the playlist setting / editing is designated, the flow shifts to the flowchart in FIG. Variables in this flowchart
k is a variable for designating each track whose reproduction order is defined by a playlist to be set. In the flowchart of FIG.
After setting this variable k to 1 in 131, step S
The process proceeds to a loop process including 132 to S134. In the loop processing including steps S132 to S134, the press of the >> | key, the | << key, the press of the edit key, and the press of the stop key are accepted. If the >> | key or the | << key is pressed, steps S132 to S1 are performed.
35, the track designated by the >> | and | << keys is designated. If the edit key is pressed, step S133 becomes Yes and the process moves to step S136.
In step S136, the track specified by the edit key is specified as the k-th track to be reproduced. Thereafter, in step S137, the variable k is incremented, and the process proceeds from step S132 to step S134.
Move to the loop processing. By repeating such processing, the second, third, and fourth tracks are sequentially specified. When the stop key is pressed in a state where a plurality of tracks to be reproduced in the newly created playlist are specified in this way, the process proceeds from step S134 to step S138, and the corresponding items are associated with these. PlayLi consisting of PL_TK_SRP that identifies the failed TKI
Generate st information.

(Recording Apparatus) {66-1} Recording Apparatus Next, an example of the recording apparatus of the flash memory card 31 will be described. FIG. 66 is a diagram illustrating an example of a recording device of the flash memory card 31. The recording device in the figure can communicate via the Internet, and when the SD_Audio directory is transmitted via a communication line in an encrypted state by electronic music distribution,
Alternatively, it is a general-purpose personal computer that can receive audio data transport streams when they are distributed by electronic music distribution.

{67-1} Hardware Configuration of Recording Apparatus FIG. 67 is a diagram showing a hardware configuration of the recording apparatus. In the figure, a recording device includes a card connector 21 for connecting a flash memory card 31 and a RAM 22.
A fixed disk device 23 storing a recording control program for performing integrated control of the recording device, an A / D converter 24 for A / D converting audio input from a microphone to obtain PCM data, ACC encoder 25 that obtains AOB_FRAME by encoding PCM data per unit and adding an ADTS header, and a FileKey for each AOB file.
A scramble unit 26 for encrypting AOB_FRAME using
When the SD_Audio directory is transmitted via the communication line in an encrypted state by electronic music distribution,
Alternatively, when an audio data transport stream is transmitted via a communication line by electronic music distribution, a modem device 27 that receives the audio data transport stream and a CP that performs integrated control in the recording device
U28 and keyboard 2 that accepts operations from the operator
9 and a display 30.

{67-2} Input Paths RT1 to RT4 When the SD_Audio directory to be written to the data area and the protection area by electronic music distribution is transmitted via a communication line in an encrypted state, the recording apparatus performs these operations. May be written to the data area and the protection area of the flash memory card 31 at the time when it is properly received. However, when the audio data transport stream itself is transmitted by electronic music distribution instead of the SD_Audio directory, or when input to the recording device in the form of PCM data, it is input to the recording device in the original sound state. If the recording device comes,
The audio data transport stream is written to the flash memory card 31 via two input paths.

[0220] When the recording apparatus in this figure stores the audio data transport stream in the flash memory card 31, the input path of the audio data transport stream includes an input path RT1 shown in FIG.
There are an input path RT2, an input path RT3, and an input path RT4. {67-3} Input path RT1 The input path RT1 is used when the SD_Audio directory is transmitted via the communication line in a state where the SD_Audio directory is encrypted by electronic music distribution, or when the audio data transport stream is transmitted via the communication line. AOB_FRAME included in the transport stream is different for each one belonging to one AOB.
It is encrypted using FileKey. Since there is no need to re-encrypt and re-encode the encrypted transport stream, the SD_Audio directory or the audio data transport stream is stored in the RAM 22 in an encrypted state.

{67-4} Input Path RT2 The input path RT2 is an input path when voice is input from a microphone. In this case, PCM data is obtained by causing the A / D converter 24 to perform A / D conversion on the sound input from the microphone. By causing the AAC encoder 25 to encode the PCM data and adding an ADTS header,
Get AOB_FRAME. After that, each AOB is
The AOB_FRAME is encrypted using the FileKey for each file to obtain encrypted audio data. After that, the audio data is stored in the RAM 22.

{67-5} Input Path RT3 The input path RT3 is an input path when PCM data read from a CD is input to the device. Since the PCM data is input in the state of PCM data, the PCM data
Input to the AC encoder 25. Entered as such
AOB_FRAME is obtained by causing the AAC encoder 25 to encode PCM data and adding an ADTS header. Then, the Fil for each AOB_FRAME is stored in the scramble unit 26.
AOB_FRAME is encrypted using the eKey to obtain encrypted audio data. Thereafter, the audio data is stored in the RAM 22.

{67-6} Input Path RT4 The input path RT4 is an input path for writing the transport stream input through the three input paths RT1, RT2, and RT3 to the flash memory card 31. With the storage of such audio data, TKI, Default_Playlist
Information is generated. As in the case of the reproducing apparatus, the functional entity of the recording apparatus is also a recording program recorded in the ROM. That is, AOB recording, TrackManager, PlayListM
The processing unique to the present embodiment, such as the recording of an anger, is realized by a recording program recorded on a fixed disk device.

{67-7_68} Processing procedure of recording processing Hereinafter, the input path RT
A description will be given of a processing procedure of a recording process when writing a transport stream to the flash memory card 31 in 1, RT2, RT3, and RT4. FIG. 68 is a flowchart showing the procedure of the recording process. The variables quoted in this flowchart are Frame_Number, Data_S
There is something like ize. Frame_Number is A
Data_Size is a variable for managing the total number of AOB_FRAMEs recorded in the OB file, and Data_Size is a variable for managing the data size of AOB_FRAME recorded in the AOB file so far.

When this flowchart is executed, in step S200, the CPU 28 sets the DefaultPlaylist, Track
Manager is created, and in step S201, variables #z,
Initialize #w (z ← 1, w ← 1). In step S202, an AOB file #z is created and stored in the data area of the flash memory card 31. In this state, the file name, the file extension, and the first cluster number of the AOB file #z are set in the directory entry of the SD_Audio directory in the data area.
In subsequent step S203, CPU creates TKI # z and stores it in TrackManager. In step S204, CPU creates DPL_TK_SRP # w and creates DefaultPlaylist.
Store in information. Thereafter, in step S205, the variable #y
Is initialized (y ← 1), and in step S206, Fram
Initialize each of e_Number and Data_Size (Frame_N
umber ← 0, Data_Size ← 0).

At step S207, the CPU 28 sets the AOB
It is determined whether the input of the audio data transport stream to be written to the file #z has been completed. AAC
Encoded by an encoder 25 and a scrambler 26
If the audio data transport stream encrypted according to is stored in the RAM 22 one after another and it is necessary to continue writing the cluster data, step S207 becomes No and the process moves to step S209. In step S209, the CPU 28 determines that
It is determined whether the AC audio data has been stored in the RAM 22. If the cluster data is stored in the RAM 22, step S209 becomes Yes, the process proceeds to step S210, and the AAC audio data of the cluster size stored in the RAM 22 is written to the flash memory card 31, and then the process proceeds to step S211. If the accumulation of the cluster data has not been completed, step S210 is skipped and the process proceeds to step S211. In step S211, the CPU 28 increments Frame_Number (Frame_Number).
Number ← Frame_Number + 1), Data_Size is AOB_FRAME
Is incremented by the data size of. After performing such an update, in step S212, Frame_Number is
It is determined whether or not the number of frames defined as “FNs_Middle_TMSRTE” has been reached. Here, "FNs_Middle_TMSRT
E '' is a value corresponding to the sampling frequency when the audio data transport stream is encoded. Step S212 is No, and step S20
Move to 7. Hereinafter, step S207, step S2
Steps S207 to S207 until 12 becomes Yes.
Step 212 is repeated.

If the Frame_Number has reached “FNs_Middle_TMSRTE” and the result of step S212 is “Yes”, the process shifts from step S212 to step S213 to set Data_Size to A.
TKI # z TK as TMSRT_entry # y for OB_ELEMENT # y
After storing the value in TMSRT and incrementing #y in step S214 (y ← y + 1), it is determined in step S215 whether or not the variable y has reached 252. Here, the value of 252 is a value indicating the total number of AOB_ELEMENTs that can be stored in one AOB, and if the variable y does not reach 252, step S2
Move to 16. In step S216, it is determined whether or not the silent state has continued for a predetermined time or longer, and whether the audio data has reached the boundary between tracks. If there is no silent state, the processing of steps S206 to S215 is repeated. If the variable y has reached 252, or if the silent state has continued for a predetermined time or longer, step S215,
Either step S216 becomes Yes, and the process proceeds to step S217 to increment the variables #z, #w (z ← z + 1, w ← w + 1). Then incremented #z
, The processes of steps S202 to S216 are repeatedly performed. By such repetition, multiple AOB_EL
AOBs including the EMENT are written to the flash memory card 31 one after another.

Here, when the transmission of the audio data transport stream from the AAC encoder 25, the scramble unit 26, and the modem device 27 is completed, the input of the audio data transport stream to be written into the AOB file #z is completed. , So that the result of step S207 is Yes, and the routine goes to step S208. In step S208, the CPU 28 sets Data_Size
T of TKI # z as TMSRT_entry # y for AOB_ELEMENT # y
After the audio data stored in the KTMSRT and the audio data stored in the RAM 22 are stored in the AOB file corresponding to AOB # z, the processing of this flowchart ends.

By the above processing, the encrypted audio data transport stream is stored in the flash memory card 31, and the FileKey for decrypting the encryption is protected in the protected area by the following processing. Is stored in In the case of the input paths RT2 and RT3, each time encoding of one AOB is started, the CPU 28
leKey is generated and set in the scramble unit 26, and the F
The scramble unit 26 is caused to perform encryption using the ileKey, and these FileKeys are stored after the FileKey Entry of the encryption key storage file existing in the protected area.

On the other hand, in the case of the input route RT1, an AOB file,
File storing TKMG, file storing PLMG, AO
An encryption key storage file that stores a different FileKey for each B
Sent from an electronic music distribution provider. CPU28
Receives the AOB file, the file storing the TKMG, and the file storing the PLMG in the user data area, and writes the encryption key storage file storing the different FileKey for each AOB in the protection area.

As described above, according to the present embodiment, since the files storing the AOBs are encrypted with different encryption keys, the encryption key used for encrypting one file is decrypted. AOB that can be decrypted by decryption even if it is exposed is stored in one file
Only AOBs have no effect on AOBs stored in other files. Loss when the encryption key is exposed can be minimized.

The above embodiment has been described only as an example of a system in which the best effects can be expected at present. The present invention can be implemented and changed without departing from the gist thereof. Specifically, the following changes (a) to (f) can be made. (A) In the present embodiment, the recording medium has been described as a semiconductor memory (flash memory card), but the present invention is not limited to this, and an optical disk such as a DVD-RAM or a hard disk can be used.

(B) In the present embodiment, AAC is used as music data. However, the present invention is not limited to this.
(MPEG 1 Audio Layer 3), Dolby-AC3, DTS (Digital
Theater System). (C) Instead of distributing the file containing TKMG and the file containing PLMG by electronic music distribution,
The source information of the TKMG, PLMG is distributed together with the AOB file and the encryption key storage file storing the different encryption keys for each AOB, and the recording device processes the information which is the source of the TKMG, PLMG, thereby processing the TKMG, PLMG. PLMG may be obtained and recorded on a flash memory card.

(D) For convenience of explanation, the recording device and the reproducing device are separately provided. However, the portable reproducing device may have the function of the recording device, or the personal computer type recording device may have the function of the reproducing device. May be provided. In addition to the portable playback device and the personal computer-type recording device, a communication device capable of downloading content from a network may be provided with the functions of the playback device and the recording device. For example, a portable telephone that can access the Internet is provided with the functions of the playback device and the recording device described in the first embodiment, and the content downloaded by the portable telephone via the wireless network is included in the first embodiment. As shown, it may be stored in the flash memory card 31. Further, in the present embodiment, the recording device has a modem device 27 for connection to the Internet, but instead may have a terminal adapter or the like for connecting to an ISDN line. Good.

(E) FIGS. 55-58, 60, 63-
The procedure and the like described with reference to the flowcharts of FIGS. 65 and 68 may be realized by an executable program, and may be recorded on a recording medium to be distributed and sold. Such a recording medium includes an IC card, an optical disk, a floppy (registered trademark) disk, and the like, and the machine language program recorded on these is used by being installed in a general-purpose computer. The general-purpose computer sequentially executes the installed executable programs to realize the functions of the reproducing device and the recording device described in the present embodiment.

(F) In this embodiment, a plurality of AOBs and a plurality of FileKeys are stored in the flash memory card 31, but one AOB and one
And two FileKeys. Alternatively, the AAC AOB may be stored in the flash memory card 31 without encrypting the AOB. (Second Embodiment) The second embodiment relates to an improvement on how to store still images to be displayed together with the AOB files shown in the first embodiment.

{69-1} Hierarchical Structure of Flash Memory Card in Second Embodiment FIG. 69 shows a flash memory card 3 according to this embodiment.
FIG. 2 is a diagram showing a hierarchical structure of No. 1; The difference from the hierarchical structure of the first embodiment is that in the second embodiment, a POB group is newly added to presentation data, and a POBManager is newly added to navigation data. These POBs are combined with JPEG (Joint Photographic Expert
s Group) format still image data.
And TrackManager. The POBManager is management information describing how these POBs are referred to by the PlayListManager and the TrackManager.

{69-1_70A-1} Configuration of User Data Area in File System Layer Since a new information element has been added to the presentation data and navigation data, the internal configuration of the user data area and the protection area in the file system layer is as follows. It is modified as shown in FIGS. 70 (a) and (b).
This drawing differs from the user data area of the first embodiment shown in FIG. 8A in that files such as POBXXX.JPG and POBXXX.SP1 are added, and a file called POB000.POM is added. It is a point.

[0239] POBXXX.JPG and POBXXX.SP1 correspond to the POB group shown in FIG. 69, and POB000.POM corresponds to POBMana.
It corresponds to ger. POBXXX.JPG and POBXXX.SP1
The difference is that there is a copyright. The former is simply JP
In contrast to files containing still image data in the EG format, the latter is encrypted to protect the copyright of the still images (SP1 of the extension is "Secure Pictur").
e ", and it is clear that there is a need for copyright protection.). Still image data such as family photos and commemorative photos taken by the user are exclusively for personal enjoyment. It is originally recorded on a flash memory card, and it is not necessary to focus on copyright protection, so it is sufficient to store it on the flash memory card in the former form, but the artist distributed by electronic music distribution Photos and illustrations, like music content, are creations created by artists, and if copied by a user, their copyrights may be infringed, so they are stored on the flash memory card in the latter form. PO in the figure
Numerical values such as 001, 002, 003 attached to BXXX.SP1 and POBXXX.JPG are POB numbers assigned to the respective POBs, and a plurality of POBs are uniquely specified by these POB numbers.

{69-2_70B-1} Configuration of User Data Area in File System Layer FIG. 70 (b) is a diagram showing the configuration of a protected area in the second embodiment. Figure 8 shows the protected area.
Compared to the configuration of the protected area shown in (b), POBS
A new encryption key storage file called P1.key has been added. This is a file storing a Filekey for decrypting POBXXX.SP1 in FIG. 70 (a).
When reading OBXXX.SP1, the Filekey must be extracted from this file.

In electronic music distribution, the server computer of the music company uses the SD_Aud shown in FIGS. 70 (a) and (b).
If the consumer issues a purchase request for the music content, the SD_Audio directory is compressed and encrypted, and then the SD_Audio directory is transmitted to the consumer who issued the purchase request. When the consumer's computer receives the SD_Audio directory, it decrypts the directory and decompresses it to obtain the SD_Audio directory. In addition, truck
(AOB) and a still image (POB) corresponding to this track are downloaded from the server computer of the music company, and the computer owned by the consumer stores the flash memory card 3
1, the SD_Audio directory shown in FIGS. 70A and 70B may be created.

{69-3_71A, B, C-1} POBXXX.JPG, POBXXX.SP
Next, the internal configuration of POBXXX.JPG and POBXXX.SP1 will be described. FIG. 71A shows the internal structure of POBXXX.JPG. In this drawing, POBXXX.JPG contains unencrypted still image data and has the same file structure as a normal JPEG file.

FIG. 71B shows the internal structure of POBXXX.SP1. As shown in this figure, POBXXX.SP1 is POB_He
It can be seen that it is composed of ader (POB_H) and encrypted JPEG still image data. POB to dashed leader line hp1
Indicates the internal configuration of _H. As shown in this figure, POB_H is
Indicates the identification number of the file, POB_ID set to a 2-byte value "FFE0", a 1-byte reserved area, and POBXXX.SP
1 includes a 1-byte POB_ATR indicating whether or not the encrypted entity part exists or not, and a 4-byte POB_SZ indicating the data length of the POB.

Since the POBXXX.SP1 has an encrypted entity, the POB_ATR is set to “0” indicating “there is an entity”, but the encrypted entity exists in the POBXXX.SP1. Instead, some files store a file path for a file storing still image data. FIG.
FIG. 1C is a diagram showing an example of a POB file storing a file path instead of an encrypted entity part. "\ DC
“Photo001.JPG” of “IM \ Ctg_001 \ photo001.JPG” is a file containing still image data captured by a digital still camera, and indicates a file path for the file. If such a directory path and file name are specified in the POB file, "\ DCIM \ Ctg_00
Still image data recorded in "photo001.JPG" of "1 \ photo001.JPG" is indirectly referred to. This PO
In BXXX.SP1, the POB_ATR in the POBManager is set to "1" indicating "substantial".

For example, recording still image data taken by a digital still camera in a specific file,
Storing the file in a unique directory,
Even when the device driver dedicated to the digital still camera requests the flash memory card (see FIG. 7).
1 (c), the device driver dedicated to the digital still camera requests that it be stored in \ DCIM \ Ctg_001 \ photo001.JPG), and the POB file in FIG. 71 (c) is the reference destination file. The JPG file containing the still image data is specified via the path. It can be displayed together with playback.

The description of the presentation data in the second embodiment has been completed. {72-1} About PlayListManager and TrackManager POBXXX.JPG and POBX in presentation data
XX.SP1 is displayed in synchronization with the reproduction of the track shown in the first embodiment. PlayListManager and TrackManage in the second embodiment to realize synchronized display with a track
r has the configuration shown in FIG. FIG. 72 is a diagram illustrating a detailed configuration of a PlayListManager and a TrackManager in the second embodiment. The difference between the configuration of the PlayListManager and the TrackManager of the first embodiment shown in FIG. 17 and FIG.
Playlist General Infomation (DPLGI), Playlist Gener
The internal configuration of al Infomation (PLGI) has been clarified, and TKI_POB_ATR and 20 TKI_POB
_SRP is newly provided.

{72-2} DPLGI The default playlist entire information (DPLGI) has an ID that can uniquely identify DPLI, as indicated by a dashed line h61.
Field, a DPLI_TK_Ns field that describes the number of tracks referenced from the DPLI, and a DPLI_PB_ field that describes the total playback time of all tracks referenced from the default playlist in milliseconds.
TM field, DPLI_POB_ATR field, and 60 DPs
LI_POB_SRP field.

{72-3} PLGI The entire playlist information (PLGI) is indicated by a broken line h62.
As shown in P, P which describes the ID that can uniquely identify the PLI
The LI_ID field and the number of tracks referenced from the PLI can be described, and up to 99 tracks can be referenced.
It consists of a PLI_TK_Ns field, a PLI_PB_TM field in which the total playback time of all tracks referenced from the playlist in milliseconds is described, a PLI_POB_ATR field, and 20 PLI_POB_SRP fields.

{72-4_73} Summary of Additional Improvements in Second Embodiment As can be seen from the above description, the TK
Two pieces of information, TKI_POB_ATR and TKI_POB_SRP, are added to the GI, and DPLI_POB_ATR-DPLI_POB_
Two pieces of information called SRP, PLGI, PLI_POB_ATR-PLI_POB
It can be seen that two pieces of information, _SRP, have been added. T
KI_POB_SRP, PLI_POB_SRP, and DPLI_POB_SRP all have a common configuration and can specify a POB. FIG. 73 is a diagram showing a state in which the POB file shown in FIG. 70 is specified by TKI_POB_SRP, PLI_POB_SRP, and DPLI_POB_SRP. Hereafter, TKI_POB_ATR (DPLI_POB_ATR, P
LI_POB_ATR), TKI_POB_SRP (DPLI_POB_SRP, PLI_POB_S
The data structure of (RP) will be described.

{74-1} TKI_POB_SRP TKI_POB_SRP indicates the POB to be displayed during the playback period during which a specific AOB is played, out of the time zone in which playback is performed in the playback order specified by the Default_Playlist information and PlayList information. The field to specify. In other words, T
rackManager can specify POB to be displayed for each track by setting TKI_POB_SRP.

FIG. 74 shows the data structure of TKI_POB_SRP and TKI_POB_ATR. In this figure, TKI_POB_SRP
`` POB designation field '' from bit number b25 to bit number b16, `` number of Pixel '' field from bit number b11 to bit number b8, `` Huffman table '' field from bit number b7 to bit number b6 , From the bit number b5 to the bit number b4
sampling field, a 'Picture Coding Mode' field occupying bit number b3 to bit number b0, bit number b12 to bit number b15, bit number b26
To a bit number b31.

[0252] The "POB designation field" is a field in which the number of the POB to be displayed (the number of the POB to be referenced) is described in the range of 1 to 999 during the period in which the AOB file corresponding to this TKI is being reproduced. It is. If a still image is not displayed during the period in which the AOB file corresponding to the TKI is being reproduced, “0” is described. Picture Codin
The "g Mode" field is a field for notifying the playback device of the method of encoding the still image when the still image specified by the POB designation field is displayed. JPEG (Joint Photograph Expert Grou
In the case of p), a value of “0000b” is described.

The “Chominance sampling” field contains P
This field indicates the ratio of sampling of the luminance component and the two color difference components when the still image specified in the OB specification field is encoded. If the ratio between the luminance component and the two chrominance components is 4: 2: 2, it is set to 00 bit.If the ratio is 4: 2: 0, it is 01 bit.
Is set to

[0254] The "Huffman table" field is a field indicating whether or not to use a typical Huffman table when displaying a still image specified in the POB specification field. When the Huffman table is used, it is set to 00 bits. The “number of Pixel” field is a field in which the image size of the still image data specified in the POB specification field is described. When the image size of the still image data is 96 × 96, a value of “0000b” is described. For 640 × 480, “0001b”, 160 × 120-1800 × 1
If the image size is 200 and the image size is other than 640 × 480, the value of “0010b” is described.

The TKGI has the TKI_PO having the above configuration.
Since there are 20 B_SRPs, a maximum of 2
0 still images can be reproduced. If one track is composed of a plurality of TKIs, TKI_POB_SRP is valid only for the first TKI. {74-2} TKI_POB_ATR “TKI_POB_ATR” is provided for designating how to display POBs specified by 20 TKI_POB_SRPs in TKGI. TKI_POB_ATR is a display order mo occupying bit number b0 to bit number b1.
It consists of a de field and a Display Timing mode field occupying bit number b2 to bit number b3.

The “Display order mode” field contains TK
The order in which the POBs specified by the 20 TKI_POB_SRPs in the GI are displayed is set. There are three modes for reproducing POBs during the AOB reproduction time. The first aspect is that up to 20 TKI_Ps in TKGI
This is the case where POBs specified in OB_SRP are displayed in the order of TKI_POB_SRP in TKGI, which is called sequential mode. The second aspect is that 20 TKI_Ps in TKGI
This is a mode in which the POB specified by OB_SRP is randomly selected and played, and is called a random mode. The third aspect is that 20 TKI_POB_
This mode randomly selects and plays POBs specified in the SRP, and is called shuffle mode. Display order
In the mode field, a value of “00b” is set when the sequential mode is set. On the other hand, the value is described as “01b” when the random mode is set, and “10b” when the shuffle mode is set.

The “Display Timing mode” field contains T
POB specified in up to 20 TKI_POB_SRPs in KGI
Is a field for setting whether or not to synchronize the display with the reproduction of the AOB file associated with the TKI.
A mode in which video and audio are synchronized is called a slide show mode, and it is not possible to skip only video display. On the other hand, a mode in which video and audio are not synchronized is referred to as a browserable mode, and only video display can be skipped.

[0258] As described above, TKGI uses the AOB corresponding to itself.
Which POBs to display during the playback of the file, in what order the POBs are displayed, and whether to synchronize the display of the POBs with the playback of the AOB file associated with the TKI No or not is set. {74-3_75} Example of setting TKI_POB_SRP included in TKI # 1 to TKI # 3 FIG. 75 is a diagram illustrating an example of setting TKI_POB_SRP for TKI # 1 to TKI # 3 included in TrackManager. The first row shows TrackManager, and the second row shows nine POB files. TrackManager in the first stage consists of 8 TKIs
And the arrows indicate which POBs TKI_POB_SRP in those TKIs
Indicates whether you are referring to a file. According to the reference relationship indicated by the arrow, TKI # 1 includes three TKI_POB_SRPs, and these three TKI_POB_SRPs specify POB001 to POB003.
Also, TKI # 2 includes three TKI_POB_SRPs, and those three TKI_POB_SRPs
POB_SRP is POB004 to POB006, TKI # 3 is three TKI_POB_SRP
It can be seen that these three TKI_POB_SRPs specify POB007 to POB009.

In this embodiment, JPEG image data in which a character string indicating lyrics is arranged on a plain background is used for POB001 to POB09. Here, the character string used in the description of the lyrics is drawn in a font that more closely matches the image of the lyrics, and is subjected to contour emphasis, decoration, and the like.
The contents of each POB are shown at the bottom of FIG. POB001
~ The content of POB003 is a lyrics card of TrackA, POB00
4 ~ POB006 is TrackB's lyrics card, POB007 ~ POB00
The content of 9 is the lyrics card of TrackC. Since it is meaningless for each of these to be reproduced during the period in which each track is being reproduced, TKI_POB_SRP included in the TKI is set to reproduce during each period in which each track is being reproduced.

[0260] The period during which each track is reproduced is the first.
This is as shown in FIG. 16 in the embodiment. That is, TK
The playback time of AOB001.SA1 corresponding to I # 1 is 6.1 minutes, the playback time of AOB002.SA1 corresponding to TKI # 2 is 3.3 minutes, and the playback time of AOB003.SA1 corresponding to TKI # 3 is 5.5 minutes. During this period, the setting of TKI_POB_SRP set in the TKI becomes valid, and the playback device can display the POB according to the valid TKI_POB_SRP.

The playback time of AOB001.SA1 corresponding to TKI # 1 is
Assuming that POB001 to POB003 are evenly displayed during this period, the display time per sheet is 2.03 minutes = (6.1
Min / 3). The playback time of AOB002.SA1 corresponding to TKI # 2 is
The playback time is 3.3 minutes, and the playback time of one piece of POB004 to POB006 is 1.1 minutes = (3.3 minutes / 3), AOB00 corresponding to TKI # 3.
3. The playback time of SA1 is 5.5 minutes, and the display time per POB007 to POB009 is 1.83 minutes = (5.5 minutes / 3).

{74-4_76} TKI_PO included in TKI # 4 to TKI # 8
Setting Example of B_SRP FIG. 76 is a diagram illustrating a setting example of TKI_POB_SRP included in TKI # 4 to TKI # 8 included in TrackManager. The first row shows the TrackManager, and the second row shows 10 POB files. According to the reference relationship indicated by the arrow, TKI # 4
Are the seven TKI_POB_SRs indicated by the seven arrows in FIG.
P, and their seven TKI_POB_SRPs are POB010-P
OB016 is specified. Also, it can be seen that TKI # 8 includes three TKI_POB_SRPs, and those TKI_POB_SRPs specify POB017 to POB019. In this embodiment, POB010 ~ 019
As in POB001-009, JPEG image data in which a character string indicating lyrics is arranged on a plain background is used. In addition, TK
TKI_POB_SRP is set only for I # 4, and TKI_POB is set for TKI # 5 to # 7.
The reason that _SRP is not set is that, as described above, when one track is composed of a plurality of TKIs, TKI_POB_SRP is valid only for the first TKI.

The contents of POB010 to POB016 are the lyrics cards of TrackD shown in FIG. 16 of the first embodiment, and the contents of POB017 to POB019 are the lyrics cards of TrackE. The playback time of AOB004.SA1 to AOB007.SA1 corresponding to TKI # 4 to TKI # 7 is 30.6 minutes, and the display time per POB010 to POB016 is 4.37 minutes (=
30.6 minutes / 7), and during these periods, each POB can be displayed evenly. AOB008.SA corresponding to TKI # 8
The playback time of 1 is 7.0 minutes, and the display time per POB017 to POB019 is 2.33 minutes (= 7.0 minutes / 3).

{77-1} DPLI_POB_SRP included in DPLGI and
DPLI_POB_ATR While TKI_POB_SRP can specify the POB to be displayed for each track, DPLI_POB_SRP in DPLGI
Is the POB to be displayed in the time zone during which multiple AOBs are played according to the order specified by the Default_Playlist information.
Is specified. FIG. 77 shows D included in DPLGI.
It is a figure which shows PLI_POB_SRP and DPLI_POB_ATR. DPLI_POB_SRP and DPLI_POB_ATR included in DPLGI are also TKI_POB_SRP
FIG. 77 also has the same data structure as that of TKI_POB_ATR. Default_Playlist
Since the information defines the reproduction order of a plurality of AOB files, DPLI_POB_SRP and DPLI_POB_ATR in FIG.
During the period in which a plurality of AOB files whose playback order is defined by the Default_Playlist information is being played, which POBs are to be displayed, in what order the POBs are to be displayed, the POB display, and the TKI Can be set to synchronize with the playback of the AOB file associated with.

{77-2_78} Example of setting 20 DPLI_POB_SRPs FIG. 78 shows 20 DPLI_POB_SRPs included in Default_Playlist information.
It is a figure showing the example of setting of _POB_SRP. The first stage is Defaul
Indicates t_Playlist information, and the frame included in it is DPLGI and 2
Indicates 0 DPLI_POB_SRP. The second stage is POB020-POB
Here are 20 POB files consisting of 039. According to the reference relationship indicated by the arrow, the 20 DPLI_POB_SRPs are each POB0
20 to POB039 are specified.

[0266] POB020 is an illustration used for a package software jacket that records a music album consisting of TrackA to TrackE, and POB021 is a logo mark of a production company that produced the music album.
POB025 is a portrait of the artist, POB026-POB031 is a scene from the promotion video, POB032-POB0
39 is a photograph taken when TrackA to TrackE were performed in a concert. DP in Default_Playlist information
Since LI_POB_SRP is defined by the creation of the music content, the POB that matches the track image of the music content and the artist's talent image
Is specified to be displayed.

[0267] During the period in which the AOB file whose reproduction order is specified by the Default_Playlist information is being reproduced, the P specified by the DPLI_POB_SRP included in the DPLGI is used.
The OB file will be displayed. For example, in the example of FIG. 40, the playback order of five tracks, TrackA to TrackE, is specified via eight TKIs by the Default_Playlist information. On the other hand, in the example of FIG.
According to DPLI_POB_SRP included in Playlist information, 20 POs
If a B file is specified, DPLI_P based on this Default_Playlist information will be
The specification of OB_SRP is valid. Further, assuming that the reproduction time of 52.5 minutes is equally allocated to POB020 to POB039, the display time per one image becomes 2.625 minutes = (52.5 minutes / 20).

{77-3_79} Foreground picture as playback time elapses
Background image transition FIG. 79 shows DPLI_POB_S included in Default_Playlist information.
10 is a timing chart showing how these are combined when a POB specified by an RP is set as a background image and a POB specified by TKI_POB_SRP included in a TrackManager is set as a foreground image. The first row in FIG. 79 shows the same POB as the second row in FIG. 78, and the second row in FIG. 79 shows the same POB as the second row in FIG. 75 and FIG. It is shown. The horizontal direction in the figure is a time axis with one minute as a unit time. Further, the width of the POB in this figure indicates how long the reproduction of each POB is continued in minutes.

Referring to the time axis of FIG.
In the period up to 6.1 minutes, POB001 to POB003 (Lyrics card of TrackA) will be displayed as foreground images, and POB020, POB021 (jacket illustration and logo of production company), and POB022 (portrait of artist) will be displayed as background images. Become. POB004 to POB009 (TrackB, TrackC) during the period from 6.1 minutes after the start of playback to 14.9 (= 6.1 + 3.3 + 5.5) minutes
Lyric card) is displayed as the foreground image, and POB022 to POB025 (portrait of the artist) are displayed as the background image.

After 14.9 minutes from the start of reproduction, POB010-PO
B011 (lyric card of TrackD) is displayed as a foreground image, and POB025 (portrait of an artist) and POB026 to POB028 (one scene of a promotion video) are displayed as background images. {77-4_80} According to this timing chart, Default_Pl
6.1 minutes after the start of playback of aylist information, POB004 is set as the foreground image (the lyrics of TrackB) and POB022 (photograph of the artist)
Is displayed as a background image. FIG.
0 is a diagram showing how the foreground image and the background image are combined after 6 minutes from the start of the reproduction of the Default_Playlist information.

{77-5_81} Also, after 16 minutes from the start of the reproduction of the Default_Playlist information, POB010 (the lyrics of TrackD) is set as the foreground picture, and POB026 (one scene of the promotion video)
Is displayed as a background image. FIG.
FIG. 1 is a diagram showing how a foreground image and a background image are combined 16 minutes after the start of reproduction of Default_Playlist information.

As described above, in the Default_Playlist information,
The POB file specified by DPLI_POB_SRP and TrackMana
If you combine and display the POB file specified by TKI_POB_SRP in ger as the foreground image and the background image, you can display the lyrics of the track, the portrait of the artist who wrote and composed the track, promotion video, concert A scene or the like can be displayed as a background image. In addition, which POB file is displayed in which time zone can be easily changed by rewriting TKI_POB_SRP and DPLI_POB_SRP in the TrackManager and Default_Playlist information. {82-1} PLI_POB_SRP and PLI_POB_ATR PLGI included in PLGI PLI_POB_SRP and PLI_POB_ATR are also
It has the same data structure as DPLI_POB_SRP and DPLI_POB_ATR included in LGI and TKI_POB_SRP and TKI_POB_ATR included in TKI. FIG. 82 shows PLI_POB_SR included in PLGI
It is a figure which shows P and PLI_POB_ATR. PlayList information is De
Unlike the fault_Playlist information, it specifies the playback order that is defined by the user, so PLI_POB_SRP and PLI_POB
_ATR indicates which POBs are to be displayed during the period in which a plurality of AOB files whose playback order is specified by the PlayList information are being played, the order in which these POBs are to be displayed, the display of POBs, AO associated with TKI
The user can set whether or not to synchronize with the playback of the B file based on his / her own idea (Note that Default_Playlist
It is only an example that the music company sets the DPLI_POB_SRP of the information, and the DPLI_POB_S in the Default_Playlist information
The user may also freely set the RP. ).

[0273] {82-2_83} PLI_PO included in PlayList information
Setting Example of B_SRP Subsequently, a setting example of PLI_POB_SRP included in the PlayList information will be described. FIG. 83 is included in PlayList information.
It is a figure showing the example of setting of 20 PLI_POB_SRP. The first row shows PlayList information, in which the frame included is PLGI,
Indicates 20 PLI_POB_SRP. The second stage is POB040-POB
Here are 20 POB files consisting of 059. According to the reference relationship indicated by the arrow, each of the 20 PLI_POB_SRPs is a POB040
~ POB059 is specified.

While POB020 to POB039 are all still image data created by the creator of the music content, POB0 to POB039 are POB0 to POB039.
40 to POB059 are all personal photographs of the user. That is, POB040 is a picture of the user's family, and POB041 is
The user's graduation photo, POB042-POB045, is a photo of the user's pet, POB046-POB051 is a commemorative photo when traveling in Europe, and POB052-POB059 is a commemorative photo when traveling in the United States. In order to simplify the description, this Pl
The total playback time of the AOB file whose playback order is specified by the ayList information and the number of POBs specified to be displayed by this PlayList information are the same as the Default_Playlist information. Then, Tr specified by this PlayList information
The total playback time of ackA ~ TrackE is 52.5 minutes, POB040 ~ PO
If B059 is displayed evenly during this playback time, the display time per image is 2.625 minutes = (52.5 minutes / 20).

{82-3_84} Foreground picture as playback time elapses
Background Image Transition FIG. 84 shows a case where the POB specified by PLI_POB_SRP included in the Playlist information is used as the background image, and the TKI included in the TrackManager.
6 is a timing chart showing how these are combined when POBs specified by _POB_SRP are set as foreground images. The first row in FIG. 84 shows the same POB as the second row in FIG. 83, and the second row in FIG.
FIG. 5 shows the same POB as the second row in FIG.
The horizontal direction in the figure is a time axis with one minute as a unit time.
Further, the width of the POB in this figure indicates how long the reproduction of each POB is continued in minutes.

In the figure, POB001 to POB003 (lyric cards of TrackA) are used as foreground images, POB040, POB041 (family photo and graduation photo), and POB042 are used as background images during the period from the start of reproduction to the elapse of 6.1 minutes. Will be displayed. POB004 to POB009 (Lyrics card for TrackB, TrackC) during the period from 6.1 minutes to 14.9 minutes
Are displayed as foreground images, and POB042 to POB045 (photos of pets) are displayed as background images. After 14.9 minutes, POB010
~ POB011 (Lyrics card of TrackD) as POB04
5, POB046-POB048 (Commemorative photo when traveling in Europe)
Will be displayed as the background image.

[0277] PO specified in Default_Playlist information
B is considered by a music content production company,
While the POB specified in the image of the track of the music content or the artist's talent image is specified, the POB specified in the PlayList information is selected by the user personally, and the user's personal The feelings are strong.

{82-4_85} According to FIG. 84, POB004 is set to the foreground image (TrackB
), And a composite video with POB042 (a photo of a pet) as a background image is displayed. FIG. 85 is a diagram showing how a foreground image and a background image are combined after 6.1 minutes have elapsed from the start of reproduction of Playlist information. {82-5_86} After 16 minutes from the start of the reproduction of the Playlist information, a composite video is displayed with POB010 (the lyrics of TrackD) as the foreground image and POB046 (the photograph of a trip to Europe) as the background image. FIG. 86 shows a state where the reproduction of the playlist information is started.
FIG. 10 is a diagram illustrating how a foreground image and a background image are combined after 16 minutes have elapsed. The contents of the lyrics in these composite images are the same as in FIGS. 80 and 81, but since the background images are different, it can be seen that the impression seen is significantly different from the composite images shown in FIGS. 80 and 81.

[0279] As described above, the Pl uniquely defined by the user.
By having PLI_POB_SRP in the ayList information specify a POB file different from the POB file specified in the Default_Playlist information, the user can display a picture or the like associated with the memory when playing the track of the memory. . {82-6_87} Setting example in which common POB is specified in DPLI_POB_SRP of Default_Playlist information In one example of FIG. 78, FIG. 79, FIG. 82, and FIG.
All DPLI_POB_SRP included in Playlist information specified different POB files, but Default_Playlist
If a duplicate POB file is specified in any of the DPLI_POB_SRPs included in the information, the number of POB files can be reduced by displaying a common POB file while multiple tracks are being played. And
The work of the title maker can be reduced. Fig. 87
Is the multiple DPLI_POB_SRP in the Default_Playlist information
In this example, the DPLI_POB_SRP specifies a common POB file to reduce the number of POB files. In this figure, DPLI_POB_SRP # 1 and DPLI_POB_SRP # 4
Specifies POB020, DPLI_POB_SRP # 2 and DPLI_P
It can be seen that OB_SRP # 5 specifies POB021.

{82-7_88} Foreground picture as playback time elapses
Background image transition FIG. 88 shows DPLI_POB_S included in Default_Playlist information.
10 is a timing chart showing how these are combined when a POB specified by an RP is set as a background image and a POB specified by TKI_POB_SRP included in a TrackManager is set as a foreground image. In this timing chart, it can be seen that POB020 indicating the jacket illustration of the package software is repeatedly displayed three times immediately after the start of playback, after the elapse of 7.875 minutes, and after the elapse of 15.75 minutes. Also, it can be seen that POB021 showing the logo of the production company is repeatedly displayed three times after elapse of 2.625 minutes, 10.5 minutes, and 18.375 minutes from the start of reproduction. As shown in FIG. 87, DPLI_POB_S
When the RP is specified, the same POB is repeatedly displayed, which is suitable when there is a POB that should be repeatedly displayed, such as a jacket illustration or a logo mark.

[0281] Although the text is long, TKGI, DPLGI, PLGI
The explanation about is finished. {69-4_89} Regarding POBMG In the second embodiment, a POBManager that is a new information element added to navigation data will be described. FIG. 89 is a diagram showing the internal configuration of the POBMG. As shown in this figure, POBMG stores POB management information (POBMGI) and POB Co
unt Information (POBCI) # 1... #n.

{69-4_89-1} Regarding POBMGI The POB management information (POBMGI) is composed of POBMGI identification information occupying the 0th byte to the 1st byte, and 3 bytes from the 2nd byte as shown by the broken line. Reserved fields occupying the eye
(reserved) and POB_ occupying the 4th to 5th bytes
It consists of an Ns field and a reserved field (reserved) occupying the sixth to seventh bytes.

In the POBMGI identification information field, an ID capable of uniquely identifying POBMGI is described (character set code "A6" of ISO646). In the POB_Ns field, "
The number of POBs from 0 "to" 999 "is described.
The explanation of the management information (POBMGI) ends. {69-4_89-2} Regarding POBCI Next, POB Count Information (POBCI) will be described. P
OB Count Information (POBCI) is management information provided in association with each POB. The bit configuration is as shown by the broken line. That is, a POB_RCN field occupying bit number b0 to bit number b9, a reserved area field occupying bit number b10 to bit number b13, and a data existence field occupying bit number b14 to bit number b15. Consists of

{69-4_89-3} Regarding POB_RCN The “POB_RCN” field indicates whether or not the display of the POB associated with POBCI is specified by DPLGI, PLGI, or TKGI. The specified number of times,
That is, the number of times display is specified is described in the range of 1 to 999. As described in the first embodiment, the TKI can be deleted, and the designation of the reproduction order in the Default_Playlist information and the PlayList information can be freely deleted. POB_
POB specified number in refernce_count is P
If the TKI that specified the OB is deleted, the deleted TKI
It is decremented by the number. Also, when Default_Playlist information and PlayList information are deleted, the deleted TKI
It is decremented by the number. If no display is specified by DPLGI, PLGI, or TKGI, POB_refernce_count becomes 0. POB for which POB_refernce_count is 0 is any TK
I, since the POB is not referenced from the PlayList information, the playback device performs the deletion every time the TKI and PlayList information are deleted.
Detect the POB whose refernce_count_number is 0, and
PO containing POB with efernce_count_number of 0
By deleting the B file, the number of still image data stored in the flash memory card can be reduced. Of a plurality of POBs, a specific POB has a close relationship with only a specific track, and if it is not played back in synchronization with that track, it makes sense to store that POB on a flash memory card. If it does not exist (for example, a case where a still image indicating the lyrics of the track stored in the flash memory card is stored as still image data corresponds to this), reference_c
By performing the deletion based on the ount_number, there is no waste of storing an extra POB in the flash memory card. In addition to the case where the TKI is deleted, the same decrement of the reference_count_number may be performed when the POB specified by DPLI_POB_SRP, PLI_POB_SRP, and TKI_POB_SRP is deleted by the editing work.

{69-4_89-4} Data existence data e occupying bit number b14 to bit number b15
The xistence field specifies whether a POB corresponding to this POB number exists. If the POB corresponding to the POB number exists, it is set to 01b, and if the POB does not exist,
00b is set. If it is specified that a POB exists, the TKI and PlayList information are deleted and even if POB_ref
Even if ernce_count becomes 0, the POB_refernce_c
The POB corresponding to the ount is considered to be worth storing on the flash memory card, and the POB is not deleted. T
Regardless of whether or not it is referenced by KI and PlayList information, if the POB alone has a storage value, set the data existance corresponding to that POB to 1. POB like no
By setting the data existance corresponding to the POB to 0, the POB having a storage value can be left in the flash memory card. On the other hand, a POB that has a storage value only when integrated with the track is deleted together with the track, so that the storage capacity of the flash memory card can be effectively used.

The description of the POBManager (POBMG) ends here. {69-5} Updating at the time of editing of TKI In the four editing cases described in the first embodiment, when some tracks are deleted (case 1), any two of a plurality of tracks are replaced by one track (Case
3) How TKI_POB_SRP and DPLI_POB_SRP are updated when one track is divided to obtain two tracks (case 4) and when the order of the tracks is changed (case 5) will be described.

When a track is deleted (case 1), the first
As shown in the embodiment, the TKI_BLK_ATR for the TKI
Is set to “Unused” and the TKI_P
Delete OB_SRP. At the same time, the POB in the POBManager corresponding to the POB specified by the TKI_POB_SRP
Decrement _refernce_count. DPLGI, POB specified in PLI_POB_SRP, DPLI_POB_SRP in PLGI
Does not change even with the deletion.

When the order of the tracks specified by DPL_TK_SRP is changed (case 5), the order of the tracks is changed, and the display order of the POBs specified by TKI_POB_SRP is the order after the replacement. For track integration (case 3), it is desirable to also integrate TKI_POB_SRP in TKI. Because, as described above, if one track is composed of multiple TKIs, TKI_POB_SRP is valid only for the first TKI, so the track integration operation
The POB specified in TKI_POB_SRP of I
This is because TKI_POB_SRP needs to be specified.

When the track is divided (case 4), it is necessary to change TKI_BLK_ATR of TKI and divide TTKMSRT and BIT into two, as described in the first embodiment. Similarly, a plurality of TKI_POB_SRPs specified by TKGI may be divided into two and distributed to the original TKI and the TKI obtained by the division. {69-6} Application example of TKI_POB_SRP, DPLI_POB_SRP setting In the data structure of TrackManager and PlayListManager described above, the correspondence between AOB file and POB
The music contents can be freely changed by setting B_SRP, DPLI_POB_SRP, and PLI_POB_SRP. A plurality of music contents having different prices can be sold to consumers according to the amount of data.

If the consumer desires to purchase the type without the lyrics, the eight AOB files shown in the first embodiment and the POB020 to POB039 shown in FIG. 78 are stored in the TK in TKI # 1 to TKI # 8.
SD_Audio including TrackManager specified by I_POB_SRP
A directory is created, compressed, and sent to a consumer-owned general-purpose personal computer. still,
Track (AOB) and corresponding still image (POB)
Are downloaded from the server computer of the music company, and the computer owned by the consumer uses the flash memory card 31 as shown in FIGS. 70 (a) and (b).
An SD_Audio directory may be created.

When the consumer desires to purchase a certain type of lyrics, the eight AOB files shown in the first embodiment and the POB001 to POB019 corresponding to the lyrics shown in FIGS.
TrackMa specified by TKI_POB_SRP in TKI # 1 to TKI # 8
Create an SD_Audio directory containing nager, compress it, and send it to a general-purpose personal computer owned by the consumer.

When the consumer desires to purchase a type having lyrics and a background image, the eight AOB files shown in the first embodiment and the POB001 to POB019 corresponding to the lyrics are written in TKI # 1 to TKI # 8.
Creates an SD_Audio directory including a TrackManager designated as TKI_POB_SRP and a PlayListManager designated as POLI020-POB039 in DPLI_POB_SRP shown in FIG. do it.

In the present embodiment, TKI_POB_SRP, DPLI_POB_
Since arbitrary still image data can be added to audio data by setting SRP and PLI_POB_SRP, music contents with different price ranges can be easily created according to the amount of accompanying still image data. {90-1_91} Regarding playback device according to second embodiment Next, a playback device according to the second embodiment will be described. The playback apparatus according to the second embodiment differs from the playback apparatus according to the first embodiment mainly in three points. The first difference is that the playback device in the first embodiment is portable, whereas the playback device in the second embodiment is in-vehicle. FIG. 90 is a diagram showing how the playback device according to the second embodiment is used, and FIG.
FIG. 2 is a diagram illustrating an appearance of only a playback apparatus body according to the embodiment. In the figure, the playback device according to the second embodiment is the first playback device.
The difference from the playback device of the embodiment is that the playback device according to the second embodiment is installed inside a car as shown in FIG. 90, and is connected to a large-sized liquid crystal display 5 and an in-vehicle speaker. Is a point. Since the liquid crystal display 5 connected to the playback device is large, the playback device according to the second embodiment can suitably display the various still image data described above.

[0294] The second difference is that the descrambler 7 in the second embodiment decrypts the POB in addition to decrypting the audio data. That is, P
If the OB file is POBXXX.SP1 and the recorded POB is encrypted, the descrambler 7 stores the Ke of the encryption key storage file POBSP1.KEY in the protected area.
Filekey stored in y Entry is set and POBXXX.S
Release the encryption at P1. Finally, the third difference is that the ROM 4 in the second embodiment stores a program describing the processing content for displaying the POB as the foreground image or the background image, and the CPU 10 displays the screen based on the program. The point to do.

{90-2_92_93_94} Next, the internal structure of the playback device according to the second embodiment will be described. The internal configuration of the playback apparatus shown in FIG. 92 is different from that of the first embodiment in that a plurality of VRAMs 61 are provided. plural
VRAM 61 is a single graphics plane
It consists of VRAM corresponding to 0. In the VRAM of each graphics plane, a transmittance α of 0% to 100% is set for each pixel, and the pixel value of an image to be displayed on the liquid crystal display 5 is calculated by the following equation. FIG. 93 (a) shows a plurality of
FIG. 7 is a diagram showing how still images stored in VRAM 61 are superimposed. Pixel value of each pixel = pixel value of graphics plane 0 x
(1-α) + pixel value of graphics plane 1 × α The character portion representing the lyrics on the foreground image side has 0% transmittance.
Is set to Therefore, the background image stored in the graphics plane 1 does not appear on the screen at all. The transmittance of the plain background portion in the foreground image is set to 100%. Therefore, the background image stored in the graphics plane 1 is fitted into the solid portion of the still image in the graphics plane 0. Thus, the transmittance α
Is set, it is possible to obtain a composite image in which a background sheet is covered with a transparent sheet on which lyrics are described, that is, a composite image as shown in FIGS. 80 and 81.

In addition to the composite image shown in FIG. 93 (a), for example, as shown in FIG. 93 (b), the lyrics are arranged in the lower half and the background image is arranged in the upper half. May be displayed. {94-1} Flowchart for Foreground Image Display Processing FIG. 94 is a flowchart showing the processing procedure for foreground image display processing. Default_Playlist information is specified
When the reproduction based on TKI # z is started, step S40
In 2, the CPU 10 determines whether the TKI_POB_SRP included in the TKGI included in the TKI specifies a POB file. When TKI_POB_SRP specifies a POB file, in step S403, the CPU 10 counts how many POB files are specified by TKI_POB_SRP included in TKGI. In step S404, the display time POB per POB file is determined based on the number of POB files.
Determine _time. Subsequently, in step S405, C
PU10 refers to TKI_POB_ATR in TKGI, and each POB
Determines what display mode the file will be displayed in. If TKI_POB_ATR is described as the sequential mode, the process proceeds from step S405 to step S406 to initialize the variable i, and in step S407, the POB file specified by the i-th TKI_POB_SRP is displayed for the display time POB_time. At this time, TKI_POB_
If the extension of the POB file specified by the SRP is JPG, the POB is displayed as it is. If the extension of the POB specified in TKI_POB_SRP is SP1 and it is encrypted, read the corresponding Filekey from the protected area, decrypt the encryption of the POB, and
Is displayed. Then, in step S408, the variable i is set to P
It is determined whether or not OB_Ns has been reached. If it has not, the variable i is incremented in step S409, and the flow shifts to step S407. Thereafter, steps S406 to S409 are repeated until the variable i reaches POB_Ns. As a result, the P specified by TKGI's TKI_POB_SRP
OBs are displayed sequentially. When the variable i has reached POB_Ns, the processing of this flowchart ends.

If TKI_POB_ATR is described as a random mode, a variable i is initialized in step S410, a random number r in the range from 1 to POB_Ns is generated in step S411, and corresponds to the random number r in step S412. P specified in r-th TKI_POB_SRP
The OB file is displayed for the display time POB_time determined in step S404. Then, step S413
In step S414, it is determined whether the variable i has reached POB_Ns. If the variable i has not reached POB_Ns, the variable i is incremented in step S414, and the flow advances to step S411. When the display is completed, a random number r in the range from 1 to POB_Ns is generated again in step S411, and the POB file specified by the r-th TKI_POB_SRP corresponding to the random number r is read in step S412, and the process proceeds to step S404. Is displayed for the display time POB_time determined in. At this time, the TKI_POB_SR
If the extension of the POB file specified by P is JPG, the POB is displayed as it is. If the extension of the POB specified in TKI_POB_SRP is SP1 and it is encrypted, read the corresponding Filekey from the protected area, decrypt the relevant POB, and then display the relevant POB I do.

Thereafter, steps S411 to S414 are repeated until the variable i reaches POB_Ns. As a result, POBs specified by TKI_POB_SRP of TKGI are displayed in random order. When the variable i has reached POB_Ns, the processing of this flowchart ends. TKI_POB_ATR
Is described as shuffle mode, step S
405 to step S415, and then to
After initializing the variable i in step S416, step S416
Then, a random number r in the range from 1 to POB_Ns is generated, and then, in step S418, it is determined whether or not the generated random number r matches the displayed POB number. If they match, the process moves to step S416 to generate a random number again. If they do not match, the process moves from step S418 to step S419, where the r-th TKI_POB_
Copy the POB file specified by SRP to step S404
Is displayed for the display time POB_time determined in. At this time, as in the case of the sequential mode and the random mode, if the extension of the POB file specified by TKI_POB_SRP is JPG, the POB is displayed as it is. TK
The extension of the POB specified by I_POB_SRP is SP1,
If it is encrypted, the corresponding Filekey is read from the protected area, and the POB is displayed after decrypting the encryption of the POB. After finishing the display,
In step S417, the variable r is stored as the displayed POB number. Then, in step S420, the variable i
Is determined to have reached POB_Ns, and if not, the variable i is incremented in step S421, and the flow shifts to step S416. Thereafter, steps S416 to S421 are repeated until the variable i reaches POB_Ns. As a result, POBs specified by TKGI's TKI_POB_SRP are displayed sequentially. When the variable i has reached POB_Ns, the processing of this flowchart ends.

{95-1} Flowchart of Background Image Display Processing The description of the foreground image display processing is completed above, and the processing procedure of the background image display processing will be described. FIG.
It is a flowchart which shows the processing procedure of a background image display process. This flowchart is described in FIG. 94 with “TKGI_TKI_
The processing performed based on “POB_SRP, TKI_POB_ATR” is replaced with “DPLI_POB_SRP, DPLI_POB_ATR of DPLGI”, and the basic processing procedure is the same as the flowchart of FIG. 94.

When the Default_Playlist information is selected, step S5 is performed in the same manner as steps S402 to S405.
In 02 to S505, the CPU 10 determines whether or not DPLI_POB_SRP included in the DPLGI specifies a POB file, and if so, counts how many POB files are specified, and counts the number of POB files. The display time per image POB_time is determined, and the display mode is determined according to DPLI_POB_ATR. DPLI_POB_ATR
Is described as the sequential mode, the POB files are sequentially displayed in steps S506 to S509 according to the variable i and according to the DPLI_POB_SRP included in the DPLGI in the same manner as in steps S406 to S409.

If the DPLI_POB_ATR is described as the random mode, the POB files are sequentially displayed according to the variable r in accordance with the DPLI_POB_SRP included in the DPLGI in steps S510 to S514 as in steps S410 to S414. . If DPLI_POB_ATR is described as shuffle mode, step S4
As in the case of 15 to step S421, step S51
5-In step S521, the DPLGI
According to DPLI_POB_SRP included in, POB files are displayed sequentially.

{96-1} Flowchart of background image display processing The description of the foreground image display processing when referring to DPLI_POB_SRP of DPLGI is completed above, and then PLI_POB_SR of PLGI
The processing procedure of the background image display processing when referring to P will be described. FIG. 96 is a flowchart showing the processing procedure of the background image display processing. In this flowchart, the processing performed based on “DPLI_POB_SRP, DPLI_POB_ATR of DPLGI” in FIG. 95 is changed to “PLG PLI_POB_SRP, DPLI_PO
B_ATR ”, and the foreground image and the basic processing procedure are the same as those in the flowchart of FIG. 95, so the same reference numerals are assigned and detailed description is omitted.

{94-2_95-2_97A, B, C} Example of display on liquid crystal display 5 By the processing procedure shown in the flowcharts of FIGS. 94 and 95, the foreground image specified by TKI_POB_SRP and the background image specified by DPLGI are displayed. FIG. 97 (a) shows what kind of combined image is displayed on the liquid crystal display 5 when combined.
To (c).

As shown in FIG. 97 (a), Default_Play
It is assumed that list information is specified and the display of the POB is started according to the reproduction order described therein. In this case, FIG.
The foreground image display processing shown in the flowchart of FIG. 95 and the background image display processing shown in the flowchart of FIG.
PO whose display is specified from multiple TKI_POB_SRP included in
B, POBs whose display is specified from a plurality of DPLI_POB_SRPs included in DPLGI are sequentially displayed. Therefore, the image composition shown in FIG. 80 is performed six minutes after the start of the reproduction, and the composite image shown in FIG. 97 (b) is displayed on the liquid crystal display 5.

The image composition shown in FIG. 81 is performed 16 minutes after the start of reproduction, and the liquid crystal display 5 displays the image shown in FIG.
The composite image shown in FIG. 7 (c) is displayed. {94-2_96-1_98A, B, C} Example of display on liquid crystal display 5 The foreground image specified by TKI_POB_SRP and the background image specified by PLI_POB_SRP are synthesized by the processing procedures shown in the flowcharts of FIGS. FIG. 98 shows what kind of composite image is displayed on the liquid crystal display 5 when
(A) to (c) are shown.

[0306] As shown in Fig. 98A, it is assumed that PlayList information is specified and POB display is started in accordance with the reproduction order described therein. In this case, the foreground image display processing shown in the flowchart of FIG. 94 and the background image display processing shown in the flowchart of FIG. 96 are performed, and are included in the POBs and PLGIs whose display is designated by a plurality of TKI_POB_SRPs included in the TKGI. POBs whose display is specified from multiple PLI_POB_SRPs are displayed sequentially. For this reason, the image composition shown in FIG. 85 is performed six minutes after the start of reproduction, and the liquid crystal display 5
Displays a composite image shown in FIG. Also, after 16 minutes have elapsed from the start of the reproduction, the image composition shown in FIG. 86 is performed, and the composite image shown in FIG. 98 (c) is displayed on the liquid crystal display 5.

{99_1} Recording Apparatus According to Second Embodiment Next, a recording apparatus according to a second embodiment will be described. The recording apparatus according to the second embodiment is novel because a plurality of recording apparatuses are different.
The POB is recorded on the flash memory card 31 and T
KI_POB_SRP, DPLI_POB_SRP and PLI_POB_SRP are set, and TKI_POB_ATR, DPLI_POB_ATR and PLI_POB_ATR are set. Such a series of processing is performed by the CPU 10 according to the second embodiment through the procedure described in the flowchart of FIG. Hereinafter, the recording process of the recording apparatus according to the second embodiment will be described with reference to the flowchart in FIG.

[0308] In step S601, the CPU 10 initializes each variable used in this flowchart. Variables used in this flowchart include variables #x, #y, #
There are z, #u, #vy, and #w. #x is a variable that specifies a POB to be processed among a plurality of POBs, and #y is a track sequence to be processed among a plurality of track sequences.
The variable for specifying (PLI), #z, is a variable for specifying a track (TKI) to be processed among a plurality of tracks.

[0309] #u is a variable for specifying the DPLI_POB_SRP to be processed among a plurality of DPLI_POB_SRPs.
Multiple PLI_POB_S included in PLI indicated by y (PLI # y)
This variable specifies the PLI_POB_SRP to be processed among RPs. #w is a variable that specifies the TKI_POB_SRP to be processed among the plurality of TKI_POB_SRPs included in the TKI #y) indicated by #z.

When these variables are initialized, POB # x is displayed in step S602. Thereby, the operator can visually confirm what kind of photograph, illustration, and lyrics the POB is. In step S603, POB # x is a selection of still image data to be displayed during the entire time period during which the track sequence is reproduced or still image data to be displayed only during the time period during which a specific track is reproduced. Is received from the operator, and any selection is accepted.

[0311] If the operator determines that "POB # x should be assigned to the track sequence", the process waits for the selection of the track sequence for displaying the POB # x in step S604. If the selection is made, the process proceeds to step S60.
In 5 it is determined whether the playlist specifying the track sequence #y is DPLI or PLI.
If the playlist is DPLI, POB # x is set to DPLI_POB_SRP # u in DPLI in step S606, and DPLI_POB_ATR # u in DPLI is set to PO in step S607.
Set based on B # x. Thus DPLI_POB_SRP, DPLI_
If both POB_ATRs have been set, #u is incremented in step S608 (# u ← # u + 1), and then #x is incremented in step S609 (# x ← # x + 1).

If PLI is selected in step S605, PLI_P in PLI # y is selected in step S610.
POB # x is set in OB_SRP # vy, and in step S611
Set PLI_POB_ATR # vy in PLI based on POB # x. Then, after #vy is incremented in step S612 (# vy ← # vy + 1), the process proceeds to step S609 so as to increment #x.

If it is determined in step S603 that POB # x should be assigned to a track, step S613
In step S614, the designation of the track is received.
And POB # x is set to TKI_POB_SRP # w set in TKI # z for the track #z specified in. afterwards,
In step S615, TKI_POB_ATR # w in TKI # z
Is set based on POB # x, and in step S616, #
After incrementing w (# w ← # w + 1), step S6
At 17, it is determined whether or not #x has reached the last number #n of the POB. If not reached, the process proceeds to step S609 to increment #x. If #x reaches the last number #n of the POB, the process proceeds to step S618.
B # 1 to #n, TKMG including PLMGTKI including DPLI and PLI are recorded on the flash memory card, and the process ends.

As described above, according to the present embodiment, there is still image data to be commonly displayed as a background image during a time period during which a plurality of tracks are reproduced, such as a photograph of an artist or a company logo mark. If Default_Play
DPLGI in list information, PlayList information, DPLI_ in PLGI
By specifying the still image data in POB_SRP and PLI_POB_SRP, common still image data is displayed in a time zone in which a plurality of tracks whose reproduction order is specified by the playlist information are being reproduced. be able to. Also, if there is still image data that is to be displayed only during a period when a specific track is being played apart from the background image, such as lyrics, etc.
It can be specified by TKI_POB_SRP in I.

The above embodiment has been described only as an example of a system in which the best effects can be expected at present.
The present invention can be implemented and changed without departing from the gist thereof. Specifically, the following changes (a), (b), and (c) can be made. (A) The procedures and the like described with reference to the flowcharts of FIGS. 94, 95, 96, and 99 may be realized by an executable program, which may be recorded on a recording medium to be distributed and sold.

(B) The case where the presentation data and navigation data according to the present embodiment are applied to music content has been described as an example. However, the announcer or voice actor reads out the book using the presentation data and navigation data according to the present embodiment. It goes without saying that the present invention may be applied to a reading book composed of audio. In this case, the still image including the character string of the text included in the book is designated by TKI_POB_SRP as the foreground image, while the illustration of the document is designated as the background image by DPLI_POB_SR
It is desirable to have P and PLI_POB_SRP specified.

(C) In the present embodiment, DPLI_POB_SRP-PL
The POB specified by I_POB_SRP is used as the background image, and TKI_
Although the POB specified by the POB_SRP is used as the foreground image, the relationship between the two may be switched. Furthermore, DPLI_POB_S
POB specified by RP-PLI_POB_SRP and TKI_POB_
Only one of the POBs specified by the SRP may be displayed. In addition, the POB may be displayed without being distinguished from the foreground image and the background image. For example, DPLI_POB_SRP (PLI
_POB_SRP) to display the specified POB, then TKI_POB_SR
It goes without saying that the POB designated by P may be displayed.

(Third Embodiment) In the second embodiment, the Play
Each POB is displayed at an equal ratio during the period when the List information and the TKI are valid. However, in the third embodiment, the phrase period table and the highlight coordinate table are stored in the flash memory card 31, and the audio reproduction is performed. This is an embodiment in which the lyrics and the lyrics are precisely synchronized.

The former phrase period table is a table in which TKI_POB_SRP for designating a POB indicating each lyric is associated with information indicating the start and end of the phrase period. FIG. 100A shows an example of the phrase period table. Here, the phrase period represents a period in which the phrase described in the lyrics appears during the playback of the AOB with a time accuracy of a millisecond unit, and the playback device performs the playback process as described in the first embodiment. With the update of the time, monitoring is performed to determine which of the phrase periods described in the table the updated playback elapsed period corresponds to. AOB, AOB_ELEMENT, AOB_FR currently playing
You can find out which POB contains the lyrics of AME. The AOB playback and the lyrics display can be synchronized with the above-described time accuracy in milliseconds by using a table in which the phrase period of the POB is described with time accuracy in millisecond units.

When the playback start time is specified by using the jog dial as shown in the first embodiment and the cueing is performed, AOB and AOB_ELEMENT are calculated by using the expressions 1 to 3 shown in the first embodiment. The AOB_FR of the AOB_ELEMENT of which AOB
Judge whether it corresponds to AME. On the other hand, for still images,
It is determined which phrase period the specified reproduction start time corresponds to. Then, the POB corresponding to the designated phrase period is displayed. In this way, even when cueing is performed using the jog dial, the corresponding POB can be displayed as appropriate. In this embodiment, the time is described in the phrase period table, but it should be synchronized with the lyrics.
AOB number indicating AOB, AOB_ELEMENT, AOB_FRAME, AOB_ELEM
The ENT number and the AOB_FRAME number may be described in the phrase period table.

On the other hand, the latter highlight coordinate table includes the display coordinates of the characters included in the lyrics and the AOB_ELEMENT and AOB_FRAME corresponding to the characters in the AOB.
Is a table in which periods are reproduced. FIG.
00 (b) is a diagram illustrating an example of a highlight coordinate table. Such a highlight coordinate table is provided, and among the lyrics displayed corresponding to the phrase period, only the characters corresponding to the currently reproduced AOB_ELEMENT and AOB_FRAME are displayed in a different color. To be performed.

For example, if the lyrics include the phrase “access to you from a small window”, the highlight coordinate table indicates “small”, “sa”, “na”, and “u”.
The display coordinates of the characters "i", "n", "do", and "@" are associated with the period during which the AOB_ELEMENT and AOB_FRAME corresponding to the characters are reproduced. Then, the playback device changes the color of the portion indicated by the display coordinates of the character in the highlight coordinate table as the playback of the AOB proceeds as described in the first embodiment.

[0323] Thus, the playback device sets the AOB in the lyrics.
It is possible to perform a video display so that the user can see at a glance where the part is being reproduced, and it is possible to realize the reproduction like the current karaoke software. As described above, according to the present embodiment, by using two tables, the phrase period table and the highlight coordinate table, it is possible to precisely synchronize the sound reproduction and the lyrics display as in the current karaoke software. Becomes possible.

[0324]

The semiconductor memory card according to the present invention shows an audio sequence including a plurality of audio objects, a plurality of still picture objects, and an order in which the plurality of audio objects included in the audio sequence are reproduced. When a plurality of audio objects are reproduced using one or more reproduction path information and the reproduction order indicated in the one or more reproduction path information, one or more still image objects to be displayed together with the audio objects are First pointer information, which is information specified in association with reproduction path information, and one or more still image objects to be displayed only during a period in which a specific audio object is reproduced, among the plurality of audio objects. , The second information which is specified in association with the specific audio object. Since the pointer information and the pointer information are stored, a plurality of audio objects included in the audio sequence are reproduced in accordance with the reproduction order indicated in the reproduction path information. When the object exists, the still image object is designated in the first pointer information in association with the reproduction path information. Thus, a common still image object can be displayed in a time zone in which a plurality of audio objects included in the audio sequence are being reproduced.

[0325] Since a common still image can be assigned to a plurality of audio objects, an audio sequence corresponding to a music album with a low name recognition may be assigned to a still image object or the like while the plurality of audio objects are being reproduced. Can be saved, labor and cost required for image production can be saved.

Conversely, for an audio sequence corresponding to a music album with a high degree of popularity, a plurality of still images are assigned to each audio object during the period in which each audio object is being reproduced, and one audio object is assigned to each still image. By displaying a plurality of still image objects, each audio object can be reproduced luxuriously. By grasping the psychology of the artist's fans by displaying such still images, sales of audio sequences (music albums) can be increased.

[0327] If there is a still picture object, such as lyrics, that is desired to be displayed only during a period in which a specific audio object is being reproduced in addition to the background picture, such a still picture object is stored in the second pointer information. Can be assigned to a specific audio object. Here, the semiconductor memory card is further associated with each still image object, and indicates whether the corresponding still image object is designated by the first pointer information or the second pointer information, and is designated. For the still image object, a symbolic counter with a plurality indicating the number of designated pieces of the first pointer information and the second pointer information may be stored.

In this case, when the recording device of the semiconductor memory card deletes an audio object or an audio sequence, the second pointer information on the deleted audio object and the first pointer information on the deleted audio sequence are specified. And these first
The assigned number of the still image object whose display is designated by the pointer information and the second pointer information is decremented. If the number of assignments for any still image object has reached 0, the still image object is determined to be a still image object that is not referenced from any of the first pointer information and the second pointer information, and the still image object is deleted. Can be done. As described above, by deleting the still image object in conjunction with the deletion of the audio object, the storage efficiency of the semiconductor memory card can be improved.

[Brief description of the drawings]

FIG. 1 is a diagram showing a shape when a flash memory card 31 is viewed from above.

FIG. 2 is a diagram showing a shape when the flash memory card 31 is viewed from a lower surface thereof.

FIG. 3 is a flash memory card 31 according to the embodiment;
FIG. 3 is a diagram showing a hierarchical structure of FIG.

4A is a diagram showing a configuration of a system area, a protection area, and a user data area provided in a physical layer of the flash memory card 31. FIG. FIG. 3B is a diagram illustrating a configuration of a protect area and a user data area in a file system layer.

FIG. 5 is a diagram showing details of a configuration in a file system layer.

FIG. 6 divides AOB001.SA1 into five parts according to the cluster size, and divides each divided part into clusters 003, 004, 005, 00A, and 00C.
FIG. 3 is a diagram assuming a state of being stored in.

FIG. 7 is a diagram showing a setting example of a directory entry and a file allocation table when AOB001.SA1 is recorded in a plurality of clusters.

8 (a) and 8 (b) When storing these two data in the application layer, what directories are configured in the user data area and the protection area in the file system layer, and what files are stored in the directory. It is a figure which shows whether it is created under subordinate.

FIG. 9: AOBSA1.KEY under the SD_Audio directory
FIG. 6 is a diagram showing the correspondence between AOB files and AOB files.

FIG. 10 is a diagram hierarchically showing the data structure of an AOB file.

FIG. 11A is a diagram showing parameters described in ISO / IEC13818-7 in a table format. (B) is a diagram illustrating, in a table form, parameters to be used when encoding is performed in the MPEG-Layer3 (MP3) format. (C) is a diagram illustrating, in a table form, parameters to be used when encoding is performed by the Windows Media Audio (WMA) method.

FIG. 12 is a diagram showing details of the configuration of AOB_FRAME.

FIG. 13 shows three AOB_FRAMEs, each AOB_FR
FIG. 3 is a diagram illustrating how the byte length of audio data in AME is set.

FIG. 14 is a diagram showing the correspondence between sampling_frequency and the number of AOB_FRAMEs included in AOB_ELEMENT.

FIG. 15 is a diagram illustrating an example of the time length of AOB_ELEMENT and the time length of AOB_FRAME.

FIG. 16: Each AOB and AOB_BL recorded in the AOB file
It is a figure which shows what kind of reproduction content is reproduced by continuously reproducing OCK.

FIG. 17 shows Playlistmanager and T in the first embodiment.
It is the figure which detailed the configuration of rackManager step by step.

FIG. 18 is a diagram showing the sizes of PlayListManager and TrackManager.

19 is a diagram showing the interrelationship between the TKI shown in FIG. 17 and the AOB file and AOB shown in FIG. 16;

20 is a diagram showing a detailed data structure of TKTMSRT shown in FIG.

FIG. 21 is a diagram showing an example of TKTMSRT.

FIG. 22 is a diagram showing a detailed configuration of TKGI.

23A and 23B are diagrams showing a detailed configuration of a BIT. (C) A diagram showing a data format of a TIME_LENGTH field.

FIG. 24 is a diagram showing clusters 007 to 00E in which AOBs including AOB_ELEMENT # 1 to # 4 are stored.

FIG. 25: AOB_FR in arbitrary AOB_ELEMENT # y in AOB
FIG. 21 is a diagram illustrating how to set AOB_FRAME # x + 1 to be reproduced next when performing forward search reproduction from AME # x.

26 (a) and (b), when an arbitrary reproduction start time is designated, AOB, AOB_ELEMENT, AO corresponding to the designated time
It is a figure showing how to specify B_FRAME.

FIGS. 27A and 27B are diagrams assuming that a track is deleted.

FIG. 28A shows a state after a track is deleted a plurality of times.
It is a figure showing TrackManager. (B) The “Unused” TKI exists, and a new T
FIG. 11 is a diagram showing how writing is performed when writing KI and AOB files.

FIGS. 29A and 29B are diagrams showing how TKI is set when two tracks are integrated.

FIG. 30A is a diagram showing an AOB of Type 1; FIG. 4B is a diagram illustrating a Type 2 AOB.

FIG. 31 (a) is a diagram showing a case where a plurality of tracks are integrated into one by a combination of Type1 + Type2 + Type2 + Type1. (B) It is a figure which shows the case where a plurality of tracks are integrated into one by the combination of Type1 + Type2 + Type2 + Type2 + Type1.

FIG. 32 (a) AOB of Type 1 at the end of the preceding track
FIG. 11 is a diagram illustrating an arrangement pattern in which Type 1 AOBs are arranged at the beginning of a subsequent track. (B) Type 1 AOB is arranged at the end of the preceding track,
FIG. 14 is a diagram illustrating an arrangement pattern in which Type 2 AOBs are arranged at the beginning of a subsequent track. (C) AO at the end of the preceding track in the order of Type1 and Type2
FIG. 9 is a diagram showing an arrangement pattern in which a B is arranged and a Type 1 AOB is arranged at the beginning of a subsequent track. (D) AO at the end of the preceding track in the order of Type1 and Type2
B is allocated, and Type2, Type1
FIG. 6 is a diagram showing an arrangement pattern in which AOBs are arranged. (E) Type2, Type2 AOB at the end of the preceding track
FIG. 11 is a diagram illustrating an arrangement pattern in which Type 1 AOBs are arranged at the beginning of a subsequent track.

FIGS. 33A and 33B are diagrams assuming a case where one track is divided into two tracks.

FIG. 34 (a) and (b) AOB003.SA1 before and after division.
FIG. 11 is a diagram showing how the SD_Audio directory entry for the SD_Audio directory to which the “.” Belongs is described.

FIG. 35 (a) is a diagram assuming a case where an AOB is divided at an intermediate part of AOB_ELEMENT # 2. (B) AOB is split at the middle of AOB_ELEMENT # 2,
FIG. 11 is a diagram showing a state in which two AOBs, B # 1 and AOB # 2, have been obtained.

36 is a diagram illustrating how BIT is set when an AOB is divided as illustrated in FIG. 35.

FIG. 37 is a diagram specifically showing how BIT changes before and after division.

FIG. 38 is a diagram specifically showing how TKTMSRT changes before and after division.

FIG. 39 (a) is a diagram illustrating a format of DPL_TK_SRP. (B) It is a figure showing the format of PL_TK_SRP.

FIG. 40 is a diagram showing the interrelationship between Default_Playlist information, TKI, and AOB files.

FIG. 41 is a diagram showing a setting example of DefaultPlaylist and PlayList information in the same notation as in FIG. 40.

[FIG. 42] DPL_TK_SRP and TK using the same notation as FIG.
It is a figure which shows the correspondence with I.

43 (a) and (b) are diagrams assuming a case where the order of tracks is changed.

(A) and (b) of DefaultPlaylis shown in FIG.
Defa when deleting DPL_TK_SRP # 2 and TKI # 2 out of t
FIG. 7 is a diagram illustrating how an ultPlaylist, a TrackManager, and an AOB file are updated.

FIG. 45 (a) and (b) TKI of “Unused” and DPL_TK_SR
FIG. 11 is a diagram showing how writing is performed when a new TKI, DPL_TK_SRP, is written in this case where P exists.

FIGS. 46A and 46B are diagrams assuming a case where tracks are integrated;

FIGS. 47A and 47B are diagrams assuming that a track is divided;

FIG. 48 is a flash memory card 3 according to the embodiment.
FIG. 1 is a diagram showing a portable playback device for No. 1;

FIG. 49 is a diagram illustrating an example of display contents of a liquid crystal display when a playlist is selected.

FIGS. 50 (a) to 50 (e) are diagrams showing examples of display contents of a liquid crystal display when a track is selected.

FIGS. 51A to 51C are diagrams illustrating operation examples of a jog dial;

FIG. 52 is a diagram illustrating an internal configuration of a playback device.

FIG. 53 is a diagram showing how data input / output in the double buffer 15 is performed.

FIGS. 54A and 54B are diagrams showing how a cyclic area is secured using a ring pointer.

FIG. 55 is a flowchart showing a procedure of an AOB file reading process.

FIG. 56 is a flowchart showing a processing procedure of AOB_FRAME output processing.

FIG. 57 is a flowchart showing a processing procedure of AOB_FRAME output processing.

FIG. 58 is a flowchart showing a processing procedure of AOB_FRAME output processing.

59 (a) to (d) are diagrams showing a state where the reproduction elapsed time displayed in the time display frame of the liquid crystal display 5 increases as the variable Play_Time is updated.

FIG. 60 is a flowchart showing a processing procedure of the CPU 10 during forward search reproduction processing.

61 (a) to (d) are diagrams showing a state where the reproduction elapsed time is incremented during forward search reproduction.

FIGS. 62 (a) and 62 (b) are diagrams showing specific examples when a time search function is performed.

FIG. 63 is a flowchart showing a processing procedure of an editing control program.

FIG. 64 is a flowchart showing a processing procedure of an editing control program.

FIG. 65 is a flowchart showing a processing procedure of an editing control program.

FIG. 66 is a diagram illustrating an example of a recording device of a flash memory card 31.

FIG. 67 is a diagram illustrating a hardware configuration of a recording apparatus.

FIG. 68 is a flowchart showing a processing procedure of a recording process.

FIG. 69 is a diagram showing a hierarchical structure of a flash memory card according to the second embodiment.

FIGS. 70A and 70B are diagrams showing the internal structures of a user data area and a protection area in a file system layer.

FIG. 71 (a) is a diagram showing the internal structure of POBXXX.JPG. FIG. 3B is a diagram illustrating an internal configuration of a POB file including encrypted still image data. (C) is a diagram showing an example of a POB file in which a file path is stored instead of an encrypted entity part.

FIG. 72 shows PlayListManager and Tra in the second embodiment.
FIG. 3 is a diagram illustrating a detailed configuration of ckManager.

FIG. 73 is a diagram showing a state in which the POB file shown in FIG. 70 is specified by TKI_POB_SRP, PLI_POB_SRP, and DPLI_POB_SRP.

FIG. 74 is a diagram showing the data structure of TKI_POB_SRP and TKI_POB_ATR.

FIG. 75 is a diagram showing a setting example of TKI_POB_SRP for TKI # 1 to TKI # 3 included in the TrackManager.

FIG. 76 is a diagram showing a setting example of TKI_POB_SRP included in TKI # 4 to TKI # 8 included in TrackManager.

FIG. 77: DPLI_POB_SRP and DPLI_ included in DPLGI
It is a figure showing POB_ATR.

FIG. 78 shows 20 DPLIs included in Default_Playlist information
It is a figure showing the example of setting of _POB_SRP.

[Fig. 79] DPLI_POB_S included in Default_Playlist information.
10 is a timing chart showing how these are combined when a POB specified by an RP is set as a background image and a POB specified by TKI_POB_SRP included in a TrackManager is set as a foreground image.

[Fig. 80] Fig. 80 is a diagram illustrating how a foreground image and a background image are combined six minutes after the start of reproduction of Default_Playlist information.

FIG. 81 is a diagram illustrating how a foreground image and a background image are combined 16 minutes after the start of reproduction of Default_Playlist information.

FIG. 82: PLI_POB_SRP and PLI_POB included in PLGI
It is a figure showing _ATR.

FIG. 83: 20 PLI_POB_SRPs included in PlayList information
It is a figure showing the example of setting of.

[Fig. 84] Fig. 84 shows a case where a POB specified by PLI_POB_SRP included in Playlist information is set as a background image and a TKI included in TrackManager.
6 is a timing chart showing how these are combined when POBs specified by _POB_SRP are set as foreground images.

FIG. 85: Six minutes after the start of playback of Playlist information,
It is a figure showing how a foreground picture and a background picture are combined.

[Fig. 86] Fig. 86 is a diagram illustrating how a foreground image and a background image are combined 16 minutes after the start of reproduction of Default_Playlist information.

FIG. 87: Multiple DPLI_Ps in Default_Playlist information
This is an example of reducing the number of POB files by causing DPLI_POB_SRP to specify a common POB file among OB_SRPs.

FIG. 88: DPLI_POB_S included in Default_Playlist information
10 is a timing chart showing how these are combined when a POB specified by an RP is set as a background image and a POB specified by TKI_POB_SRP included in a TrackManager is set as a foreground image.

FIG. 89 is a diagram showing the internal configuration of POBMG.

FIG. 90 is a diagram showing how the playback device according to the second embodiment is used.

FIG. 91 is a diagram showing the appearance of only the playback device main body according to the second embodiment.

FIG. 92 is a diagram showing the internal configuration of the playback device according to the second embodiment.

FIG. 93 (a) is a diagram illustrating how still images stored in a plurality of VRAMs 61 are superimposed. (B) is a diagram showing how still images stored in a plurality of VRAMs 61 are superimposed.

FIG. 94 is a flowchart showing a processing procedure for foreground image display processing.

FIG. 95 is a flowchart showing a processing procedure of background image display processing.

FIG. 96 is a flowchart showing a processing procedure of background image display processing.

FIGS. 97A to 97C show what happens when the foreground picture specified by TKI_POB_SRP and the background picture specified by DPLGI are combined by the processing procedures shown in the flowcharts of FIGS. FIG. 9 is a diagram showing whether a composite image is displayed on the liquid crystal display 5.

FIGS. 98 (a) to 98 (c) show what happens when the foreground image specified by TKI_POB_SRP and the background image specified by PLI_POB_SRP are synthesized by the processing procedures shown in the flowcharts of FIGS. Liquid crystal display 5
FIG.

FIG. 99 is a flowchart illustrating a processing procedure of the recording apparatus according to the second embodiment.

FIG. 100 (a) is a diagram showing an example of a phrase period table. FIG. 4B is a diagram illustrating an example of a highlight coordinate table.

[Explanation of symbols]

 1 Card Connector 2 User Interface 3 RAM 4 ROM 5 Liquid Crystal Display 6 LCD Driver 7 Descrambler 8 AAC Decoder 9 A / D Converter 11 DPLI Resident Area 12 PLI Storage Area 13 TKI Storage Area 14 FileKey Storage Area 15 Double Buffer 21 Card connector 22 RAM 23 Fixed disk device 24 Converter 24 A / D step S 25 AAC encoder 26 Scramble unit 27 Modem device 28 CPU 29 Keyboard 30 Display 31 Flash memory card 32 Protect switch 61 VRAM

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06K 19/07 H04N 5/907 B 5D108 G10K 15/02 G06K 19/00 Q 5J104 G10L 19/00 N H04L 9 / 08 G10L 9/00 N H04N 5/907 9/18 JM H04L 9/00 601C (72) Inventor Tomokazu Ishikawa 1006 Ojidoma, Kadoma City, Osaka Prefecture Matsushita Electric Industrial Co., Ltd. (72) Inventor Shinji Inoue Osaka 1006, Kazuma, Kadoma, Matsushita Electric Industrial Co., Ltd. (72) Inventor Hideki Matsushima 1006, Kadoma, Kazuma, Kadoma, Osaka Pref. Matsushita Electric Industrial Co., Ltd. F term (reference) in Denki Sangyo Co., Ltd. 5B017 AA03 BA07 CA11 CA16 5B035 AA00 AA13 BB09 CA38 CA39 5B058 CA13 CA27 KA02 KA04 KA06 KA08 KA35 YA16 5C052 AA17 AC08 BB04 BB10 CC11 CC20 GA02 GA03 GB00 GB07 GB09 GC00 GC05 GD01 GE08 5D045 DA20 DB01 5D108 BA06 BA24 BB04 BD02 BE06 BG06 CA04 CA07 CA15 CA29 5J104 A

Claims (15)

[Claims] 1. An audio sequence including a plurality of audio objects, a plurality of still image objects, and at least one reproduction path information indicating an order in which the plurality of audio objects included in the audio sequence are reproduced; When a plurality of audio objects are reproduced using the reproduction order shown in one or more reproduction path information, one or more still image objects to be displayed together with these are displayed.
First information which is information specified in association with the reproduction path information
Pointer information, and information that specifies one or more still image objects to be displayed only during a period in which a specific audio object is played out of the plurality of audio objects in association with the specific audio object. A semiconductor memory card storing certain second pointer information. 2. The specific audio object:
Music data, the plurality of still image objects include a still image object indicating lyrics of the music data, and the second pointer information associates the still image object indicating lyrics of the music data with the music data. 2. The semiconductor memory card according to claim 1, wherein the memory card is designated by a key. 3. The semiconductor memory card is further associated with each still image object, and indicates whether or not the corresponding still image object is designated by the first pointer information or the second pointer information. 2. A still image object according to claim 1, wherein a plurality of symbolic counters indicating the designated number of the first pointer information and the second pointer information are stored. Semiconductor memory card. 4. A plurality of still image objects are encrypted, and the semiconductor memory card further includes identification information for each of the plurality of still image objects, and the still image object is encrypted. Management information including additional information indicating whether or not the still image object has been stored, position information indicating the storage position of the still image object, and key information for decrypting the encrypted still image object. Of the equipment
One or more decryption keys that can be accessed only by the device whose authenticity has been authenticated are stored. The first pointer information and the second pointer information can be determined by using the identification information in the first management information. 2. The semiconductor memory card according to claim 1, wherein said still image object is designated. 5. The semiconductor memory card is an area that can be freely accessed by a device connected to the semiconductor memory card only when the validity of the device is authenticated, and the one or more decryption keys are The audio sequence, the plurality of static areas, and a protected area that is stored and a non-protected area that is accessed by the device regardless of whether the validity of the device is authenticated. The image object, the plurality of pieces of reproduction path information, the first pointer information, the second pointer information, and the management information are stored in the non-protected area. 5. The semiconductor memory card according to claim 4, wherein the encrypted data is encrypted using one or more decryption keys in the protected area. 6. A plurality of encrypted still image objects, a plurality of decryption keys are stored in a protected area, and the plurality of decryption keys are arranged in a predetermined order to form a decryption key sequence. 6. The semiconductor according to claim 5, wherein the identification information about the encrypted still image object includes a key number indicating the position of a corresponding decryption key in the decryption key sequence. Memory card. 7. An audio sequence including a plurality of audio objects, a plurality of still image objects,
When a plurality of audio objects included in an audio sequence are reproduced, first pointer information specifying a still image object to be displayed together with the plurality of audio objects, and a still image to be displayed only during a period in which a specific audio object is reproduced A reproducing device for a semiconductor memory card storing a second pointer information for designating an image object in association with the specific audio object, wherein the reproducing device sequentially reproduces the audio objects included in the audio sequence; Display means for displaying at least one still image object specified by the first pointer information throughout the entire time period in which a plurality of audio objects included in the audio sequence are reproduced; and wherein the specific audio object is reproduced. Wait for That is, once the playback of the audio object is started, throughout the playback period of the audio object,
And a control unit for displaying a still image object specified by the second pointer information on a display unit. 8. The composition unit according to claim 1, wherein the control unit combines at least one still image object assigned to the audio sequence by the first pointer information with a still image object assigned to the audio object by the second pointer information. The playback device according to claim 7, wherein an image is displayed. 9. A recording device for a semiconductor memory card storing an audio sequence including a plurality of audio objects and a plurality of still image objects, wherein a plurality of audio objects among the plurality of still image objects are reproduced. Allocating means for allocating a still image object to be displayed during the entire time zone to the audio sequence, and allocating the still image object to be displayed during the time zone in which the specific audio object is reproduced to the specific audio object; The semiconductor pointer stores first pointer information indicating the one assigned to the audio sequence among the plurality of still image objects and second pointer information indicating the one assigned to each audio object among the plurality of still image objects. Recording apparatus comprising: a recording means for recording on the card. 10. An audio sequence including a plurality of audio objects, a plurality of still image objects, and a plurality of audio objects included in the audio sequence, when playing, specify a still image object to be displayed together with the audio objects. A semiconductor memory card storing pointer information and second pointer information for designating a still image object to be displayed only during a period in which a specific audio object is reproduced in association with the specific audio object A recording medium which records a program for causing a computer to perform a reproducing procedure for the computer in a computer-readable format, the reproducing step sequentially reproducing audio objects included in the audio sequence, and Little A display step of displaying at least one still image object during the entire time period during which a plurality of audio objects included in the audio sequence are played; andawaiting the playback of the specific audio object, and playing back the audio object. Once started, throughout the playback duration of the audio object,
A computer-readable recording medium on which a program for causing a computer to perform a procedure including a control step of displaying a still image object designated by second pointer information on a display step is recorded. 11. The control step includes: synthesizing at least one still image object assigned to the audio sequence by the first pointer information with a still image object assigned to the audio object by the second pointer information. 11. The computer-readable recording medium according to claim 10, wherein an image is displayed. 12. A computer-readable program for causing a computer to perform a recording procedure for a semiconductor memory card storing an audio sequence including a plurality of audio objects and a plurality of still image objects. A recording medium, wherein, among a plurality of still image objects, a still image object to be displayed throughout an entire time zone in which a plurality of audio objects are reproduced is assigned to an audio sequence, and a specific audio object is reproduced in a time zone in which the specific audio object is reproduced. An allocating step of allocating a still image object to be displayed to the specific audio object; first pointer information indicating one of the plurality of still image objects allocated to the audio sequence; and a plurality of still image objects. Recording a second pointer information indicating an audio object assigned to each audio object on a semiconductor memory card, and recording the program on a semiconductor memory card. Recording medium. 13. A method for designating an audio sequence including a plurality of audio objects, a plurality of still image objects, and a still image object to be displayed together with the plurality of audio objects included in the audio sequence when the plurality of audio objects are reproduced. A semiconductor memory card storing pointer information and second pointer information for designating a still image object to be displayed only during a period in which a specific audio object is reproduced in association with the specific audio object A playback step of sequentially playing back audio objects included in the audio sequence, and at least one still image object specified by the first pointer information is converted into a plurality of audio objects included in the audio sequence. Displaying the audio object during the entire time zone in which the audio object is reproduced; and waiting for the specific audio object to be reproduced, and when the reproduction of the audio object is started, during the reproduction period of the audio object,
A control step of displaying a still image object designated by the second pointer information on a display step. 14. The control step comprises: synthesizing at least one still image object assigned to the audio sequence by the first pointer information with a still image object assigned to the audio object by the second pointer information. 14. The reproducing method according to claim 13, wherein an image is displayed. 15. A recording method for a semiconductor memory card storing an audio sequence including a plurality of audio objects and a plurality of still image objects, wherein a plurality of audio objects among the plurality of still image objects are reproduced. Assigning a still image object to be displayed during the entire time period to the audio sequence, and assigning the still image object to be displayed during the time period in which the specific audio object is reproduced to the specific audio object; The first pointer information indicating the one assigned to the audio sequence among the plurality of still image objects and the second pointer information indicating the one assigned to each audio object among the plurality of still image objects are derived. Recording method characterized by comprising a recording step of recording on the memory card.