JP2002118826A - Data transfer method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a data transfer method by which a multimedia device, which stores a stream resulting from digitizing video data and audio data, indexes positions of a sequence header code, a GOP(Group of Picture) start code, a picture start code or the like included in the stream, uses index data to read the stream from the midway or up to the midway thereof from a recording medium and reproduces the read stream, can correctly decode a TS(Transport Stream) without destroying a structure of the TS or a PES(Packetized Elementary Stream) even when a processed stream is the TS. SOLUTION: The multimedia device processes a TS packet including any of the sequence header code, the GOP start code, and the picture start code when reading stream data from a recording medium to eliminate excess data and inserts a header of a PES packet as required.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an MPEG (Moving
Picture Experts Group) 2-TS (TransportStrea
m; a transport stream), a specific code in the stream is detected and recorded on a recording medium, and the stream data in the recording medium is transferred to a reproducing apparatus for decoding.

[0002]

2. Description of the Related Art In recent years, digital compression techniques such as MPEG1 and MPEG2 have been standardized, and high-performance CPUs,
Memory and storage media are becoming available at lower prices. Therefore, many multimedia devices that digitize and store video data and audio data and reproduce the stored data are being commercialized.

[0003] In the case of such a multimedia device, it is necessary to perform playback from the middle of the stream, or to perform special playback such as chase playback or fast playback. However, in a system using MPEG, intra-frame encoding is performed. Intra-frame coded, such as transfer from frame, transfer in GOP (Group of Picture) as a unit of intra-frame coding and inter-frame coding, or transfer of only intra-coded frames Frame, GOP
Of a sequence header code (hereinafter, referred to as SHC), a GOP start code (hereinafter, referred to as GSC), or a picture start code (hereinafter, referred to as PSC) as a starting point of Is often read out from a recording medium and transferred to a device that performs decoding.

For example, Japanese Patent Laid-Open No. Hei 10-285555 discloses a technique for recording an SHC (sequence header code) so that the head position coincides with the head of a sector. Japanese Patent Application Laid-Open No. 7-170488 discloses S
A technique for reading data from the head position of the HC is disclosed.

[0005] In these conventional techniques, a video is an elementary stream (hereinafter, referred to as ES).
There is no problem when the multiplexed stream is composed, but there is a case where the multiplexed stream cannot be dealt with.

In MPEG2, in addition to ES, packetized elementary stream (Packetized Elementary Stream; hereinafter referred to as P)
ES), a transport stream obtained by dividing a PES (hereinafter referred to as TS), and a program stream (Program Stream; hereinafter referred to as PS) having a configuration in which a plurality of PES packets are packed. There is.

[0007] In particular, TS is used in digital broadcasting and the like because it can handle video, audio, and data in a multiplexed manner, and can transfer fixed-length packets.

FIG. 8 shows the structure of a packet constituting a TS. The TS packet is a fixed-length 188-byte packet composed of a 4-byte fixed-length packet header, a variable-length adaptation field, and a payload.

The packet header includes a synchronization byte, a PID,
It is composed of an adaptation field control flag, a cyclic counter, and other flags. The sync byte is
This is 1-byte data including a code indicating that the position is the head of the TS packet. The PID is a 13-bit number for identifying a packet, and video and audio are divided into payloads of a plurality of TS packets having different PIDs and transmitted. The adaptation control flag indicates whether an adaptation field or a payload is included in the packet.
This is a bit flag. FIG. 8A shows a packet structure when the adaptation field and the payload are included, and FIG. 8B shows a packet structure when only the payload is included. The cyclic counter indicates 0x00 between TS packets having the same PID.
4-bit data including a value set so as to circulate values from 0x0f to 0x0f. The other flags include a flag indicating that a new PES packet is started in the payload.

[0010] The adaptation field includes an adaptation field length, a flag, an optional field, and a stuffing byte. The adaptation field length is 1-byte data representing the length of the adaptation field after the flag in byte units. The optional field is an area including synchronization information and the like, and is a variable-length area in which the presence or absence of information is indicated by a flag. The stuffing byte is dummy data and fills the remaining area of the adaptation field.

[0011] The payload includes data to be transmitted.

The PES is a basic element constituting a TS or a PS, and is an intermediate stream for enabling conversion between the two streams. FIG. 9 shows a structure of a packet constituting the PES.

