Recherche avancée

Médias (0)

Mot : - Tags -/formulaire

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (108)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 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 (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains 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 (17069)

  • Android App Bundle build error : File 'root/lib/x86/ffmpeg' uses directory name 'lib'

    7 septembre 2020, par Patel Pinkal

    I 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
 }


    


    enter image description here
enter image description here

    


  • Rendering video by ffmpeg.wasm in browser occured an error

    15 septembre 2022, par James Bor

    When a local video renderer uses the ffmpeg.wasm library in the Chrome browser, very often an error with the SBOX_FATAL_MEMORY_EXCEEDED code occurs during the rendering process. The standard command set is used. The code below is half fake because it is very long, but describes an approximate action algorithm. Computer performance and RAM capacity do not affect the video, files used - minimal size. Has anyone experienced this and how can we solve it ?
Error screen

    


    const videoGenerate = async (project) => {
  const ffmpeg = createFFmpeg({
      corePath: 'ffmpeg/ffmpeg-core.js',
      workerPath: 'ffmpeg/ffmpeg-core.worker.js'
  });
  await loadFfmpeg(ffmpeg);
  project.projectName = "Default";
  project.fileType = "video/mp4";

  const resultVideo = {
    title: `${project.projectName}ConcatenatedVideo.mp4`,
  };
  // *For fetchFile method and ffmpeg.FS('writeFile', title, file);
  await uploadObjects(project.projectName, ffmpeg);
  // *
  const command = ['-i', project.video, resultVideo.title];
  await ffmpeg.run(...command);
  await ffmpeg.FS("unlink", resultVideo.title);
  resultVideo["blob"] = ffmpeg.FS('readFile', title);
  return resultVideo.blob;
};


    


    These dependencies are used : "@ffmpeg/core" : " 0.8.5", "@ffmpeg/ffmpeg" : " 0.9.7". Upgrading the library to the latest version does not work either.

    


  • Create video vom rendered OpenGL frames

    10 mai 2012, par MrMuh

    i am searching for a way to create a video from a row of frames i have rendered with OpenGL and transfered to ram as int array using the glGetTexImage function. is it possible to achieve this directly in ram ( 10 secs video) or do i have to save each frame to the harddisk and encode the video afterwards ?

    i have found this sample http://cekirdek.pardus.org.tr/ ismail/ffmpeg-docs/api-example_8c-source.html in an other SO question but is this still the best way to do it ?