JP4207132B2 - Editing apparatus and editing method - Google Patents

Description

  The present invention relates to an editing apparatus and an editing method, and more particularly to an editing apparatus and an editing method for editing a program recorded on a recording medium.

  Conventionally, recording media used in audio equipment generally have a capacity capable of recording audio data of about 80 minutes. However, with the recent increase in capacity of recording media, it is not comparable to conventional recording media. Long audio data can be stored in a recording medium. In addition, the price of recording media has been reduced, and users can enjoy large-capacity recording media at low cost. Among them, a hard disk drive (hereinafter referred to as HDD), which is representative of a large-capacity recording medium, is a medium that has attracted the most attention in recent years in terms of capacity and price.

  Since HDDs can store and store a large number of songs that cannot be compared with conventional recording media, the functions of audio devices themselves have also changed greatly. For example, the playlist function is one of them.

  With the playlist function, you can create a virtual album that collects only your favorite songs by selecting only the music files (tracks) recorded on the hard disk and registering them in a file called a playlist. Function. In other words, it is a function that is an extension of the program playback function provided in the conventional CD playback device.

  However, with the conventional playlist function, when the tracks registered in the playlist are divided (divided), combined (combined), or erased, the songs registered in the playlist cannot be played back. Is a problem. This is a problem that occurs because the track information registered in the playlist is not updated when the actual track is edited.

  Another problem with the conventional playlist function is that it is highly likely that editing operations such as divide, combine, and erase are erroneously performed on tracks registered in the playlist.

  Accordingly, an object of the present invention is to provide an editing apparatus and an editing method capable of deleting track information corresponding to a track from a playlist when the actual track is edited.

  Another object of the present invention is to provide an editing apparatus and an editing method capable of preventing a track registered in a playlist from being erroneously edited.

In order to solve the above-mentioned problem, the first invention
Operating means for instructing the program to edit based on the first management information with respect to a recording medium which is managed by the first management information and also records the program managed by the second management information; ,
A discriminating unit for discriminating whether or not the program instructed to edit by the operating unit is managed by the second management information;
A notification means for giving a warning before performing an editing operation when the determination means determines that the program is managed by the second management information;
A control means for editing the first management information and the second management information when the editing instruction is confirmed by the notification means and the editing instruction is confirmed and the editing instruction is confirmed;
The control means deletes the program before the combination or division from the second management information when the editing instruction for the combination or division is given to the program based on the first management information. The editing apparatus newly registers the divided program in the second management information.

The second invention is
Was an editing instruction given to the program based on the first management information on a recording medium that is managed by the first management information and also recorded by the second management information? A first determination step of determining whether or not,
A second determination step of determining whether or not the program instructed to be edited is managed by the second management information when it is determined that the editing instruction is performed in the first determination step;
A notification step of giving a warning before performing an editing operation when it is determined in the second determination step that the program is managed by the second management information;
An editing process for editing the first management information and the second management information when the editing instruction is confirmed in the notification process and the editing instruction is confirmed and the editing instruction is confirmed;
In the editing step, when a combination or division editing instruction is given to the program based on the first management information in the first determination step, the program before the combination or division is deleted from the second management information. In this editing method , the combined or divided program is newly registered in the second management information.

In the present invention, when a predetermined program editing is instructed second management information to determine whether it is managed, it is the determine by being managed by the second management information, Before editing the predetermined program, the user is warned that the predetermined program instructed to be edited is managed by the second management information . Therefore, the user is informed that the predetermined program instructed to edit is the second management information. You can check whether it is registered in.

As described above, according to the present invention, when the edits to Jo Tokoro program is instructed, whether or not a predetermined program is managed by the second management information is discriminated, the second management when it is determined that the management information before editing the predetermined program, since it is alerting the user to a predetermined program to edit instruction is given is managed by the second management information, The user can confirm whether or not the predetermined program instructing editing is managed by the second management information . Accordingly, it is possible to prevent an erroneous editing operation for the program managed by the second management information .