The head start code is 3-byte data including a fixed value indicating that the position is the head of the PES packet. The stream ID is 1-byte data including a number for identifying the type of ES (video, audio, etc.) included in the PES packet. Packet length is PES
This is 2-byte data including a value defining the number of bytes in the packet. Only when the data in the PES packet is the video ES, the value 0 whose packet length is not specified can be set. The PES header length is 1-byte data that defines the number of bytes in the conditional coding area.
Conditional coding is a variable-length area in which the presence or absence of information is indicated by a 14-bit flag. The packet data includes ES data to be transmitted.

[0014] For the video stream, the ES stream is converted to PE.
It is divided into S packets and transmitted in a form further divided into TS packets. FIG. 10 shows TS packets and PES
4 shows a relationship between a packet and an ES.

The video stream is composed of picture data representing an intra-coded frame and picture data representing an inter-coded frame, and each data is stored in an area starting with a PSC (picture start code). Is done. In the stream, GSC (GOP start code) and SHC (sequence header code) for representing a GOP (group of pictures) are inserted. PES packets are obtained by dividing this stream, and are further divided into TS packets.

[0016]

Here, when transferring data from the SHC which is the starting point of a GOP in order to play back from the middle of a stream, how SHC is stored in a PES packet or a TS packet is described. Is a problem. In the example shown in FIG. 10, the SHC is stored in TS2 and TS8 in the TS packet, and in PES1 and PES3 in the PES packet.

When data after the SHC is transferred to reproduce from the SHC, the data is reproduced from the middle of the TS packet, and the data of the TS packet is shifted with respect to the boundary of every 188 bytes.

Further, when an attempt is made to reproduce the TS packet including the SHC from the start position, the PES packet which is a basic element thereof is truncated on the way, and is transferred in an abnormal state.

The same applies to the case of transferring data in picture units for fast-forwarding. When data is transferred from the PSC, the TS packet is reproduced from the middle, and even if an attempt is made to reproduce from the start position of the TS packet including the PSC, the PES packet is cut off in the middle, so that an abnormal state is caused. Will be transferred.

A similar situation occurs when transferring data until the next SHC appears in order to stop reproduction.

When a stream having such an abnormal structure is transferred to a decoding device, it is expected that the stream cannot be decoded or an abnormal operation is performed. Therefore, as in the prior art, data is read from the SHC,
However, such a stream cannot be reproduced by reading from a TS packet that includes a.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and has as its object to store a digitized stream of video data and audio data and to store SHC and GSC data contained therein. , PSC, etc., and in a multimedia device that plays back from or to the middle of the stream using the index data, even if the stream to be handled is a TS stream,
An object of the present invention is to enable correct decoding without destroying the structure of S.

[0023]

According to the present invention, in order to achieve the above object, when reading stream data from a recording medium, a TS packet containing an SHC to be transferred is processed.

For example, when data after the SHC is required for reproduction or the like, the data before the SHC may be deleted from the TS packet. In this case, the structure of the PES including the SHC is destroyed, but this is dealt with by creating a new PES by adding a header of the PES packet. The header of the PES packet is shown in FIG.
It is composed of 9 bytes as shown by. As the insertion position of the PES header, there may be a case where the TS is inserted into the TS including the sequence header, and a case where the TS including the PES header is included before the TS including the SHC.

When data before the SHC is required, for example, when reproduction is stopped, the data after the SHC may be deleted from the TS packet. In the deletion, the length of the adaptation field may be increased by shifting the data of the payload, and the area may be filled with stuffing bytes.

When it is desired to extract only a specific picture, such as fast forward, data before the PSC of the picture located next to that picture is required. In this case, the data after the PSC may be deleted from the TS including the corresponding PSC.

[0027]

Embodiments of the present invention will be described below with reference to the drawings.

<First Embodiment> In this embodiment, when it is desired to transfer data from a specific code, a TS packet including the specific code is processed, data before the specific code is deleted, and the data is transferred. This is an application example of the data transfer method described above. In the present embodiment, SHC is used as the specific code, but may be applied to GSC or PSC.

FIG. 4 is a diagram showing an example of packet processing according to the present embodiment. The TS packet located at the top in FIG. 4 represents a packet including SHC therein. SH
The hatched area located after C is an area including data to be transferred together with the SHC, and the dot pattern area before the SHC is data included in a GOP before the SHC. When this data is transferred, the decoder that decodes the TS may cause an error.
The data of the dot pattern area before the HC is deleted. However,
If the PES packet is deleted as it is, the PES packet belonging to the TS becomes a packet without a header.
It is necessary to insert the header of the ES packet.

