MXPA01002742A - Recording medium with write protected defect list - Google Patents

Abstract

The invention relates to recording of information, in particular a real-time audio and/or video signal, in a recording track (3) of a recording medium (2) divided into blocks (45). The recording medium contains a defect list (BS) of addresses of blocks (45*) which are known to be defective. This list is read and during the recording process the defective blocks are skipped. The recording process is performed without any read-after-write check so as to speed up the process. The defect list is updated by noting, during playback, which blocks give rise to reading problems and by including the addresses of these blocks in the defect list on the recording medium.

Description

MEDIA OF RECORDING WITH LIST OF DEFECTS PROTECTED FROM WRITING The present invention is generally related to a method of recording information on a recording medium having at least one recording track, said recording track being divided into logical blocks, each having an individual logical address. The recording medium can be, for example, an optical or magnetic recording recording medium. The present invention typically and in particular, although not exclusively, relates to recording on an optical disc and will then be elucidated with reference to this example for use. However, it is emphasized that the invention also applies to other fields of use, such as tape recording. In general, the amount of information to be recorded in a recording session is greater than a block. The information to be recorded, also referred to as "file", is then divided into successive data packets that are the size of a block, and the successive data packets of a file are recorded in different blocks of the recording medium, which for the purpose of simplification it is referred to hereinafter as "recording disc". For a fast data transfer then it is desirable that the successive data packets are recorded in successive blocks. The recording process can then proceed virtually continuously. In the same way, during the subsequent reading (play-back) of the information recorded on the disc, the reading process can proceed continuously. In practice, a disk can show defective blocks, that is, blocks where a recording without information failures is no longer possible or where any resulting small writing error can no longer be corrected during reading. This block is then no longer suitable for recording. The only remedy is then to record the data packet that was to be stored in that defective block in another block. In a conventional manner, the blocks are tested against defects by checking them during a write operation whether the recording has been made correctly or not. Said revision, which is referred to as "read after writing" revision, is mainly carried out on a block-by-block basis, although it is also possible to record a plurality of blocks and subsequently review a plurality of blocks. In itself, a test procedure of reading after writing implies that an information packet is stored in a read memory after writing which is the size of a block, which is read after the recording of the just-written block , and that the information read from said block is compared with the information packet stored in the read memory after writing. If these two information packets correspond, the conclusion indicates that the recording has been successful and a subsequent information packet can be recorded in a next recording block of the recording track. However, in the case of a difference between the two information packets, it is inferred that the recording has not been successful and the recording of the relevant information packet is repeated. Another recording attempt, also called "new attempt", can be made in the same block but if after a given number of attempts the recording in this block still fails, this block is considered as a defective block in which the recording does not it is possible and the recording of the relevant information package proceeds in another block. In this way, the information is recorded in a reliable way. A recording method using said test procedure to read after writing and a possible new recording attempt in order to repair the damaged information requires a lot of time in a comparative manner. Said recording method is therefore less suitable for uses where a stream of information with a high average of data is to be recorded. Said use is, for example, a recording of audio and / or real-time video signals. It is an object of the present invention to provide a recording method and recording apparatus that are more suitable for recording information streams with a high average of data, in particular real-time recording of audio and / or video signals. The present invention more particularly helps to provide an apparatus of the above-mentioned type which is suitable as a digital audio and / or video recording apparatus. It is known in itself that a recording apparatus is adapted to first examine the quality of the recording blocks in a test cycle before the actual recording process. If defective blocks are detected, the sequence numbers or addresses of these blocks are stored in a memory and, consequently, this memory is addressed during the actual recording process and the defective blocks are skipped. However, again tests are performed with the help of a write-read process after writing and, as a result, the test cycle takes a long time before the recording process can begin. According to the first important aspect of the present invention, the recording medium itself contains a list of defective block addresses. This list is present in a file that should never be overwritten. For this purpose this file can be placed on a predetermined portion of a recording track but, alternatively, this file can have a predetermined name and the recording apparatus is adapted to use the file that has this name exclusively for recording of bad block addresses.

