Recherche avancée

Médias (0)

Mot : - Tags -/logo

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

Autres articles (60)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

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

Sur d’autres sites (8703)

  • ac3enc : do not clip coefficients after transforms

    9 janvier 2021, par Lynne
    ac3enc : do not clip coefficients after transforms
    

    In either encoder, its impossible for the coefficients to go past 25 bits
    right after the MDCT. Our MDCT is numerically stable.
    For the floating point encoder, in case a NaN is contained, lrintf() will
    raise a floating point exception during the conversion.

    • [DH] libavcodec/ac3enc_template.c
  • first few seconds of m3u8 clip isn't working, which is generated from another m3u8 file by node js

    13 janvier 2021, par Alan

    index.js

    


    
const ffmpegPath = require('@ffmpeg-installer/ffmpeg').path;
const ffmpeg = require('fluent-ffmpeg');
const process = require('process');


const args = process.argv.slice(2);
if (args.length !== 4) {
    console.error('Incorrect number of arguments');
    process.exit(1);
  }
const startTime = args[0];
const timeDuration = args[1];
const inputFile = args[2];
const outputFile=args[3];

ffmpeg.setFfmpegPath(ffmpegPath);

ffmpeg(inputFile)
  .setStartTime(startTime)
  .setDuration(timeDuration)
  .output(outputFile)
  .outputOptions('-hls_list_size 0')
  .on('end', function(err) {
    if(!err) { console.log('conversion Done') }
  })
  .on('error', function(err){
    console.log('error: ', err)
  }).run();



    


    


    Here is my code which I'm using to create a clip m3u8 formatted file from another m3u8 file. I'm using this command on the terminal to generate it.
Here is the command

    


    node index.js 5 40 ../path/input.m3u8 ../path/output.m3u8

    


    so here 5 is the starting time and 40 is the duration in seconds.
The issue is the first ts file it's generating (for example output_test0.ts) isn't working as it should. It's getting generated in kb format while the others in MB format. So when I play the new m3u8 file, the first 3-5 seconds clip is a static pic but other than that everything works fine.
Here is a link to the m3u8 file. https://mp4.to/downloads/0cb552cd749c4cf4b

    


    


    


    enter image description here

    


    


    


    As you can see the first output_test0.ts file isn't like others. Other output ts files are in MB while the first one only in kb and this case been happening with the first file only. Any command input I'm missing ? need help.

    


    


  • full m3u8 clip isn't getting generated from m3u8 file by node.js

    13 janvier 2021, par Alan

    index.js

    


    const ffmpegPath = require('@ffmpeg-installer/ffmpeg').path;
const ffmpeg = require('fluent-ffmpeg');
const process = require('process');

const args = process.argv.slice(2);
if (args.length !== 4) {
  console.error('Incorrect number of arguments');
  process.exit(1);
}

const startTime = args[0];
const timeDuration = args[1];
const inputFile = args[2];
const outputFile=args[3];

ffmpeg.setFfmpegPath(ffmpegPath);

ffmpeg(inputFile)
  .setStartTime(startTime)
  .setDuration(timeDuration)
  .output(outputFile)
  .on('end', function(err) {
    if(!err) { 
      console.log('conversion Done') 
    }
  })
  .on('error', function(err){
    console.log('error: ', err)
  }).run();


    


    I am running this command on the terminal to generate a clip from the m3u8 file
node index.js 00:00:10 46 ./path/sample.m3u8 ./path/output.m3u8

    


    The main problem is that it is not creating a clip for more than 13 seconds. For example, the above command should generate a 46s clip but it is going near 13 seconds. So I don't get what is the issue. Any clip less than 13 works perfectly fine. Is there any way to fix that ?

    


    Here is a link to the m3u8 file https://mp4.to/downloads/0cb552cd749c4cf4b