Recherche avancée

Médias (1)

Mot : - Tags -/biomaping

Autres articles (88)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications 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, 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 ;

  • Ecrire une actualité

    21 juin 2013, par

    Pré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 (12054)

  • couldn't find "liblicense-jni.so lib using Android Studio

    15 novembre 2016, par Virani Ashish

    i have crated gif maker app using ffmpeg lib

    but zenfone 5 (asus t00j) not couldn’t find "liblicense-jni.so in app lib folder and other devicecan load lib perfect.

    if any one can idea to solve this error ?

    11-15 10:15:28.947 15471-15471/com.aspiration.gifmaker E/AndroidRuntime: FATAL EXCEPTION: main
        Process: com.aspiration.gifmaker, PID: 15471
        java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.aspiration.gifmaker-1/base.apk"],nativeLibraryDirectories=[/data/app/com.aspiration.gifmaker-1/lib/x86, /vendor/lib, /system/lib]]] couldn't find "liblicense-jni.so"
            at java.lang.Runtime.loadLibrary(Runtime.java:366)
            at java.lang.System.loadLibrary(System.java:989)
            at com.netcompss.ffmpeg4android.LicenseCheckJNI.<clinit>(LicenseCheckJNI.java:42)
            at com.netcompss.ffmpeg4android.GeneralUtils.isLicenseValid(GeneralUtils.java:509)
            at com.aspiration.gifmaker.activity.VideoSpeedActivity.onCreate(VideoSpeedActivity.java:210)
            at android.app.Activity.performCreate(Activity.java:5975)
            at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1105)
            at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2269)
            at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2376)
            at android.app.ActivityThread.access$800(ActivityThread.java:147)
            at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1281)
            at android.os.Handler.dispatchMessage(Handler.java:102)
            at android.os.Looper.loop(Looper.java:135)
            at android.app.ActivityThread.main(ActivityThread.java:5253)
            at java.lang.reflect.Method.invoke(Native Method)
            at java.lang.reflect.Method.invoke(Method.java:372)
            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:899)
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:694)
    </clinit>
  • Audio merging using ffmpeg : Error decoding a SILK frame

    29 janvier 2018, par arjuncc

    I am using following command to merge two audio files with ffmpeg. On the output file one of the audio is not audible. When these audios are taken separately both files are audible(mka file).

    ffmpeg  -i file1.mka -i file2.mka -filter_complex "[1]adelay=12509.000000|12509.000000[d];[0][d]amix=inputs=2" -strict
    -2 output_audio.webm

    I am getting following error in log

    [opus @ 000000fba65e22c0] Error decoding a SILK frame.
    [opus @ 000000fba65e22c0] Error decoding an Opus frame.
    [opus @ 000000fba65e22c0] LBRR frames is not implemented. Update your FFmpeg ver
    sion to the newest one from Git. If the problem still occurs, it means that your
    file has a feature which has not been implemented.

    I have had a hint form this and this link but It was also not helpful.

    Finally I converted file ’file2.mka’ into mp3 and merged with the first file, at that time audio is clear, also the synching is perfect. So I suppose data is not lost, It should be an issue with codec. Can anyone help ?
    I have also tried below command but no luck

    ffmpeg  -i file1.mka -i file2.mka -filter_complex "[1]adelay=12509.000000|12509.000000[d];[0][d]amix=inputs=2" -map 0:0 -c:a libopus -map 1:0  -strict -2 output_audio.webm

    Full implementation is given in this link

  • GoPro (MP4) video timestamp sync with precision of milliseconds

    3 février 2021, par Raphael Ottoni

    I need your help with a data sync problem... I m currently trying to sync my GoPro video with real world time (a.k.a my notebook). I manage to sync date and time of my notebook and my GoPro 3+ black perfectly. The problem is that when the GoPro save the files in disk it round up the milliseconds on the creation_time (the milliseconds is always 000000) . Thus, turning the perfect sync impossible. In attachment is a picture of the meta information (extracted by ffprobe) of the MP4 video.

    &#xA;&#xA;

    My question is : What I have to do, so the GoPro actually save the creation_time with precision of milliseconds ?

    &#xA;&#xA;

    Another small question : Looking at the attachment figure, we see the "timecode" which is a time synchronization data in the format of hours:minuts:seconds:frame. I was thinking that I could use the "frame" value to calculate the missing milliseconds value. If we take this attachment, as a example, we can see that the frame value is "36". Meaning that the millisecond that it started to record was the one associated with the 36th frame of the FPS (in this video : 60fps) value : Some thing like 1000/60 * 36 which is 600 milliseconds, thus the actual creation_time of this video would be : 2017-07-19T18:10:34.600

    &#xA;&#xA;

    Is this logic right ? it didn't work ! I don't know what else to do.

    &#xA;&#xA;

    P.S : I need this kind of time precision because I will sync the video frames with a external sensor data that is recorded at 11hz.

    &#xA;&#xA;

    Please Help

    &#xA;&#xA;

    enter image description here

    &#xA;&#xA;

    update

    &#xA;&#xA;

    I forgot to mention, even if you check the original raw file information, inside the GoPro SSD card, using "stats" to read the creation time (see attachment) it still has the same timestamp without milliseconds.

    &#xA;&#xA;

    enter image description here

    &#xA;