JP2001142495A - Method and device for editing, and non-volatile memory - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make a musical piece under reproduction on the like retrievable after setting y enabling a user himself or herself to arbitrarily designate digest information. SOLUTION: A CPU 70 is connected to a DSP of a recorder having a memory card as a medium. When a reproducing button 84 is operated as prescribed in the reproducing state, index management information write processing is performed in parallel with the reproducing operation. In this processing, information which indicates the start position of an index part prescribed by timing of uer's depression of the reproducing button 85 and information indicating the duration of depression of the reproducing button 85 are generated in the CPU 70 and are written in a prescribed area of the memory card through the DSP as information indicating a reproducing section. Thus a user's favorite characteristic part or what is called a digest part is specified in a musical piece or the like in the middle of reproducing.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an editing apparatus, an editing method, and a nonvolatile memory for designating a digest portion relating to a program / album by a user and recording the position and period of the specified digest portion in a management area.

[0002]

2. Description of the Related Art EEPROM (Electrically Erasable P)
An electrically rewritable nonvolatile memory called a programmable memory (rogrammable ROM) has a large occupation area per bit because one bit is composed of two transistors, and there is a limit in increasing the degree of integration. In order to solve this problem, a flash memory capable of realizing one bit with one transistor by an all-bit batch erasing method has been developed. A flash memory is expected as a substitute for a recording medium such as a magnetic disk and an optical disk.

[0003] A memory card in which a flash memory is configured to be detachable from a device is also known. If this memory card is used, digital audio recording / recording using a memory card in place of a conventional disk-shaped medium such as a CD (compact disk), MD (mini-disc), or the like is possible.
A playback device can be realized.

In a conventional digital audio recording / reproducing apparatus, for example, a CD (compact disk) player, C
Introscan, music scan, and other functions that automatically play back the beginning of each song (for example, 10 seconds) one after another so that the contents recorded in D can be grasped immediately. There is. However,
This function only plays the first part,
In some cases, the user could not grasp the contents or characteristics of the music.

Conventionally, there has been proposed a reproducing apparatus for designating and reproducing a digest portion of a music piece on a video CD.
Since a video CD cannot be recorded on a read-only disc, the digest part determined in advance by the creator (content holder or record company) is recorded, and it is not possible for the user to set an arbitrary location of his choice. It was possible.

[0006] As another method, it is conceivable to record a digest portion of a song for each disc specified by a user in a non-volatile memory built in the main body of the disc reproducing apparatus. In this case, the digest portion of the song is tabulated in association with the disc identifier, stored in the non-volatile memory, and referred to the disc identifier mounted in the playback device and the table identifier with reference to the table. When the same identifier is determined, the corresponding digest portion can be reproduced.

[0007]

However, since the digest information is not recorded on the disc, it must be referred to a table in the main unit of the reproducing apparatus, and the processing by the microcomputer is difficult. It took time. Further, conventionally, digest information for each song has been recorded, but digest information for each album has not been recorded.

Accordingly, it is an object of the present invention to provide an editing apparatus, an editing method, and a nonvolatile memory in which digest information of a music piece designated by a user is recorded in the nonvolatile memory.

It is another object of the present invention to provide an editing apparatus, an editing method, and a nonvolatile memory capable of recording digest portions of a plurality of albums recorded in one nonvolatile memory.

[0010]

According to a first aspect of the present invention, there is provided an editing apparatus for editing a digest portion of a program recorded in a nonvolatile memory. Input means for the user to input a position, generating means for generating a start address and digest period information of the digest part according to the start position and end position, and a start address and digest period information of the digest part to the nonvolatile memory An editing apparatus comprising a recording unit for performing recording.

According to a seventh aspect of the present invention, in an editing method for editing a digest portion of a program recorded in a nonvolatile memory, an input step for a user to input a start position and an end position of the digest portion, and a start position and an end position And a recording step of recording the digest section start address and the digest period information in the non-volatile memory.

According to an eighth aspect of the present invention, in a nonvolatile memory storing a program composed of a plurality of blocks, one of the plurality of blocks is used as an attribute information recording area in which attribute information is recorded. Each of the blocks is a non-volatile memory that includes a header section and a main data section, and records the start address of the digest section of the program specified by the user and the digest period information in the attribute information recording area.

According to the present invention, since the start address and the period of the digest section are set based on the user's input, the user can specify the digest section. In addition, since the digest section information is recorded in the non-volatile memory, the process of reproducing the digest section can be simplified. Further, digest information of each of a plurality of albums recorded in one nonvolatile memory can be recorded.

[0014]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below. FIG. 1 shows the overall configuration of a digital audio recorder / player using a memory card according to an embodiment of the present invention. This embodiment is a digital audio signal recording and reproducing apparatus using a removable memory card as a recording medium. More specifically, the recorder / player comprises an amplifier device,
An audio system is configured together with a speaker, a CD player, an MD recorder, a tuner, and the like. The present invention can be applied to other audio recorders. That is, the present invention can be applied to a portable recording / reproducing apparatus. The present invention is also applicable to a set-top box for recording digital audio signals distributed via data communication using satellites, digital broadcasting, the Internet, and the like. Further, the present invention can be applied to recording / reproduction of moving image data, still image data, and the like in addition to digital audio signals. In one embodiment, additional information such as images and characters other than digital audio signals can be recorded / reproduced.

The recording / reproducing apparatus includes an audio encoder / decoder IC 10 composed of one chip IC,
Security IC 20, DSP (Digital Signal Proces)
sor) 30. Further, a memory card 40 which is detachable from the recording / reproducing apparatus main body is provided. Memory card 4
0 is a flash memory (non-volatile memory), a memory control block, and a DES (Data Encryption Standar).
The security block including the encryption circuit of d) is integrated on one chip. In this embodiment, the DSP 30 is used, but a microcomputer may be used.

Audio encoder / decoder IC 10
Is an audio interface 11 and an encoder /
It has a decoder block 12. The encoder / decoder block 12 encodes the digital audio signal with high efficiency for writing to the memory card 40 and decodes the data read from the memory card 40. ATRAC3, which is an improved version of ATRAC (Adaptive Transform Acoustic Coding) used in minidiscs, is used as a highly efficient encoding method.

In ATRAC3 described above, audio data with 16-bit quantization bits sampled at a sampling frequency of 44.1 kHz are subjected to high-efficiency encoding processing. The smallest data unit when processing audio data in ATRAC3 is the sound unit SU. 1SU
Is obtained by compressing 1024 samples (1024 × 16 bits × 2 channels) into several hundred bytes, which is about 23 ms in time. The audio data is compressed to about 1/10 by the above-described high-efficiency encoding process. ATRAC3 as well as ATRAC1 applied on the minidisc
Compression / compression of the processed audio signal
Degradation of the sound quality due to the decompression process is small.

A line input selector 13 selectively selects an MD reproduction output, a tuner output, and a tape reproduction output from an A / D converter.
It is supplied to the converter 14. The A / D converter 14 converts the input line input signal into a sampling frequency of 44.1 kHz.
z, quantization bits = convert to 16-bit digital audio signals. The digital input selector 16 selects M
Digital outputs of D, CD, and CS (satellite digital broadcasting) are selectively supplied to a digital input receiver 17.
The above digital input is transmitted, for example, via an optical cable. The output of the digital input receiver 17 is supplied to the sampling rate converter 15, and the digital input is converted into a digital audio signal having a sampling frequency of 44.1 kHz and quantization bits of 16 bits.

Audio encoder / decoder IC 10
The encoded data from the encoder / decoder block 12 is supplied to the DES encryption circuit 22 via the interface 21 of the security IC 20. The DES encryption circuit 22 has a FIFO 23. The DES encryption circuit 22 is provided to protect the copyright of the content. The memory card 40 also incorporates a DES encryption circuit. The DES encryption circuit 22 of the recording / reproducing device has a plurality of master keys and a unique storage key for each device. Further, the DES encryption circuit 22 has a random number generation circuit, and can share the authentication and session key with a memory card incorporating the DES encryption circuit. Still further, the DES encryption circuit 22 can be re-keyed with the storage key through the DES encryption circuit.

The encrypted audio data from the DES encryption circuit 22 is transmitted to a DSP (Digital Signal Processor).
r) 30. The DSP 30 communicates with a memory card 40 mounted on a detachable mechanism (not shown) via a memory interface, and writes encrypted data to a flash memory. Serial communication is performed between the DSP 30 and the memory card 40. Also, in order to secure the memory capacity necessary for controlling the memory card,
An external SRAM (StaticRandom Ac
cess Memory) 31 is connected.

Further, a bus interface 32 is connected to the DSP 30, and data from an external controller (not shown) is supplied to the DSP 30 via a bus 33. An external controller controls the operation of the entire audio system, and supplies data such as a recording command and a reproduction command generated in response to a user operation from the operation unit to the DSP 30 via the bus interface 32. Further, data of additional information such as image information and character information is also supplied to the DSP 30 via the bus interface 32. The bus 33
This is a bidirectional communication path, and additional information data, control signals, and the like read from the memory card 40 are taken into an external controller via the DSP 30, the bus interface 32, and the bus 33. The external controller is specifically included in another device included in the audio system, for example, an amplifier device. Further, an external controller controls display of additional information, display of the operation state of the recorder, and the like. The display unit is shared by the entire audio system. Here, since the data transmitted and received via the bus 33 is not a literary work, it is not encrypted.

The encrypted audio data read from the memory card 40 by the DSP 30 is decrypted by the security IC 20 and is subjected to ATRAC3 decryption processing by the audio encoder / decoder IC 10. The output of the audio encoder / decoder 10 is supplied to a D / A converter 18 and converted into an analog audio signal. Then, the analog audio signal is taken out to the line output terminal 19.

The line output is transmitted to an amplifier (not shown) and reproduced by a speaker or headphones.
A muting signal is supplied to the D / A converter 18 from an external controller. When the muting signal indicates that muting is on, the line output terminal 19
Audio output from is prohibited.

