Recherche avancée

Médias (91)

Autres articles (51)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • L’espace de configuration de MediaSPIP

    29 novembre 2010, par

    L’espace de configuration de MediaSPIP est réservé aux administrateurs. Un lien de menu "administrer" est généralement affiché en haut de la page [1].
    Il permet de configurer finement votre site.
    La navigation de cet espace de configuration est divisé en trois parties : la configuration générale du site qui permet notamment de modifier : les informations principales concernant le site (...)

  • Activation de l’inscription des visiteurs

    12 avril 2011, par

    Il est également possible d’activer l’inscription des visiteurs ce qui permettra à tout un chacun d’ouvrir soit même un compte sur le canal en question dans le cadre de projets ouverts par exemple.
    Pour ce faire, il suffit d’aller dans l’espace de configuration du site en choisissant le sous menus "Gestion des utilisateurs". Le premier formulaire visible correspond à cette fonctionnalité.
    Par défaut, MediaSPIP a créé lors de son initialisation un élément de menu dans le menu du haut de la page menant (...)

Sur d’autres sites (8240)

  • FFMPEG Scan and Convert Movie files and Delete Original - reclusively

    29 mai 2021, par Frodo Baggins

    I have folders within folders that have movie files, some of them are .mp4, .avi or .mov/.MOV. I need to re-compress them into H264 High Quality (Lets say, 10MBPS) and delete the originals when complete. I have the following code, but this is for audio and I don't know where to go from here. I am using Mac terminal.

    


    for i in *.ogg; do ffmpeg -i "$i" -b:a 320000 "${i%.*}.mp3"; done

    


  • Movie from PNGs using FFmpeg and Python - rgb24 vs yuv420p

    7 février 2016, par Eilam G

    I wrote a little Python program to grab a bunch of PNGs and render them into a movie using the FFmpeg command line. The PNGs are read into [X*Y*3] numpy arrays (ignoring the alpha channel), new frames are added via interpolation, and the data is fed into FFmpeg as a pipe and saved as an mp4.

    The files play fine in VLC on Windows, but don’t work in iMovie on a Mac. I think it might have to do with most programs expecting H264 videos to be in the YUV420P color space, which my movies aren’t. I’ve tried changing the ffmpeg command -pix_fmt from rgb24 to yuv420p, but no go.

    Relevant Python code attached below.

    def init_vars(args):
       global log_file, file_names, command, num_int_frames, num_files, silent

       file_names = glob('./*.png')
       num_files = len(file_names)

       if args.log:
           log_file = 'bmmp.log'
       else:
           log_file = os.devnull

       silent = args.silent

       frames_per_second = args.fps
       wanted_movie_length = args.length
       movie_file_name = args.name + '.mp4'

       num_int_frames = round((frames_per_second * wanted_movie_length - 1) / (num_files - 1) - 1)

       if sys.platform == 'win32':
           ffmpeg_bin = 'ffmpeg.exe'
       else:
           ffmpeg_bin = 'ffmpeg'

       command = [ffmpeg_bin,
                  '-y', # (optional) overwrite output file if it exists
                  '-f', 'rawvideo',
                  '-vcodec','rawvideo',
                  '-s', '1280x720', # size of one frame
                  '-pix_fmt', 'rgb24',
                  '-r', str(frames_per_second), # frames per second
                  '-i', '-', # The input comes from a pipe
                  '-an', # Tells FFMPEG not to expect any audio
                  movie_file_name]

    Cheers,
    Eilam

  • The duration of movie file recorded by AVAssetWriter is not correct

    1er mars 2016, par ideawu

    I am recording video files with AVAssetWriter combining with AVCaptureVideoDataOutputSampleBufferDelegate. So I can take control over every frame the camara gives in the method :

    - (void)captureOutput:(AVCaptureOutput *)captureOutput didOutputSampleBuffer:(CMSampleBufferRef)sampleBuffer fromConnection:(AVCaptureConnection *)connection{
       double time = CMTimeGetSeconds(CMSampleBufferGetPresentationTimeStamp(sampleBuffer));
       NSLog(@"%f", time);
       [_videoInput appendSampleBuffer:sampleBuffer];
    }

    So I am so sure how many samples have been written to AVAssetWriter via AVAssetWriterInput, and I know exactly the start time and end time of the samples being written. The duration is calculated by end_time - start_time. Say the duration calculated in the video capture programm is 0.5 second.

    I get the .mov/.mp4 file on disk, inspected with ffmpeg -i, it shows a very different duration.

    ffmpeg -i m003.mp4 2>&1 | grep Dura
     Duration: 00:00:01.37, start: 0.836667, bitrate: 95 kb/s

    The movie file show a duration of 1.37 seconds, which it’s quite different with the EXACT duration 0.5.

    Does any one knows the reason ?