
Recherche avancée
Autres articles (53)
-
Installation en mode standalone
4 février 2011, parL’installation de la distribution MediaSPIP se fait en plusieurs étapes : la récupération des fichiers nécessaires. À ce moment là deux méthodes sont possibles : en installant l’archive ZIP contenant l’ensemble de la distribution ; via SVN en récupérant les sources de chaque modules séparément ; la préconfiguration ; l’installation définitive ;
[mediaspip_zip]Installation de l’archive ZIP de MediaSPIP
Ce mode d’installation est la méthode la plus simple afin d’installer l’ensemble de la distribution (...) -
MediaSPIP en mode privé (Intranet)
17 septembre 2013, parÀ partir de la version 0.3, un canal de MediaSPIP peut devenir privé, bloqué à toute personne non identifiée grâce au plugin "Intranet/extranet".
Le plugin Intranet/extranet, lorsqu’il est activé, permet de bloquer l’accès au canal à tout visiteur non identifié, l’empêchant d’accéder au contenu en le redirigeant systématiquement vers le formulaire d’identification.
Ce système peut être particulièrement utile pour certaines utilisations comme : Atelier de travail avec des enfants dont le contenu ne doit pas (...) -
Contribute to documentation
13 avril 2011Documentation is vital to the development of improved technical capabilities.
MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
To contribute, register to the project users’ mailing (...)
Sur d’autres sites (7620)
-
cbs_av1 : Don't reject unknown metadata
24 janvier 2023, par Mark Thompsoncbs_av1 : Don't reject unknown metadata
Accept it and pass it through unchanged.
The standard requires that decoders ignore unknown metadata, and indeed
this is tested by some of the Argon coverage streams. -
Unknown encoder 'libx264' in flutter android app
17 juillet 2023, par ololoI am trying to use libx264 via ffmpeg_kit_flutter with full-gpl options in my Flutter app. However, when I start the app on Android, I keep getting the error :


"Unknown encoder 'libx264'."


Here is my current setup :


In android/build.gradle file :


buildscript {
 ext {
 ffmpegKitPackage = "full-gpl" // Notice I specified the option here
 kotlin_version = '1.8.0'
 }

 repositories {
 google()
 mavenCentral()
 }
 // .....
}



In android/app/build.gradle file :


android {
 compileSdkVersion 33

 compileOptions {
 sourceCompatibility JavaVersion.VERSION_1_8
 targetCompatibility JavaVersion.VERSION_1_8
 }

 packagingOptions { 
 // I specified the libx264 in this packageOptions block
 pickFirst 'lib/x86_64/libx264.so'
 pickFirst 'lib/arm64-v8a/libx264.so'
 pickFirst 'lib/armeabi-v7a/libx264.so'
 pickFirst 'lib/x86/libx264.so'
 }
}



In pubspec.yaml file :


dependencies:
 ffmpeg_kit_flutter: ^5.1.0



What could be the issue causing the "Unknown encoder 'libx264'" error ? Any help would be appreciated. Thank you !


-
Possible issue / unknown "feature" of ffmpeg ? [closed]
23 septembre 2023, par Grumpy OldManI'm using ffmpeg to split up a MP4 file into shorter (about 5 seconds) files, each of which I will then later add hard-coded captions to.


ffmpeg -i master.mp4 -ss 00:00:00 -t 00:00:05 -c:v copy -c:a copy x-01.mp4



It seems that if there is SRT file with the same base name as the output file (i.e. 'x-01.srt' in the above example), captions will be added to it. This is not what I was wanting. My workflow is to add it at a later stage. Is this an intended feature of the software or did I accidentally discover some sort of unintended side effect ?


I've tried searching the web, but can't find any mention of the "feature". If I change the ffmpeg command to use an output file name that does not have an associated ".srt" file with the same name, it works as expected.