
Recherche avancée
Autres articles (47)
-
Qualité du média après traitement
21 juin 2013, parLe bon réglage du logiciel qui traite les média est important pour un équilibre entre les partis ( bande passante de l’hébergeur, qualité du média pour le rédacteur et le visiteur, accessibilité pour le visiteur ). Comment régler la qualité de son média ?
Plus la qualité du média est importante, plus la bande passante sera utilisée. Le visiteur avec une connexion internet à petit débit devra attendre plus longtemps. Inversement plus, la qualité du média est pauvre et donc le média devient dégradé voire (...) -
Mise à jour de la version 0.1 vers 0.2
24 juin 2013, parExplications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...) -
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
Sur d’autres sites (8562)
-
Offline tracking in Matomo JavaScript Tracker – We need your feedback
16 octobre 2020, par Matomo Core Team — Development, UncategorizedAs part of our Matomo 4 release we are working on adding support for offline tracking using service workers (SW) and IndexedDB. An early version of this new feature is now available as part of our latest Matomo 4 beta and we now need your feedback to fix any outstanding issues.
How does it work behind the scenes ?
- The service worker caches the Matomo JavaScript tracker so if a user becomes offline on subsequent requests the JS tracker will be still loaded.
- If a user is offline, any tracking request will be put into the local IndexedDB.
- Once the user becomes online, all requests from the IndexedDB will be retried.
How do I integrate offline tracking into my website or app ?
Follow the steps in our FAQ on how to set up offline tracking.
We need your feedback
We’d love to hear your feedback if this new feature is working for you or not. Simply leave a comment on the offline tracking issue and let us know if it worked for you, if something didn’t work, whether you miss any options or any other kind of feedback.
Are you a service worker or IndexedDB pro ? We’d love if you could help us review our implementation. You can check out the code in the offline tracking pull request. We appreciate any feedback to help us improve this feature !
Thank you for your help !
-
How to make mpv more compatible with ffmpeg filters like minterpolate ?
1er octobre 2020, par F usedEmacs -con fusedffmpeg filter minterpolate (motion interpolation) does not work in MPV.



(Nevertheless the file then is played normally without the minterpolate).



(I researched using search engines and throughout documentation and troubleshooted to make a use of opengl and generally tried everything apart from asking for help and learning to understand more in the source code and I'm not a programmer)…



--gpu-context=angle --gpu-api=opengl
also does not make opengl work. (I'm guessing opengl could help from seeing its use in the documentations).




Note

 

To get a full list of available video filters, see —vf=help and
 http://ffmpeg.org/ffmpeg-filters.html .

 

Also, keep in mind that most actual filters are available via the
 lavfi wrapper, which gives you access to most of libavfilter's
 filters. This includes all filters that have been ported from MPlayer
 to libavfilter.

 

Most builtin filters are deprecated in some ways, unless they're only
 available in mpv (such as filters which deal with mpv specifics, or
 which are implemented in mpv only).

 

If a filter is not builtin, the lavfi-bridge will be automatically
 tried. This bridge does not support help output, and does not verify
 parameters before the filter is actually used. Although the mpv syntax
 is rather similar to libavfilter's, it's not the same. (Which means
 not everything accepted by vf_lavfi's graph option will be accepted by
 —vf.)

 

You can also prefix the filter name with lavfi- to force the wrapper.
 This is helpful if the filter name collides with a deprecated mpv
 builtin filter. For example —vf=lavfi-scale=args would use
 libavfilter's scale filter over mpv's deprecated builtin one.





I expect MPV to play with minterpolate (one of several filters that MPV can use, listed in http://ffmpeg.org/ffmpeg-filters.html) enabled. But this is what happens :



Input :
"--vf=lavfi=[minterpolate=fps=60000/1001:mi_mode=mci]"



Output :



cplayer: (+) Video --vid=1 (*) (h264 1280x720 29.970fps)
 cplayer: (+) Audio --aid=1 (*) (aac 2ch 44100Hz)
 vd: Using hardware decoding (d3d11va).
 ffmpeg: Impossible to convert between the formats supported by the filter 'mpv_src_in0' and the filter 'auto_scaler_0'
 lavfi: failed to configure the filter graph
 vf: Disabling filter lavfi.00 because it has failed.




(Interesting is also that
--gpu-api=opengl
does not work (despite that according to specification my—not to brag—HD Graphics 400 Braswell supports its 4.2 version)… And thataresample
seems to have no effect too, and with the few audio filters selected playback often doesn't start nor output errors.)

-
Automator bash shell script trouble
6 avril 2015, par DaeI’m probably missing something really simple here, but I’m have trouble building an automator service that runs a bash shell script. All of the elements of the script work fine when plugged into shell, but for some reason the automator service is failing to run. The script calls ffmpeg to convert an audio file passed to it from the finder :
for f in "$@"
do
fn="${f%%.*}"
~/Applications/ffmpeg/ffmpeg -i "$f" -acodec libmp3lame -q:a 7 -ar 8000 -ac 1 "$fn.mp3"
doneThe script runs fine without the ffmpeg command, and the ffmpeg command runs fine in the terminal on its own. Where’s the error coming from ?
Thanks !