Recherche avancée

Médias (1)

Mot : - Tags -/belgique

Autres articles (105)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

Sur d’autres sites (11355)

  • Video playing, how to play a video back a a rapid rate at random timestamp locations

    10 avril 2020, par Zarc Rowden

    Note : this is a mildly general question that is looking more for pointers in the right direction and not exactly requiring a concise coded answer. I appreciate any and all input, thank you for lending your brain power to me for this moment :)

    



    I have a script that receives midi messages in real time and triggers playback of a single video on various timestamps that are changed/selected regularly and randomly by a user. Currently this is working in the browser, however, I've realized that there is some noticeable latency between (i'm guessing the cause here so please correct me) the moment a request to play a video at a specific time is made(note : the video is not being requested over the wire, this action does not take place until a JS Blob Url is loaded into the player) and the moment where that request is fulfilled and delivered from storage to pixels on the screen.

    



    My question is : Is it reasonable to assume that there is a tool out there, that given the correct video format and optimizations both in the code and in the file that could load an entire, say : 1 gb video into memory and play it back at random timestamps every 60 milliseconds at completely random, constantly changing timestamps.

    



    If you're now all the way down here... Thanks for reading this far, or scanning ! Please let me know if this question makes any sense / could be improved, I'm happy to clarify further.

    


  • Firefox does not support mkv format videos, need to convert video to mp4

    21 mai 2021, par sambhav jain

    I am making a screen recorder app that records your screen and upload the video to the s3 bucket. the video is in mpv format. the mkv format is supported by chrome, edge but not by firefox. Firefox supports the mp4 format. so how do I convert the video to mp4 format for firefox ? videofile is in mkv which needs to be converted to mp4

    


    handleUpload() {
    for (let i = 0; i < this.files.length; i++) {
      this.awsUploadService
        .getSignedUrlS3(this.files[i]["name"], this.files[i]["type"])
        .subscribe(
          ({ url, keyFile }) => {
            this.awsUploadService
              .uploadfileAWSS3(url, this.files[i]["type"], this.files[i])
              .subscribe(
                (data) => {
                  if (data["type"] === 1) {
                    this.files[i]["progress"] =
                      (data["loaded"] / data["total"]) * 100;
                  }
                  if (data["type"] === 4) {
                    this.files[i]["isUploadCompleted"] = true;
                    this.files[i][
                      "uploadLocation"
                    ] = `https://${environment.S3_BUCKET_NAME}.s3.${environment.S3_Region}.amazonaws.com/${keyFile}`;
                  }
                },
                (error) => {
                  this.files[i].isUploadCompleted = false;
                  throw error;
                }
              );
          },
          (error) => {
            this.files[i].isUploadCompleted = false;
            throw error;
          }
        );
    }
  }


    


  • need more clarity on compiling syntax for shared binaries using static dependencies

    22 juin 2016, par art vanderlay

    I am compiling on linux and am trying to understand the complexities of shared and static libs, what can be done and what should not be done.

    Using the example of ffmpeg, I have x264 as an included dependency.

    Based on many posts here on SO, it seems a static build of x264 would be best. Then load these into several different version of ffmpeg dynamically as needed.

    What is the correct configure syntax when compiling both binaries.

    scenario one

    x264 --enable-static --disable-shared
    ffmpeg --disable-static --enable-shared --enable-libx264  

    or the other way round

    x264 --disable-static --enable-shared    
    ffmpeg --enable-static --disable-shared --enable-libx264  

    scenario two, assume a theoretical dependency waterfall, where we must include (prog-x into x264) then x264 dynamically loaded into ffmpeg

    progx--enable-static --disable-shared    
    x264 --enable-static --disable-shared
    ffmpeg --disable-static --enable-shared --enable-libx264