FIG. 2 shows the internal configuration of the DSP 30. D
The SP 30 includes a core 34, a flash memory 35,
It comprises a RAM 36, a bus interface 37, a memory card interface 38, and a bus and a bridge between the buses. The DSP 30 has the same function as a microcomputer, and the core 34 corresponds to a CPU. A program for processing of the DSP 30 is stored in the flash memory 35. SRAM 36 and external SRAM
31 are used as RAM.

The DSP 30 includes a bus interface 32,
In response to an operation signal such as a recording command received via the communication device 37, predetermined encrypted audio data and predetermined additional information data are written to the memory card 40, and these data are written from the memory card 40. Controls the reading process. That is, the DSP 30 is located between the application software of the entire audio system for recording / reproducing audio data and additional information and the memory card 40, and the DSP for access to the memory card 40 and the software such as a file system are used.
30 operates.

The file management on the memory card 40 in the DSP 30 uses the FAT system used in the existing personal computer. In addition to this file system, in one embodiment, a management file having a data configuration as described below is used. The management file manages a data file recorded on the memory card 40. The management file as the first file management information manages a file of audio data. The FAT as the second file management information manages the entire file on the flash memory of the memory card 40 including the audio data file and the management file. The management file is recorded on the memory card 40. The FAT is pre-written on the flash memory at the time of shipment together with the root directory and the like. F
Details of the AT will be described later.

In one embodiment, audio data compressed by ATRAC3 is encrypted to protect copyright. On the other hand, the management file is not encrypted because it does not need copyright protection. In addition, some memory cards have an encryption function and some do not. As in the embodiment, a memory card that supports a recorder that records audio data as a literary work is only a memory card having an encryption function. A voice recorded by an individual or a recorded image is recorded on the memory card having no encryption function.

FIG. 3 shows the configuration of the memory card 40.
The memory card 40 has a control block 41 and a flash memory 42 configured as a one-chip IC. The bidirectional serial interface between the player / recorder DSP 30 and the memory card 40
Consists of a book line. The four main lines are a clock line SCK for transmitting a clock during data transmission, a status line SBS for transmitting status, a data line DIO for transmitting data, and an interrupt line INT. In addition, two GND lines and two VCC lines are provided as power supply lines. Two lines Reserve
Is an undefined line.

The clock line SCK is a line for transmitting a clock synchronized with data. Status line SBS
Is a line for transmitting a signal indicating the status of the memory card 40. The data line DIO is a line for inputting / outputting a command and encrypted audio data. The interrupt line INT is a line for transmitting an interrupt signal requesting an interrupt from the memory card 40 to the DSP 30 of the player / recorder. When the memory card 40 is inserted, an interrupt signal is generated. However, in this embodiment, since the interrupt signal is transmitted via the data line DIO, the interrupt line INT is grounded.

The serial / parallel conversion / parallel / serial conversion / interface block (hereinafter abbreviated as S / P / P / S / IF block) 43 of the control block 41 is a recorder connected via a plurality of lines as described above. Is an interface between the DSP 30 and the control block 41. S / P / P / S / IF block 43
Converts the serial data received from the player / recorder DSP 30 into parallel data, takes it into the control block 41, converts the parallel data from the control block 41 into serial data, and sends it to the player / recorder DSP 30. Also, S / P / P /
When receiving the command and data transmitted via the data line DIO, the S / IF block 43 separates the command and data for normal access to the flash memory 42 from the command and data necessary for encryption. I do.

In the format transmitted via the data line DIO, a command is transmitted first, and then data is transmitted. S / P / P / S / IF block 43
Detects the command code and determines whether it is a command and data necessary for normal access or a command and data required for encryption. According to the result of this determination, the command necessary for normal access is stored in the command register 44.
And the data is stored in the page buffer 45 and the write register 46. An error correction encoding circuit 47 is provided in association with the write register 46. For the data temporarily stored in the page buffer 45, the error correction coding circuit 47 generates a redundant code of the error correction code.

Command register 44, page buffer 4
5, write register 46 and error correction encoding circuit 4
7 is supplied to a flash memory interface and a sequencer (hereinafter abbreviated as a memory I / F sequencer) 51. Memory IF / Sequencer 51
Is a control block 41 and a flash memory 42
Interface to control the exchange of data between the two. Data is written to the flash memory 42 via the memory IF / sequencer 51.

AT written to flash memory 42
Audio data compressed by RAC3 (hereinafter A
TRAC3 data) is protected by the security IC 20 of the player / recorder and the security block 52 of the memory card 40 for copyright protection.
It is encrypted. Security block 52
Is a buffer memory 53 and a DES encryption circuit 54
And a non-volatile memory 55.

The security block 52 of the memory card 40 has a plurality of authentication keys and a unique storage key for each memory card. The non-volatile memory 55 stores a key required for encryption, and has a structure that cannot be analyzed even by chip analysis. In this embodiment, for example, a storage key is stored in the nonvolatile memory 55.
Furthermore, it has a random number generation circuit, can perform authentication with a compatible player / recorder, and can share a session key. D
Through the ES encryption circuit 54, the content key is re-keyed with the storage key.

For example, mutual authentication is performed when the memory card 40 is mounted on the player / recorder. The authentication is performed by the security IC 20 of the player / recorder and the security block 52 of the memory card 40.
When the player / recorder authenticates that the attached memory card 40 is a compatible memory card, and authenticates that the memory card 40 is a compatible player / recorder of the opponent player / recorder, the player / recorder recognizes each other. It means that the authentication process was performed normally. When the authentication is performed, the player / recorder and the memory card 40 respectively generate a session key and share the session key. A session key is generated for each authentication.

When writing content to the memory card 40, the player / recorder encrypts the content key with the session key and passes it to the memory card 40.
In the memory card 40, the content key is decrypted with the session key, encrypted with the storage key, and passed to the player / recorder. The storage key is a key unique to each of the memory cards 40. When the player / recorder receives the encrypted content key, the storage key performs a format process, and the encrypted content key and the encrypted content key are processed. The content is written to the memory card 40.

The write processing for the memory card 40 has been described above. The read processing for the memory card 40 will be described below. Flash memory 42
The data read from the memory IF / sequencer 51
Are supplied to the page buffer 45, the read register 48, and the error correction circuit 49 via the The data stored in the page buffer 45 is subjected to error correction by an error correction circuit 49. Page buffer 4 with error correction
5 and the output of the read register 48 are S / P · P
/ S · IF block 43 and the DSP / player 3 of the player / recorder through the serial interface described above.
0 is supplied.

At the time of reading, the content key encrypted with the storage key and the content encrypted with the block key are read from the flash memory 42.
The security block 52 decrypts the content key with the storage key. The decrypted content key is re-encrypted with the session key and transmitted to the player / recorder. The player / recorder decrypts the content key with the received session key. The player / recorder generates a block key using the decrypted content key. With this block key, the encrypted AT
The RAC3 data is sequentially decoded.

The ConfigROM 50 is a memory that stores version information of the memory card 40, various types of attribute information, and the like. In addition, the memory card 40 has a switch 6 for preventing erroneous erasure that can be operated by the user as needed.
0 is provided. When the switch 60 is in the connection state where erasure is prohibited, erasure of the flash memory 42 is prohibited even if a command instructing erasure of the flash memory 42 is sent from the recorder side. Further, OSC Cont. 61 is an oscillator that generates a clock that is a timing reference for processing of the memory card 40.

FIG. 4 shows a file system processing hierarchy of a computer system using a memory card as a storage medium. As the file system processing layer, the application processing layer is at the top, and a file management processing layer, a logical address management layer, a physical address management layer, and a flash memory access are sequentially stacked thereunder. In the above-described hierarchical structure, the file management processing layer is a FAT system. The physical address is assigned to each block of the flash memory, and the correspondence between the block and the physical address is unchanged. The logical address is an address logically handled by the file management processing layer.

FIG. 5 shows an example of a physical configuration of data in the flash memory 42 in the memory card 40. In the flash memory 42, a data unit called a segment is divided into a predetermined number of blocks (fixed length), and one block is divided into a predetermined number of pages (fixed length). In the flash memory 42, erasing is performed collectively in block units, and writing and reading are performed collectively in page units. Each block and each page have the same size, and one block is composed of page 0 to page m. One block has a capacity of, for example, 8 KB (K bytes) or 16 KB, and one page has a capacity of 512 B. In the entire flash memory 42, when 1 block = 8 KB, 4 MB (512 blocks), 8
MB (1024 blocks), 1 block = 16K
In case of B, 16MB (1024 blocks), 32MB
(2048 blocks), 64 MB (4096 blocks)
Of capacity.

One page has a data portion of 512 bytes and one
It consists of a 6-byte redundant part. The first three bytes of the redundant portion are an overwrite portion that is rewritten in accordance with updating of data. In each of the three bytes, a block status, a page status, and an update status are recorded in order from the top. The remaining 13 bytes of the redundant part are
In principle, it is fixed according to the contents of the data section. The 13 bytes include a management flag (1 byte), a logical address (2 bytes), a format reserve area (5 bytes), shared information ECC (2 bytes), and data ECC (3 bytes). The shared information ECC is redundant data for error correction for a management flag, a logical address, and a format reserve. The data ECC is redundant data for error correction for 512-byte data.

As the management flag, a system flag (its value is 1: user block, 0: boot block), a conversion table flag (1: invalid, 0: table block),
Each flag of copy prohibition designation (1: OK, 0: NG) and access permission (1: free, 0: read protection) is recorded.

The first two blocks 0 and 1
Is a boot block. Block 1 is for backup in which the same data as block 0 is written. The boot block is the first block of valid blocks in the card, and is the first block to be accessed when a memory card is loaded into a device. The remaining blocks are user blocks. A header, a system entry, and boot & attribute information are stored in the first page 0 of the boot block. The page 1 stores the use prohibition block data. Page 2 shows CIS (Card Information Structur)
e) / IDI (Identify Drive Information) is stored.

