Recherche avancée

Sur d’autres sites (13233)

• Latest FFmpeg fails to create a good MP4 out of JPG file (Windows 10)

  30 décembre 2023, par mengrie

  I am using FFmpeg to create an MP4 file out of several JPG files. The command to accomplish this

  


  ffmpeg.exe ^
-hide_banner -nostats -loglevel error -y ^
-loop 1 -t 6 -i 001.jpg ^
-loop 1 -t 6 -i 002.jpg ^
-loop 1 -t 6 -i 003.jpg ^
-loop 1 -t 6 -i 004.jpg ^
-loop 1 -t 6 -i 005.jpg ^
-loop 1 -t 6 -i 006.jpg ^
-filter_complex ^
"[0:v]scale=1920:1080:force_original_aspect_ratio=decrease,pad=1920:1080:(ow-iw)/2:(oh-ih)/2,setsar=1,fade=t=out:st=5:d=1[v0]; ^
[1:v]scale=1920:1080:force_original_aspect_ratio=decrease,pad=1920:1080:(ow-iw)/2:(oh-ih)/2,setsar=1,fade=t=in:st=0:d=1,fade=t=out:st=5:d=1[v1]; ^
[2:v]scale=1920:1080:force_original_aspect_ratio=decrease,pad=1920:1080:(ow-iw)/2:(oh-ih)/2,setsar=1,fade=t=in:st=0:d=1,fade=t=out:st=5:d=1[v2]; ^
[3:v]scale=1920:1080:force_original_aspect_ratio=decrease,pad=1920:1080:(ow-iw)/2:(oh-ih)/2,setsar=1,fade=t=in:st=0:d=1,fade=t=out:st=5:d=1[v3]; ^
[4:v]scale=1920:1080:force_original_aspect_ratio=decrease,pad=1920:1080:(ow-iw)/2:(oh-ih)/2,setsar=1,fade=t=in:st=0:d=1,fade=t=out:st=5:d=1[v4]; ^
[5:v]scale=1920:1080:force_original_aspect_ratio=decrease,pad=1920:1080:(ow-iw)/2:(oh-ih)/2,setsar=1,fade=t=in:st=0:d=1,fade=t=out:st=5:d=1[v5]; ^
[v0][v1][v2][v3][v4][v5]concat=n=6:v=1:a=0,format=yuv420p[v]" -map "[v]" -r 30 006.mp4


  


  Using "ffmpeg version 2022-12-25-git-eeb280f351-full_build-www.gyan.dev Copyright (c) 2000-2022 the FFmpeg developers built with gcc 12.1.0 (Rev2, Built by MSYS2 project)" does the job as expected.

  


  However, yesterdag I downloaded (from gyan.dev - Windows - ffmpeg-git-full.7z) the latest version and upgrade the tool. "ffmpeg version 2023-12-28-git-c1340f3439-full_build-www.gyan.dev Copyright (c) 2000-2023 the FFmpeg developers built with gcc 12.2.0 (Rev10, Built by MSYS2 project)"

  


  Using this version, the MP4 contains only a few JPGs and timing is also messed up, resulting in a useless MP4.

  


  Has something changed or are these parameters causing a new behaviour ?

  


  Thx

  


  In meanwhile I went back to older version

  


• Exception thrown at 0x00007FFC0B57BCEF (swscale-6.dll) in App.exe : 0xC0000005 : Access violation reading location 0xFFFFFFFFFFFFFFFF

  9 novembre 2023, par JIUN-YU

  Trying to play a video using FFmpeg on visual studio 2022 on windows 10.
