JP2003099098A - Semiconductor memory card, editing device, editing method, computer-readable recording medium - Google Patents

Abstract

(57) [Summary] [Problem] In conjunction with the deletion of the audio object,
A semiconductor memory card capable of improving the storage efficiency of a semiconductor memory card by deleting a still image object. A “POB_RCN” field in management information of a still image object (POB) indicates that the display of the POB is DPLGI or PLG.
Indicates whether it is specified by I or TKGI, and if specified, the number of times it is specified is described. If the TKI that specified the POB is deleted, this field is decremented by the number of deleted TKIs. Also Default_Playlis
When the t information and PlayList information are deleted, the deleted T
It is decremented by the number of KI. POB_refernce_count is 0
In such a case, the number of POBs stored in the flash memory card can be reduced by deleting the POB file.

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 image data, and control data, an editing device, a reproducing method, an editing method, and a computer-readable recording medium, and more particularly to electronic music distribution. The present invention relates to an improvement in storing audio data, image data, and control data distributed as content in the content distribution service of.

[0002]

2. Description of the Related Art Electronic music distribution, which makes it possible to purchase music contents on the Internet, can be a trigger for activating the music market, and the infrastructure for realizing it is being steadily improved. is there. The above-mentioned semiconductor memory card is a portable recording medium that is suitable for storing music contents purchased from electronic music distribution and carrying the contents, and it is expected that the demand thereof will dramatically increase in the future.

[0003] Music contents include "media mix" type music contents which are not only capable of music reproduction but also capable of displaying images related to the music together with music reproduction. The image showing the lyrics and the image that becomes the background image are recorded in the recording medium together with the karaoke music,
"Karaoke software," which displays lyrics when playing karaoke music, is a typical "media mix" type of music content. We must also consider the distribution and sale of content. Along with this, a more specific study of the storage method for storing "media mix" type music content in a semiconductor memory card will be required.

Now, 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 storing method in the recording medium will be described.
In order to perform music playback and image display, the conventional "media mix" type music content is a recording medium of multiplexed data obtained by multiplexing audio data of music and image data showing lyrics and background images. The audio data is reproduced and the image data is displayed at the same time. CD-Gra is used for recording media that realized image display during audio data playback by multiplexing.
There is something called phics (subcode Graphics). One unit of multiplexing in this CD-Graphics consists of 16-bit main code and sub-code. Audio data is assigned to 16-bit main code, and image data such as lyrics and background image is assigned to sub-code. ing.
When playback of any of the music contents recorded on the CD-Graphics is started, the audio data assigned to the 16-bit main code is played sequentially, and the image data assigned to the sub-code is displayed sequentially. .

[0005]

By the way, when an attempt is made to produce a music album consisting of a plurality of music contents in accordance with the above-mentioned audio data-image data multiplexing system, images are provided uniformly for each music content. That is, the conventional audio data-image data multiplexing method is required to allocate at least one image to each music content, which causes a problem that a maker has to make such an image. ..

[0006] However, for music albums of high-profile artists, it will be welcomed by consumers that different images are provided for each music content, and it is expected that the sales of music albums will be large. , It is likely that the labor and cost will be paid. On the other hand, for music albums of artists with low popularity, even if different images are provided for each music content, the reaction of consumers will be slow, and it can not be expected that sales of music albums will be large, so it takes time and effort. It is likely that the cost will not be paid.

Whether or not the labor and expense required for image production are rewarded is clear that there is a large difference between a music album with a high name recognition and a music album with a low name recognition. The multiplexing method has been unsatisfactory for the producer in this respect because it is required to allocate at least one image to each music content regardless of the name recognition of the artist and the expected number of sales.

It is an object of the present invention to provide a semiconductor memory card which can reduce the time and effort for producing an image to be assigned to each music content when producing a music album consisting of a plurality of music contents.

[0009]

[Means for Solving the Problems] 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, the background image to be displayed may be shared when playing a plurality of music contents. For example, if multiple music contents are written, composed and sung by the same person,
By displaying a common photo of the person as a background image when playing those multiple music contents,
A method of storing audio data (audio object) and image data (still image object) that saves the maker's effort can be considered.

In order to achieve common use of image data (still image objects) among a plurality of music contents, the semiconductor memory card according to the present invention has a plurality of audio objects, still image objects, reproduction path information, A semiconductor memory card that stores first pointer information, second pointer information, and a symbolic counter, wherein the reproduction path information indicates a reproduction order of audio objects, and the first pointer information corresponds to the reproduction path information. The second pointer information corresponds to a specific audio object and indicates the reproduction order of the still image objects during the entire reproduction time of the audio object according to the reproduction path information. Shows the playback order of still image objects during time, The symbolic counter is 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. Regarding the designated still image object, , The number of designations by the first pointer information and the second pointer information is indicated.

