
Recherche avancée
Médias (1)
-
The Great Big Beautiful Tomorrow
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
Autres articles (90)
-
Le profil des utilisateurs
12 avril 2011, parChaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...) -
Configurer la prise en compte des langues
15 novembre 2010, parAccéder à la configuration et ajouter des langues prises en compte
Afin de configurer la prise en compte de nouvelles langues, il est nécessaire de se rendre dans la partie "Administrer" du site.
De là, dans le menu de navigation, vous pouvez accéder à une partie "Gestion des langues" permettant d’activer la prise en compte de nouvelles langues.
Chaque nouvelle langue ajoutée reste désactivable tant qu’aucun objet n’est créé dans cette langue. Dans ce cas, elle devient grisée dans la configuration et (...) -
XMP PHP
13 mai 2011, parDixit Wikipedia, XMP signifie :
Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...)
Sur d’autres sites (6918)
-
To all Matomo plugin developers : Matomo 4 is coming, make your plugin compatible now
6 août 2020, par Matomo Core Team — DevelopmentWe’re planning to release the first beta of Matomo 4 in a few weeks. For making it easy for Matomo users to be able to upgrade to this beta, it would be great if as many plugins on the Marketplace as possible would be already updated and compatible with Matomo 4. Then many users would be able to upgrade to the first beta without any issues.
Presumably, as you put your plugin on our Marketplace, you want people to use it. Making your plugin compatible with Matomo 4 helps ensure that people will be able to find and keep using your plugin. If your plugin is not compatible with Matomo 4, your plugin will be automatically deactivated. We’ll be happy to help you achieve compatibility should there be any issue.
How do I upgrade my Matomo to Matomo 4 ?
If you have installed your Matomo development environment through git you can simply checkout the Matomo 4 branch “
4.x-dev
” by executing these commands :git checkout 4.x-dev
composer install
Alternatively, you can also download the latest version directly from GitHub as a zip file and run
composer install
afterwards.How do I upgrade my plugin to Matomo 4 ?
- We recommend you create a new branch for your plugin that supports Matomo 4. For example a branch named “
4.x-dev
“. This way you will be able to make changes to your plugin for Matomo 3 and Matomo 4 and release separate versions. - Check out our migration guide from Matomo 3 to Matomo 4 and the list of all breaking changes.
- Release a new version of your plugin in GitHub as usual.
While there were many breaking changes in Matomo 4, most of our Platform APIs remain unchanged, and almost all changes are for rarely used APIs. Often to make your plugin compatible it will just be a matter of adjusting the “
plugin.json
” file (as mentioned in the migration guide).You can find all developer documentation on our developer zone which has already been updated for Matomo 4.
How do I know my plugin changes were released successfully ?
If you have configured an email address within your “
plugin.json
” file, then you will receive a confirmation or an error email within a few minutes. Alternatively, you can also check out your plugin page on the Marketplace directly. If the plugin release was successful, you will see additional links below the download button showing which versions your plugin is compatible with.How can I downgrade to Matomo 3 or switch between Matomo 3 and Matomo 4 ?
To downgrade from Matomo 4 to Matomo 3 :
- check out the “
3.x-dev
” branch - run a composer install as usual.
- run the SQL statements from this downgrade guide to restore the previous MySQL schema.
When will the final Matomo 4 release be available ?
We estimate the final stable Matomo 4.0.0 release will be released in approx. 3 months.
What’s new in Matomo 4 ?
We don’t have a summary of the changes available just yet but you can see all closed issues within this release here.
Any questions or need help ?
If you have any questions, or experience any problems during the migration don’t hesitate to get in touch with us. We’ll be happy to help get your plugin compatible and the update published. If you find any undocumented breaking change or find any step during the migration process not clear, please let us know as well.
Thank you for contributing a plugin to the Marketplace and making Matomo better. We really appreciate your work !
-
ffmpeg vaapi hardware acceleration with some videos not working
15 juillet 2020, par Maisen1886I have a problem with transcoding various videos on my Synology NAS. Some videos work, some do not.


ffmpeg command :