In the present embodiment, the function of the stuffing byte of the adaptation field is used to delete this area. Instead of deleting the data, create an adaptation field without optional fields, fill the area of the deleted data with stuffing bytes, insert a new PES header before the SHC, and the TS packet starts at the start of the PES packet. The target TS packet can be obtained by turning on the flag indicating that there is.

The lower TS packet in FIG. 4 is the processed TS packet. In order to create an adaptation field without an optional field, an area indicating an adaptation field length and a flag in the adaptation field is provided, and a value indicating that there is no optional field is set in the flag (O in the figure).
FF), the adaptation field length is set to a value smaller by 10 bytes than the deleted data. This is to insert the 9 bytes of the new PES packet header,
This is because the area of the adaptation field length is not counted. A stuffing byte is inserted in the remaining area of the adaptation field.

FIG. 1 is a flowchart showing a process of processing a TS packet including an SHC and deleting data before the SHC according to the present embodiment.

First, paying attention to the packet including the SHC, the number of offset bytes from the head of the corresponding TS is obtained (step S101). Hereinafter, this value is represented as X. A bit indicating that the corresponding TS is the start of a new PES packet in the flag area is turned ON (step S10).
2). The adaptation field control flag is turned on to indicate that the adaptation field exists in the corresponding TS (step S103).

Next, X-14 is set as the value of the adaptation field length (step S104), and a value in which all the flags are turned off is set as the value of the flag area in the adaptation field (step S10).
5). This indicates that there is no optional field in this TS.

Subsequently, a stuffing byte of X-15 bytes is inserted from the seventh byte position from the head of the packet (step S106), and a PES header is inserted from the next byte position (step S107).

By the processing of this flowchart, the corresponding TS is started from a new PES packet, and the ES contained therein is also started from the SHC.

When processing for GSC or PSC,
What is necessary is just to replace SHC in a flowchart with GSC or PSC, and to perform. When processing is performed on a packet having GSC or PSC, the corresponding TS
E that starts with and is contained in the ES packet
S also starts from GSC or PSC.

<Second Embodiment> In this embodiment, when it is desired to transfer data from a specific code, a TS packet including the specific code is processed, data before the specific code is deleted, and the TS packet to be processed is deleted. This is an application example of a data transfer method in which a TS packet including a new PES header is arranged before transferring data. In the present embodiment, the SHC is used as the specific code, but may be applied to a GSC, a PSC, or the like.

FIG. 5 is a diagram showing an example of packet processing according to the present embodiment. The TS packet located at the top in FIG. 5 represents a packet including SHC therein. First
Similarly to the embodiment, the hatched area located after the SHC is:
This is the area that contains the data you want to transfer with the SHC,
The area of the dot pattern before the SHC is data included in the GOP before the SHC. Therefore, from the TS packet,
What is necessary is just to delete the data of this dot pattern area. However,
If the PES packet is deleted as it is, the PES packet belonging to the TS becomes a packet without a header.
It is necessary to insert the header of the ES packet.

In the present embodiment, a TS packet located before the corresponding TS is created, and the header of the PES packet and the SH
C is included therein. This packet is a packet having only a PES packet header and an SHC code as data. The PID, flag, and counter are set to necessary values.

Further, the area of the dot pattern from the corresponding TS and the SHC
Use the stuffing byte function of the adaptation field to remove Instead of deleting the data, an adaptation field having no optional field is created, and the area of the deleted data is filled with stuffing bytes, whereby a target TS packet can be obtained.

The lower TS packet in FIG. 5 is the processed TS packet. The packet located at the lower right in the figure is a packet containing the SHC, and in order to create an adaptation field without an optional field, an area indicating an adaptation field length and a flag in the adaptation field is provided,
A value indicating that there is no optional field is set in the flag (OFF in the figure), and the value of the adaptation field length is set to a value one byte smaller than the deleted data. A stuffing byte is inserted in the remaining area of the adaptation field.

