Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP 0.2

Autres articles (63)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

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

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

Sur d’autres sites (6575)

  • Video width is different in different devices

    8 novembre 2017, par David

    I have a special video when i want to get this video’s width code returns different value for Samsung galaxy s6 and Samsung note 3. I tested many different codes and libraries, but result is the same.
    in Samsung galaxy s6 : 640x480
    in Samsung note 3 : 853x480
    when I open this video with Gspot program it shows :

    Recommended Display Size : 853x480

    and this is the same value is returned by our IOS app tested in Iphone 7. aspect radio is not the same and this is big problem.

    here is some of codes I tested :

    (1)

        MediaMetadataRetriever metaRetriever = new MediaMetadataRetriever();
    
    metaRetriever.setDataSource(path);
    
    Bitmap bmp = metaRetriever.getFrameAtTime(-1);
    

    
    int height = bmp.getHeight();
    
    int width = bmp.getWidth();

    (2)

        MediaPlayer myMediaPlayer= MediaPlayer.create(ApplicationLoader.applicationContext, 
    
                                     Uri.fromFile(new File(path)));
    

    
    width = myMediaPlayer.getVideoWidth();
    
    height = myMediaPlayer.getVideoHeight();

    (3)

     MediaMetadataRetriever metaRetriever = new MediaMetadataRetriever();
    
        metaRetriever.setDataSource(path);
    
 String heights = metaRetriever.extractMetadata(MediaMetadataRetriever.METADATA_KEY_VIDEO_HEIGHT);
    
        String widths = metaRetriever.extractMetadata(MediaMetadataRetriever.METADATA_KEY_VIDEO_WIDTH);
    
    int height = Integer.valueOf(heights);
    
        int width = Integer.valueOf(widths);

    (4)

      MediaPlayer myMediaPlayer= MediaPlayer.create(ApplicationLoader.applicationContext, Uri.fromFile(new File(path)));
    
            myMediaPlayer.setOnVideoSizeChangedListener((mp, width, height) -> {
    
        int videoWidth = width;
    
        int videoHeight = height;
    
    );
    
            myMediaPlayer.setDataSource(path);
    
            myMediaPlayer.prepare();

    FFmpegMediaMetadataRetriever, FFmpeg Java, ExoPlayer and some other libraries returns the same result.

  • Specifying input duration of .aac with ffmpeg

    28 septembre 2020, par Jademalo

    I had an error with an mp4 recording, and after recovering the video and audio streams I've still got an issue. The aac audio file is 160kb/s CBR. However, ffmpeg returns this when trying to work with it ;

    


    [aac @ 000001187e6944c0] Estimating duration from bitrate, this may be inaccurate
Input #0, aac, from 'result.aac':
  Duration: 00:38:41.01, bitrate: 174 kb/s
    Stream #0:0: Audio: aac (LC), 44100 Hz, stereo, fltp, 174 kb/s


    


    That duration and bitrate is totally wrong. It should be 42 minutes long, and it definitely has a bitrate of 160 kb/s.

    


    This results in the audio being very inconsistently timed, as well as having all sorts of other issues. It's very weird.

    


    Is there any way I can specify that the input is 160 cbr to try and wrangle it back into a usable file ?

    


  • Unable to find a suitable output format for 'pipe :' pipe: : Invalid argument

    22 août 2017, par Mahi

    When I run this command :

    raspivid -n -vf -hf -t 0 -w 960 -h 540 -fps 25 -b 500000 -o - |
    
ffmpeg -i - -vcodec copy -an -metadata title="Streaming from raspberry pi camera" \
    
-f flv $RTMP_URL/$STREAM_KEY

    it returns :

    [NULL @ 0x3414410] Unable to find a suitable output format for 'pipe:'
    
pipe:: Invalid argument

    How should I tweak my command line ?

Navigation