Recherche avancée

Sur d’autres sites (4441)

• ffmpeg compilation error in windows 10 x64 for Visual Studio 2015 CE

  12 avril 2016, par Anqush

  So i was trying to use FFmpegInterop for win10 UWP application. And followed the specification given on https://trac.ffmpeg.org/wiki/CompilationGuide/WinRT.

  here is some environment information :

  VS2015 Community Edition with 10.0.10240.0 SDK

  OS : Windows 10 Enterprise x64

  PATH were set to:Program Files (x86)/Microsoft Visual Studio 14.0/VC/BIN/x64_ARM

  So when i did this in msys2_shell.bat

  ../../../configure \
  
  --toolchain=msvc \
  
  --disable-programs \
  
  --disable-d3d11va \
  
  --disable-dxva2 \
  
  --arch=x86_64 \
  
  --enable-shared \
  
  --enable-cross-compile \
  
  --target-os=win32 \
  
  --extra-cflags="-MD -DWINAPI_FAMILY=WINAPI_FAMILY_APP -D_WIN32_WINNT=0x0A00" \
  
  --extra-ldflags="-APPCONTAINER WindowsApp.lib" \
  
  --prefix=../../../Build/Windows10/x64

  I got a warning regarding some pkg file that can’t be found and may cause library detection issues.

  For then i ignored it. After that i entered

  make

  this started a series of processing in which there is a lot of possibly harmful warnings. Like :-

  c:\ffmpeginterop\ffmpeg\libavcodec\get_bits.h(307): warning C4101: 're_cache': unreferenced local variable
  
  CC libavformat/srtdec.o
  
  srtdec.c
  
  c:\ffmpeginterop\ffmpeg\libavutil\libm.h(438): warning C4211: nonstandard extension used: redefined extern to static
  
  c:\ffmpeginterop\ffmpeg\libavformat\subtitles.h(189): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data

  So my question is that. Is this dangerous to proceed with. Can you help me for i should proceed with my project without any worry or not ? And i would be gratefull if anyone can guide me to watc out for specific errors that this could generate.

  I know this is a lot to ask. But i would be gratefull.
  Thanks

  Edit : Now i cant run the samples included in the ffmpeginterop package. The sample project wont debug. saying these are out of date.

• FFmpeg function avdevice_list_devices causes C++ Runtime error

  29 mai 2023, par ffvideoner

  I use Windows, C#, FFmpeg.AutoGen.
I want to get list of devices.

  


  public static class Helpers
{

    private static unsafe AVDeviceInfoList** _devicesList;

    public static unsafe void GetMediaSourceNames()
    {

        ffmpeg.avdevice_register_all();

        AVFormatContext* context = ffmpeg.avformat_alloc_context();

        ffmpeg.avdevice_list_devices(context, _devicesList);

    }

}


  


  Function avdevice_list_devices() causes error :

  


  


  Microsoft Visual C++ Runtime Library.
This application has requested the Runtime to terminate it in an unusual way.

  


  


  What am I doing wrong ?

  


  UPDATE

  


  Another reason for the error :

  


  Assertion s->oformat || s->iformat failed at src/libavdevice/avdevice.c:192


  


  If we look at the context in debugging, we will see that context.oformat and context.iformat are equal to zero.

  


  UPDATE 2

  


  If set some non-zero value, then the error will disappear.
Like this :

  


  AVInputFormat avformat = new AVInputFormat();

(*context).iformat = &avformat;


  


  But can't get list of devices.
Now the code looks like this. The last line throws an exception "Object reference not set to an instance of an object". But in debugging can see the value of nb_devices is ten (in fact, there are no devices at all).

  


  public static class Helpers
{

    private static unsafe AVDeviceInfoList* _devicesList;


    public static unsafe void GetMediaSourcesNames()
    {

        ffmpeg.avdevice_register_all();

        AVFormatContext* context = ffmpeg.avformat_alloc_context();


        AVInputFormat avformat = new AVInputFormat();

        (*context).iformat = &avformat;


        fixed (AVDeviceInfoList** devicesListPointer = &_devicesList)
        {
            ffmpeg.avdevice_list_devices(context, devicesListPointer);
        }


        int devicesQuantity = (*_devicesList).nb_devices;

    }

}


  


• configure : Define feature test macros for —std=gnu99

  31 janvier 2016, par Henrik Gramner

  configure : Define feature test macros for —std=gnu99
  Makes the printf() family functions on MinGW use the correct C99 POSIX
  
  versions instead of the broken pre-VS2015 Microsoft ones.
  Also allows us to get rid of some _GNU_SOURCE and _ISOC99_SOURCE defines.
  

  • [DH] common/cpu.c
  • [DH] common/set.c
  • [DH] configure
  • [DH] encoder/analyse.c
  • [DH] encoder/ratecontrol.c
  • [DH] x264.c