The packet located at the lower left in FIG.
C is a TS packet inserted before the TS packet containing C, and a PES packet header and SH
C. An adaptation field without optional fields is created to shorten the payload area. An area representing an adaptation field length and a flag in the adaptation field is provided, and a value indicating that there is no optional field is set in the flag (OFF in the figure), and the adaptation field length is set to a value 170. This value indicates the number of areas including the stuffing byte and the flag in the adaptation. The PID in the TS header is set to the same value as the packet located at the lower right in the figure, and the flag indicating that the TS packet is the start of the PES packet is turned ON.
To Also, the value of the counter is set to a value one smaller than the value of the packet located at the lower right in the figure. In the adaptation control flag, a value indicating that the adaptation is included is set.

FIG. 2 is a flowchart of a process for processing a TS packet including an SHC and deleting data before the SHC according to the present embodiment.

First, processing is performed on the packet including the SHC. Attention is paid to the packet including the SHC, and the number of offset bytes from the head of the corresponding TS is obtained (step S20).
1). Hereinafter, this value is represented as X. The adaptation field control flag is turned ON to indicate that the adaptation field exists in the corresponding TS (step S
202).

Next, X-1 is set as the value of the adaptation field length (step S203). A value in which all the flags are turned off is set as the value of the flag area in the adaptation field (step S20).
4). This indicates that there is no optional field in this TS.

Next, a stuffing byte of X-2 bytes is inserted from the position of the seventh byte from the head of the packet (step S205).

Next, in order to process the immediately preceding TS packet, it moves to the head position of the immediately preceding TS (step S).
206). First, the header of the TS is set (step S207). The header contains a synchronization byte, a flag area,
A counter and a PID are included. The counter is set in step S
1 less than the value of the TS packet processed in 201 to S205
A smaller value is set, and the same value is set for the PID. In the flag, a flag indicating that a PES packet is started from the TS and a flag indicating that the TS includes an adaptation field are set.

Next, a fixed value 170 is set in the area for storing the adaptation field length (step S20).
8) The flag in the adaptation field is set to a value indicating that no optional field is included (step S209).

Next, from the first byte of the packet, 16
9 stuffing bytes are inserted (step S
210) Finally, the header of the PES packet and the SHC
Is inserted (step S211, step S212).

By the processing of this flowchart, TS
Is started from a new PES packet, and the ES contained therein is also started from the SHC.

When processing GSC or PSC,
What is necessary is just to replace SHC in a flowchart with GSC or PSC, and to perform it. When processing is performed on a packet having GSC or PSC, the corresponding TS
E that starts with and is contained in the ES packet
S also starts from GSC or PSC.

In this embodiment, after data is deleted from the TS including the SHC, the TS including the PES packet header is deleted.
Was created, but may be performed in the reverse order. Also,
In the present embodiment, the method of inserting the SHC into the preceding TS packet has been described, but a method of leaving the SHC in the corresponding TS and including only the PES packet header in the previous TS packet is also conceivable.

<Third Embodiment> In the present embodiment, when transferring data up to the SHC, the TS packet containing the SHC is processed, the data after the SHC is deleted, and the data is transferred. This is an application example of a data transfer method.

FIG. 6 is a diagram showing an example of packet processing according to the present embodiment. The TS packet located on the left side in FIG. 6 represents the TS packet before and after processing when there is no adaptation field in the original TS packet, and the TS packet located on the right side in FIG. Represents the pre-processing and post-processing TS packets when the adaptation field is included in the TS packet.

First, the case where the adaptation field exists will be described. The hatched area located before the SHC in the upper right TS packet in FIG. 6 is an area including the data to be transferred, and the area of the dot pattern following the SHC and the SHC is included in the next GOP. Data. In order to make the data to be transferred well separated, the SHC and the dot pattern data may be deleted. This can be dealt with by increasing the number of stuffing bytes in the adaptation field instead of the data to be deleted. T at the lower right in FIG.
The S packet is a TS packet after the SHC and the dot pattern data have been deleted.

Next, the case where the adaptation field does not exist will be described. The hatched area located before the SHC in the upper left TS packet in FIG. 6 is an area including the data to be transferred, and the area of the dot pattern following the SHC and the SHC is included in the next GOP. Data. In order to make the data to be transferred well separated, the SHC and the dot pattern data may be deleted as in the case where the adaptation field exists. In this case, it is possible to deal with this by creating an adaptation field and filling the adaptation field with stuffing bytes instead of the data to be deleted.