Further, it is possible to prevent the program that is not managed by the first management information, generated in the second management information. That is, it is possible to prevent a state in which the program managed by the second management information cannot be reproduced by editing.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing an example of the configuration of a dubbing apparatus according to an embodiment of the present invention. As shown in FIG. 1, a dubbing apparatus according to an embodiment of the present invention includes a system controller 100, a disk playback apparatus 200, an HD recording / playback apparatus 300, an audio input / output unit 400, and an external control signal input / output unit 500. .

  The audio signal transmitted / received among the disc playback apparatus 200, the HD recording / playback apparatus 300, and the audio input / output unit 400 is an audio signal that conforms to a digital audio interface of IEC60958, for example. However, since the audio input / output unit 400 includes an analog input terminal which will be described later, an audio signal analog input to the analog input terminal of the audio input / output unit 400 is digitally converted by an AD converter which will be described later, and an LR clock and a bit clock. Is supplied to the HD recording / reproducing apparatus 300.

  FIG. 2 is a block diagram showing an example of the configuration of the system controller 100 according to one embodiment of the present invention. As shown in FIG. 2, the system controller 100 includes a controller 101, a display device 102, and an operation device 103. The controller 101 controls each block provided in the dubbing apparatus using a system control signal.

  The display device 102 is a display device configured by, for example, a liquid crystal display or an FL tube. The display device 102 is connected to the controller 101 and performs display based on a signal supplied from the controller 101. For example, the display device 102 displays information such as track number and performance time based on a signal supplied from the controller 101.

  The operation device 103 is for operating the dubbing device, and specifically includes a power key, a playback key, a pause key, a stop key, a recording key, a synchronized recording key, a playlist registration key, a menu key, and a jog key. Etc.

  The power key is for turning on / off the power of the dubbing apparatus. The reproduction key is for starting reproduction of a music file recorded on an optical disk loaded in the disk reproduction apparatus 200 or an HD recording / reproduction apparatus. The pause key is used to temporarily stop recording / playback of a file recorded on an optical disk or HD recording / playback apparatus loaded in the disk playback apparatus 200. The stop key is used to stop recording / playback of the music file recorded on the optical disk or HD recording / playback apparatus loaded in the disk playback apparatus 200. The recording key is a key for starting recording of data to the HD recording / reproducing apparatus.

  The synchronized recording key is a key for performing synchronized recording. Synchronized recording is a recording method that automatically starts / stops recording in accordance with the playback side. Specifically, when the synchronized recording key is pressed, the recording of the HD recording / reproducing apparatus 300 is started in synchronization with the reproduction of the disk reproducing apparatus 200. Then, the recording of the HD recording / reproducing apparatus 300 is stopped in synchronization with the stop of the reproduction of the disk reproducing apparatus 200. Therefore, the user can easily store the data reproduced by the disc reproducing apparatus 200 in the HD recording / reproducing apparatus 300 without operating the disc reproducing apparatus 200 and the HD recording / reproducing apparatus 300, respectively. The menu key is for displaying a menu such as an editing operation on the display device 102. The playlist registration key is for starting registration of a song to the playlist.

  The jog key can be pressed and has a rotatable structure. Specifically, there are, for example, 10 stop positions intermittently per rotation, and data is updated at each stop position. For example, when rotating to the right, the numerical value selected on the display device 102 is updated +, and when rotating to the left, the numerical value selected on the display device 102 is updated. Note that playback, pause, stop, recording, synchronized recording, menu selection, and the like can be performed only by this jog key operation.

  FIG. 3 is a block diagram showing an example of the configuration of the disc playback apparatus 200 according to one embodiment of the present invention. As shown in FIG. 3, the disk reproducing apparatus 200 includes a spindle motor 201, an optical head 202, an RF (Radio Frequency) amplifier 203, a servo circuit 204, a thread 205, an EFM (Eight to Fourteen Modulation), and a CIRC (Cross Interleave Reed). -Solomon Code) It is composed of a decoding circuit 206 and a controller 207. Here, the optical disk D is a compact disk, for example.

  The optical disk D mounted on the disk playback apparatus 200 is driven to rotate at a constant linear velocity (Constant linear Velocity (CLV)) by the spindle motor 201 during the CD playback operation.

  The optical head 202 irradiates the recording surface of the optical disc D with laser light and receives reflected light, thereby reading data recorded in the form of pits on the optical disc D and supplying it to the RF amplifier 203. The laser light intensity is optimized by APC (Automatic Power Control) (not shown). The optical head 202 can be displaced in the tracking and focusing directions. Further, the optical head 202 is movable in the radial direction of the optical disc D based on a signal supplied from the sled 205.

  The RF amplifier 203 generates a reproduction RF signal, a focus error signal, and a tracking error signal based on the signal supplied from the optical head 202. Then, the focus error signal and tracking error signal are supplied to the servo circuit 204, and the reproduction RF signal is supplied to the EFM and CIRC decoding circuit 206.

  The servo circuit 204 generates various drive signals such as a focus drive signal, a tracking drive signal, a threat drive signal, and a spindle drive signal based on the focus error signal and the tracking error signal supplied from the RF amplifier 203. Based on these signals, the operations of the thread 205 and the spindle motor 201 are controlled.

  The EFM and CIRC decoding circuit 206 binarizes the reproduction RF signal supplied from the RF amplifier to obtain an EFM signal. Then, by performing EFM demodulation and CIRC decoding on the EFM signal, the information read from the optical disk is decoded into a digital format of 16-bit (Binary digiT (bit)) quantization and 44.1 KHz sampling. To the audio input / output unit 400. Here, CIRC decoding is error detection and error correction processing using CIRC, and specifically, error detection and error correction processing using C1 and C2 codes.

  Further, the EFM and CIRC decoding circuit 206 extracts control data such as a TOC (Table Of Contents) and a subcode described later from the reproduction RF signal supplied from the RF amplifier 203, and supplies these control data to the controller 207. To do.

  The controller 207 controls each unit based on data such as TOC and subcode supplied from the EFM and CIRC decoding circuit 206. In addition, the controller 207 transmits control data such as TOC and subcode to the system controller 100, for example. Further, the controller 207 receives a system control signal from the system controller 100, and controls each unit provided in the disc playback apparatus 200 based on the system control signal.

  FIG. 4 shows a frame structure of data generated by the EFM and CIRC decoding circuit 206 shown in FIG. 3 and supplied to the controller 207. As shown in FIG. 4, one frame includes a synchronization pattern portion (24 channel bits), a sub-coding portion (1 symbol, ie, 14 channel bits), a first data portion (12 symbols, ie, 12 × 14 channel bits), The first parity part (4 symbols, ie 4 × 14 channel bits), the second data part (12 symbols, ie 12 × 14 channel bits), and the second parity part (4 symbols, ie 4 × 14 channel bits) ). Here, although not shown in the figure, 3 bits of combined bits are included in the frame in order to combine each symbol (the synchronization pattern is also regarded as a symbol consisting of 24 bits). The total number of combined bits is 34 × 3 = 102 channel bits. Therefore, one frame consists of 588 channel bits in total.

  As shown in FIG. 5, 98 frames form a piece of information (subcode frame) composed of frame synchronization information, subcode information, data, and parity information. Subcode data in 98 frames represents subcode information as one block. Such a block will be described with reference to FIG. The subcodes of the first frame F1 and the second frame F2 are composed of fixed synchronization patterns S0 = 0010000000000000 and S1 = 00000000010010, respectively. As S0 and S1, a pattern that cannot appear in EFM modulation is used, and thereby the start position of the block related to the subcode information is specified during reproduction.

  The subcodes of the 96 frames of the third frame F3, the fourth frame F4,..., The 97th frame F97, and the 98th frame F98 are P1, Q1, R1, S1, T1, and U1, respectively. , V1, W1, P2 to W2,..., P95 to W95, P96 to W96. P1, P2,..., P96, Q1, Q2,..., Q96, R1 to R96, S1 to S96, T1 to T96, U1 to U96, V1 to V96, and W1 to W96 are completed. Formed information channels.

  The sub-coding information includes (1) information related to a program function such as cuing of music and reproduction according to a preset order, and (2) additional information such as text information. The subcode P channel and Q channel are used as information (1), and the subcode R channel to W channel are used as information (2). The P channel indicates a pause between music pieces, and is information used for rough cueing. The Q channel is information for more detailed control.

  FIG. 7 shows an example of the contents of Q data. As shown in FIG. 8, the Q data includes a control part, an address part, a data part, and a CRC (Cyclic Redundancy Code) part.

  The control unit is composed of 4 bits Q1 to Q4, and records data for identifying the number of audio channels, emphasis, digital data, and the like.

  The address part is composed of 4 bits Q5 to Q8, and records a control signal indicating the format and type of data in the data part to be described later.

  The CRC part is composed of 16 bits Q81 to Q96, and records data for error detection of the cyclic code.

  As shown in FIG. 8, the data portion is composed of 72-bit data Q9 to Q80. When the 4-bit data in the address part is “0001”, the data part (TOC (Table of Contents)) in the lead-in area of the optical disc D has the structure shown in FIG. That is, as shown in FIG. 9, the data part includes an MNR part (music number part), a POINT part (point part), a MIN part (elapsed time component part), an SEC part (elapsed time second component part), and a FRAME part. (Elapsed time frame number part), ZERO part (zero part), PMIN part (absolute time component part), PSEC part (absolute time second component part) and PFRAME part (absolute time frame number part). Each of these units is composed of 8-bit data.

  The MNR part, MIN part, SEC part, FRAME part and ZERO part are all fixed to “00” in hexadecimal notation, and “0” is assigned to all 8 bits.

  The PMIN section indicates the first music number or movement number when the POINT section is "A0" in hexadecimal display, and the last music number or movement number when the POINT section is "A1" in hexadecimal. Indicates the movement number. Further, when the POINT portion is “A2” in hexadecimal notation, the PMIN portion (absolute time component portion), the PSEC portion (absolute time second component portion) and the PFRAME portion (absolute time frame number portion) are respectively Indicates the absolute time (PTIME) when the lead-out area begins.

  Further, when the POINT part is expressed by a 2-digit BCD, the PMIN part (absolute time component part), the PSEC part (absolute time second component part) and the PFRAME part (absolute time frame number part) are respectively The address at which each song or movement indicated by the numerical value starts is expressed in absolute time (PTIME).

  Here, the case where the disc playback device 200 is a disc playback device capable of loading one optical disc has been described as an example, but the disc playback device 200 is a disc changer-type playback device capable of loading a plurality of optical discs. It does not matter.

  FIG. 9 is a block diagram showing an example of the configuration of the HD recording / reproducing apparatus 300 according to an embodiment of the present invention. The HD recording / reproducing apparatus 300 is an apparatus for recording data for recording / reproducing audio data and managing audio data.

  As shown in FIG. 9, the HD recording / reproducing apparatus 300 includes a digital audio interface (hereinafter referred to as digital audio I / F) 301, an AD / DA interface (hereinafter referred to as AD / DA I / F) 302, an encoding / decoding apparatus 303, Magic gate core unit 304, shared RAM (Random Access Memory) 305, HD controller 306, SDRAM (Synchronous Dynamic Random Access Memory) 307, FAT (File Allocation Table) file system 308, HDD (Hard Disk Drive) 309.

  The digital audio I / F 301 is an interface for digital audio signals, and is supplied from an EFM and CIRC decoding circuit 206 provided in the disc playback apparatus 200 or a digital input terminal (described later) provided in the audio input / output unit 400. The obtained digital audio signal is supplied to the encoding / decoding device 303. Further, the digital signal supplied from the encoding / decoding device 303 is supplied to a digital output terminal (described later) provided in the audio input / output unit 400.

  The AD / DA I / F 302 supplies a digital audio signal supplied from an A / D conversion unit (described later) provided in the audio input / output unit 400 to the encoding / decoding device 303. Further, the digital audio signal supplied from the encoding / decoding device 303 is supplied to the DA converter 402 provided in the audio input / output unit 400.

  The encoding / decoding device 303 compresses the digital audio signal supplied from the digital audio I / F 301 or AD / DA I / F 302 by ATRAC3 (Adaptive Transform Acoustic Cording 3) and supplies the compressed signal to the magic gate core unit 304. The data compression method is not limited to ATRAC3, but is MP3 (MPEG-1 audio layer 3), WMA (Windows (registered trademark) Media Audio), AAC (Advanced Audio Cording), or TwinVQ (Transform-domain). A compression method such as Weighted Interleave Vector Quantization may be used.

  The audio compression encoding / decoding device 303 decompresses the data compressed by ATRAC3 supplied from the magic gate core unit 304 and supplies the decompressed data to the digital interface 301 and / or the AD / DA I / F 302.

  The magic gate core unit 304 encrypts the audio data supplied from the encoder / decoding device 303 and supplies it to the shared RAM 305. MagicGate (MAGIC GATE) is a function for encrypting content (music) for the purpose of copyright protection and mutual recognition between devices.

  The shared RAM 305 stores the digital audio data supplied from the magic gate core unit 304 and supplies it to the HD controller 306. The shared RAM 305 stores the digital audio data supplied from the HD controller 306 and supplies it to the magic gate core unit 304.

  The HD controller 306 is a microcomputer, and each part of the HD recording / reproducing apparatus 300 is controlled by the microcomputer. For example, the HD controller 306 controls the ATRAC3 encoding / decoding device 303 to start ATRAC3 encoding or start ATRAC3 decoding. The HD controller 306 controls the start of encryption or the start of decryption for the MAGIC GATE CORE unit (5-4). The HD controller 306 and the HDD 309 are connected by, for example, an IDE (Integrated Device (Drive) Electronics) bus compliant with ATA (AT Attachment), and data writing and reading via this bus are performed in a PIO (Programmable I / O) mode. It is done by data transfer using.

  The HD controller 306 receives an interrupt from the shared RAM 305 every time encryption of one sound unit (about 23.2 msec) is completed in the magic gate core unit 304. Each time this interrupt occurs, the HD controller 306 transfers the data stored in the shared RAM 305 to the SDRAM 307, further transfers it to the HDD 309 via the FAT32 file system (308), and records music as a file on the HDD 309. .

  The shared RAM 305 interrupts the HD controller 306 whenever the decoding of one sound unit is completed in the magic gate core unit 304. The HD controller 306 transfers the next sound unit from the SDRAM 307 to the shared RAM for each interrupt.

  The SDRAM 307 stores audio digital data supplied from the HDD 309 or the shared RAM 305.

  The FAT32 file system 308 is a file system used when the HD controller 306 reads data from the HDD 309 and writes data to the HDD 309, and is indispensable for managing the data written in the HDD 309 for each file. It is a thing. Here, for convenience, the FAT32 file system 308 is indicated by a block, but the FAT32 file system 308 is software incorporated in the HD controller 306 and is not a physical one as shown in other blocks. In the embodiment of the present invention, the FAT32 file system is used as the file system, but the VFAT32 file system may be used as the file system. NTFS (NT File System), HFS (Hierarchical File System), HFS Plus, and the like may be used as the file system.

  All data recorded in the HDD 309 is a file managed by the FAT32 file system 308, and a database for audio data and music management information, which will be described later, is also a file managed by the FAT32 file system 308. The FAT32 file system 308 includes system calls such as opening, closing, reading, and writing of files necessary for file operations.

  The HDD 309 stores audio data and the like. Specifically, the HDD 309 stores an album number management file, a playback time management database file, an album / track name database file, a TOC database file, an album playback management file, a music file, a playlist management file, and the like. Details of these files will be described later.

  FIG. 10 is a flowchart for explaining a process of recording audio data in the HD recording / reproducing apparatus 300. Here, recording audio data in the HD recording / reproducing apparatus 300 means that the HD controller 306 creates a file on the HDD 309 using the FAT32 file system 308.

  First, the HD controller 306 creates a new file on the HDD 309 using the FAT32 file system 308 (step S1).

  Next, the ATRAC3 encoding / decoding device 303 converts the digital audio signal supplied from the audio input / output unit 400 via the digital audio I / F 301 or AD / DA I / F 302 into the ATRAC3 based on the control of the HD controller 306. The sound is compressed with high sound quality and high efficiency using a compression coding technique and supplied to the magic gate core unit 304 (step S2).

  Next, the magic gate core unit 304 encrypts the ATRAC3-compressed audio data based on the control of the HD controller 306, and supplies the encrypted audio data to the shared RAM 305 (step S3).

  Next, every time the encryption of one sound unit is completed, the HD controller 306 transfers the data stored in the shared RAM 305 to the SDRAM 307 (step S4), and further transfers it to the HDD 309 via the FAT32 file system 308. Audio data is recorded as a file in the HDD 309 (step S5).

  If the audio data of IEC60958 is recorded and the category is CD, the HD recording / reproducing apparatus 300 analyzes the C bit and U bit of the audio data, and the HDD 309 according to the CD song number. It is possible to record on.

  FIG. 11 is a flowchart for explaining a process of recording audio data in the HD recording / reproducing apparatus 300. Here, reproducing audio data using the HD recording / reproducing apparatus 300 means that the HD controller 306 opens a music file recorded on the HDD 309 and reads the data.

  First, the HD controller 306 opens a desired file to be reproduced using the FAT32 file system 308 (step S11), and reads the opened file from the HDD 309 to the SDRAM 307 (step S12).

  Next, every time decoding of one sound unit is completed in the magic gate core unit 304, the HD controller 306 transfers one sound unit from the SDRAM 307 to the shared RAM 305 (step S13).

  Next, the magic gate core unit 304 decodes the audio data supplied from the HD controller 306 via the shared RAM 305 and supplies the decoded audio data to the encoding / decoding device 303 (step S14).

  Next, the encoding / decoding device 303 decompresses the audio data supplied from the magic gate core unit 304 and supplies it to the audio input / output unit 400 via the digital audio I / F 301 or AD / DAI / F 302 (step). S15).

  In the HD recording / reproducing apparatus 300 according to an embodiment of the present invention, 500 trays (files) called albums for grouping a plurality of music (tracks) are prepared in advance. In addition to this album, ten trays (files) called “play lists” that can collect arbitrary tracks actually recorded on the HDD 309 are prepared in advance. The difference between an album and a playlist is that the former is a saucer (file) for storing the recorded music itself, while the latter has a link to the music (track) held by the former It is not a saucer (file) that holds the actual music file itself.

  The number of music files that can be recorded in one album is 400 (400 songs). This limitation on the number of tracks in the album also applies to playlists. Therefore, the HD recording / reproducing apparatus 300 can hold music of up to 200,000 songs (500 albums × 400 tracks). However, the disc reproducing apparatus 200 and the HD recording / reproducing apparatus 300 integrated dubbing apparatus to which the present invention is applied are limited to a maximum of 20,000 songs in order to guarantee comfortable music reproduction and recording.

  FIG. 12 is a branch diagram showing the structure of a file stored in the HDD 309. A music file and a database file for managing the music file are placed under a directory called HiFi under the root directory. Under the HiFi directory, an album number management file Pblist.P called an album playback list indicating the playback order of 500 albums. msf (hereinafter simply referred to as Pblist) (16 kb) is stored. In this Pblist, the file numbers of the reproduction management files of 500 albums are written. In the directory, in addition to Pblist, an album / track name database file Named.b, which is a database of album names / track names / artist names of all albums and tracks. msf (hereinafter simply referred to as Namedb), a playback time management database file Playtime. Each album can be obtained by using msf (hereinafter simply referred to as “Playtime”), the TOC of the optical disc when performing synchronized recording with the disc playback apparatus 200, and using a service such as CDDB (Compact Disc Data Base) later. , A TOC database file Tocdb. msf (hereinafter referred to as Toccdb) is stored. The directory called Album000 under the HiFi directory is an album playback management file called a playback list in which data such as the total number of tracks, album name, playback song order, and album highlight included in each of the 500 albums is stored. Pb000001. msf to Pb0001f4. msf (hereinafter simply referred to as Pb000000) is stored.

  The 100 directories from Album001 to Album100 under the HiFi directory are directories for storing recorded music files. Since a maximum of 20,000 music files can be created, if all these music files are placed in the same directory, a long time is required for the FAT32 file system 308 to search for the file location. In order to shorten this time, it is effective to distribute and store music files. For these reasons, the recorded music files are distributed and stored in 100 directories from Album001 to Album100. The music file is A3dxxxx. It has a file name of msa (hereinafter simply referred to as A3dxxxx), and serial numbers are assigned from the first to the 20,000th track.

  Finally, a Playlist directory under the HiFi directory is a directory for storing playlist management files Pb0001f5 to Pb0001fe for realizing the playlist function described above.

  FIG. 13 shows the configuration of the album number management file Pblist, and FIGS. 14A and 14B show the header and other parts of the album number management file Pblist. The album number management file Pblist has a size of one cluster (1 block = 16 KB). The header shown in FIG. 14A consists of 32 bytes. In a portion other than the header shown in FIG. 14B, a table Alb-nnn for managing the playback order of albums and a part of information in the header are recorded. The head of each of these different types of data groups is defined to be a predetermined position in the reproduction management file.

  The album number management file has a header of 32 bytes from the beginning represented by (0x0000) and (0x0010) shown in FIG. 14A. A unit divided by 16 bytes from the beginning in the file is called a slot. In the headers arranged in the first and second slots of the file, data having the following meanings, functions, and values are arranged in order from the top. Note that the data described as Reserved represents undefined data. Normally, null (0x00) is written, but the Reserved data is ignored no matter what is written. There may be changes in future versions. Also, writing to this part is prohibited.

