Top |
RygelMediaEngineRygelMediaEngine — This is the base class for media engines that contain knowledge about the streaming and transformational capabilites of the media library in use. |
#define | RYGEL_TYPE_MEDIA_ENGINE |
struct | RygelMediaEngine |
struct | RygelMediaEngineClass |
enum | RygelMediaEngineError |
Media engines express what representations of a MediaObject they can produce by returning MediaResource objects which will, in turn, be used to express to endpoints representations can be streamed from the MediaServer. These representations may include transformations, time-scaled representations, and/or encrypted representations.
See, for instance, Rygel's built-in "gstreamer" and "simple" media engines, or the external rygel-gst-0-10-media-engine module.
The actual media engine used by Rygel at runtime is specified by the media-engine configuration key. For instance, in rygel.conf: media-engine=librygel-media-engine-gst.so
Media engines should also derive their own RygelDataSource, returning an instance of it from create_data_source()
.
See the <link linkend="implementing-media-engines">Implementing Media Engines</link> section.
#define RYGEL_TYPE_MEDIA_ENGINE (rygel_media_engine_get_type ())
The type for RygelMediaEngine.
struct RygelMediaEngine { GObject parent_instance; RygelMediaEnginePrivate * priv; };
This is the base class for media engines that contain knowledge about the streaming and transformational capabilites of the media library in use.
Media engines express what representations of a MediaObject they can produce by returning MediaResource objects which will, in turn, be used to express to endpoints representations can be streamed from the MediaServer. These representations may include transformations, time-scaled representations, and/or encrypted representations.
See, for instance, Rygel's built-in "gstreamer" and "simple" media engines, or the external rygel-gst-0-10-media-engine module.
The actual media engine used by Rygel at runtime is specified by the media-engine configuration key. For instance, in rygel.conf: media-engine=librygel-media-engine-gst.so
Media engines should also derive their own RygelDataSource, returning an instance of it from create_data_source()
.
See the <link linkend="implementing-media-engines">Implementing Media Engines</link> section.
struct RygelMediaEngineClass { GObjectClass parent_class; GList* (*get_dlna_profiles) (RygelMediaEngine* self); void (*get_resources_for_item) (RygelMediaEngine* self, RygelMediaObject* item, GAsyncReadyCallback _callback_, gpointer _user_data_); GeeList* (*get_resources_for_item_finish) (RygelMediaEngine* self, GAsyncResult* _res_); RygelDataSource* (*create_data_source_for_resource) (RygelMediaEngine* self, RygelMediaObject* item, RygelMediaResource* resource, GHashTable* replacements, GError** error); RygelDataSource* (*create_data_source_for_uri) (RygelMediaEngine* self, const gchar* uri, GError** error); GList* (*get_internal_protocol_schemes) (RygelMediaEngine* self); };
The class structure for RYGEL_TYPE_MEDIA_ENGINE
. All the fields in this structure are private and should never be accessed directly.
virtual method called by |
||
virtual method called by |
||
asynchronous finish function for |
||
virtual method called by |
||
virtual method called by |
||
virtual method called by |