The TS packet at the lower left in FIG. 6 is the TS packet from which the data of the SHC and the dot pattern have been deleted. In order to create an adaptation field, an area for storing an adaptation field length and a flag in the adaptation field are prepared, and the rest is used as a stuffing byte. For the adaptation field length, a value obtained by subtracting 1 from the amount of data to be deleted is set, and for the flag, a value indicating that the optional field is not included is set. In addition, a value indicating that this TS includes an adaptation field is set in the adaptation field control flag.

FIG. 3 is a flowchart of a process of processing a TS packet including an SHC and deleting data after the SHC according to the present embodiment.

First, paying attention to the packet including the SHC, the number of offset bytes from the head of the corresponding TS is obtained (step S301). Hereinafter, this value is represented as X.

Next, the adaptation control flag of the corresponding TS is confirmed, and it is checked whether an adaptation field exists (step S302).

In step S302, when it is confirmed that the adaptation field exists, the length of the adaptation field is obtained (step S302).
303). Hereinafter, this value is represented as Y.

Next, the data X-
The Y-5 byte is copied to the end of the corresponding TS packet (step S304), and the (Y + 6) th byte from the beginning of the packet and the XY-4th byte counting from the end of the packet are used.
The space between 8-X bytes is filled with a stuffing byte (step S305). Finally, the adaptation field length is set to a value represented by Y + 188-X (step S306).

On the other hand, if it is confirmed in step S302 that the adaptation field does not exist, the data X-4 bytes located before the SHC are copied to the end of the corresponding TS packet (step S30).
7) The space between the 186th and 186th bytes of the 7th byte from the beginning of the packet and the 3rd byte from the end of the packet is filled with stuffing bytes (step S308).

Next, a value indicated by 187-X is set in the area for storing the adaptation field length (step S309), and a value indicating that the optional field is not included is set in the flag in the adaptation field. (Step S310). Finally, the adaptation control flag in the TS header is set to a value indicating that the corresponding TS includes an adaptation field (step S311).

By the processing of this flowchart, TS
Is a stream that includes data up to target data that is well-divided in GOP units.

<Fourth Embodiment> In the present embodiment, when transferring data up to the PSC, a TS packet including the PSC is processed, data after the PSC is deleted, and the data is transferred. This is an application example of a data transfer method.

FIG. 7 is a diagram showing an example of packet processing according to the present embodiment. The TS packet located on the left side in FIG. 7 represents the TS packet before and after processing when there is no adaptation field in the original TS packet, and the TS packet located on the right side in FIG. Represents the pre-processing and post-processing TS packets when the adaptation field is included in the TS packet.

First, the case where the adaptation field exists will be described. The hatched area located before the PSC in the upper right TS packet in FIG. 7 is an area including the data to be transferred, and the PSC and the dot pattern area following the PSC are included in the next picture. Data. In order to make the data to be transferred well separated, the PSC and the dot pattern data may be deleted. This can be dealt with by increasing the number of stuffing bytes in the adaptation field instead of the data to be deleted. The TS packet at the lower right in FIG. 7 is the TS packet after deleting the data of the PSC and the dot pattern.

Next, the case where the adaptation field does not exist will be described. The hatched area located before the PSC in the upper left TS packet in FIG. 7 is an area containing data to be transferred, and the PSC and the dot pattern area following the PSC are included in the next picture. Data. In order to make the data to be transferred well separated, the PSC and the dot pattern data may be deleted as in the case where the adaptation field exists.
In this case, it is possible to deal with this by creating an adaptation field and filling the adaptation field with stuffing bytes instead of the data to be deleted.

The TS packet at the lower left in FIG. 7 is the TS packet after deleting the data of the PSC and the dot pattern. In order to create an adaptation field, an area for storing the adaptation field length and a flag in the adaptation are prepared, and the rest is used as a stuffing byte. For the adaptation field length, a value obtained by subtracting 1 from the amount of data to be deleted is set, and for the flag, a value indicating that the optional field is not included is set.
In addition, a value indicating that this TS includes an adaptation field is set in the adaptation field control flag.

The processing of this embodiment is achieved by replacing the SHC with the PSC in the flowchart shown in FIG.

By the processing of this flowchart, TS
Is a stream including up to target data which is well-divided in picture units.

[0074]

According to the first aspect of the present invention, since it is possible to delete and transfer extra data included in the packets constituting the stream, when the reproduction is started from the middle of the stream, the TS Even if the transfer is performed in packet units, it is possible to transfer data that does not include extra data.