The boot block header records a boot block ID and the number of valid entries in the boot block. The system entry includes the start position of the prohibited block data, its data size, data type, CIS /
The IDI data start position, its data size, and data type are recorded. The boot & attribute information includes the type of memory card (read only, read / write, hybrid of both types, etc.), block size, number of blocks, total number of blocks, whether security is supported, data related to card manufacturing (Manufacturing date, etc.) are recorded.

In a flash memory, the rewriting of data causes deterioration of the insulating film, thereby limiting the number of rewritings. Therefore, it is necessary to prevent repeated accesses from being intensively performed to a certain storage area (block). Therefore, when rewriting data at a certain logical address stored at a certain physical address, the flash memory file system does not rewrite updated data to the same block, but to an unused block. And write the updated data. As a result, the correspondence between the logical address and the physical address before the data update changes after the update. By performing the swap processing, it is possible to prevent the same block from being repeatedly and intensively accessed, and it is possible to extend the life of the flash memory.

Since the logical address accompanies the data once written to the block, even if the block in which the data before update and the data after update are written moves, the F
The same address can be seen from the AT, and subsequent access can be properly performed. Since the correspondence between the logical address and the physical address is changed by the swap processing, a logical-physical address conversion table indicating the correspondence between the two is required. By referring to this table, the physical address corresponding to the logical address specified by the FAT is specified, and the block indicated by the specified physical address can be accessed.

The logical-physical address conversion table is DS
It is stored on the SRAM by P30. Young, RAM
When the capacity is small, it can be stored in a flash memory. This table roughly includes a logical address (2 bytes) arranged in ascending order and a physical address (2 bytes).
Is a table corresponding to each. Since the maximum capacity of the flash memory is 128 MB (8192 blocks), the address of 8192 can be represented by 2 bytes. Further, the logical-physical address conversion table is managed for each segment, and its size increases according to the capacity of the flash memory. For example, if the capacity of the flash memory is 8 MB (2 segments), 2
For each of the two segments, two pages are used for the logical-physical address conversion table. When the logical-physical address conversion table is stored in the flash memory, whether or not the block is a block storing the logical-physical address conversion table is determined by a predetermined bit of the management flag in the redundant portion of each page described above. Is indicated.

The above-mentioned memory card can be used by a FAT system of a personal computer, similarly to a disk-shaped recording medium. Although not shown in FIG. 5, an IPL area, a FAT area, and a root directory area are provided on the flash memory. In the IPL area, an address at which a program to be first loaded into the memory of the recorder is written, and various information of the memory are written. Block (cluster) in FAT area
The related matters are written. In the FAT, values indicating an unused block, a next block number, a bad block, and a last block are defined. Further, directory entries (file attributes, update date, start cluster, file size, etc.) are written in the root directory area.

FIG. 6 illustrates a management method based on FAT management. FIG. 6 shows a schematic diagram in the memory, from the top, a partition table, a free area, a boot sector, a FAT area, a FAT copy area, and a Root Di.
a directory area, a subdirectory area,
Data areas are stacked. The memory map is
It is a memory map after converting a logical address to a physical address based on a logical-physical address conversion table.

The above-described boot sector, FAT area, FA
T copy area, Root Directory area,
The Sub Directory area and the data area are collectively referred to as a FAT partition area.

In the above partition table, F
The start and end addresses of the AT partition area are recorded. The FAT used for a normal floppy (registered trademark) disk does not have a partition table. Since the first track does not contain anything other than the partition table, an empty area is created.

Next, a 12-bit FA is stored in the boot sector.
The size of the FAT structure, the cluster size, and the size of each area are recorded depending on whether it is T or 16-bit FAT. The FAT manages the position of a file recorded in the data area. The FAT copy area is an area for backup of the FAT. In the root directory portion, a file name, a leading cluster address, and various attributes are recorded.
Use bytes.

The subdirectory portion exists as a file having the attribute of a file called a directory.
In the embodiment of PBLIST. MSF, CAT. MS
A, DOG. There are four files: MSA, MAN. MSA. In this subdirectory part, a file name and a recording position on the FAT are managed. That is, in FIG. The slot on which the file name “MSA” is recorded manages the FAT address “5”. The slot in which the file name MSA is recorded has an F of "10".
An address on the AT is managed.

In the present embodiment, audio data compressed by ATRAC 3 is recorded in the actual data area from cluster 2 onward. Further, M
The FAT address “110” is managed in the slot in which the file name “AN.MSA” is recorded.

In the embodiment of the present invention, cluster 5,
CAT. A with file name MSA
Audio data compressed by the TRAC3 is recorded, and DOG. MSA
DOG-1 which is the first part of the file name is AT
Audio data compressed by RAC3 is recorded, and DOG. DOG-2 which is the latter part of the file name of MSA is ATRA
Audio data compressed in C3 is recorded. Further, MAN. M
Audio data compressed by ATRAC3 having a file name of SA is recorded.

This embodiment shows an example in which a single file is divided into two and recorded discretely. The area marked Empty on the data area is a recordable area.

The cluster 200 and subsequent areas are areas for managing file names. M
A file named “DOG.SA” is stored in the cluster 201.
An MSA file is stored in the cluster 202 as MAN.
A file called MSA is recorded. When the file order is rearranged, the rearrangement may be performed after the cluster 200.

When the memory card of this embodiment is inserted for the first time, the start and end addresses of the FAT partition area are recorded with reference to the first partition table. After reproducing the boot sector, the Root Directory, Sub Directory
The reproduction of the gallery part is performed. And Sub Dire
Playback management information PBLIS recorded in the directory
T. Search for the slot where the MSF is recorded, and
LIST. The address of the end of the slot in which the MSF is recorded is referred to.

In the case of this embodiment, PBLIST.
At the end of the slot where the MSF is recorded, “20
Since the address “0” is recorded, the cluster 20
0. The cluster 200 and subsequent areas are areas that manage the file names and the order in which the files are played back. In this embodiment, the file named CAT.MSA is the first song, and the DOG. The file named MSA is the second song, and MAN. The file named MSA is the third song.

Here, after referring to all the clusters 200 and thereafter, the process proceeds to the subdirectory section, and CAT. MSA,
DOG. MSA and MAN. Reference the slot that matches the file name named MSA. In FIG. 6, CAT. An address “5” is recorded at the end of the slot where the file name “MSA” is recorded.
An address “10” is recorded at the end of the slot where the file “OG.MSA” is recorded. M
The end of the slot where the file named SA is recorded is 1
The address 10 is recorded.

CAT. The entry address on the FAT is searched based on the address “5” recorded at the end of the slot in which the file name “MSA” is recorded.
In the entry address 5, a cluster address “6” is entered. When referring to the entry address “6”, a cluster address “7” is entered, and when referring to the entry address “7”, “8” is entered. Is entered, and referring to the entry address “8”, “FF” is entered.
A code indicating the end of "F" is recorded.

Therefore, CAT. The file “MSA” uses the cluster areas of clusters 5, 6, 7, and 8. By referring to clusters 5, 6, 7, and 8 in the data area, CAT. An area in which ATRAC3 data of MSA is actually recorded can be accessed.

Next, discretely recorded DOG. MSA
The method of searching for the file named is shown below. DOG.
At the end of the slot where the file name MSA is recorded, an address “10” is recorded. Here, the entry address on the FAT is searched based on the address “10”. In the entry address 10, a cluster address “11” is entered. When referring to the entry address “11”, a cluster address “12” is entered. When referring to the entry address “12”, “1” is entered.
The cluster address “00” is entered.
Furthermore, referring to the entry address “100”, the cluster address “101” is entered, and referring to the entry address “101”, a code meaning the end of FFF is recorded.

Therefore, DOG. The file MSA uses cluster areas of clusters 10, 11, 12, and 10101, and clusters 10 and 11 of the data area.
11 and 12, DOG. An area in which ATRAC3 data corresponding to the first half part of the MSA file is actually recorded can be accessed. Further, referring to the clusters 100 and 101 in the data area, the DOG. An area in which ATRAC3 data corresponding to the latter part of the MSA file is actually recorded can be accessed.

Further, MAN. The entry address on the FAT is searched based on the address “110” recorded at the end of the slot in which the file name “MSA” is recorded. "111" is entered in the entry address 110.
Is entered, and "11
Referring to the entry address "1", a code meaning the end of "FFF" is recorded.

Therefore, MAN. The file “MSA” uses a cluster area of clusters 110 and 111. By referring to the clusters 110 and 111 of the data area, MAN. An area in which ATRAC3 data of MSA is actually recorded can be accessed.

As described above, data files discretely recorded on the flash memory can be linked and sequentially reproduced.

In this embodiment, the management for managing each track and the parts making up each track for the music file separately from the file management system defined by the format of the memory card 40 described above. I have a file. This management file is
The data is recorded on the flash memory 42 using the user block of the memory card 40. As a result, as described later, even if the FAT on the memory card 40 is broken, the file can be repaired.

This management file is created by the DSP 30. For example, when the power is first turned on, it is determined whether or not the memory card 40 is mounted. When the memory card is mounted, authentication is performed. If the authentication confirms that the card is a valid memory card, the boot block of the flash memory 42 is read into the DSP 30. Then, the logical-physical address conversion table is read. The read data is stored in the SRAM. Even when a memory card is used for the first time by the user, the FAT is stored in the flash memory 42 at the time of shipment.
And the root directory has been written. The management file is created when a recording is made.

That is, a recording command generated by a user's remote control or the like is transmitted from an external controller via the bus and bus interface 32 to the DSP 3.
0 is given. Then, the received audio data is compressed by the encoder / decoder IC 10, and ATRAC3 data from the encoder / decoder IC 10 is encrypted by the security IC 20. DSP30
Saves the encrypted ATRAC3 data on the memory card 40.
In the flash memory 42. After this recording, FA
T and the management file are updated. Each time a file is updated, specifically, recording of audio data is started, and each time recording is completed, a FAT is stored in the SRAMs 31 and 36.
And the management file is rewritten. Then, when removing the memory card 40 or turning off the power,
The final FAT and management file are stored from the SRAMs 31 and 36 to the flash memory 42 of the memory card 40. In this case, recording of the audio data is started, and every time the recording is completed, the F
The AT and the management file may be rewritten. When editing is performed, the contents of the management file are updated.

