Then, after async-done message was received, I issue one or several new_step events.
The playbin2 successfully steps one or several frames back (this doesn't happen on all my mpeg-2 files, but this is another problem, I wrote about it already).
Then I press "Play" button on my application's form, which issues queries for the current position and segmend, then issues the seek event to turn the playback forward again:
how can we derive decoders from Gstbasetransform element when in
our decoder elements, the pad capabilities of the input pad cannot be
the same as the output pad.
The information contained in this e-mail message and in any
attachments/annexure/appendices is confidential to the
recipient and may contain privileged information.
If you are not the intended recipient, please notify the
sender and delete the message along with any
attachments/annexure/appendices. You should not disclose,
copy or otherwise use the information contained in the
message or any annexure. Any views expressed in this e-mail
are those of the individual sender except where the sender
specifically states them to be the views of
Toshiba Embedded Software India Pvt. Ltd. (TESI),Bangalore.
Although this transmission and any attachments are believed to be
free of any virus or other defect that might affect any computer
system into which it is received and opened, it is the responsibility
of the recipient to ensure that it is virus free and no responsibility
is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or
damage arising in any way from its use.
On Sun, Jun 27, 2010 at 10:20 PM, Shivaprasad P
<[hidden email]> wrote:
> Dear All,
> how can we derive decoders from Gstbasetransform element when in
> our decoder elements, the pad capabilities of the input pad cannot be
> the same as the output pad.
Decoders should not be derived from GstBaseTransform.