According to the second aspect of the present invention, a TS including data starting from the SHC can be transferred.
Even in the case where data is transferred in units of P, data that does not include extra data in units of TS packets can be transferred.

In the invention according to claim 3, the SHC is PES.
Even if the packet is started in the middle of the packet, the correct data can be sent as a PES packet including a new PES packet header. Therefore, even if the transfer is performed from the TS packet including the SHC, the decoding device can operate correctly. Streams can be sent.

According to the fourth aspect of the present invention, the newly added packet is a fixed-length packet. For a packet including the SHC, it is only necessary to delete the extra data. Can be deleted, and the mechanism for adding the PES header can be simplified.

According to the fifth aspect of the present invention, it is possible to delete and transfer extra data located at the end of a packet constituting a stream.

In the invention according to claim 6, since a stream including the end of the GOP can be transferred, a stream that can be correctly operated by a decoding device can be transmitted even when reproduction is stopped.

According to the seventh aspect of the present invention, since a stream including the end of a picture can be transferred, a stream that can be correctly operated by a decoding device even if transfer is performed in units of pictures by fast forward or the like is transmitted. I can do it.

[Brief description of the drawings]

FIG. 1 is a flowchart illustrating a processing flow according to a first embodiment of the present invention.

FIG. 2 is a flowchart illustrating a processing flow according to a second embodiment of the present invention.

FIG. 3 is a flowchart illustrating a processing flow according to a third embodiment of the present invention.

FIG. 4 is an explanatory diagram showing an example of packet processing according to the first embodiment of the present invention.

FIG. 5 is an explanatory diagram illustrating an example of packet processing according to a second embodiment of the present invention.

FIG. 6 is an explanatory diagram illustrating an example of packet processing according to a third embodiment of the present invention.

FIG. 7 is an explanatory diagram showing an example of packet processing according to a fourth embodiment of the present invention.

FIG. 8 is an explanatory diagram showing a configuration of a TS packet.

FIG. 9 is an explanatory diagram showing a configuration of a PES packet.

FIG. 10 is an explanatory diagram showing a relationship between a TS packet, a PES packet, and an ES.

 ──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Tsuyoshi Hayama 22-22 Nagaikecho, Abeno-ku, Osaka City, Osaka Inside (72) Inventor Shinichiro Shirai 22-22 Nagaikecho, Abeno-ku, Osaka City, Osaka (72) Inventor Koki Shimizu 22-22 Nagaikecho, Abeno-ku, Osaka City, Osaka Sharp Corporation (72) Inventor Kaoru Hishikawa 22-22 Nagaikecho, Abeno-ku, Osaka City, Osaka Sharp Corporation (72) Inventor Ryoji Ohno 22-22, Nagaike-cho, Abeno-ku, Osaka, Japan F-term in Sharp Corporation (reference) 5C053 GA11 GB06 GB29 GB37 GB38 HA24 5C059 MA00 MA04 MA05 PP04 SS11 UA02 5K030 GA11 HA08 HB01 HB02 HB21 JA05 KA19 LA07

Claims (7)

[Claims] An MPEG2-TS (transport stream) is input, data is recorded on a recording medium while detecting a specific code therein, and the stream data in the recording medium is transferred to a reproducing apparatus for decoding. In the transfer method, if you want to transfer stream data from a specific code,
A data transfer method comprising processing a TS packet containing a specific code, deleting data before the specific code, and transferring the data. 2. The data transfer method according to claim 1, wherein the specific code is a sequence header code included in a stream. 3. The processing of the TS packet according to claim 1, wherein in the processing of the TS packet, a header of a new PES (packetized elementary stream) packet is included before a specific code in the TS packet. Characteristic data transfer method. 4. The processing of the TS packet according to claim 1, wherein the processing of the TS packet includes a TES including a header of a new PES packet before the TS packet including the specific code.
A data transfer method comprising arranging S packets. 5. A data transfer method for inputting an MPEG2-TS, recording it on a recording medium while detecting a specific code therein, and transferring stream data in the recording medium to a reproducing apparatus for decoding. When transferring stream data up to a code, a data transfer method is characterized in that a TS packet including a specific code is processed, and subsequent data including the specific code is deleted to transfer the data. 6. The data transfer method according to claim 5, wherein the specific code is a sequence header code included in a stream. 7. The data transfer method according to claim 5, wherein the specific code is a picture start code included in a stream.