[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 subsequent sentence is attached with a classification number having the following system at the beginning of the sentence.

{X1-x2_x3-x4} The number of digits of the classification number means the hierarchical depth of the item. Specifically, x1 is the drawing number quoted in the description. The figures attached to this specification are numbered according to the order in which they are cited in the specification, and therefore the order of the figure numbers is almost the same as the order of description. x2 indicates the order of description when the description is given with reference to the diagram shown in x1. x3 indicates the drawing number of the explanatory diagram when the explanatory diagram is cited in order to explain the components of x2 in more detail, and x4 indicates
The order of the description in the case of referring to the diagram shown in x3 will be described.

(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 the shape of the flash memory card 31 when viewed from the top, and FIG. 2 is a diagram showing the structure when the flash memory card 31 is viewed from the bottom. 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 in width.
The thickness is about 2.0 mm and the thickness is about 2.0 mm, which is a size (stamp size) that can be held with a fingertip. Nine connectors are provided on the bottom surface for connection with devices, and on the side surface, there is a protect switch 32 that allows the operator to set whether to allow or prohibit overwriting of stored contents. Has been.

{3-1} Physical Structure of Flash Memory Card 31 FIG. 3 shows the semiconductor memory card (hereinafter,
FIG. 3 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, but the logical structure of each layer is 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, and each sector stores 512 bytes of digital data. For example, in case of 64MByte type flash memory card 31, its memory capacity is 67108864 (= 64 × 1024 × 1024)
The number of valid sectors at this time is 131072 (= 6710
8864/512). Furthermore, if the number of alternative sectors for error is subtracted from this valid sector, the number of remaining valid sectors will be
It will be 128,000, and various data will be recorded here.

{3-2_4A-1} Three areas in the physical layer The area formed by these effective sectors is shown in FIG. 4 (a).
Three areas are provided. FIG. 4A is a diagram showing a “system area”, a “protected 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 read the data freely, and its internal area depends on the file system. It is managed. The “system area” is an area in which a media ID having a unique value for each flash memory card 31 is stored. The user data area is writable, whereas the system area is read-only and the media ID stored therein cannot be rewritten.

Like the user data area, the "protected area" is an area in which data can be written. The difference from the user data area is that data can be freely read and written in the user data area, whereas in the protected area, the device connected to the flash memory card 31 is
Reading and writing can be performed only when the flash memory card 31 confirms mutual validity, that is, only when mutual authentication between the flash memory card 31 and a device connected to the flash memory card 31 is successful. This is a possible point.

{3-2_4A-2} Usage of three areas in the physical layer When a device connected to the flash memory card 31 writes data in the flash memory card 31, depending 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 a FileKey). This File
The Key can be freely set by the copyright holder, and the copyright of the data is protected by this alone, but the FileKey itself used for this encryption is also encrypted for the sake of completeness. When encrypting the FileKey itself, what is used as a key is an arbitrary value obtained by applying the media ID stored in the system area to a predetermined arithmetic expression, and the protected area is the arbitrary value. Store the FileKey encrypted using. Data that requires copyright protection is encrypted using a specified FileKey, and this 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 is improved. Next, the configuration of the file system layer existing on this physical layer will be described. The file system layer of the DVD is a UDF (universal disk format) type file system, whereas the file system layer of the flash memory card 31 is a FAT type file system (FAT: FAT: FAT: FAT: FAT: FAT).
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 protect area and the user data area in the file system include a “partition boot sector”, a “file allocation table (FAT)”, a “root directory entry”, and
It is also apparent from this figure that the data area is included and both the protect area and the user data area have the same structure. FIG. 5 is a diagram showing the details of these file system configurations. Hereinafter, the configuration of the user data area will be described with reference to FIGS. 4 and 5.

{3-2_4B-2} partition boot sector "partition boot sector" is a flash memory card 31 loaded in a general-purpose personal computer,
When the flash memory card 31 is assigned to the boot disk of the operating system of the general-purpose personal computer, this is a sector in which the contents that the general-purpose personal computer should refer to at the time of booting are described.

{3-2_4B-3_5} data area The "data area" is an area accessed by the device connected to the flash memory card 31 with the cluster as the minimum unit. The sector size of the flash memory card 31 is 512 bytes, while the cluster size is 16 Kbytes, so 3 in the file system layer.
Data is read and written in units of two sectors. The reason for setting the cluster size to 16K bytes is as follows. That is, when writing data to the flash memory card 31,
The data stored in must be erased once before writing data. In the flash memory card 31, the size in which such data can be erased is 16 Kbytes. Therefore, by setting the cluster size to this erasable size,
Data writing is performed appropriately. Figure 5
The dashed lead line ff2 in (1) indicates a plurality of clusters 002, 003, 004, 005 ... Included in the data area. In the figure, the numbers 002, 003, 004, 005, 006, 007, 008 ... Show the 3-digit hexadecimal notation cluster numbers assigned to identify each cluster. Since the access to the data area is performed with the cluster as the minimum unit, the internal position of the data area is designated using these cluster numbers.

{3-2_4B-4_5} File allocation table "File allocation table" is based on ISO / IEC 9293
It has a file system structure conforming to
It consists of a FAT value. Each FAT value is associated with each cluster, and when the corresponding cluster is read, it indicates which cluster should be read next. The broken line ff1 in FIG. 5 indicates a plurality of FAT values 002,003,004,005, ... Included in the file allocation table. The numerical value “002,003,004,005 ...” given to this FAT value indicates which cluster each FAT value is associated with, that is, each FAT value.
Indicates the cluster number of the cluster with which the value is associated.

{3-2_4B-5_5-1} Root directory entry "Root directory entry" is information indicating what kind of file exists in the root directory. Specifically, the root directory entry includes 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 "The first cluster number of the file" in which the beginning part of is stored is described.

{3-2_4B-5_5-2} Directory Entry of Subdirectory Information about files in the root directory is:
Although described in this root directory entry, information about the subdirectory is not described in this root directory entry. Directory entries for subdirectories are 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, and this SD_Audio directory entry is similar to the root directory entry as the “file name” of a file existing in that subdirectory. The "extension" of the file, the "file attribute", the "update time and date" of the file, and the "file first cluster number" in which the head of the file is stored are described.

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

{3-2_4B-5_7-1} When the AOB file storage method AOB001.SA1 is divided and stored, the directory entry and the 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 part of AOB001.SA1 is recorded in the cluster 003, the "first cluster number" in the SD_Audio directory entry contains the cluster number 003 of the cluster in which the head part is stored. . After that, it can be seen that the subsequent portion of AOB001.SA1 is stored in the cluster 004 and the cluster 005. FAT value 003 (004) corresponds to cluster 003 that stores the first part of AOB001.SA1.
This FAT value indicates the cluster 004 that stores the subsequent portion of the AOB file. In addition, clusters 004 and 005 that store the parts that follow it have a FAT value of 00.
4 (005) and FAT value 005 (00A) correspond, but the FAT value of this indicates the cluster 005,00A storing the next succeeding part of the AOB file.

If the cluster numbers described in these FAT values are sequentially read as shown by arrows fk1, fk2, fk3, fk4, fk5 ..., All the divided parts 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 with the cluster as the minimum unit, and the FAT value is associated with each cluster. A cluster that stores the end of the AOB file (in the example of FIG. 7, cluster 00C)
In the FAT value associated with, the cluster number "FFF" indicating that the cluster stores the last part of the file is described.

The description of the file system of the flash memory card 31 of the present invention is completed above.
The configuration of the application layer existing on the above-mentioned file system will be described. {3-3} Outline of application layer in flash memory card 31 Outline of application layer in flash memory card 31 is as follows.
As described in FIG. As indicated by the 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 indicated by a broken line PN2 in the figure, the presentation data includes an audio object group (AOB group) obtained by encoding voice data such as music, and the navigation data is a playlist manager. (PlaylistManager (PLMG)),
Includes Track Manager (TKMG). {3-3_8A, B-1} directory structure FIGS. 8 (a) and 8 (b) show what kind of data is stored in the user data area and protect area in the file system layer when these two data are stored in the application layer. It is a figure which shows a directory is formed and what kind of file is created under the said directory. "SD_AUDIO.PLM" and "SD_AUDIO.TKM" in this figure are files containing navigation data such as playlist manager (PlaylistManager (PLMG)) and track manager (Track Manager (TKMG)).
1 ”“ AOB002.SA1 ”“ AOB003.SA1 ”“ AOB004.SA1 ”
Is a file that stores audio objects that are presentation data (hereinafter referred to as an AOB file).

The extension "SA" in "AOB0xx.SA1" is
Abbreviation of "Secure Audio", and these stored contents indicate that there is a need for copyright protection (note that only eight AOB files are described in Fig. 8 (a). This is just an example, the SD_Audio directory can store up to 999 AOB files.) When the presentation data requires copyright protection as described above, 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. The encryption key storage file AOBSA1.KEY contains FileKeys # 1 to # 8, which are encryption key strings formed by arranging multiple encryption keys FileKey in a predetermined order.
Is stored.

In electronic music distribution, the server computer of the music company uses SD_Audio shown in FIGS. 8 (a) and 8 (b).
If the consumer holds a directory and a purchase request for the music content is issued by the consumer, the SD_Audio directory is compressed and encrypted, and then the SD_Audio directory owned by the consumer who issued the purchase request is sent via the public network. To send. When the computer owned by the consumer receives this SD_Audio directory, it decrypts this directory and decompresses it to obtain an SD_Audio directory. Including all networks that are open to the public, such as wireless communication networks typified by mobile phones). The AOB file may be downloaded from the server computer of the 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.

Correspondence between {3-3_9-1} AOBSA1.KEY and AOB File FIG. 9 is a diagram showing the correspondence between AOBSA1.KEY and SDB audio files under SD_Audio. 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 placed in the same directory name as the directory in which the encrypted file is stored. Since the AOB file is placed in the SD_Audio directory and the encryption key storage file is also placed in the SD_Audio directory in the user data area of FIG. 9, it can be seen that the files are arranged according to this rule. ..

(2) The encryption key storage file is given a file name in which the first three characters of the file name of the AOB file in the data area are combined with a predetermined extension ".key". If the file name of the AOB file is "AOB001.SA1", the encryption key storage file will contain the first three characters "AOB", "SA1", and the extension ".key" in the encryption key storage file, as indicated by arrows nk1 and nk2. It can be seen that the file name "AOBSA1.KEY" consisting of "" 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 start position of the area in which each File Key in the encryption key storage file is stored. . On the other hand, the file name of the AOB file is "001", "00
Serial numbers such as 2 "," 003 ", and" 004 "are assigned. The serial number in these AOB files means the position of the corresponding FileKey in the encryption key sequence, so each AOB file Fil used when encrypting the file
eKey has the same serial number as “File Key Entr
y'will exist. Arrows AK1, AK2, AK3 in Fig. 9
Indicates the correspondence between the AOB file and the FileKey. That is,
AOB001.SA1 in the user data area is "File Key Ent
It corresponds to the FileKey stored in "ry # 1", and AOB00
2.SA1 is the FileKe stored in “FileKey Entry # 2” or later.
y and AOB003.SA1 indicate that they correspond to File Keys stored after “File Key Entry # 3”. As can be seen from (3) above, the FileKey used to encrypt the AOB file
Is different for each file, and they are the same as the serial numbers such as "001", "002", "003", "004" embedded in the file name and "File Key Entry ”. Each AOB file is encrypted using a different FileKey, so even if the encryption key of a specific AOB file is exposed,
Other AOB files cannot be decrypted using the exposed FileKey. This will minimize the damage if the FileKey is exposed when the AOB file is encrypted.

{3-3_10-1} Internal Structure of AOB File Next, the internal structure of the AOB file will be described. Figure 1
0 is a diagram hierarchically showing the data structure of the AOB file. The first row of this 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 AOB, and includes ADTS header and ADT
S (Audio Data Transport Stream) format audio data. Audio data in ADTS format is MPEG
16K encoded with 2-AAC [Low Complexity Profile]
Stream data that is played back at a transmission rate of bps to 144 Kbps (Note that PCs recorded on existing compact discs
Since the transmission speed of M data is 1.5 Mbps, it can be seen that it is much lower than that of 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, further encrypted, transmitted over the public network, and transmitted to the consumer. The AOB file stores the audio data transport stream thus transmitted by dividing it into AOB_FRAME sequences.

{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
Refer to Advanced Audio Coding (AAC). It should be noted here that the AOB is compressed by the MPEG2-AAC method applied by limiting the parameter table described in ISO / IEC13818-7 as shown in FIG. 11 (a). . Figure 1
1 (a) is a diagram showing a parameter table described in ISO / IEC13818-7, in which a Parameter column, a Value column, and a Comm
It consists of a comment field indicating the contents of the ent field.

The parameter column "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, 16kH
z ”indicates that the sampling frequency is applied. Parameter field “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 in the MPEG-AAC system, AOB_FRAME is MPE.
G-Layer3 (MP3) method, Windows (registered trademark) Media Audio
(It may be encoded by another encoding method such as the WMA method. At this time, the parameter tables shown in FIGS. 11B and 11C are used instead of the parameters shown in FIG. 11A. Must be used.

{3-3_10-2_12} Structure of AOB_FRAME "AOB_FRAME" includes audio data encoded under the above restrictions, but the data length of the audio data included in AOB_FRAME has a reproduction time of 20 mm. It's just data in seconds. However, since the MPEG2-AAC method is a variable length coding method, the data length of audio data included in each AOB_FRAME differs for each AOB_FRAME. Hereinafter, the details of the configuration of AOB_FRAME will be described with reference to FIG. The first row of this figure is AOB_FRAME
And the second row shows how each part of AOB_FRAME is encrypted. By referring to the second row, it can be seen that the ADTS header is not encrypted, that is, is not encrypted. Also, the audio data includes both an encrypted part and a non-encrypted part. The encrypted part consists of multiple 8-byte encrypted data. 8 bytes of encrypted data is 6
It is generated by encrypting 4-bit original data using a 56-bit FileKey. The non-encrypted part is left unencrypted because it 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 the non-encrypted part. The ADTS header is 7 bytes and contains a 12-bit sync word (set to FFF),
The data length of audio data included in the same AOB_FRAME and the sampling frequency when encoding the audio data are described. {3-3_10-3_13} Setting the byte length of AOB_FRAME Fig. 13 shows the AOB_FR for each of the three AOB_FRAMEs.
It is a figure which shows how the byte length of the audio data in AME is set. In this figure, AOB_FRAM
Audio data # 1 included in E # 1 has a data length of 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.If the data lengths are different from each other, such as x1, x2, x3, the data length will be written Data length x2 is described in the ADTS header included in AOB_FRAME # 2, and 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 determine where the subsequent AOB_FRAME exists. You can get it. This is the end of the description of AOB_FRAME.

{3-3_10-4} AOB_ELEMENT Next, in FIG. 10, the AOB_ELEMENT located at the fourth level
Will be described. "AOB_ELEMENT" is a set of consecutive AOB_FRAMEs. Where 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 _FRAME is the AOB_FRAME included in the AOB_ELEMENT.
The playback time is set to about 2 seconds, and the number of playbacks varies depending on the sampling frequency and the encoding method.

AO included in {3-3_10-5_14} AOB_ELEMENT
B_FRAME Number FIG. 14 is a diagram showing the correspondence between sampling_frequency and the number of AOB_FRAME included in AOB_ELEMENT. In the figure, N indicates the reproduction period of AOB_ELEMENT in seconds, and is "2" if the encoding method is MPEG-AAC. If sampling_frequency is 48kHz, AOB_ELEMENT
The number of frames included in is 94 (= 47 × 2), and sampli
When ng_frequency is 44.1kHz, the number of frames included in AOB_ELEMENT is 86 (= 43 × 2) and sampling_frequency is
At 32kHz, the number of frames included in 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
When it is 22.05kHz, the number of frames included in AOB_ELEMENT is 44 (= 22 × 2), and when sampling_frequency is 16kHz, the number of frames included in AOB_ELEMENT is 32 (= 16 × 2).
It becomes an individual. However, if you edit the AOB by splitting it, A
The number of AOB_FRAME of the first and last AOB_ELEMENT of OB is shown in FIG.
May be less than the number of.

No special information such as a header is added to AOB_ELEMENT, but instead, the data length is shown 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 showing an example of time length of AOB_ELEMENT and AOB_FRAME. The first row of this figure shows multiple AOB_BL
The OCK sequence, and the second row shows the sequence of multiple AOB_ELEMENTs. The third row shows the arrangement of multiple AOB_FRAMEs.

Referring to this figure, AOB_ELEMENT is about 2.0.
It corresponds to the playback time length of seconds, and AOB_FRAME in this figure
It can be seen that 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 reproduction and reverse search reproduction by referring to SRT_entry, it is possible to realize intermittent reproduction of skipping 2.0 seconds and reproducing for 240 milliseconds.

{3-3_10-7} About AOB_BLOCK Above, the explanation about AOB_ELEMENT is finished, and then AOB_E
A higher order of LEMENT, that is, AOB_BLOCK located in the third row in the diagram showing the data structure of the AOB file in FIG. 10 will be described. "AOB_BLOCK" is a valid AOB_ELEMENT
This is an area consisting of 1 and exists in the AOB file. A
OB_ELEMENT corresponds to a playback time of 2 seconds, while AOB_BLOCK corresponds to a playback time of up to 8.4 minutes. The reason that each AOB is limited to the playback time of 8.4 minutes is that the size of the time search table is suppressed to 504 bytes or less by limiting the number of AOB_ELEMENT included in AOB_BLOCK.

{3-3_10-8} Suppression of Time Search Table Below, 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 millisecond playback" is performed in which reading for 2 seconds is skipped and playback is performed for 240 milliseconds. In this way, when skipping the time length of 2 seconds, as a rule, AOB_FRAM
It is enough to refer to the data length shown in the ADTS header of E in order, but in that case, 100 (= 2 seconds / 20 milliseconds) AOB_FRAME to skip the time interval of 2 seconds.
Must be sequentially detected, which imposes an extra processing load on the playback device. 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 backward search reproduction are instructed, the reproducing device refers to this. Good. That is,
The time search table contains information for calculating the read destination address 2 seconds ahead and 4 seconds ahead, specifically, each AOB_ELEMEN
The data length for T is described in advance, and the playback device may perform forward search playback-reverse search playback with reference to this. Consider how the data length corresponding to 2 seconds becomes. The bit rate during playback of audio data is 16 Kbps to 144 Kbps as described above.
, The data length that is played back every 2 seconds is 4
Kbyte (= 16Kbps x 2/8) to 36Kbyte (= 144Kbps x 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 the audio data requires 2 bytes (16 bits). This is because if you assign a 16-bit length 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 entry to be provided in this time search table is 252 (= 504 / 2) Must be limited to As described above, since the entry is provided every 2 seconds, the reproduction time corresponding to 252 entries is 504 seconds (= 2 seconds × 252), which is 8 minutes and 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 set to 504 bytes or less.

{3-3_10-9} AOB The description of AOB_BLOCK has been completed, and then the AOB will be described. The AOB located in the second row of FIG. 10 is the AOB.
It is an area with invalid area before and after _BLOCK, and AOB
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 and written together with the AOB_BLOCK. In the AOB, which part of the AOB_BLOCK corresponds to is specified by BIT included in the navigation data (details thereof will be described later).

From the above, it became clear what kind of data is stored in each AOB file. Then, in FIG.
The following describes what kind of content is reproduced by continuously reading out the AOB and AOB_BLOCK included in the eight AOB files shown in FIG. {3-3_10-10_16} Figure 16 shows each AOB and AOB_BL recorded in the AOB file.
It indicates what kind of reproduction content is reproduced by continuous reproduction of OCK. The first row shows eight AOB files in the user data area, and the second row shows each AOB file.
The eight AOBs contained in the AOB file are shown. The third row shows eight AOB_BLOCKs included in each AOB.

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

Referring to these broken lines, the AOB_Block included in each AOB # 1 is the song played at a time of 6.1 minutes.
(SongA), AOB_Block included in each AOB # 2 is a song played in 3.3 minutes (SongB), AOB_Block included in each AOB # 3 is a song played in 5.5 minutes (Son
gC). As above, AOB001.SA1 ~ AOB003.SA1
You can see that each corresponds to an independent song. The sixth row shows a track sequence consisting of Tracks A to E. These TrackA to E are SongA, SongB, SongC,
There is a one-to-one correspondence with each of the five songs, SongD and SongE, and they are treated as one independent playback unit.

On the other hand, AOB # 4 is the beginning part of the song (Song D) reproduced at a time of 30.6 minutes, and is reproduced at a reproduction time of 8.4 minutes. AOB_BLOC included in AOB # 5 and AOB # 6
K is the middle part of SongD, with a playback time of 8.4 minutes, AOB
AOB_BLOCK included in # 7 is the end part of SongD, and 5.
It is played with a playback time of 4 minutes. Thus, a song with a play time of 30.6 minutes is (8.4 minutes + 8.4 minutes + 8.4 minutes + 5.4 minutes
You can see that each AOB is divided by the unit of minutes. As can be understood from this figure, it can be seen that all the songs included in the AOB file are recorded within the playback time of 8.4 minutes.

From the above description, it became clear that by limiting the reproduction time length of the AOB, the data size of the time search table associated with each AOB is also limited. Next, the navigation data including this time search table will be described. {3-3_8A, B-2} Navigation data is "SD_Audio.PLM""SD_Audi
As mentioned above, it consists of two files, "o.TKM". The file "SD_Audio.PLM" contains a playlist manager (Playlistmanager),
Audio.TKM ”includes a track manager.

As described in the description of the presentation data, the plurality of AOB files record the encoded AOBs, but how long the reproduction time of these AOBs is and how long each AOB is There is no description of what the song name is and who the composer is. On the other hand, since the plurality of AOBs are only recorded in the plurality of AOB files, there is no description about the order in which they are played. The track manager and playlist manager are provided to notify the playback device of such information.

Here, the track manager shows the correspondence between the AOBs recorded in the AOB file and the tracks, how long the playback time of these AOBs is, and what song name each AOB has. And includes a plurality of track management information indicating various information such as who the composer is. A track is a unit of reproduction that is meaningful to the user. When a music work is stored in the flash memory card 31, a track corresponds to a song, and a reading book is stored in the flash memory card 31 ( A reading book is not a book but a document work represented by a reading voice.) If it is a book genre, a track corresponds to a chapter / section of a sentence. The track manager is provided to manage a plurality of AOBs recorded in a plurality of AOB files as a set of tracks.

The play list defines a plurality of reproduction orders of tracks, and the play list manager includes a plurality of such play lists. 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 the Playlistmanager and Track in the embodiment.
FIG. 18 is a diagram in which the configuration of the Manager is detailed step by step.
FIG. 6 is a diagram showing sizes of PlayListManager and TrackManager. That is, in the figure, the logical format located on the right side is a detailed version of the logical format located on the left side. It clarifies which part of the has been refined.

In accordance with such notation, Tr in FIG.
Referring to the configuration of ackManager, TrackManager indicates that 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 that describes text information specific to TKI
_Infomation_Data_Area (TKTXTI_DA), Track_Time_Serch_Table (TKTMSRT) having the role of time search table
You can see that it consists of. Referring to FIG. 18, TKI itself has a fixed size (1024 bytes), and TKGI and TKTXTI_DA
It can be seen that and have 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 ... # as shown by the broken line h3.
You can see that it consists of n and. Correlation between {17-2_19} TKI, AOB File and AOB FIG. 19 is a diagram showing a correlation between the TKI shown in FIG. 17 and the AOB file and AOB shown in FIG. The square frame in the first row of FIG. 19 is a track sequence consisting of TrackA to E, and the square frame in the second row of FIG. 19 is Trac.
FIG. 16 shows kManager, and the third and fourth stages show the eight AOB files shown in FIG. 8 frames in the 5th row are 8
Shows one AOB. These eight AOB files are the ones that recorded the eight AOBs shown in FIG. 16, and are TrackA and Trac.
It forms a music album that includes kB, TrackC, TrackD, and TrackE. The second row shows eight TKIs. The numbers "1", "2", "3", "4" assigned to these TKIs are serial numbers for identifying each TKI, and each TKI has the same serial number 0
It is associated with the AOB file with 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.
It can be seen that 02.SA1 and 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. ). In this way, each TKI has a one-to-one correspondence with the AOB recorded in each AOB file.
Information specific to AOB can be written in detail in KI.

Regarding the data structure of {17-3_20} TKTMSRT As information unique to the AOB recorded in the AOB file,
First, TKTMSRT will be described. 20 is shown in 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. Figure 20
In, the data size of the time search table header is 8 bytes, and TMSRT_ID (0th byte to 1st byte), reserved (2nd byte to 3rd byte), Total T
It has three fields, MSRT_entry_Number (4th to 7th bytes). "TMSRT_ID" contains TMSRT
Describes the ID that can uniquely identify the. 『Total TMSRT_en
“Try Number” describes the total number of TMSRT_entry in the TMSRT.

{17-3_21-1} Specific Example of TKTMSRT Next, the TKTMSRT will be described in more detail. Figure 21
FIG. 6 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 this figure
B consists of a plurality of AOB_ELEMENTs # 1, # 2, # 3 ... In addition, "0""32000""64200""9700" in the figure
Numerical values such as “0”, “1203400”, and “1240000” are occupied areas AR1 of each AOB_ELEMENT from the beginning of AOB_BLOCK included in AOB.
Indicates the relative address up to AR2, AR3, ARn-1, ARn. AOB_ELE
MENT # 2 indicates that it is recorded at a position separated by "32000" from the beginning 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 it is recorded at a position separated by "1203400" from the beginning of AOB_BLOCK.

It should be noted that the intervals between the head addresses of the occupied areas are not constant values, that is, the occupied areas of each AOB_ELEMENT occupy a plurality of clusters of different sizes. The size of each occupied area is different because the code allocation in each AOB_FRAME is variable length. The occupied size of each AOB_ELEMENT is different, so if you jump to the beginning of each AOB_ELEMENT,
It is necessary to instruct the playback device in advance where the OB_ELEMENT exists in the AOB. With such a purpose,
Multiple TMSRT_entry are listed. Arrow RT1, RT2, RT3
..... RTn-1 and RTn are occupied areas AR of each of these AOB_ELEMENT
1, AR2, AR3 ・ ・ ・ ・ ・ ・ ARn-1, ARn and 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 TMSRT
_entry # 1 describes the size of the occupied areas AR2 and AR3 of AOB_ELEMENT # 2 and AOB_ELEMENT # 3 in TMSRT_entry # 2 and TMSRT_entry # 3.

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

{17-3_21-2} TKTMSRT Read Method As described above, it is understood that the data size of AOB_ELEMENT is described in the time search table. On the other hand, AO
As mentioned in the description of B_ELEMENT, the data length of each AOB_BLOCK is set so that the playback time is within 8.4 minutes, so the total number of AOB_ELEMENTs contained in one AOB is the specified number.
(252 shown in FIG. 20) or less. AOB_ELEME
Since the number of NTs is suppressed to a predetermined number or less, the total number of TMSRT_entries corresponding to AOB_ELEMENT is also a predetermined number or less, and the data size of TKTMSRT including these is also a predetermined size or less. Since the size of TKTMSRT is suppressed, the playback device can read and use the TKI as follows.

When a certain AOB is read and its reproduction is started, the corresponding TKI is read and stored in the memory. After that, this TKI is stored in the memory while the reproduction of the AOB continues. When the playback of the AOB ends, the AOB that follows it is read, and when the playback is started, the TKI corresponding to it is read and the TKI stored in the memory until that time is newly read. Overwrite with the issued TKI. After that, this TKI is stored in the memory while the reproduction of the AOB continues.

By reading the TKI and storing it in the memory in this manner, even if the amount of memory mounted in the reproducing apparatus is small, it is only necessary to read the TKI to perform forward search reproduction and reverse search. Special playback such as playback 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 of to the beginning of each AOB_ELEMENT may be described.

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

{17-4} About TKTXTI_DA This is the end of the description of the time search map (TKTMSRT). Next, the Track Text Information Data Area (TKTXTI_DA) described in the upper part of TKTMSRT in FIG. 17 will be described. Track Text Information Data Area (T
In KTXTI_DA), text information indicating an artist name, an album name, an arranger name, a producer name, etc. is described. This area is reserved even if there is no text data.

{17-5} TKGI Next, the TKGI in the upper part of TKTXTI_DA will be described.
In FIG. 17, the TKGI of the TKI is the TKI identifier “TKI_ID”, the TKI number “TKIN”, as shown by the broken line h4.
TKI size "TKI_SZ", link pointer to the 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. (Note that some fields are omitted in this figure for the sake of simplicity.) .).

{17-5_22-1} TKGI The detailed structure of TKGI will be described below with reference to FIG. The difference between this figure and FIG. 17 is that TK shown in FIG.
The data structure of GI is located on the left side of the figure, and it has not been revealed in FIG. 17 "TKI_BLK_ATR", "TKI_AOB_"
The bit configuration of "ATR" and "ISRC" is arranged on the right side in the figure.

{17-5_22-2} Regarding TKI_ID In "TKI_ID", an ID (a 2-byte code "A4" in this embodiment) that can uniquely identify a TKI is described. {17-5_22-3} About TKIN "TKIN" describes TKI numbers in the range of 1 to 999. This TKI number is described in the TKIN of other TKIs.
Must not duplicate TKI number. As such a TKIN, the order of TKI in TrackManager, that is, TrackMana
It shall describe the position of TKI in ger. In the figure, TKI # 1 describes the TKI number as "1", TKI # 2 describes the TKI number as "2", and TKI # 3 describes the TKI number as "3".

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

When a track is composed of a plurality of AOBs and they are recorded in a plurality of AOB files, a plurality of TKIs associated with the plurality of AOB files are united to manage the track. It will be. When a plurality of TKIs are integrated as described above, it is necessary to indicate which TKI corresponds to which AOB file follows the AOB file corresponding to these TKIs. TKI_LNK_PTR is each T
It is used for describing TKIN of TKI that follows KI.

{17-5_22-6_19} TKI_LNK_PTR Hereinafter, in the eight TKIs shown in FIG. 19, TKI_LNK_PTR
Will be described. In TKI # 1 to TKI # 3 and TKI # 8 that make up one track, the T
KI_LNK_PTR is not set, but the four A's that make up TrackD
TKI # 4, TKI # 5, TKI # 6, TKI # 7 corresponding to OB file,
Each TKI_LNK_PTR is set to indicate the next TKI_LNK_PTR. That is, as shown by arrows TL4, TL5, TL6, TKI # 4
TKI_LNK_PTR indicates TKI # 5, and TKI # 5's TKI_LNK
_PTR indicates TKI # 6, and TKI_LNK_PTR of TKI # 6 indicates TKI # 7. All of these form TrackD. These TKI_LNK in TKI corresponding to four AOB files
By referring to _PTR, the four TKIs TKI # 4 to TKI # 7
It can be seen that KI and four AOB files of AOB004.SA1 to AOB007.SA1 collectively form TrackD.

{17-5_22-7} About TKI_BLK_ATR "TKI_BLK_ATR" describes attributes about TKI. In FIG. 22, the bit structure of TKI_BLK_ATR is shown in the frame drawn from TKI_BLK_ATR with a broken line. In this figure, TKI_BLK_ATR is 16 bits, and bits b3 to b15 are reserved for future expansion. The attributes of the TKI are described using 3 bits of 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 contains multiple TKIs,
If the TKI is at the beginning, TKI_BLK_ATR contains "001
The value of "b" is described (hereinafter, this setting is "Head_of_Trac
k ”. ). When TKI is used, one track is composed of multiple TKIs, and the TKI is in the middle, a value of "010b" is described in TKI_BLK_ATR (hereinafter,
This setting is called "Midpoint_of_Track"). When the TKI is used, one track is composed of a plurality of TKIs, and the TKI is the end of the TKI, a value of "011b" is described in TKI_BLK_ATR (hereinafter, this setting is referred to as "End_of_Track"). . If the TKI is unused and there is a TKI area,
That is, in the case of the deleted TKI, the value of "100b" is described (hereinafter, this setting is referred to as "Unused"). TKI
Is unused and there is no TKI area, that is, when the TKI is in the initial state, the value of "101b" is described.

{17-5_22-8_19} Setting example of TKI_BLK_ATR In the example of FIG. 19, TKI_BLK_A for each TKI is set.
Explain how TR is set. each
If you refer to TKI_BLK_ATR in TKI, TKI # 1 (AOB001.
SA1), TKI # 2 (AOB002.SA1), TKI # 3 (AOB003.SA1), T
The four pairs of 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 set to“ End_o
It can be seen that “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 a corresponding relationship with TKI # 5 and TKI # 6 (AOB005.AOB004.SA1).
SA1) and TKI # 6 (AOB006.SA1) are in the middle of the truck,
TKI # 7 (AOB007.SA1), which has a corresponding relationship with TKI # 7, means the end of the track.

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

{17-5_22-9} About TKI_PB_TM "TKI_PB_TM" describes the reproduction time of the track (song) composed of the AOB recorded in the AOB file corresponding to the TKI. When the 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. For the second and subsequent TKIs,
AOB playback time corresponding to each TKI is described.

{17-5_22-10} About TKI_AOB_ATR In "TKI_AOB_ATR", what sampling frequency the AOB recorded in the AOB file corresponding to TKI is sampled and what bit rate is transferred. Or the number of channels, the encoding conditions for AOB generation are described. 『TKI_AOB_
The frame drawn from the “ATR” with a broken line shows the bit configuration of TKI_AOB_ATR. In the figure, TKI_AOB_ATR is 20 bits, and the coding mode is described in the fields from bit number b16 to bit number b19. MPEG-2
When encoded with AAC (with ADTS header), the value of "0000b", when encoded with MPEG-layer3 (MP3), the value of "0001b" is Windows (registered trademark) Media If encoded with Audio (WMA), "
0010b "is described respectively.

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

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

The areas from bit number b31 to bit number 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 from “ISRC” in FIG. 22 by a broken line shows the contents of ISRC. As shown in this frame, the ISRC consists of 10 bytes, and the Recording-item code (# 12) is described in the field from bit number b4 to bit number b7.
Recording cod in the field from b8 to bit number b11
e / Recording-item code (# 11) is described.

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

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

{17-5_22-12_23A-2} DATA_Offset In “DATA_OFFSET”, the relative address from the cluster boundary to the beginning of each AOB_BLOCK is described in bytes. This expresses how many invalid areas exist between AOB and AOB_BLOCK. If the music stored in the flash memory card 31 as the AOB is air-checked and recorded, and the disc jockey's voice is mixed in the intro portion of the music, the BIT
By setting DATA_Offset in, it is possible to exclude this unnecessary sound from AOB_BLOCK and prevent it from being reproduced.

{17-5_22-12_23A-3} Regarding SZ_DATA In "SZ_DATA", the data length of each AOB_BLOCK is described in bytes. The sum of SZ_DATA and DATA_Offset
By subtracting from the size of the file that contains AOB (an integer multiple of the cluster size), you can determine the size of the invalid area following AOB_BLOCK.

{17-5_22-12_23A-4} Regarding 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
Regarding “_TMSRTE” and “FNs_Middle_TMSRTE”, “FNs_1st_TMSRTE” describes the number of AOB_FRAME included in the first AOB_ELEMENT in 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 AOBs
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 for describing the reproduction period of AOB_ELEMENT with the time accuracy of millisecond order in the format shown in FIG. 23 (c). FIG. 23
As shown in (c), the TIME_LENGTH field has a 16-bit length, and the encoding method is MPEG-AAC or MPEG-Layer.
In the case of 3 systems, the reproduction period of AOB_ELEMENT is 2 seconds, so a value of 2000 is described in TIME_LENGTH.

{17-5_22-13_23B} FIG. 23B is a diagram showing how many AOB_FRAMEs are stored in FNs_Middle_TMSRTE. This figure is similar to Figure 14.
The correspondence between sampling_frequency and the number of AOB_FRAME included in the AOB_ELEMENT in the middle part is shown. It can be seen that the correspondence relationship between sampling_frequency and the number of frames included in AOB_ELEMENT in this figure is exactly the same as in FIG. 14, and the number is different depending on the sampling frequency. "FNs_1st_TMSRTE" and "FNs_Last_TMSRTE"
The number of frames in is set to the same number as the number of frames in "FNs_Middle_TMSRTE" in principle,
When setting an invalid area in AOB_ELEMENT located at the beginning or end of AOB_BLOCK, "FNs_1st_TMSRTE" and "FNs_La
"st_TMSRTE" has a different value from "FNs_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 consisting of AOB_ELEMENTs # 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
007 ~ AOB_ELEMENT # 1 ~ AOB stored in cluster 00E
Each of _ELEMENT # 4 is provided with a triangular flag-shaped symbol, which indicates that TMSRT_entry included in the TKI is set in each of AOB_ELEMENT # 1 to AOB_ELEMENT # 4.

At this time, the leading end portion of AOB_ELEMENT # 1 at the AOB leading end is stored in the cluster 007, and the trailing end portion of AOB_ELEMENT # 4 at the AOB ending is stored in the cluster 00E. AOB_ELEMENT # 1 to # 4 are in the middle of cluster 007
Occupies from md0 to md4 in the middle of cluster 00E. SZ_DATA in BIT is AOB_ELEMENT # 1 to A as shown by arrow sd1.
OB_ELEMENT # 4 is instructed to the end, and cluster 007,
It is an area within 00E and does not indicate the parts ud0 and ud1 which are not occupied by AOB_ELEMENT.

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

As described above, each AOB_ELEMENT is freely arranged regardless of the cluster boundary, and it is understood that 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} Usage of the number of frames for each AOB_ELEMENT 1 The following describes how the number of frames for each AOB_ELEMENT described in BIT is used. The number of frames described in BIT is, first of all, the playback elapsed time of 2
This is used when performing forward search playback and reverse search playback in which the second skip is performed and playback is performed for 240 milliseconds.

FIG. 25 shows the case of performing forward search reproduction from AOB_FRAME # x in arbitrary AOB_ELEMENT # y in AOB.
It is a figure which shows how to set AOB_FRAME # x + 1 which should be reproduced next. This figure shows the AOB included in AOB_ELEMENT # y
FIG. 13 is a diagram drawn assuming that a forward search reproduction is instructed at the time when _FRAME # x is reproduced. In this figure, t is the predetermined intermittent playback time (= 240 ms), 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 during intermittent playback (2 seconds in this case), 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.

Jump to the beginning of the flag (AOB_ELEMENT) with reference to TMSRT_entry described in TKTMSRT. Jump to the beginning of the next flag (AOB_ELEMENT) that plays for 240 ms. In the present embodiment, a method for realizing more accurate intermittent reproduction of reproducing for 240 milliseconds, jumping to a position 2 seconds later, and reproducing for 240 milliseconds will be described.

AOB_FRAME # x + 1, which is 2 seconds + 240 milliseconds after AOB_FRAME # x included in AOB_ELEMENT # y, is AOB_ELEMENT #
It should be in y + 1. AOB_FRAM after 2 seconds + 240 ms
When specifying E # x + 1, the start address for the next AOB_ELEMENT # y + 1 can be calculated immediately by reading TMSRT_entry in TKTMSRT.
The number of AOB_FRAMEs 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_F
AOB_EL is calculated 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).
It must be obtained by subtracting the total number of frames included in EMENT # y. As such, 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 the 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 to specify AOB_ELEMENT and AOB_FRAME corresponding to the designated time when an arbitrary playback start time is designated.

When reproduction is instructed by designating an arbitrary time, assuming that the reproduction designated time is Jmp_Entry (second), from AOB_ELEMENT # y and AOB_FRAME position x that satisfy the following formula,
Start playing. {Formula 2} Jmp_Entry (second) = (FNs_1st_TMSRTE ＋ FNs_midd
le_TMSRTE × y ＋ x) × 20msec These “FNs_1st_TMSRTE” and “FNs_Middle_TMSRTE”
Is described in BIT, so if AOB_ELEMENT # y and AOB_FRAME # x are calculated by applying these to {Formula 2}, refer to TKTMSRT corresponding to this AOB, and y + 2th in AOB The start address of the AOB_ELEMENT # y + 2 located at is searched, the search for AOB_FRAME # x is started from this start address, and if the xth AOB_FRAME is searched, the reproduction is started from this xth AOB_FRAME. This allows Jmp_E
Playback can be started from the time specified by ntry (seconds).

At this time, the ADTS header part of the AOB file is not searched, and AOB_ in which TMSRT_entry is described in TKTMSRT
Since it is sufficient to search 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 for tracks consisting of multiple AOBs and Jmp_Entry (seconds) is specified,
AOB_ELEMENT # y and AOB_FRAME that satisfy the following {Equation 3}
#x and should be calculated. {Equation 3} Jmp_Entry (sec) = Sum of playback times from AOB # 1 to AOB # n + (FNs_1st_TMSRTE (# n + 1) + FNs_middle_TMSRT
E (# n + 1) ・ y + x) ・ 20msec Here, the total playback time of AOB from AOB # 1 to AOB # n is
It is as follows. Sum of playback times from AOB # 1 to AOB # n = ("FNs_1st_TMSRTE"(# 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) + 'FNs_Last_TMSRTE'(# n)) ・ AOB # n, AOB_ELEMENT # y, AOB_FRAME # that satisfies 20 msec {Equation 3}
When x is calculated, the TKTMSRT corresponding to this AOB # n + 1 is referred to, the search for AOB_FRAME # x is started from the address located at the y + 2nd AOB_ELEMENT # y + 2, and the xth AOB_FRAME If is searched, the reproduction is started from the x-th AOB_FRAME.

{17-5_22-16_27A, B} AOB file and TKI
Deleting all of the information included in TKI, when some tracks were deleted (case 1), when some tracks were deleted and new tracks were recorded (case 2),
How TKI is updated when combining any two of multiple tracks into one track (case3), dividing one track to get two tracks (case4) Will be described.

First, the case where some tracks are deleted (case 1) will be described. 27 (a), (b)
[Fig. 6] is a diagram assuming a case where 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. The AOB corresponding to this TrackB is AOB002.SA
Since it is recorded in 1 and it is associated with TKI # 2, AOB002.SA1 is deleted and TKI_BLK of TKI # 2 is deleted.
_ATR is set to “Unused”. FIG. 27B shows a state in which AOB002.SA1 is deleted and TKI_BLK_ATR of TKI # 2 is 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 when newly recording an AOB file A case (case 2) in which a new track is recorded after some tracks are subsequently deleted will be described. FIG. 28
(A) shows TrackM after a track has been deleted multiple times.
It is a figure which shows an anager. In this figure, multiple tracks are deleted and these are TKI # 2, TKI # 4, TKI # 5, TKI # 7, TK.
If it is mapped to I # 8, the TKI_ of these TKIs
BLK_ATR is set to "Unused". AOB files are deleted in the same way as normal files, but TrackManager
Deletes only by setting TKI_BLK_ATR of the corresponding TKI to “Unused”. Then, as shown in this figure, "Unused" TKI will appear like a worm on TrackManager.

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

Since these four AOBs form one track, TKI_BLK_ATR for TKI # 2 is set 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 compose
_LNK_PTR is the next TKI_LNK_PT that composes the 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 specifies TKI # 7, and TKI_LN of TKI # 7.
K_PTR points to TKI # 8.

After that, four files AOB002.SA1 and A having the same numbers as TKI # 2, TKI # 4, TKI # 7 and TKI # 8, respectively.
OB004.SA1, AOB007.SA1, and AOB008.SA1 are created, and four AOBs that form TrackD are recorded in these four files. By setting such TKI_BLK_ATR and TKI_LNK_PTR, the fourth track TrackD is TKI # 2, TKI # 4, TKI # 7,
It will be managed using TKI # 8.

As described above, the flash memory card 3
If you want to write a new track to 1, use TrackMan until then.
It can be seen that the TKI set to "Unused" in the ager is assigned to the TKI of the track to be newly recorded. {17-5_22-18_29A, B} T when integrating two tracks
KI setting Next, update of TKI when integrating tracks (case 3) is explained.

FIGS. 29 (a) and 29 (b) 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 the anager, and in Track (C) in FIG.
It is assumed that the operator desires an editing operation of integrating TrackE and one track. Track C, Trac
AOBs corresponding to kE are 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 can be rewritten. Be seen. FIG. 29B is a diagram showing a state after rewriting TKI_BLK_ATR of TKI. TKI_ of TKI # 3 and TKI # 8 in this figure
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”. By rewriting TKI_BLK_ATR in this way, TKI # 3, TKI # 8, and AO corresponding to these
B003.SA1 and AOB008.SA1 are handled as one track called TrackC. In addition to this, TKI_LNK_PTR of TKI # 3 is rewritten to point to TKI # 8 as a link destination.

It should be noted 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 encrypted AOB files are decrypted and then encrypted again. This is because it is necessary to perform the above two processes for each AOB file, which requires a large processing load. In addition, the AOB file after integration has only one FileKey
Because it is encrypted by, the copyright protection will be weakened compared to before integration.

In addition, the TKI is originally defined so that the size of TKTMSRT does not become large. However, if this is integrated into one in an editing operation, the size of the combined TKI may become too large. Because. As described above, the integrated editing of tracks in this embodiment is performed by AO
It can be seen that it can be 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 The integration of tracks is realized by changing the attribute of TKI_BLK_ATR, as described above. Upon integration, it is required that the AOBs included in the integrated trucks meet the following conditions. The first condition is that the audio attributes (audio coding mode, bit rate, sampling frequency, number of channels) of the AOB included in the following track and the AOB included in the preceding track match. . this is,
This is because if the audio attributes of the AOB differ between the preceding and following AOBs, the playback device must reset the decoder operation once, making it difficult to play two consecutive AOBs seamlessly (without interruption). .

The second condition is that the number of AOB_FRAME is "FNs_Middle_TMSRT" in the track obtained after integration.
It means that there are no more than three consecutive AOBs consisting only of AOB_ELEMENT that are less than E ”. AOB is 2 depending on whether at least one of AOB_ELEMENT has the same number of AOB_FRAME as the number of frames specified in "FNs_Middle_TMSRTE".
There are two types. The first type of AOB is "FN
s_Middle_TMSRTE ”and the same number of frames A
An AOB that has at least one AOB_ELEMENT with OB_FRAME, and the second type of AOB is'FNs_Middle_TM
It is an 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 AOB is less than the number of frames specified by "FNs_Middle_TMSRTE", and the second condition described above is the Type2 AOB.
It prohibits that three or more consecutive. The reason for prohibition is as follows. That is, when sequentially reading AOBs, the buffer in the playback device must have a sufficient number of AOB_FRAMs.
Although it is desirable to be filled with E, if the Type 2 AOB is continuous, the buffer in the playback device is set to AOB_FRAME
Can not be filled with. Then, the buffer in the playback device underflows, and the continuity of AOB playback cannot be maintained. In order to avoid such underflow, the second condition prohibits three or more Type 2 AOBs in a row.

FIG. 30A shows a Type 1 AOB, and FIG.
0 (b) is a diagram showing a Type 2 AOB. Figure 30 (b)
The AOB in consists only of two or less AOB_ELEMENT, and those AOB_ELEMENT of two or less are "FNs_Middle_TMSRTE".
Does not have AOB_FRAME shown in (in this case, BIT
In, only FNs_1st_TMSRTE is described. ). 『FNs_Mi
Since the requirement of Type2AOB is that it does not have AOB_FRAME shown in "ddle_TMSRTE", even an AOB composed of only one AOB_FRAME will be classified into this Type2 AOB.

FIG. 31A shows Type1 + Type2 + Type2 + T.
It is a figure which shows the case where several tracks are integrated into one by the combination of ype1. In this case, three consecutive Type 2 AOBs are avoided, so 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 a combination of + Type2 + Type1. In this case, Type 2 AOB
It is prohibited to combine them into one track as they are three consecutive.

{17-5_22-18_29A, B-1_32} Type1, Type2
According to the track integration shown in FIG. 31 (a), if the end of the preceding track is Type1, this track is a track in which a Type2 AOB is placed at the beginning, or the beginning To
It can be integrated with a truck with Type 1 AOB.
FIG. 32 (a) shows a Type 1 AOB at the end of the preceding track.
FIG. 3 is a diagram showing an arrangement pattern in which the AOB of Type 1 is arranged at the beginning of the subsequent track. Also in FIG.
(B) is a diagram showing an arrangement pattern in which a Type 1 AOB is arranged at the end of the preceding track and a Type 2 AOB is arranged at the beginning of the following track. All of these are conditions
Fill 2 so you can combine them into one track.

The end of the preceding track is Type2,
If the Type 1 AOB is placed immediately before that Type 2,
This track can be integrated with a track of which the head is a Type 1 or a track in which a Type 2 AOB is arranged at the head and a Type 1 AOB is arranged immediately after that. FIG. 32 (c)
FIG. 6 is a diagram showing an arrangement pattern in which AOBs of Type1 and Type2 are arranged at the end of the preceding track and AOBs of Type1 are arranged at the beginning of the following track. FIG. 32 (d) shows
FIG. 7 is a diagram showing an arrangement pattern in which AOBs are arranged in the order of Type1 and Type2 at the end of the preceding track, and AOBs of Type2 and Type1 are arranged at the beginning of the succeeding 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 Type 2 AOB is placed immediately before that Type 2,
This track can be integrated with a track that has a Type 1 AOB at the beginning. FIG. 32 (e) is a diagram showing an arrangement pattern in which Type 2 and Type 2 AOBs are arranged at the end of the preceding track and Type 1 AOBs are arranged at the beginning of the following track. Since this also satisfies the condition 2, it can be integrated into one track. As described above, when integrating tracks, it is determined in advance whether the two tracks to be integrated satisfy the above two conditions,
Only if it is determined that these two conditions are met, combine the two tracks into one.

Next, updating of the TKI when dividing the track (case 4) will be described. {17-5_22-19_33A, B} TKI setting when 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 TrackC is divided 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 the division, “Unused” is displayed as shown in FIG. 33 (b).
TKI # 2 set to is the newly generated AOB002.SA
Assigned to 1.

{17-5_22-19_33A, B-1_34A, B} Update directory entry and FAT value Here, when AOB003.SA1 is divided and AOB002.SA1 is generated, the directory entry and FAT value must be updated. I won't. The following describes how to update these directory entries and FAT values. Figure 34 (a)
FIG. 9 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 multiple clusters 007,008,009,00A ...
-It is assumed to be stored in 00D and 00E. In this case, for AOB003.SA1 in the directory entry, the "file first cluster number" 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) ...
It is described as (00D) and (00E).

In this state, divide the latter half of AOB003.SA1
When obtaining AOB002.SA1, "file name", "file extension", and "file first cluster number" for AOB002.SA1 are added to the SD_Audio directory entry. FIG. 34 (b) shows AOB003.SA1 after division.
FIG. 6 is a diagram showing how an SD_Audio directory entry for an SD_Audio directory to which is belongs is described.

The cluster 00F in this figure stores a copy of the contents of the cluster 00B including the division boundary designated by the operator. The divided parts following the divided part of AOB002.SA1 stored in the cluster 00B are stored in the clusters 00C, 00D, and 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 later, AOB002.SA
In "File first cluster number" for 1, the cluster number 00F indicating the cluster 00F is described.
FAT value 00F, 00C, 00 associated with 00F, 00C, 00D, 00E
(00C), (00D), and (00E) are described in D, 00E.

{17-5_22-19_33A, B-2_35A, B} A by updating the directory entry and FAT value above the setting of the information element in the TKI
After obtaining OB002.SA1, we will describe how to set the information elements in the TKI for AOB002.SA1. When generating a TKI for a divided track, the information element of the TKI can be copied and inherited from the original TKI (1), and must be updated based on the original TKI. There are two types of things that do not (2). The former is TKTXTI_DA, ISRC and the latter is BI.
The remaining components, including T and TKTMSRT. Since both of them exist, in the present embodiment, when the TKI for the divided track is generated, the TKI of the division source is copied.
Then, a new TKI template is created, and TKTMSRT and BIT contained in it are divided and updated, and the remaining information elements are updated.

FIG. 35 (a) is a diagram on the assumption that AOB is divided by 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 and AOB_ELEMENT # 4. these
The data length of each of the 4 AOB_ELEMENT is 4 TMSRT
_entry # k-1, # k, # k + 1, # k + 2 (k = 2 here) as TKTM
It is 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 a frame before the division boundary bd1 and an area composed of a frame 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 divided.
It is a figure which shows the state which was obtained.

{17-5_22-19_33A, B-3_36} BIT Setting 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,
The AOB # 1 obtained by the division is AOB_ELEMENT # 1 and AO_ELEMENT # 1.
Contains two AOB_ELEMENTs called B_ELEMENT # 2, AOB # 2 is
AOB_ELEMENT # 1, AOB_ELEMENT # 2, AOB_ELEMENT # 3 3
It can be seen that it contains one AOB_ELEMENT.

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 handles cluster 007 to cluster 00A as one unit. Where AOB_ELEMENT # 2 in AOB # 1
Does not occupy the end of cluster 00A,
Since it occupies the division boundary bd1 where cluster 00A exists, SZ_DATA for AOB # 1 is from area md0 to cluster 0
It indicates the data length up to the division boundary bd1 at 0A. AOB # 1's "FNs_1st_TMSRTE" is the same as before the split, but AOB # 1's "FNs_Last_TMSRTE" is AOB_ELEMENT #
It differs from that before division in that the number of frames from the beginning before division 2 to the division boundary bd1 is designated.

Next, AOB # 2 obtained by division will be described. AOB_ELEMENT # 1, AOB_ELEMEN included in AOB # 2
T # 2 and AOB_ELEMENT # 3 occupy cluster 00B to cluster 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 cluster 00A.
Is occupied by AOB_ELEMENT # 2 of AOB # 1, so
AOB_E included in AOB # 2 that is different from this cluster
This is because it needs to be assigned to LEMENT # 1. ).

AOB_ELEMENT # 1 in AOB # 2 is a cluster
SZ_DATA for AOB # 2 is from the beginning of cluster 00B to cluster 00 because it does not occupy from the top of 00F but occupies the division boundary bd1 and later where cluster 00F exists.
The sum of the data length up to the middle of E and the data length occupied by AOB_ELEMENT # 1 in cluster 00F is instructed.

Cluster 00A stored in cluster 00F
AOB_ELEMENT # 2 of AOB # 1 is recorded in the copy of AOB # 1, and the part occupied by AOB_ELEMENT # 2 of AOB # 1 must be excluded from AOB # 2.
DATA_Offset for AOB # 1 in cluster 00F
The size occupied by AOB_ELEMENT # 2 of 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 are not changed from those before the division. Recognize. Therefore, AOB #
"FNs_Last_TMSRTE" of 2 is set to the same value as "FNs_Last_TMSRTE" of AOB_ELEMENT # 4 before division, and "FNs of AOB # 2"
In “s_1st_TMSRTE”, 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 is set.

{17-5_22-19_33A, B-4_37} BIT Setting FIG. 37 is a diagram more specifically showing how the BIT changes before and after the division. BIT on the left side of FIG. 37 shows a setting example of BIT before division. BIT before dividing the track
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 setting of BIT for two tracks after division. When the AOB corresponding to this BIT is divided as shown in FIG. 35 (a), in the BIT of the first track, Data_Offset is set to the same value “x” as before the division, but up to the division point bd1 in SZ_DATA. The data length is updated to "Q", and the first TMSRT_entr is set in TMSRTE_Ns.
It is updated to "k" which is the number of TMSRT_entries from y to the kth TMSRT_entry. FNs_1st_TMSRTE and FNs_Middl
e_TMSRTE is set to 80,94 frames as before division, but the last AOB_ELEM of the AOB of 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-data length "Q" up to the dividing point bd1, and TMSRTE_Ns is set to n-k + 1 (k It is the number obtained by adding nk, which is the number of TMSRT_entries from the nth TMSRT_entry to the nth TMSRT_entry, and one, 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 division, but the first AOB_ELEM of the AOB of the second track after division.
ENT contains 94-p AOB_FRAMEs, so FNs_
1st_TMSRTE is set to “94-p frame”.

{17-5_22-19_33A, B-5_38} BIT Setting FIG. 38 is a diagram showing the TKTMSRT after division. First TMSRT
Is as follows. The first track TMSRT is from the beginning of the AOB TMSRT before division to the kth entry
(TMSRT_entry # 1 to TMSRT_entry # k) are included. It should be noted here that AOB_ELEMENT # k including the division boundary only includes the area, and thus the k-th entry includes only the data size of the portion corresponding to this area. Two
TMSRT of the track is n from the kth entry before division.
Including (TMSRT_entry # k to TMSRT_entry # n) up to the second entry. It should be noted here that AOB_ELEMEN including the division boundary
T # k only contains the area on the second track, so
The kth entry before division contains only the data size of the part corresponding to this area.

If the TKI is copied, the TKTMSRT and BIT are divided / 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, encrypted AOB files remain encrypted without decryption
The track corresponding to an AOB file can be split into two. Since the decryption / re-encryption is not involved when dividing the AOB file, it can be seen that the processing load when dividing the track is reduced. As a result, even if the processing performance of the playback device is low, it is possible to edit the track.

The long sentence has been described above, but the explanation of the TKI is completed. Next, the play list will be described. {17-6} Playlistmanager The playlistmanager shown in Fig. 17 has a broken line h5
PlaylistManager_Info that manages the playlists stored in the flash memory card 31, as shown in FIG.
rmation (PLMGI) and Default_Playlist_Informa that manages all tracks stored in the flash memory card 31.
tion (DPLI) and Playlist Information (PLI) # 1, # 2, # 3, # 4,
Default_Playlist_Gener consists of # 5 ... # n, and Default_Playlist information is
al_Information (DPLGI), Default_Playlist_Track_Serch
It can be seen that _Pointer (DPL_TK_SRP) # 1, # 2, # 3, # 4 ... In addition, each PLI has Playlist_General_Information (PLGI), Playlist_
Track_Serch_Pointer (PL_TK_SRP) # 1, # 2, # 3, # 4 ... It is understood that it consists of #m.

Here, Default_Playlist information and PlayList
Explain the difference from the information. Default_Playlist
The information is obliged to specify all tracks, whereas the PlayList information does not have such an obligation, and any track may be specified. Therefore, the user can generate PlayList information that specifies only his or her favorite track and store it in the flash memory card 31, or the Flash memory card 3
The playback device automatically generates PlayList information that specifies only a track of a predetermined genre among the plurality of tracks stored in the flash memory card 31.
It is suitable for use as a memory.

{17-7_18} Number of playlists, data size Referring to FIG. 18, the maximum number of playlists 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 the PlayList information is P
It contains only L_TKIN. These DPL_TK_ATR, DPL_TKI
N, PL_TKIN has the format shown in FIG.

{17-8_39-1} DPL_TK_SRP Format FIG. 39 (a) shows the format of DPL_TK_SRP. In FIG. 39 (a), in DPL_TK_SRP, DPL_TKIN is described in the 0th to 9th bits, DPL_TK_ATR is described in the 13th to 15th bits, and the 10th to 12th bits are reserved. It is reserved.

Next, the TKI number is described in DPL_TKIN which occupies the fields from the 0th bit to the 9th bit.
By writing the TKI number here, it is possible to specify the TKI. {17-9_39B} PL_TK_SRP format 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, the TKI number is described therein.

{17-8_39A-2} Configuration of DPL_TK_ATR From “DPL_TK_ATR” in FIG. 39 (a), broken line arrows h51, h52
An example of setting DPL_TK_ATR is shown in the frame extracted in.
As can be understood from the description in this frame, the setting of DPL_TK_ATR for DPL_TK_SRP is TKI_BLK_A for TKI.
It is the same as the TR setting, and "Track", "Head_of_Trac
k ”,“ Midpoint_of_Track ”, or“ End_of_Track ”is set.

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

The TKI specified by TKIN is in use,
When the audio object corresponding to only the middle part of the track is recorded in the AOB file corresponding to the TKI (“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 in use and corresponds to the TKI.
When the audio object corresponding to only the end of the track is recorded in the AOB file (TKI_BLK of TKI)
"End_of_Track" in _ATR) and "0" in DPL_TK_ATR
The value of 11b "is set.

The TKI specified by TKIN is unused and T
If only the KI area is secured, that is, if it 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 relationship with any one of a plurality of TKIs by describing the TKI number in DPL_TKIN. Also, the rank of DPL_TK_SRP in the Default_Playlist information indicates the order of reproduction of the AOB (AOB file) corresponding to the TKI having a corresponding relationship 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 played back, that is, the playback order of the tracks.

{17-9_40-1} Default_Playlist information, TK
Mutual Relationship of I and AOB Files FIG. 40 is a diagram showing the mutual relationship of Default_Playlist information, TKI, and AOB files. The second, third, and fourth levels in this figure are the same as the first level, the second level, and the third level in FIG. 19, and show a TrackManager including eight TKIs and eight AOB files. . The difference from FIG. 19 is that the Default_
This is the point where a rectangular frame indicating the Playlist information is described.
Eight small frames included in the first frame are Default_Playlis.
The eight DPL_TK_SRPs included in the t information are shown. 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, there is a correspondence relationship between DPL_TK_SRP # 1 and TKI # 1, and DPL_TK_SRP # 2 and TKI # 1. Between # 2 and DPL_T
It can be seen that there is a corresponding relationship 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, 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 of # 8 → TKI # 8 (AOB008.SA1) correspond to independent tracks.

DPL_TK_SRP # 4, DPL_TK_SRP # 5, DPL_TK_SRP
Neither DPL_TK_ATR of # 6 and DPL_TK_SRP # 7 is set to Track, and DPL_TK_ATR of DPL_TK_SRP # 4 is “Head_of_Tr
It can be seen that 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 correspondence 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 correspondence with SRP # 5, # 6
KI # 6 (AOB006.SA1) has DPL_TK_S in the middle of the track
This means that TKI # 7 (AOB007.SA1) having a correspondence relationship with RP # 7 is the end of the track.

The order of DPL_TK_SRP in DefaultPlaylist shows in what order the AOBs associated with each TKI are to be played back. DPL in DefaultPlaylist in 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 second, TOB # 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 in FIG. 40. In the figure, a square frame in the first row shows Default_Playlist information, and three square frames in the second row show PlayList information. The small frame included in DefaultPlaylist is DefaultPlayli
The eight DPL_TK_SRPs included in st indicate 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
Settings are the same as in FIG. However, it can be seen 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 uses the same notation as in FIG.
It is a figure which shows the correspondence with I. 42, Playlist # 1
Consists of PL_TK_SRP # 1, # 2, # 3. Of these PL_TK_SRP # 1
PL_TKIN is described as # 3, PL_TK_SRP # 2's PL_TKI
N is described as # 1 and PL_TKIN of PL_TK_SRP # 3 is described as # 2. Therefore, when playing a track using PlayList information # 1, a plurality of tracks are displayed as indicated by arrows (11), (12), and (13). AOB is AOB # 3, #
Played in order of # 1 and # 2.

Playlist # 2 is composed of PL_TK_SRP # 1, # 2 and # 3. Among them, 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 indicated by arrows (21) (22) (23), multiple AOBs are AOB # 8, #
Playback is performed in the order of 3, # 1, that is, in an order completely different from Playlist # 1.

Playlist # 3 is composed of PL_TK_SRP # 1, # 2, # 3 and # 4. Of these, PL_TK_SRP # 1, # 2, # 3, # 4 PL_TKIN is # 8, #
Since it is described as 4, # 3, # 1, when the tracks are reproduced using the PlayList information # 3, the AOB is reproduced in the reproduction order shown below. First, the AOB # 8 constituting TrackE is reproduced as indicated by the arrow (31), and AOB # 4, AOB # 5, AOB # 6, AOB # 7 constituting TrackD as indicated by the arrow (32) are reproduced in this. It is then played back. Then, as shown by the arrows (33) and (34), TrackC and Trac
Playback is performed in the order of AOB # 3 and AOB # 1 that compose kA. It should be noted here that when a track is composed of multiple TKIs, 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, TK
I # 6 and TKI # 7 were specified, but PL in PlayList information
_TK_SRP need not specify these 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, the DPLI including a plurality of DPL_TK_SRP is 1
RAM has a data size that fits in a sector
Resident on top. Therefore, when playing each track based on Playlist, DPL_T resident in RAM
By referring to K_SRP, each TKI can be searched at high speed. That is, in order to play a TKI (AOB) using PL_TK_SRP in which only the first TKI number is written among multiple TKIs, RAM is based on the TKI described in PL_TK_SRP.
Search the DPL_TK_SRP resident above to determine if the track is composed of multiple TKIs. Multiple T
If it is composed of a KI, the procedure of reproducing all the corresponding TKI (AOB) is performed.

As described above, Defau is set in PlayListManager.
ltPlaylist, multiple PlayList information are described, and if DPL_TK_SRP, DPL_TKIN of PL_TK_SRP, and PL_TKIN that compose them have different playback orders, multiple AO
B is reproduced in a different reproduction order. If the reproduction is performed in a completely different reproduction order, the operator can use the flash memory card 31 as if a plurality of music albums are stored.

It should be noted that DPL_TK_ of DPL_TK_SRP and TKI, both of which are associated with the AOB file.
SRP data size is small (only 2 bytes), TKI
The data size of is large (it has 1024 bytes). Swapping the order of TKIs in TrackManager frequently causes access to the flash memory card 31, but even if the order of DPL_TK_SRP in Default_Playlist information and PlayList information is swapped, access to the flash memory card 31 does not become so large. In view of this point, when editing navigation data, the order of DPL_TK_SRP in DefaultPlaylist is positively changed according to the editing operation, while Trac
The order of TKIs in kManager is kept constant regardless of editing operations.

{17-9_40-2_43A, B} Swap Order of DPL_TK_SRP Next, how to perform an edit operation of changing the playback order of tracks by changing the order of DPL_TK_SRP in the Default_Playlist information will be described.
FIGS. 43 (a) and 43 (b) are diagrams assuming a case where the order of the tracks is exchanged. DPL_TK in FIG. 43 (a)
The settings of _SRP and TKI are the same as in FIG. Figure 40
In (a), DPL_TK_SRP # 3's DPL_TKIN is TKI #
3, DPL_TKIN in DPL_TK_SRP # 8 was set to TKI # 8, but in this state, DPL_TK_SRP # 3 surrounded 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 change is shown. With this in mind,
The reproduction order in FIG. 43 (a) is TrackA, TrackB, Tr.
ackC, TrackD, and TrackE, but in FIG. 43 (b)
In the Default_Playlist information, DPL_TK_SRP # 3, DPL_TK_SRP
The order of DPL_TKIN for # 8 has been changed, so Tr
It will be played in the order of ackA, TrackB, TrackE, TrackD, and TrackC. As described above, by changing the order of DPL_TK_SRP in the Default_Playlist information, the reproduction order of tracks can be easily changed.

The editing operation called the track changing operation has been described. As in the case of TKI, when some tracks are deleted (case 1), after some tracks are deleted, a new track is recorded. In case (case2), when combining any two of multiple tracks into one track (case3), when dividing one track to obtain two tracks (case4), DPL_TK_SRP and TKI are Explain how it is updated.

{17-9_40-3_44A, B} When deleting tracks First, when some tracks are deleted (case 1)
Will be described. 44 (a) and 44 (b) are DPL_TK_SRP # 2 and TKI # 2 of the DefaultPlaylist shown in FIG.
DefaultPlaylist, TrackManager, AOB when deleting
FIG. 6 is a diagram showing how a file is updated. FIG. 44 has the same parts as FIG. 27 cited in the explanation of TKI deletion. That is, the second, third and fourth steps in FIG. 44 are the same as those in FIG. The difference is that, as in FIG. 40, Default_Playlist information including a plurality of DPL_TK_SRPs is described in the first row. Track consisting of DPL_TK_SRP # 2 → TKI # 2 (AOB002.SA1) surrounded by a thick frame in FIG. 44 (a)
Assume that the user has deleted B. In this case, Default_P
In the laylist information, DPL_TK_SRP # 2 is deleted and DPL_TK_SRP # 2 is deleted.
_TK_SRP # 3 to DPL_TK_SRP # 8 are moved up one by one so that the fields occupied by DPL_TK_SRP # 2 are packed. In this way, the order of each DPL_TK_SRP is advanced, and the last DPL_TK_SRP # 8 is set to “Unused”. On the other hand, the TKI is only set to “Unused” as described with reference to FIGS. 27A and 27B, and TKI # 2 is not moved so as to be packed. Also AOB002.SA1
Can be seen to have been deleted. Although the order has been advanced for DPL_TK_SRP, the order has not been advanced for TKI, so in Figure 44 (b), DP
DPL_TKIN in L_TK_SRP has been updated. That is, the new DPL_TK_SRP # 2 DPL_TKIN is as shown by the arrow DT11.
Instructing TKI # 3, DPL_TKIN of DPL_TK_SRP # 3 is arrow D
As shown in T12, TKI # 4, DPL_TK_SRP # 4 DPL_TKIN is TK
DPL_TKIN of I # 5 and DPL_TK_SRP # 5 indicates TKI # 6, respectively. In addition, DPL_TK_SRP # 8 set to “Unused”
It can be seen that DPL_TKIN sets TKI # 2 set to “Unused” as shown by the arrow DT13.

When a track is deleted, DPL_TK_SRP that is being used is moved up to the head, but it can be seen that the TKI corresponding to it is set to unused while maintaining the original arrangement. In this way, since the TKI arrangement is fixed before and after editing, the processing load associated with the editing process can be reduced. {17-9_40-4_45A, B} TKI allocation when recording a track Next, a case where a new track is recorded after some tracks are deleted (case 2) will be described. Figure 45
(A) and (b) are diagrams showing how "Unused" TKI and DPL_TK_SRP exist, and when new TKI and DPL_TK_SRP are written therein, the writing is performed. In FIGS. 45 (a) and 45 (b), "Unused"
When explaining a case of assigning a new TKI to the TKI of FIG. 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 there are multiple DPs in the first row of FIG.
This is the point where Default_Playlist information consisting of L_TK_SRP is described. In FIG. 45 (a), 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 "U" as shown in FIG. 28 (a).
It turns out that it is'nused '. In TrackManager, "U
While the Nused 'TKI exists like a worm, De
In the fault_Playlist information, the DPL_TK_SRP of "Unused" is summarized as described above.
This is because DPL_TK_SRP other than “Unused” is carried up, whereas TKI is not carried up.

Here, assume a case where a TrackD composed of four AOBs is to be written. The TKI for each of the four AOBs is written in each of TKI # 2, TKI # 4, TKI # 7, and TKI # 8 set to "Unused" in TrackManager. 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 make up one track, DPL_TK_ATR for DPL_TK_SRP # 4 is "Head_of_Track" and DPL_TK_SRP # 5, D
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
It is set as TKI # 2 and DPL_TKIN for DPL_TK_SRP # 5 is T
KI # 4, DPL_TK_SRP # 6 DPL_TKIN is TKI # 7, DPL_T
DPL_TKIN for K_SRP # 7 is set to TKI # 8.
By setting DPL_TKIN and DPL_TK_ATR as above, TKI #
2, TKI # 4, TKI # 7, TKI # 8 will be managed as the fourth track TrackD.

In the above processing, writing to the TKI of "Unused" is performed, but TKI # 1, TKI # 2, TKI # 3, TKI
Regarding KI # 4, the point that no change is made is shown in FIG. 28.
It is similar to the case of. {17-9_40-5_46A, B} When integrating tracks (case3) Default_Pla when integrating tracks (case3)
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 FIGS. 29 (a) and 29 (b) cited when explaining the TKI integration processing. 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 Default_ in FIGS. 46 (a) and 46 (b).
Playlist information is described and DPL_TK included in it
_SRP # 8 is set to "Unused" and also "Unuse
It has a corresponding relationship with TKI # 2 set in "d". In this figure, when the track integration process as shown in FIG. 29 is performed on the AOB file and the TKI,
The contents of DPL_TK_SRP # 3 to DPL_TK_SRP # 6 are shifted one by one, and the description contents of DPL_TK_SRP # 7 enclosed in a thick frame are 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 performing track division (case 4), 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 figure has the same parts as FIGS. 33 (a) and 33 (b) cited when explaining the division processing for TKI. That is, the second and third stages in this figure are the same as those in FIG.
It is the same as the first and second stages in (a) and (b). The difference is Default_Pl in FIGS. 47 (a) and 47 (b).
The aylist information is described and it is included in DPL_TK_S
RP # 8 is set to "Unused" and also "Unused"
It has a corresponding relationship with TKI # 2 set to. In this state, when the TKI # 3 and AOB003.SA1 surrounded by a thick frame are divided into two, as in the case of FIG. 33,
DPL_TK_SRP # 3 to DPL_TK_SRP # 7 are moved down one by one, and "Unused" DPL_TK in Default_Playlist information
Move _SRP to DPL_TK_SRP # 3. DPL_TK_SRP after moving
TKI # 2 obtained by division is associated with # 3. T
AOB002.SA1 associated with KI # 2 was originally AOB003.S
Although the latter half of A1 is stored, DPL_TK_SRP # 2 exists before DPL_TK_SRP # 3 associated with 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 first half of the original AOB003.SA1.
DPL_TK_SRP # 2 and DPL_TK_SRP # 3 that specify these are
Since the playback order is specified to play these AOB files in the order of AOB003.SA1 and AOB002.SA1, the original AO
The second half portion and the first half portion of B003.SA1 are reproduced in the order of the first half portion and the second half portion by the reproduction order designation of DPL_TK_SRP.

{17-9_40-8} Application of Editing Processing By combining the above four editing operations, the operator can perform various editing operations. That is, if there is a disc jockey announcement at the beginning of a track and you want to delete it, the above-mentioned track division process divides the announcement part into one track, and then deletes that track. For example, you can only partially remove the disc jockey announcement.

Above, the description of the navigation data is completed, and then, such navigation data,
A playback device configured to play presentation data will be described. {48-1} Appearance of Playback Device FIG. 48 shows the flash memory card 3 according to the present embodiment.
FIG. 3 is a diagram showing a portable playback device for No. 1. In the figure, the reproducing device includes a key panel for receiving a key operation such as an insertion slot into which the flash memory card 31 is inserted, reproduction, forward search reproduction, reverse search reproduction, fast forward, rewind, stop and the like from an operator. , And has an appearance similar to a normal portable audio device. The key panel has a Playlist key that accepts playlist / track selection, a "| <<key" that accepts skipping to the beginning of the track, a ">> | key" that accepts skipping to the beginning of the next track, fast forward, and winding. ">>key","<<key" that accepts rewind, forward search playback, and reverse search playback, and a Display key that accepts an operation to display a still image when the flash memory card 31 stores a still image. , Rec key that accepts recording operation from the operator, Stereo / Monoral selection, Audio key that accepts sampling frequency selection from the operator, Mark key that accepts bookmark specification, Track editing, Edit key that accepts title input .

{48-2} Improvements in Portable Playback Device of Flash Memory Card 31 The portable playback device of the flash memory card 31 differs from the normal portable audio device in the following improvements (1) to
It is (4). That is, the Default_Playlist information from the operator, P
In order to accept the layList information and the designation of the track, the LCD display shall show a list of playlists and tracks (1), and any one of the playlists or tracks listed as such. A key has been assigned to specify as a playback target or edit target (2), along with the playback progress of the track,
The LCD display shows the elapsed playback time of the track (3), and the time search function and the jog dial used to set the playback start time when performing split editing (4). Is.

{48-2_49_50} Details of Improvement (2) Details of the improvement (2) are as follows. FIG. 49 is a diagram showing an example of display contents of the liquid crystal display when a playlist is selected, and FIG. 50 is a diagram showing an example of display contents of the liquid crystal display when a track is selected. . 49 "DEFAULTPLAYLIST""PLA
YLIST # 1 ”, PLAYLIST # 2”, “PLAYLIST # 3”, “PLAYLIST #
4 ”indicates a default playlist stored in the flash memory card 31 and four playlists A
It is a SCII string. In addition, “TRAC in FIG.
K # 1 ”, TRACK # 2”, “TRACK # 3”, “TRACK # 4”, “TRACK # 5”
Is an ASCII character string indicating five tracks whose playback order is designated in the default playlist stored in the flash memory card 31. 49 and 50
In (a), these hatched playlists and tracks are designated to be reproduced or edited. As shown in FIG. 50 (b), when the >> | key is pressed with TRACK # 1 designated as a playback target, a list of tracks whose playback order is specified in the playlist is displayed on the liquid crystal display. Among the plurality of tracks listed as shown in, TRACK # 2 under the track is designated as the reproduction target. If the >> | key is pressed while TRACK # 2 is designated as the playback target, one of the tracks in the lower row of the plurality of tracks displayed as shown in FIG. 50C is displayed.
TRACK # 3 is designated as the playback target. When the | << key is pressed while TRACK # 3 is designated as the playback target, the TRACK # 2 one level higher than the TRACK # 2 is played back as shown in FIG. Specified in. As described above, any of the tracks is selected as the reproduction target according to the pressing of the >> | key or the | << key. Therefore, when any track is selected as the reproduction target, FIG. When the playback key is pressed as shown in, playback 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. 51 shows
It is a figure which shows the operation example of a jog dial. The jog dial accepts a rotation operation by the operator, and the reproduction elapsed 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, if the jog dial is rotated counterclockwise, the reproduction start time decreases to "00:00:10" according to the rotation amount. If the jog dial is rotated clockwise as shown in FIG. 51 (c),
The playback start time increases according to the amount of rotation, and the playback time starts at "00:00:
30 ”.

The reason why the playback time is increased or decreased in this way is to specify an arbitrary playback time on the track. If the arbitrary playback time is specified by the rotation of the jog dial and the playback key is pressed, {Formula 2}
Play the AOB from the position specified according to {Equation 3}. In addition, in split editing, the jog dial is used for finely adjusting the split boundary when specifying an arbitrary reproduction start time as the split boundary.

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

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

{52-3} TKI storage area 13 The TKI storage area 13 contains a plurality of TKIs included in TrackManager.
T corresponding to the AOB file that is the playback target
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 protected area.
This area is reserved for storing only the FileKey corresponding to the AOB file that is the reproduction target among the plurality of FileKeys included in Y.

{52-5} Double buffer 15 The double buffer 15 stores the cluster data read from the flash memory card 31 (data stored in each cluster) in sequence and stores it. Encrypted from clustered data AOB_FRAM
This is an input / output buffer used when the output process of reading E and sequentially outputting it to the descrambler 7 is performed in parallel. The double buffer 15 sequentially releases the area occupied by the cluster that has been output as AOB_FRAME to a free area, and uses this free area to store the newly read cluster, that is, a ring. 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 the double buffer 15 is performed. FIG. 54 (a),
(B) is a diagram showing how a cyclic area is secured using a ring pointer. In these drawings, an arrow pointing downward to the left indicates a pointer for the write destination address of the cluster data, that is, a write destination pointer. An arrow pointing to the upper left indicates a pointer for 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 indicated by arrows w1 and w2. The read cluster data is stored in the double buffer 15 in the write destination pointer WP1,
The data is sequentially stored in the position indicated by WP2.

{52-7_54A} Of the AOB_FRAME included in the cluster data thus stored, the AOB_FR existing at the position designated by the read destination pointer
The AME is sequentially de-selected as indicated by arrows r1, r2, r3, r4, r5 ...
It is output to the scrambler 7. Here, the cluster data 002,003 is stored in the double buffer 15,
If the read destination indicated by the read destination pointer moves as shown in (5) in FIG.
Since all of the AOB_FRAMEs included in are read, the cluster 004 is newly read, and the area occupied by the cluster 002 is overwritten as indicated by the arrow w6 in FIG. 54 (a).

{52-8_54B} Further, when the reading destination indicated by the reading destination pointer moves as shown by and reaches to, it means that all the AOB_FRAMEs included in the cluster 003 have been read. Read cluster 005 to
As shown by an arrow w7 in FIG. 54B, the area occupied by the cluster 003 is overwritten. As above, AOB_FRAM
The output of E and the overwriting of 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} Playback Control Program Stored in ROM 4 Next, the playback control program stored in the ROM 4 will be described. FIG. 55 is a flowchart showing the processing procedure of the AOB file read processing, and FIGS.
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 for instructing each of a plurality of DPL_TK_SRPs, and the variable z is each AOB file, its corresponding TKI, and its included. This is a variable for uniquely indicating the AOB to be stored. The variable y is a variable for designating each AOB_ELEMENT included in the AOB # z designated by the variable z, and the variable x is the AO designated by the variable y.
This is a variable that indicates each AOB_FRAME included in B_ELEMENT # y. First, the processing procedure of the AOB file reading processing will be described with reference to FIG.

{52-9_55-2} In step S1, the CPU 1
0 reads PlayListManager, Default_Playlist
List information and PlayList information. In step S2, the CPU 10 waits for specification of which of Default_Playlist information and PlayList information is used to reproduce the AOB. Here, if Default_Playlist information is specified, the process proceeds from step S2 to step S3, the variable w is initialized (# w ← 1), and in step S4, by DPL_TKIN associated with DPL_TK_SRP # w in Default_Playlist information. Specified TKI # z is specified and only that TKI # z is TKI
Read to storage area 13. Then, in step S5, the AOB file #z having the same number as the TKI #z is specified.
By the steps so far, the AOB file to be played is finally specified. The identified AOB file is
Since it has been encrypted, the processing of steps S6 and S7 is performed thereafter to cancel the encryption of this AOB file. That is, in step S6, the protected area is accessed and the AOB file #
The FileKey # z stored in the File Key Entry # z having the same number as z is read. CPU10 in step S7
Sets FileKey # z to descrambler 7. Since the FileKey is set in the descrambler 7 by such setting, if the AOB_FRAMEs included in the AOB file are sequentially input to the descrambler 7 thereafter, the AOB_FRAMEs are sequentially reproduced.

After {52-9_55-3}, each cluster storing the AOB file is sequentially read out. Step S8
Then, the "file first cluster number" for the AOB file #z in the directory entry is specified, and in step S9, the CPU 10 reads the data stored in the cluster from the flash memory card 31. In step S10, it is determined whether or not the cluster number is described as FFF in the FAT value, and if the FAT value is
If the value is other than FFF, the data stored in the cluster designated by the FAT value is read in step S11. After such reading, the process proceeds to step S10. Here, when reading the data stored in any of the clusters and referring to the FAT value associated with that cluster, as long as any cluster number other than FFF is described in the FAT value, The processing from step S10 to step S11 is repeated. This allows that FA
The clusters designated by the T value are sequentially read out. When the cluster number is described as FFF in the FAT value, it means that all the clusters forming the AOB file #z have been read out, so that steps S10 to S
Move to 12.

{52-9_55-4} The CPU in step S12
10 determines whether or not the variable #w matches the total number of DPL_TK_SRP. If they do not match, the process proceeds to step S13, increments the variable #w (# w ← # w + 1), and then proceeds to step S4. Default_Pl in step S4
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 into the TKI storage area 13. At this time, the TKI that has been used until then is stored in the TKI storage area 13, but the CPU 1
0 overwrites the TKI already stored in the TKI storage area 13 with the newly read TKI. Due to such overwriting, only the latest TKI is stored in the TKI storage area 13. If the TKI is overwritten in this way, the processes of steps S5 to S12 are repeated for the AOB file #z. The processing of Step S5 to Step S12 is repeated, and all the Default_Playlist information includes
If the TKI and AOB files corresponding to DPL_TK_SRP are read, the variable #w and the total number of DPL_TK_SRP match, 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 executes AOB_FR according to the flowcharts of FIGS. 56, 57 and 58.
Perform AME output processing. In this flowchart, play_ti
me is a variable indicating the elapsed time of the reproduction, that is, the elapsed reproduction time, and the display contents of the time in the time display frame of the liquid crystal display 5 are rewritten according to the update of the play_time. Also, play_data is the data length that has been played so far.

{52-9_56-1} In step S21, C
The PU 10 monitors whether the cluster data for AOB file #z has been accumulated in the double buffer 15. This step S21 is repeated unless the cluster data is accumulated. However, if the cluster data is accumulated, #x and #y are initialized in step S22 (# x ← 1, # y
← 1), then in step S23, AOB file
BIT # z included in TKI # z in the cluster about #z
AOB_FRAM in AOB_ELEMENT # y from Data_Offset onwards
Detect E # x. Assuming that the 7 bytes from SZ_DATA are occupied by the ADTS header, refer to the ADTS header, analyze that the data length indicated in the ADTS header is the audio data of the main body, and And the audio data of the main body are read and output to the descrambler 7. If the descrambler 7 decrypts the AOB_FRAME and the AAC decoder 8 decrypts it, it will be reproduced as voice.

{52-9_56-2} After detection, AOB_FRAME # x is output to the descrambler 7 in step S24, and the reproduction elapsed time play_time is AOB_F in step S25.
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 reproduction time length of AOB_FRAME is 20 msec, 20 msec is added to the reproduction elapsed time play_time.

If the first AOB_FRAME is output to the descrambler 7, A of AOB_FRAME # x is output in step S26.
Refer to the DTS header to identify where the next AOB_FRAME is. In step S27, the variable #x is incremented (# x ← # x + 1), and the next AOB_FRAME is AOB_FRAME.
#x. In step S28, AOB_FRAME # x is put into the descrambler 7. Then, in step S29, play_time is incremented by the playback 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 determines whether or not #x has reached "FNs_1st_TMSRTE". If #x does not reach "FNs_1st_TMSRTE", it is checked in step S31 whether a 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
Until a key other than the ay key is pressed, step S26-
The process of step S31 is repeated. Play here
When any key other than the key is pressed, this flowchart is ended and the 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 playback process is paused.

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

Then, in step S33, TKTMSRT
Calculate the start address for AOB_ELEMENT # y by referring to. After that, the processing including steps S34 to S42 is performed. The process of steps S34 to S42 can be said to be the same as the process of steps S24 to S31 in that the AOB_FRAME included in the AOB_ELEMENT is read one after another. The difference from the processing of steps S24 to S31 is that the end condition of the loop processing in the latter is #x reaches “FNs_1st_TMSRTE”, whereas the end condition of the loop processing in the former is #FNs_Middle_TMSRTE. 』Is reached. #
When x reaches "FNs_Middle_TMSRTE", step S34-
When the loop process including step S42 ends, step S41 becomes Yes and the process proceeds to step S43.
In step S43, the CPU 10 increments #y and initializes #x (# y ← # y + 1, # x ← 1). After that, in step S44, the variable y is TMSRT_ of TKI # z.
It is determined whether the value equal to (TotalTMSRT_entry_Number-1) in 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 moves from step S44 to step S32, and thus step S3
The process of 2 to step S42 is continuously performed. #y is (Total
TMSRT_entry_Number-1), the last AOB_ELEME
It is considered that the reading process of AOB_FRAME has been completed up to AOB_ELEMENT one before NT, so step S44 is Yes.
Therefore, the process proceeds to step S45 of FIG.

{52-9_57-2} The processing of steps S45 to S54 is performed by the plurality of A's included in the last AOB_ELEMENT.
It can be said that the processing is the same as the processing of steps S33 to S42 described above in that it is the processing of reading each OB_FRAME. The difference is that the loop processing in steps S33 to S42 is performed in step S41.
While the end condition of the loop processing is that #x reaches “FNs_Middle_TMSRTE”, in step S53,
The point where #x is “FNs_Last_TMSRTE” and Play_data indicating the data size read so far reaches SZ_DATA is the end condition of the loop processing.

The processes of steps S49 to S54 are repeated until the condition of step S53 is satisfied, and if this condition is satisfied, step S53 is Ye.
s, and the process proceeds to step S55. Step S5
In 5, the CPU 10 increments #z and then moves to step S21 (# z ← # z + 1) to wait 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 processes of steps S22 to S54 are repeated for the next AOB file. That is, the next DPL_TK_SRP
The TKI specified by DPL_TKIN is specified, and the AOB file corresponding to that TKI, that is, the AO having the same number as the TKI
Identify the B file. After that, access the protected area, identify the FileKey that has the same number as the TKI in the encryption key storage file, read the FileKey, set the FileKey in the descrambler, and then use the same number as that TKI. AOB_FR included in AOB file with
The AME is read out in sequence and played back.

{52-9_57-3_59} Update of elapsed playback time FIG. 59 is a diagram showing that the elapsed playback time displayed in the time display frame of the liquid crystal display 5 increases as the variable Play_Time is updated. is there. In the figure (a), the playback elapsed time is 00: 00: 00.000, but when the playback of AOB_FRAME # 1 is completed, the playback length is 2 hours of AOB_FRAME.
0msec is added and updated to 00: 00: 00.020. AOB
When the playback of _FRAME # 2 ends, AOB_
FRAME time length of 20msec is added to 00: 00: 00.040, AOB
When the playback of _FRAME # 6 is finished, the playback elapsed time is 00: 0
You can see that it is 0: 00.120.

The above is the whole picture of the AOB_FRAME output processing.
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, and there is a pause key or a stop key as such a key other than the Play key. Has also been explained, but in addition to the pause key and stop key,
Even when a key for causing the playback device to perform special playback is pressed, the processing of the flowcharts of FIGS. 56, 57, and 58 is interrupted, and the processing corresponding to the pressed key is executed. After that, the >> key is pressed and the processing procedure of the CPU 10 when executing the forward search reproduction, and the time search function is executed by operating the jog dial after pressing the pause key or stop key. CPU when
The processing procedure of 10 will be described.

{52-10_60} Forward Search Reproduction FIG. 60 is a flowchart showing the processing procedure of the CPU 10 when performing forward search reproduction. >> key is pressed by the operator and step S3 in FIGS. 56, 57, and 58
This flowchart is executed by the CPU 10 when the answer to Step 1, Step S42, and Step S54 is Yes.

At step S61, the CPU 10 sends AOB_E
LEMENT # y AOB_FRAME # x to x + f (t) -1 are thrown into 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 reproduction time, in step S62, play_time indicating the reproduction elapsed time and play_data indicating the number of reproduced data are defined as t: intermittent reproduction 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_
It corresponds to the playback time length of FRAME). ).

