Recherche avancée

Médias (91)

Autres articles (67)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

Sur d’autres sites (5374)

  • Slow execution of cuCtxDestroy causing Windows desktop freeze [closed]

    24 avril 2024, par sun

    I’m encountering a problem with the cuCtxDestroy function that seems to be causing my system to freeze and result in a black screen. I’m running Windows 11 on my computer, and I would appreciate any assistance in troubleshooting this issue.

    


    When I call cuCtxDestroy, it takes more than 10 seconds to complete, during which both the GPU and CPU appear to be stuck. Eventually, the screen goes black, and in some cases, the system may recover, while in other cases, it requires a system reboot.

    


    Here is some information about my system :

    


      

    • Integrated Intel graphics card

      


    • 


    • NVIDIA GeForce GTX 1650

      


    • 


    • Driver Version : 546.65

      


    • 


    • CUDA Version : 12.3

      


    • 


    • Windows 11

      


    • 


    


    cuda profile image

    


  • ffmpeg error with device when transcoding from HEVC to H.264 on GPU using NVENC [closed]

    5 décembre 2022, par Slakter

    I wanted to transcode my videos that have hevc encoding into h.264 using ffmpeg with Nvidia CUDA acceleration.
Basically I've followed the guide provided in the official documentation and read through CUDA part in here

    


    My GPU is GeForce RTX2060 and the OS is Windows 10

    


    ffmpeg configuration just after start says :

    


    ffmpeg version 5.1.2-essentials_build-www.gyan.dev Copyright (c) 2000-2022 the FFmpeg developers
  built with gcc 12.1.0 (Rev2, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-sdl2 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libgme --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libtheora --enable-libvo-amrwbenc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-librubberband
  libavutil      57. 28.100 / 57. 28.100
  libavcodec     59. 37.100 / 59. 37.100
  libavformat    59. 27.100 / 59. 27.100
  libavdevice    59.  7.100 / 59.  7.100
  libavfilter     8. 44.100 /  8. 44.100
  libswscale      6.  7.100 /  6.  7.100
  libswresample   4.  7.100 /  4.  7.100
  libpostproc    56.  6.100 / 56.  6.100


    


    So all the required options for Nvidia encoding are in the list.

    


    Then I tried to transcode a video in mkv format with encoding H.265 (hevc) into h.264 using h264_nvenc .
Here is the line

    


     ffmpeg -hwaccel cuda -hwaccel_device 0 -hwaccel_output_format cuda -extra_hw_frames 14 -i .\input.mkv -c:v h264_nvenc -profile:v high444p -pixel_format yuva444p16le -preset lossless -b:v 1M output.mp4 -y


    


    Even when I leave just this, the error is the same

    


     ffmpeg -hwaccel cuda -hwaccel_device 0 -hwaccel_output_format cuda -i .\Violet1.mkv -c:v h264_nvenc output.mp4 -y


    


    Here is the error message :

    


    Stream mapping:
  Stream #0:0 -> #0:0 (hevc (native) -> h264 (h264_nvenc))
  Stream #0:1 -> #0:1 (opus (native) -> aac (native))
Press [q] to stop, [?] for help
[h264_nvenc @ 000002023642d7c0] 10 bit encode not supported
[h264_nvenc @ 000002023642d7c0] Provided device doesn't support required NVENC features
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height


    


    Also, If I take another file with encoding H.265 (hev1) in mp4 format and use the command below, then it works fine.

    


    ffmpeg -hwaccel cuda -hwaccel_device 0 -hwaccel_output_format cuda -extra_hw_frames 5 -i .\hev1.mp4 -gpu 0 -c:v h264_nvenc -profile:v high444p -preset lossless -b:v 1M output.mp4 -y


    


    It's the same as the first command but with different extra_hw_frames and output file

    


    My guess is that the problem in encoding from mkv or hevc codec specifically or maybe I have to change some options, but I haven't found anything about this error in the net. Thanks everyone how could help

    


  • VLC huge buffering times over rtp for local H264 stream

    15 mars 2022, par mike

    I'm outputting an H264 stream, encoded by my application using ffmpeg. I can display it using ffplay, but when trying to view the stream in VLC, I only get the first frame, or it looks like that's the case.

    


    The messages output shows that it is "buffering", taking around a minute to get to 100% when the frame updates.
When using ffplay, the latency is about 50-100ms at worst.

    


    I am sending to rtp://127.0.0.1:6666?pkt_size=1316 with the format rtp_mpegts.
I am new to this and it's highly likely I haven't set the frame up completely correctly. The process is (minus declarations and error checking)

    


    codec_name = "libx264";&#xA;codec = avcodec_find_encoder_by_name(codec_name.c_str());&#xA;context = avcodec_alloc_context3(codec);&#xA;pkt = av_packet_alloc();&#xA;context->bit_rate = 5 * Mega;&#xA;context->width = info.DisplayWidth;&#xA;context->height = info.DisplayHeight;&#xA;context->time_base = { 1, FPS };&#xA;context->framerate = { FPS, 1 };&#xA;context->gop_size = 100;&#xA;context->max_b_frames = 1;            &#xA;context->pix_fmt = AV_PIX_FMT_YUV420P;&#xA;if (codec->id == AV_CODEC_ID_H264)&#xA;            {&#xA;                check_ret("set option: preset", av_opt_set(context->priv_data, "preset", "fast", 0));&#xA;                check_ret("set option: tune", av_opt_set(context->priv_data, "tune", "zerolatency", 0));&#xA;                check_ret("set option: profile", av_opt_set(context->priv_data, "profile", "baseline", 0));                &#xA;            }&#xA;check_ret("open codec", avcodec_open2(context, codec, NULL));&#xA;&#xA;// setup the stream &#xA;fmt = (AVOutputFormat*)av_guess_format("rtp_mpegts", NULL, NULL);&#xA;&#xA;avformat_alloc_output_context2(&amp;avfctx, fmt, fmt->name,&#xA;            "rtp://127.0.0.1:6666?pkt_size=1316"); &#xA;        &#xA;avio_open(&amp;avfctx->pb, avfctx->url, AVIO_FLAG_WRITE);&#xA;AVStream* stream = avformat_new_stream(avfctx, codec);&#xA;avcodec_parameters_from_context(stream->codecpar, context);&#xA;stream->time_base.num = 1;&#xA;stream->time_base.den = FPS;&#xA;avformat_write_header(avfctx, NULL);&#xA;&#xA;// then the encoding (in an output loop)&#xA;<not get="get" frame="frame" from="from" rgba="rgba" to="to" yuv="yuv">&#xA;yuvFrame->pts = i&#x2B;&#x2B;; // i is incremented every frame&#xA;avcodec_send_frame(enc_ctx, yuvFrame);&#xA; while (ret >= 0) {&#xA;  ret = avcodec_receive_packet(enc_ctx, pkt);          &#xA;  //ret = av_interleaved_write_frame(avfctx, pkt); was using this, don&#x27;t seem to need it&#xA;  ret = av_write_frame(avfctx, pkt);&#xA;  av_packet_unref(pkt);&#xA;}&#xA;</not>

    &#xA;

    The VLC output looks like this :

    &#xA;

    main debug: using hw decoder module "d3d11va"&#xA;avcodec info: Using D3D11VA (NVIDIA GeForce RTX 2080 Super with Max-Q Design, vendor 10de(NVIDIA), device 1e93, revision a1) for hardware decoding&#xA;qt debug: Logical video size: 1280x720&#xA;main debug: resized to 1280x720&#xA;main debug: VoutDisplayEvent &#x27;resize&#x27; 1280x720&#xA;main debug: Received first picture&#xA;main debug: Buffering 1%&#xA;main debug: Buffering 2%&#xA;main debug: Buffering 3%&#xA;main debug: auto hiding mouse cursor&#xA;main debug: Buffering 4%&#xA;main debug: Buffering 5%&#xA;main debug: Buffering 6%&#xA;main debug: Buffering 7%&#xA;main debug: Buffering 8%&#xA;main debug: Buffering 9%&#xA;main debug: Buffering 10%&#xA;main debug: auto hiding mouse cursor&#xA;main debug: Buffering 11%&#xA;rtp warning: 1 packet(s) lost&#xA;rtp warning: 1 packet(s) lost&#xA;rtp warning: 1 packet(s) lost&#xA;ts warning: discontinuity received 0x3 instead of 0xd (pid=256)&#xA;ts warning: discontinuity received 0x5 instead of 0xf (pid=256)&#xA;ts warning: discontinuity received 0x1 instead of 0xb (pid=256)&#xA;main debug: Buffering 12%&#xA;main debug: Buffering 13%&#xA;main debug: Buffering 14%&#xA;main debug: Buffering 15%&#xA;main debug: Buffering 16%&#xA;main debug: Buffering 17%&#xA;main debug: Buffering 18%&#xA;main debug: auto hiding mouse cursor&#xA;main debug: Buffering 19%&#xA;main debug: Buffering 20%&#xA;

    &#xA;