Difference between revisions of "Hacker Guide/Access"
|Line 27:||Line 27:|
* Read or Block
* Read or Block
After implementing those
After implementing those , you should assign them to the corresponding pf_ function.
== Seek ==
== Seek ==
Revision as of 16:38, 11 November 2010
The modules of 'access' capability are designed to be the first and last elements of a modules chain.
We will discuss about 'input access' in this page.
Starting to write an access module
To write an access module, read the introduction to module writing.
Then, you should specify your module of being of access type:
set_capability( "access", 60 ) set_category( CAT_INPUT ) set_subcategory( SUBCAT_INPUT_ACCESS )
Your module can be of either a 'Block' or a 'Read' type, depending on what you need to access.
Functions to implement
After implementing Open() and Close() functions, you will need to implement a few majors features that will be implemented by your functions.
As you can see include/vlc_access.h, you should define:
- Seek, as in pf_seek
- Control, as in pf_control
- Read or Block
After implementing those functions, you should assign them to the corresponding pf_ function.
int (*pf_seek) ( access_t *, uint64_t );
The seeking function will be called whenever a seek is requested.
The arguments are a pointer to the module structure, and the requested position.
NB: Seeking function can be NULL, if it isn't possible to seek in the protocol or device.
int (*pf_control)( access_t *, int i_query, va_list args);
Control function is quite easy, the input core will query the module using this function.
The i_query parameter can be of several type. We will cover here the most important ones.
If the query has succeeded, it should return VLC_SUCCESS. Else it should return VLC_EGENERIC.
Control Query types
The first ones are request to know what the module supports. They are all of boolean type and should always succeed.
ACCESS_CAN_SEEK, ACCESS_CAN_FASTSEEK, ACCESS_CAN_PAUSE, ACCESS_CAN_CONTROL_PACE,
The following one is a request for the PTS delay. It must always succeed.
The following ones are for requesting various info about the input, like Metadata, Titles and Chapters or device signal strength. All of them can fail.
ACCESS_GET_TITLE_INFO, ACCESS_GET_META, ACCESS_GET_CONTENT_TYPE, ACCESS_GET_SIGNAL,
Depending to the answer of the CAN_ requests, the core can set a few things, like pausing or changing title or chapter
ACCESS_SET_PAUSE_STATE, ACCESS_SET_TITLE, ACCESS_SET_SEEKPOINT,
ssize_t (*pf_read) ( access_t *, uint8_t *, size_t );
Return -1 if no data yet, 0 if no more data, else actual data read on the medium.
block_t *(*pf_block)( access_t * );
Returns a block of data in his 'natural' size. It will return NULL if not yet data or eof.