sudo /volume1/@appstore/VideoStation/bin/ffmpeg -y -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -i '/path/to/my/video/IMG_8647.MOV' -vf hwupload,scale_vaapi=w=640:h=-1:format=nv12 -c:v h264_vaapi -b:v 2M -movflags +faststart 'path/to/output4.mp4'



After i enter the command above, i get following error output :


ffmpeg version 3.3.7 Copyright (c) 2000-2019 the FFmpeg developers
 built with gcc 4.9.3 (crosstool-NG 1.20.0) 20150311 (prerelease)
 configuration: --prefix=/usr/pkg --incdir='${prefix}/include/ffmpeg' --arch=i686 --target-os=linux --cross-prefix=/usr/local/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu- --enable-cross-compile --enable-optimizations --enable-pic --enable-gpl --enable-version3 --enable-nonfree --enable-encoders --enable-pthreads --disable-muxer=image2 --disable-muxer=image2pipe --disable-swscale-alpha --disable-ffplay --disable-ffserver --disable-doc --disable-devices --disable-bzlib --disable-altivec --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libmp3lame --disable-decoder=amrnb --disable-encoder=zmbv --disable-encoder=dca --disable-decoder=dca --disable-encoder=ac3 --disable-encoder=ac3_fixed --disable-encoder=eac3 --disable-decoder=eac3 --disable-encoder=truehd --disable-decoder=truehd --extra-cflags=-I/usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/sys-root/usr/pkg/include --extra-ldflags=-L/usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/sys-root/usr/pkg/lib --cc=/usr/local/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-ccache-gcc --enable-shared --disable-static --enable-yasm --enable-libx264 --enable-vaapi --enable-encoder=h264_vaapi --enable-encoder=libx264
 libavutil 55. 58.100 / 55. 58.100
 libavcodec 57. 89.100 / 57. 89.100
 libavformat 57. 71.100 / 57. 71.100
 libavdevice 57. 6.100 / 57. 6.100
 libavfilter 6. 82.100 / 6. 82.100
 libswscale 4. 6.100 / 4. 6.100
 libswresample 2. 7.100 / 2. 7.100
 libpostproc 54. 5.100 / 54. 5.100
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /var/packages/VideoStation/target/lib/libva/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/volume1/homes/maisen20/Drive/iPhone Medien Neu/2020/06/Videos/2020-06-28_19-25-54_IMG_8647.MOV':
 Metadata:
 major_brand : qt 
 minor_version : 0
 compatible_brands: qt 
 creation_time : 2020-06-28T17:25:54.000000Z
 com.apple.quicktime.location.ISO6709: +47.1156+009.0640+430.715/
 com.apple.quicktime.make: Apple
 com.apple.quicktime.model: iPhone X
 com.apple.quicktime.software: 13.5.1
 com.apple.quicktime.creationdate: 2020-06-28T19:25:54+0200
 Duration: 00:00:25.10, start: 0.000000, bitrate: 50256 kb/s
 Stream #0:0(und): Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv, bt709), 3840x2160, 50115 kb/s, 60.01 fps, 60 tbr, 600 tbn, 600 tbc (default)
 Metadata:
 rotate : 90
 creation_time : 2020-06-28T17:25:54.000000Z
 handler_name : Core Media Data Handler
 encoder : HEVC
 Side data:
 displaymatrix: rotation of -90.00 degrees
 Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 98 kb/s (default)
 Metadata:
 creation_time : 2020-06-28T17:25:54.000000Z
 handler_name : Core Media Data Handler
 Stream #0:2(und): Data: none (mebx / 0x7862656D), 26 kb/s (default)
 Metadata:
 creation_time : 2020-06-28T17:25:54.000000Z
 handler_name : Core Media Data Handler
 Stream #0:3(und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
 Metadata:
 creation_time : 2020-06-28T17:25:54.000000Z
 handler_name : Core Media Data Handler
Stream mapping:
 Stream #0:0 -> #0:0 (hevc (native) -> h264 (h264_vaapi))
 Stream #0:1 -> #0:1 (aac (native) -> aac (native))
Press [q] to stop, [?] for help
Impossible to convert between the formats supported by the filter 'graph 0 input from stream 0:0' and the filter 'auto_scaler_0'
Error reinitializing filters!
Failed to inject frame into filter network: Function not implemented
Error while processing the decoded data for stream #0:0



