Recherche avancée

Médias (1)

Mot : - Tags -/stallman

Autres articles (44)

  • 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

  • Encodage et transformation en formats lisibles sur Internet

    10 avril 2011

    MediaSPIP transforme et ré-encode les documents mis en ligne afin de les rendre lisibles sur Internet et automatiquement utilisables sans intervention du créateur de contenu.
    Les vidéos sont automatiquement encodées dans les formats supportés par HTML5 : MP4, Ogv et WebM. La version "MP4" est également utilisée pour le lecteur flash de secours nécessaire aux anciens navigateurs.
    Les documents audios sont également ré-encodés dans les deux formats utilisables par HTML5 :MP3 et Ogg. La version "MP3" (...)

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

Sur d’autres sites (7914)

  • Location of the amd64 compiler in Visual Studio 2022 | Compiling FFmpeg with NVENC

    6 juin 2022, par Gal Grünfeld

    I'm trying to follow Nvidia's guide to compile FFmpeg with nvenc support on Windows and it has a stage to export the path of Visual Studio's 2013 SP2 amd64 compiler to the global path variable of the compilation dev environment :

    


    


    export PATH="/c/Program Files (x86)/Microsoft Visual Studio 12.0/VC/BIN/amd64/" :$PATH

    


    


    They say earlier in the guide that for different versions of Visual Studio different path might be required. I'm trying to use Visual Studio 2022 Community, but don't know where its amd64 compiler directory is.
I also don't know what that VC stands for ("Visual C", maybe, whatever that "Visual" might mean ?).

    


    I found in the installation directory of Visual Studio 2022 a few directories named amd64 but none of them were under one with VC or something similar in its name.
