Recherche avancée

Médias (0)

Mot : - Tags -/objet éditorial

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

Autres articles (70)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

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

  • 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" (...)

Sur d’autres sites (12447)

  • Which command line and version do I need to reproduce those properties ?

    26 décembre 2015, par Zurechtweiser

    I have a file for which ffmpeg gave those properties :

    ...
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'TEST.MOV':
    
  Metadata:
    
    major_brand     : qt  
    
    minor_version   : 0
    
    compatible_brands: qt  
    
    creation_time   : 2015-12-26 07:45:26
    
  Duration: 00:00:02.75, start: 0.000000, bitrate: 4935 kb/s
    
    Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuvj420p(pc), 1280x720 [SAR 1:1 DAR 16:9], 4775 kb/s, 59.94 fps, 59.94 tbr, 180k tbn, 119.88 tbc (default)
    
    Metadata:
    
      creation_time   : 2015-12-26 07:45:26
    
      handler_name    : Ambarella AVC
    
    Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 64 kb/s (default)
    
    Metadata:
    
      creation_time   : 2015-12-26 07:45:26
    
      handler_name    : Ambarella AAC

    Which command line and version do I need to reproduce those properties ?

    I tried

    ffmpeg -i "test.mp4" -s 1280x720 -vcodec libx264 -c:a libvo_aacenc -q:a 3 -r 59.94 -b:v 4935k -b:a 64k -ac 1 -ar 48000 TEST2.MOV

    But it’s not the same.

    Goal is simple : my actioncam has a hdmi-output. I want to watch movies next to my own footage using my actioncam when I am abroad. Goal is to make the actioncam think, it was it’s own footage to play it back. Currently I only get ’invalid’.

  • Redirect StandardOutput from a process

    25 décembre 2015, par Prakash M

    I am working on C++/CLI winforms
    how to redirect standard output to textbox ?
    I followed this video, but it didn’t work
    https://www.youtube.com/watch?v=BDTCviA-5M8

    I can see output in console window, but till process finishes GUI freezes !

    ProcessStartInfo ^psi = gcnew ProcessStartInfo("D://ffmpeg.exe", "-y -i D://1.avi D://process.mp4");        
    
psi->WindowStyle = ProcessWindowStyle::Hidden;
    
psi->UseShellExecute = false;
    
psi->RedirectStandardOutput = true;
    
process->StartInfo = psi;
    

    
process->Start();
    
String^ details = process->StandardOutput->ReadToEnd();
    
textBox1->Text = details; 
    
Console::WriteLine(details);

    Where am I going wrong ?

  • FFmpegWrapper - get exact segment start or end times ?

    21 décembre 2015, par Stefan Kendall

    Right now, I’m using FFmpegWrapper, and I watch for changes via kernel events. This gets the segments when they’re created, but I’m not sure how accurate this is.

    Really, I want to know the presentation timestamp of when the hls segment is created. Right now I capture and encode frames manually and write packets via
    FFOutputFile *outputFile;
    [_outputFile writePacket:_packet error:&error];

    So I have each frame’s presentationTimestamp, but I don’t know which frame goes to which eventual MPEG-TS segment. Once I write to the FFOutputFile, it’s a blackbox to me.

    Is there any way to know what frame will go to what segment ahead of time, or get a callback from FFmpeg when a new segment is written ?

    Exact times are ideal. Close times are better. Watching the directory for new files via kernel events is what I have right now, so any solution of that time magnitude isn’t useful.

Navigation