Recherche avancée
Médias (3)
-
GetID3 - Bloc informations de fichiers
9 avril 2013, par
Mis à jour : Mai 2013
Langue : français
Type : Image
-
GetID3 - Boutons supplémentaires
9 avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
-
Collections - Formulaire de création rapide
19 février 2013, par
Mis à jour : Février 2013
Langue : français
Type : Image
Autres articles (97)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs
Sur d’autres sites (9494)
-
Cannot enable GD support for ffmpeg-php extension
26 avril 2015, par user3529796This is from
phpinfo()ffmpeg
ffmpeg-php version 0.6.0-svn
ffmpeg-php built on Apr 25 2015 20:01:27
ffmpeg-php gd support disabled
ffmpeg libavcodec version Lavc52.72.2
ffmpeg libavformat version Lavf52.64.2
ffmpeg swscaler version SwS0.11.0
Directive Local Value Master Value
ffmpeg.allow_persistent 0 0
ffmpeg.show_warnings 0 0
gd
GD Support enabled
GD Version bundled (2.1.0 compatible)
FreeType Support enabled
FreeType Linkage with freetype
FreeType Version 2.3.11
GIF Read Support enabled
GIF Create Support enabled
JPEG Support enabled
libJPEG Version 6b
PNG Support enabled
libPNG Version 1.2.49
WBMP Support enabled
XPM Support enabled
libXpm Version 30411
XBM Support enabled
Directive Local Value Master Value
gd.jpeg_ignore_warning 0 0I just need to enable gd support for ffmpeg. I’ve tried using
./configure --enable-skip-gd-checkand nothing has worked. I’ve scoured google for the last 12 hours and tried every "solution" so any advice is appreciated. Thanks.Terminal output after
./configure --enable-skip-gd-check:root@ip-111-111-111-11 [/usr/local/src/ffmpeg-php-0.6.0]# ./configure --enable-skip-gd-check
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for a sed that does not truncate output... /bin/sed
checking for cc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking how to run the C preprocessor... cc -E
checking for icc... no
checking for suncc... no
checking whether cc understands -c and -o together... yes
checking for system library directory... lib
checking if compiler supports -R... no
checking if compiler supports -Wl,-rpath,... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for PHP prefix... /usr/local
checking for PHP includes... -I/usr/local/include/php
I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib
checking for PHP extension directory... /usr/local/lib/php/extensions/no-debug-non-zts-20121212
checking for PHP installed headers prefix... /usr/local/include/php
checking if debug is enabled... no
checking if zts is enabled... no
checking for re2c... no
configure: WARNING: You will need re2c 0.13.4 or later if you want to regenerate PHP parsers.
checking for gawk... gawk
checking for ffmpeg support... yes, shared
checking whether to force gd support in ffmpeg-php... yes
checking for ffmpeg headers... ...found in /usr/include/libavcodec
checking for ffmpeg libavcodec.so... ...found in /usr/lib64
checking for ffmpeg swscale support... yes
checking for ld used by cc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 1966080
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if cc supports -fno-rtti -fno-exceptions... no
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking whether the cc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
creating libtool
appending configuration tag "CXX" to libtool
configure: creating ./config.status
config.status: creating config.h -
Flutter Android release crash with ffmpeg_kit_flutter_new : Bad JNI version returned from JNI_OnLoad in libffmpegkit_abidetect.so (debug works) [closed]
20 août, par Muhammad Rakha AlmasahProblem
My Flutter app crashes only in release when the FFmpegKit plugin is registered. The app runs fine in debug on the same devices. The crash happens before my UI shows up, during plugin registration.


Error (release logcat)


On Samsung SM-A105G (Android 11, API 30, 32-bit device) :


E/AndroidRuntime: FATAL EXCEPTION: main
java.lang.Error: FFmpegKit failed to start on brand: samsung, model: SM-A105G, device: a10, api level: 30,
abis: armeabi-v7a armeabi, 32bit abis: armeabi-v7a armeabi, 64bit abis: .
 at com.antonkarpenko.ffmpegkit.AbiDetect.<clinit>(SourceFile:3)
 at com.antonkarpenko.ffmpegkit.FFmpegKitConfig.<clinit>(SourceFile:16)
 ...
Caused by: java.lang.UnsatisfiedLinkError: Bad JNI version returned from JNI_OnLoad in
"/data/app/.../lib/arm/libffmpegkit_abidetect.so": 0
 at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
 at java.lang.System.loadLibrary(System.java:1664)

</clinit></clinit>

On Redmi 24094RAD4G (Android 15/35, 64-bit) :


java.lang.Error: FFmpegKit failed to start on brand: Redmi, model: 24094RAD4G, device: citrine, api level: 35,
abis: arm64-v8a armeabi-v7a armeabi, 32bit abis: armeabi-v7a armeabi, 64bit abis: arm64-v8a.
...
Caused by: java.lang.UnsatisfiedLinkError: Bad JNI version returned from JNI_OnLoad in
"/data/app/.../split_config.arm64_v8a.apk!/lib/arm64-v8a/libffmpegkit_abidetect.so": 0



What’s strange
In debug the plugin loads and prints :


I/ffmpeg-kit: Loaded ffmpeg-kit-full-gpl-arm-v7a-neon-6.0-20250810.


and the app works normally.


Environment


Flutter (stable), Android


compileSdk = 35, minSdk = 24, targetSdk = 35


NDK I tried :


26.1.10909125 (recommended by many plugins)


25.2.9519653


Devices that crash in release :


Samsung SM-A105G (32-bit only, API 30)


Redmi 24094RAD4G (arm64-v8a capable, API 35)