Unfortunately I do not know that much about transcoding videos. Does anyone know what the problem here could be ?


Without hardware support (without -hwaccel_output_format vaapi) it works.


thanks a lot !


-
Splitting or segmenting a video with ffmpeg changes audio at the beginning
6 novembre 2020, par VSVI am using ffmpeg to split a video file to short bites :

ffmpeg i source.mp4 -codec copy -segment_time 5 -reset_timestamps 1 -force_key_frames "expr:gte(t,n_forced*5)" -f segment short%d.mp4


And by tonometer audio found that audio at the beginning starts like by fade in https://i.stack.imgur.com/Vj2KL.jpg


The same behavior when I use cut by ss, t, to parameters or remove -codec copy.


How can I remove this fade in or what is it behavior ?


Output


ffmpeg-2020-10-11-git-7ea4bcff7b-full_build\bin\ffmpeg -i C:\Projects\data\video7\in.mp4 -codec copy -segment_time 5 -reset_timestamps 1 -force_key_frames "expr:gte(t,n_forced*5)" -f segment C:\Projects\data\video7\out%d.mp4 -y
ffmpeg version 2020-10-11-git-7ea4bcff7b-full_build-www.gyan.dev Copyright (c) 2000-2020 the FFmpeg developers
 built with gcc 10.2.0 (Rev3, 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-libsnappy --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-frei0r --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-libglslang --enable-vulkan --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
 libavutil 56. 60.100 / 56. 60.100
 libavcodec 58.111.100 / 58.111.100
 libavformat 58. 62.100 / 58. 62.100
 libavdevice 58. 11.102 / 58. 11.102
 libavfilter 7. 87.100 / 7. 87.100
 libswscale 5. 8.100 / 5. 8.100
 libswresample 3. 8.100 / 3. 8.100
 libpostproc 55. 8.100 / 55. 8.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\Projects\data\video7\in.mp4':
 Metadata:
 major_brand : isom
 minor_version : 0
 compatible_brands: isom3gp4
 creation_time : 2020-10-26T15:17:18.000000Z
 Duration: 00:00:15.74, start: 0.000000, bitrate: 16816 kb/s
 Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x1080, 17029 kb/s, 29.96 fps, 30 tbr, 90k tbn, 180k tbc (default)
 Metadata:
 rotate : 90
 creation_time : 2020-10-26T15:17:18.000000Z
 handler_name : VideoHandle
 Side data:
 displaymatrix: rotation of -90.00 degrees
 Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 121 kb/s (default)
 Metadata:
 creation_time : 2020-10-26T15:17:18.000000Z
 handler_name : SoundHandle
[segment @ 000001e2ace958c0] Opening 'C:\Projects\data\video7\out0.mp4' for writing
Output #0, segment, to 'C:\Projects\data\video7\out%d.mp4':
 Metadata:
 major_brand : isom
 minor_version : 0
 compatible_brands: isom3gp4
 encoder : Lavf58.62.100
 Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x1080, q=2-31, 17029 kb/s, 29.96 fps, 30 tbr, 90k tbn, 90k tbc (default)
 Metadata:
 rotate : 90
 creation_time : 2020-10-26T15:17:18.000000Z
 handler_name : VideoHandle
 Side data:
 displaymatrix: rotation of -90.00 degrees
 Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 121 kb/s (default)
 Metadata:
 creation_time : 2020-10-26T15:17:18.000000Z
 handler_name : SoundHandle
Stream mapping:
 Stream #0:0 -> #0:0 (copy)
 Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help
[segment @ 000001e2ace958c0] Opening 'C:\Projects\data\video7\out1.mp4' for writing
[segment @ 000001e2ace958c0] Opening 'C:\Projects\data\video7\out2.mp4' for writing
[segment @ 000001e2ace958c0] Opening 'C:\Projects\data\video7\out3.mp4' for writing
frame= 463 fps=0.0 q=-1.0 Lsize=N/A time=00:00:15.72 bitrate=N/A speed= 301x
video:32077kB audio:233kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown