Recherche avancée

Médias (91)

Autres articles (79)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

Sur d’autres sites (7006)

  • lavu/vulkan : remove unused field from the execution pool structure

    19 juillet 2023, par Lynne
    lavu/vulkan : remove unused field from the execution pool structure
    
    • [DH] libavutil/vulkan.h
  • ac3enc_template : Use the correct context field

    24 juillet 2015, par Vittorio Giovara
    ac3enc_template : Use the correct context field
    

    For audio encoders, delay has no effect, use the appropriate one,
    initial_padding (see 2df0c32).

    • [DBH] libavcodec/ac3enc_template.c
  • What's the purpose of the END field in files containing metadata for ffmpeg ?

    15 juillet 2023, par rdrg109

    Table of contents

    


      

    • The context
    • 


    • Minimal working example

        

      • no. 1
      • 


      • no. 2
      • 


      • no. 3
      • 


      


    • 


    • The questions
    • 


    


    


    The context

    


    I'm aware that it is possible to insert metadata of chapters into a video using ffmpeg (link to documentation). Minimal working example no. 1 shows this point.

    


    When I insert chapters that are not consecutive, ffmpeg doesn't use the end time that is specified in the metadata file through the END field. "Minimal working example no. 2" shows this point. In "Minimal working example no. 3", the END field of all chapters is 1 millisecond, yet we get the same result of Minimal working example no. 2. What is worth noting is that the END of the last chapter is the only one that is added correctly.

    


    


    Minimal working example

    


    


    no. 1

    


    Consider the following ffmpeg metadata file. It creates chapters in the following time ranges

    


      

    • From 0 to millisecond 9999, the chapter is This is my chapter one
    • 


    • From 10000 to millisecond 19999, the chapter is This is my chapter two
    • 


    • From 20000 to millisecond 29999, the chapter is This is my chapter three
    • 


    • From 30000 to millisecond 39999, the chapter is This is my chapter four
    • 


    


    ;FFMETADATA1
title=The title of my video

[CHAPTER]
TIMEBASE=1/1000
START=0
END=10000
title=This is my chapter one

[CHAPTER]
TIMEBASE=1/1000
START=10000
END=20000
title=This is my chapter two

[CHAPTER]
TIMEBASE=1/1000
START=20000
END=30000
title=This is my chapter three


    


    The following command creates a simple video and inserts the metadata shown above into that video.

    


    ffmpeg -v error -y -f lavfi -i 'testsrc=d=120:size=100x100' -i metadata.txt -map_metadata 1 output.mp4


    


    The following command shows information about the metadata in the video file that was created by the previous command.

    


    ffprobe -v error -show_chapters -print_format json output.mp4 | jq


    


    {
  "chapters": [
    {
      "id": 0,
      "time_base": "1/1000",
      "start": 0,
      "start_time": "0.000000",
      "end": 10000,
      "end_time": "10.000000",
      "tags": {
        "title": "This is my chapter one"
      }
    },
    {
      "id": 1,
      "time_base": "1/1000",
      "start": 10000,
      "start_time": "10.000000",
      "end": 20000,
      "end_time": "20.000000",
      "tags": {
        "title": "This is my chapter two"
      }
    },
    {
      "id": 2,
      "time_base": "1/1000",
      "start": 20000,
      "start_time": "20.000000",
      "end": 30000,
      "end_time": "30.000000",
      "tags": {
        "title": "This is my chapter three"
      }
    }
  ]
}


    


    No problem until here.

    


    


    no. 2

    


    ;FFMETADATA1
title=The title of my video

[CHAPTER]
TIMEBASE=1/1000
START=0
END=5000
title=This is my chapter one

[CHAPTER]
TIMEBASE=1/1000
START=10000
END=15000
title=This is my chapter two

