
Recherche avancée
Autres articles (55)
-
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 ;
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)
Sur d’autres sites (7499)
-
Streaming without Content-Length in response
29 août 2011, par kainI'm using Node.js, Express (and connect), and fluent-ffmpeg.
We want to stream audio files that are stored on Amazon S3 through http.
We have all working, except that we would like to add a feature, the on-the-fly conversion of the stream through ffmpeg.
This is working well, the problem is that some browsers checks in advance before actually getting the file.
Incoming requests containing the Range header, for which we reply with a 206 with all the info from S3, have a fundamental problem : we need to know in advance the content-length of the file.
We don't know that since it is going through ffmpeg.
One solution might be to write out the resulting content-length directly on S3 when storing the file (in a special header), but this means we have to go through the pain of having queues to encode after upload just to know the size for future requests.
It also means that if we change compressor or preset we have to go through all this over again, so it is not a viable solution.We also noticed big differencies in the way Chrome and Safari request the audio tag src, but this may be discussion for another topic.
Fact is that without a proper content-length header in response everything seems to break or browsers goes in an infinite loop or restart the stream at pleasure.
Ideas ?
-
Android App Bundle build error : File 'root/lib/x86/ffmpeg' uses directory name 'lib'
7 septembre 2020, par Patel PinkalI have used FFmpeg Android in the project from this repo FFmpeg-Android-Java and implement only the FFmpegAndroid module in the project.


FFmpeg library is working fine when we run directly from Android Studio or we make APK file (debug or Signed).


But When I try to generate the app bundle from Android studio I get the below error.


Execution failed for task ':app:packageReleaseBundle'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
 > File 'root/lib/x86/ffmpeg' uses reserved file or directory name 'lib'.





Project Level build.gradle




// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {

// Different version declaration
ext {
 kotlin_version = '1.4.0'
 supportVersion = "28.0.0"
 retrofitVersion = "2.0.2"
 okhttp3Version = "3.2.0"
 smackVersion = "4.3.0"
 nav_version = "2.1.0-alpha02"
}

repositories {
 google()
 jcenter()
 maven { url "https://jitpack.io" }
 maven { url 'https://maven.fabric.io/public' }
 mavenCentral()
}
dependencies {
 classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
 classpath 'com.google.gms:google-services:4.3.3'
 classpath 'com.android.tools.build:gradle:4.0.1'
 classpath 'io.fabric.tools:gradle:1.28.1'
 classpath 'me.tatarka:gradle-retrolambda:3.3.1'
 classpath 'com.jakewharton:butterknife-gradle-plugin:9.0.0-rc2'
 classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.7.3'
 classpath "com.github.dcendents:android-maven-gradle-plugin:2.0"
 classpath 'com.google.firebase:perf-plugin:1.3.1'
}
}

 allprojects {
 repositories {
 google()
 jcenter()
 maven { url "https://jitpack.io" }
 maven { url 'https://maven.fabric.io/public' }
 mavenCentral()
 }
 }

 task clean(type: Delete) {
 delete rootProject.buildDir
 }





-
What does "probe_score" means from ffprobe output ?
13 août 2014, par DrakeGiven a media file, after running
ffprobe -i input.mp4 -show_format -print_format json
, I got something like this :{
"format": {
"filename": "ooxx.mp4",
"nb_streams": 2,
"nb_programs": 0,
"format_name": "mov,mp4,m4a,3gp,3g2,mj2",
"format_long_name": "QuickTime / MOV",
"start_time": "0.000000",
"duration": "231.210000",
"size": "65133325",
"bit_rate": "2253650",
"probe_score": 100,
"tags": {
"major_brand": "isom",
"minor_version": "512",
"compatible_brands": "isomiso2avc1mp41",
"encoder": "Lavf55.33.100",
}
}
}I’m wondering what does probe_score mean here ? How does it get calculated ?