According to another important aspect of the present invention, the recording apparatus is adapted to read said file before a recording session and to store the addresses of blocks specified therein in an auxiliary memory and to read said auxiliary memory during the session of recording. recording and to skip the blocks whose addresses appear in this auxiliary memory during recording. This prevents attempts to record for blocks that are already known as bad blocks. Therefore, time is not wasted with recording attempts that are destined to fail. It is known in itself that during the reading of information (play-back) errors can occur, in view of which a reading device includes an error correction system, and error correction information for use in this system. Error correction is recorded during the recording of the data packet. Said error correction system enables comparatively small errors to be corrected. These errors may have occurred during the recording and may be present in the recording medium itself. The degree to which such errors can be corrected depends on the error correction system used; since the error correction systems are known per se and the present invention can be used in conjunction with known error correction systems, a detailed explanation of the error correction system will not be provided in this document. According to another important aspect of the present invention, the quality of the read data packets of each block read during the reading of information (play-back) is monitored. If it is discovered that a given data packet shows incorrigible errors or if the reading of a block fails completely, but preferably also if the number of correctable errors appearing in a block is greater than the predetermined acceptance limit, the address The relevant block is stored in a second auxiliary memory. After the end of the play-back session, the blocks whose addresses have been stored are tested. During this test a standard read operation is performed after writing for these blocks in the course of the test process. The test process for each block includes a step in which a restoration attempt is made. Then, this block is read once more, the data packet then read is presented in the error correction system. If the error correction system is able to actually correct the error, the restored data is recorded in the relevant block instead of just reading the information, after which a read operation is performed after writing for the data. restored data for the purpose of determining whether the recording has been carried out in a satisfactory manner or not. Therefore, the error is corrected in an active way, as a result of this, fewer errors occur during a subsequent reading and the delay in the transmission of data that need correction of errors is less. However, if the error correction system can not correct the error in the information read, it examines whether the error is just a non-recurring write error in a block otherwise without failures, or if the recording block itself It is defective. For this purpose, a predetermined pattern or data or code word is recorded in the relevant block, after which a standard read operation is performed after writing for said code word in order to check whether the recording has been made or not in the right way If this is the case, the block apparently is not defective; during a subsequent reading cycle the word code is recognized as a "proof". Otherwise, the relevant block is recorded in said file in the recording medium. As explained earlier in this document, this prevents this block from being addressed during a subsequent recording session.

In addition, it is also possible to skip the restoration step and include each block whose address was noted during playback in the list of defective blocks as a standard procedure. As a result of this, the apparatus will be ready more quickly at the end of a play-back session but, which eventually results in an unnecessary reduction in the storage capacity of the recording medium.