Further, in the data configuration of this embodiment, additional information is also created and updated in the management file and recorded on the flash memory 42. In another data configuration of the management file, the additional information management file is created separately from the track management file. The additional information is provided from an external controller to the DSP 30 via the bus and the bus interface 32. The additional information received by the DSP 30 is recorded on the flash memory 42 of the memory card 40. The additional information is the security IC 20
It is not encrypted. The additional information is stored in the DSP 3 when the memory card 40 is removed or the power is turned off.
0 is written to the flash memory 42 from the SRAM.

FIG. 7 shows the entire file structure of the memory card 40. The directories include a still image directory, a moving image directory, a voice directory, a control directory, and a music (HIFI) directory. In this embodiment, music is recorded / reproduced, so that a music directory will be described below. Two types of files are placed in the music directory. One of them is the reproduction management file PBLIST. M
SF (hereinafter simply referred to as PBLIST), and the other is an ATRA containing encrypted music data.
C3 data file A3Dnnnn. MSA (hereinafter simply referred to as A3Dnnn). ATRAC3
The maximum number of data files is specified up to 400. That is, up to 400 songs can be recorded. AT
The RAC3 data file is arbitrarily created by the device after being registered in the reproduction management file.

FIG. 8 shows the structure of a reproduction management file.
FIG. 9 shows the structure of an ATRAC3 data file of one FILE (one song). The playback management file is a 16 KB fixed length file. The ATRAC3 data file is composed of a head attribute header followed by actual encrypted music data in song units. 16 attribute headers
It has a KB fixed length and has a configuration similar to the playback management file.

The playback management file shown in FIG. 8 has a header,
It is composed of the name NM1-S of the one-byte code memory card, the name NM2-S of the two-byte code memory card, the reproduction table TRKTBL in the order of music, and the additional information INF-S of the entire memory card. The attribute header at the head of the data file shown in FIG.
1 or 2 byte code song name NM2, track information TRKINF such as track key information, parts information PRTIN
F and additional information INF of the track. The header includes information on the total number of parts, name attributes, size of additional information, and the like.

ATRAC3 music data follows the attribute header. The music data is divided into 16 KB blocks, and a header is added to the head of each block.
The header includes an initial value for decrypting the encryption.
Note that only the music data in the ATRAC3 data file is subjected to the encryption process, and other data such as the reproduction management file and the header are not encrypted.

Referring to FIG. 10, the relationship between the music and the ATRAC3 data file will be described. One track is one
Means a song. One song is composed of one ATRAC3 data file (see FIG. 9). The ATRAC3 data file is audio data compressed by ATRAC3. The data is recorded on the memory card 40 in units called clusters. One cluster is, for example, 16
This is the capacity of KB. Multiple files are not mixed in one cluster. The minimum unit for erasing the flash memory 42 is one block. In the case of the memory card 40 used for recording music data, the block and the cluster are synonyms, and one cluster is defined as one sector.

One song is basically composed of one part, but once edited, one song may be composed of a plurality of parts. Parts means the unit of data recorded within a continuous time from the start of recording to its stop,
Normally, one track is composed of one part. The connection of the parts in the song is indicated by the parts information P in the attribute header of each song.
It is managed by RTINF. That is, the part size is P
Part size PRTSIZE in RTINF 4
Expressed as byte data. The first two bytes of the part size PRTSIZE indicate the total number of clusters of the part,
The subsequent one byte indicates the position of the start sound unit (hereinafter abbreviated as SU) and the position of the end SU in the first and last clusters. By having such a method of describing parts, it is possible to eliminate the movement of a large amount of music data that is normally required when editing music data. If the editing is limited to the block unit, the movement of the music data can be similarly avoided, but the editing unit in the block unit is too large compared to the SU unit.

SU is the minimum unit of a part.
This is the minimum data unit when audio data is compressed by TRAC3. For 1024 samples obtained at a sampling frequency of 44.1 kHz (1024 × 16 bits ×
SU is data of several hundred bytes obtained by compressing audio data of (2 channels) about 1/10. One SU is approximately 23 ms in terms of time. Typically, thousands of SUs
Constitutes one part. One cluster is 42
When composed of SUs, one cluster can represent about one second of sound. The number of parts constituting one track is affected by the size of the additional information. The number of parts is determined by the number excluding the header, the song title, the additional information data, and the like from one block. Therefore, the state where there is no additional information is a condition under which the maximum number (645) of parts can be used.

FIG. 10A shows a file structure in the case where audio data from a CD or the like is recorded continuously for two songs.
The first song (file 1) is composed of, for example, five clusters. Between the songs of the first song and the second song (file 2), two files are not allowed to be mixed in one cluster, so the file 2 is created from the beginning of the next cluster.
Therefore, the end of the part 1 (the end of the first song) corresponding to the file 1 is located in the middle of the cluster, and no data exists in the remaining part of the cluster. The second song (file 2) is similarly composed of one part. In the case of file 1, the part size is 5, the start cluster SU is 0, and the end cluster is 4.

Editing operations include divide, combine,
Four types of operations, erase and move, are defined. The divide is to divide one track into two. When the divide is performed, the total number of tracks increases by one. The divide divides one file into two files on the file system,
To update. Combine is to combine two tracks into one. When combined, the total number of tracks is reduced by one. The combine integrates the two files into one file on the file system, and updates the reproduction management file and the FAT. Erase is to erase a track. The track number after being erased is decreased by one. Move is changing the order of tracks. As for the erase and move processing,
Update the playback management file and FAT.

FIG. 10B shows the result of combining the two songs (file 1 and file 2) shown in FIG. 10A. The combined result is one file,
This file consists of two parts. FIG.
C shows the result of dividing one song (file 1) in the middle of cluster 2. By divide, file 1 consisting of the front sides of clusters 0, 1 and 2;
A file 2 consisting of the back side of cluster 2 and clusters 3 and 4 is generated.

As described above, in this embodiment, since there is a description method regarding parts, in FIG. 10B, which is a result of combining, the start position of part 1, the end position of part 1, the start position of part 2, 2 can be defined in SU units. as a result,
In order to close the joint gap as a result of the combine,
There is no need to move the music data of part 2. In addition, since there is a description method for parts, there is no need to move data so as to fill the head space of file 2 in FIG.

FIG. 11 shows a reproduction management file PBLIST.
FIG. 12A and FIG.
B indicates a header constituting the playback management file PBLIST and other parts. Playback management file P
BLIST has a size of one cluster (one block = 16 KB). The header shown in FIG. 12A is composed of 32 bytes. Parts other than the header shown in FIG. 12B are the name NM1-S (256 bytes), the name NM2-S (512 bytes), and CONTENTSKE for the entire memory card.
Y, MAC, S-YMDhms, table TRKTBL (800 bytes) for managing reproduction order, additional information INF-S (14720 bytes) for the entire memory card
Finally, part of the information in the header is recorded again. The head of each of these different types of data groups is defined to be at a predetermined position in the reproduction management file.

The reproduction management file is shown in FIG.
The first 32 bytes represented by (x0000) and (0x0010) are the header. Note that a unit divided in 16-byte units from the beginning in the file is called a slot. In the header arranged in the first and second slots of the file, data having the following meaning, function, and value are arranged in order from the top. Note that the data described as Reserved represents undefined data. Normally null (0x00) is written, but whatever is written, Res
erved data is ignored. Future versions may change. Writing to this part is prohibited. If the part written as “Option” is not used, it is all treated the same as “Reserved”.

BLKID-TL0 (4 bytes) Meaning: BLOCKID FILE ID Function: value for identifying the start of the playback management file Value: fixed value = "TL = 0" (for example, 0x544C2D3)
0) MCode (2 bytes) Meaning: MAKER CODE Function: Code for identifying the manufacturer and model of the recorded device Value: Upper 10 bits (maker code) Lower 6 bits (model code) REVISION (4 bytes) Meaning: PBLIST Number of rewrites Function: Increment every time the playback management file is rewritten Value: Starts from 0 and increases by +1 S-YMDhms (4 bytes) (Option) Meaning: Year, month, day, hour, and time recorded by a device with a reliable clock Minute / Second Function: Value to identify the last recording date and time Value: 25 to 31 bits Year 0 to 99 (1980 to 2079) 21 to 24 bits Month 0 to 12 16 to 20 bits Day 0 to 31 11 to 15 bits 0 to 2305 to 10 bits Min. 0 to 59 00 to 04 bits Seconds 0 to 29 (in units of 2 seconds).

SN1C + L (2 bytes) Meaning: Represents the attribute of the name (1 byte) of the memory card written in the NM1-S area Function: Represents the character code and language code to be used in each 1 byte Value: Character code (C ) Is the upper 1 byte and distinguishes characters as follows. 00: No character code is set. Treat as a simple binary number 01: ASCII (American Standard Code for Information I
nterchange) 02: ASCII + KANA 03: modifided8859-1 81: MS-JIS 82: KS C 5601-1989 83: GB (Great Britai
n) 2312-80 90: S-JIS (Japanese Industrial Standards) (for Voic
e).

The language code (L) is the lower one byte and distinguishes the language according to the rules of EBU Tech 3258 as follows. 00: Not set 08: German 09: English 0A: Spanish 0F: French 15: Italian 1D: Dutch 65: Korean 69: Japanese 75: Chinese If there is no data, set to all zeros.

SN2C + L (2 bytes) Meaning: Represents the attribute of the name (2 bytes) of the memory card written in the NM2-S area Function: Represents the character code and language code to be used in 1 byte each Value: SN1C + L Same SINFSIZE (2 bytes) Meaning: Represents the total size of all additional information on the entire memory card written in the INF-S area Function: Describes the data size in 16-byte units,
If there is no data, be sure to set all zeros. Value: Size is 0x0001 to 0x39C (924) T-TRK (2 bytes) Meaning: TOTAL TRACK NUMBER Function: Total number of tracks Value: 1 to 0x0190 (up to 400 tracks), when there is no data Is all zeros VerNo (2 bytes) Meaning: Version number of format Function: Upper version is major version number, Lower is minor version number Value: Example 0x0100 (Ver1.0) 0x0203 (Ver2.3)

