MXPA05006039A - Editing of real time information on a record carrier. - Google Patents

Abstract

A device for real-time recording information has a file subsystem for storing the real-time information according to predefined allocation rules, including a predefined extent length (N). The device has an application subsystem for managing application control information, which includes clips (291,292) of the real-time information, a playlist of playitems indicating parts to be played of the real-time information in the clip. A bridge clip (293) is provided for linking a first and a second playitem based on re-encoded real-time information from an ending part of the first clip and a starting part of the second clip. The file subsystem is arranged for copying additional units of real-time information (294) from the first clip and/or the second clip for creating the bridge clip stream having at least the predefined extent length, and the application subsystem is arranged for adapting the application control information for accessing the bridge clip stream including said additionally copied units. In borderline cases the remaining part of a preceding or following clip is completely copied to the bridge clip.

Description

EDITING REAL-TIME INFORMATION IN A REGISTRATION CARRIERS DESCRIPTION OF THE INVENTION The invention relates to a device for recording real-time information in a record carrier, wherein the device has recording means for recording blocks of data based on logical addresses that are found in the record carrier, a file subsystem for storing real-time information in units that have unit numbers (SPN) in the data blocks, according to predefined allocation rules, rules that include storing a flow of real-time information that is going to be reproduced without junctions in a sequence of consecutive data block extensions, wherein the extensions have at least one predefined extension length, and an application subsystem for handling application control information, wherein the application control information includes at least one real-time information connector, wherein the connector comprises information of The connector for accessing a stream of the connector of the real-time information units, through the unit numbers, at least one Play List wherein the Playlist comprises at least one Play Element and the Element of Play. EEF: 162502 Play indicates a part, which is to be played, of the real-time information in the connector, the Play List indicates in which order the Play Elements have to be played, and at least one bridge connector to link a first and a second Playback Elements through the bridge connector, a stream of the bridge connector comprising re-encoded real-time information, based on a final part of the first connector and an initial part of the second connector. The invention also relates to a method and a product consisting of a computer program, for controlling the recording of real-time information, and to a record carrier carrying the real-time information.