These and other aspects, features and advantages of the present invention will be elucidated later by the following description of a preferential characterization of a recording apparatus and a recording method according to the invention with reference to the drawings, in which identical or similar ones keep the same reference symbols and in which: Figure 1 shows in diagrammatic form an apparatus adapted to record information on a recording disc and for play-back a recording disc; Figure 2 shows diagrammatically the logical structure of a recording medium: Figure 3 is a flow diagram of a method according to the present invention; and Figure 4 is a flow diagram of a play-back method according to the present invention. Figure 1 shows diagrammatically an apparatus 1 for registering and reading a disc-shaped recording medium or a recording disc 2. The apparatus has an input 6 for receiving information to be recorded on disc 2, for example a video and / or real-time audio signal, and an output 7 for providing a signal read from disk 2 in a reading cycle. Obviously, input 6 and output 7 can be combined to form a combined input / output. The disk 2 can be a magnetic recording disk, for example a hard disk, in which the apparatus 1 is a magnetic recording / reading apparatus. The disk 2 can also be an optical recording medium, for example a CD-RW, in which case the apparatus 1 is an optical recording / reading apparatus. It should be noted that the invention is not exclusively related to a disc-shaped recording medium, but also includes, for example, a recording tape. The disk 2 has a multitude of mutually concentric recording tracks 3, which are assumed to be individual circular tracks in the following, but it is also possible that the tracks 3 represent a continuous spiral track. As it is known per se, the apparatus 1 has an optical writing / reading head 10 and a turntable, which is not shown for the sake of simplicity and faces the head 10, in said turntable the disc 2 can be placed and which disc 2 can be provided a rotary movement with respect to the head 10, then enabling the track 3 to be scanned by the head 10. the recording apparatus 1 also includes means, which are known per se and which they are not shown for the sake of simplicity, to move the head 10 in a radial direction of the disk 2, thus enabling different tracks 3 of the disk 2 to be accessed by the head 10. As is well known, the information is written in the track 3 by a laser beam 11 of the head 10 in the case of optical recording. The writing process, like the reading process, is controlled by means of a functional unit 20, hereinafter referred to as the write / read control unit. Said write / read control unit 20 is known per se and is therefore not described later. It should be noted that the read write control unit 20 is adapted to control the positioning of the head 10 with respect to the disc 2 such that the writing process or the reading process is carried out at the desired location in the disc 2 through the control of said turntable for the disc 2 and said positioning means for the writing head 10. In addition, the read-write control unit 20 controls the intensity of the laser beam 11 depending on the output signal S which is going to be recorded. This control function of the read-write control unit 20 is shown diagrammatically as the coupling 22 in FIG. 1. The recording apparatus 1 further has a functional unit 30., hereinafter referred to as the assignment administrator. Said allocation manager 30 is known per se and therefore will not be described later. It should be noted that the allocation manager 30 is adapted to determine in which part of the disk 2 a certain recording or recording session takes place. When a user begins a recording, the allocation manager 30 determines if there is enough space to record on the relevant disk 2, and if this is the case, how much space is available. The allocation manager 30 informs the writing control unit 20 about the starting location of this available space, which is represented as a diagram as the signal acquisition 31. Since the magnetic and optical recording are processes that are known itself and the possible constructions for a magnetic recording medium 10 or an optical recording medium 10 are known per se, while in addition the optical recording / reading apparatuses 1 are known per se, these will not be described in detail in this document. . Figure 2 diagrammatically represents the logical structure of the disk 2. the recording tracks 3 together define a recordable area 40 of the disk 2, which is shown as a continuous line in Figure 2 and which will also be referred to hereinafter as the recording area. The recording area 40 of the disk 2 has been divided into logical blocks 45, which each have a predetermined individual address. The reference symbol 45 * refers to a defective block. The value of the relevant address of a block 45 has been recorded in a predetermined address field of block 45. Then it is possible to record information directly in a given location corresponding to a given address in disk 2 and in the same way it is possible to read the information directly from a given location that corresponds to a given address. Blocks 45 have a block size that does not need to be the same for all blocks. The amount of data that can be written to a block is called a data package. The recording area 40 consists largely of a so-called addressable space 41, which the user can access for the purpose of recording information and then will also be referred to hereinafter as the user area. The information in the user area 41 is accommodated in logical rows f 1, f2, etc., each row corresponds to a recording session. Each row may involve a large number of blocks 45, the successive data packets in a row usually correspond to successive blocks 45 of the user area 41. The recording area further includes a reserved area 43 for administrative information that is related to with disc 2 and the information recorded on this disc. This area 43 will also be referred to hereinafter as the administrative area 43. The administrative area 43 among other things includes a table of contents that relates to the files recorded on disk 2, said table specifying the start addresses, the length, the name etc, of each row. In general, the name of each file can be chosen freely by the user. However, in accordance with an important aspect of the present invention, the disk 2 has at least one file in the user area 41 to which the user does not have access and which has a pre-defined standard name, the standard name chosen in the present case is "BS". The BS file has a non-critical physical location in the user area 41; in Figure 2 the BS file is shown at the beginning of the user area 41 but this is not necessary. It is only important that the location of the file is known and that this file is protected against deletion and overwriting by the user. The recording area 40 of the disc 2 may further include an extra area 42 reserved for replacement recording, but this is not relevant to the present invention. According to another important aspect of the present invention, the BS file contains a list of block addresses in the free recording area 41 known to be defective. This list is also referred to as a list of defects. The defect list can be implemented in the form of an initially empty memory in which only numbers and defect sequence addresses are stored. It is also possible to implement the list of defects in the form of a memory having a predetermined number of storage locations, each storage location corresponding to the sequence number of a specific recording track and the content of this storage location being an indicator whether the relevant recording track is defective or not; each of the storage locations then need to be composed of a single bit. Furthermore, according to an important aspect of the present invention, the recording apparatus 1 is adapted to detect, before the recording of information on the disc, whether the disc 2 has a file called BS and, if this is the case, for revert the contents of this BS file in order to discover addresses of bad blocks and to skip these blocks during the writing process subscribe.