The data (FIG. 13B) written in the area following the above-mentioned header will be described below.

NM1-S Meaning: 1-byte name for the entire memory card Function: Variable-length name data represented by 1-byte character code (up to 256) Always write end code (0x00) at the end of name data The size must be calculated from this end code, and if there is no data, at least the null (0x0020)
x00) should be recorded in 1 byte or more Value: Various character codes NM2-S Meaning: 2-byte name for the entire memory card Function: Variable-length name data represented by 2-byte character code (512 at maximum) Name data For the end, be sure to write the end code (0x00). The size must be calculated from this end code. If there is no data, at least the first code (0x0120) is null (0x0120).
x00) must be recorded in 2 bytes or more. Value: Various character codes.

CONTENTS KEY Meaning: Stored after being protected by MG (M) with a value prepared for each song. Here, CON attached to the first song
Same value as TENTS KEY Function: A key required for calculating S-YMDhms MAC Value: 0 to 0xFFFFFFFFFFFFFFFF MAC Meaning: Copyright information falsification check value Function: Contents of S-YMDhms and CONTENTS K
Value created from EY Value: 0 to 0xFFFFFFFFFFFFFFFF.

TRK-nnn Meaning: SQN of ATRAC3 data file to be reproduced
(Sequence) number Function: Describes FNo in TRKINF Value: 1 to 400 (0x190) Set to all zeros when there is no track INF-S Meaning: Additional information data (for example, photos, lyrics, Information such as explanation) Function: Variable-length additional information data with a header A plurality of different additional information may be arranged. Each is assigned an ID and a data size. The additional information data including each header is composed of a minimum of 16 bytes or more and an integral multiple of 4 bytes. For details, refer to Value: Additional Information Data Structure described later. S-YMDhms (4 bytes) (Option) Meaning: Year, month, day, hour, minute, second recorded by a device with a reliable clock Value to identify the recording date and time, mandatory for EMD Value: 25 to 31 bits Year 0 to 99 (1980 to 2079) 21 to 24 bits Month 0 to 12 16 to 20 bits Day 0 to 31 11 to 15 bits 0 to 2305 to 10 bits Min. 0 to 59 00 to 04 bits Seconds 0 to 29 (in units of 2 seconds).

As the last slot of the playback management file, the same BLKID-TL0 as that in the header, M
Code and REVISION are written.

As a consumer audio device, the memory card may be pulled out during recording or the power may be turned off, and it is necessary to detect the occurrence of these abnormalities when the device is restored. As described above, the REVISION is written at the beginning and end of the block, and every time this value is rewritten, +1 is added.
I try to increment. If an abnormal end occurs in the middle of a block, the first and last REVIS
ION values do not match, and abnormal termination can be detected. Since there are two REVISIONS, abnormal termination can be detected with high probability. When abnormal termination is detected, a warning such as an error message is displayed.

Since the fixed value BLKID-TL0 is inserted at the head of one block (16 KB),
A fixed value can be used as a measure of repair if T breaks. That is, the file type can be determined by looking at the fixed value at the head of each block. In addition, since the fixed value BLKID-TL0 is duplicated in the header of the block and the end of the block, its reliability can be checked. The playback management file P
The same BLIST may be recorded twice.

The ATRAC3 data file has a considerably larger data amount than the track information management file, and the ATRAC3 data file has a block number BLOCK SERIAL as described later. However, the ATRAC3 data file usually has a plurality of files on the memory card.
After distinguishing contents by ONNUM0, BLO
Without CK SERIAL, duplication will occur and FA
It becomes difficult to recover the file when T is broken. In other words, a single ATRAC3 data file contains multiple BLs
Since it is composed of OCTs and may be arranged discretely, CONNUM0 is used to determine BLOCKs constituting the same ATRAC3 data file, and the ascending / descending order in the same ATRAC3 data file is changed to the block number BLOCK SERIAL. Determined by

Similarly, in the case where the FAT is not destroyed but the logic is erroneously inconvenient as a file, the maker code (MCode) is set at the beginning of the block so that the model of the maker that wrote it can be specified. Is recorded at the end.

FIG. 12C shows the structure of the additional information data. The following header is written at the head of the additional information. Variable-length data is written after the header.

INF Meaning: FIELD ID Function: Fixed value indicating the beginning of additional information data Value: 0x69 ID Meaning: Additional information key code Function: Indicates additional information classification Value: 0 to 0xFF SIZE Meaning: Individual additional information Size Function: Data size is free, but must be an integral multiple of 4 bytes. It must be at least 16 bytes. Null (0x
00) Value: 16 to 14784 (0x39C0) MCode Meaning: MAKER CODE Function: Code for identifying the manufacturer and model of the recorded device Value: Upper 10 bits (maker code) Lower 6 bits (model code) C + L Meaning: Represents the attribute of the character written in the data area from the 12th byte from the beginning Function: Represents the character code and language code to be used in 1 byte each Value: Same as SNC + L described above DATA Meaning: Individual additional information data Function: Represented by variable length data. The beginning of the actual data is always 12
Starting from the byte, the length (size) must be at least 4 bytes and always an integer multiple of 4 bytes. If there is a remainder from the end of the data, fill it with null (0x00) Value: Defined individually according to the content.

FIG. 13 shows the values of the additional information key code (0 to 0).
63) and an example of correspondence between types of additional information. Key code values (0 to 31) are assigned to character information relating to music, and (32 to 63) are URL (Uniform R).
esource Locator) (Web related). Character information such as an album title, an artist name, and a CM is recorded as additional information.

FIG. 14 shows the value of the additional information key code (64
To 127) and an example of correspondence between types of additional information. Key code values (64 to 95) are assigned to paths / others, and (96 to 127) are assigned to control / numerical value / data relations. For example, (ID = 9
In case 8), the additional information is TOC (Table of Content).
t) -ID. The TOC-ID is based on the TOC information of a CD (compact disc),
It shows the last music number, the music number, the total playing time, and the music playing time.

FIG. 15 shows the value of the additional information key code (12
8 to 159) and an example of correspondence between types of additional information.
Key code values (128 to 159) are assigned to the synchronous playback relationship. The EMD (Electroni
c Music Distribution) means electronic music distribution.

A specific example of the additional information data will be described with reference to FIG. FIG. 16A is similar to FIG.
The data structure of additional information is shown. FIG. 16B shows an example in which the key code ID = 3 and the additional information is an artist name. SIZE = 0x1C (28 bytes), indicating that the data length of this additional information including the header is 28 bytes. Further, C + L is a character code C = 0x01, and a language code L = 0x09. This value is an ASCII character code and indicates an English language according to the above-described rules. Then, with 1-byte data from the twelfth byte from the top, "SIMON & GRA
FUNKEL ”is written.
Since the size of the additional information is determined to be an integral multiple of 4 bytes, the remainder of 1 byte is (0x00).

FIG. 16C shows that the key code ID is 97 and the additional information is ISRC (International Standard Reco
rding Code). SIZE = 0
x14 (20 bytes), indicating that the data length of this additional information is 20 bytes. Also, C + L is C
= 0x00 and L = 0x00, which indicates that there is no setting of characters and languages, that is, that the data is a binary number. Then, an 8-byte ISRC code is written as data. ISRC provides copyright information (country, owner,
Recording year, serial number).

FIG. 16D shows an example in which the additional information is the recording date and time when the key code ID is 97. SIZE = 0x1
0 (16 bytes) and the data length of this additional information is 1
It is shown to be 6 bytes. Also, C + L is C = 0
x00, L = 0x00, which indicates that there is no setting of characters and languages. Then, 4 bytes (32
Bit) code, and the recording date and time (year, month, day,
Hours, minutes, seconds).