In particular, the invention relates to the field of recording a digital video signal, in a disk type record carrier, and subsequently editing an information signal previously recorded in the disk type record carrier. An apparatus for recording a real-time information signal, such as a video information signal encoded in MPEG, in a record carrier, is known from WO99 / 48096 (PHN 17.350). The record carrier in that document is a disk type record carrier. It also proposes a recording system for real-time information, for a high-density optical disc known as Blu-ray Disc (BD), as described in the document Rewritable Blu-ray Disc Format , part 3: Specifications of the Audiovisual Database, June 2002, the relevant parts of the document are included substantially in the following description with reference to the figures from 13 to 26. The background of the technique describes a layered structure used in the BD to record video, where the structure has a layer of the file system to store the real-time information in the data blocks, in accordance with predefined allocation rules and an application layer for handling application control information, as follows. The real-time information is stored in the connector's stream files, and the corresponding control information is stored in the connector's information files. A Playlist indicates parts of the real-time information that will be reproduced through the Play Elements. This is further explained with reference to figures 13 and 14, and detailed definitions of an audio-visual stream (AV) of the connector, of the AV stream file of the bridge connector are provided., of the connector information file and the Playlist. In general, in the connector flow file the data is stored in units called source packets, and the addressing in the file is based on source packet numbers (SPN). Each connector flow file has a corresponding connector information file. The connector information file has some subtables, which include Connector Information, Sequence Information, and Feature Point Information (CPI). The Playlist contains a certain number of Play Elements and the indicators in the Playlist of the Playlist are based on the time axis. Indicators (addresses) for the connector stream file are based on the numbers of source packages. Using the Connector Information the timing indicators are converted into indicators for locations in the file (the CPI provides entry points to decode the real-time information). The Playlists can be presented to the user in a Table of Contents as Titles. During playback, a Play List is selected, the Play Elements found therein are analyzed, and the resulting time indicators are translated into the connector's SPN and the source packets that need to be presented are read from the disk. In the apparatuses according to the prior art, there are the following problems to link two Reproduction Elements without joints, for example during editing. The connectors contain encoded real-time information, for example, video encoded in MPEG. Hence, when two parts of different connectors (or the same connector), are going to be presented one after the other, a presentation without joints is not achieved during this transition. To achieve a seamless transition, the following restrictions must be met. The MPEG data should be continuous, for example a closed group of images (GOP) at the end of the Playback Element-1 and at the start of the Playback Element-2, and there should not be insufficient flow or excessive, intermediate flow of the memory intermediate decoding in the MPEG decoder. The presentation without connections during the connection of two Elements of Playback is achieved on the Blu-ray disc, with the so-called bridge connector. The bridge contains real-time re-encoded information from a final part of the first connector and a first. -part of the second connector. The MPEG problem is solved by re-coding the last part of the Playback Element-1 and the first part of the Playback Element-2. For a connection without connections, only those source packages that are necessary should be read in the reading buffer. To prevent insufficient flow of the read buffer, the data is stored in the record carrier according to predefined allocation rules including, for example, a minimum block size of data blocks of a real time stream, to allow connection without unions, where the sequences are called extensions. It takes a jump to jump from the end of the Playback Element-1 that corresponds to a first connector, until the start of the Playback Element-2 that corresponds to a second connector. This jump requires some time and during this time interval there is no entry to the reading buffer, while a leak rate still exists because the data is encoded for presentation. To prevent the insufficient flow of the reading buffer, care should be taken that the buffer is sufficiently full to survive the jump. The buffer can be filled enough only if the previous Play Element is long enough to fill the buffer. Hence, to prevent the insufficient flow of reading buffer, each connector must have at least the minimum extension size. A known device problem occurs if the bridge connector, or the remaining part of the first or second connector, does not have the minimum extension size. The connection of those connectors will not be without unions. An object of the invention is to provide a recording system that allows to edit real-time data and create connections without joints, and at the same time maintain the layer structure of the file system and the control information of the application. For this purpose, in the recording device, as described in the introductory paragraph, the file subsystem is arranged to copy additional units of real-time information from a part of the first connector stream, before the final part of the first connector and / or part of the flow of the second connector, after the initial part of the second connector, to create the bridge connector flow having at least the predefined extension length, and the application subsystem is arranged to adapt the control information of the application, to gain access to the flow of the bridge connector, including the units copied additionally. . - The measures taken in the invention have the following effect. The file subsystem is aware of the real-time information actually recorded that is in the files of the flow, and has the task of maintaining the allocation rules. The file system allows to achieve the necessary extension sizes, by copying the additional units. The control information of the application is adapted to, during the representation of the real-time information, to gain access to the flow of the bridge connector including the copied units. This has the advantage that a seamless connection is created through the bridge connector and the additionally copied units. In one embodiment of the device, the file subsystem is arranged to provide access information to the application subsystem to indicate the location of the additionally copied units. This has the advantage that the application subsystem can adapt the control information of the application based on the access information. In one embodiment of the device, the file subsystem is arranged to copy the units of the first stream of the connector, before the final part of the first connector and / or the flow units of the second connector after the initial part of the second connector, to create the bridge connector, and the application subsystem is arranged to adapt the application control information to gain access to the bridge connector and skip the flow of the first connector and / or the flow of the second connector. Due to the copying of the remaining units of a flow to the bridge connector flow, the first or second original connectors do not need to be read. This has the advantage that even in the case of short connectors, a seamless connection is achieved. These and other aspects of the invention will be apparent and elucidated with reference to the later embodiments in the description of the figures, in which: Figure 1 shows an embodiment of the apparatus, Figures 2a-2b show the recording of information blocks in areas of fragments in the record carrier, Figure 3 shows the beginning of the reproduction of a video information signal, Figure 4 shows the principle of editing video information signals, Figure 5 shows the beginning of the "Simultaneous" playback and recording, Figures 6a-6b show a situation during editing, when the generation and recording of a bridge connection information block is not required, Figures 7a-7b show an example of the editing of a video information signal and the generation of a bridge connection information block, in the location of an exit point of the information signal, Figures 8a-8b show another example of the edition of a video information signal and the generation of a bridge connection information block, in the - same location of the exit point as in figure 7, figures 9a-9b show an example of the edition of a video information signal and the generation of a bridge connection information block, in the location of a point input for the information signal, Figure 10 shows an example of the edition of two information signals and the generation of a bridge connection information block, _. _ _ -. Figure 11 shows an example of the edition of two information signals and the generation of a bridge connection information block, where the edition includes the re-coding of part of the information of the two information signals, the figure 12 shows a further elaboration of the apparatus, Figure 13 shows a simplified structure of the application format, Figure 14 shows - "an- illustration of a real playlist and a playlist: irtual, Figure 15 shows an example of the assembly edition, through a seamless connection between two Reproduction Elements, Figure 16 shows an example of an assembly edition, through a connection without connections, between: two Elements of Reproduction. global time axis of a playlist, Figure 18 shows a relation-- between an Element of 'Current Playback and a Previous Playback Element, The Figure 19 shows a Play Element syntax, Figure 20 shows a connection-free connection through a bridge connector, Figure 21 shows an example of Bridge Sequence Information, Figure 22 shows a Sequence Information syntax of Bridges, Figure 23 shows a syntax of a connector information file, Figure 24 shows a Connector Information syntax, Figure 25 shows a 'Sequence Information' syntax, Figure 26 shows a structure of a transport stream of a Blu-Ray Audiovisual Disc (BDAV) in MPEG-2 format, Figure 27 shows extensions and assignment rules, Figure 28 shows a border case of an assignment rule, Figure 29 shows a bridge extension, in where the data of a previous connector stream has been copied, FIG. 30 shows a layered model of a real-time data recording and / or reproducing device, Figure 31 shows a structure of application layers,. The_. -figure 32 shows a bridge with only re-encoded data, Figure .33 shows a bridge with re-encoded data and additionally copied data, Figure 34 shows a flow chart of a method for controlling the recording of real-time information . The corresponding elements in different figures have identical reference numbers. Figure 1 shows an embodiment of the apparatus according to the invention. In the following description of the figures, attention will be focused on the recording, reproduction and editing of a video information signal. However, it should be noted that other types of signals could be equally well processed, such as audio signals or data signals. The apparatus comprises an input terminal 1 for receiving a video signal that is to be recorded on the disk type record carrier 3. Further, the apparatus comprises an output terminal 2 for supplying an information signal of the video carrier of the record carrier 3. The "record carrier 3" is a disk-type record carrier of the magnetic or optical form.The data area of the disk-type record carrier 3 consists of a contiguous interval of Physical sectors, which have corresponding sector addresses, This address space is divided into fragment areas: A fragment area is an adjoining sequence of sectors, with a fixed length. Preferably this length corresponds to a whole number of ECC blocks included in the video information signal to be recorded. The apparatus shown in Figure 1 is broken down into two main parts of the system, namely a disk subsystem 6 that includes recording media and a file subsystem to control the recording media, and a "video recorder subsystem". 8, also called application subsystem. The recording means, a detailed example of which is described in Figure 12, includes a unit for physically scanning the record carrier, such as a read / write head, also called an optical pickup unit, a positioning servo system for position the head on a track, and a disk drive to rotate the record carrier. The following peculiarities characterize the two subsystems: -The disk subsystem can be transparently addressed in terms of logical addresses. Manipulates the handling of defects (including the mapping of logical addresses in physical addresses) autonomously. -For real-time data, the disk subsystem is addressed in a database related to fragments. For data routed in this way, the disk subsystem can guarantee a maximum, sustainable bit rate for reading and / or writing. In the case of simultaneous reading and writing, the disk subsystem manipulates the read / write programming and the placement, in associated buffer, of the flow data, from the independent reading and writing channels. -For non-real time data, the disk subsystem can be addressed on a per sector basis. For data addressed in this manner, the disk subsystem can not guarantee a sustainable bit rate for read or write. -The video recorder subsystem is responsible for the video application, as well as the management of the file system. Hence, the disk subsystem does not interpret any of the data that is recorded in the data area of the disk. In order to achieve real-time playback in all situations, the areas of fragments introduced above need to have a specific size. Also, in a situation where simultaneous recording and playback occurs, the reproduction must be uninterrupted. In the present example, the fragment size is selected to satisfy the following requirement: fragment size = 4 B = 222 bytes Next, the recording of a video information signal will be briefly analyzed, with reference to figure 2. In the video recorder subsystem, the video information signal, which is a real-time signal, is converted into a real-time file, as shown in Figure 2a. A real-time file consists of a sequence of blocks of information signals recorded in areas of corresponding fragments. There is no restriction with respect to the location of the areas of the fragments on the disk and, therefore, any two areas of consecutive fragments, comprising portions of information of the recorded information signal, can be found-anywhere in the logical address space, as shown in Figure 2b. Within each fragment area, eal time data is allocated contiguously. Each real-time file represents a single audiovisual stream (AV). The audiovisual flow data is obtained by concatenating the fragment data in the sequence order of the file. Subsequently, the reproduction of a video information signal recorded in the record carrier will be briefly analyzed, with reference to figure 3. The reproduction of a video information signal recorded in the record carrier is controlled by what is known as "reproduction control program" (PBC program). In general, each PBC program defines a (new) playback sequence. This is a sequence of fragment areas that have, for each fragment area, a specification of a data segment that has to be read from that fragment. In this respect reference is made to Figure 3, wherein the reproduction is shown only as a portion of the first three areas of fragments in the sequence of fragment areas in Figure 3. A segment may be a complete fragment area, but in general it will be only part of the fragment's area. (The latter usually occurs around the transition from somewhere in an original recording to the next part of the same recording or other recording, as a result of editing). Note that the simple linear reproduction of an original recording can be considered as a special case of PBC program: in this case the playback sequence is defined as the sequence of fragment areas in the real-time file, where each segment is a full fragment area, except probably for the segment that is in the last fragment area of the file. For the areas of fragments in a reproduction sequence there is no restriction on the location of the fragment areas and therefore any two consecutive fragment areas can be found anywhere in the logical address space. Subsequently, the editing of one or more video information signals recorded on the record carrier will be briefly discussed below with reference to Figure 4. Figure 4 shows two video information signals previously recorded on the record carrier 3, indicated by two sequences of fragments called "file A" and "file B". To make an edited version of one or more previously recorded video information signals, a new PBC program must be made to define the edited AV sequence. This new PBC program thus defines a new AV sequence obtained by the concatenation of parts of previous AV recordings, in a new order. The parts can be from the same recording or from different recordings. In order to play-a-p'rógramá PBC, data from several parts of (one or more) real-time files, have to be fed to a decoded. This implies that a new data flow is obtained by concatenating parts of the flows represented by "each - real-time file." In figure 4 this is illustrated for a PBC program that uses three parts, one from file A and two from file B Figure 4 shows that the edited version starts at a point i in the area of the fragment f (i) in the sequence of areas of 'fragments of figure A and continues to point P2 in the new fragment area f (i) + 1) from file A. Subsequently, the playback jumps through point P in the fragment area f (j) in file B and continues to point P4 in the fragment area f (j + 2) in file B. Subsequently, the playback jumps through point P5 in the same file B, which can be a previous point in the sequence of fragment areas of file B compared to point P3, or a later point in the sequence, compared to the point P4, after which a condition for reproduction will be analyzed ion without junctions during simultaneous recording. In general, seamless reproduction of PBC programs can only be performed under certain conditions. The most severe condition is required to ensure seamless reproduction while simultaneous recording is carried out. A simple condition will be introduced for this purpose. It is a restriction on the length of the data segments that occur in the playback sequences, as follows. In order to ensure simultaneous playback, without joins, of a PBC program, the playback sequence defined by the PBC program shall be such that the length of the segment in all the fragments (except the first and last fragment area) satisfies the following: 2 MB = segment length = 4 MB The use of fragment areas allows us to consider the requirements for operation in the worst case, in terms of areas of fragments and segments (the signal blocks stored in the fragment areas) only, as will be described later. This is based on the fact that it is guaranteed that individual logical fragment areas, and therefore data segments within fragment areas, are physically contiguous on the disk, even after performing a new mapping due to defects. However, between areas of fragments there is no such guarantee: the areas of logically consecutive fragments can be arbitrarily located on the disk. As a result of this, the analysis of the operating requirements focuses on the following: a. For reproduction, it is considered that a data stream is read from a sequence of segments on the disk. Each segment is contiguous and has an arbitrary length between 2 MB and 4 MB, but the segments have arbitrary locations on the disk. b. For recording, it is considered that a data stream will be written in a sequence of 4 MB fragment areas on the disk. Fragment areas have arbitrary locations on the disk. Note that for reproduction the length of the segment is flexible. This corresponds to the condition of the segment for playback without joints during simultaneous recording. However, for recording, areas of complete segments with fixed lengths are written. Given a data stream for recording and playback, attention will now be focused on the disk subsystem during simultaneous recording and playback. It is assumed that the video recorder subsystem delivers a sequence of segment addresses for both the recording and the playback stream, well in advance. For simultaneous recording and playback, the disk subsystem must be able to intersperse actions from. reading and writing, such that the recording and playback channels can guarantee sustained operation at maximum speed without excessive flow or insufficient flow in the buffer. In general, different read / write programming algorithms can be used to achieve this. However there are strong reasons for performing 'programming in such a way that the reading / writing cycle time, at maximum speeds, is as short as possible: Shorter cycle times' involve buffer sizes Minor, for the read and write buffer, and therefore for the total memory in the disk subsystem.-Shorter cycle times imply shorter response times for user actions. As an example of the response time, consider a situation in which the user is performing simultaneous recording and playback and suddenly wants to start playback from a new position. In order to maintain the total response time of the device (visible to the user on the screen), as short as possible, it is important that the disk subsystem can start supplying the flow data from the new position, as soon as possible. may be possible. Of course this must be done in such a way that, once the supply has started, the reproduction without joints is guaranteed at the maximum speed. Also, the writing must continue uninterrupted with a guaranteed performance. For the analysis in the present, a programming approach based on a cycle in which a complete fragment area is written is assumed. For the analysis of the subsequent disk unit parameters, it is sufficient to consider the minimum cycle time under the worst case conditions. That worst-case cycle consists of a writing interval in which a 4-MB segment is written, and a reading interval in which at least 4 MB is read, divided by one or more segments. The cycle includes at least two jumps (to and from the writing location), and possibly more, because the lengths of the segments for reading are flexible and can be less than 4MB.

