Hi, Why don't you use emotion API directlry?
Basically, the emotion sink renders video into registered emotion object as "emotion-object" property. Moreover, I am not sure whether you could use emotion-sink directly. emotion-sink is embedded in emotion plugin module as I know.. (try gst-inspect) Somehow, even if you made pipeline manually with emotion-sink, you should create/register emotion object as target to be rendered. The thing is that if you created and played emotion object, the gstreamer pipeline would be created internally. Why do you go a long way around? Regards, Wonguk Jeong 2014. 7. 17. 오후 2:28에 "Prathamesh P Ghanekar" <prathamesh.ghane...@igate.com>님이 작성: > Hi Carsten, > > I am still in the process of understanding "rage" player that you > suggested. > > But, I have following thing in mind : > I have built EFL with the gstreamer1 module, which has generated emotion > library(module) for gstreamer1.0 backend. Now, can I simply create a > gstreamer pipeline (say playbin) through my code and link it to this > library and other ELF libraries? I will add 'emotion-sink'-(the custom sink > defined by the module) to this pipeline. Will this render the video in > emotion-sink? > > The reason I am trying to avoid completely EFL-based video player is that > It will take some time to get familiar with EFL APIs, and time is a premium > for me currently!! > > Regards, > Prathamesh Ghanekar > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Information contained and transmitted by this e-mail is confidential and > proprietary to IGATE and its affiliates and is intended for use only by the > recipient. If you are not the intended recipient, you are hereby notified > that any dissemination, distribution, copying or use of this e-mail is > strictly prohibited and you are requested to delete this e-mail immediately > and notify the originator or mailad...@igate.com <mailto: > mailad...@igate.com>. IGATE does not enter into any agreement with any > party by e-mail. Any views expressed by an individual do not necessarily > reflect the view of IGATE. IGATE is not responsible for the consequences of > any actions taken on the basis of information provided, through this email. > The contents of an attachment to this e-mail may contain software viruses, > which could damage your own computer system. While IGATE has taken every > reasonable precaution to minimise this risk, we cannot accept liability for > any damage which you sustain as a result of software viruses. You should > carry out your own virus checks before opening an attachment. To know more > about IGATE please visit www.igate.com <http://www.igate.com>. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