{52-10_60-1_61A, B} FIG. 61 (a),
FIG. 7B is a diagram showing how the reproduction elapsed time is incremented during forward search reproduction. Figure 6
1 (a) shows 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 reproduction elapsed time in this case is 00: 00: 01.000. Here, as the intermittent playback time, the 1st to 12th AOB_FRAMEs are thrown into the descrambler 7,
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 increments the AOB after the increment.
_FRAME # x is compared with the total number of frames in AOB_ELEMENT # y, and AOB_FRAME # x after increment is AOB_ELEMENT
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 ”, the number of frames of the last one is“ FNs_Last_TMSRT
E ”, the determination is made by comparing these with AOB_FRAME # x. If updated AOB_FRAME # x
Is not present in AOB_ELEMENT, step S64
At, it is determined whether there is an AOB_ELEMENT following AOB_ELEMENT # y. Where AOB_ELEMENT # y is the last AOB_ELE
If it is MENT and there is no following AOB_ELEMENT,
When step S64 is No and the process of this flowchart ends, but when there is a subsequent AOB_ELEMENT, in step S65, AOB_FRAME # x to AOB_ELEMENT # y.
Reduce the number of frames in
By updating (y ← y + 1), AOB_FRAME # x is converted to the frame position of AOB_FRAME in the subsequent AOB_ELEMENT # y. If the updated AOB_FRAME # x exists in AOB_ELEMENT, these steps S65 to S6.
Skip 6 and move to step S67.

{52-10_60-3} Subsequently, AOB_FRAME # x, reproduction elapsed time play_time, and the number of reproduced 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, AOB_FRAME # x, playback elapsed time play_time, and number of played data play_data are updated using these in step S67 (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
B_ELEMENT is updated to the next AOB_ELEMENT, and AOB_FRAME # x is converted to the frame position in AOB_ELEMENT # 52 by 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 elapsed playback time is 2.000 at 00: 00: 01.240.
By adding, it becomes 00: 00: 03.240. AOB_FRAM
E # x is AOB_FRAME # 62 (= (3240ms
ec-2000msec) / 20msec).

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

If AOB_FRAME # x and AOB_ELEMENT # y are incremented according to the intermittent playback time and the intermittent skip time, the CPU 10 at step S72 determines that TKTMSRT
AOB_FRAME # x is detected by calculating the start address for AOB_ELEMENT # y by referring to, and starting the ADTS header search from the start address in AOB_ELEMENT # y in step S73. Then, in step S74
In step S61, after it is determined whether or not any key other than the forward skip key is pressed, AOB_ELEM is determined.
AOB_FRAME # x to x + f (t) -1 of ENT # y are input to the descrambler 7, and the processes of steps S62 to S73 are repeated.

With the above processing, AOB_FRAME # x, AOB_ELEME
NT # y is incremented and the playback position advances.
After that, if the operator presses the reproduction key, step S74 becomes No, and the processing of this flowchart ends. {52-11} Execution of the time search function The processing when the time search function is performed will be described. A list of tracks in the Default_Playlist information is displayed, and designation of any track is accepted. When the track is specified and the jog dial is operated, the playback start time is updated. When the playback key is pressed after the playback start time has increased or decreased, the time specified for that playback will be changed to Jmp_Entry.
Specify (seconds). On the other hand, the specified track has multiple AO
Determine if it consists of B or a single AOB. single
If it consists of AOB, AOB_ELEMENT # y that satisfies {Equation 2}
And AOB_FRAME # x are calculated. AOB that satisfies {Equation 2}
If _ELEMENT # y and AOB_FRAME # x are calculated, in TKTMSRT corresponding to this AOB, the search for AOB_FRAME # x is started from the address located at the y + 2nd position, and if the xth AOB_FRAME is searched, this Playback starts from the xth AOB_FRAME.