This may result in additional breaks from one reading segment location to another. However, since the reading segments are not less than 2 MB, it does not take more than two additional steps to collect a total of 4 MB. Therefore, a worst-case reading / writing cycle has a total of four jumps, as illustrated in Figure 5. In this figure x denotes the last part of a reading segment, and denotes a full reading segment, with a length between 2 MB and 4 MB, and z denotes the first part of a reading segment and the total size of x, and z is again 4 MB in the present example. In general, the required disk unit parameters, in order to achieve guaranteed performance, for simultaneous recording and reproduction, depends on major design decisions, such as rotation mode, etc. These decisions in turn depend on the characteristics of the media. The conditions formulated above for the reproduction without joints, during the simultaneous recording, are derived in such a way that they can be satisfied by different designs with realistic parameters. In order to show this, the example of a CLV (constant linear velocity) disk drive design is analyzed. In the case of a CLV design, the transfer rates for reading and writing are the same and independent of the physical location on the disk. Therefore, the worst-case cycle, described above, can be analyzed in terms of only two disk unit parameters: the transfer rate R and the access time only input, in the worst case, t. The access time in the worst case t is the maximum time between the end of the transfer of data in one location and the start of the transfer of data in another location, for any pair of locations in the data area of the disk . This time covers the speed of disk acceleration / deceleration, rotational latency, possible retries, etc., but not processing delays, etc. For the worst-case cycle described in the previous section, all jumps can be the worst-case jumps with a duration t. This gives the following expression for the worst-case cycle time: Tmax = 2F / Rt + 4.t where F is the size of the fragment: F = 4 MB = 33.6.106 bits. In order to guarantee sustainable operation at the maximum speed of user R, the following must be fulfilled: F = R.Tmax This produces: R = F / Tmax = Rt.F / 2 (F + 2Rt.T) As an example, with Rt = 35 Mbps and t = 500 ms, we would obtain: R = 8. 57 Mbps. Subsequently, the edition will be further described. The creation of a new PBC program or the existing PBC program edition usually results in a new playback sequence. The goal is to ensure that the result can be reproduced without joints under all circumstances even during simultaneous recording. We will analyze a series of examples where it is assumed that the user's intention is to produce a new AV flux between one or two existing AV flows. The examples will be analyzed in terms of two flows A and B, where the user's intention is to produce a transition from A to B. This is illustrated in Figure 6 where a is the point of departure sought from flow A and in where B is the intended entry point to flow B. Figure 6a shows the sequence of fragment areas, f (il), f (i), f (i + l), f (i + 2), .. .. from flow A and figure 6b shows the sequence of fragment areas .-, f (jl), f (j), f (j + l), f (j + 2), ... From flow B The edited video information signal consists of the portion of the stream A that precedes the exit point a in the fragment area f (i + l), and the portion of the stream B that starts from the entry point b in the area of the fragment f (j).

This is a general case that covers all editions of the cut and paste type, including the annexation of two flows, etc. It also covers the special case where A and B are equal. Depending on the relative position of a and b, this special case corresponds to PBC effects such as dodging part of a flow or repeating part of a flow. The analysis of the examples focuses on the achievement of the capacity of reproduction without unions, during simultaneous recording. The condition for the reproduction capability without joints is the condition of the length of the segment in the length of the signal information blocks stored in the fragment areas, which was previously analyzed. It will be shown later that, if flows A and B satisfy the segment length condition, then a new flow can be defined such that it also satisfies the segment length condition. In this way, the flows that can be reproduced without -unions can be edited to obtain new flows that can be reproduced without unions. Since the original recordings can be reproduced without joints by construction, this implies that any edited flow can be reproduced without joints. As a result it is also possible to arbitrarily edit previously edited streams. Therefore the flows A and B in the analysis do not need to be original recordings: these can be arbitrary results of previous virtual editing steps. In a first example, a simplified assumption will be made about the AV encoding format and the choice of the exit and entry points. It is assumed that points a and b are such that, from the point of view of the AV coding format, it would be possible to make a direct transition. In other words, it is assumed that the direct concatenation of the data from flow A (which ends at the exit point a) and the data from flow B (which starts from entry point b) results in a valid flow, as far as the AV encoding format is concerned. The above assumption implies that in principle a new reproduction sequence can be defined based on the existing segments. However, for the ability to reproduce without joints in the transition from A to B, you must be sure that all segments satisfy the segment length condition. Focus attention on flow A and see how this is secured. Consider the fragment area of flow A that contains the exit point a. Let s be the segment in this fragment area, which ends at point a, see figure 6a. If l (s), the length of s, is at least 2 MB, then this segment can be used in the new reproduction sequence and point a is the exit point that should be stored in the PBC program.