The operation of a writing / reading apparatus 1 according to the invention will be described in more detail with reference to the flow diagrams of Figures 3 and 4. In a step 101 of a recording cycle 100 the apparatus 1 receives an order of the user's recording The allocation manager 30 is adapted to then determine in a step 102 that part of the user area 41 of the recording area 40 of the disk 2 has already been used for previous recordings and defines a NW area where the recording can be made in a portion unused from the user area 41. The allocation manager 30 is adapted to address the administrative area 43 of the recording area 40 of the disk 2 in a step 103 and to examine whether the disk 2 contains a file called "BS". The allocation manager 30 is adapted to create a BS file in a step 104 if it appears in step 103 that the disk 2 does not yet contain said file. If in step 103 it is discovered that there is a Hamado file "S", the allocation manager 30 refers to the defect list of the BS file in a step 105 in order to examine which blocks in the NW area defined for recording are it knows that they are defective In a step 106 the allocation manager 30 stores the addresses of the defective blocks 45 * found in the NW area in a first auxiliary memory 51. For the purpose of illustration now it is assumed that this is the first time that a recording is to be made in the NW area This means that there is still no information available on the blocks 45 that this NW area is defective or not, therefore no block address is now stored in the first auxiliary memory 51 .

After these preparations, which require a comparatively short time, the current recording process begins. In a step 111 the allocation manager 30 determines the next block address (at the start: the first block address) in the NW area defined to record. In a step 112 the allocation manager 30 checks whether this block address appears in the first auxiliary memory 51. If this is the case, it is known that the relevant blocks are defective and in a step 113 it is decided to skip this block, in the that the allocation manager 30 returns to step 111. In the other case a new data packet of the signal or information stream received in the input 6 is written to the relevant block 45 in a step 114. if the recording has not yet been has completed, in a step 115 the assignment manager 30 returns step 111. Let it be assumed that the NW area does not contain said defective block 45 *. Since, as assumed, this information was not known before the recording process began and, consequently, the block address of this defective block 45 * has not yet been stored in the first auxiliary memory 51, a packet of data will be written to this defective block 45 *. Thus, in accordance with an important aspect of the present invention, a data packet is written to all available blocks of the NW area defined for recording and no revision to read after writing is carried out during the recording process. As a result of this, the actual recording process is comparatively fast, which is an important advantage of the present invention. Upon termination of the recording, the allocation manager 30, in a step 116, updates the information in the administrative area 43 in a routine manner and, specifically, records the start address and the length and / or the terminal address of the the new recording and a name for this recording.