Exception is thrown at sws_scale in the code. Don't know why this is occurred.
It is worth noting that this error sometimes occurs when reading the camera and sometimes it does not.

  


  here is my code

  


  bool CalibrationPanel::video_reader_read_frame(VReaderState* state, cv::Mat cvimg)
{
    // Unpack members of state
    auto& width = state->width;
    auto& height = state->height;
    auto& av_format_ctx = state->av_format_ctx;
    auto& av_codec_ctx = state->av_codec_ctx;
    auto& video_stream_index = state->video_stream_index;
    auto& av_frame = state->av_frame;
    auto& av_packet = state->av_packet;
    auto& sws_scaler_ctx = state->sws_scaler_ctx;


    // Decode one frame
    int response;
    while (av_read_frame(av_format_ctx, av_packet) >= 0)
    {
        if (av_packet->stream_index != video_stream_index)
        {
            av_packet_unref(av_packet);
            continue;
        }

        response = avcodec_send_packet(av_codec_ctx, av_packet);
        if (response < 0)
        {
            char errStr[256] = {0};
            av_strerror(response, errStr, sizeof(errStr));
            printf("Failed to decode packet: %s\n", errStr);
            return false;
        }

        response = avcodec_receive_frame(av_codec_ctx, av_frame);
        if (response == AVERROR(EAGAIN) || response == AVERROR_EOF)
        {
            av_packet_unref(av_packet);
            continue;
        }
        else if (response < 0)
        {
            char errStr[256] = {0};
            av_strerror(response, errStr, sizeof(errStr));
            printf("Failed to decode packet: %s\n", errStr);
            return false;
        }

        av_packet_unref(av_packet);
        break;
    }
    int64_t* pts = &ppts;
    *pts = av_frame->pts;

    // Set up sws scaler
    if (!sws_scaler_ctx)
    {
        sws_scaler_ctx = sws_getContext(width, height, av_codec_ctx->pix_fmt,
                                        width, height, AV_PIX_FMT_BGR24,
                                        SWS_BILINEAR, NULL, NULL, NULL);
        if (!sws_scaler_ctx)
        {
            printf("Couldn't initialize sw scaler\n");
            return false;
        }
    }


    // Creating an image space to hold YUV images
    AVFrame* frameYUV = av_frame_alloc();
    auto* out_buffer = (unsigned char*)av_malloc(av_image_get_buffer_size(AV_PIX_FMT_BGR24, width, height, 1));
    av_image_fill_arrays(frameYUV->data, frameYUV->linesize, (const uint8_t*)out_buffer, AV_PIX_FMT_BGR24, width, height, 1);

    uint8_t* dest[4] = {cvimg.data, NULL, NULL, NULL};
    sws_scale(sws_scaler_ctx, av_frame->data, av_frame->linesize, 0, av_frame->height, dest, frameYUV->linesize);

    return true;
}


  


  fixed this bug, so it's not luck that makes the camera turn on every time.

  


• Problem with Linking FFMPEG Libraries in Visual Studio on Windows 10 [closed]

  14 mars 2024, par Dentricky73

  I'm facing an issue while trying to link FFMPEG libraries in Visual Studio on a Windows 10 OS. Specifically, Visual Studio seems to locate the headers correctly, but encounters difficulties in finding the associated libraries. Initially, I attempted to compile the FFMPEG SDK myself, but encountered problems with the library extensions, which ended with a Linux .o file instead of a Windows .lib. Subsequently, I downloaded a prebuilt version from here, but I'm still encountering errors.

  


  In Visual Studio 2022, I've configured the following settings :

  


  


  Property > Configuration Properties > C/C++ > General > Additional Include Directories
C :\cmder\c++SDK\ffmpeg\include

  


  


  


  Property > Configuration Properties > Linker > General > Additional Library Directories
C :\cmder\c++SDK\ffmpeg\lib

  


  


  


  Property > Configuration Properties > Linker > Input > Additional Dependencies
avcodec.lib, avdevice.lib, avfilter.lib, avformat.lib, avutil.lib, postproc.lib, swresample.lib, swscale.lib

  


  


  Despite these configurations, Visual Studio fails to locate the FFMPEG libraries during the linking process. Could someone please provide guidance on how to resolve this issue and correctly link the FFMPEG libraries in Visual Studio on Windows ? Any help or insights would be greatly appreciated.

  


  Specific Issues Encountered :

  


  During the compilation and linking process in Visual Studio 2022, I encountered the following errors :

  


  Error 1 : A value of type "const AVCodec *" cannot be used to initialize an entity of type "AVCodec *".
Error 2 : Identifier "av_free_packet" is undefined.
Error 3 : Class "AVStream" has no member "codec".
Error 4 : Class "AVFrame" has no member "owner".
Despite configuring the project settings to include the correct include directories and library dependencies, these errors persist.

  


  Why Previous Attempts Didn't Meet My Needs :

  


  My previous attempts to resolve these issues were unsuccessful because I couldn't pinpoint the root cause of the compilation and linking errors. While I ensured that the include directories and library dependencies were correctly configured in Visual Studio, the errors persisted, indicating that there may be underlying issues with the setup or compatibility between the FFMPEG SDK and Visual Studio environment.