From: Jan S. <th...@ma...> - 2007-10-30 13:30:25
|
<quote who="al...@ke..."> > CVS Root: /cvs/gstreamer > Module: gst-plugins-bad > Changes by: alima > Date: Tue Oct 30 2007 12:49:19 UTC > > Log message: > Created new plugin ('medadata') and element ('metadataparse') that extract metadata from images (look at bug #486659). > I may be alone in this, but I really hate these element names. Can't you come up with something a bit less general? Jan. -- Jan Schmidt th...@ma... "Karaoke bars combine two of the nation's greatest evils: people who shouldn't drink with people who shouldn't sing." -Tom Dreesen |
From: Sharath M. <sha...@mi...> - 2007-11-22 07:38:40
|
To: gst...@li... Subject: Issue: gst_element_factory_make ("my_new_plugin") =3D=3D 0 ??? Hello all, PROBLEM: I cannot succeed gst_element_factory_make ("my_new_plugin","A_sample"); WHAT DID I DO? 1. I have created a new filter plugin "my_new_plugin" (just like in = plugin guide). 2. I have now written a test program to include 'my_new_plugin' (just = like in the plugin guide). 3. the gst_element_factory_make ("my_new_plugin","A_sample"); FAILS! WHAT VERIFICATIONS I DID? 1. Checked if Shared Object is in $(libdir)/gstreamer-0.10/. (It is = there!) 2. gst-inspect-0.10 lists my_new_plugin. 3. gst-inspect-0.10 my_new_plugin gives me the details of my plugin. 4. gst-launch-0.10 fakesrc ! my_new_plugin ! fakesink works fine. I see = "I'm plugged, therefore I'm in." message from the chain function! 5. Alternatively, gst_element_factory_find ("my_new_filter"); FAILS in = the program. QUESTIONS: 1. why is gst_element_factory_make () FAILING ? Please, help me out! Thanks and regards, Sharath PS: Please, ignore the DISCLAIMER! Sorry about this! DISCLAIMER: This message (including attachment if any) is confidential and may be = privileged. If you have received this message by mistake please notify = the sender by return e-mail and delete this message from your system. = Any unauthorized use or dissemination of this message in whole or in = part is strictly prohibited. E-mail may contain viruses. Before opening attachments please check them = for viruses and defects. While MindTree Consulting Limited (MindTree) = has put in place checks to minimize the risks, MindTree will not be = responsible for any viruses or defects or any forwarded attachments = emanating either from within MindTree or outside. Please note that e-mails are susceptible to change and MindTree shall = not be liable for any improper, untimely or incomplete transmission. MindTree reserves the right to monitor and review the content of all = messages sent to or from MindTree e-mail address. Messages sent to or = from this e-mail address may be stored on the MindTree e-mail system or = else where. |
From: Steve F. <sp...@gm...> - 2007-11-23 06:09:17
|
Did you call gst_init()? (Just a stab in the dark.) You'll probably have to run with GST_DEBUG='*:4' or '*:5'. Yuck. |
From: Stefan K. <en...@ho...> - 2007-10-31 18:00:49
|
Hi, Jan Schmidt schrieb: > <quote who="al...@ke..."> > >> CVS Root: /cvs/gstreamer >> Module: gst-plugins-bad >> Changes by: alima >> Date: Tue Oct 30 2007 12:49:19 UTC >> >> Log message: >> Created new plugin ('medadata') and element ('metadataparse') that extract metadata from images (look at bug #486659). >> > > I may be alone in this, but I really hate these element names. Can't you > come up with something a bit less general? > > Jan. Its in bad for now and we are aware that the name is far from perfect. Any better suggestion is welcome. But have a look at e.g. xmp website before and see the amount of formats covered. Having separate xmpmux/demux, exifmux/demux and ipctmux/demux would need a utillity lib (was proposed already but rejected) and suffers from the problem that you coudl have all three in any order (nedds careful caps media-type design). Stefan |
From: Martin S. <co...@su...> - 2007-10-31 18:12:23
|
How about "imgmetadata" which should decribe the use precisely? --- M.S. On Wed, 2007-10-31 at 19:06 +0200, Stefan Kost wrote: > Hi, > > Jan Schmidt schrieb: > > <quote who="al...@ke..."> > > > >> CVS Root: /cvs/gstreamer > >> Module: gst-plugins-bad > >> Changes by: alima > >> Date: Tue Oct 30 2007 12:49:19 UTC > >> > >> Log message: > >> Created new plugin ('medadata') and element ('metadataparse') that extract metadata from images (look at bug #486659). > >> > > > > I may be alone in this, but I really hate these element names. Can't you > > come up with something a bit less general? > > > > Jan. > > Its in bad for now and we are aware that the name is far from perfect. Any > better suggestion is welcome. But have a look at e.g. xmp website before and see > the amount of formats covered. Having separate xmpmux/demux, exifmux/demux and > ipctmux/demux would need a utillity lib (was proposed already but rejected) and > suffers from the problem that you coudl have all three in any order (nedds > careful caps media-type design). > > Stefan > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gstreamer-devel mailing list > gst...@li... > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel > |
From: Stefan K. <en...@ho...> - 2007-11-02 19:27:26
|
hi, Martin Szulecki schrieb: > How about "imgmetadata" which should decribe the use precisely? > well it can be images, video and audio. "mediametadata" sounds like a tongue twister. Stefan > --- M.S. > > On Wed, 2007-10-31 at 19:06 +0200, Stefan Kost wrote: >> Hi, >> >> Jan Schmidt schrieb: >>> <quote who="al...@ke..."> >>> >>>> CVS Root: /cvs/gstreamer >>>> Module: gst-plugins-bad >>>> Changes by: alima >>>> Date: Tue Oct 30 2007 12:49:19 UTC >>>> >>>> Log message: >>>> Created new plugin ('medadata') and element ('metadataparse') that extract metadata from images (look at bug #486659). >>>> >>> I may be alone in this, but I really hate these element names. Can't you >>> come up with something a bit less general? >>> >>> Jan. >> Its in bad for now and we are aware that the name is far from perfect. Any >> better suggestion is welcome. But have a look at e.g. xmp website before and see >> the amount of formats covered. Having separate xmpmux/demux, exifmux/demux and >> ipctmux/demux would need a utillity lib (was proposed already but rejected) and >> suffers from the problem that you coudl have all three in any order (nedds >> careful caps media-type design). >> >> Stefan >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> gstreamer-devel mailing list >> gst...@li... >> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gstreamer-devel mailing list > gst...@li... > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
From: Sharath M. <sha...@mi...> - 2007-11-21 11:06:41
|
Hello all, PROBLEM: Unable to build a Gst Plugin. I am trying to build a filter plugin lib (.so) with a corresponding = header and put it in /lib/gstreamer-0.10/ WHAT DID I DO? 1. Downloaded gst-template folder. 2. make_element Wow ( generated gstwow.h & gstwow.c) 3. ./configure ( assuming, this is what we should do.. just like = building gstreamer src) 4. make WHERE IS THE PROBLEM NOW? Step #3 above fails (please see shell logs below). A file called = Makefile.in seems to be missing. _________________________________________________________________________= ___ [root@localhost gst-plugin]# [root@localhost gst-plugin]# [root@localhost gst-plugin]# [root@localhost gst-plugin]# ls aclocal.m4 comedi configure gst-autogen.sh m4 = src autogen.sh config.guess configure.ac INSTALL Makefile.am tools autom4te.cache config.h.in COPYING install-sh missing autoregen.sh config.sub cvignore ltmain.sh plplot [root@localhost gst-plugin]# pwd /root/project_files/code_sample/gst-template/gst-plugin [root@localhost gst-plugin]# ./configure configure: configuring gst-plugin for development with nano 1 checking whether to enable maintainer-specific portions of Makefiles... = no checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... none checking build system type... i686-redhat-linux-gnu checking host system type... i686-redhat-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... none checking how to run the C++ preprocessor... g++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld) supports shared = libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared = libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/bin/ld) supports shared = libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for g77 option to produce PIC... -fPIC checking if g77 PIC flag -fPIC works... yes checking if g77 static flag -static works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/bin/ld) supports shared = libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking to see if compiler understands -Wall... yes checking to see if compiler understands -Werror... yes checking for pkg-config... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GST... yes checking for GST_BASE... yes checking for GSTPB_BASE... yes checking for GSTCTRL... yes configure: creating ./config.status config.status: creating Makefile config.status: error: cannot find input file: Makefile.in [root@localhost gst-plugin]# [root@localhost gst-plugin]# [root@localhost gst-plugin]# make make: *** No targets specified and no makefile found. Stop. _________________________________________________________________________= _ QUESTIONS: 1. How to build the new plugin code generated using = ../tools/make_elements ? 2. How to let gst-inpsect & gst-launch (and other tools) know that I = have created a plugin? CONCERN: The plugin writer's Guide form gstreamer.freedesktop.org seems to be = missing some pages :-(.=20 I referred to previous related mail archives. It has only added to = confusion. Please, help me out of this.. Thanks and regards, Sharath PS: Please, ignore the DISCLAIMER! Sorry about this! DISCLAIMER: This message (including attachment if any) is confidential and may be = privileged. If you have received this message by mistake please notify = the sender by return e-mail and delete this message from your system. = Any unauthorized use or dissemination of this message in whole or in = part is strictly prohibited. E-mail may contain viruses. Before opening attachments please check them = for viruses and defects. While MindTree Consulting Limited (MindTree) = has put in place checks to minimize the risks, MindTree will not be = responsible for any viruses or defects or any forwarded attachments = emanating either from within MindTree or outside. Please note that e-mails are susceptible to change and MindTree shall = not be liable for any improper, untimely or incomplete transmission. MindTree reserves the right to monitor and review the content of all = messages sent to or from MindTree e-mail address. Messages sent to or = from this e-mail address may be stored on the MindTree e-mail system or = else where. |
From: Sharath M. <sha...@mi...> - 2007-11-22 06:20:58
|
Hello, I could resolve the issue! Thanks, Sharath -----Original Message----- From: Sharath Mudalamane=20 Sent: Wednesday, November 21, 2007 4:36 PM To: gst...@li... Subject: Issue: Creating a sample Gst plugin Hello all, PROBLEM: Unable to build a Gst Plugin. I am trying to build a filter plugin lib (.so) with a corresponding = header and put it in /lib/gstreamer-0.10/ WHAT DID I DO? 1. Downloaded gst-template folder. 2. make_element Wow ( generated gstwow.h & gstwow.c) 3. ./configure ( assuming, this is what we should do.. just like = building gstreamer src) 4. make WHERE IS THE PROBLEM NOW? Step #3 above fails (please see shell logs below). A file called = Makefile.in seems to be missing. _________________________________________________________________________= ___ [root@localhost gst-plugin]# [root@localhost gst-plugin]# [root@localhost gst-plugin]# [root@localhost gst-plugin]# ls aclocal.m4 comedi configure gst-autogen.sh m4 = src autogen.sh config.guess configure.ac INSTALL Makefile.am tools autom4te.cache config.h.in COPYING install-sh missing autoregen.sh config.sub cvignore ltmain.sh plplot [root@localhost gst-plugin]# pwd /root/project_files/code_sample/gst-template/gst-plugin [root@localhost gst-plugin]# ./configure configure: configuring gst-plugin for development with nano 1 checking whether to enable maintainer-specific portions of Makefiles... = no checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... none checking build system type... i686-redhat-linux-gnu checking host system type... i686-redhat-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... none checking how to run the C++ preprocessor... g++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld) supports shared = libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared = libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/bin/ld) supports shared = libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for g77 option to produce PIC... -fPIC checking if g77 PIC flag -fPIC works... yes checking if g77 static flag -static works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/bin/ld) supports shared = libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking to see if compiler understands -Wall... yes checking to see if compiler understands -Werror... yes checking for pkg-config... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GST... yes checking for GST_BASE... yes checking for GSTPB_BASE... yes checking for GSTCTRL... yes configure: creating ./config.status config.status: creating Makefile config.status: error: cannot find input file: Makefile.in [root@localhost gst-plugin]# [root@localhost gst-plugin]# [root@localhost gst-plugin]# make make: *** No targets specified and no makefile found. Stop. _________________________________________________________________________= _ QUESTIONS: 1. How to build the new plugin code generated using = ../tools/make_elements ? 2. How to let gst-inpsect & gst-launch (and other tools) know that I = have created a plugin? CONCERN: The plugin writer's Guide form gstreamer.freedesktop.org seems to be = missing some pages :-(.=20 I referred to previous related mail archives. It has only added to = confusion. Please, help me out of this.. Thanks and regards, Sharath PS: Please, ignore the DISCLAIMER! Sorry about this! DISCLAIMER: This message (including attachment if any) is confidential and may be = privileged. If you have received this message by mistake please notify = the sender by return e-mail and delete this message from your system. = Any unauthorized use or dissemination of this message in whole or in = part is strictly prohibited. E-mail may contain viruses. Before opening attachments please check them = for viruses and defects. While MindTree Consulting Limited (MindTree) = has put in place checks to minimize the risks, MindTree will not be = responsible for any viruses or defects or any forwarded attachments = emanating either from within MindTree or outside. Please note that e-mails are susceptible to change and MindTree shall = not be liable for any improper, untimely or incomplete transmission. MindTree reserves the right to monitor and review the content of all = messages sent to or from MindTree e-mail address. Messages sent to or = from this e-mail address may be stored on the MindTree e-mail system or = else where. |