BLKID-TL0 (4 bytes)
Meaning: BLOCKID FILE ID
Function: Value for identifying the beginning of the album number management file Value: Fixed value = “TL = 0” (for example, 0x544C2D30)

REVISION (4 bytes)
Meaning: Plist rewrite count Function: Every time the album number management file is rewritten Value: Starts from 0 and increases by +1

T-ABLE (2 bytes)
Meaning: TOTAL TRACK NUMBER
Function: Total number of albums Value: 1 to 512 (including playlist) If there is no data, set to all zeros

Alb-nnn
Meaning: SQN (sequence) number of the album to be played Function: Each album playback management file Pbxxxxxxxx. Describes the file number of msf Value: 1 to 512
All zeros when there is no album

  FIG. 15 shows the structure of an album playback management file, and FIG. 16 shows the structure of an ATRAC3 data file of 1 FILE (one song). The album playback management file is a 16 KB fixed length file. The ATRAC3 data file is composed of a leading attribute header followed by actual encrypted audio data in units of music. The attribute header also has a fixed length of 16 KB, and has a configuration similar to that of the album reproduction management file.

  The album playback management file shown in FIG. 15 includes a header, an area NM1-S for storing a 1-byte character string album name, an area NM2-S for storing a 2-byte character string album name, a song order playback table TRKTBL, and additional information INF. -S. The attribute header at the top of the data file shown in FIG. 16 includes a header, a 1-byte code song name NM1, a 2-byte code song name NM2, track key information such as track key information TRKINF, part information PRTINF, and track additional information INF. Consists of. The header includes information on the total number of parts, name attributes, size of additional information, and the like.

  The ATRAC3 audio data follows the attribute header. The audio 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 audio 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.

  With reference to FIG. 16, the relationship between a song and an ATRAC3 data file will be described. One track means one song. One song is composed of one ATRAC3 data file (see FIG. 16). The ATRAC3 data file is audio data compressed by ATRAC3. Information is recorded on the HDD 309 in units called clusters. One cluster has a capacity of 16 KB, for example. Multiple files are not mixed in one cluster.

  One song is basically composed of one part, but if editing is performed, one song may be composed of a plurality of parts. A part means a unit of data recorded within a continuous time from the start of recording to the stop thereof, and usually one track is composed of one part. The connection of the parts in the music is managed by the part information PRTINF in the attribute header of each music. That is, the part size is represented by 4-byte data called the part size PRTSIZE in PRTINF. The first 2 bytes of the part size PRTSIZE indicate the total number of clusters held by the part, and each subsequent 1 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 part description method, it is possible to eliminate the movement of a large amount of audio data that is normally required when editing audio data. If the editing is limited to the block unit, the movement of the audio data can be similarly avoided. However, the editing unit of the block unit is too large compared to the SU unit.

  SU is the minimum unit of parts, and is the minimum data unit when audio data is compressed by ATRAC3. The SU is data of several hundred bytes obtained by compressing audio data of 1024 samples (1024 × 16 bits × 2 channels) obtained at a sampling frequency of 44.1 kHz to about 1/10. One SU is about 23 milliseconds in terms of time. Usually, one part is composed of thousands of SUs. When one cluster is composed of 42 SUs, a sound of about 1 second can be represented by one cluster. The number of parts constituting one track is affected by the additional information size. Since the number of parts is determined by the number of headers, music titles, additional information data, etc. removed from one block, a state where there is no additional information is a condition for using the maximum number (645) of parts.

  FIG. 17A shows a file structure in the case where two pieces of audio data from a CD or the like are recorded continuously. The first song (file 1) is composed of, for example, 5 clusters. Between the first song and the second song (file 2), two files cannot be mixed in one cluster, so file 2 is created from the beginning of the next cluster. Therefore, the end of the part 1 corresponding to the file 1 (end of the first music piece) 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.

  As the track editing operations, six types of operations are defined: track divide, track combine, track erase, track move, track name addition, and track artist name addition. Divide is to divide one track into two. When the divide is performed, the total number of tracks increases by one. The divide file is divided into two files on the file system, and the reproduction management file and FAT are updated. Combine is to combine two tracks into one. When combined, the total number of tracks decreases by one. Combine combines two files on the file system into one file, and updates the playback management file and FAT. Erase is to erase a track. The track number after deletion is reduced by one. Move is to change the track order. As described above, the reproduction management file and the FAT are also updated for the erase and move processing. Adding a track name is to add a track name to the track. The addition of the artist name of the track is to give the artist name to the track.

  FIG. 17B shows the result of combining the two songs (file 1 and file 2) shown in FIG. 17A. The combined result is a single file, which consists of two parts. FIG. 17C shows the result of dividing one song (file 1) in the middle of cluster 2. Due to the divide, a file 1 consisting of clusters 0 and 1 and the front side of cluster 2 and a file 2 consisting of the rear side of cluster 2 and clusters 3 and 4 are generated.

  As described above, in this embodiment, since there is a description method regarding parts, in FIG. 17B that is a result of the combination, the start position of part 1, the end position of part 1, the start position of part 2, the end of part 2 Each position can be defined in SU units. As a result, it is not necessary to move the audio data of part 2 in order to close the gap between the joint results. In addition, since there is a description method related to parts, it is not necessary to move data so as to fill the empty space at the head of file 2 in FIG.

  Further, as an album editing operation, erasing an album, moving an album, adding an album name, adding an artist name of the album, and the like are defined. To erase an album is to erase the album. The album number after being erased decreases by one. The move of the album is to change the order of the album. Also for the erase and move process, the album number management file and the FAT are updated. Adding an album name is to add an album name to the album. The addition of the artist name of the album is to give the artist name to the album.

  FIG. 18 shows a more detailed data structure of the album reproduction management file, and FIGS. 19A and 19B show a header and other parts constituting the album reproduction management file, respectively. The album reproduction management file has a size of one cluster (1 block = 16 KB). The header shown in FIG. 19A consists of 32 bytes. 12B includes a name NM1-S (256 bytes), a name NM2-S (512 bytes), CONTENTSKEY, C_MAC [0], S-YMDhms, and a table TRKTBL (800 bytes) for managing the reproduction order. ), Additional information INF-S (14720 bytes) and finally a 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 a predetermined position in the reproduction management file.

  The album reproduction management file has a header of 32 bytes from the beginning represented by (0x0000) and (0x0010) shown in FIG. 19A. A unit divided by 16 bytes from the beginning in the file is called a slot. In the headers arranged in the first and second slots of the file, data having the following meanings, functions, and values are arranged in order from the top. Note that the data described as Reserved represents undefined data. Normally, null (0x00) is written, but the Reserved data is ignored no matter what is written. There may be changes in future versions. Also, writing to this part is prohibited. When the part written as Option is not used, it is all handled in the same manner as Reserved.

