Recherche avancée

Sur d’autres sites (7345)

• shared library built with g++ compile is works and with automake compile can not be used

  23 avril 2013, par user2310175

  I'm building a shared libraries on CentOS 6.2.
  The shared library will be build have some cpp files,headers,c shared libraries
  and ffmpeg.The shared library is used to convert videos. When i use the g++ compile like this :

  g++    DataType.h    h264function.h  h264function.cpp videoconvert.h videoconvert.cpp      stdafx.h stdafx.cpp YV12toRGB.h YV12toRGB.cpp -lMPCtrl -lavcodec -lavformat -lavutil -   lhcnetsdk -lPlayCtrl -lpthread -fPIC -shared -o libtest.so

  It can work properly,and the video can be converted as standard h264 coded.That seems the files used for building the library is

  good.But when i use the autotools to make the library,it can not work correct.Here is my configure.in and Makefile.am :

  Makefile.am :

  prefix=/usr
  
  lib_LTLIBRARIES=libhikvisiontranso.la
  
  
  
  libhikvisiontranso_la_SOURCES=stdafx.h stdafx.cpp videoconvert.h videoconvert.cpp 
  
  h264function.h h264function.cpp YV12toRGB.h YV12toRGB.cpp DataType.h 
  
  
  
  libhikvisiontranso_la_LDFLAGS=-avoid-version -shared 
  
  libhikvisiontranso_la_LIBADD=-lpthread -lMPCtrl -lhcnetsdk -lPlayCtrl -lavformat -    lavcodec -lavutil
  
  ACLOCAL_AMFLAGS= -I m4

  configure.in :

  #                                               -*- Autoconf -*-
  
  # Process this file with autoconf to produce a configure script.
  
  
  
  AC_PREREQ([2.63])
  
  AC_INIT([hikvisiontranso],[1.0], [songxiawuren@gmail.com])
  
  AM_INIT_AUTOMAKE([libhikvisiontranso.so],[1.0])
  
  AC_CONFIG_SRCDIR([DataType.h])
  
  AC_CONFIG_HEADERS([config.h])
  
  AC_CONFIG_MACRO_DIR([m4])
  
  AT_INIT
  
  # Checks for programs.
  
  AC_PROG_CXX
  
  AC_PROG_CC
  
  
  
  # Checks for libraries.
  
  
  
  # Checks for header files.
  
  AC_CHECK_HEADERS([inttypes.h limits.h stddef.h stdint.h stdlib.h string.h])
  
  
  
  # Checks for typedefs, structures, and compiler characteristics.
  
  AC_HEADER_STDBOOL
  
  AC_C_INLINE
  
  AC_TYPE_INT16_T
  
  AC_TYPE_INT32_T
  
  AC_TYPE_INT64_T
  
  AC_TYPE_INT8_T
  
  AC_TYPE_SIZE_T
  
  AC_TYPE_UINT16_T
  
  AC_TYPE_UINT32_T
  
  AC_TYPE_UINT64_T
  
  AC_TYPE_UINT8_T
  
  
  
  # Checks for library functions.
  
  AC_FUNC_MALLOC
  
  AC_PROG_LIBTOOL
  
  AC_CONFIG_FILES([Makefile])
  
  AC_OUTPUT

  The wrong output is :

  SDL Init
  
  
  
  init console=1
  
  
  
  Output #0, avi, to '/home/ningge/Desktop/HaikangDvr.avi':
  
  
  
  Stream #0.0: Invalid Codec type -1
  
  
  
  Height = 576; Width = 704;totalfram=90000
  
  
  
  Segmentation fault (core dumped)

  The right is :

  SDL Init
  
  
  
  init console=1
  
  
  
  Output #0, avi, to '/home/ningge/Desktop/HaikangDvr.avi':
  
  
  
  Stream #0.0: Video: mpeg4, yuv420p, 704x576, q=2-31, 200 kb/s, 90k tbn, 25 tbc
  
  
  
  Height = 576; Width = 704;totalfram=90000
  
  
  
  CSDLInit goOut 

  I hope someone can help me to find what's wrong with automake.

• Missing functions in new version of FFmpeg

  25 avril 2013, par Asik

  I am upgrading a wrapper around ffmpeg to the most recent version of the library. Some functions have been renamed or replaced. For the most part I've been able to found equivalents easily, but the following two are giving me trouble :

  av_abort_set_callback
  
  av_abort_default_callback

  I could not find these functions by searching online, so what happened to them and what should they be replaced with now ?

  Here is a copy of the header file "abort.h" where they were located :

  /* 
  
   * This file is part of FFmpeg. 
  
   * 
  
   * FFmpeg is free software; you can redistribute it and/or 
  
   * modify it under the terms of the GNU Lesser General Public 
  
   * License as published by the Free Software Foundation; either 
  
   * version 2.1 of the License, or (at your option) any later version. 
  
   * 
  
   * FFmpeg is distributed in the hope that it will be useful, 
  
   * but WITHOUT ANY WARRANTY; without even the implied warranty of 
  
   * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU 
  
   * Lesser General Public License for more details. 
  
   * 
  
   * You should have received a copy of the GNU Lesser General Public 
  
   * License along with FFmpeg; if not, write to the Free Software * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 
  
   */
  
  
  
  #ifndef AVUTIL_ABORT_H
  
  #define AVUTIL_ABORT_H
  
  
  
  /** 
  
   * Causes abnormal program termination. By default, av_abort_callback calls 
  
   * abort() from the stdlib. This behavior can be altered by setting a 
  
   * different av_abort callback function. 
  
   */
  
  
  
  void av_abort_internal(void);
  
  void av_abort_set_callback(void (*)(void));
  
  void av_abort_default_callback(void);
  
  
  
  #define av_abort()    do { av_log(NULL, AV_LOG_ERROR, "Abort at %s:%d\n", __FILE__, __LINE__); av_abort_internal(); } while(0)
  
  
  
  #endif /* AVUTIL_ABORT_H */

• C - FFmpeg streaming from a C program ?

  8 août 2016, par golmschenk

  I’m looking to replicate an FFmpeg command-line command in my C code. Specifically I would like to be able to run :

  ffmpeg -re -i video.mp4 -f mpegts udp://localhost:7777

  One thing I’ve noticed when looking at people’s code who have used the libraries of FFmpeg in their own code is that they often have a few hundred lines of code for a single command similar to an FFmpeg command-line command. I’m guessing this is just because they are doing something very specific, because if I can run that short command on my command line and get what I want it should probably only take about ten lines of code to do the same thing in my C code. This should only take about that much work right ? Why would it take much more ?

  I’m having a bit of difficulty finding explanations on how to use the streaming capabilities of the FFmpeg libraries that aren’t overly complex because they’re for a very specific purpose. Can anyone explain how I might go about writing the code for the above command ? Or at the very least point me to some documentation explaining how to write such a script/program ? Thank you much !

  EDIT : I do hope to run this from an iPhone app eventually so I won’t just be able to straight up call FFmpeg from my program. I’ll need to use the libraries used by FFmpeg.