FIG. 16E shows an example of a reproduction log in which key code ID = 107 and additional information is used. SIZE = 0x
10 (16 bytes), indicating that the data length of this additional information is 16 bytes. Also, C + L is C =
0x00 and L = 0x00, indicating that there is no setting of characters and languages. Then, 4 bytes (3
A 2-bit code is written, and the playback log (year, month, day,
Hours, minutes, seconds). Those with a playback log function,
16 bytes of data are recorded for each reproduction.

FIG. 17 shows that one SU has N bytes (for example, N =
ATRAC3 data file A for 384 bytes)
3 shows a data array of 3Dnnnn. FIG. 17 shows an attribute header (1 block) of a data file and a music data file (1 block). In FIG.
The first byte (0x0000 to 0x7FF0) of each slot of the two blocks (16 × 2 = 32 Kbytes) is shown. As shown separately in FIG. 18, 32 bytes from the beginning of the attribute header are the header, 256 bytes are the music title area NM1 (256 bytes), and 512 bytes are the music title area NM2 (512 bytes). The following data is written in the header of the attribute header.

BLKID-HD0 (4 bytes) Meaning: BLOCKID FILE ID Function: Value for identifying the beginning of ATRAC3 data file Value: Fixed value = "HD = 0" (for example, 0x48442D3
0) MCode (2 bytes) Meaning: MAKER CODE Function: Code for identifying the manufacturer and model of the recorded device Value: Upper 10 bits (maker code) Lower 6 bits (model code) BLOCK SERIAL (4 bytes) Meaning: Track Serial number assigned to each function Function: The beginning of a block starts from 0 and the next block is +
Increment by 1 The value does not change even if edited. Value: Starting from 0 to 0xFFFFFFFF.

N1C + L (2 bytes) Meaning: Represents the attribute of track (song name) data (NM1) Function: Represents the character code and language code used for NM1 in 1 byte Value: Same as SN1C + L N2C + L (2 bytes) Meaning: Represents the attribute of track (song name) data (NM2) Function: Represents the character code and language code used for NM2 in 1 byte each Value: Same as SN1C + L INFSIZE (2 bytes) Meaning: All additional information on track Function: Describes the data size in 16-byte units,
If not, be sure to set all zeros. Value: Size is from 0x0000 to 0x3C6 (966) T-PRT (2 bytes) Meaning: Total number of parts Function: Indicates the number of parts that compose the track. Normally 1 Value: 1 to 0x285 (645 dec) T-SU (4 bytes) Meaning: Total SU number Function: Indicates the actual total SU number in one track. Value corresponding to the playing time of the song Value: 0x01 to 0x001FFFFF INX (2 bytes) (Option) Meaning: Relative location of INDEX Function: Pointer indicating the beginning of the rust portion (characteristic portion) of the song. The position from the beginning of the music is specified by the number obtained by dividing the number of SUs by 1/4. This is equivalent to a time four times longer than a normal SU (about 93 ms). Value: 0 to 0xFFFF (maximum, about 6084 seconds) XT (2 bytes) (Option) Meaning: INDEX playback time Function: The number of SUs at the time to be reproduced from the beginning specified by INX-nnn is specified by 1/4. This is equivalent to a time four times as long as a normal SU (about 93 ms). Value: 0x0000: No setting 0x01 to 0xFFF
E (up to 6084 seconds) 0xFFFF: Until the end of the song.

Next, the song name areas NM1 and NM2 will be described.

NM1 Meaning: Character string representing music title Function: Variable-length music title represented by one-byte character code (256 at maximum) When the end of name data, be sure to write the end code (0x00). If there is no data, at least from the beginning (0x0020) to null (0
x00) must be recorded in 1 byte or more Value: Various character codes NM2 Meaning: Character string representing song title Function: Variable-length name data represented by 2-byte character code (512 at maximum) Termination of name data is always terminated Write the code (0x00) The size must be calculated from this end code, and if there is no data, at least the null (0
x00) must be recorded in 2 bytes or more. Value: Various character codes.

The 80-byte data starting from the fixed position (0x320) of the attribute header is stored in the track information area TRK.
This is called INF, and mainly manages information related to security and copy control in a lump. FIG. 19 shows TRKINF.
Part is shown. The data in TRKINF will be described below according to the arrangement order.

CONTENTS KEY (8 bytes) Meaning: A value prepared for each song, which is stored after being protected by the security block of the memory card. Function: First key required when playing a song . Value used during MAC calculation: 0 to 0xFFFFFFFFFFFFFFFF MAC (8 bytes) Meaning: Copyright information falsification check value Function: Value created from the contents of multiple TRKINFs including the cumulative number of contents and the hidden sequence number Is a sequence number recorded in a hidden area of the memory card. Non-copyrighted recorders cannot read hidden areas. In addition, a personal computer equipped with a copyright-compatible dedicated recorder or an application capable of reading a memory card can access the hidden area.

A (1 byte) Meaning: Attribute of part Function: Indicates information such as compression mode in part Value: described below with reference to FIG. Special join with only 1 for sub signal and 1 for main signal (L + R)
The t mode is defined as monaural. The information of bits 2 and 1 may be ignored by a normal player.

Bit 0 of A forms information of ON / OFF of emphasis, bit 1 forms information of reproduction SKIP or normal reproduction, and bit 2 forms data division, for example, audio data or FAX. And other data. Bit 3 is undefined. Bit 4,
By combining 5, 6, as shown, A
TRAC3 mode information is defined. That is, N
Are the values of the mode represented by these three bits, that is, mono (N = 0, 1), LP (N = 2), SP (N = 4), and H
For five types of modes, X (N = 5) and HQ (N = 7), the recording time (in the case of a 64 MB memory card), the data transfer rate, and the number of SUs in one block are shown. The number of bytes of one SU is (mono: 136 bytes,
LP: 192 bytes, SP: 304 bytes, EX: 38
4 bytes, HQ: 512 bytes). Further, the mode of ATRAC3 (0: Dual 1:
J0int).

As an example, the case of using the 64 MB memory card and in the SP mode will be described. A 64 MB memory card has 3968 blocks. In the SP mode, since one SU is 304 bytes, there are 53 SUs in one block. One SU is (1024/441)
00) seconds. Therefore, one block is (1024/44100) × 53 × (3968-16)
= 4863 seconds = 81 minutes The transfer rate is (44100/1024) × 304 × 8 = 104737
bps.

LT (1 byte) Meaning: Reproduction restriction flag (bit 7 and bit 6) and security version (bit 5 to bit 0) Function: Indicates that there are restrictions on this track Bit 5 to bit 0: security version 0 (playback is prohibited if other than 0) FNo (2 bytes) Meaning: file number Function: track number when first recorded, and this value is Specify the position of the value for MAC calculation recorded in the hidden area Value: 1 to 0x190 (400) MG (D) SERIAL-nnn (16 bytes) Meaning: Serial number of security block (security IC 20) of recording device Function : A unique value that is different for each recording device. Value: 0 to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF CONNUM (4 bytes) Meaning: Content accumulation number Function: A unique value that is accumulated for each song and managed by the security block of the recording device. 2 to the 32nd power, 4
200 million songs are prepared and used to identify recorded songs. Value: 0 to 0xFFFFFFFF.

YMDhms-S (4 bytes) (Opti
on) Meaning: The playback start date and time of the track with the playback restriction Function: The date and time when the playback start specified by EMD is permitted Value: Same as the date and time notation described above YMDhms-E (4 bytes) (Option) Meaning: The playback restriction Track playback end date and time Function: Date and time when playback permission specified by EMD is completed Value: Same as the above date and time notation MT (1 byte) (Option) Meaning: Maximum value of the number of times playback is permitted Function: Maximum specified by EMD Number of times of reproduction Value: 1 to 0xFF When unused, the value of MT is set to 00 when bit7 of LT is 0. CT (1 byte) (Option) Meaning: Number of times of reproduction Function: Reproduction permitted Of the number that can actually be played. Decrements each time playback is performed. Value: 0x00 to 0xFF 0x00 when not used. When bit7 of LT is 1 and CT value is 00, playback is prohibited.

CC (1 byte) Meaning: COPY CONTROL Function: copy control Value: As shown in FIG. 21, bits 6 and 7 represent copy control information, and bits 4 and 5 represent copy control information relating to high-speed digital copy. , Bits 2 and 3 represent the security block authentication level. Bits 0 and 1 are undefined. Example of CC: (bit 7, 6) 11: Unlimited copy permitted, 01: Copy prohibited, 00: One copy permitted (bit 3, 2) 00: From analog or digital input Recording, MG authentication level is 0. Digital recording from CD is (bit7,6) is 0.
0, (bit3, 2) becomes 10 CN (1 byte) (Option) Meaning: High speed digital copy HSCMS (High speed Se
rial Copy Management System) Number of permitted copies Function: Extends the distinction between single copy and copy free.
Specify by the number of times. Valid only for the first generation copy, subtracted for each copy Value: 00: Copy prohibited, 01 to 0xFE: Number of times, 0x
FF: Unlimited number of times.

Following the above-described track information area TRKINF, 24-byte data starting from 0x0370 is called a parts management area PRTINF for parts management.
When one track is composed of a plurality of parts, PRTINFs are arranged in the order of the time axis. FIG. 22 shows the PRTI.
NF part is shown. About the data in PRTINF,
This will be described below according to the arrangement order.

PRTSIZE (4 bytes) Meaning: Part size Function: Indicates the size of the part. Cluster: 2 bytes (top), start SU: 1 byte (upper), end SU: 1 byte (lower) Value: cluster: 1 to 0x1F40 (8000), start SU: 0 to 0xA0 (160), end SU : 0 to 0
xA0 (160) (However, the counting method of SU is 0, 1,
PRTKEY (8 bytes) Meaning: Value for encrypting parts Function: Initial value = 0, follow editing rules when editing Value: 0 to 0xFFFFFFFFFFFFFFFF CONNUM0 (4 bytes) Meaning: Content cumulative number key created first Function: Role of ID for making content unique Value: The same value as the content cumulative number initial value key.

The attribute header of the ATRAC3 data file contains additional information INF as shown in FIG. This additional information is identical to the additional information INF-S in the playback management file except that the start position is not fixed.
(See FIGS. 11 and 12B). The data of the additional information INF starts from a position next to the last byte portion (in units of 4 bytes) of one or a plurality of parts.

INF Meaning: additional information data related to track Function: variable-length additional information data with a header. A plurality of different pieces of additional information may be arranged. I for each
D and the data size are added. The additional information data including the individual headers is a minimum of 16 bytes or more and is an integral multiple of 4 bytes. Value: Same as the additional information INF-S in the reproduction management file.

For the attribute header described above, ATRAC
The data of each block of the three data files follows. FIG.
As shown in FIG. 7, a header is added for each block. The data of each block will be described below.

BLKID-A3D (4 bytes) Meaning: BLOCKID FILE ID Function: value for identifying the beginning of ATRAC3 data Value: fixed value = “A3D” (for example, 0x41333442)
0) MCode (2 bytes) Meaning: MAKER CODE Function: Code identifying the manufacturer and model of the recorded device Value: Upper 10 bits (Maker code) Lower 6 bits (Model code) CONNUM0 (4 bytes) Meaning: First Cumulative content number created Function: role of ID to make content unique,
The value does not change even if it is edited. Value: The same value as the content cumulative number initial value key. BLOCK SERIAL (4 bytes) Meaning: Serial number assigned to each track Function: The start of a block starts from 0 and the next block Is +
The value does not change even if it is incremented one by one. Value: Starting from 0 to 0xFFFFFFFF BLOCK-SEED (8 bytes) Meaning: One key for encrypting one block Function: The head of the block is the security block of the recording device Generates a random number with the following block, the value incremented by +1. If this value is lost, no sound can be output for about 1 second, which is equivalent to one block. I will Does not change the value even if edited Value: Initially a random number of 8 bytes INITIALIZATION VECTOR (8 bytes) Meaning: Initial value required when encrypting and decrypting ATRAC3 data for each block Function: The beginning of the block starts from 0 The next block is the last encrypted 8-byte value of the last SU. In the case of the middle of the divided block, the last 8 bytes immediately before the start SU are used. Does not change the value even if edited Value: 0 to 0xFFFFFFFFFFFFFFFF SU-nnn Meaning: Sound unit data Function: Data compressed from 1024 samples, the number of bytes output differs depending on the compression mode. Do not change the value even if edited (for example, in SP mode,
N = 384 bytes) Value: ATRAC3 data value.