BLKID-TL0 (4 bytes)
Meaning: BLOCKID FILE ID
Function: Value for identifying the beginning of the reproduction management file Value: Fixed value = “TL = 0” (for example, 0x544C2D30)
MCode (2 bytes)
Meaning: MAKER CODE
Function: Code that identifies the manufacturer and model of the recorded device Value: Upper 10 bits (maker code) Lower 6 bits (model code)
REVISION (4 bytes)
Meaning: Number of times the album playback management file is rewritten Function: Incremented each time the album playback management file is rewritten Value: Starts from 0 and increases by 1

SN1C + L (2 bytes)
Meaning: Indicates the attribute of the title (1 byte) of the album written in the NM1-S area. Function: Indicates the character code and language code to be used with 1 byte each. Value: The character code (C) is the upper 1 byte. To distinguish characters
00: No character code is set. Treat as a simple binary number
01: ASCII (American Standard Code for Information Interchange)
02: ASCII + KANA 03: modifided8859-1
81: MS-JIS 82: KS C 5601-1989 83: GB (Great Britain) 2312-80
90: S-JIS (Japanese Industrial Standards) (for Voice).

The language code (L) is the low-order byte and distinguishes languages according to the EBU Tech 3258 standard as shown below.
00: Not set 08: German 09: English 0A: Spanish
0F: French 15: Italian 1D: Dutch
65: Korean 69: Japanese 75: Chinese
Set to zero when there is no data.

SN2C + L (2 bytes)
Meaning: Indicates the attribute of the album title (2 bytes) written in the NM2-S area Function: Indicates the character code and language code to be used in 1 byte each Value: Same SINFSIZE as SN1C + L described above (2 bytes)
Meaning: Represents the total size of all additional data written in the INF-S area. Function: Describes the data size in units of 16 bytes. If there is no data, be sure to set it to all zeros. Value: From 0x0001 0x39C (924)
T-TRK (2 bytes)
Meaning: TOTAL TRACK NUMBER
Function: Total number of tracks Value: 1 to 0x0190 (maximum 400 tracks), all zeros when there is no data

Data (FIG. 19B) written in the area following the header described above will be described below.

NM1-S
Meaning: 1-byte character string Album name storage area Function: Variable-length name data expressed in 1-byte character code (256 at maximum)
The end of the name data must be written with the end code (0x00). The size should be calculated from this end code. If there is no data, at least the first (0x0020) and null (0x00) should be recorded. Various character codes NM2-S
Meaning: Area storing the 2-byte character string album name Function: Variable-length name data expressed in 2-byte character code (maximum 512)
The end of the name data must be written with the end code (0x00). The size should be calculated from this end code. If there is no data, at least the first (0x0120) and null (0x00) should be recorded. Various character codes.

CONTENTS KEY
Meaning: The value prepared for each song is protected by MG (R) and then stored. Here, the same value as the CONTENTS KEY attached to the first song Function: A key required for calculating the MAC of S-YMDhms Value: MAC from 0 to 0xFFFFFFFFFFFFFFFF
Meaning: Copyright information alteration check value Function: Value created from S-YMDhms content and CONTENTS KEY Value: From 0 to 0xFFFFFFFFFFFFFFFF.