Dependencies (relevant)


I mainly need FFmpeg through a video editor workflow.


Tried these FFmpeg packages :


ffmpeg_kit_flutter_new 3.2.0 → release crash


ffmpeg_kit_flutter_new 1.6.1 → release crash


(for testing) the discontinued ffmpeg_kit_flutter 6.0.3 → gradle couldn’t resolve com.arthenica:ffmpeg-kit-https:6.0-2 in release


Other media deps : video_editor (git), video_thumbnail (git), video_player, etc


App config
android/app/build.gradle


plugins {
 id "com.android.application"
 id "kotlin-android"
 id "dev.flutter.flutter-gradle-plugin"
}

def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
 localPropertiesFile.withReader('UTF-8') { reader ->
 localProperties.load(reader)
 }
}

def keystoreProperties = new Properties()
def keystorePropertiesFile = rootProject.file('key.properties')
if (keystorePropertiesFile.exists()) {
 keystoreProperties.load(new FileInputStream(keystorePropertiesFile))
}


def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
 flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
 flutterVersionName = '1.0'
}

android {
 namespace "id.fitacademy.app"
 compileSdk = 35
 ndkVersion = "26.1.10909125"

 compileOptions {
 sourceCompatibility JavaVersion.VERSION_1_8
 targetCompatibility JavaVersion.VERSION_1_8
 }

 kotlinOptions {
 jvmTarget = JavaVersion.VERSION_1_8
 }

 sourceSets {
 main.java.srcDirs += 'src/main/kotlin'
 }

 defaultConfig {
 applicationId "id.fitacademy.app"
 minSdkVersion 24
 targetSdkVersion 35
 versionCode flutterVersionCode.toInteger()
 versionName flutterVersionName
 multiDexEnabled true
 ndk { abiFilters "armeabi-v7a" }
 }

 packagingOptions {
 jniLibs { useLegacyPackaging true } // muat .so via ekstraksi
 // pickFirsts += ['**/libc++_shared.so'] // aktifkan hanya kalau ada konflik duplikat
 }

 signingConfigs {
 release {
 keyAlias keystoreProperties['keyAlias']
 keyPassword keystoreProperties['keyPassword']
 storeFile keystoreProperties['storeFile'] ? file(keystoreProperties['storeFile']) : null
 storePassword keystoreProperties['storePassword']
 }
 debug {
 keyAlias keystoreProperties['keyAlias']
 keyPassword keystoreProperties['keyPassword']
 storeFile keystoreProperties['storeFile'] ? file(keystoreProperties['storeFile']) : null
 storePassword keystoreProperties['storePassword']
 }
 }
 buildTypes {
 release {
 signingConfig signingConfigs.release
 }
 debug {
 signingConfig signingConfigs.debug
 }
 }
}

flutter {
 source '../..'
}



AndroidManifest.xml


<manifest>

 
 
 
 
 
 
 
 
 
 
 

 <queries>
 <package></package>
 <package></package>
 <package></package>
 <package></package>
 <package></package>
 <package></package>
 <package></package>

 <provider></provider> 
 <provider></provider> 

 <intent>
 <action></action>
 <data></data>
 </intent>
 </queries>

 
 
 
 
 
 <action></action>
 <category></category>
 

 
 
 
 <action></action>
 <category></category>
 <category></category>
 <data></data>
 <data></data>
 <data></data>
 <data></data>
 
 

 
 


 
 

 <provider>
 
 </provider>

 
 
 
</manifest>


APK / AAB inspection


jar tf app-release.apk | findstr ffmpegkit_abidetect shows the library is packaged, e.g. :


lib/arm/libffmpegkit_abidetect.so (on 32-bit build)


lib/arm64-v8a/libffmpegkit_abidetect.so (on 64-bit)


So the .so is present in the release artifact.


What I tried


Switch NDK 25.2 ↔ 26.1 and align with plugins.


Add android:extractNativeLibs="true" in the manifest.


packagingOptions jniLibs useLegacyPackaging true .


Build both APK and AAB, and also flutter run —release -d .


With and without abiFilters.


Full flutter clean, delete Gradle caches, rebuild.


Verified .env files and other assets are included (unrelated but checked).


The crash always happens at plugin startup in release with :
Bad JNI version returned from JNI_OnLoad in ... libffmpegkit_abidetect.so : 0.


-
Evolution #3432 (Nouveau) : Mise à jour automatique de SPIP avec notification admin
29 avril 2015, par Gilles VINCENTWordpress propose ce type de fonctionnalité.
Est-ce que cela ne pourrait pas être repris dans SPIP ?.Gilles
---------- Forwarded message ----------
From : WordPress <wordpress@xxx>
Date : 2015-04-27 21:10 GMT+02:00
Subject : [Prise de notes] Votre site a été mis à jour vers WordPress 4.1.4
To : gilles.vincent@gmail.comSalutations ! Votre site à l’adresse http://xxx a été automatiquement mis à jour vers WordPress 4.1.4.
Pour en savoir plus sur la version 4.1.4, lisez l’écran À Propos de WordPress :
http://xxx/wp-admin/about.phpWordPress 4.2.1 est disponible. La mise à jour est facile et ne requiert que quelques secondes :
http://xxx/wp-admin/update-core.phpSi vous rencontrez des problèmes ou avez besoin d’assistance, les volontaires du forum d’entraide de WordPress-fr.net devraient pouvoir vous aider.
http://www.wordpress-fr.net/supportPour des questions de sécurité, il est important de garder votre site à jour. Par ailleurs, cela rend le Web plus sûr pour vous et vos lecteurs.
L’équipe WordPress
Syndiquer tout le site