In FIG. 17, since N = 384, 42 SU is written in one block. Also, the first two slots (4 bytes) of one block are used as a header, and the last one slot (2 bytes) is assigned to BLKID-A3D, MCo.
de, CONNUM0, and BLOCK SERIAL are written in duplicate. Therefore, the remaining area M bytes of one block is (16,384-384 × 42−16 × 3 = 20).
8 (bytes). As described above, the 8-byte BLOCK SEED is duplicated therein.

An embodiment in which the present invention is applied to the above-described digital audio recorder will be described below with reference to the drawings. FIG. 24 shows a configuration of a main part of an embodiment of the present invention. In FIG. 24, reference numeral 70 denotes a CPU provided in the audio system.
The PU 70 is connected to the DSP 30 via a bus interface and a bus. An operation unit 80 is connected to the CPU 70.

As shown in FIG. 24, the operation unit 80 is provided with button groups 81 to 86 and the like. Specifically, 81
Is the back button for the recording / playback position.
Reference numeral 84 denotes a recording / reproduction position advance button, reference numeral 82 denotes a recording button, reference numeral 85 denotes a reproduction button, reference numeral 83 denotes a stop button, reference numeral 86 denotes a stop button. Is a pause button.

When one of the button groups 81 to 86 of the operation unit 80 is pressed, detection information corresponding to the pressed button is generated in the operation unit 80 at the timing when the button is pressed. Is supplied to the CPU 70.
The CPU 70 monitors the operation state of the operation unit 80 based on the detection information from the operation unit 80, and when it is determined that a predetermined operation has been performed on a predetermined button, generates the control information corresponding to the operation button. Various operations are executed by supplying control information to each unit.

For example, when the recording button 82 is pressed, a recording operation is started. That is, audio data generated from the selected predetermined input source is sequentially written to a predetermined area of the memory card 40. When the play button 85 is pressed, a reproducing operation is started. That is, audio data written in a predetermined area of the memory card 40 is sequentially read out, an analog audio signal is generated based on the read audio data, and taken out from the line output terminal 19.

In the playback state, when the playback button 85 is further pressed and kept pressed for a predetermined time or longer by the user, the process proceeds to the index management information writing process in parallel with the playback operation, and the user performs any operation. Is set. Specifically, in the index management information writing process, information indicating the start position of the index information defined by the timing at which the play button 85 is pressed;
The information indicating the time when the play button 85 is kept pressed is the CP
The information is generated in U70, and the information is written in a predetermined area of the memory card 40 as information indicating a playback section.

That is, a characteristic part or a so-called digest part that the user likes in the reproduced music or the like is designated by the user, and information indicating the reproduction section is written in a predetermined area of the memory card 40. The information indicating the start position of the index information defined by the timing at which the play button 85 is pressed is stored, for example, in the INX in the attribute header of the ATRAC3 audio file A3DDnnn, and the play button 85 is kept pressed. Information indicating the time is stored in XT. INX
Can be specified up to about 6084 seconds by XT, and can be specified up to about 6084 seconds by XT.

[0134] Once a characteristic part or a so-called digest part that the user likes is specified in this manner, and information indicating the reproduction section is written in a predetermined area of the memory card 40, the reproduction operation from the next time is performed. Prior to this, it is possible to easily search for a song, and it is also possible to collectively reproduce only characteristic portions.

With respect to the above-described embodiment of the present invention,
This will be described in more detail with reference to FIGS. 26 and 27. In the data format described above, the number of SUs is reduced to 1/4 as the values of INX and XT. However, in the following description, the number of SUs is reduced to 1/4 for simplicity.
An example will be described. First, a playback operation is started by inserting a memory card into the recorder and pressing a play button 85 (step S1). In step S2,
It is determined whether it is the beginning of the track. If it is determined that it is the head of the track, counting of the number of SUs is started, and the process proceeds to step S3.

Then, in step S3, it is determined whether or not the play button 85 has been further pressed. Only when it is determined that the play button 85 has been pressed, the process proceeds to step S4. In step S4, it is determined whether or not the play button 85 has been pressed for 4 seconds or longer. Only when the play button 85 is kept pressed for 4 seconds or longer, the process moves to step S5, and the index management information is written in parallel with the play operation. In the index management information writing state, first, the count value of the number of SUs from the beginning of the track to the timing when the play button 85 is pressed is written to INX. More specifically, as shown in FIG. 27, when the play button 85 is pressed at the timing of t1 and continues to be pressed for 4 seconds to reach the timing t2, the SU from the beginning of the track to the timing t1 goes back 4 seconds from the timing t2. Count value P
1 is written to INX. The start position of the index information is defined by the processing in step S5.

When the processing in step S5 is completed, it is determined in step S6 whether or not the play button 85 has been depressed. Step S only when the finger is released from the play button 85 and the play button 85 is turned off.
7, and in step S7, the count value of the number of SUs corresponding to the time when the play button 85 is kept pressed is X.
It is written to T. Specifically, assuming that the play button 85 is turned off at the timing of t3 as shown in FIG. 27, the time during which the play button 85 is kept pressed (t3-t1)
The count value (P3-P1) of the number of SUs corresponding to XT is XT
Is written to. The length of the playback section specified by the processing in step S7 is defined. When the processing in step S7 is completed, the index management information writing processing parallel to the reproduction operation ends.

In the description of the above-described embodiment, the play button 85 is also used for more than 4 seconds.
The case where the process is shifted to the index management information writing process when the button is continuously pressed has been described.However, not only the timing when the button is pressed as another button but also the timing when the button is turned off is monitored and pressed for a predetermined time or more. If the process is continued, the process may proceed to the index management information writing process. That is, in the normal operation unit monitoring process,
Although only the timing at which the arranged button is pressed is used to generate various control information, the present invention also utilizes the timing at which the button is turned off to determine whether the button has been pressed for 4 seconds or more. The use of the operation button is enabled by distinguishing between the normal operation and the index management information writing process. Therefore, the determination time for distinguishing the normal operation from the index management information writing process is not limited to 4 seconds, and may be 4 seconds or more or 4 seconds or less as long as malfunction can be prevented.

FIG. 25 shows an operation unit 8 according to another embodiment.
0 is shown. In another embodiment, a dedicated index button 87 is provided in addition to the normal operation button groups 81 to 86, and the index management information is written by using the index button 87. The detection information generated in the operation unit 80 according to the operation state is the same as that in the above-described embodiment.
It is supplied to PU70.

For example, when the recording button 82 is pressed, a recording operation is started. That is, audio data generated from the selected predetermined input source is sequentially written to a predetermined area of the memory card 40. When the play button 85 is pressed, a reproducing operation is started. That is, audio data written in a predetermined area of the memory card 40 is sequentially read out, an analog audio signal is generated based on the read audio data, and taken out from the line output terminal 19.

When the index button 87 is pressed in the playback state and kept pressed for a predetermined time or more by the user, the process proceeds to the index management information writing process in parallel with the playback operation, and the user selects an arbitrary value. A playback section is set. Specifically, in the index management information writing process, information indicating the start position of the index information defined by the timing at which the index button 87 is pressed and information indicating the time during which the index button 87 is pressed are stored in the CPU 70. The information is generated and written in a predetermined area of the memory card 40 as information indicating a playback section.

That is, a characteristic part or a so-called digest part that the user likes in the reproduced music or the like is designated by the user, and information indicating the reproduction section is written in a predetermined area of the memory card 40. The information indicating the start position of the index information defined by the timing at which the index button 87 is pressed is stored in the INX of the ATRAC3 data file A3D-nnn, similarly to the above-described embodiment, and the playback button 85
Is stored in the XT.

[0143] Once the characteristic part or the so-called digest part which the user likes is specified in this way, and the information indicating the reproduction section is written in a predetermined area of the memory card 40, the reproduction operation from the next time is started. Prior to this, it is possible to easily search for a song, and it is also possible to collectively reproduce only characteristic portions.

Another embodiment of the present invention will be described in more detail with reference to FIGS. 27 and 28. First, a playback operation is started by inserting a memory card into the recorder and pressing a play button 85 (step S11). In step S12, it is determined whether or not the track is the head. If it is determined that the track is the head of the track, counting of the number of SUs is started, and step S
Go to step 13.

Then, in a step S13, it is determined whether or not the index button 87 is pressed. Only when it is determined that the index button 87 has been pressed, the process proceeds to step S14. In step S14, it is determined whether index button 87 has been pressed for 4 seconds or more. Step S15 only when the index button 87 is pressed for more than 4 seconds.
Then, the index management information is written in parallel with the reproduction operation. In the index management information writing state, first, the count value of the number of SUs from the beginning of the track to the timing at which the index button button 87 is pressed is written to the INX. More specifically, as shown in FIG. 27, when the index button 87 is pressed at the timing of t1 and continuously pressed for 4 seconds to reach the timing t2, the SU from the beginning of the track to the timing t1 goes back 4 seconds from the timing t2. Is written to INX. The start position of the index information is defined by the processing in step S15.

When the processing in step S15 is completed, it is determined in step S16 whether or not the index button 87 has been depressed. Only when the finger is released from the index button 87 and the index button 87 is turned off, the process proceeds to step S17. In step S17, the count value of the number of SUs corresponding to the time the index button 87 is kept pressed is written to XT. It is. Specifically, if the index button 87 is turned off at the timing of t3 as shown in FIG.
The time during which the index button 87 is kept pressed (t3-t
The count value (P3-P1) of the number of SUs corresponding to 1) is written into XT. The length of the playback section specified by the processing in step S17 is defined. Step S1
When the process of No. 7 is completed, the index management information writing process in parallel with the reproduction operation ends.

In the above description of the other embodiment, the case has been described where the dedicated index button 87 is used and the process shifts to the index management information writing process when the index button 87 is kept pressed for 4 seconds or more. Alternatively, the index management information may be written using only the timing at which the provided index button 87 is pressed.