[CHAPTER]
TIMEBASE=1/1000
START=20000
END=25000
title=This is my chapter three


    


    The following command creates a simple video and inserts the metadata shown above into that video.

    


    ffmpeg -v error -y -f lavfi -i 'testsrc=d=120:size=100x100' -i metadata.txt -map_metadata 1 output.mp4


    


    The following command shows information about the metadata in the video file that was created by the previous command.

    


    ffprobe -v error -show_chapters -print_format json output.mp4 | jq


    


    {
  "chapters": [
    {
      "id": 0,
      "time_base": "1/1000",
      "start": 0,
      "start_time": "0.000000",
      "end": 10000,
      "end_time": "10.000000",
      "tags": {
        "title": "This is my chapter one"
      }
    },
    {
      "id": 1,
      "time_base": "1/1000",
      "start": 10000,
      "start_time": "10.000000",
      "end": 20000,
      "end_time": "20.000000",
      "tags": {
        "title": "This is my chapter two"
      }
    },
    {
      "id": 2,
      "time_base": "1/1000",
      "start": 20000,
      "start_time": "20.000000",
      "end": 25000,
      "end_time": "25.000000",
      "tags": {
        "title": "This is my chapter three"
      }
    }
  ]
}


    


    From the output above, we can notice the following :

    


      

    • The end time of the chapter with title This is my chapter one is 10000 which should be 15000, since that is the value we specified in the END field
    • 


    • The end time of the chapter with title This is my chapter two is 20000 which should be 25000, since that is the value we specified in the END field
    • 


    • The end time of the last chapter is the only one that is the same to the value that we wrote in the metadata file
    • 


    


    I consider this unexpected behavior because ffmpeg should use the end time that we have specified in the metadata file.

    


    


    no. 3

    


    ;FFMETADATA1
title=The title of my video

[CHAPTER]
TIMEBASE=1/1000
START=0
END=1
title=This is my chapter one

[CHAPTER]
TIMEBASE=1/1000
START=10000
END=10001
title=This is my chapter two

[CHAPTER]
TIMEBASE=1/1000
START=20000
END=20001
title=This is my chapter three


    


    The following command creates a simple video and inserts the metadata shown above into that video.

    


    ffmpeg -v error -y -f lavfi -i 'testsrc=d=120:size=100x100' -i metadata.txt -map_metadata 1 output.mp4


    


    The following command shows information about the metadata in the video file that was created by the previous command.

    


    ffprobe -v error -show_chapters -print_format json output.mp4 | jq


    


    {
  "chapters": [
    {
      "id": 0,
      "time_base": "1/1000",
      "start": 0,
      "start_time": "0.000000",
      "end": 10000,
      "end_time": "10.000000",
      "tags": {
        "title": "This is my chapter one"
      }
    },
    {
      "id": 1,
      "time_base": "1/1000",
      "start": 10000,
      "start_time": "10.000000",
      "end": 20000,
      "end_time": "20.000000",
      "tags": {
        "title": "This is my chapter two"
      }
    },
    {
      "id": 2,
      "time_base": "1/1000",
      "start": 20000,
      "start_time": "20.000000",
      "end": 20001,
      "end_time": "20.001000",
      "tags": {
        "title": "This is my chapter three"
      }
    }
  ]
}


    


    From the output above, we can notice the following :

    


      

    • The end time of the chapter with title This is my chapter one is 10000, but it should be 15000, since that is the value we specified in the END field in the metadata file
    • 


    • The end time of the chapter with title This is my chapter two is 20000, but it should be 25000, since that is the value we specified in the END field in the metadata file
    • 


    • The end time of the last chapter is the only one that is the same to the value that we wrote in the metadata file
    • 


    


    I consider this unexpected behavior because ffmpeg should use the end time that we have specified in the metadata file.

    


    


    The questions

    


    In minimal working example no. 2 and minimal working example no. 3, we could see that although the metadata file sets END for each chapter, a different time is used (except for the last chapter). My questions are :

    


      

    • What's the purpose of having a field called END when it only serves a purpose in the last chapter ?
    • 


    • Given that ffmpeg only adds the correct value for END for the last chapter ? Wouldn't a better name for END be END_ONLY_FOR_LAST_CHAPTER ?
    • 


    • Am I doing something wrong that is casuing ffmpeg to use a different value for END in all chapters but the last one ?
    •