Consider these as low level pfspd data access routines. There is no interpretation of the data, so these routines are more generic that all others. However, you can create files that cannot be processed by standard tools.
Supported on (almost) all pfspd file formats. Therefore, these functions use less strict header checking.
For standard i/o: the component shall be accessed in the same order as the data is stored in the file. This corresponds with the order in the header. Furthermore, for interlaced files only the field access functions can be used. For file i/o these restriction do not apply.
|
Functions |
pT_status | p_read_field_comp (const char *filename, pT_header *header, int frame, int field, int comp, unsigned char *c_fld, int read_mode, int width, int fld_height, int stride) |
pT_status | p_read_frame_comp (const char *filename, pT_header *header, int frame, int comp, unsigned char *c_frm, int read_mode, int width, int frm_height, int stride) |
pT_status | p_write_field_comp (const char *filename, pT_header *header, int frame, int field, int comp, const unsigned char *c_fld, int width, int fld_height, int stride) |
pT_status | p_write_frame_comp (const char *filename, pT_header *header, int frame, int comp, const unsigned char *c_frm, int width, int frm_height, int stride) |
pT_status | p_read_field_comp_16 (const char *filename, pT_header *header, int frame, int field, int comp, unsigned short *c_fld, int read_mode, int width, int fld_height, int stride) |
pT_status | p_read_frame_comp_16 (const char *filename, pT_header *header, int frame, int comp, unsigned short *c_frm, int read_mode, int width, int frm_height, int stride) |
pT_status | p_write_field_comp_16 (const char *filename, pT_header *header, int frame, int field, int comp, const unsigned short *c_fld, int write_mode, int width, int fld_height, int stride) |
pT_status | p_write_frame_comp_16 (const char *filename, pT_header *header, int frame, int comp, const unsigned short *c_frm, int write_mode, int width, int frm_height, int stride) |