FIG. 29 shows a processing procedure when writing index management information using only the timing at which the index button 87 is pressed. A modification of the other embodiment will be described in more detail with reference to FIGS. 29 and 27. First, the playback operation is started by inserting the memory card into the recorder and pressing the play button 85 (step S21). In step S22, it is determined whether the track is the head. If it is determined that the track is the head of the track, counting of the number of SUs is started,
Move to step S23.

In step S23, it is determined whether the index button 87 has been pressed for 0.2 seconds or more. Only when it is determined that the index button 87 has been pressed, the process proceeds to step S24. In step S24, it is determined again whether index button 87 has been pressed for 0.2 seconds or more. In step S23 and step S24, the criterion of 0.2 seconds is provided to determine whether or not the index button 87 has been pressed, because whether or not an intentional operation has been performed on the index button 87 May be simply determined to determine whether the button has been pressed. Only when it is determined that the index button 87 has been pressed, the process proceeds to step S25, and the index management information writing state is set in parallel with the reproducing operation. In the index management information writing state, first, the count value of the number of SUs from the beginning of the track to the timing when the index button button 87 is first pressed is written to the INX. Specifically, as shown in FIG. 27, the index button 87 is pressed at the timing of t1, and is continuously pressed for 0.2 seconds at the timing t1.
4, the count value P1 of the number of SUs from the beginning of the track to the timing t1 is written into the INX 0.2 seconds before the timing t4. This step S
The start position of the index information is defined by the processing of 25.

When the processing in step S25 is completed, in step S26, S is determined according to the time from when the first index button 87 is pressed to when the second index button 87 is pressed.
The count value of the number of U is written to XT. The length of the playback section specified by the process of step S26 is defined. More specifically, as shown in FIG. 27, when the index button 87 is pressed at the timing of t3 and continues to be pressed for 0.2 seconds to reach the timing t5, the end of the playback section goes back 0.2 seconds from the timing t5. Timing is defined, and the count value (P3-P1) of the number of SUs according to the time (t3-t1) from the timing when the first index button 87 is pressed to the timing when the second index button 87 is pressed is calculated. Written to XT. When the processing in step S26 is completed, the index management information writing processing parallel to the reproduction operation ends.

In the description of the above-described embodiment and other embodiments, in the playback state in which the playback button 85 is pressed, when a predetermined operation is performed on a predetermined operation member, the index management information writing process is performed. Has been described, but even in the recording state in which the recording button 82 is pressed, the index management information writing process is performed in parallel with the recording operation when a predetermined operation is performed on a predetermined operation member. It is also possible.

According to the present invention, as shown in FIG. 20, a recordable recording time of 128 minutes can be set in the LP mode. For example, three 40-minute CDs are recorded on one memory card. be able to. Thus, 1
When a plurality of albums are recorded on a single memory card, it is convenient for searching if a representative song of each album can be reproduced as a digest portion. It is desirable that the representative song of the album is a digest portion of a song that is single-cut from the album.

The digest part of the album is, for example, 0x06 of the reproduction management file (PBLIST) shown in FIG.
Recorded in INF-S after 47. In the present invention, FIG.
As shown in FIG. 4, the album digest is specified with a variable length at ID = 77. The playback management file (PBL)
In the case where digest points are set for a plurality of albums in the IST), the total number of albums recorded on one memory card (refer to ID = 117 in FIG. 14)
That is, the number of album digests to be set to ID = 77 is determined with reference to (total number of sets). Digests (INX, X) for all songs already recorded on the given album
If Y) is set, the song number of the representative song in the album is set to the ID = 77.

When the digest portion of the album is reproduced, ID = 77 is searched by referring to the INF-S after address 0x0647 of the reproduction management file (PBLIST), and the album number and the song number set therein are referred to. Play a representative song by doing that. In addition, the digest information (INX, X
T) may be recorded.

In the description of the above-described one embodiment and other embodiments, the case where the count value of the number of SUs from the head of the track is used as the information defining the start position of the index information in the index management information writing state is described. However, information indicating another reproduction position or reproduction timing may be written in INX. Also, a case has been described where the count value of the number of SUs during a predetermined timing is used as the information defining the length of the playback section, but information indicating other playback positions and playback timings is written in XT. Is also good. Furthermore, although the case where the index management information is written in INX and XT has been described, the index management information may be written in another predetermined area.

In the above description, the present invention is applied to the processing of audio data. However, the present invention is applicable to a content composed of both audio data and video data, or a content composed of only video data. Can be applied.

[0157]

According to the present invention, when a predetermined operation is performed on a predetermined operation member, the process shifts to index management information writing processing in parallel with the reproduction operation, and the user can set an arbitrary reproduction section. It becomes possible. In particular,
In the index management information writing process, information indicating the start position of the index information defined by the timing at which the play button is pressed by the user, and information indicating the time during which the play button was pressed are generated in the control unit, These pieces of information are written in a predetermined area of the semiconductor memory as information indicating a reproduction section. As a result, it is possible to specify a characteristic portion that the user likes in the reproduced music or the like, or a so-called digest portion. Therefore, according to the present invention, the index information of the music can be specified by the user himself, and the search can be easily performed using the index information. Therefore, the convenience of the recording / reproducing apparatus can be improved, and the usability can be improved.

[Brief description of the drawings]

FIG. 1 is a block diagram relating to a digital audio recorder / player using a nonvolatile memory card of the present invention.

FIG. 2 shows an internal block diagram of a DSP applied to the present invention.

FIG. 3 shows an internal block diagram of a memory card applied to the present invention.

FIG. 4 is a schematic diagram showing a file management structure using a memory card as a storage medium according to the present invention.

FIG. 5 shows a physical structure of data in a flash memory in a memory card applied to the present invention.

FIG. 6 shows a data structure in a memory card applied to the present invention;

FIG. 7 is a branch diagram showing a file structure stored in a memory card.

FIG. 8 shows a data structure of a playback management file PBLIST.MSF, which is a subdirectory stored in the memory card.

FIG. 9 is a data structure diagram in a case where one continuous ATRAC3 data file is divided for each predetermined unit length and an attribute file is added.

FIG. 10 is a structural diagram for explaining combine edit processing and split edit processing of the present invention.

FIG. 11 shows a data structure diagram of a reproduction management file PBLIST.

FIG. 12 shows a data structure diagram of a reproduction management file PBLIST.

FIG. 13 shows a correspondence table of the types of the additional information data.

FIG. 14 shows a correspondence table of types of the additional information data.

FIG. 15 shows a correspondence table of types of the additional information data.

FIG. 16 shows a data structure of additional information data.

FIG. 17 is a detailed data structure diagram of an ATRAC3 data file.

FIG. 18 is a data structure diagram of an upper part of an attribute header constituting an ATRAC3 data file.

FIG. 19 is a data structure diagram of a middle section of an attribute header constituting an ATRAC3 data file.

FIG. 20 is a table showing types of recording modes, recording times in each recording mode, and the like.

FIG. 21 is a table showing a copy control state.

FIG. 22 is a data structure diagram of a lower part of an attribute header constituting an ATRAC3 data file.

FIG. 23 is a data structure diagram of a header of a data block of an ATRAC3 data file.

FIG. 24 is a schematic diagram of the vicinity of an operation unit according to an embodiment of the present invention.

FIG. 25 is a schematic diagram of the vicinity of an operation unit according to another embodiment of the present invention.

FIG. 26 is a flowchart showing a procedure for specifying a digest part in one embodiment of the present invention.

FIG. 27 is a timing chart related to designation of a digest unit in one embodiment of the present invention and another embodiment.

FIG. 28 is a flowchart showing a procedure of specifying a digest part according to another embodiment of the present invention.

FIG. 29 is a flowchart showing a procedure of specifying a digest part in another embodiment of the present invention.

[Explanation of symbols]

10 ... audio encoder / decoder IC, 20
... Security IC, 30 ... DSP, 40 ...
・ Memory card, 42 ・ ・ ・ Flash memory, 52 ・
..Security block, 70... CPU, 80.
..Operation section, 85 ... play button, 87 ... index button, TRKLIST. MSF: Track information management file, INFLIST. MSF: additional information management file, A3Dnnnn. MSA: Audio data file

Claims (9)

[Claims] 1. An editing apparatus for editing a digest portion of a program recorded in a non-volatile memory, comprising: input means for allowing a user to input a start position and an end position of a digest portion; An editing apparatus comprising: generating means for generating a starting address of digest section and digest period information; and recording means for recording the starting address of digest section and digest period information in a nonvolatile memory. 2. The program according to claim 1, wherein said program is divided into a plurality of blocks, one of said plurality of divided blocks is used as a management area, and said start address and digest period information are recorded in said management area. 2. The editing device according to claim 1, wherein: 3. The editing apparatus according to claim 1, wherein the input of the start position and the end position of the digest portion by the user is designated by twice operating the same key. 4. The editing apparatus according to claim 3, wherein said key is an index key. 5. The editing apparatus according to claim 3, wherein said key is a reproduction key. 6. The editing apparatus according to claim 1, wherein the program recorded in said non-volatile memory is categorized into a plurality of albums, and further comprising a reproduction management file area in which digest information for each of said albums is described. 7. An editing method for editing a digest portion of a program recorded in a nonvolatile memory, comprising: an input step for a user to input a start position and an end position of the digest portion; and a digest portion according to the start position and the end position. And a recording step of recording the digest section start address and the digest period information in a nonvolatile memory. 8. A nonvolatile memory in which a program composed of a plurality of blocks is recorded, wherein one of the plurality of blocks is used as an attribute information recording area in which attribute information is recorded, and each of the other blocks is Is a non-volatile memory comprising a header section and a main data section, in which the start address of the digest section of the program specified by the user and the digest period information are recorded in the attribute information recording area. 9. The nonvolatile memory according to claim 8, wherein the recorded program is categorized into a plurality of albums, and further comprising a reproduction management file area in which digest information for each of the albums is recorded.