
Recherche avancée
Médias (91)
-
GetID3 - Boutons supplémentaires
9 avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
-
Core Media Video
4 avril 2013, par
Mis à jour : Juin 2013
Langue : français
Type : Video
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
-
Exemple de boutons d’action pour une collection collaborative
27 février 2013, par
Mis à jour : Mars 2013
Langue : français
Type : Image
-
Exemple de boutons d’action pour une collection personnelle
27 février 2013, par
Mis à jour : Février 2013
Langue : English
Type : Image
Autres articles (49)
-
List of compatible distributions
26 avril 2011, parThe table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...) -
Publier sur MédiaSpip
13 juin 2013Puis-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 -
Ajouter notes et légendes aux images
7 février 2011, parPour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
Modification lors de l’ajout d’un média
Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)
Sur d’autres sites (12756)
-
How to use ffmpeg to upscale video resolution with anime4k ?
29 juillet 2023, par IronboxIn Vapoursynth, it is convenient to download and use plugins to change the frame rate of videos. However, it seems that using FFmpeg has more limitations (or maybe I haven't found the right method). Anime4K is a video enhancement algorithm suitable for anime and similar videos. In MPV, their plugins can be imported and used for real-time frame rate conversion.


In FFmpeg, how can I use the algorithms in glsl files to change the video frame rate, instead of using FFmpeg's built-in algorithms ?


In FFmpeg, i can use libplacebo filters can also be used to apply GLSL shaders. In my tests, using command like :


libplacebo=custom_shader_path=Anime4K_Upscale_CNN_x2_VL.glsl



this leads to noticeable GPU usage, but the output video resolution remains the same as the original.


I can pass in the w and h parameters when calling the libplacebo filter :


libplacebo=w=iw*2:h=ih*2:custom_shader_path=shaders/Anime4K_Upscale_CNN_x2_VL.glsl



This achieves the purpose of super resolution, but is it essentially using anime4k for upscaling behind the processing ?
Is it using the upscaling algorithm in libplacebo first, before applying anime4k ? How can I achieve my original goal that only use anime4k to upscale ?
here's my full command (in python) :


[
 'ffmpeg -hide_banner',
 '-hwaccel', 'cuda',
 '-i', '"{input_ab_path}"',
 '-filter_complex',
 '"[0:v]libplacebo=custom_shader_path=libplacebo=custom_shader_path=shaders/Anime4K_Upscale_CNN_x2_VL.glsl,subtitles="{sub_file}":si=0[out]"',
 '-map', '0:a',
 '-map', '"[out]"',
 '-c:v', 'libsvtav1',
 '-svtav1-params', 'scm=2:scd=1:enable-overlays=1:enable-tf=0:tune=0:preset=7:crf=18',
 '-c:a', 'libvorbis',
 '-qscale:a', '10',
 '-pix_fmt', 'yuv420p10le',
 '-y', '"{output_ab_path}"'
]



-
How to use ffmpeg to upscale video resolution with libplacebo ?
30 juillet 2023, par IronboxIn Vapoursynth, it is convenient to download and use plugins to change the frame rate of videos. However, it seems that using FFmpeg has more limitations (or maybe I haven't found the right method). Anime4K is a video enhancement algorithm suitable for anime and similar videos. In MPV, their plugins can be imported and used for real-time frame rate conversion.


In FFmpeg, how can I use the algorithms in glsl files to change the video frame rate, instead of using FFmpeg's built-in algorithms ?


In FFmpeg, i can use libplacebo filters can also be used to apply GLSL shaders. In my tests, using command like :


libplacebo=custom_shader_path=Anime4K_Upscale_CNN_x2_VL.glsl



this leads to noticeable GPU usage, but the output video resolution remains the same as the original.


I can pass in the w and h parameters when calling the libplacebo filter :


libplacebo=w=iw*2:h=ih*2:custom_shader_path=shaders/Anime4K_Upscale_CNN_x2_VL.glsl



This achieves the purpose of super resolution, but is it essentially using anime4k for upscaling behind the processing ?
Is it using the upscaling algorithm in libplacebo first, before applying anime4k ? How can I achieve my original goal that only use anime4k to upscale ?
here's my full command (in python) :


[
 'ffmpeg -hide_banner',
 '-hwaccel', 'cuda',
 '-i', '"{input_ab_path}"',
 '-filter_complex',
 '"[0:v]libplacebo=custom_shader_path=libplacebo=custom_shader_path=shaders/Anime4K_Upscale_CNN_x2_VL.glsl,subtitles="{sub_file}":si=0[out]"',
 '-map', '0:a',
 '-map', '"[out]"',
 '-c:v', 'libsvtav1',
 '-svtav1-params', 'scm=2:scd=1:enable-overlays=1:enable-tf=0:tune=0:preset=7:crf=18',
 '-c:a', 'libvorbis',
 '-qscale:a', '10',
 '-pix_fmt', 'yuv420p10le',
 '-y', '"{output_ab_path}"'
]



-
FFMPEG, MPV, SVP 4 Pro : not converting as original resolution problem, yuv420p10 -> p010 [closed]
12 août 2023, par LeeSheyI 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 --