However, if l (s) is less than 2 MB, then the resulting segment s does not satisfy the segment length condition. This is shown in Figure 7. In this case a new fragment area is created, the one known as bridging fragment area f 'in this -fragment area, a bridge connection segment comprising a copy of s preceded by a copy of some preceding data in flow A. For this, consider the original segment r preceding it in flow A, shown in figure 7a. Now, depending on the length of r, the segment stored in the fragment area f (i), either all or part of r is copied into the new fragment area f: If l (r) + l (s) = 4 MB, then all r is copied to f, and the original segment r is not used in the new playback sequence, 'such as. is illustrated in Figure 7a. More specifically, the new exit point is the point denoted by ', and this new departure point a' is stored in the PBC program, and subsequently, after having finished the editing step, it is recorded in the registration carrier of disk type. In this way, in response to this PBC program, during the reproduction of the information stream - of edited video, after having read the information stored in the fragment area f (il), the program jumps to the connection fragment area .by bridge f ', - to reproduce the information stored in the bridge connection fragment area f, and then jump to the entry point in video stream B to reproduce the portion of flow B, as shown schematically in Figure 7b. If l (r) + l (s) > 4 MB, then a certain part p from the end of r is copied to f, where the length p is such that 2 MB is obtained < l (r) - l (p) < 4 MB? 2 MB < l (p) + l (s) < 4 MB Reference is made to Figures 8a-8b, wherein Figure 8a shows the original flow A and Figure 8b shows the edited flow A with the bridge connection fragment area f '. In the new reproduction sequence, only a smaller segment r 'is now used in the fragment area f (i) that contains r. This new segment r 'is a subsegment of r, that is, the first part of r with the length l (r') = l (r) - l (p). In addition, a new departure point a 'is required, which indicates the position in which the original flow A should move away, for a jump to the bridging fragment f'. This new output position should then be stored in the PBC program, and stored later on the disk. In the example provided above, we analyzed how to create a bridge connection segment (or a block of bridge connection information) for the fragment area f, in which case the last segment in flow A (ie s) is it's too short Focus attention now on the flow B. In the flow B there is a similar situation for the segment that contains the entry point b, see figure 9. Figure 9a shows the original flow B and figure 9b shows the flow edited. Let t be the segment comprising the entry point b. If t becomes too short, a bridge connection segment g can be created to store it in a corresponding bridge connection fragment area. Analogous to the situation for the bridged connection fragment area f, g will consist of a copy of t plus a copy of some more data of flow B. This data is taken from the original segment u that follows t in the fragment area f (j + l) in flow B. Depending on the length of u, either all or part of u is copied in g. This is analogous to the situation for r described in the previous example. The different cases will not be described in detail, but Figure 9b provides the idea by illustrating the analogy of Figure 8 where u is divided into v and u '. This results in a new entry point b 'in flow B, to be stored in the PBC program and, subsequently, in the record carrier; The next example, described with reference to figure 10, shows how a new sequence that can be reproduced without joints, can be defined under all circumstances, creating at most two fragments of bridge connection (f and g). It can be shown that, in effect, an area of bridge connection fragment is sufficient, even if both s and t are too short. This is achieved if both s and t are copied into a single bridge fragment area. This will not be described extensively here, but Figure 10 shows the general result. In the examples described above it was assumed that the concatenation of flow data at the entry and exit points, a and b, was sufficient to create a valid AV flow. In general, however, some re-encoding has to be done in order to create a valid AV stream. This is usually the case if the exit and entry points are not in the GOP boundaries, when the encoded video information signal is a video information signal encoded in MPEG. The re-encoding will not be analyzed here, but the general result will be that a certain sequence of bridges is needed to go from flow A to flow B. As a consequence there will be a new exit point a 'and a new entry point b' , and the sequence of bridges will contain re-encoded data that correspond to the original images of a 'aa, followed by the original images of bab'. Not all cases will be described in detail here, but the total result is the same as in the previous examples: there will be one or more bridging fragments to cover the transition from A to B. Unlike the previous examples, the The data in the bridge connection fragments are now a combination of re-encoded data and some additional data from the original segments. Figure 11 provides the general appearance of this. As a final observation, note that no special restrictions have to be imposed on the re-encoded data. The re-encoded stream data simply has to satisfy the same bit rate requirements as the original stream data. Figure 12 shows a schematic version of the apparatus in greater detail. The apparatus comprises a signal processing unit 100 which is incorporated in the subsystem 8 of FIG. 1. The signal processing unit 100 receives the video information signal through the input terminal 1 and processes the information of the signal. video in a channel signal to record the channel signal in the disk type record carrier 3. In addition, a read / write unit 102 is available which is incorporated in the disk subsystem 6. The read / write unit 102 comprises a read / write head 104, which in the present example is an optical read / write head for reading / writing the channel signal in and from the record carrier 3. In addition, positioning means are present. 106 to locate the head 104 in a radial direction through the record carrier 103. A read / write amplifier 108 is present in order to amplify the signal to be recorded. and amplify the read signal of the registration carrier 3. A motor 110 is available to rotate the registration carrier 3 in response to a motor control signal supplied by a signal generating unit to control the motor 112. A microprocessor 114 is present to control all circuits through control lines 116, 118 and 120. Signal processing unit 100 is adapted to convert the received video information through input terminal 1 into blocks of information of the channel signal that has a specific size. The size of the information blocks (which is the segment mentioned above) can be variable, but the size is such that it satisfies - the following relationship:. · -. - "| SFA / 2 < size of a block of the channel signal = SFA, where SFA is equal to the fixed size of the fragment areas. In the example given above, SFA = 4 MB. The writing unit 102 is adapted to write an information block of the channel signal -in uri. fragment area in the record carrier. In order to allow editing of the video information recorded in a previous recording step, in the record carrier 3, the apparatus is further provided with an input unit 130 to receive an output position in a first signal of video information recorded on the record carrier and to receive an entry position on a second video information signal recorded on that same record carrier. The second information signal may be the same as the first information signal. In addition, the apparatus comprises a memory 132, for storing information related to the output and input positions. In addition, the apparatus comprises a bridge connection block generating unit 134, incorporated in the signal processing unit 100, for generating at least one block of bridge connection information (or bridge connection segment) of a specific size. As explained above, the bridge connection information block comprises information of at least one of the first and second video information signals, information that is located before the output position in the first video information signal and / or after the entry position in the second video information signal. During the editing, as described above, one or more bridge connection segments are generated in the unit 134 and in the editing step, the one or more bridge connection segment (s) is (are) encoded in the register carrier 3 in a corresponding fragment. The size of the at least one block of bridge connection information also satisfies the relationship: SFA / 2 = size of a bridge connection information block = SFA. In addition, the PBC programs obtained in the editing step can be stored in a memory incorporated in the microprocessor 114, or in another memory incorporated in the apparatus. The program created in the editing step for the edited video information signal will be recorded in the record carrier, after the editing step has been completed. In this way, the edited video information signal can be reproduced by means of a direct playback device, retrieving the PBC program from the record carrier and reproducing the edited video information signal, using the PBC program corresponding to the Edited video information signal. In this way an edited version can be obtained, without portions of re-encoding the first and / or second video information signal, but simply generating and recording one or more -bridge connection segments in fragment areas (connection by bridge), in the -registration carrier. In the following part we analyze a practical modality of a high density disc recording format called Rewritable Blu-ray Disc Format, used to record audio-video streams (BDAV). In the modality, the allocation rules for recording real-time data in extensions and application control information are described. Figure 13 shows a simplified structure of the application format. The figure is used to explain basic concepts about the recording application format of the MPEG-2 transport stream. The figure describes a simplified structure of the application format. The application format shows application control information 130, including two layers for handling AV stream files, which are Play List 134 'and Connector 131. The BDAV Information Controller manages the Connectors and Playlists in a BDAV directory. Each pair of an AV flow file and its attribute is considered an object. The AV stream file is called an AV stream file from Connector 136 or an AV stream file from the Bridge Connector, and the attribute, is called Connector Information File 137. Each object of a Connector AV stream file and its Connector Information file is called a Connector. Each object in an AV Stream file in the Bridge Connector and its Connector Information file is called a Bridge Connector 133. Bridge Connectors are special connectors that are used for a special purpose described later. The AV stream files in the Connector store data that is formatted in an MPEG-2 transport stream, in a structure defined by this document. The structure is called the BDAV MPEG-2 transport stream. The AV stream files of the Connector are normal AV stream files, in this document. An AV stream file of the Connector is created in the BDAV directory, when the recorder encodes analog input signals in an MPEG-2 transport stream and records the stream or when the recorder records a digital input stream. An AV stream file of the Bridge Connector also has the structure of the BDAV MPEG-2 transport stream. The AV stream files in the Bridge Connector are special AV stream files, which are used to make the connection without junctions between two display intervals selected in the Connectors. Generally, the AV stream files of the Bridge Connector have a very small data size compared to the AV stream files of the Connector. The Connector 137 Information file, also called connector information, has the parameters to access the connector flow. In general, a file is considered to be a sequence of data bytes, but the content of the AV stream file (AV Stream Connector or AV Stream Bridge Connector) is developed in a time period. The access points in the AV stream file are mainly specified with a timestamp base. When a time stamp is provided for an access point to the AV stream file, the Connector Information file finds the address information for the position where the player should start reading the data in the AV stream file. An AV stream file has an associated Connector Information file. Connectors are accessed through two types of playlists, a Real Play List 134 and a Virtual Play List 138. Figure 14 shows an illustration of a real playlist and a Virtual Playlist. In general, the Playlist is introduced so that you can easily edit playback intervals in the Connectors that the user wants to play, for example, assembly editing without moving, copying, or deleting the part of the Connectors in the BDAV directory. A Playlist is a collection of playback intervals - in Connectors. Basically a reproduction interval is called a Playback Element and is a pair of INPUT point and OUTPUT point, which indicates the positions, on the time axis, of the Connector. Therefore, a Playlist is a collection of Play Elements. Here the. INPUT point means a starting point of a playback interval, and OUTPUT means an end point of the playback interval. There are two types of Playlist: one is a Real Playlist 134 and the other is a Virtual Playlist 141. The Playlist can only use AV stream files from the connector and can not use AV stream files from the connector. bridge connector. It is considered that the Real Reproduction List comprises the reference parts of the Connectors. In this way, it is considered that the Play List occupies the data space that is equivalent to its reference parts of the Connectors on the disk (the data space is occupied mainly by the AV stream files). When the Real Playlist is deleted, the reference parts of the Connectors are also eliminated. The Virtual Play List 141 may use both the AV stream files of the connector and the AV stream files of the bridge connector 142. The bridge connector 142 contains re-encoded data from a final part of the preceding connector 143 and a part initial 144 of the next connector. The Virtual Playlist is considered not to have the data of the AV stream files of the Connector, but it has the data of the AV stream files of the Bridge Connector if it uses AV stream files from the bridge connector. When the Virtual Playlist that does not use the AV stream files of the Bridge Connector is deleted, the Connectors do not change. When the Virtual Playlist using the AV stream files from the bridge connector is removed, the AV bridge files from the bridge connector and the associated Connector Information files do not change, but the AV stream files from the connector The bridge and the associated Connector Information file, used by the Virtual Playlist, are also deleted. In the concept of "user interface, the Connectors are only internal to the player / recorder system and are not visible to the user interface of the player / recorder system, only the Playlists are displayed to the user. Real Playlists can be used to delete, split or combine connectors, and also to remove part of a connector, however, to edit the connectors and make connections without unions, virtual playlists are used.Figure 15 shows an example of assembly editing, through a seamless connection between two Play Elements in playlist 150 and playlist 151. The figure shows the production of the Playback Elements that the user wants to play, combining the Elements of Playback in a Virtual Play List 152. Figure 16 shows an example of assembly editing, through s a connection-free connection between two Play Elements in Playlist 150 and Playlist 151. The application format supports the production of a presentation without connections, through a connection point between two Play Elements , making a Bridge Connector 162. Since it is possible to reproduce the MPEG video stream, without junctions, at the connection point, normally a small number of images around the connection point must be re-encoded, and the Bridge Connector contains the re-encoded images. This operation does not change the AV stream files of the connector and the associated Connector Information files. A replay operation of the virtual playlist is considered as one of the following actions: Change the INPUT point and / or the OUTPUT point of the Playback Element in the Virtual Playback List, by attaching or inserting a new Playback Element into the Virtual Play List, or removed from the Playback Element in the Virtual Play List. If the user is going to change the INPUT point and / or the OUTPUT point that refers to a Bridge Connector, the recorder should provide a warning and ask the user for the action that the Bridge Connector will be eliminated and needs create a new Bridge Connector to make a seamless connection. If the answer is yes, the recorder can delete the old Bridge Connector and create the new Bridge Connector. It is noted that the audio information can be added to the video through the Virtual Playlist, which is called audio transfer. Figure 17 shows a global time axis of a Playlist. The figure shows a Play List defined by a number of Playback Elements 171, 172, 173. The Playback Element specifies a reproduction interval based on time, from the ENTRY time to the EXIT time. The reproduction interval basically refers to a Connector, and can optionally refer to a Connector and a Bridge Connector. When a Playlist is composed of two or more Playlist elements, the reproduction intervals of these Playlist elements must be placed in an aligned manner without time lapse or overlap, on a Global time axis of the Playlist, such as the picture shows. The Global time axis can be visible at the user interface in the system, and the user can give instructions for a start time of playback on the global time axis for the system, for example that the playback starts 30 minutes after starting on the Playlist. Figure 18 shows a relationship between a current Playback Element and a previous Playback Element. When the connection of two Play Elements is considered, a current Play Element 181 is connected by a connection condition 182 to a Previous Play Element 180. These two Playback Elements appear in the Play List consecutively, and the previous Playback Element is connected immediately forward with the current Playback Element as shown in the figure. The "elapsed_time_of the current Playback Element" means the_INVERENT time from which the current Playback Element has started.The "elapsed_time of the current Playback Element" means the_SALID_time, at which the current Play Element ends. "Pre-Play Element" means the TRAP time in which the previous Play Element starts.The "out_time" of the previous Play Element "means the OUT_time in which the Element ends. Previous reproduction. When the previous Playback Element and current Playback Element are connected in the Playlist, the current Playback Element has a connection condition 182 between the time_INVALUE of the current Playback Element and the_SET time of the Previous Playback Element. The connection_condition field of the current Playback Element indicates the connection condition. When the previous Playback Element and the current Playback Element are connected with a Bridge Connector for a connection without joins, the current Playback Element has an additional set of parameters called Bridge Sequence Information. Figure 19 shows a syntax of the reproduction element. The fields of the Reproduction Element are defined in a first column 190, while the length and type of the fields are defined in a second and third columns. It is noted that the Reproduction Element contains a Bridging Sequence Information field 191 if the con_condition is equal to 3 which indicates a connection without junctions. The Bridge Sequence Information gives a name of the Connector Information file to specify an AV stream file of the Bridge Connector. The Connector Information file for the AV stream file of the Bridge Connector gives information for the connection between the previous Play Element and the current Play Element, as described below with the preceding semantics_Name_File_Internet Connector, SPNoutput from the next Connector, nextConnection Informationfilename and SPNnextNext Connector . The parameters of the Reproduction Element shown in Figure 19 have the following semantics. A length field indicates the number of bytes of the Playback Element () that immediately follows this length field and to the end of the Playback Element (). A Connector_First_File_Information field specifies the name of an Connector information field for the Connector used by the Playback Element. This field must contain the 5-digit "zzzzz" number of the Connector name except the extension. It shall be coded according to ISO 646. The field Connectorflukhotype in the Connector Information of the Connector Information file shall indicate "an AV flow of the BDAV PEG-2 transport stream connector". A field of Connector_coder-decoder_identifier must have a value that indicates the video encoder / decoder, for example the WM2TS "encoded according to ISO 646. The PL_CPI_type in a Playlist indicates (with the decoder_coder-decoder_identifier) a predefined, corresponding map of information of a characteristic point (CPI). the connection condition between the current_inst_time of the current Playback Element and the_out_time of the previous Playback Element.A few predefined values, for example from 1 to 4, are allowed for the_condition_condition.If the Playback Element is the first Element of Playback in the Play List, the connection_condition has no meaning and should be set to 1. If the Playback Element is not the first in the Playlist, the meanings of the connection_condition are additionally defined, in particular a connection_condition = 3 indicates a connection without joints using a bridge connector Figure 20 shows a connection without connections through a bridge connector. A Pre-Play Element 201 is connected to a current Playback Element 202 through a bridge connector 203. A connection without junctions 204 is located on the bridge connector 203. The restrictions in connection_condition = 3 are that the condition is only allowed for predefined types of PL_CPI_type. The condition is only allowed for the Virtual Play List, and the previous Playback Element and the current Playback Element are connected to the Bridge Connector, with a clean break at the connection point. The TIME__FUSE of the Previous Playback Element shall indicate a final time of presentation of the last video presentation unit (in order of presentation) in the first time sequence (ATC) of the AV stream file of the bridge connector specified by the Information of Bridge Sequence of the current Playback Element. The ENTER_Time of the current Playback Element shall indicate the start time of presentation of the first video display unit (in order of presentation) in the second time sequence (ATC) of the AV stream file of the bridge connector specified by the Bridge Sequence Information of the current Playback Element.

Figure 21 shows an example of Bridge Sequence Information. The figure shows a Pre-Play Element in a first (preceding) connector 210 connected to a current Playback Element in a second | (next) connector 211 via a bridge connector 212. The bridge connector 212 has a first sequence of time 213 and a second time sequence 214. The Bridge Sequence Information is an attribute for the current Play Element as described above. The Bridge Sequence Information () contains the Bridge_Name_File_Information_bridge to specify an AV stream file of the Bridge Connector and the associated Connector Information file, and a connector_output_output SPN 215, which is a source packet number of a source packet that is found in the first connector 210 shown in the figure. And the end of the source package is the point where the player leaves the first connector at the start of the AV stream file of the Bridge Connector. This is defined in the Connector Information () of the Bridge Connector. In an SPN_input_to_Next_Connector 216 a source packet number of a source packet is provided in the second Connector 211. And the start of the source packet is the point where the player enters the second connector from the end of the AV stream file of the Bridge Connector . This is defined in the Connector Information () of the Bridge Connector. The AV stream file of the Bridge Connector contains two time sequences (ATC). Note that the first connector 210 and the second connector 211 can be the same Connector. Figure 22 shows a syntax of Information of Bridge sequences. The fields in the Bridge Sequence Information are as follows. A field of Bridge_Counter_format_field_name specifies the name of an information file of the Connector for the Bridge Connector used by the Bridge Sequence Information. The field must contain the 5-digit number wzzzzz "of the connector name except the extension, it must be coded in accordance with ISO 646. A field of the connector flow type in the Connector Information of the Connector information file shall indicate "an AV flux · of the bridge connector of the BDAV MPEG-22 transport stream. h field of Connector_coder-decoder_identifier must identify the codes. Figure 23 shows a file syntax for connector information. The connector information file, for example for a BDAV MPEG-2 transport stream, is composed of six objects defined in fields as shown, and those objects are Connector Information (), Sequence InformationO, Program Information () _, CP (), Connector Mark () and Private Data Markers (). The same 5-digit "zzzzz" number must be used for either the AV stream file (an AV stream file from the Connector or an AV stream file from the Bridge Connector) of the associated information file. The fields are as follows. An indicator_type field must have a predefined value, "M2TS" encoded according to ISO 646. A number_number is a string of four characters that indicates the version number of the Connector Information file. Secuencia_inicio_dirección information indicates the start address of the Sequence Information () in the number of relative bytes from the first byte of the Connector Information file. The relative. Number of bytes starts from zero. A Program_Initial_address information indicates the start address of the Program Information () in the relative number of bytes from the first byte of the Connector Information file. The relative number of bytes starts from zero. A CPI_home_address indicates the address of. Start of the CPI () in the relative number of bytes from the first byte of the Connector Information file. The number relative bytes starts from zero. A Connector_set_address mark indicates the start address of the Connector Mark () in the relative number of bytes from the first byte of the Connector Information file. The relative number of bytes starts from zero. Private Data of Markers_home_address indicates the starting address of the Markers () of Private Data in the number of relative bytes from the first byte of the Connector Information file. The relative number of bytes starts from zero. If this field is set to zero, there is no data for the Private Data of the O Markers. This rule applies only to Private Data of Markers__first_address Fill words should be inserted according to the syntax of .zzzzz.clpi. Each word_fill can have any value. Figure 24 shows an information syntax of the Connector The table in the figure defines the syntax of the Connector Information () in a Connector information file. The Connector Information () stores the attributes of the associated AV stream file (the AV stream of the connector or the AV stream of the Bridge Connector) in. the-following fields. A length field indicates the number. "bytes" of the Connector Information () immediately after this length field and to the end of the Connector Information (). A Type_Stream Connector indicates an AV flow type associated with the Connector Information file, for example Type_Flow_Connector = 2 indicates a bridge connector A coding_condition indicates a transport stream coding condition for the Connector A transcode_mode_signifier indicates a form of recording of MPEG-2 transport streams received from a digital transmitter A control_time_signifier indicates a recording form of "controlled time." A TS_average_time and recording speed TS indicates transport flow rates for the calculation.A field of source_number_packages shall indicate the number of source packets stored in the AV stream file associated with the Connector Information file. field BD_system_use contains the protection information content for the AV stream file associated with the Connector nformation file. If the Connector_type_indicator indicates the Connector is an AV stream file of Bridge Connector, then a precedent_connector_File_Information_Information specifies the name of a Connector Information file associated with an AV stream file of the connector that is connected in advance with the AV stream file of the Connector. bridge connector. This field will contain the 5-digit number "zzzzz" of the Connector name except the extension. The name should be coded according to ISO 646. The Connector indicated by this field is the first Connector 210 shown in Figure 21. A field SPN_out_of_precedent_Connector indicates a number of source packets of a source packet in a Connector specified by the preceding_Name_File_Information_Internet. And the end of the source package is the point where the player leaves the Connector at the beginning of the AV stream file of the connector I bridge. This means that the source packet indicated by the SPN_output_connector is connected to the first source packet of the AV stream file of the bridge connector, as shown in Figure 21. If the Type_Stream Connector indicates-that the Connector is an AV stream file of the Bridge Connector, then the following_Name_File_Internet Connector specifies the name of a Connector Information file associated with an AV stream file of the connector that is connected behind with the AV stream file of the bridge connector. This field will contain the 5-digit number "zzzzz" of the Connector name except the extension. The name will be coded in accordance with ISO 646. The Connector indicated by this field is the second connector 211 shown in Figure 21. An SPN_entra_to_Next_Connector field indicates a source packet number of a source packet in a Connector specified by the following_Name_File_Internet. And the start of the source packet is the point where the player enters the Connector from the end of the AV stream file of the Bridge Connector. This means that the last source packet of the AV stream file of the Bridge Connector is connected to the source package indicated by the SPN_entra_to_Next_Connector, as indicated in Figure 21. Figure 25 shows a sequence information syntax. The Sequence Information stores information to describe time sequences (ATC and STC sequences) for the AV flow file. ATC is based on a timeline in the arrival time of each source packet in the AV stream file. The sequence of source packets that does not include discontinuity based on arrival time (ATC) is called an ATC sequence. When a new recording of an AV stream file from the connector is made, the Connector should not contain discontinuity based on the arrival time, that is, the Connector should only contain an ATC sequence. It is assumed that discontinuities based on the arrival time, in the connector's AV flow file, can occur only in the case that parts of the Connector's AV flow are eliminated by editing and the necessary parts originated from it. Connector itself are combined into a new AV stream file of the Connector. The Sequence Information () stores addresses when the bases of the arrival time begin. The SPN_ATC_inicio indicates the address. The first source packet of the ATC sequence shall be the first source pack of an aligned unit. A source packet sequence that does not include discontinuity STC (clock discontinuity based on system time) is called an STC sequence. The 33-bit counter of the STC can be wrapped in the STC sequence. The Sequence Information () stores addresses where the system time bases begin.The SPN_STC_starts indicates the address The STC sequence except the last one in the AV stream file starts from the "source" package indicated by SPN_STC_start, and ends at the source package immediately before the source package indicated by the next SPN_STC_start. The last STC sequence starts from the source package indicated by the last SPN_STC_start, and ends in the last source packet. No STC sequence can overlap with the border of the ATC sequence. The fields in the Sequence Information are as follows. A length field indicates the number of bytes of the Sequence Information () that immediately follow this length field and until the end of the Sequence Information (). Number_of_ATC_sequences indicates the number of ATC sequences in the AV stream file (AV stream file of the connector or AV stream file of the Bridge Connector). An SPNATCinicio [atcid] field indicates a source packet number of a source packet where the ATC sequence indicated by atc_id starts in the AV stream file. A field of number_of_STC_sequences [atc_id] indicates the number of STC sequences in the ATC sequence indicated by the atc_id. a shiftfield_stc_id_ [atc_id] indicates the shift stc_id value for the first STC sequence in the ATC sequence indicated by the atc_id. A field of SPN_STC_start [atc_id] [stc_id] indicates a source packet number of a source packet, where it starts the STC sequence indicated by the stc_id in the ATC sequence indicated by the atc_id. A presentation_time_initial field [atc_id] [stc_id] indicates a start time for displaying the AV stream data for the STC sequence indicated by the stc_id in the ATC sequence indicated by the atc_id. A presentation field_fin_time [atc_id] [stc_id] indicates an end time of presentation of the AV stream data for the STC sequence indicated by the stc_id in the AT sequence indicated by the atc_id. Presentation times are measured in units of a 45 kHz clock of the STC sequence or the STC sequence. Additional details about the time sequence are described in the Blu-Ray Disc format. Figure 26 shows a structure of a BDAV MPEG-2 transport stream. The AV stream files have the structure of the BDAV-MPEG-2 transport stream. - E '' BDAV MPEG-2 transport stream is constructed from an integer number of aligned units 261. The size of an aligned unit is 6144 bytes, which corresponds to 3 data blocks of 2048 bytes. The aligned unit starts from the first byte of source packets 262. The length 'of a source packet is 192 bytes. A source pack 263 consists of a TP_extra_header and a transport packet. The length of the TP_extra_header - is 4 bytes and the length of the transport packet is 188 bytes. -An aligned unit consists of 32 source packets 261. The last unit aligned in the BDAV MPEG-2 transport stream also consists of 32 source packets. In this way, the BDAV MPEG-2 transport stream ends at the end of an aligned drive. If the last aligned unit is not completely filled with an input transport stream that is to be recorded in the volume, the remaining bytes must be filled with source packets with null packets (transport packet -with PID = OxlFFF). The invention seeks to provide means for allowing a seamless connection and maintaining the structure of the Play List that applies timing information as described above. The Connector Information, of a Bridge Connector in accordance with the invention, contains the SPN of the last source packet that has to be read in the previous Reproduction Element and contains the SPN where it must start reading the Playback Element. current . Now, the procedure to create a bridge connector is as follows. The Play List is selected, and the Play Elements are investigated. If there is a connection = 3 between two Play Elements, then it is known that the connection is achieved with a bridge connector. In this way, there is a reference to the name of the bridge connector, as indicated in Figure 19. The Connector Information of this bridge connector has the SPN output of the preceding connector and the SPN input to the next connector, as shown in Figure 1. indicated in Figure 24. On the Blu-Ray Disc there is an assignment rule that indicates that each contiguous extension must have a minimum size of N (for example N = 12 MB). When editing with a sequence of bridges, it is necessary to ensure that the extension before the bridge sequence, the bridge sequence itself and the segment after the bridge sequence, satisfy all the minimum extension size. The minimum extension size is achieved through the file system by copying additional source packets from the preceding and / or following connector to the bridge as explained in later embodiments. Figure - 27 shows extensions and allocation rules. A first flow file of a first connector is stored in a first extension 271, which complies with the assignment rule that the length is = N. A second flow file of a second connector is stored in a second one - extension 272, which also complies with the assignment rule that the length is = N. A file of the bridge connector stream is stored in a third extension 273, which also complies with the assignment rule that the length is = · N. | Figure .28 shows a border case of an assignment rule. A first flow file of a first connector is stored in a first extension 281, which barely complies with the assignment rule because the length is approximately N. A second flow file of a second connector is stored in a second extension 282, which also barely complies with the assignment rule because the length is approximately N. A bridge connector stream file is stored on a third extension 273, which also barely complies with the assignment rule because the length is approximately N. Note that with an addressing scheme based on source packet numbers (as indicated in the figure) this does not represent a problem because the lengths of the extensions should be based on the source packets. However, the jump to / from the connection must be addressed using time indicators as discussed above, and the CPI is used to resolve the time for the location of the source packets. Hence, the points in the CPI determine where the jump should be made. Due to the CPI in the current situation there is a need to either copy more or less data from the original flows to the bridge, any of them will violate the assignment rule. In one embodiment of the invention one of the extensions is copied from the original sequence to the connection, which is shown in the following figure. Figure 29 shows a bridge extension where data from a previous connector stream has been copied. A pre-connector stream 291 has been completely copied to a bridge stream file in a first portion 294 of a bridge 293. A re-encoded part 295 of the bridge stream file is smaller than the minimum extension size N , but the allocation rules are not violated due to the immediately preceding part 294. It should be noted that also the next connector 292, or both connectors, could have been copied to the bridge. In fact, depending on how the assignment is made, the result could be much worse. If the assignment is in fact done in blocks of N then, when the bridge is created, there is a need to copy either substantially an entire extension or none of it. However, CPI locations are based on video content. The CPI locations are not related to the assignment extensions, so that in general the CPI points will never correspond to the beginning of an assignment extension. In one embodiment, the problem is much more severe in an allocation scheme where the minimum size of allocation extension is equal to the size of the fragment. In one embodiment, an addressing scheme based on copying source packages is used. In general, it may be necessary, in certain cases, to copy more extensions in the bridge sequence. Through the use of packet-based addressing, the number of instances of copying full extensions is reduced to a minimum. The copying of additional data to the bridge is explained in detail in the following part. Figure 30 shows a layered model of a real-time data recording and / or reproducing device. In a user interface layer 301, a user of the device is provided with information regarding the state of the device, and controls, for example, a screen, buttons, a cursor, etc. In an application layer 302 files are made, and stored / retrieved through a layer of the 303 file system. Addressing within the files is based on the number of bytes for the data files and source packets for real-time files (audio and video files). In the File System layer (FS) the files are assigned in logic blocks of the logical volume, tables are kept in the file system layer with the mapping of the files in the address space A physical layer 304 takes over the translation of logical block numbers into physical addresses and interconnects with the record carrier 305 to write and read blocks of data based on the physical addresses. application 302 an application layer structure is applied.Figure 31 shows an application layer structure.There is a PlayList 310 layer and a Connector layer 311. A PlayList 312 concatenates a number of Playback Elements 313. Each Playback Element contains an ENTRY time and an EXIT time and a reference to the Connector 314 file. Addressing in the Playlist of the Playlist It is based on time. Addressing in the Connector layer to a file 315 is based on numbers of source packets to indicate parts 316, 317 that are to be reproduced from the connector stream. Using the Connector Information file 314 translates the time base to the location in the 315 flow file. Now you know what parts of the flow file should be read. The application sends a message to the File System (FS) with the numbers of source packages that have been read. The FS translates this into logical blocks that have to be read. An instruction to physical layer 304 is provided to read and send back these logic blocks. When two parts of one (or two different) connector (s) are going to be presented one after the other, this is usually called editing. During a presentation without unions such · transition in general is not made. To have a seamless transition, for example, the following restrictions must be satisfied: the MPEG data must be continuous (for example, closed GOPs at the end of the Playback Element-1 and at the beginning of the Playback Element-2), there must be no flow insufficient, or excessive, intermediate, of the decoding buffer, in the MPEG decoder), and there must not be an insufficient, intermediate, read flow. As explained above, the presentation without joints by connecting two Play Elements is done in the BD with the so-called bridge. The MPEG problem is solved by re-coding the last part of the Playback Element-1 and the first part of the Playback Element-2. Figure 32 shows a bridge with only re-encoded data. In a first Playback Element 321 an exit time is set, for example selected by the user, and in a second Playback Element 322 an entry time is set. A final part 324 before the Exit Time is re-encoded starting,. for example, at time A "," resulting in re-coded data 326 constituting a first part of a bridge 320. An initial part 325 after the entry time is re-encoded, for example, starting at time B , resulting in re-coded data 326 constituting a second part of the bridge 320. The re-encoding is carried out in the application layer If the Play Element-1 is now read to A then the bridge is read and the Playback Element-2 starts at B, then the MPEG data is continuous, however, a jump must be made at A and B. This jump requires some time and during this time interval there are no entries to the reading buffer and meanwhile there is still a leak rate.To prevent the insufficient flow of the reading buffer, care must be taken that the buffer is sufficiently full to survive the jump. The media may be sufficiently full only if the previous Play Element is long enough to fill the buffer. In general, the bridge may be too short to fill the read buffer, which may cause insufficient flow in the read buffer. Continuous data flow is performed on the Blu-Ray Disc with allocation rules, which includes the length requirements for the extensions that store the flow data. The assignment rules are carried out in the File System (FS) layer. In the FS layer, nothing is known about MPEG. Figure 33 shows a bridge with re-encoded data and additionally copied data. Figure 33 shows the same data elements of the flow as shown in Figure 32. However, in addition, a number of units of the first Playback Element 321 and / or of the second Playback Element 322 is copied to the bridge 320 to provide a Bridge flow file that has at least the minimum length according to the allocation rules. In the figure a first number of units 331 is copied from the first Playback Element 321 to the bridge, as additionally copied units 332, and a second number of units 333 is copied from the second Playback Element 322 to the bridge as additionally copied units 334. The amount of data that is copied depends only on the size of the extensions and not on the boundaries of MPEG GOPs. Note that points A and B are no longer related at the GOP borders but are related to source packet numbers as shown in Figure 24. Usually logical blocks (LB) are aligned in error correction blocks (32 LB in an ECC block). The ECC block is the smallest physical block that can be written or read. In one modality the source packages of the files are in aligned units and in LB (32 source packages in one aligned unit and 3 LB in one aligned unit), as shown in figure 26. In a modality points A and B are fixed at the borders of an ECC block. A combination of the packet alignment and the ECC boundary results in a point selected for A or B once every 3 ECC blocks. It is observed that the data encryption, which is common in the transmission and storage of data, is also aligned in Aligned Units. Of course the adjustment points A and B aligned as indicated are advantageous in combination with the encryption. It is noted that a packet-based addressing scheme is used for the bridge. In the FS layer the presentation time is not known. Points A and B are not aligned with CPI entries (GOP borders). Points A and B can not be entered directly into the Playback Element because the indicators of the Playback Element are based on time. Therefore the application layer will enter the location of the copied data additionally into the Connector layer (in the Bridge Connector Information, as shown in Figure 24). During Playback, a Playlist is played with the. Play Elements 1-2. The connection-between condition - these Playback Elements indicates that there is a bridge for presentation without joints. The Bridge Connector Information contains the addresses of points A and B. The application layer asks the FS layer to play Connector-1 to point A and then starts with the bridge connector. The FS layer asks the physical layer to read the corresponding LBs.

In one mode, a message is transferred from the FS layer to the Connector layer to indicate the additionally copied data. The application layer stores the packet-based addresses in the Connector Information. It should be noted that the FS layer did not receive a direct instruction to copy data from the preceding connectors and / or subsequent connectors, but autonomously decides to copy additional data, and subsequently reports to the application layer by sending the message. In a practical embodiment, the response of the FS layer to an instruction from the application layer, relating to storing a bridge connector, may include the message. Figure 34 shows a flow chart of a method for controlling the recording of real-time information. The method serves to be executed in a computer program, for example in a main computer that controls a recording device, but can also be implemented (partially) in the recording device in dedicated circuits, in state machines or in a microcontroller and in unalterable memory programs. The method has the following steps which lead to a final step of RECORDING 248 in which instructions are given to a recording unit to actually record the real-time information in blocks of data based on logical addresses. In an initial step of ENTRY 341 the real-time information is received, for example, from a transmission or from a video camera of the user. The real-time information is packaged in units that have unit numbers, for example the source packages and the numbers described above. In an APPLICATION step 342 the application control information is created and adapted. The control information includes connectors of the real-time information, wherein a connector comprises a connector information to access a connector stream of the real-time information units through the unit numbers, and a Play List , wherein the Play List comprises a Playback Element and the Playback Element indicates a part to be reproduced, of the real time information in the connector, and the Playback List indicates in which order they have to be reproduced. Elements of Reproduction. The connectors and the Playlist have been described above with reference to Figures 13-17. In a next step of CREATE BRIDGE 343 a bridge connector is created to link a first and a second Playback Elements through the bridge connector in response to a user edit instruction. The stream of the bridge connector contains real-time re-encoded information based on a final part of the first connector and a start portion of the second connector, as explained in relation to FIG. 32. In a next step of FILE MGT 344 instructs a file system to store the real-time information and the corresponding application control information, created in steps 342 and 343. The file system step further includes retrieving ASSIGNMENT RULES 345 of a memory for store the real-time information in blocks of data. Assignment rules 345 include a rule for storing a stream of real-time information that must be reproduced without joins in a sequence of consecutive data block extensions, wherein the extensions have at least one predefined extension length. The file system checks the lengths of the extensions based on the original application control information. If the lengths of the extensions comply with the rules, the recording step 348 is entered directly as indicated by line 349. If the lengths of the extensions violate the rules for assigning the minimum extension length, a next step of COPY 346 is entered. Additional real-time information units are copied from preceding and / or following connector flow files as described above, for example in relation to FIGS. 29 and 33. By copying additional real-time information units from a portion of the first stream of the connector before the end portion of the first connector and / or a portion of the stream of the second connector. , after the initial part of the second connector, the flow of the bridge connector is adapted to have at least the predefined extension length. In a next step of ADAPTATE 347 the application control information is updated to achieve access (during playback) of the bridge connector stream that includes those additionally copied units. The file system reports the locations of the additionally copied units to the application management system to adapt the application control information as described above, for example in relation to FIG. 24. Although the invention has been described with reference To preferred embodiments thereof, in particular the Blu-Ray disc format, it should be understood that these are not limiting examples. For example, the record carrier may alternatively be of magneto-optical or magnetic type. In this manner, various modifications may be apparent to those skilled in the art, without departing from the scope of the invention, as defined by the claims. In addition, the invention resides in each and every one of the novel characteristics or combinations of characteristics. The invention can be implemented both by physical computing elements (hardware) and by sets of computer programs (software), and the different "means" can be represented by the same hardware element. In addition, the word "comprising" does not exclude the presence of other elements or steps different from those listed in the claims.

It is noted that in relation to this date, the best method known to the applicant to carry out the aforementioned invention is that which is clear from the present description of the invention.

Claims (9)

2. Having described the invention as above, the content of the following claims is claimed as property: 1. The device for recording real-time information in a record carrier, the device is characterized by: -recording means for recording blocks of data in base to logical addresses in the record carrier, -a file subsystem for storing real-time information in units that have unit numbers (SPN) in the data blocks, "according to predefined allocation rules, where the rules they include storing a stream of real-time information to be reproduced without junctions in a sequence of consecutive data block extensions, the extensions have at least one predefined extension length, and an application subsystem for handling control information. application, the application control information includes - at least one information connector In real-time, the connector comprises a connector information to gain access to a connector stream of the real-time information units through the unit numbers, -at least one playlist, the playlist comprises the less a reproduction element, the reproduction element indicates a part to be reproduced, of the real-time information, in the connector, the reproduction list indicates in what order the reproduction elements have to be reproduced, and -al minus a bridge connector for linking a first and a second playback element via the bridge connector, a stream of the bridge connector comprising re-encoded real-time information based on a final part of the first connector and an initial part of the second connector, -the file subsystem is arranged to copy additional units of real-time information, from a part of the flow of the first "connector before the end part of the first connector and / or part of the flow of the second connector, after the initial part of the second connector, to create the bridge connector flow having at least the predefined extension length , and the application subsystem is arranged to adapt the application control information to gain access to the flow of the bridge connector that includes the additionally copied units. The device according to claim 1, characterized in that the file subsystem is arranged to provide access information to the application subsystem, to indicate the location of the additionally copied units.
3. 3. The device according to claim 2, characterized by the file subsystem is arranged to provide the access information, sending a message indicating that the first unit has been additionally copied by a part number of the part's output unit. of the first connector before the final part of the first connector and / or indicating that the last unit has been additionally copied by an input unit number to the part of the second connector after the initial part of the second connector.
4. The device according to claim 1, characterized in that the file subsystem is arranged to copy the flow units of the first connector, before the final part of the first connector and / or the flow units of the second connector after the initial part of the second connector, to create the bridge connector, and the application subsystem is arranged to adapt the control information of the application, to gain access to the bridge connector and skip the flow of the first connector and / or the flow of the second connector.
5. 5. The device according to claim 1, characterized in that the file subsystem is arranged for said copying, selecting a unit that is aligned with a beginning of a data block as the first unit that has to be copied additionally, or selecting a unit that is aligned with an end of a data block, such as the last unit that has to be copied additionally.
6. The device according to claim 5, characterized in that the recording means are arranged to record error correction blocks containing a predefined number of data blocks, and the file subsystem is arranged for copying, selecting a unit that is aligned with a beginning of a block of error corrections, such as the first unit that has to be copied additionally, or selecting a unit that is aligned with an end of an error correction block, such as last unit that has to be copied additionally.
7. 7. The method for controlling the recording of real-time information in blocks of data based on logical addresses, the method is characterized in that it comprises: -store the real-time information in units that have unit numbers in the data blocks, according to predefined allocation rules, wherein the rules include storing a stream of real-time information that has to be reproduced without joins, in a sequence of consecutive data block extensions, the extensions have at least one predefined extension length , -manage the control information of the application, where the application control information includes -at least one real-time information connector, the connector comprises a connector information to gain access to a connector flow of the units of real-time information, through unit numbers, -at least one playlist, the list of reproduction comprises at least one reproduction element, the reproduction element indicates a part to be reproduced, of the real-time information in the connector, the reproduction list indicates in which order the reproduction elements have to be reproduced. , and - at least one bridge connector for linking a first and a second reproduction element, through the bridge connector, a bridge connector stream comprises re-encoded real-time information, based on a final part of the first connector and an initial part of the second connector, -copying additional units of the real-time information of a part of the flow of the first connector, before the final part of the first connector and / or of a part of the flow of the second connector after the initial part of the second connector, to create the flow of the bridge connector that has at least the predefined extension length, and -adapt the control information of the tion, to gain access to the flow of the bridge connector that includes the additionally copied units.
8. 8. A product consisting of a computer program for controlling the recording of real-time information, the program is characterized in that it operates to cause a processor to execute the method according to claim 7.
9. 9. The registration carrier characterized in that carries real-time information and corresponding application control information, in blocks of data based on logical addresses, -the real-time information is stored in units that have unit numbers, in the data blocks, according to assignment rules predefined, wherein the rules include storing a stream of real-time information that has to be reproduced without joins, in a sequence of consecutive data block extensions, the extensions have at least a predefined extension length, -the control information of the application includes -at least one real-time information connector, the connector co Learn a connector information to gain access to a real-time information unit connector stream, through the numbers of units, -at least one playlist, the playlist comprises at least one reproduction element, the reproduction element indicates a part that goes to >; -sex played back, of real-time information on the connector, the playlist indicates in which order the playback elements have to be reproduced, and -at least one bridge connector to link a first and a second playback element , through the bridge connector, a stream of the bridge connector comprises real-time re-encoded information, based on a final part of the first connector and an initial part of the second connector, -the bridge connector flow "-contains units, additional real-time information copied from; -: a part of the flow of the first connector, before the final part of the first connector and / or of a part of the flow of the second connector, after the initial part of the second connector, for create the bridge connector stream that has at least the predefined extension length, and - ·. - the application control information includes information to gain access to the connector flow. This includes the units copied additionally. ·