{52-12} AOB # n, AO that satisfies {Equation 3} when it consists of multiple AOBs
Calculate B_ELEMENT # y and AOB_FRAME # x. {Formula 3}
If AOB # n, AOB_ELEMENT # y, and AOB_FRAME # x satisfying the above are calculated, in the TKTMSRT corresponding to this AOB # n, the search for AOB_FRAME # x is started from the address located at the y + 2nd position, and the xth position If AOB_FRAME is searched, this xth AOB
Start playback from _FRAME.

[0209] Next, FNs_1st_TMSRTE in BIT is 80 frames, FNs_Last_TMSRTE is 50 frames, and FNs_Mid.
In the AOB in which dle_TMSRTE is 94 frames, a case where reproduction is started from an arbitrary reproduction time will be described. {52-13_62A, B} Here, as a specific example of when the time search function is performed, when the playback start time is specified by the jog dial, the AOB_ELEMENT at which playback should start and the frame position at which playback should start Will be described. FIG. 62 is a diagram showing a specific example when the time search function is performed. Here, as shown in FIG.
When the playback device is gripped and a certain AOB is designated as the playback target, the thumb of the right hand rotates the jog dial to start the playback start time = 00: 04: 40.000 (= 28
(0.00 sec) shall be specified. About this AOB TKI
62B, if the reproduction start time = 00: 04: 40.000 (= 280.00sec) is applied to {Formula 2}, 280sec = (FNs_1st_TMSRTE + FNs_middle_TMSRTE ・ y + x) × 20msec = (80 + 94/148 + 8) x 20 msec, so AOB_ELEMENT # y, AOB_F that satisfies {Equation 2}
As RAME # x, AOB_FRAME with y = 148 and x = 8 is obtained.

Since y = 148 is thus specified, the entry address of the y + 2nd AOB_ELEMENT # 150 (= 148 + 2) is T
Get it from KTMSRT and from the 8th AOB_FRAME from here,
If you start playback, playback elapsed time = 00: 04: 40.000 (= 280.
Playback can be started from (00 sec). {52-14_63_64_65} Above, the description of the processing content of the CPU 10 when the Play key is pressed is finished. Next, the edit control program stored in the ROM will be described. This edit control program is executed when the Edit key is pressed, and its processing procedure is shown in FIGS. 63, 64, and 65. Hereinafter, the processing contents of the edit control program will be described with reference to these flowcharts.

{52-14_63-1} Edit control program Dialog that presents to the operator which of the typical edit operations such as deletion, division, and integration to be performed in step S101 of FIG. 63 when the Edit key is pressed The screen is displayed, and then, in step S102, it is determined whether the process for the interactive screen is designated. Here, in the operation of the interactive screen, the >> | and | << keys are used as keys for accepting the up / down cursor operation, that is, the up / down cursor keys. When the deletion process is designated, the process moves to the loop process including steps S103 and S104. In step S103, it is determined whether the >> | key or | << key is pressed, and in step S104, it is determined whether the edit key is pressed. If the >> |, | << keys are pressed, the process proceeds 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 TKI_BLK_ATR of the TKI for the specified track is set to “Unus
Delete the specified track by setting "ed".

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

When the edit target of the second track is specified,
If step S109 becomes Yes, the process proceeds to step S112. In step S112, the preceding track,
AOBs located at the end and beginning of both tracks by referring to the TKI BIT for the following tracks
(If there are AOBs before and after that, A before and after that
OB) type is Type1 or Type2.

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

{52-14_64-1} Track division processing When the division of a track is designated, the processing shifts from step S102 to loop processing including steps S116 to S117. In the loop processing including steps S116 to S117, the pressing of the >> | key, the | << key, and the pressing of the edit key are accepted. If the >> ||, | << keys are pressed, the process proceeds from step S116 to step S118, and the designated track is designated as the editing target.
If the edit key is pressed, step S117 becomes Yes and the process moves to step S119. In step S119, the track designated by the cursor key is designated as the editing target. Then, in step S120, the reproduction of the track for which division is designated is started, and step S1
At 21, the depression 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 the loop process including steps S122 to S123. In step S122, the rotation operation for the jog dial is accepted, and when the rotation operation is performed for the jog dial, the reproduction start time is increased or decreased in accordance with the rotation operation in step S124. After that, the process returns to the loop process including steps S122 to S123. If the edit key is pressed while the reproduction start time is increased or decreased by the rotation operation, step S123
Then, the process proceeds from step S125 to step S125, where the playback time when the edit key is pressed is designated as a division boundary (note that the undo function (cancellation of editing) can be used when the division boundary is designated). After that, in step S126, the processing explained in FIG.
Track division is performed by updating LI and TKI.

{52-14_65-1} Play list setting / editing process When play list 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 playback order is defined by the playlist to be set, and in the flowchart of FIG.
After setting 1 to this variable k in 131, step S
Then, the process proceeds to the loop process including 132 to step S134. In the loop processing including steps S132 to S134, the pressing of the >> | key, the | << key, the pressing of the edit key, and the pressing of the stop key are accepted. If the >> | key or | << key is pressed, steps S132 to S1
In step 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 designated by the edit key is specified as the k-th track to be reproduced. Then, in step S137, the variable k is incremented, and steps S132 to S134 are performed.
Move to the loop processing of. By repeating such processing, the second track, the third track, and the fourth track are sequentially specified. In this way, when the stop key is pressed while a plurality of tracks to be reproduced are specified in the newly created playlist, the process proceeds from step S134 to step S138 and is associated with these. PlayLi consisting of PL_TK_SRP that identifies the TKI
Generate st information.

(Recording Device) {66-1} Recording Device Next, an example of the recording device of the flash memory card 31 will be described. FIG. 66 is a diagram showing an example of a recording device of the flash memory card 31. The recording device in the figure is capable of communication via the Internet, and when the SD_Audio directory is encrypted by electronic music distribution and is transmitted via a communication line,
Alternatively, it is a general-purpose personal computer capable of receiving audio data transport streams when they are delivered by electronic music delivery.

{67-1} Hardware Configuration of Recording Device FIG. 67 is a diagram showing the hardware configuration of the recording device. In the figure, the 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 voice input from a microphone to obtain PCM data, and unit time ACC encoder 25 that obtains AOB_FRAME by encoding per PCM data and adding ADTS header, and FileKey for each AOB file
Scrambler 26 for encrypting AOB_FRAME using
And when SD_Audio directory is encrypted and transmitted via the communication line by electronic music distribution,
Alternatively, when the audio data transport stream is transmitted through the communication line by electronic music distribution, the modem device 27 that receives the audio data transport stream and the 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 in the data area and protect area by electronic music distribution is transmitted via the communication line in an encrypted state, the recording device It is sufficient to write the data in the data area and the protect area of the flash memory card 31 at the time of properly receiving. However, if the audio data transport stream itself is transmitted by electronic music distribution instead of the SD_Audio directory, or if it is input to the recording device in the PCM data state, it is input to the recording device in the original sound state. If it comes, the recording device is
The audio data transport stream is written to the flash memory card 31 via one input path.

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

{67-4} Input Route RT2 The input route RT2 is an input route when voice is input from a microphone. In this case, the A / D converter 24 is caused to perform A / D conversion on the voice input from the microphone to obtain PCM data. Then, by causing the AAC encoder 25 to encode the PCM data and adding the ADTS header,
Get AOB_FRAME. After that, each AOB is sent to the scramble unit 26.
By encrypting AOB_FRAME using the FileKey for each file, encrypted audio data is obtained. 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 the PCM data read from the CD is input to the device. Since it is input in the state of PCM data, the PCM data is A
It is input to the AC encoder 25. So typed
AOB_FRAME is obtained by causing the AAC encoder 25 to encode the PCM data and adding the ADTS header. After that, the scramble unit 26 is configured to fill the Fil for each AOB_FRAME.
By encrypting AOB_FRAME using eKey, encrypted audio data is obtained. After that, 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 streams input through the three input paths RT1, RT2, RT3 into the flash memory card 31. With the storage of such audio data, TKI, Default_Playlist
Information is generated. Similar to the case of the reproducing apparatus, the functional entity of the recording apparatus is also the recording program recorded in the ROM. That is, AOB recording, TrackManager, PlayListM
The processing peculiar to this embodiment such as recording of an anager is realized by a recording program recorded in the fixed disk device.

{67-7_68} From the processing procedure of the recording processing, referring to the flowchart, the input path RT
A description will be given of a processing procedure of recording processing when the transport stream is written in the flash memory card 31 in 1, RT2, RT3, and RT4. FIG. 68 is a flowchart showing the processing procedure of the recording processing. Frame_Number and Data_S are variables that are referred to in this flowchart.
There is something like ize. Frame_Number is so far A
Data_Size is a variable for managing the total number of AOB_FRAME 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 flow chart is executed, in step S200, the CPU 28 determines DefaultPlaylist, Track
Manager is created, and in step S201, the variable #z,
Initialize #w (z ← 1, w ← 1). In step S202, the AOB file #z is created and stored in the data area of the flash memory card 31. In this state, the directory entry of the SD_Audio directory in the data area is set with the file name, file extension, and first cluster number of the AOB file #z.
In the following step S203, the CPU 28 creates TKI # z and stores it in TrackManager, and in step S204, the CPU 28 creates DPL_TK_SRP # w and 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).

In step S207, the CPU 28 determines that the AOB
It is judged whether the input of the audio data transport stream to be written in the file #z is completed. AAC
The scrambler 26 is encoded by the encoder 25.
If the audio data transport stream encrypted by is successively stored in the RAM 22 and it is necessary to continue writing the cluster data, step S207 becomes No and the process proceeds to step S209. In step S209, the CPU 28 sets A for the cluster size.
It is determined whether the AC audio data is accumulated in the RAM 22. When the cluster data is accumulated in the RAM 22, step S209 becomes Yes, the process proceeds to step S210, the AAC audio data of the cluster size accumulated in the RAM 22 is written in the flash memory card 31, and then the process proceeds to step S211. When the accumulation of cluster data is not 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 to its AOB_FRAME
Increment by the data size of. After performing such update, in step S212, Frame_Number is
It is determined whether the number of frames defined as "FNs_Middle_TMSRTE" has been reached. Here, "FNs_Middle_TMSRT
Since “E” has a value according to the sampling frequency when the audio data transport stream is encoded, when Frame_Number reaches “FNs_Middle_TMSRTE”, step S212 is Yes, but otherwise. Step S212 becomes No, and step S20
Move to 7. After that, step S207 and step S2
Until S12 becomes Yes, steps S207 to S207
Step 212 is repeated.

When Frame_Number reaches “FNs_Middle_TMSRTE” and Yes is obtained in step S212, the process proceeds from step S212 to step S213, and Data_Size is set to A.
TK of TKI # z as TMSRT_entry # y about OB_ELEMENT # y
After storing 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 252 is a value indicating the total number of AOB_ELEMENTs that can be stored in one AOB. 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 the audio data has reached the boundary between the tracks. When there is no silent state, the processes of steps S206 to S215 are repeated. When the variable y reaches 252, or when the silent state continues for a predetermined time or more, step S215,
Either one of step S216 becomes Yes, and the process proceeds to step S217 to increment the variables #z and #w (z ← z + 1, w ← w + 1). Then the incremented #z
For, the processing of steps S202 to S216 is repeated. By repeating this, multiple AOB_EL
AOBs including EMENTs are written in 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 finished, the input of the audio data transport stream to be written in the AOB file #z is finished. Therefore, step S207 becomes Yes and the process moves to step S208. In step S208, the CPU 28 sets Data_Size
T of TKI # z as TMSRT_entry # y about AOB_ELEMENT # y
After the audio data stored in the KTMSRT and stored in the RAM 22 is 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 releasing this encryption is protected by the following processing. Stored in. In the case of the input paths RT2 and RT3, the CPU 28 changes the Fi each time when the encoding of one AOB is started.
Generate a leKey, set it in the scramble unit 26, and set F
The scrambling unit 26 is encrypted by ileKey, and those FileKeys are stored after 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 containing TKMG, file containing PLMG, AO
The encryption key storage file that stores a different FileKey for each B
Sent from an electronic music distribution provider. CPU 28
Upon receiving them, the AOB file, the file storing the TKMG, and the file storing the PLMG are written in the user data area, and the encryption key storage file storing a different FileKey for each AOB is written in the protect area.

As described above, according to the present embodiment, the files storing the AOB are encrypted with different encryption keys, so the encryption key used to encrypt one file is decrypted, AOB that can be decrypted even if exposed is stored in one file
Only the AOB has no effect on the AOB stored in other files. The 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 effect can be expected at present. The present invention can be implemented and modified without departing from the gist thereof. Specifically, the modifications as shown in the following (a) to (f) are possible. (A) In the present embodiment, the description has been given assuming that the recording medium is a semiconductor memory (flash memory card), but the recording medium is not limited to this, and can be replaced with an optical disk such as a DVD-RAM or a hard disk.

(B) In the present embodiment, AAC is used as music data, but the present invention is not limited to this, and MP3
(MPEG 1 Audio Layer 3), Dolby-AC3, DTS (Digital
Theater System) or the like. (C) Instead of distributing the file storing TKMG and the file storing PLMG by electronic music distribution,
TKMG, PLMG source information, AOB file, distributed with the encryption key storage file that stores different encryption key for each AOB, in the recording device, by processing the TKMG, PLMG source information TKMG, You may obtain PLMG and record it in a flash memory card.

(D) For convenience of explanation, the recording device and the reproducing device are separate devices, but 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 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 mobile phone 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 mobile phone via the wireless network is described 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 the modem device 27 for connecting to the Internet, but instead of this, it may have a terminal adapter or the like for connecting to the ISDN line. Good.

(E) FIGS. 55-58, 60, 63-
The procedure described with reference to the flowcharts of FIGS. 65 and 68 may be realized by an executable program, and the program may be recorded in a recording medium to be distributed or sold. Such recording media include IC cards, optical disks, flexible disks, and the like, and the machine language programs recorded on these are provided for use by being installed in a general-purpose computer. This general-purpose computer sequentially executes the installed executable programs to realize the functions of the reproducing apparatus and the recording apparatus shown in this embodiment.

(F) Although a plurality of AOBs and a plurality of FileKeys are stored in the flash memory card 31 in this embodiment, one AOB is stored in the flash memory card 31.
You can store two FileKeys. Further, the AOB of the AAC method may be stored in the flash memory card 31 without encrypting the AOB. (Second Embodiment) The second embodiment relates to an improvement of 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 the flash memory card 3 according to the present embodiment.
It is a figure which shows the hierarchical structure of 1. The difference from the hierarchical structure of the first embodiment is that the POB group is newly added to the presentation data and the POB Manager is newly added to the navigation data in the second embodiment. These POB groups are JPEG (Joint Photographic Expert
s Group) format still image data and PlayListManager
And referenced by TrackManager. The POBManager is management information that describes how these POBs are referenced by the PlayListManager and TrackManager.

{69-1_70A-1} Configuration of User Data Area in File System Layer Since new information elements have been added to the presentation data and navigation data, the internal configurations of the user data area and protected area in the file system layer are as follows: It is modified as shown in FIGS. 70 (a) and 70 (b).
The difference between this figure and the user data area of the first embodiment shown in FIG. 8A is that files such as POBXXX.JPG and POBXXX.SP1 are added, and a file called POB000.POM is added. That is the point.

POBXXX.JPG and POBXXX.SP1 correspond to the POB group shown in FIG. 69, and POB000.POM is POBMana.
It corresponds to ger. POBXXX.JPG and POBXXX.SP1
The difference is the presence or absence of copyright. The former is simply JP
While the file contains still image data of the EG method, the latter is encrypted to protect the copyright of the still image (SP1 of the extension is "Secure Pictur
It is an abbreviation for "e", and it is clear from now on that there is a need for copyright protection.) Still image data such as family photos and commemorative photos taken by the user is exclusively for personal enjoyment. Originally, it is recorded on a flash memory card, and it is not necessary to be sensitive to copyright protection, so it is sufficient to store it in the flash memory card in the former form, but it is an artist distributed by electronic music distribution. Photos and illustrations are created by artists as well as music contents, and the copyright may be infringed by copying by the user, so they are stored in 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 each POB, 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 the protect area in the second embodiment. The protected area is shown in FIG.
Compared to the structure of the protected area shown in (b), the 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), and P
When reading OBXXX.SP1, you have to extract the Filekey from this file.

In electronic music distribution, the server computer of the music company uses SD_Aud shown in FIGS. 70 (a) and 70 (b).
If the consumer holds an io directory and a purchase request for the music content is issued, 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 computer owned by the consumer receives this SD_Audio directory, it decrypts this directory and decompresses it to obtain the SD_Audio directory. Incidentally, the truck
(AOB) and still image (POB) corresponding to this track are downloaded from the music company's server computer, and the computer owned by the consumer uses the flash memory card 3
In FIG. 1, the SD_Audio directory shown in FIGS. 70 (a) and 70 (b) may be created.

{69-3_71A, B, C-1} POBXXX.JPG, POBXXX.SP
1 Internal Configuration Next, the internal configuration of POBXXX.JPG and POBXXX.SP1 will be described. FIG. 71A shows the internal structure of POBXXX.JPG. In the figure, 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 consists of ader (POB_H) and encrypted still image data of the JPEG method. POB on the broken line hp1
The internal structure of _H is shown. As shown in this figure, POB_H is POB
Indicates the file identification number, POB_ID set to the 2-byte value "FFE0", 1-byte reserved area, and POBXXX.SP
It consists of a 1-byte length POB_ATR that indicates whether or not the encrypted substance part exists in 1, and a 4-byte length POB_SZ that indicates the POB data length.

[0244] Since POBXXX.SP1 has an encrypted entity, POB_ATR is set to "0" indicating "entity", but POBXXX.SP1 has an encrypted entity. Instead, some store the file path for the file storing still image data instead. Figure 7
FIG. 1C is a diagram showing an example of a POB file in which a file path is stored instead of the encrypted substance part. "\ DC
“Photo001.JPG” of “IM \ Ctg_001 \ photo001.JPG” is a file in which still image data taken by the digital still camera is recorded, and shows the file path for the file. When such a directory path and file name are specified in the POB file, the contents described in the POB file cause "\ DCIM \ Ctg_00
The still image data recorded in "photo001.JPG" of "1 \ photo001.JPG" will be indirectly referenced. This PO
In BXXX.SP1, POB_ATR in POBManager is set to "1" indicating "absent".

For example, recording still image data photographed by a digital still camera in a specific file,
Storing the file in a specific directory
Even if the device driver dedicated to the digital still camera requests the flash memory card (see FIG. 7).
In the example of 1 (c), the device driver dedicated to the digital still camera requires storage in \ DCIM \ Ctg_001 \ photo001.JPG), and the POB file in FIG. 71 (c) is the reference file. Since a JPG file containing still image data is specified via a path, while storing still image data shot by a digital still camera in a special file or special directory, such still images can be stored in the music content. It can be displayed during playback.

