Recherche avancée

Médias (1)

Mot : - Tags -/artwork

Autres articles (49)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (8089)

  • x264vfw Configuration Settings in VC++

    18 mai 2012, par meghana

    i need to set All configuration settings of x264Vfw from pragmatically from code (in VC++ ).

    Do anybody have reference code or guide for that ??

    Thanks

  • FFMPEG, MPV, SVP 4 Pro : not converting as original resolution problem, yuv420p10 -> p010 [closed]

    12 août 2023, par LeeShey

    I am using SVP4 Pro(Frame rate conversion).
The SVP 4 Pro setting :
RIFE AI engine setting
encoder commands
Transcoding 4K(3840x2160) video exports 3840x2144 resolution.
I think converting yuv420p10 -> p010 causes video height loss.

    


    I did transcoding FHD video(just for test), but it worked lossless.
Problems to 4K, but not FHD ??

    


    Here's the log :

    


    19:36:05.942: ===== Starting mpv ======
19:36:05.942: Command line: C:\Program Files (x86)\SVP 4\mpv64\mpv.exe D:/Candy/prob3.mov --o=D:/Candy/prob3.SVP.VO.mov --no-audio --no-sub --no-sub-auto --input-ipc-server=mpvencodepipe --input-media-keys=no --no-msg-color --vf=lavfi=[yadif=send_frame],vapoursynth:[C:\Users\????\AppData\Roaming\SVP4\scripts\ffff.py]:4:16 --ovc=hevc_nvenc --ovcopts=preset=lossless,time_base=1000/120000,threads=16
19:36:05.982: (+) Video --vid=1 (*) (prores 3840x2160 60.000fps)
19:36:05.982: Audio --aid=1 --alang=eng (*) (pcm_s16le 2ch 48000Hz)
19:36:06.277: vstrt: TensorRT version mismatch, built with 2135 but loaded with 2136; continue but fingers crossed...
19:36:06.856: CUDA lazy loading is not enabled. Enabling it can significantly reduce device memory usage. See `CUDA_MODULE_LOADING` in https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#env-vars
19:36:06.930: CUDA lazy loading is not enabled. Enabling it can significantly reduce device memory usage. See `CUDA_MODULE_LOADING` in https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#env-vars
19:36:07.005: CUDA lazy loading is not enabled. Enabling it can significantly reduce device memory usage. See `CUDA_MODULE_LOADING` in https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#env-vars
19:36:07.079: CUDA lazy loading is not enabled. Enabling it can significantly reduce device memory usage. See `CUDA_MODULE_LOADING` in https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#env-vars
19:36:09.683: [autoconvert] Converting yuv420p10 -> p010
19:36:09.693: VO: [lavc] 3840x2144 p010
19:36:09.693: [vo/lavc] Opening encoder: NVIDIA NVENC hevc encoder [hevc_nvenc]
19:36:09.695: [ffmpeg] hevc_nvenc: The selected preset is deprecated. Use p1 to p7 + -tune or fast/medium/slow.
19:36:10.130: [encode] Opening output file: D:/Candy/prob3.movprob3.SVP.VO.mov
19:36:10.131: [encode] Opening muxer: QuickTime / MOV [mov]
19:36:10.131: [ffmpeg] mov: WARNING codec timebase is very high. If duration is too long,
19:36:10.131: [ffmpeg] file may not be playable by quicktime. Specify a shorter timebase
19:36:10.131: [ffmpeg] or choose different container.
19:36:10.136: [autoconvert] Converting yuv420p10 -> p010
19:36:10.145: V: 00:00:00 / 00:00:15 (0%) {0.0min 0.0MB}
19:36:11.087: -- PAUSED --



    


  • adpcm : Write the proper predictor in trellis mode in IMA QT

    5 juin 2014, par Martin Storsjö
    adpcm : Write the proper predictor in trellis mode in IMA QT
    

    The actual predictor value, set by the trellis code, never
    was written back into the variable that was written into
    the block header. This was accidentally removed in b304244b.

    This significantly improves the audio quality of the trellis
    case, which was plain broken since b304244b.

    Encoding IMA QT with trellis still actually gives a slightly
    worse quality than without trellis, since the trellis encoder
    doesn’t use the exact same way of rounding as in
    adpcm_ima_qt_compress_sample and adpcm_ima_qt_expand_nibble.

    CC : libav-stable@libav.org
    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DBH] libavcodec/adpcmenc.c