Now let's assume that the user wants to play back the recording he just made. In a step 201 the apparatus 1 receives the appropriate command for this from the user, for this purpose, the user introduces for example a sequence number or the name of a recording selected by it. In a step 202 the allocation manager 30 refers to the administrative area 43 in order to obtain the first block address of the selected recording and in a step 203 the allocation manager 30 instructs the writing / reading unit 20 so that read user area 41 from disk 2 starting at this first block address, and to transfer the information that is being read to output 7 for further processing by, for example, an audio or video playback system. In a step 204 the writing / reading unit 20 reads the data in the relevant block and determines the quality of the data, which is done in the known way with the help of an error correction algorithm. Since said error correction algorithms are known per se, it is not necessary to describe an example of said error correction algorithm. If in step 204 the block being read does not present errors or only a small number of errors that appear to be correctable, the writing / reading unit proceeds to a step in order to take out the information read through output 7. if the end of the recording has not been reached, the writing / reading unit 20, in a step 206, returns to step 204 to read the next block. If in step 204 the block being read has no errors or only a small number of errors that appear to be correctable but appear in such an amount that the predetermined limit is exceeded, the write / read unit 20 transfers the block address relevant to the allocation manager 30 in a step 211, in which the allocation manager 30 stores the relevant block address in a second auxiliary memory 52 in a step 212, where the auxiliary memory is also referred to as "problem memory". In the following, the write / read unit 20 proceeds to step 205 for the purpose of outputting the read information via the output 7. If in step 204 the block to be read appears as non-readable or contains at least one error uncorrectable or a hop code (the meaning of which will be explained hereafter), the reading splinter unit 20 transfers the relevant block address to the allocation manager 30 in a step 221, in which the allocation manager 30 stores the address relevant block in the problem memory 52 in a step 222. It is also possible that the writing / reading unit proceeds directly to step 206 and then step 205 is skipped, as shown in Figure 4, in order to inhibit an output of information via the output 7. However, it is also possible that the damaged information or the test information of the hop code is generally fed via the output 7, optionally provided with a warning bit as a sign that the information in this block is not reliable. In this last mentioned case, the reading writing unit 20 proceeds to step 205 after step 222; in fact, the individual steps 221, 222 can then be dispersed. If in step 206 it appears that all the blocks of the requested recording have been read, the play-back cycle 200 is finished.

Preferably, and as illustrated, the allocation manager 30 now proceeds to a restoration cycle 300 for the purpose of attempting to improve the quality of the blocks defined in the problem memory. In a step 301 the allocation manager 30 reads from said problem memory 52 the next block address (at the start: the first block address) of a block 45 where problems have been encountered during the play-back. In a step 302 the allocation manager 30 reads the data of said block. In a step 303 the assignment manager 30 checks whether reading is possible. If reading is possible, the allocation manager 30 checks in a step 304 whether the relevant block contains a jump code. If this does not seem to be the case, the assignment manager 30 reviews in a step 305, with the help of an error correction algorithm, if the block presents only correctable errors. If this is the case, the corrected information is written to the relevant block in a restoration step 306, and is checked by the read operation after writing if the restored data has been recorded successfully. Subsequently, the allocation manager 30 reads the problem memory 52 in a step 307 in order to determine whether the problem memory 52 contains more addresses of problem blocks. If this is the case, the allocation manager 30 proceeds to step 301. If at step 303 it appears that the reading of the relevant block is not possible, or if at step 304 it appears that the relevant block contains at least one incorrigible error , a test is carried out to check if the relevant block is defective. For this purpose, the allocation manager 30 writes a predetermined data pattern or code word, referred to as "jump code", in the relevant block in a step 311, as a result of which this block may be identified as defective or as Test in a subsequent reading session. In a step 312 the allocation manager 30 checks through a read operation after writing if the skip code has been recorded successfully. If in a step 313 the jump code is recorded correctly, the conclusion indicates that the relevant block is not defective and the allocation manager 30 proceeds to step 307. Otherwise, the conclusion indicates that the relevant block is due to definitively label as a defective block 45 *, for that purpose the allocation manager 30, in a step 314, stores the address of this block in a third actuator memory 53, referred to hereinafter as the "erasure memory". " After this, the allocation manager 30 proceeds to step 307. If in step 307 it appears that all the blocks whose addresses have been stored in the problem memory 52 have been processed in the restoration cycle 300, the restoration cycle is concludes. Then the allocation manager 30 proceeds with a deletion step 400, in which the allocation manager 30 writes the addresses of the erase memory 53 in the BS file on the disk 2. If the disk 2 is a disk that is not yet contains a BS file, that file must be created first.

In this way, some blocks of the already read recording (can) have been restored; during a subsequent reading a smaller number of reading errors can be expected. However, the recording may still contain defective blocks; during a subsequent reading these blocks will be recognized and no attempt will be made to subject these blocks to an error correction algorithm, as a result of which the loss of time is avoided. When the user no longer wishes to keep the relevant recording, it will release the part of the user area 41 occupied by this recording for later recording. During a subsequent recording session, the user then no longer confronts these defective blocks in this area, since in step 105 the allocation manager 30 will recognize the defective blocks and skip these blocks in step 113.