This concludes the description of the presentation data in the second embodiment. {72-1} PlayListManager and TrackManager POBXXX.JPG and POBX in the 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 for realizing synchronous display with tracks
r has the configuration shown in FIG. FIG. 72 is a diagram showing a detailed configuration of the PlayListManager and TrackManager in the second embodiment. The difference between the configuration of the PlayListManager and TrackManager of the first embodiment shown in FIG. 17 and that of the first embodiment shown in FIG. 17 is Default which has not been clarified in FIG.
Playlist General Infomation (DPLGI), Playlist Gener
The internal structure of al Infomation (PLGI) has been clarified, and TKI_POB_ATR and 20 TKI_POBs have been added to the internal structure of TKGI.
_SRP is newly provided.

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

{72-3} About PLGI For the entire playlist information (PLGI), see the broken line h62.
As shown in, P that describes the ID that can uniquely identify the PLI
The LI_ID field and the number of tracks referenced by PLI can be described, and up to 99 tracks can be referenced.
It is composed of a PLI_TK_Ns field, a PLI_PB_TM field in which a total of playback times of all tracks referred to by the playlist in units of 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 understood from the above description, TK in the present embodiment
Two pieces of information, TKI_POB_ATR and TKI_POB_SRP, are added to GI, and DPLI_POB_ATR-DPLI_POB_ is also added to DPLGI.
PLI_POB_ATR-PLI_POB is also included in two pieces of information called SRP, PLGI.
You can see that two pieces of information, _SRP, are added. T
KI_POB_SRP, PLI_POB_SRP, and DPLI_POB_SRP all have a common configuration, and POB can be designated. FIG. 73 is a diagram showing a state in which the POB file shown in FIG. 70 is designated by TKI_POB_SRP, PLI_POB_SRP, and DPLI_POB_SRP. After that, TKI_POB_ATR (DPLI_POB_ATR, P
LI_POB_ATR), TKI_POB_SRP (DPLI_POB_SRP, PLI_POB_S
RP) data structure is explained.

{74-1} TKI_POB_SRP TKI_POB_SRP is a POB to be displayed during a reproduction period in which a specific AOB is reproduced in a reproduction period specified by Default_Playlist information and PlayList information. This is a designated field. In other words, T
rackManager can specify the POB to be displayed for each track by setting TKI_POB_SRP.

FIG. 74 is a diagram showing a data structure of TKI_POB_SRP and TKI_POB_ATR. In this figure, TKI_POB_SRP
Is the "POB specification field" from bit number b25 to bit number b16, the "number of Pixel" field from bit number b11 to bit number b8, and the "Huffman table" field from bit number b7 to bit number b6. , Bit number b5 to bit number b4 "Chominance
"sampling" field, "Picture Coding Mode" field occupying bit number b3 to bit number b0, bit number b12 to bit number b15, bit number b26
To a reserved area from 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 when the AOB file corresponding to this TKI is being played. Is. When the AOB file corresponding to this TKI is being reproduced, "0" is described when a still image is not displayed. 『Picture Codin
The “g Mode” field is a field for notifying the reproducing apparatus of how the still image is encoded when the still image designated by the POB designation field is displayed. JPEG (Joint Photograph Expert Grou
In the case of p), the value of “0000b” is described.

The "Chominance sampling" field is set to P
This is a field that indicates at what ratio the luminance component and the two color difference components were sampled when the still image designated in the OB designation field was encoded. If the ratio of the luminance component and the two color difference components is 4: 2: 2, it is set to 00bit, and if it is 4: 2: 0, 01bit.
Is set to.

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

TKGI is TKI_PO having the above structure.
Since it has 20 B_SRPs, a maximum of 2 when playing a track.
You can play back 0 still images. If one track consists of multiple TKIs, only the first TKI of TKI_POB_SRP is valid. {74-2} TKI_POB_ATR "TKI_POB_ATR" is provided to specify in what mode the POBs specified by 20 TKI_POB_SRPs in TKGI are displayed. TKI_POB_ATR occupies from bit number b0 to bit number b1
It consists of a de field and a Display Timing mode field that occupies bit numbers b2 to b3.

[Display order mode] field is TK
The order in which POBs specified by 20 TKI_POB_SRP in GI are displayed is set. There are three modes of how to reproduce the POB during the reproduction time of the AOB. The first mode is up to 20 TKI_P in TKGI
This is the case where the POB specified by OB_SRP is displayed in the order of TKI_POB_SRP in TKGI, which is called sequential mode. The second mode is 20 TKI_P in TKGI.
This is a mode in which a POB specified by OB_SRP is randomly selected and played, and this is called a random mode. The third aspect is to set 20 TKI_POB_ in TKGI to avoid duplication.
This is a mode in which POBs designated by SRP are randomly selected and played, and it is called shuffle mode. Display order
A value of "00b" is set in the mode field when the sequential mode is set. On the other hand, a value of "01b" is set when the random mode is set, and a value of "10b" is set when the shuffle mode is set.

[Display Timing mode] field is T
Up to 20 POBs specified by TKI_POB_SRP in KGI
Is a field in which it is set whether or not to synchronize the display of and the reproduction of the AOB file associated with the TKI.
The mode in which the video and audio are synchronized is called the slide show mode, and it is not possible to skip only the video display. On the other hand, a mode in which video and audio are not synchronized is called a browsable mode, and only video display can be skipped.

As described above, TKGI is an AOB corresponding to itself.
Which POBs are to be displayed, in what order the POBs are displayed, and whether to synchronize the POB display with the playback of the AOB file associated with the TKI during the playing period of the file. Whether or not is set. {74-3_75} Setting Example of TKI_POB_SRP Included in TKI # 1 to TKI # 3 FIG. 75 is a diagram showing an example setting of 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. The TrackManager in the first row consists of 8 TKIs.
And the arrows indicate which POBs TKI_POB_SRP in those TKIs
Indicates if you are referencing a file. According to the reference relationship shown by the arrow, TKI # 1 includes three TKI_POB_SRPs, and these three TKI_POB_SRPs specify POB001 to POB003.
In addition, TKI # 2 includes three TKI_POB_SRP, and these three TKI_POB_SRP
POB_SRP is POB004-POB006, TKI # 3 is three TKI_POB_SRP
It can be seen that these three TKI_POB_SRP specify POB007 to POB009.

In this embodiment, POB001 to 009 use JPEG image data in which a character string indicating lyrics is arranged on a plain background. The character strings used to describe the lyrics here are drawn in a font that more closely matches the image of the lyrics, and contour enhancement and decoration are applied.
The bottom of FIG. 75 shows the contents of each POB. POB001
~ The content of POB003 is the lyrics card of TrackA, POB00
4 ~ POB006 contents are TrackB lyrics card, POB007 ~ POB00
The content of 9 is the lyrics card of TrackC. All of these are meaningless unless they are reproduced during the reproduction of each track. Therefore, TKI_POB_SRP included in the TKI is set to reproduce during the reproduction of each track.

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 the period, the setting of TKI_POB_SRP set in TKI becomes valid, and the playback device can display the POB according to the valid TKI_POB_SRP.

[0261] The playback time of AOB001.SA1 corresponding to TKI # 1 is
It is 6.1 minutes, and if the POB001 to POB003 are evenly displayed during this period, the display time per sheet is 2.03 minutes = (6.1
Min / 3). Play time of AOB002.SA1 corresponding to TKI # 2
3.3 minutes, the playback device has a display time of POB004 to POB006 per sheet of 1.1 minutes = (3.3 minutes / 3), and 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
B_SRP Setting Example FIG. 76 is a diagram showing a setting example of TKI_POB_SRP included in TKI # 4 to TKI # 8 included in TrackManager. The first row shows TrackManager, and the second row shows 10 POB files. According to the reference relationship indicated by the arrow, TKI # 4
Is the seven TKI_POB_SR indicated by the seven arrows in Fig. 76.
PB, and these seven TKI_POB_SRPs are POB010-P
OB016 is specified. Further, it can be seen that TKI # 8 includes three TKI_POB_SRPs, and these TKI_POB_SRPs specify POB017 to POB019. In the present embodiment, POB010 to 019
Similarly to 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 in I # 4, and TKI_POB is set in TKI # 5- # 7.
_SRP is not set because, 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 card of TrackD shown in FIG. 16 of the first embodiment, and the contents of POB017 to POB019 are the lyrics card 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 each POB can be displayed evenly during these periods. 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 TKI_POB_SRP can specify the POB to be displayed for each track, whereas DPLI_POB_SRP in DPLGI
Is the POB that should be displayed during the time when multiple AOBs are played according to the order specified by the Default_Playlist information.
Is to be specified. Figure 77: 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
It is clear from FIG. 77 that the data structure is the same as that of TKI_POB_ATR. Default_Playlist
Since the information defines the playback order of a plurality of AOB files, DPLI_POB_SRP and DPLI_POB_ATR in FIG.
Specifies which POBs to display, in what order the POBs should be displayed, the POB display, and TKI during the period in which multiple AOB files whose playback order is defined by Default_Playlist information are being played. It can be set whether or not to synchronize the reproduction of the AOB file associated with.

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

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

[0267] P specified by DPLI_POB_SRP included in this DPLGI during the period during which the AOB file whose reproduction order is specified by Default_Playlist information is being reproduced.
The OB file will be displayed. For example, in the example of FIG. 40, the default_Playlist information specifies the playback order of the five tracks TrackA to TrackE via eight TKIs. On the other hand, in the example of FIG. 78, Default_
20 POs by DPLI_POB_SRP included in Playlist information
Assuming that a B file is specified, DPLI_P according to this Default_Playlist information will be used in the playback time of 52.5 minutes.
The specification of OB_SRP is valid. Further, if the reproduction time of 52.5 minutes is evenly assigned to POB020 to POB039, the display time per sheet is 2.625 minutes = (52.5 minutes / 20).

{77-3_79} Foreground image with passage of playback time-
The background image transition diagram 79 shows DPLI_POB_S included in Default_Playlist information.
6 is a timing chart showing how these are combined when the POB designated by RP is the background image and the POB designated by TKI_POB_SRP included in TrackManager is the foreground image. The first row of FIG. 79 shows the same POB as the second row of FIG. 78, and the second row of FIG. 79 shows the same POB as the second row of FIGS. 75 and 76. It is shown. The horizontal direction of this figure is a time axis with 1 minute as a unit time. In addition, the width of the POB in this figure indicates how long the reproduction of each POB continues, in minutes.

