
Recherche avancée
Autres articles (61)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Possibilité de déploiement en ferme
12 avril 2011, parMediaSPIP peut être installé comme une ferme, avec un seul "noyau" hébergé sur un serveur dédié et utilisé par une multitude de sites différents.
Cela permet, par exemple : de pouvoir partager les frais de mise en œuvre entre plusieurs projets / individus ; de pouvoir déployer rapidement une multitude de sites uniques ; d’éviter d’avoir à mettre l’ensemble des créations dans un fourre-tout numérique comme c’est le cas pour les grandes plate-formes tout public disséminées sur le (...) -
Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs
12 avril 2011, parLa manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.
Sur d’autres sites (11751)
-
Flutter : How to use flutter_ffmpeg to add overlays like watermarks and texts to a video ?
29 septembre 2022, par Ryan WangI try to implement the
video_editing
feature to my app, and I'd tried the Tapioca Package and the Video_Manipulation package but found that they both do not meet my criteria, so I put my last hope on the flutter_ffmpeg package.

But as I read through its official doc on pub.dev, not a thing on my mind but "WHAT THE HECK", I can't understand what those commands are used for, and though I can't find anything related to add widget overlays to a video. And almost no tutorial on the web that explains how to use it.


So if you successfully implemented adding watermarks/texts to a video with the ffmpeg package, please show me how. Thanks !


-
aacenc : implement Intensity Stereo encoding support
2 juillet 2015, par Rostislav Pehlivanovaacenc : implement Intensity Stereo encoding support
This commit implements intensity stereo coding support
to the native aac encoder. This is a way to increase the efficiency
of the encoder by zeroing the right channel’s spectral coefficients
(in a channel pair) and rederiving them in the decoder using information
from the scalefactor indices of special band types. This commit
confomrs to the official ISO 13818-7 specifications, although due to
their ambiguity certain deviations have been taken to ensure maximum
sound quality. This commit has been extensively tested and has shown
to not result in audiable audio artifacts unless in extreme cases.
This commit also adds an option, aac_is, which has the value of
0 by default. Intensity Stereo is part of the scalable aac profile
and is thus non-default.The way IS coding works is that it rederives the right channel’s
spectral coefficients from the left channel via the scalefactor
index values left in the right channel. Since an entire band’s
spectral coefficients do not need to be coded, the encoder’s
efficiency jumps up and it unzeroes some high frequency values
which it previously did not have enough bits to encode. That way
less information is lost than the information lost by rederiving
the spectral coefficients with some error. This is why the
filesize of files encoded with IS do not decrease significantly.
Users wishing that IS coding should reduce filesize are expected
to reduce their encoding bitrates appropriately.This is V2 of the commit. The old version did not mark ms_mask as
0 since M/S and IS coding are incompactible, which resulted in
distortions with M/S coding enabled. This version also improves
phase detection by measuring it for every spectral coefficient in
the band and using a simple majority rule to determine whether the
coefficients are in or out of phase. Also, the energy values per
spectral coefficient were changed as to reflect the
official specifications.Reviewed-by : Claudio Freire <klaussfreire@gmail.com>
Signed-off-by : Michael Niedermayer <michaelni@gmx.at> -
Convert video to HLS in iOS app without triggering GPL (FFmpegKit alternative ?) [closed]
7 juillet, par Aziz BibitovI'm building an iOS app in Swift that needs to convert local video files to HLS format (
.m3u8
). Initially, I used theffmpeg-kit-ios-full-gpl
package from FFmpegKit, which works well. However, since this build includes GPL-licensed components (such aslibx264
), I'm concerned that using it would require my app to be released under the GPL, which is not compatible with App Store distribution.

That said, my needs are fairly basic : I only need to convert H.264
.mp4
video files into HLS format.

My Questions :


- 

- Is there a safe way to use FFmpegKit—such as the
full-libarary-lgpl
variant—that guarantees no GPL components are used for this task ? - Are there any iOS-native or third-party tools that can reliably convert H.264
.mp4
video files to HLS on-device without introducing GPL concerns ? - Is using Apple’s
AVAssetExportSession
a viable alternative for exporting to HLS ? I haven't found much official documentation about using it for HLS output.








Any guidance on how to perform HLS conversion in an App Store–safe (non-GPL) way would be much appreciated.


- Is there a safe way to use FFmpegKit—such as the