Therefore, the invention provides a very effective method of recording information, in particular audio and / or real-time video information, in a recording track 3 divided into blocks 45 in a recording medium 2. The recording medium contains or is provided with a list of BS defects with addresses of blocks 45 * that are known to be defective. This list is read and the defective blocks are skipped during the recording process, which is carried out without a review of read after writing in order to increase the speed. The list of defects is updated by noting which given blocks created reading problems while reading a file and recording the address of these blocks in this list of defects in the recording medium after reading.

It will be apparent to one skilled in the art that the vision of the present invention is not limited to the examples described herein above, but that several changes and modifications are possible therein without departing from the vision of the invention as defined in Claims attached. Therefore, it is possible for example to carry out the steps 311-313 in a separate cycle prior to the deletion step 400. In the same way it is possible to simplify and therefore increase the speed of the restoration cycle in which the step 212 of the play-back cycle 200 a block address of a block containing only correctable errors is stored in the problem memory 52 and in step 222 of the play-back cycle 200 a block address of a block that has been discovered which shows more severe errors is stored in another auxiliary memory. In said simplified restoration cycle step 306 is carried out for the block addresses specified in the problem memory 52 and the steps 311-314 are carried out for the block addresses specified in said other auxiliary memory.

If desired, the restoration cycle 300 can be dispensed with completely, in which case the problem memory 52 is consumed in the deletion step 400, instead of the erasure memory 53, which can be dispensed with in this variant.

Claims (15)

CHAPTER CLAIMING Having described the invention, it is considered as a novelty and, therefore, the content is claimed in the following:
1. CLAIMS 1. A recording medium (2) having at least one recording track (3) and having a recording area (40) divided into logical blocks (45) which each have an individual logical address, where a Defect list (BS) of defective block addresses (45 *) is stored in the recording area (40).
2. 2. A recording medium as claimed in Claim 1, wherein said defect list (BS) is protected against overwriting and / or deletion by the user.
3. 3. A recording medium as claimed in Claim 2, wherein for the purpose of said defect list (BS) has a predetermined standard name and / or is recorded in a predetermined location.
4. 4. A method of recording information in a recording medium (2) having at least one recording track (3) and having a recording area (40) divided into logical blocks (45) which each have a logical address individual, where, before the actual writing process, it is examined whether the recording medium (2) has a file having a predetermined name (BS), said file is indicative of the presence of a list of block address defects defective (45 *) and where, if the recording medium (2) does not yet have said file, said file is created in the first instance.
5. 5. A method of recording information in a recording medium (2) having at least one recording track (3) and having a recording area (40) divided into logical blocks (45) which each have a logical address individual, where, before the actual writing process, it is examined whether the recording medium (2) has a file having a predetermined name (BS), said file is indicative of the presence of a list of block address defects defective (45 *) and where, if the recording medium (2) actually has said file, the block addresses specified in said file are read and skipped in the actual writing process.
6. 6. A method of recording information in a recording medium (2) having at least one recording track (3) and having a recording area (40) divided into logical blocks (45) which each have a logical address individual, where if problems occur during the reading of a block, for example, if the reading of a block fails completely or, for example, if a block seems to contain incorrigible errors during reading, and preferably also if the number of errors correctable events occurring in a block is greater than the predetermined acceptance limit, the address of the relevant block is stored in a problem memory (52); and where at the completion of the reading cycle (200) the addresses of the blocks stored in the problem memory are recorded in a defect list in a predetermined file (BS) in a recording medium (2).
7. 7. A method of recording information in a recording medium (2) having at least one recording track (3) and having a recording area (40) divided into logical blocks (45) which each have a logical address individual, where if problems occur during the reading of a block, for example, if the reading of a block fails completely or, for example, if a block seems to contain incorrigible errors during reading, and preferably also if the number of errors correctable events occurring in a block is greater than the predetermined acceptance limit, the address of the relevant block is stored in a problem memory (52); and where at the end of the reading cycle (200) the blocks specified in the problem memory are checked.
8. 8. A method as claimed in Claim 7, wherein during the revision of a block specified in the problem memory, the information in said block is read and subjected to an error correction algorithm, and where, if the information already read it appears to be restorable, the restored information is written to a relevant block in a restore step (306), after which a read review after writing is preferably carried out.
9. 9. A method as claimed in Claim 7, wherein during the revision of a block specified in the problem memory, the information in said block is read and subjected to an error correction algorithm, and where, if the information already read it seems not to be restorable, a predetermined code word (jump code) is written in the relevant block, after which a read revision is carried out after writing (312); and where, if during said review after reading (312) it appears that said code word has not been written successfully, the address of the relevant block is recorded (314,400) in a list of defects in a predetermined file (BS) in a recording medium (2).
10. 10. A method for recording information, in particular a real-time audio and / or video signal in a recording track (3) of a recording medium (2), said recording track has been divided into blocks (45); wherein the recording medium contains a list of defects (BS) of addresses of blocks (45 *) known to be defective, or is provided with said list; where said list of defects is read and where during the recording process, which is carried out without a review of reading after writing to then accelerate the process, the blocks whose addresses have been read from said defect list are skipped; and where said list of defects is updated by annotation from which the blocks gave rise to reading problems during the reading of a file and by recording the addresses of these blocks in said list of defects in the recording medium after reading .
11. 11. An apparatus (1) for recording information, in particular a real-time audio and / or video signal in a recording track (3) of a recording medium (2), said recording track has been divided into blocks (45). ); and to read information recorded in said recording medium, said apparatus comprises: - a writing / reading unit (20) adapted to control the writing process and the reading process; an allocation manager (30) coupled to said read write unit (20); a first auxiliary memory (51) associated with the allocation manager (30); wherein the allocation manager (30) is adapted to read, after having received a recording command (101) and having defined a part (NW) (102) directed to record in the recording area (40) of the medium of recording (2), a file (BS) recorded on the recording medium (2) and containing a list of defects of defective block addresses (45 *) and for storing (106) the addresses of blocks specified in the list of defects in the first auxiliary memory (51); and where the allocation manager (30) is adapted to examine (112), each time a new block (45) is reached during the recording process, if the block address of said new block appears in the first auxiliary memory ( 51) or not, and to skip said block if the block address of said new block actually appears in the first auxiliary memory (51).
12. 12. An apparatus as claimed in Claim 11, wherein the allocation manager (30) is adapted to not allow the user to use a predetermined name (BS) reserved for the defect list, and wherein the allocation manager (30) is adapted to not allow the user to delete and / or overwrite the file that has said predetermined name (BS) reserved for the defect list.
13. 13. An apparatus as claimed in Claim 11 or 12, further comprising a problem memory (52) associated with the allocation manager (30); wherein the reading writing unit (20) is adapted to be monitored, using an error correction algorithm, the data quality is read during the reading cycle (200), each time the data of a given block is read and, if given problems occur, transfer (211, 221) the address of the relevant block to the assigned administration (30); i_fc and wherein the allocation manager (30) is adapted to store a block address already received from the read write unit (20) in the problem memory (52).
14. 14. An apparatus as claimed in Claim 13 wherein the allocation manager (30) is adapted to read, after the completion of the read cycle (200), the data of a block stored in the problem memory (52) and for subjecting said data to an error correction algorithm (302) and, if the data already read seems to be restorable (305), to write (306) the restored data in the relevant block and after that, to preferably carry out a Review of reading after writing.
15. 15. An apparatus as claimed in Claim 13 or 14, further comprising an erasure memory (53) associated with an allocation manager (30); wherein the allocation manager (30) is adapted to read, after the completion of the reading cycle (200), the data of a block stored in the problem memory (52) and to subject said data to a correction algorithm of errors (302) and, if the data already read appear not to be restorable (305), to write (311) a predetermined code word (code word) in the relevant block and, after this, carry out the review of reading after to write (312); wherein the allocation manager (30) is adapted to store (314) the block address of the relevant block in said erasure memory (53) if during said review of reading after writing (312) it appears that said code word is not he has written successfully; and wherein the allocation manager (30) is adapted to record (400) the addresses of blocks stored in the erasing memory 853) in a list of defects in a predetermined file (BS) in the recording medium (2) after that all the blocks stored in the problem memory (52) have already been checked.