Jframe: Difference between revisions
Jump to navigation
Jump to search
(Add known info about j-frames) |
mNo edit summary |
||
| Line 2: | Line 2: | ||
[[MPlayer]] on x86 can play files containing these frames using a binary codec. ffmpeg can also play files containing j-frames, but, those frames will be skipped. j-frames have not been reverse engineered, so there is no documentation available. If a stream contains j-type frames the j-type bit will be set in the streams extradata. | [[MPlayer]] on x86 can play files containing these frames using a binary codec. ffmpeg can also play files containing j-frames, but, those frames will be skipped. j-frames have not been reverse engineered, so there is no documentation available. If a stream contains j-type frames the j-type bit will be set in the streams extradata. | ||
Note: j-frame is the notiation used by ffmpeg developers. Only microsoft knows the correct terminology. | |||
The main differences between j-frames and i-frames: | The main differences between j-frames and i-frames: | ||
Revision as of 05:22, 30 May 2007
A j-frame (also known as a j-type frame) is a type of frame similar to an i-frame used in microsofts mpeg4 variation codec WMV2 and the same coding method (with the different header) is used in WMV3 Complex Profile under the name "X8".
MPlayer on x86 can play files containing these frames using a binary codec. ffmpeg can also play files containing j-frames, but, those frames will be skipped. j-frames have not been reverse engineered, so there is no documentation available. If a stream contains j-type frames the j-type bit will be set in the streams extradata.
Note: j-frame is the notiation used by ffmpeg developers. Only microsoft knows the correct terminology.
The main differences between j-frames and i-frames:
- They are not derived from MPEG-4 standard
- Picture is coded as blocks, not as macroblocks
- Each frame may use its own Huffman codes