Referring to the time axis of this figure, from the start of reproduction
In the period up to 6.1 minutes, POB001-POB003 (the lyrics card of TrackA) will be displayed as the foreground picture, and POB020, POB021 (jacket illustration and the logo of the production company) and POB022 (portrait of the artist) will be displayed as background pictures. Become. During the period from 6.1 minutes after the start of playback to 14.9 (= 6.1 + 3.3 + 5.5) minutes, POB004 to POB009 (TrackB, TrackC
Will be displayed as the foreground picture, and POB022 to POB025 (portrait of the artist) as the background picture.

[0270] After 14.9 minutes from the start of reproduction, POB010 to POB
B011 (TrackD lyrics card) is displayed as a foreground picture, and POB025 (portrait of the artist) and POB026 to POB028 (one scene of the promotion video) are displayed as background pictures. {77-4_80} According to this timing chart, Default_Pl
6.1 minutes after the aylist information starts to play, POB004 is used as the foreground picture (Track B lyrics), and POB022 (artist's photo)
A composite video with the background image of will be displayed. Figure 8
0 is a diagram showing how the foreground image and the background image are combined 6 minutes after the start of the reproduction of the Default_Playlist information.

{77-5_81} Also, after 16 minutes have passed from the start of playing the Default_Playlist information, POB010 (the lyrics of TrackD) is used as the foreground picture, and POB026 (one scene of the promotion video).
A composite video with the background image of will be displayed. Figure 8
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
By combining and displaying the POB file specified by TKI_POB_SRP in ger as the foreground image and the background image respectively, the lyrics about the track, the portrait of the artist who wrote and composed the track, the promotion video, the concert A scene or the like can be displayed as a background image. Moreover, which POB file is displayed in which time zone can be easily changed by rewriting TKI_POB_SRP and DPLI_POB_SRP in TrackManager and Default_Playlist information is included in PLI_POB_SRP and PLI_POB_ATR PLGI included in {82-1} PLGI. PLI_POB_SRP and PLI_POB_ATR are also DP
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. Figure 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 defines the playback order that is uniquely defined by the user, so PLI_POB_SRP and PLI_POB
_ATR is a POB display, which POBs are to be displayed, in what order they are to be displayed during the period in which a plurality of AOB files whose playback order is defined by PlayList information is being played. AO associated with TKI
The user can set whether or not to synchronize the playback of the B file with his / her own thoughts (Default_Playlist
The fact that the music company has set DPLI_POB_SRP in the information is only an example, and DPLI_POB_S in the Default_Playlist information is set.
The user may also freely set the RP. ).

{82-2_83} PLI_PO included in PlayList information
B_SRP Setting Example Next, a setting example of PLI_POB_SRP included in the PlayList information will be described. FIG. 83 is included in the PlayList information.
It is a figure which shows the example of setting of 20 pieces of PLI_POB_SRP. The first row shows PlayList information, and the frame included in it is PLGI,
20 PLI_POB_SRPs are shown. The second level is POB040-POB
Shows 20 POB files consisting of 059. According to the reference relationship shown by the arrow, 20 PLI_POB_SRPs are POB040 each.
~ POB059 is specified.

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

{82-3_84} Foreground picture with progress of playback time-
In the background image transition diagram 84, the POB specified by PLI_POB_SRP included in the playlist information is used as a background image, and the TKI included in TrackManager is included.
9 is a timing chart showing how these are combined when the POB designated by _POB_SRP is the foreground picture. The first tier in FIG. 84 shows the same POB as the second tier in FIG. 83, and the second tier in FIG.
5 shows the same POB as in the second row of FIG. 76.
The horizontal direction of this figure is a time axis with 1 minute as a unit time.
In addition, the width of the POB in this figure indicates how long the reproduction of each POB continues, in minutes.

[0276] In the figure, POB001 to POB003 (the lyrics card of TrackA) are the foreground images, POB040, POB041 (family photos and graduation photos), and POB042 are the background images in the period from immediately after the start of playback until 6.1 minutes have elapsed. Will be displayed. POB004-POB009 (TrackB, TrackC lyrics card) during the period from 6.1 minutes to 14.9 minutes
Is displayed as a foreground picture, and POB042 to POB045 (pictures of pets) are displayed as background pictures. After 14.9 minutes, POB010
~ POB011 (TrackD lyrics card) is used as POB04
5, POB046 ~ POB048 (commemorative photo when traveling to Europe)
Will be displayed as the background image.

[0277] The PO specified in the Default_Playlist information
B is the idea of the music content production company,
The POB specified in the image of the track of the music content or the talent image of the artist is specified, whereas the POB specified in the PlayList information is personally selected by the user, and I have a strong feeling.

{82-4_85} According to FIG. 84, POB004 is displayed in the foreground (TrackB
, And the composite image with POB042 (pet picture) as the 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 have passed from the start of playing the Playlist information, a composite image is displayed with POB010 (the lyrics of TrackD) as the foreground picture and POB046 (a photo of a European trip) as the background picture. FIG. 86 shows the start of playback of Playlist information.
It is a figure which shows how a foreground picture and a background picture are synthesize | combined after 16 minutes progress. The lyrics contents in these composite images are the same as those in FIGS. 80 and 81, but it can be seen that the impression seen is greatly different from the composite images shown in FIGS. 80 and 81 because the background images are different.

As described above, the Pl uniquely defined by the user
By allowing PLI_POB_SRP in ayList information to specify a POB file different from the POB file specified in Default_Playlist information, the user can display the photos, etc. related to their memories when playing the track of their memories. . {82-6_87} Setting example in which a common POB is designated in DPLI_POB_SRP of Default_Playlist information In the examples of FIGS. 78, 79, 82, and 83, Default_
I specified different POB files for all DPLI_POB_SRP included in Playlist information, but Default_Playlist
If one of the DPLI_POB_SRPs included in the information specifies a duplicate POB file, the number of POB files can be reduced by displaying a common POB file while multiple tracks are being played. Then
The time and effort of the title creator can be reduced. Fig. 87
Shows multiple DPLI_POB_SRP in Default_Playlist information
In this example, the number of POB files is reduced by having DPLI_POB_SRP specify a common POB file. In this figure, DPLI_POB_SRP # 1 and DPLI_POB_SRP # 4
Specifies POB020, and DPLI_POB_SRP # 2 and DPLI_P
It can be seen that POB021 is designated as OB_SRP # 5.

{82-7_88} Foreground image with the passage of playback time-
The background image transition diagram 88 is DPLI_POB_S included in Default_Playlist information.
6 is a timing chart showing how these are combined when the POB designated by RP is the background image and the POB designated by TKI_POB_SRP included in TrackManager is the foreground image. In this timing chart, POB020 showing the jacket illustration of the packaged software is repeatedly displayed three times immediately after the start of playback, after 7.875 minutes, and after 15.75 minutes. Also, it can be seen that POB021 showing the logo of the manufacturing company is repeatedly displayed three times after 2.625 minutes, 10.5 minutes, and 18.375 minutes from the start of reproduction. DPLI_POB_S as shown in FIG.
When the RP is specified, the same POB is repeatedly displayed, which is suitable when there are some POBs that should be repeatedly displayed, such as jacket illustrations and logo marks.

[0281] Although the long sentence has been described above, TKGI, DPLGI, PLGI
Finish the explanation. {69-4_89} About POBMG In the second embodiment, POBManager, which is a new information element added to navigation data, will be described. FIG. 89 is a diagram showing the internal structure of the POBMG. As shown in this figure, POBMG consists of POB management information (POBMGI) and POB Co
unt Information (POBCI) # 1 ・ ・ ・ ・ ・ ・ #n.

{69-4_89-1} About POBMGI The POB management information (POBMGI) is the POBMGI identification information that occupies the 0th byte to the 1st byte and the 2nd byte to the 3rd byte, as indicated by the broken line. Reserved fields that occupy the eyes
(reserved) and POB_ occupying 4th to 5th bytes
It consists of an Ns field and a reserved field (reserved) that occupies the 6th and 7th bytes.

In the POBMGI identification information field, an ID capable of uniquely identifying POBMGI is described (ISO646 character set code "A6"), and in the POB_Ns field, "
The number of POBs from 0 "to" 999 "is described.
The explanation of management information (POBMGI) ends. {69-4_89-2} About 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 lead line. That is, the POB_RCN field that occupies bit numbers b0 to b9, the reserved area field that occupies bit numbers b10 to b13, and the data existence field that occupies bit numbers b14 to 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 the POBCI is designated by DPLGI, PLGI, TKGI, and if designated, The specified number of times,
That is, the number of times the display is designated 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 playback order in the Default_Playlist information and PlayList information can be freely deleted. POB_
The number of POBs specified in refernce_count is the corresponding P
If the TKI that specified OB was deleted, the deleted TKI
Decremented by the number. Also, when Default_Playlist information and PlayList information are deleted, the deleted TKI
Decremented by the number. If the display is not specified by DPLGI, PLGI or TKGI, POB_refernce_count will be 0. A POB whose POB_refernce_count is 0 is any TK
Since it is a POB that is not referred to by I or PlayList information, the playback device, every time TKI and PlayList information is deleted,
Detecting the POB whose refernce_count_number is 0, r
PO that contains POB with 0 efernce_count_number
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 does not play in synchronization with that track, it makes sense to store that POB in a flash memory card. If it does not exist (for example, this corresponds to the case where a still image showing the lyrics of the track stored in the flash memory card is stored as still image data), refernce_c
By deleting based on the ount_number, there is no waste of storing extra POB in the flash memory card. In addition to the case where the TKI is deleted, the same refernce_count_number may be decremented when the POB specified by DPLI_POB_SRP, PLI_POB_SRP, TKI_POB_SRP is deleted by the editing operation.

Regarding {69-4_89-4} data existence, data e occupying bit number b14 to bit number b15
The xistence field specifies whether or not there is a POB corresponding to this POB number. If the POB corresponding to the POB number exists, it is set to 01b. If the POB does not exist,
00b is set. If the POB is specified to exist, the TKI and PlayList information is deleted, 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 in the flash memory card, and the POB is not deleted. T
If the POB alone has a storage value regardless of whether it is referenced by KI or PlayList information, set the data existance corresponding to that POB to 1, and if it is not referenced by TKI or PlayList information, the storage value There is no POB
By setting the data existance corresponding to the POB to 0, the POB having a save value can be left in the flash memory card. On the other hand, a POB that has a storage value only when it is integrated with a track can be effectively utilized by deleting the track and deleting the POB.

This is the end of the description of the POBManager (POBMG). {69-5} Update when editing TKI Four editing cases described in the first embodiment, when some tracks are deleted (case 1), any two of a plurality of tracks are changed to one track. When integrating with (case
3) How to update TKI_POB_SRP and DPLI_POB_SRP when one track is divided to obtain two tracks (case 4) and the track order is changed (case 5) will be described.

When the track is deleted (case 1), the first
As shown in the embodiment, TKI_BLK_ATR for that TKI
Is set to "Unused" and the TKI_P in that TKI
Delete OB_SRP. Along with that, the POB in the POBManager corresponding to the POB specified by that TKI_POB_SRP.
Decrement _refernce_count. POB specified by DPLGI, PLI_POB_SRP, DPLI_POB_SRP in PLGI
With regard to, there is no change due to its deletion.

[0288] 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 POB specified by TKI_POB_SRP is the order after the change. Regarding track integration (case 3), it is desirable to integrate TKI_POB_SRP in TKI. This is because, as described above, when one track is composed of multiple TKIs, TKI_POB_SRP is valid only for the first TKI.
The POB specified in TKI_POB_SRP of I is
This is because TKI_POB_SRP needs to be specified.

As described in the first embodiment, it is necessary to change TKI_BLK_ATR of TKI and divide TKTMSRT and BIT into two when dividing a track (case 4). Similarly, a plurality of TKI_POB_SRP specified by TKGI may be divided into two, and the original TKI and the TKI obtained by the division may be distributed. {69-6} Application example of TKI_POB_SRP and DPLI_POB_SRP settings In the data structure of TrackManager and PlayListManager described above, the correspondence between AOB files and POBs is TKI_POB.
Since it can be freely changed by setting B_SRP, DPLI_POB_SRP, and PLI_POB_SRP, the music content provider can provide a still image such as a type without lyrics, a type with lyrics, and a type with lyrics and background image. It is possible to sell a plurality of music contents having different prices to consumers depending on the amount of data.

When the consumer desires to purchase the type without lyrics, the eight AOB files shown in the first embodiment and the POB020 to POB039 shown in FIG. 78 are replaced by TK in TKI # 1 to TKI # 8.
SD_Audio including TrackManager specified in I_POB_SRP
Create a directory, compress it, and send it to a consumer-owned general-purpose personal computer. still,
Track (AOB) and still image (POB) corresponding to this track
Are downloaded from the server computer of the music company, and the computer owned by the consumer is shown in FIGS. 70 (a) and 70 (b) in the flash memory card 31.
You may create an SD_Audio directory.

When the consumer desires to purchase a certain type of lyrics, the eight AOB files shown in the first embodiment and POB001 to POB019 corresponding to the lyrics shown in FIGS. 75 and 76 are displayed.
TrackMa specified in 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 that has lyrics and a background image, the eight AOB files shown in the first embodiment and the POB001 to POB019 corresponding to the lyrics are set to TKI # 1 to TKI # 8.
Create an SD_Audio directory that contains the TrackManager specified in TKI_POB_SRP and the PlayListManager specified in DPLI_POB_SRP in POB020 to POB039 shown in FIG. do it.

In this embodiment, TKI_POB_SRP, DPLI_POB_.
By setting SRP and PLI_POB_SRP, it is possible to attach arbitrary still image data to the audio data. Therefore, it is possible to easily create music contents having different price ranges depending on the amount of the attached still image data. {90-1_91} Playback Device According to Second Embodiment Next, the playback device according to the second embodiment will be described. The reproducing apparatus according to the second embodiment differs from that of the first embodiment in three major points. The first difference among them is that the reproducing apparatus in the first embodiment is portable, whereas the reproducing apparatus in the second embodiment is in-vehicle. FIG. 90 is a diagram showing how the reproducing apparatus according to the second embodiment is used, and FIG. 91 shows the second reproducing apparatus.
FIG. 3 is a diagram showing an external appearance of only the playback device main body according to the embodiment. In the figure, the playback device according to the second embodiment is the first
Unlike the reproducing apparatus according to the embodiment, the reproducing apparatus according to the second embodiment is installed inside a vehicle as shown in FIG. 90 and is connected to a large liquid crystal display 5 and a vehicle-mounted speaker. It is a point. Since the liquid crystal display 5 connected to the reproducing device is large, the reproducing device according to the second embodiment can suitably display the various still image data described above.

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

{90-2_92_93_94} Subsequently, the internal configuration of the reproducing apparatus according to the second embodiment will be described. The internal structure of the playback device shown in FIG. 92 differs from that of the first embodiment in that a plurality of VRAMs 61 are provided. The plurality of VRAMs 61 are VRAMs each corresponding to one graphics plane 0.
VRAM for each graphics plane is 0% to 10 for each pixel
The transmittance α of 0% is set, and the pixel value of the image to be displayed on the liquid crystal display 5 is calculated by the following formula. FIG. 93A is a diagram showing how still images stored in a plurality of VRAMs 61 are overlaid. Pixel value of each pixel = pixel value of graphics plane 0 ×
(1-α) + pixel value of graphics plane 1 x α The character portion that represents the lyrics on the foreground side has 0% transparency.
Is set to. Therefore, the background image stored in the graphics plane 1 does not appear on the screen at all. In the plain background portion of the foreground image, the transmittance is set to 100%. Therefore, the background image stored in the graphics plane 1 is embedded in the plain portion of the still image in the graphics plane 0. Thus the transmittance α
By setting, it is possible to obtain a composite image in which a transparent sheet on which lyrics are described is covered with a background image, that is, a composite image as shown in FIGS.

In addition to the composite image shown in FIG. 93 (a), for example, as shown in FIG. 93 (b), a composite image in which 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 a 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 TKI_POB_SRP included in TKGI included in the TKI specifies a POB file. When TKI_POB_SRP specifies a POB file, the CPU 10 counts how many POB files are specified by TKI_POB_SRP included in TKGI in step S403. In step S404, the display time POB per POB file is calculated based on the number of POB files.
Determine _time. Then, in step S405, C
The PU 10 refers to TKI_POB_ATR in TKGI and refers to each POB
Determines in what display mode the file is displayed. 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 designated 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 SRP is JPG, the POB is displayed as it is. If the extension of the POB specified by TKI_POB_SRP is SP1 and it is encrypted, read the corresponding Filekey from the protected area, decrypt the encryption of the POB, and then delete the POB.
Is displayed. After that, in step S408, the variable i is set to P
It is determined whether or not OB_Ns has been reached, and if not reached, the variable i is incremented in step S409, and the process moves to step S407. After that, steps S406 to S409 are repeated until the variable i reaches POB_Ns. By this, P specified by TKI_POB_SRP of TKGI
OBs are displayed in sequence. When the variable i reaches POB_Ns, the processing of this flowchart ends.

If TKI_POB_ATR is described as the random mode, after initializing the variable i 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 rth TKI_POB_SRP
The OB file is displayed for the display time POB_time determined in step S404. Then, step S413
At, it is determined whether the variable i has reached POB_Ns. If not, the variable i is incremented at step S414, and the process proceeds to step S411. When the display ends, a random number r in the range from 1 to POB_Ns is generated again in step S411, the POB file designated by the r-th TKI_POB_SRP corresponding to the random number r is read in step S412, and step S404. Display only the display time POB_time determined in. At this time, as in the sequential mode, 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 by TKI_POB_SRP is SP1 and it is encrypted, read the corresponding Filekey from the protected area, decrypt the encryption of the POB, and then display the POB. To do.

Thereafter, step S411 to step S414 are repeated until the variable i reaches POB_Ns. As a result, POBs designated by TKI_POB_SRP of TKGI are displayed in random order. When the variable i reaches POB_Ns, the processing of this flowchart ends. TKI_POB_ATR
If is described as shuffle mode, step S
405 to step S415, and step S4
After initializing the variable i in step 15, step S416
In step S418, a random number r in the range of 1 to POB_Ns is generated. Then, in step S418, it is determined whether the generated random number r matches the displayed POB number. If they match, the process proceeds to step S416 to generate a random number again. If they do not match, the process proceeds from step S418 to step S419, and the r-th TKI_POB_ corresponding to the random number r.
The POB file specified by SRP is set to step S404.
Display only 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 POB specified in I_POB_SRP is SP1,
If the POB is encrypted, the corresponding Filekey is read from the protected area, the POB is decrypted, and then the POB is displayed. After finishing the display,
In step S417, the variable r is stored as the displayed POB number. Then, in step S420, the variable i
Has reached POB_Ns, and if it has not reached POB_Ns, the variable i is incremented in step S421, and the process proceeds to step S416. After that, steps S416 to S421 are repeated until the variable i reaches POB_Ns. As a result, POBs designated by TKI_POB_SRP of TKGI are displayed in sequence. When the variable i reaches 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 then the processing procedure of the background image display processing is described. FIG. 95 shows
It is a flow chart which shows a processing procedure of background picture display processing. This flowchart is shown in FIG. 94, “TKGI TKI_
The processing performed based on "POB_SRP, TKI_POB_ATR" is replaced with "DPPL_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, as in steps S402 to S405, step S5
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 POB file. The display time POB_time for each image is determined, and which display mode is used for display is determined according to DPLI_POB_ATR. DPLI_POB_ATR
Is described as a sequential mode, the POB files are sequentially displayed in accordance with the variable i in accordance with the variable i in accordance with the DPLI_POB_SRP included in the DPLGI in steps S506 to S509, as in steps S406 to S409.

If DPLI_POB_ATR is described as a random mode, POB files are sequentially displayed in accordance with DPLI_POB_SRP included in DPLGI in accordance with the variable r 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
In 5 to step S521, DPLGI is set according to the variable r.
Display the POB files sequentially according to DPLI_POB_SRP included in.

{96-1} Flowchart of Background Image Display Processing The description of the foreground image display processing in the case of referring to DPLI_POB_SRP of DPLGI is completed above, and PLGI's PLI_POB_SR is then continued.
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. This flowchart shows the processing performed based on "DPLGI's DPLI_POB_SRP, DPLI_POB_ATR" in FIG. 95 in "PLGI's PLI_POB_SRP, DPLI_PO".
B_ATR ”, and the basic processing procedure for the foreground image is the same as that in the flowchart in FIG. 95, so the same reference numerals are given and detailed description thereof is omitted.

{94-2_95-2_97A, B, C} Display example on liquid crystal display 5 The foreground image specified by TKI_POB_SRP and the background image specified by DPLGI are processed by the processing procedure shown in the flowcharts of FIGS. 94 and 95. FIG. 97 (a) shows what kind of composite image is displayed on the liquid crystal display 5 when composited.
~ (C).

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

After 16 minutes have passed from the start of reproduction, the image composition shown in FIG. 81 is performed, and the liquid crystal display 5 is displayed as shown in FIG.
The composite image shown in 7 (c) is displayed. {94-2_96-1_98A, B, C} Display example 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 procedure shown in the flowcharts of FIGS. 94 and 96. FIG. 98 shows what kind of composite image is displayed on the liquid crystal display 5 when
It shows in (a)-(c).

As shown in FIG. 98 (a), it is assumed that the PlayList information is specified and the POB display is started in accordance with the reproduction order described therein. In this case, the foreground image display process shown in the flowchart of FIG. 94 and the background image display process shown in the flowchart of FIG. 96 are performed and included in the POB and PLGI whose display is specified by the plurality of TKI_POB_SRP included in TKGI. POBs whose display is specified by multiple PLI_POB_SRPs are sequentially displayed. Therefore, the image composition shown in FIG. 85 is performed 6 minutes after the reproduction is started, and the liquid crystal display 5 is displayed.
Displays a composite image shown in FIG. 98 (b). Further, after 16 minutes have elapsed from the start of reproduction, the image combination shown in FIG. 86 is performed, and the combined image shown in FIG. 98 (c) is displayed on the liquid crystal display 5.

{99_1} Recording Device According to Second Embodiment Next, a recording device according to the second embodiment will be described. The recording device according to the second embodiment is new in that
While recording POB in the flash memory card 31,
The point is to set KI_POB_SRP, DPLI_POB_SRP, PLI_POB_SRP, and the point to set TKI_POB_ATR, DPLI_POB_ATR, PLI_POB_ATR. 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. 99. Hereinafter, the recording process of the recording apparatus according to the second embodiment will be described with reference to the flowchart of FIG. 99.

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

#U is a variable for identifying the DPLI_POB_SRP to be processed among the plurality of DPLI_POB_SRP, and #vy is #
Multiple PLI_POB_S included in PLI (PLI # y) indicated by y
It is a variable that identifies PLI_POB_SRP to be processed among RPs. #w is a variable that identifies the TKI_POB_SRP to be processed among the plurality of TKI_POB_SRP included in the TKI # y indicated by #z).

When these variables are initialized, POB # x is displayed in step S602. This allows the operator to visually confirm what kind of photo, illustration, and lyrics the POB is. In step S603, POB # x is a selection as to whether it is still image data to be displayed during the entire time period in which the track sequence is reproduced or still image data to be displayed only in the time period during which a specific track is reproduced. Is asked from the operator to accept any selection.

If the operator determines that "POB # x should be assigned to a track sequence", the process waits for the selection of the track sequence in which POB # x is to be displayed in step S604, and if a selection is made, 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 in DPLI_POB_SRP # u in DPLI in step S606, and DPLI_POB_ATR # u in DPLI is set in PO in step S607.
Set based on B # x. Thus DPLI_POB_SRP, DPLI_
If both POB_ATR are set, #u is incremented in step S608 (# u ← # u + 1), and then #x is incremented in step S609 (# x ← # x + 1).

When PLI is selected in step S605, PLI_P in PLI # y is selected in step S610.
Set POB # x in OB_SRP # vy, and in step S611
Set PLI_POB_ATR # vy in PLI based on POB # x. Then, after incrementing #vy in step S612 (# vy ← # vy + 1), the process proceeds to step S609 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 accepted.
Set POB # x to TKI_POB_SRP # w set to TKI # z for 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 #x has reached the POB last number #n. If not reached, the process proceeds to step S609 and #x is incremented. If #x reaches the last number #n of POB, at step S618 PO
The TKMG including the PLMGTKI including B # 1 to #n, DPLI and PLI is recorded in the flash memory card, and the process ends.

As described above, according to the present embodiment, still image data desired to be commonly displayed as a background image exists in a time zone in which a plurality of tracks are being reproduced, such as a photograph of an artist and a logo mark of a company. If Default_Play
DPLGI in list information and PlayList information, DPLI_ in PLGI
By specifying the still image data in POB_SRP and PLI_POB_SRP, common still image data is displayed during the time zone in which multiple tracks whose playback order is specified by their playlist information are being played. be able to. Also, if there is still image data such as lyrics that you want to display only during the period when a specific track is being played apart from the background image, such still image data is
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 effect can be expected at present.
The present invention can be implemented and modified without departing from the gist thereof. Specifically, the modifications as shown in the following (a), (b), and (c) are possible. (A) The procedure and the like described with reference to the flowcharts of FIGS. 94, 95, 96, and 99 may be realized by an executable program, and the program may be recorded in a recording medium for distribution / sales.

(B) The case where the presentation data and navigation data according to the present embodiment are applied to music contents has been described as an example, but the announcer and voice actor read the book aloud the presentation data and navigation data according to the present embodiment. It goes without saying that it may be applied to a reading book composed of voice. In this case, TKI_POB_SRP is used to specify a still image containing the text strings of the text in the book as the foreground image, while DPLI_POB_SR is used as the background image for the illustration of the document.
P, PLI_POB_SRP should be specified.

(C) In this embodiment, DPLI_POB_SRP-PL
The POB specified by I_POB_SRP is used as the background image, and TKI_
The POB specified by POB_SRP was used as the foreground picture, but the relationship between the two may be interchanged. In addition, DPLI_POB_S
RP-PLI_POB_SRP specified POB and TKI_POB_
Only one of the POBs designated by the SRP may be displayed. In addition, the POB may be displayed without distinguishing it from the foreground image and the background image. For example, DPLI_POB_SRP (PLI
Display the POB specified in (_POB_SRP), then TKI_POB_SR
It goes without saying that the POB designated by P may be displayed.

(Third Embodiment) In the second embodiment, Play
The POBs are displayed at an equal ratio during the period in which 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 to reproduce the voice. And the lyrics display are closely synchronized.

The former phrase period table is a table in which TKI_POB_SRP designating a POB indicating each lyrics is associated with information indicating the beginning / end of the phrase period. FIG. 100A is a diagram showing an example of the phrase period table. Here, the phrase period represents the period in which the phrase described in the lyrics appears in the time accuracy of the millisecond unit when the AOB is played back, and the playback device uses the playback progress as shown in the first embodiment. With the update of the time, it is monitored which of the phrase periods listed in the table the updated playback elapsed period corresponds to. By such monitoring, AOB, AOB_ELEMENT, AOB_FR which is currently being reproduced.
You can find out which POB contains the lyrics of AME. By using a table in which the time period of the POB phrase is described with the time accuracy of the millisecond unit, the AOB reproduction and the lyrics display can be synchronized with the time accuracy of the millisecond unit described above.

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

On the other hand, the latter highlight coordinate table is the display coordinates for the character included in the lyrics and the AOB_ELEMENT and AOB_FRAME corresponding to that character in the AOB.
Is a table in which the period of time is reproduced. Figure 1
00 (b) is a diagram showing an example of a highlight coordinate table. This highlighting coordinate table is provided, and the operation of displaying only the characters corresponding to the currently reproduced AOB_ELEMENT and AOB_FRAME among the lyrics displayed corresponding to the phrase period in different colors Let it be done.

For example, if the lyrics include the phrase “access you from a small window”, the highlight coordinate table shows “small”, “sa”, “na”, and “u”.
The display coordinates of the characters "i", "n", "do", and "u" are associated with the periods in which AOB_ELEMENT and AOB_FRAME corresponding to the characters are reproduced. Then, the reproducing apparatus changes the color of the portion designated by the display coordinates of the character in the highlight coordinate table as the reproduction of the AOB as shown in the first embodiment progresses.

As a result, the playback device can read the AOB from the lyrics.
It is possible to display at a glance where the part being played is, and it is possible to realize the playback like the existing 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 closely synchronize the sound reproduction and the lyrics display as in the current karaoke software. Is possible.

[0324]

The semiconductor memory card according to the present invention is a semiconductor memory card that stores a plurality of audio objects, still picture objects, reproduction path information, first pointer information, second pointer information, and a symbolic counter. The path information indicates the reproduction order of the audio objects, the first pointer information corresponds to the reproduction path information, and the reproduction order of the still image objects during the entire reproduction time of the audio objects according to the reproduction path information. The second pointer information corresponds to a specific audio object, indicates the reproduction order of the still image objects during the entire reproduction time of the audio object, and the symbolic counter corresponds to each still image object. The corresponding still image object It indicates whether or not it is designated by the first pointer information or the second pointer information, and indicates the designated number of how many pieces of the first pointer information and the second pointer information are designated for the designated still image object. Therefore, a plurality of audio objects included in the audio sequence are played back according to the playback order indicated in the playback path information,
When there is a still image object to be commonly displayed as the background image, the still image object is designated in the first pointer information in association with the reproduction path information.
As a result, during the time when multiple audio objects included in the audio sequence are being played,
A common still image object can be displayed.

Since a common still picture can be assigned to a plurality of audio objects, for an audio sequence corresponding to a music album with a low name recognition, a still picture object or the like is reproduced during a period in which the plurality of audio objects are being reproduced. By displaying in common, the labor and cost required for image production can be saved.

On the other hand, for an audio sequence corresponding to a music album with a high name recognition, a plurality of still images are assigned to each audio object during the reproduction of each audio object, and one audio object is assigned. By displaying a plurality of still image objects, the reproduction of each audio object can be luxuriously rendered. It is possible to increase sales of audio sequences (music albums) by grasping the psychology of artist fans by displaying such still images.

If there is a still image object such as lyrics that is desired to be displayed only during the period when a specific audio object is being reproduced separately from the background image, such a still image object is used as the second pointer information. Can be assigned to a specific audio object. Furthermore, the corresponding still image object is the first
The symbolic counter indicates whether or not it is designated by the pointer information or the second pointer information. This symbolic counter has a number of first pointer information,
Since even the designated number is designated by the second pointer information, when the recording device of the semiconductor memory card deletes the audio object or the audio sequence, the second pointer information about the deleted audio object. Identify the first pointer information for the deleted or deleted audio sequence and
The allocation number for the still image object whose display is designated by the pointer information and the second pointer information is decremented. When the allocation number for any still image object reaches 0, the still image object is regarded as a still image object that is not referred to by any first pointer information or second pointer information, and the still image object is deleted. Can be lost. In this way, by deleting the still image object in association with the deletion of the audio object, the storage efficiency of the semiconductor memory card can be improved.

[Brief description of drawings]

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

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

FIG. 3 shows a flash memory card 31 according to this embodiment.
It is a figure which shows the hierarchical structure of.

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

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

[Figure 6] AOB001.SA1 is divided into five parts according to the cluster size, and each divided part is divided into clusters 003,004,005,00A, 00C
It is the figure which assumed the state 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.

FIG. 8A and FIG. 8B, when storing these two data in the application layer, what directory is configured in the user data area and protect area in the file system layer, and what file is the directory. It is a figure which shows whether it is created under the control of.

[Figure 9] AOBSA1.KEY under the SD_Audio directory
It is a figure which shows the correspondence with AOB file.

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

FIG. 11A is a diagram showing, in a tabular form, parameters described in ISO / IEC13818-7. (B) It is a figure which shows the parameter which should be used when encoding by a MPEG-Layer3 (MP3) system in a table format. (C) It is a figure which shows the parameter which should be used when encoding by a Windows (trademark) Media Audio (WMA) system in a table format.

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

[Fig. 13] AOB_FR of three AOB_FRAMEs
It is a figure which shows how the byte length of the audio data in AME is set.

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

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

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

FIG. 17: Playlist manager and T in the first embodiment
It is the figure which detailed the structure of rackManager in steps.

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

19 is a diagram showing a mutual relationship between the TKI shown in FIG. 17 and the AOB file and AOB shown in FIG.

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.

FIG. 23 is a diagram showing a detailed configuration of (a) and (b) BIT. It is a figure which shows the data format of (c) TIME_LENGTH field.

[Fig. 24] Fig. 24 is a diagram illustrating clusters 007 to 00E in which AOBs composed of AOB_ELEMENT # 1 to # 4 are stored.

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

26A and 26B are AOB, AOB_ELEMENT, and AO corresponding to the designated time when an arbitrary playback start time is designated.
It is a figure which shows how to identify B_FRAME.

FIG. 27 is a diagram assuming a case where (a) and (b) tracks are deleted.

FIG. 28A shows a track after the track is deleted a plurality of times.
It is a figure which shows TrackManager. (B) There is a TKI of "Unused", and there is a new T here.
It is a figure which shows how the writing is performed, when writing a KI and AOB file.

29 (a) and 29 (b) are diagrams showing how TKIs are set when two tracks are integrated.

FIG. 30 is a diagram showing (a) Type 1 AOB. (B) It is a figure which shows AOB of Type2.

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

[FIG. 32] (a) Type 1 AOB at the end of the preceding track
FIG. 3 is a diagram showing an arrangement pattern in which the AOB of Type 1 is arranged at the beginning of the subsequent track. (B) A Type 1 AOB is placed at the end of the preceding track,
FIG. 7 is a diagram showing an arrangement pattern in which a Type 2 AOB is arranged at the beginning of a subsequent track. (C) AO in the order of Type1 and Type2 at the end of the preceding track
FIG. 9 is a diagram showing an arrangement pattern in which B is arranged and a Type 1 AOB is arranged at the beginning of the subsequent track. (D) AO at the end of the preceding track in the order of Type1 and Type2
B is arranged and Type2 and Type1 are added at the beginning of the following tracks.
It is a figure which shows the arrangement pattern in which the AOB of FIG. (E) Type2, Type2 AOB at the end of the preceding track
FIG. 3 is a diagram showing an arrangement pattern in which the AOB of Type 1 is arranged at the beginning of the subsequent track.

33 (a) and (b) are diagrams assuming a case where one track is divided into two tracks.

FIG. 34 (a) and (b) before and after division, AOB003.SA1
FIG. 3 is a diagram showing how an SD_Audio directory entry for an SD_Audio directory to which is belongs is described.

[Fig. 35] Fig. 35 (a) is a diagram assuming a case where an AOB is divided in the middle part of AOB_ELEMENT # 2. (B) AOB is divided in the middle of AOB_ELEMENT # 2, and AO
It is a figure showing the state where two AOBs, B # 1 and AOB # 2, were obtained.

FIG. 36 is a diagram showing how BIT is set when the AOB is divided as shown in FIG. 35.

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

[Fig. 38] Fig. 38 is a diagram specifically showing how TKTMSRT changes before and after division.

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

[Fig. 40] Fig. 40 is a diagram illustrating a mutual relationship between Default_Playlist information, a TKI, and an AOB file.

[Fig. 41] Fig. 41 is a diagram illustrating 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 in FIG.
It is a figure which shows the correspondence with I.

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

44 (a) and (b) DefaultPlaylis shown in FIG. 40.
Deta when deleting DPL_TK_SRP # 2 and TKI # 2 of t
It is a figure which shows how ultPlaylist, TrackManager, and an AOB file are updated.

[Fig. 45] (a) and (b) TKI of "Unused" and DPL_TK_SR
FIG. 14 is a diagram showing how P and P exist and write a new TKI, DPL_TK_SRP, here.

46 (a) and 46 (b) are diagrams assuming a case where tracks are integrated.

47A and 47B are diagrams supposing a case where tracks are divided.

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

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

FIG. 50 is a diagram showing an example of the display contents of the liquid crystal display when the tracks (a) to (e) are selected.

FIG. 51 is a diagram showing an operation example of the jog dials (a) to (c).

[Fig. 52] Fig. 52 is a diagram illustrating an internal configuration of a playback device.

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

54 (a) and 54 (b) are diagrams showing how a cyclic area is secured using a ring pointer.

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

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 in which the elapsed playback 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 at the time of forward search reproduction processing.

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

FIG. 62 is a diagram showing a specific example of the case where the time search function is performed in (a) and (b).

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

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

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

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

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

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

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

70 (a) and 70 (b) are diagrams showing the internal structures of a user data area and a protect area in the file system layer.

71 is a diagram showing the internal structure of (a) POBXXX.JPG. FIG. (B) It is a figure which shows the internal structure of the POB file containing the encrypted still image data. (C) It is a figure which shows an example of the POB file which stored the file path instead of the encrypted substance part.

[Fig. 72] PlayListManager and Tra in the second embodiment
It is a figure which shows the detailed structure of ckManager.

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

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

[Fig. 75] Fig. 75 is a diagram illustrating a setting example of TKI_POB_SRP for TKI # 1 to TKI # 3 included in TrackManager.

[Fig. 76] Fig. 76 is a diagram illustrating 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 which shows POB_ATR.

[Fig. 78] 20 DPLIs included in Default_Playlist information
It is a figure which shows the example of a setting of _POB_SRP.

[Fig. 79] DPLI_POB_S included in Default_Playlist information.
6 is a timing chart showing how these are combined when the POB designated by RP is the background image and the POB designated by TKI_POB_SRP included in TrackManager is the foreground image.

[Fig. 80] Fig. 80 is a diagram illustrating how a foreground image and a background image are combined after 6 minutes have elapsed from the start of playback of Default_Playlist information.

[Fig. 81] Fig. 81 is a diagram illustrating how a foreground image and a background image are combined after 16 minutes have elapsed from the start of playback of Default_Playlist information.

FIG. 82 PLI_POB_SRP and PLI_POB included in PLGI
It is a figure which shows _ATR.

[Fig. 83] 20 PLI_POB_SRPs included in PlayList information
It is a figure which shows the example of a setting of.

[Fig. 84] A TKI included in TrackManager with a POB specified by PLI_POB_SRP included in Playlist information as a background image.
9 is a timing chart showing how these are combined when the POB designated by _POB_SRP is the foreground picture.

[FIG. 85] After 6 minutes have passed from the start of the reproduction of the Playlist information,
It is a figure which shows 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 after 16 minutes have elapsed from the start of playback of Default_Playlist information.

[Fig. 87] Plural DPLI_Ps in Default_Playlist information
This is an example of reducing the number of POB files by making DPLI_POB_SRP of OB_SRP specify a common POB file.

[Fig. 88] DPLI_POB_S included in Default_Playlist information.
6 is a timing chart showing how these are combined when the POB designated by RP is the background image and the POB designated by TKI_POB_SRP included in TrackManager is the foreground image.

FIG. 89 is a diagram showing an internal structure of a POBMG.

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

[Fig. 91] Fig. 91 is a diagram showing an external appearance of only the reproducing device main body according to the second embodiment.

[Fig. 92] Fig. 92 is a diagram showing the internal structure of the playback device according to the second embodiment.

FIG. 93 (a) is a diagram showing how still images stored in a plurality of VRAMs 61 are superimposed. (B) It is a figure which shows how the still image stored in several VRAM61 is piled up.

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.

97 (a) to (c) What happens when the foreground image specified by TKI_POB_SRP and the background image specified by DPLGI are combined by the processing procedure shown in the flowcharts of FIGS. 94 and 95. 6 is a diagram showing whether a composite image is displayed on the liquid crystal display 5. FIG.

98A to FIG. 98C show how the foreground image specified by TKI_POB_SRP and the background image specified by PLI_POB_SRP are combined by the processing procedure shown in the flowcharts of FIGS. 94 and 96. Liquid crystal display 5
It is a figure which shows what is displayed on.

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

100A is a diagram showing an example of a phrase period table. FIG. (B) It is a figure which shows an example of a highlight coordinate table.

[Explanation of symbols]

1 card connector 2 User interface section 3 RAM 4 ROM 5 LCD display 6 LCD driver 7 De Scrambler 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 Scrambler 27 Modem equipment 28 CPU 29 keyboard 30 Display 31 flash memory card 32 Protect switch 61 VRAM

─────────────────────────────────────────────────── ─── Continuation of the front page (51) Int.Cl. ⁷ Identification code FI theme code (reference) G10L 9/00 N 9/18 M (72) Inventor Tomokazu Ishikawa 1006 Kadoma, Kadoma City, Osaka Matsushita Electric Industrial (72) Inventor Shinji Inoue 1006 Kadoma, Kadoma-shi, Osaka Prefecture Matsushita Electric Industrial Co., Ltd. (72) Inventor Hideki Matsushima 1006, Kadoma, Kadoma-shi, Osaka Matsushita Electric Industrial Co., Ltd. (72) Inventor Masayuki Kozuka 1006 Kadoma, Kadoma City, Osaka Prefecture Matsushita Electric Industrial Co., Ltd. F term (reference) 5B017 AA07 BB10 CA14 CA15 5B035 AA00 BB09 BC05 CA11 5C052 AA17 AB03 CC01 DD04 DD06 EE08 GA03 GA08 GA09 GB01 GB07 GE45 DA20DB0 5D

Claims (4)

[Claims] 1. A plurality of audio objects, still image objects, reproduction path information, first pointer information, and second
A semiconductor memory card storing pointer information and a symbolic counter, wherein reproduction path information indicates a reproduction order of audio objects, and first pointer information corresponds to the reproduction path information. The second pointer information corresponds to a specific audio object, and indicates the reproduction order of the still image object during the entire reproduction time of the audio object. The reproduction order is indicated, and the symbolic counter is 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. For drawing objects, how many first points Data, the semiconductor memory card indicating the designated number designated by the second pointer information. 2. The editing device for a semiconductor memory card according to claim 1, wherein the input accepting unit accepts a deletion request of a audio object recorded in the semiconductor memory card from a user, and the deletion request is issued. Audio object deleting means for deleting the deleted audio object from the semiconductor memory card, and reproduction path information editing for updating the reproduction order information defining the reproduction order of the audio object to the reproduction order excluding the audio object requested to be deleted Means, second pointer information editing means for deleting the second pointer information associated with the audio object requested to be deleted, and decrementing the symbolic counter corresponding to the still picture object specified by the second pointer information. Shin When the symbolic counter becomes 0 as a result of decrementing the symbolic counter of a specific still image object by the lick counter editing means and the symbolic counter editing means, the still image object is deleted from the semiconductor memory card. An editing apparatus comprising: 3. A recording medium for recording a program for causing a computer to edit the semiconductor memory card according to claim 1, wherein a deletion request for an audio object recorded in the semiconductor memory card is received from a user. The audio object requested to be deleted is excluded from the input acceptance step, the audio object deletion step of deleting the requested audio object from the semiconductor memory card, and the playback path information that defines the playback order of audio objects. A reproduction path information editing step of updating to the reproduction order, a second pointer information editing step of deleting the second pointer information associated with the deletion-requested audio object, and a still image specified by the second pointer information. object When the symbolic counter becomes 0 as a result of decrementing the symbolic counter of the specific still image object by the symbolic counter editing step of decrementing the symbolic counter corresponding to the A recording medium recording a program including a still image object deleting step to be deleted from a memory card. 4. The method of editing a semiconductor memory card according to claim 1, wherein an input receiving step of receiving a deletion request of a user from an audio object recorded on the semiconductor memory card, and a deletion request are made. An audio object deleting step of deleting the audio object from the semiconductor memory card, and a reproducing path information editing step of updating the reproducing path information defining the reproducing order of the audio object to the reproducing order excluding the audio object requested to be deleted. And a second pointer information editing step of deleting the second pointer information associated with the deletion-requested audio object, and decrementing the symbolic counter corresponding to the still image object specified by the second pointer information. When the symbolic counter becomes 0 as a result of decrementing the symbolic counter of the specific still image object by the symbolic counter editing step and the symbolic counter editing step, the still image object to delete the still image object from the semiconductor memory card. A method of editing a semiconductor memory card, including: a deleting step.