TRK-nnn
Meaning: SQN (sequence) number of the ATRAC3 data file to be played Function: Describes FNo in TRKINF Value: 1 to 400 (0x190)
Set to zero when there is no track. INF-S
Meaning: Album additional information (for example, additional information such as artist name)
Function: Variable-length additional information data with header Multiple different additional information may be arranged. Each has an ID and data size. Additional information data including individual headers is composed of an integral multiple of 4 bytes with a minimum of 16 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 on a device with a reliable clock Function: A value to identify the last recorded date and time, mandatory for EMD Value: 25 to 31 bits Year 0 to 99 ( (1980-2079)
21-24 bits month 0-12
16-20 bits day 0-31
11 to 15 bits 0-23
05-10 bits min 0-59
00 to 04 bits Seconds 0 to 29 (in units of 2 seconds).

  As the last slot of the reproduction management file, the same BLKID-TL0, MCode, and REVISION as those in the header are written.

  As a consumer audio device, a memory card may be removed during recording or the power may be cut off, and it is necessary to detect the occurrence of these abnormalities when the memory card is restored. As described above, REVISION is written at the beginning and end of the block, and each time this value is rewritten, it is incremented by +1. If an abnormal end occurs in the middle of a block, the values of the REVISION at the beginning and end do not match, and the abnormal end can be detected. Since there are two REVISIONs, abnormal termination can be detected with high probability. When an abnormal end is detected, a warning such as an error message is generated.

  In addition, since the fixed value BLKID-TL0 is inserted at the beginning of one block (16 KB), the fixed value can be used as a guideline for restoration when the FAT is broken. That is, the file type can be determined by looking at the fixed value at the beginning of each block. Moreover, since the fixed value BLKID-TL0 is described twice in the header of the block and the end portion of the block, the reliability of the fixed value BLKID-TL0 can be checked. The same album reproduction management file 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 is assigned a block number BLOCK SERIAL as will be described later. However, since the ATRAC3 data file usually has a plurality of files on the HDD 309, if the contents are distinguished by CONNUM0 and BLOCK SERIAL is not attached, duplication occurs and the file of the FAT file is broken. Recovery becomes difficult. In other words, a single ATRAC3 data file is composed of a plurality of BLOCKs and may be arranged in a discrete manner. Therefore, CONNUM0 is used to discriminate BLOCKs constituting the same ATRAC3 data file and the same. The ascending / descending order in the ATRAC3 data file is determined by the block number BLOCK SERIAL.

  Similarly, if the FAT is not destroyed, but the logic is inadvertently inconvenient as a file, the manufacturer code (MCode) is placed at the beginning and end of the block so that the manufacturer's model can be specified. It is recorded.

  FIG. 19C shows the configuration of 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 head of additional information data Value: 0x69
ID
Meaning: Additional information key code Function: Indicates the classification of additional information Value: 0 to 0xFF
SIZE
Meaning: Size of individual additional information Function: Data size is free, but it must be an integer multiple of 4 bytes. It must be at least 16 bytes. If there is a remainder from the end of the data, fill it with null (0x00) Value: 16 to 14784 (0x39C0)
MCode
Meaning: MAKER CODE
Function: Code that identifies the manufacturer and model of the recorded device Value: Upper 10 bits (maker code) Lower 6 bits (model code)
C + L
Meaning: Indicates the attribute of the character written in the data area from the 12th byte from the beginning Function: Indicates the character code and language code to be used in 1 byte each Value: DATA same as the above SNC + L
Meaning: Individual additional information data Function: Expressed as variable-length data. The beginning of the actual data always starts from the 12th 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 by content.

  FIG. 20 shows a data array of the ATRAC3 data file A3Dnnnn when 1 SU is N bytes (for example, N = 384 bytes). FIG. 20 shows an attribute header (1 block) of the data file and an audio data file (1 block). In FIG. 20, the first byte (0x0000 to 0x7FF0) of each slot of the two blocks (16 × 2 = 32 Kbytes) is shown. As shown separately in FIG. 21, the first 32 bytes of the attribute header are the header, 256 bytes are the song title area NM1 (256 bytes), and 512 bytes are the song 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 the ATRAC3 data file Value: Fixed value = “HD = 0” (for example, 0x48442D30)
MCode (2 bytes)
Meaning: MAKER CODE
Function: Code that identifies the manufacturer and model of the recorded device Value: Upper 10 bits (maker code) Lower 6 bits (model code)
BLOCK SERIAL (4 bytes)
Meaning: Sequential number assigned to each track Function: The beginning of a block starts from 0 and the next block is incremented by +1. Even if edited, the value does not change. Value: Starts from 0 to 0xFFFFFFFF.

N1C + L (2 bytes)
Meaning: Indicates the attribute of track (song title) data (NM1) Function: Indicates the character code and language code used for NM1 in 1 byte each Value: Same as SN1C + L N2C + L (2 bytes)
Meaning: Indicates the attribute of the track (song title) data (NM2) Function: Indicates the character code and language code used for NM2 in 1 byte each Value: Same SIZESIZE as SN1C + L (2 bytes)
Meaning: Indicates the total size of all additional information related to the track. Function: Describes the data size in units of 16 bytes. If there is no data, be sure to set all zeros. Value: Size ranges from 0x0000 to 0x3C6 (966)
T-PRT (2 bytes)
Meaning: Total number of parts Function: Indicates the number of parts that make up the track. Usually 1
Value: 1 to 0x285 (645dec)
T-SU (4 bytes)
Meaning: Total number of SUs Function: Indicates the actual total number of SUs in a track. Value corresponding to the performance time of the song: 0x01 to 0x001FFFFF
INX (2 bytes) (Option)
Meaning: Relative location of INDEX Function: Pointer indicating the beginning of the rust part (characteristic part) of the song. The position from the beginning of the song is specified by a number that is 1/4 of the number of SUs. This is equivalent to 4 times longer than normal SU (approximately 93 ms). Value: 0 to 0xFFFF (maximum, approximately 6084 seconds)
XT (2 bytes) (Option)
Meaning: INDEX playback time Function: 1/4 the number of SUs to be played from the beginning specified by INX-nnn
Specify the number. This is equivalent to 4 times longer than normal SU (approximately 93 ms) Value: 0x0000: No setting 0x01 to 0xFFFE (maximum 6084 seconds)
0xFFFF: Until the end of the song.

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

NM1
Meaning: Character string representing song name Function: Variable-length song name represented by a 1-byte character code (256 at maximum)
The end of the name data must be written with the end code (0x00). The size should be calculated from this end code. If there is no data, at least the first (0x0020) and null (0x00) should be recorded. Various character codes NM2
Meaning: Character string representing song name Function: Variable-length name data represented by 2-byte character code (maximum 512)
The end of the name data must be written with the end code (0x00). The size should be calculated from this end code. If there is no data, at least the first (0x0120) and null (0x00) should be recorded. Various character codes.

The 80-byte data starting from the fixed position (0x320) of the attribute header is called a track information area TRKINF, and mainly manages information related to security and copy control. FIG. 22 shows the TRKINF part. TRKINF
These data will be described below according to the arrangement order.

CONTENTS KEY (8 bytes)
Meaning: A value prepared for each song, which is protected after being protected by MG (R). Function: When playing a song, it is the first key required. Value used for MAC calculation: 0 to 0xFFFFFFFFFFFFFFFF C_MAC [0] (8 bytes)
Meaning: Copyright information alteration check value

WM
Meaning: Water Mark
Function: Indicates the Water Mark status of content

A (1 byte)
Meaning: Part attribute Function: Indicates information such as compression mode in the part Value: Explained below with reference to FIG. 23. However, for monaural signals with N = 0, 1, bit 7 is 1 and sub signal is 0, main A special joint mode of only the signal (L + R) is defined as monaural. The information of bits 2 and 1 may be ignored by a normal player.

  Bit 0 of A forms emphasis on / off information, bit 1 forms information of reproduction SKIP or normal reproduction, and bit 2 other than data section, for example, audio data, FAX, etc. The information of the data is formed. Bit 3 is undefined. By combining the bits 4, 5, and 6, the mode information of ATRAC3 is defined as shown. That is, N is the value of the mode represented by these 3 bits, and is mono (N = 0, 1), LP (N = 2), SP (N = 4), EX (N = 5), HQ ( The recording time, the data transfer rate, and the number of SUs in one block are shown for the five modes (N = 7). The number of bytes of 1 SU is (mono: 136 bytes, LP: 192 bytes, SP: 304 bytes, EX: 384 bytes, HQ: 512 bytes). Further, bit 7 indicates the mode of ATRAC3 (0: Dual 1: Joint).

LT (1 byte)
Meaning: Playback restriction flag (bits 7 and 6) and security version (bits 5 to 0)
Function: Indicates that there is a restriction on this track Value: Bit 7: 0 = No restriction 1 = Restriction Bit 6: 0 = Within deadline 1 = Expired Bit 5 to Bit 0: Security version 0 (if other than 0) (Reproduction prohibited)
FNo (2 bytes)
Meaning: File number Function: Track number when first recorded, and this value specifies the position of the value for MAC calculation recorded in the hidden area in the memory card Value: 1 to 0x190 (400)
MG (D) SERIAL-nnn (16 bytes)
Meaning: Serial number of the security block (security IC 20) of the 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 and 4.2 billion songs are prepared, and used to identify the recorded songs Value: 0 to 0xFFFFFFFF.

YMDhms-S (4 bytes) (Option)
Meaning: Playback start date and time of a track with playback restrictions Function: Date and time permitted to start playback specified by EMD Value: YMDhms-E (4 bytes) same as the date and time notation described above (Option)
Meaning: Playback end date and time of playback-restricted track Function: Date and time when playback permission ends specified by EMD Value: Same MT (1 byte) (Option)
Meaning: Maximum number of permitted playbacks Function: Maximum number of playbacks specified by EMD Value: 1 to 0xFF 0x00 when not used
When the value of bit 7 of LT is 0, the value of MT should be 00. CT (1 byte) (Option)
Meaning: Number of playbacks Function: Number of times that playback can actually be performed within the permitted number of playbacks. Decrement each time playback value: 0x00 to 0xFF 0x00 when not used. When bit 7 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. 24, the copy control information is represented by bits 6 and 7,
Bits 4 and 5 represent copy control information for high-speed digital copying, and bits 2 and 3 represent the security block authentication level. Bits 0 and 1 are undefined CC example: (bit 7, 6) 11: Permit unlimited copy, 01: Prohibit copy, 00: Permit one copy (bit 3, 2) 00: Analog or digital input Recording from MG, MG authentication level is 0. In digital recording from CD, (bit7, 6) is 00, (bit3, 2) is 00 CN (1 byte) (Option)
Meaning: High speed serial copy management HSCMS
Number of permitted copies in System) Function: Expanded the distinction between copying once and copying free, and specifies the number of times. Valid only for copy 1st generation, subtracted for each copy Value: 00: Copy prohibited, 01 to 0xFE: Number of times, 0xFF: Unlimited number of times.

Following the track information area TRKINF described above, 2 starting from 0x0370
The 4-byte data is called a parts information area PRTINF for parts management. When one track is composed of a plurality of parts, the PRTINFs are arranged in the order of the time axis. FIG. 25 shows the PRTINF portion. The data in PRTINF 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 (most significant), start SU: 1
Byte (upper), end SU: 1 byte (lowest)
Value: Cluster: 1 to 0x1F40 (8000), start SU: 0 to 0xA0
(160), end SU: 0 to 0xA0 (160) (however, SU is counted as 0
, 1, 2, and 0)
PRTKEY (8 bytes)
Meaning: Value for encrypting parts Function: Initial value = 0, obey editing rules when editing Value: 0 to 0xFFFFFFFFFFFFFFFF
CONNUM0 (4 bytes)
Meaning: Initially created content accumulation number key Function: Role of ID for making content unique Value: Same value as content accumulation number initial value key.

The attribute header of the ATRAC3 data file includes additional information INF as shown in FIG. This additional information is the additional information INF-S in the reproduction management file (see FIGS. 18 and 19B), except that the start position is not fixed.
Is the same. The data of the additional information INF starts with the next position after the last byte part (in units of 4 bytes) of one or more parts as a start position.

INF
Meaning: Additional information data about the track Function: Additional information data of variable length with header. A plurality of different additional information may be arranged. An ID and a data size are added to each. The additional information data including individual headers is the same as the additional information INF-S in the reproduction management file.

The data of each block of the ATRAC3 data file follows the attribute header described above. As shown in FIG. 26, 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, 0x41334420)
MCode (2 bytes)
Meaning: MAKER CODE
Function: Code that identifies the manufacturer and model of the recorded device Value: Upper 10 bits (maker code) Lower 6 bits (model code)
CONNUM0 (4 bytes)
Meaning: Initially created content accumulation number Function: Role of ID to make content unique, value does not change even if edited Value: BLOCK SERIAL (4 bytes) that is the same value as the content accumulation number initial value key )
Meaning: Sequential number assigned to each track Function: Start of block starts from 0 and next block increments by +1 Does not change value even if edited Value: BLOCK-SEED (starting from 0 to 0xFFFFFFFF) (8 bytes)
Meaning: One key for encrypting one block Function: The beginning of the block generates a random number in the security block of the recording device, and the subsequent block is a value incremented by +1. Since no sound can be produced for about 1 second, the same thing is written twice at the end of the header and block. Value is not changed even if edited Value: Initially 8 bytes random number 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, and the next block is the last encrypted 8-byte value of the last SU. Start S in the middle of a divided block
Use the last 8 bytes immediately before U. Does not change value even if edited Value: 0 to 0xFFFFFFFFFFFFFFFF
SU-nnn
Meaning: Sound unit data Function: Compressed data from 1024 samples, the number of bytes output differs depending on the compression mode. Even if edited, the value does not change (for example, in SP mode, N = 384 bytes)
Value: ATRAC3 data value.

  In FIG. 20, since N = 384, 42 SU is written in one block. In addition, the first two slots (4 bytes) of one block are used as headers, and BLKID-A3D, MCode, CONNUM0, and BLOCK SERIAL are written twice in the last slot (2 bytes). Therefore, the remaining area M bytes of one block is (16,384-384 × 42−16 × 3 = 208 (bytes). As described above, 8 bytes of BLOCK SEED are recorded twice. Is done.

  Using the album number management file, album playback management file, and music file described above, the playback order of albums 1 to 500, the playback order of music (tracks) included in each album, the acquisition of recordable tracks, and the album name of each album It is possible to obtain the track name of each track, the artist name of each album / track, the total performance time of each album, and the performance time of each track. However, these pieces of information need to be read by actually opening the files stored in the HDD 309 one by one, and a comfortable operating environment cannot be obtained as a system. Therefore, in addition to the above-mentioned files, an album / track name database file Namedb and a playback time management database file Playtime are created under the HiFi directory so that the above information is stored in a database and the desired information can be quickly acquired. Yes. These files are described below.

  FIG. 27 shows the structure of the album / track name database file Namedb. This Namedb is a file for quickly searching for the names (album, song name, artist name) registered in the name fields NM1, NM2 and additional information INF (artist name) of Pblist, Pbxxxxxxxx, A3dxxxx. Only the name is recorded. Namedb is composed of 9 album name blocks and 323 song name blocks (1 block 16 kb).

  Each block (16 kb) is composed of one BLK record (8 bytes fixed length) and 62 name records (264 bytes fixed length (62 records)). Therefore, although 558 (= 62 × 9) can be recorded in the name record of the album name block, in one embodiment of the present invention, up to 510 is valid, and thereafter the invalid data (fixed to 0x00) is assumed. The name record of the song name block can be recorded as 200026 (= 323 × 62), but in one embodiment of the present invention, up to 20000 is valid, and thereafter the invalid data (fixed to 0x00). The file size is 332 blocks × 16384 (16 kb) = 5439488 bytes (5312 kb).

  FIG. 28 shows the structure of a BLK record. The BLK-ID (4 bytes) is an “ANMO” fixed character string in the album name block, and a “TNMO” fixed character string in the song name block. The block serial number (4 bytes) is a serial number starting from 1.

  FIG. 29 shows the structure of the name record. Records are recorded in the order of album file numbers 1 to 500 and in order of music file numbers 1 to 20000. Note that the album / song file number 0 is invalid data.

  FIG. 30 shows the structure of the playback time management database file Playtime. This Playtime is a file for making it possible to obtain the total performance time for each album at a high speed, and the performance time for each song is recorded in this file. In addition, an index and TNO associated with TOC information in a TOC database described later are recorded. This Playtime is composed of 15 blocks (1 block 16 kb).

  Each block (16 kb) is composed of one BLK record (8-byte fixed length), 1365 TRK records (12-byte fixed length (1365)), and a reserved record (4-byte fixed length (fixed 0x00)). Therefore, although 20475 (= 1365 × 15) can be recorded in the TRK record, in one embodiment of the present invention, up to 20000 is valid, and thereafter, invalid data (fixed to 0x00). The file size is 15 blocks × 16384 = 245760 bytes (240 kb).

  FIG. 31 shows the configuration of the BLK record portion of the record format. The BLK-ID is a “TRKO” fixed character string, and the block serial number is a serial number from 1.

  FIG. 32 shows the structure of a TRK record. Records are recorded in the order of music file numbers 1 to 20000. Here, an album file number of 0 is invalid data. Since the album file number of the playlist is not set, the total performance time of the playlist is Pbnnnnnn. It is calculated by obtaining a TRK record from a reproduction order file number in MSF (nnnnnn: 0001F5 to 0001FE).

  The dubbing apparatus according to the embodiment of the present invention can perform synchronous recording (synchronized recording) from the disk playback apparatus 200 as a playback source to the HD recording / playback apparatus 300 as a recording destination. Before starting the synchronous recording, the HD recording / reproducing apparatus 300 requests the disc reproducing apparatus 200 to transmit the TOC data of the CD to be reproduced. In addition to the system control signal shown in FIG. 1, an IEC60958 audio signal is input to the HD recording / reproducing apparatus 300, and the data request method is included in the U bit of the audio signal using the digital in-interface circuit of the HD recording / reproducing apparatus 300. There is a way to analyze the information that is being processed. By storing the TOC information of the playback source CD in a database file, when connecting to a site where CD information such as CDDB can be obtained later, the album / track recorded in the HD recording / playback apparatus 300 is stored. Be able to name it. A database file for this role is Tocdb.

  FIG. 33 shows the structure of the TOC database file Tocdb. The TOC database file Tocdb is a file for assigning an album name and a track name to an album and a track recorded on the HD recording / reproducing apparatus 300 using a site on the Internet such as CDDB. Specifically, TOC information for searching CDDB or the like is recorded. The system controller 100 accesses a site on the Internet such as CDDB via an external device connected to the external control signal input / output unit 500, for example, a personal computer.

  The file name is Tocdb, and this file is composed of 13 blocks (1 block 16 kb). Each block (16 kb) is composed of a BLK record (8 bytes fixed length), an ALBUM TOC record (412 bytes fixed length (39 records)), and a reserved record (308 bytes fixed length (0x00 fixed)). The ALBUM TOC record can be recorded 507 (= 39 × 13). However, in one embodiment of the present invention, up to 500 is valid, and thereafter, invalid data (fixed to 0x00) is assumed. The file size is 13 blocks × 16384 = 221292 bytes (208 kb).

  FIG. 34 shows the structure of a block record. BLK-ID is a “TOCO” fixed character string, and the block serial number is a serial number from 1. The number of albums is the number of ALBUM TOC records (1 to 500).

  FIG. 35 shows the structure of the Album TOC record. As shown in FIG. 35, the Album TOC record includes a TOC DB IDX, a usage state, and TOC information.

  FIG. 36 shows details of the TOC information. As shown in FIG. 36, the TOC information includes Trk No. (1 byte), AMIN (1 byte), ASEC (1 byte), and AFRAME (1 byte). Trk No. Is a track number, which is a number from 1 to 20000. AMIN, ASEC, and AFRAME are Trk No. Are the absolute time component, absolute time second component, and absolute time frame number of the track corresponding to the track number recorded in.

  The Toccdb ALBUM TOC record and the Playtime TRK record portion (TOCDB IDX, TOC TNO) are mutually related. That is, the track information of Playtime can know which TOC TNO in the Toccdb corresponds to the TOC. For this reason, the correct song name can be acquired from the CDDB even if the audio file is edited or deleted.

  As described above, the HD recording / reproducing apparatus 300 according to the embodiment of the present invention can perform an editing operation. Editing operations include song divide, song combine, song erase, album erase, song move, album move, album name, album artist name, song ( Track name addition and artist name addition of music (track). After these editing operations, the database except for Tocdb is always updated for each editing, and these databases are managed so that there is no difference between the entity and the database.

  FIG. 37 is a block diagram illustrating an example of the structure of the voice input / output unit 400. As shown in FIG. 37, the audio input / output unit 400 includes an A / D converter 401, a DA converter 402, an analog input terminal 403, a digital input terminal 404, a digital output terminal 405, and an analog output terminal 406.

  The AD converter 401 converts the analog signal supplied from the analog input terminal 403 into a serial signal synchronized with the LR clock and the bit clock, and supplies the serial signal to the AD / DA I / F 302 provided in the HD recording / reproducing apparatus 300.

  The DA converter 402 DA-converts the audio data supplied from the disk playback device 200 or the HD recording / playback device 300, for example, audio data in the IEC60958 format, and supplies the analog output terminal 406 with the DA. The DA converter 402 not only outputs audio data, but also silences the audio data when instructed by the disk playback device 200 or the HD recording / playback device 300.

  The analog input terminal 403 is a terminal for inputting an analog signal, and the analog signal supplied to the analog input terminal 403 is supplied to the AD converter 401.

  The digital input terminal 404 is a terminal for inputting a digital signal, and the digital signal input to the digital input terminal 404 is supplied to a digital audio I / F 301 provided in the HD recording / reproducing apparatus 300.

  Note that the audio signal input to the HD recording / reproducing apparatus 300 is output from an analog output terminal 406 described later as a monitor sound when the HD recording / reproducing apparatus 300 is in a recording state.

  The digital output terminal 405 is a terminal for outputting a digital audio signal supplied from the digital audio I / F 301 provided in the HD recording / reproducing apparatus 300 to an external device or the like.

  The analog output terminal 406 is a terminal for outputting the analog signal supplied from the DA converter 402 to an external device or the like.

  The external control signal input / output unit 500 is for enabling communication between an external device such as a personal computer and a dubbing apparatus, and is, for example, a USB (Universal Serial Bus) connector.

  In the dubbing device according to the embodiment of the present invention, the music (track) is registered in the playlist by pressing the playlist registration key provided in the operation device 103 and then using the jog key or the like. This is possible by selecting music (track) and a playlist to which the music (track) is registered. In the dubbing apparatus according to the embodiment of the present invention, the music (track) being played back can be easily registered in the playlist. The playlist registration method will be described below.

  FIG. 38 is a flowchart for explaining an example of the registration operation and processing for registering the music (track) being reproduced in the playlist. Here, an example is shown in which track 2 of album 2 (album 2 playback management file) is registered in playlist 2 (playlist 2 management file).

  First, the jog keys provided in the operation device 103 are appropriately operated to reproduce the track 2 of the album 2 (step 21).

  Next, the play list registration key provided in the operation device 103 of the system controller 100 is pressed (step 22). Thereby, registration to the playlist is started, and a display “registration destination playlist?” Prompting the user to select a playlist registration destination file is displayed on the display device 102 of the system controller 100 (step 23).

  Next, using the operation device 103 of the system controller 100, the playlist 2 is selected as the registration destination playlist (step 24). Thereby, the information of the playlist 2 management file Pb0001f6 is updated (step 25), and the playlist registration operation and processing are ended.

  In the above-described registration method, the example in which the user selects the registration destination playlist has been described. However, the registration destination playlist may be selected in advance by default. In this way, in step 22, after pressing the playlist registration key provided in the system controller 100, for example, by pressing the playlist registration key provided in the system controller 100 again, the music being played back (Track) can be registered in the playlist. In other words, the music (track) to be registered in the playlist can be reproduced and the reproduced music (track) can be easily registered in the playlist simply by pressing the playlist registration key twice.

  Further, in addition to the function for starting registration in the playlist, a function for registering the music (track) being played back in the playlist may be added to the playlist registration key. By giving such a function to the playlist registration key, it is possible to easily register the music (track) being played back in the playlist with a single press of the playlist registration key. .

  Next, an editing operation of the dubbing apparatus according to one embodiment of the present invention will be described. As described above, the dubbing apparatus according to the embodiment of the present invention can edit the audio data stored in the HD recording / reproducing apparatus 300. Here, operations of track erase, combine, divide, and album erase will be described as editing operations.

  FIG. 39 is a table showing album numbers and the number of tracks included in each album before the editing operation. 39, albums (Album) 1, 2,..., 500 are the album 1 management file, album 2 management file,..., Album 500 management file shown in FIG. Show.

  FIG. 40 is a table showing the link destinations of the tracks registered in each play list before the editing operation. In FIG. 40, playlists (P.List) 501, 502,..., 510 are playlist 1 management file, playlist 2 management file,. Indicates a management file.

  FIG. 41 is a flowchart for explaining the operation and processing of the track erase in the dubbing apparatus according to the embodiment of the present invention. Here, the case where the music (track) corresponding to album number 3 and track number 4 is erased is shown as an example. Note that music (tracks) corresponding to album number 3 and track number 4 is registered in track 4 of playlist 502.

  First, the user presses a menu key provided on the operation device 103, displays a menu screen on the display device 102, and selects track erase from the menu screen (step S31).

  Next, the user appropriately operates a jog key provided in the operation device 103, and inputs the album number and track number of the track for which track erasure is desired (step S32). Here, album number 3 and track number 4 are input.

  Next, in step S32, the controller 101 determines whether or not the track corresponding to the input album number and track number is registered in the playlist (step S33). If it is determined that it is not registered in the playlist, the process proceeds to step S36. If it is determined that the track is registered in the playlist, the display device 102 displays a warning “Registered in the playlist” to warn the user that the track desired to be erased is registered in the playlist. Is displayed (step S34).

  Next, the controller 101 determines whether or not an erase instruction has been confirmed by the user based on a signal supplied from the controller device 103 (step S35). If the erase instruction has not been finalized, the erase operation and processing ends. When the erase instruction is confirmed, the track corresponding to the album number and the track number input in step S32 and the track information registered in the track 4 of the playlist 502 are erased (step S36).

  FIG. 42 is a table showing the link destinations of the tracks registered in each play list after the erase operation. As shown in FIG. 42, the track 4 of the playlist 502 shown in FIG. 40 is erased by the erase operation described above.

  FIG. 43 is a flowchart for explaining the combine operation and processing in the dubbing apparatus according to the embodiment of the present invention. Here, a case where a track corresponding to album number 23 and track number 1 and a track corresponding to album number 23 and track number 18 are combined is shown as an example. The tracks corresponding to album number 23 and track number 18 are registered in track 1 of playlist 501 and track 2 of playlist 502.

  First, the user presses a menu key provided in the operation device 103, displays a menu screen on the display device 102, and selects a combine operation from the menu screen (step S41).

  Next, the user appropriately operates the jog key provided in the operation device 103, and inputs the album number and track number of the track for which the combine operation is desired (step S42). Here, album number 3 and track number 4 and album number 23 and track number 18 are input.

  Next, the controller 101 determines whether or not the track corresponding to the input album number and track number is registered in the play list in step S42 (step S43). If it is determined that it is not registered in the playlist, the process proceeds to step S46. If it is determined that it is registered in the playlist, the display device 102 warns the user that the track for which the combine operation is desired is registered in the playlist. Is displayed (step S44).

  Next, the controller 101 determines whether or not the combine instruction has been confirmed by the user based on the signal supplied from the controller device 103 (step S45). If the combine instruction has not been finalized, the combine operation and processing ends. When the combine instruction is confirmed, the track corresponding to the album number and the track number input in step S42 is combined, the track information registered in the track 1 of the playlist 501 and the track 1 of the playlist 502 are combined. The information of the track registered in (1) is deleted (step S46).

  FIG. 44 is a table showing the link destinations of tracks registered in each playlist after the combine operation. As shown in FIG. 44, the track 1 of the playlist 501 and the track 1 of the playlist 502 shown in FIG. 40 are deleted by the combine operation.

  FIG. 45 is a flowchart for explaining the division operation and processing in the dubbing apparatus according to the embodiment of the present invention. Here, a case where a track corresponding to album number 1 and track number 1 is divided is shown as an example. The track corresponding to the album number and track number 1 is registered in track 3 of playlist 502 and track 1 of playlist 510.

  First, the user presses a menu key provided on the operation device 103, displays a menu screen on the display device 102, and selects a divide operation from the menu screen (step S51).

  Next, by appropriately operating the jog key provided on the operation device 103 that desires the divide, the track corresponding to the album number 1 and the track number 1 that the user desires to operate is reproduced, and the point where the divide is desired is determined. Simultaneously with playback, press the jog key. (Step S52).

  Next, the controller 101 determines whether or not the track corresponding to the input album number and track number is registered in the playlist in step S52 (step S53). If it is determined that it is not registered in the playlist, the process proceeds to step S56. If the display device 102 determines that it is registered in the playlist, the display device 102 displays a message “Registered in the playlist” that warns the user that the track desired to be divided is registered in the playlist. It is displayed (step S54).

  Next, the controller 101 determines whether or not the divide instruction is confirmed by the user based on the signal supplied from the controller device (step S55). If the divide instruction is not finalized, the editing process ends. When the divide instruction is confirmed, the track is divided at the point instructed in step S52, and the track information registered in the track 4 of the playlist 502 and the track registered in the track 1 of the playlist 510 are checked. The information is erased (step S56).

  FIG. 46 is a table showing the link destinations of tracks registered in each playlist after the divide operation. As shown in FIG. 46, the track 4 in the playlist 502 and the track 1 in the playlist 510 shown in FIG. 40 are erased by the above-described divide operation.

  FIG. 47 is a flowchart for explaining the operation and processing of album erase editing in the dubbing apparatus according to one embodiment of the present invention. Here, the case where the album 47 is erased is shown as an example. Note that track 4 of album 47 and 128 of album 47 are registered in track 2 of playlist 505 and track 4 of playlist 510, respectively.

  First, the user presses a menu key provided in the operation device 103, displays a menu screen on the display device 102, and selects an album erase from the menu screen (step S61).

  Next, the user appropriately operates a jog key provided in the operation device 103, and inputs the album number of the album for which album erasure is desired (step S62). Here, the album number 47 is input.

  Next, in step S62, the controller 101 determines whether or not the track corresponding to the input album number and track number is registered in the playlist (step S63). If it is determined that it is not registered in the playlist, the process proceeds to step S66. If it is determined that the track is registered in the playlist, the display device 102 warns the user that the track desired to be erased is registered in the playlist. “Registered in playlist” Is displayed (step S64).

  Next, the controller 101 determines whether or not an erase instruction has been confirmed by the user based on a signal supplied from the controller device (step S65). If the erase instruction has not been finalized, the editing process ends. When the erase instruction is confirmed, the track included in the album of the album number 47 input in step S52 is erased, and the track information registered in the track 2 of the playlist 505 and the track 4 of the playlist 510 are also erased. The registered track information is erased (step S66).

  FIG. 48 is a table showing the link destinations of tracks registered in each playlist after erasure. As shown in FIG. 48, track 2 of playlist 505 and track 4 of playlist 510 shown in FIG. 40 are erased by the above-described album erase.

  As described above, according to one embodiment of the present invention, when the user instructs editing of a music file (track) recorded in the HD recording / reproducing apparatus 300, the system controller 100 performs editing. Since the information on the instructed music file (track) is deleted from the playlist, it is possible to prevent the music file (track) having no link destination from being generated in the playlist. That is, it is possible to prevent a situation in which a music file (track) registered in the playlist cannot be reproduced by editing.

  Also, according to one embodiment of the present invention, when the user instructs editing of a music file recorded on the HD recording / reproducing apparatus 300, the system controller 100 causes the music file (track) to be edited to be edited. Is displayed on the display device 102, the user can confirm whether or not a predetermined program instructing editing is registered in the management information. Therefore, it is possible to prevent an erroneous editing operation on the music file (track) registered in the playlist.

  The embodiment of the present invention has been specifically described above, but the present invention is not limited to the above-described embodiment, and various modifications based on the technical idea of the present invention are possible.

  For example, in the above-described embodiment, when a deletion instruction is given to a predetermined song belonging to a predetermined group, it is determined whether or not the deletion target song is registered in a playlist. Although the warning display is performed, as a modification, the music for which the deletion instruction is given may be deleted from the group but not deleted from the playlist. In this case, in the group, the management of the recording position for the music to be erased may be edited (erased) and the entity management may be performed using the playlist. In the above embodiment, entity management such as recording position is performed by group management, and the playlist side manages the group number and track number to which the song belongs, but does not perform entity management. However, entity management is also performed on the playlist side. By doing so, linked erasure can be prevented. As a result, even if it is deleted on the group side, it can be left unaffected on the playlist side.

  In the embodiment described above, an example in which the present invention is applied to an edit operation such as erase, combine, divide, etc., to a track or album registered in a playlist, and a dubbing apparatus capable of this edit operation. Although shown, this invention is not limited to this example. That is, the present invention can be applied to an editing operation for erasing a music file registered in a playlist from the hard disk (erase) and a dubbing apparatus capable of this editing operation. Further, the present invention can be applied to an editing operation for changing the size of music registered in a playlist (divide combine) and a dubbing apparatus capable of the editing operation. Specifically, an editing operation in which the previous Fno number indicated by TRK-xxx of the playlist management files Pb0001f5 to Pb0001fe is changed, or the size of the corresponding Fno is changed even if the number is not changed, and this editing operation is possible. The present invention can be applied to a simple dubbing apparatus.

  In the above-described embodiment, the example in which the user is warned that the track that the user has instructed to edit is recorded in the HD recording / reproducing apparatus 300 is shown. However, the warning is not performed. It doesn't matter. That is, when an instruction to edit a music file recorded on the HD recording / reproducing apparatus 300 is given, the system controller 100 indicates that the file instructed to edit via the display apparatus 102 is registered in the playlist. The editing instructed by the user may be executed without warning.

  Further, in the above-described embodiment, the case where the debyted track is erased from the playlist when the track is divided is shown. However, two tracks after debiting are newly registered in the playlist. It doesn't matter if you do. Alternatively, any one of the two tracks after debiting may be registered in the playlist.

  Further, in the above-described embodiment, the case where the combined track is deleted from the playlist when the tracks are combined has been described. However, the combined track may be newly registered in the playlist. It doesn't matter.

It is a block diagram which shows an example of a structure of the dubbing apparatus by one Embodiment of this invention. It is a block diagram which shows an example of a structure of the system controller 100 by one Embodiment of this invention. It is a block diagram which shows an example of a structure of the disc reproducing | regenerating apparatus 200 by one Embodiment of this invention. It is a basic diagram which shows an example of the structure of the flame | frame in CD. It is a basic diagram which shows an example of the format structure of the subcode in CD. It is a basic diagram which shows an example of a structure of the subcode frame in CD. It is a basic diagram which shows an example of a structure of Q data in a subcode. It is a basic diagram which shows an example of a structure of the data part in Q data. It is a block diagram which shows an example of a structure of HD recording / reproducing apparatus by one Embodiment of this invention. It is a flowchart for demonstrating the process which records audio data in HD recording / reproducing apparatus by one Embodiment of this invention. It is a flowchart for demonstrating the process which records audio data in the HD recording / reproducing apparatus concerning one Embodiment of this invention. It is a branch drawing which shows the structure of the file memorize | stored in HDD. It is a data structure figure of an album number management file. It is a data structure figure of an album number management file. Album reproduction management file Pbxxxxxxxx. It is a structural diagram of msf. It is a data structure figure at the time of dividing one continuous ATRAC3 data file for every predetermined unit, and adding an attribute file. It is a structure figure for demonstrating the combine edit process and division | segmentation edit process of this invention. Album reproduction management file Pbxxxxxxxx. The data structure figure of msf is shown. Album reproduction management file Pbxxxxxxxx. The data structure figure of msf is shown. It is a detailed data structure diagram of an ATRAC3 data file. It is a data structure figure of the upper part of the attribute header which comprises an ATRAC3 data file. It is a data structure figure of the middle part of the attribute header which comprises an ATRAC3 data file. It is a table | surface which shows the kind of recording mode, the recording time in each recording mode, etc. FIG. It is a table | surface which shows a copy control state. It is a data structure figure of the lower part of the attribute header which constitutes an ATRAC3 data file. It is a data structure figure of the header of the data block of an ATRAC3 data file. Album / track name database file Namedb. It is a structural diagram of msf. Album / track name database file Namedb. The block ID part of msf is shown. Album / track name database file Namedb. The name record part of msf is shown. Playback time management database file Playtime. It is a structural diagram of msf. Playback time management database file Playtime. The block ID part of msf is shown. Playback time management database file Playtime. This shows the TRK record part of msf. CD TOC database file Tocdb. It is a structural diagram of msf. CD TOC database file Tocdb. The block ID part of msf is shown. CD TOC database file Tocdb. Indicates an ALFUM TOC record of msf. CD TOC database file Tocdb. The TOC information of the ALBUM TOC record of msf is shown. It is a block diagram which shows an example of a structure of the audio | voice input / output part concerning one Embodiment of this invention. It is a flowchart for demonstrating the place registration operation and process in the dubbing apparatus by one Embodiment of this invention. 10 is a table showing the number of each album stored in the HD recording / reproducing apparatus and the number of tracks included in each album before editing processing. 10 is a table showing the number of each album stored in the HD recording / reproducing apparatus and the number of tracks included in each album before editing processing. It is a flowchart for demonstrating operation and processing of track erasure editing in the dubbing apparatus by one Embodiment of this invention. 10 is a table showing the number of each album stored in the HD recording / reproducing apparatus and the number of tracks included in each album after the editing process. It is a flowchart for demonstrating the operation and process of combined editing in the dubbing apparatus by one Embodiment of this invention. 10 is a table showing the number of each album stored in the HD recording / reproducing apparatus and the number of tracks included in each album after the editing process. It is a flowchart for demonstrating the operation and process of division | segmentation editing in the dubbing apparatus by one Embodiment of this invention. 10 is a table showing the number of each album stored in the HD recording / reproducing apparatus and the number of tracks included in each album after the editing process. It is a flowchart for demonstrating the operation | movement and process of an album deletion edit in the dubbing apparatus by one Embodiment of this invention. 10 is a table showing the number of each album stored in the HD recording / reproducing apparatus and the number of tracks included in each album after the editing process.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 ... System controller 101 ... Controller 102 ... Display device 103 ... Operation device 200 ... Disc reproducing device 201 ... Spindle motor 202 ... Optical head 203 ... RF amplifier, 204 ... servo circuit, 205 ... thread, 206 ... EFM and CIRC decode circuit, 207 ... controller, 300 ... HD recording / reproducing apparatus, 301 ... digital audio I / F, 302 ... AD / DA I / F, 303 ... encoding / decoding device, 304 ... magic gate core, 305 ... shared RAM, 306 ... HD controller, 307 ... SDRAM, 308... FAT32 file system, 309... HDD, 400. AD converter, 402 ... DA converter, 403 ... analog input terminal, 404 ... digital input terminal, 405 ... digital output terminal, 406 ... analog output terminal, 500 ... external signal input Output section

Claims (2)

An operating means for instructing the program to edit based on the first management information with respect to a recording medium that is managed by the first management information and also records a program managed by the second management information. When,
Determining means for determining whether the program instructed to edit by the operation means is managed by the second management information;
Notification means for giving a warning before performing an editing operation when the determination means determines that the program is managed by the second management information;
Control means for editing the first management information and the second management information when the editing instruction is confirmed by the notification means and the editing instruction is confirmed,
The control means deletes the program before the combination or division from the second management information when an instruction to edit the combination or division is given to the program based on the first management information. , the editing apparatus to be newly registered in the program after coupling or dividing the second management information. An editing instruction is given to a recording medium that is managed by the first management information and also records the program managed by the second management information based on the first management information. A first determination step of determining whether or not
A second determination step of determining whether or not the program instructed to be edited is managed by the second management information when it is determined that the editing instruction is performed in the first determination step; ,
A notification step of giving a warning before performing an editing operation when it is determined in the second determination step that the program is managed by the second management information;
An editing step for editing the first management information and the second management information when the editing instruction confirmation that has given a warning in the notification step is performed and the editing instruction is confirmed,
In the editing step, when an editing instruction for combination or division is given to the program based on the first management information in the first determination step, the program before the combination or division is stored in the second management information. An editing method in which a program after deletion or combination and division is newly registered in the second management information.

Images