The one I think is the most likely candidate to be the updated compiler is at /MSBuild\Current\Bin\amd64.

    


    If anyone knows, please tell me if if this is the right path, and if not, what is the right path.

    


    Microsoft does offer a version of Visual Studio 2013 Update 2, though (I assume they changed their naming scheme from "service packs" to "updates, which would make it the same software), but it doesn't offer a 64-bit version of it, and I want to compile a 64-bit software - so I assume it doesn't come with one. Please do correct me if I'm wrong, it'd save me needing to use a version of Visual Studio that is different than the one in the guide.

    


  • ffmpeg - error processing files generated by premier pro 2022

    23 mai 2022, par QRrabbit

    Please help with the error, trying to re-encode the source file produced with prores 4444+alpha. Alpha channel is required in my case.

    


    I've tried two separate options, both are erroring out :

    


    $ ffmpeg -i Input.mxf -vcodec prores_ks -profile:v 4 -y Output.mxf 


    


    I'm getting this output

    


    ffmpeg version 4.4 Copyright (c) 2000-2021 the FFmpeg developers
  built with Apple clang version 12.0.5 (clang-1205.0.22.9)
  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.4_2 --enable-shared --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libdav1d --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libspeex --enable-libsoxr --enable-libzmq --enable-libzimg --disable-libjack --disable-indev=jack --enable-avresample --enable-videotoolbox
  libavutil      56. 70.100 / 56. 70.100
  libavcodec     58.134.100 / 58.134.100
  libavformat    58. 76.100 / 58. 76.100
  libavdevice    58. 13.100 / 58. 13.100
  libavfilter     7.110.100 /  7.110.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  9.100 /  5.  9.100
  libswresample   3.  9.100 /  3.  9.100
  libpostproc    55.  9.100 / 55.  9.100
Input #0, mxf, from 'Input.mxf':
  Metadata:
    operational_pattern_ul: 060e2b34.04010101.0d010201.01010100
    uid             : b52947e8-d982-11ec-9a2d-b42e99ab5f4d
    generation_uid  : b52947e9-d982-11ec-a612-b42e99ab5f4d
    company_name    : Adobe Inc.
    product_name    : Premiere Pro
    product_version_num: 2.0.0.0.1
    product_version : 22.4.0
    application_platform: Mac OS X
    product_uid     : 0c3919fe-46e8-11e5-a151-feff819cdc9f
    toolkit_version_num: 5.3.6.0.1
    modification_date: 2022-05-22T03:53:15.000000Z
    material_package_umid: 0x060A2B340101010501010D1113000000F88BD5002197058861C9B42E99AB5F4D
    timecode        : 00:00:00;00
  Duration: 00:00:59.66, start: 0.000000, bitrate: 32803 kb/s
  Stream #0:0: Video: prores (4444) (ap4h / 0x68347061), yuva444p12le(tv, bt709, progressive), 1920x1080, SAR 1:1 DAR 16:9, 29.97 tbr, 29.97 tbn, 29.97 tbc
    Metadata:
      file_package_umid: 0x060A2B34010101050101051213D028BEF88BD500219705880089B42E99AB5F4D
      file_package_name: Source Package
      track_name      : Track 1
Stream mapping:
  Stream #0:0 -> #0:0 (prores (native) -> prores (prores_ks))
Press [q] to stop, [?] for help
Output #0, mxf, to 'Output.mxf':
  Metadata:
    operational_pattern_ul: 060e2b34.04010101.0d010201.01010100
    uid             : b52947e8-d982-11ec-9a2d-b42e99ab5f4d
    generation_uid  : b52947e9-d982-11ec-a612-b42e99ab5f4d
    timecode        : 00:00:00;00
    material_package_umid: 0x060A2B340101010501010D1113000000F88BD5002197058861C9B42E99AB5F4D
    product_version_num: 2.0.0.0.1
    modification_date: 2022-05-22T03:53:15.000000Z
    application_platform: Mac OS X
    product_uid     : 0c3919fe-46e8-11e5-a151-feff819cdc9f
    toolkit_version_num: 5.3.6.0.1
    encoder         : Lavf58.76.100
  Stream #0:0: Video: prores (ap4h / 0x68347061), yuva444p10le(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 29.97 fps, 29.97 tbn
    Metadata:
      file_package_umid: 0x060A2B34010101050101051213D028BEF88BD500219705880089B42E99AB5F4D
      file_package_name: Source Package
      track_name      : Track 1
      encoder         : Lavc58.134.100 prores_ks
[mxf @ 0x7fbbbc008200] could not get prores profile0:00.00 bitrate=N/A speed=   0x    
av_interleaved_write_frame(): Operation not permitted
Error writing trailer of Output.mxf: Unknown error occurred
frame=   33 fps= 27 q=-0.0 Lsize=       0kB time=00:00:00.03 bitrate=   0.0kbits/s speed=0.027x    
video:67kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
Conversion failed!


    


    Above I can't even fully see the error since the red text over black background covers the screen :
enter image description here

    


    I have also tried the following encoding options :

    


     -c:v qtrle -pix_fmt argb 


    


    to which, I'm getting the following error :

    


    track 0: could not find essence container ul, codec not currently supported in container
Could not write header for output file #0 (incorrect codec parameters ?): Operation not permitted
Error initializing output stream 0:0 --
Conversion failed!


    


    In case this is helpful, I'm displaying MediaInfo for the source file :
enter image description here

    


  • Trouble building ffmpeg with cuda for windows 32 with visual studio 2022

    27 juillet 2022, par manou

    Here is my building process

    


    I open mingw32 from the x64 Native Tools Command Prompt for VS 2022

    


    then in the mingw32 shell :

    


    # cd /
# ./c/Program\ Files/Microsoft\ Visual\ Studio/2022/Community/VC/Auxiliary/Build/vcvars32.bat
# cd ~
# pacman -Sy diffutils git make gcc yasm pkg-config --noconfirm
# git clone --depth 1 https://git.ffmpeg.org/ffmpeg.git ffmpeg 
# git clone https://git.videolan.org/git/ffmpeg/nv-codec-headers.git nv-codec-headers 
# cd nv-codec-headers/
# make PREFIX=/usr/local
# make install PREFIX=/usr/local
# cd ..
# mkdir nv_sdk
# cp -r /c/Program\ Files/NVIDIA\ GPU\ Computing\ Toolkit/CUDA/v11.7/lib/Win32/* nv_sdk
# cp -r /c/Program\ Files/NVIDIA\ GPU\ Computing\ Toolkit/CUDA/v11.7/include/* nv_sdk
# export PATH="/c/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.32.31326/bin/Hostx86/x86/":$PATH
# export PATH="/c/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.7/bin/":$PATH
# ./configure --disable-everything --enable-decoder=h264 --enable-decoder=hevc --enable-cross-compile --disable-avdevice --disable-swresample --disable-postproc --disable-avfilter --target-os=mingw32 --enable-cuda-nvcc --enable-nonfree --toolchain=msvc --extra-cflags=-I../nv_sdk --extra-ldflags=" -m32 -L../nv_sdk" --enable-shared --shlibdir=SHARED_LIBS --arch=x86_32 --enable-runtime-cpudetect --enable-w32threads
# make -j8
# make install


    


    first I have a bunch of warnings during the making looking like that :
libavutil/opt.c(1075): warning C4133: 'fonction' : types incompatibles - de 'AVPixelFormat *' à 'int *'

    


    And finally the make install returns :

    


    EXTERN_PREFIX="_" AR="lib.exe" NM="dumpbin.exe -symbols" ./compat/windows/makedef libavutil/libavutil.ver libavutil/adler32.o libavutil/aes.o libavutil/aes_ctr.o libavutil/audio_fifo.o libavutil/avsscanf.o libavutil/avstring.o libavutil/base64.o libavutil/blowfish.o libavutil/bprint.o libavutil/buffer.o libavutil/camellia.o libavutil/cast5.o libavutil/channel_layout.o libavutil/color_utils.o libavutil/cpu.o libavutil/crc.o libavutil/des.o libavutil/detection_bbox.o libavutil/dict.o libavutil/display.o libavutil/dovi_meta.o libavutil/downmix_info.o libavutil/encryption_info.o libavutil/error.o libavutil/eval.o libavutil/fifo.o libavutil/file.o libavutil/file_open.o libavutil/film_grain_params.o libavutil/fixed_dsp.o libavutil/float_dsp.o libavutil/frame.o libavutil/hash.o libavutil/hdr_dynamic_metadata.o libavutil/hdr_dynamic_vivid_metadata.o libavutil/hmac.o libavutil/hwcontext.o libavutil/hwcontext_d3d11va.o libavutil/hwcontext_dxva2.o libavutil/imgutils.o libavutil/integer.o libavutil/intmath.o libavutil/lfg.o libavutil/lls.o libavutil/log.o libavutil/log2_tab.o libavutil/lzo.o libavutil/mastering_display_metadata.o libavutil/mathematics.o libavutil/md5.o libavutil/mem.o libavutil/murmur3.o libavutil/opt.o libavutil/parseutils.o libavutil/pixdesc.o libavutil/pixelutils.o libavutil/random_seed.o libavutil/rational.o libavutil/rc4.o libavutil/reverse.o libavutil/ripemd.o libavutil/samplefmt.o libavutil/sha.o libavutil/sha512.o libavutil/slicethread.o libavutil/spherical.o libavutil/stereo3d.o libavutil/tea.o libavutil/threadmessage.o libavutil/time.o libavutil/timecode.o libavutil/tree.o libavutil/twofish.o libavutil/tx.o libavutil/tx_double.o libavutil/tx_float.o libavutil/tx_int32.o libavutil/utils.o libavutil/version.o libavutil/video_enc_params.o libavutil/x86/cpu.o libavutil/x86/cpuid.o libavutil/x86/fixed_dsp.o libavutil/x86/fixed_dsp_init.o libavutil/x86/float_dsp.o libavutil/x86/float_dsp_init.o libavutil/x86/imgutils.o libavutil/x86/imgutils_init.o libavutil/x86/lls.o libavutil/x86/lls_init.o libavutil/x86/tx_float.o libavutil/x86/tx_float_init.o libavutil/xga_font_data.o libavutil/xtea.o > libavutil/avutil-57.def
Could not create temporary library.
make: *** [ffbuild/library.mak:118: libavutil/avutil-57.dll] Error 1


    


    What am I doing wrong ?
shall I install others packets from pacman ?