Recherche avancée

Médias (1)

Mot : - Tags -/musée

Autres articles (98)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

Sur d’autres sites (17312)

  • libavcodec/libx264 : fix reference frame computation based on level

    16 avril 2020, par Josh Brewster
    libavcodec/libx264 : fix reference frame computation based on level
    

    The current implementation allows passing levels to libavcodec as
    integers (such as "31" instead of "3.1").

    However, in this case, the maximum reference frame value per level was
    ignored because libavcodec converted the string to 310 instead of 31.

    Since libx264 has correctly parsed the level to int
    (x4->params.i_level_idc), we should rely on this value instead of
    attempting to parse the level string on our own.

    Signed-off-by : Josh Brewster <josh.brewster@protonmail.com>
    Signed-off-by : Josh de Kock <josh@itanimul.li>

    • [DH] libavcodec/libx264.c
  • Edit H264 video stream header information ("start_pts" and "start_time")

    27 juin 2020, par David

    I have a video clip that appears to be slightly corrupted. Does not play on VLC but works on Potplayer. I used FFprobe to get information on the video.

    &#xA;

    The problem appears to be with the start points of the video stream :

    &#xA;

    time_base=1/90000&#xA;start_pts=585050940&#xA;start_time=6500.566000&#xA;duration_ts=585050940&#xA;duration=6500.566000&#xA;bit_rate=3123218&#xA;

    &#xA;

    I'm just wondering whether it is possible to manually edit the "start_pts" and "start_time" to 0 ? Is there any specific software to do this ? Due to large size of video file, I couldn't load it in Notepad++.

    &#xA;

    Full ffprobe output shown below :

    &#xA;

    # ffprobe output&#xA;&#xA;[streams.stream.0]&#xA;index=0&#xA;codec_name=h264&#xA;codec_long_name=H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10&#xA;profile=unknown&#xA;codec_type=video&#xA;codec_time_base=1/60&#xA;codec_tag_string=avc1&#xA;codec_tag=0x31637661&#xA;width=1920&#xA;height=1080&#xA;coded_width=1920&#xA;coded_height=1080&#xA;closed_captions=0&#xA;has_b_frames=0&#xA;sample_aspect_ratio=N/A&#xA;display_aspect_ratio=N/A&#xA;pix_fmt=unknown&#xA;level=-99&#xA;color_range=unknown&#xA;color_space=unknown&#xA;color_transfer=unknown&#xA;color_primaries=unknown&#xA;chroma_location=unspecified&#xA;field_order=unknown&#xA;timecode=N/A&#xA;refs=1&#xA;is_avc=true&#xA;nal_length_size=4&#xA;id=N/A&#xA;r_frame_rate=30/1&#xA;avg_frame_rate=30/1&#xA;time_base=1/90000&#xA;start_pts=585050940&#xA;start_time=6500.566000&#xA;duration_ts=585050940&#xA;duration=6500.566000&#xA;bit_rate=3123218&#xA;max_bit_rate=N/A&#xA;bits_per_raw_sample=N/A&#xA;nb_frames=195017&#xA;nb_read_frames=N/A&#xA;nb_read_packets=N/A&#xA;&#xA;[streams.stream.0.disposition]&#xA;default=1&#xA;dub=0&#xA;original=0&#xA;comment=0&#xA;lyrics=0&#xA;karaoke=0&#xA;forced=0&#xA;hearing_impaired=0&#xA;visual_impaired=0&#xA;clean_effects=0&#xA;attached_pic=0&#xA;timed_thumbnails=0&#xA;&#xA;[streams.stream.0.tags]&#xA;language=und&#xA;handler_name=VideoHandler&#xA;&#xA;[streams.stream.1]&#xA;index=1&#xA;codec_name=aac&#xA;codec_long_name=AAC (Advanced Audio Coding)&#xA;profile=LC&#xA;codec_type=audio&#xA;codec_time_base=1/48000&#xA;codec_tag_string=mp4a&#xA;codec_tag=0x6134706d&#xA;sample_fmt=fltp&#xA;sample_rate=48000&#xA;channels=2&#xA;channel_layout=stereo&#xA;bits_per_sample=0&#xA;id=N/A&#xA;r_frame_rate=0/0&#xA;avg_frame_rate=0/0&#xA;time_base=1/48000&#xA;start_pts=0&#xA;start_time=0.000000&#xA;duration_ts=312029184&#xA;duration=6500.608000&#xA;bit_rate=189376&#xA;max_bit_rate=189376&#xA;bits_per_raw_sample=N/A&#xA;nb_frames=304718&#xA;nb_read_frames=N/A&#xA;nb_read_packets=N/A&#xA;&#xA;[streams.stream.1.disposition]&#xA;default=1&#xA;dub=0&#xA;original=0&#xA;comment=0&#xA;lyrics=0&#xA;karaoke=0&#xA;forced=0&#xA;hearing_impaired=0&#xA;visual_impaired=0&#xA;clean_effects=0&#xA;attached_pic=0&#xA;timed_thumbnails=0&#xA;&#xA;[streams.stream.1.tags]&#xA;language=eng&#xA;handler_name=SoundHandler&#xA;&#xA;[format]&#xA;filename=D\:\\Start\\test.mp4&#xA;nb_streams=2&#xA;nb_programs=0&#xA;format_name=mov,mp4,m4a,3gp,3g2,mj2&#xA;format_long_name=QuickTime / MOV&#xA;start_time=0.000000&#xA;duration=6500.608000&#xA;size=2703218140&#xA;bit_rate=3326726&#xA;probe_score=100&#xA;&#xA;[format.tags]&#xA;major_brand=isom&#xA;minor_version=512&#xA;compatible_brands=isomiso2avc1mp41&#xA;

    &#xA;

  • Basic "pass-through" use of FFmpegReader/FFmpegWriter in scikit-video

    6 février 2021, par JonathanZ supports MonicaC

    I am starting to use scikit-video and am having trouble writing files. I have reduced the problem to the simplest possible example

    &#xA;

    vid_file = "6710185719062326259_stamp_25pct.mp4"&#xA;output_file = "out_temp3.mp4"&#xA;reader = skvideo.io.FFmpegReader(vid_file)&#xA;writer = skvideo.io.FFmpegWriter(output_file)&#xA;for frame in reader.nextFrame():&#xA;        writer.writeFrame(frame)&#xA;writer.close()&#xA;

    &#xA;

    I'm playing the files in VLC, and the vid_file is valid but the output file, though playable, is mostly big green blocks (though I can discern some details from the original video in it).

    &#xA;

    My goal, or course, is to do "interesting" manipulations of the frame before I write it out, but I need to get the "no modifications" version working correctly first. I'm also going to be using this on large files, so the vread/vwrite functions that process an entire file at once are not appropriate.

    &#xA;

    I'm guessing I need to set the appropriate values in the outputdict parameter for the FFmpegWriter, but there are so many that I don't know where to start. I have tried

    &#xA;

    writer = skvideo.io.FFmpegWriter(output_file, outputdict={&#x27;-crf&#x27;: &#x27;0&#x27;, &#x27;-pix_fmt&#x27;: &#x27;rgb24&#x27;})&#xA;

    &#xA;

    (-crf 0 to suppress any compression, -pixfmt rgb24 as that's what FFmpegReader says it delivers by default, but these don't work either.

    &#xA;

    Any ideas on how to make this work ?

    &#xA;

    Here's the skvideo.io.ffprobe video information for the input file.

    &#xA;

    {&#xA;    "@index": "0",&#xA;    "@codec_name": "h264",&#xA;    "@codec_long_name": "H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10",&#xA;    "@profile": "High",&#xA;    "@codec_type": "video",&#xA;    "@codec_time_base": "1/30",&#xA;    "@codec_tag_string": "avc1",&#xA;    "@codec_tag": "0x31637661",&#xA;    "@width": "480",&#xA;    "@height": "270",&#xA;    "@coded_width": "480",&#xA;    "@coded_height": "272",&#xA;    "@has_b_frames": "2",&#xA;    "@pix_fmt": "yuv420p",&#xA;    "@level": "21",&#xA;    "@chroma_location": "left",&#xA;    "@refs": "1",&#xA;    "@is_avc": "true",&#xA;    "@nal_length_size": "4",&#xA;    "@r_frame_rate": "15/1",&#xA;    "@avg_frame_rate": "15/1",&#xA;    "@time_base": "1/15360",&#xA;    "@start_pts": "0",&#xA;    "@start_time": "0.000000",&#xA;    "@duration_ts": "122880",&#xA;    "@duration": "8.000000",&#xA;    "@bit_rate": "183806",&#xA;    "@bits_per_raw_sample": "8",&#xA;    "@nb_frames": "120",&#xA;    "disposition": {&#xA;        "@default": "1",&#xA;        "@dub": "0",&#xA;        "@original": "0",&#xA;        "@comment": "0",&#xA;        "@lyrics": "0",&#xA;        "@karaoke": "0",&#xA;        "@forced": "0",&#xA;        "@hearing_impaired": "0",&#xA;        "@visual_impaired": "0",&#xA;        "@clean_effects": "0",&#xA;        "@attached_pic": "0",&#xA;        "@timed_thumbnails": "0"&#xA;    },&#xA;    "tag": [&#xA;        {&#xA;            "@key": "language",&#xA;            "@value": "und"&#xA;        },&#xA;        {&#xA;            "@key": "handler_name",&#xA;            "@value": "VideoHandler"&#xA;        }&#xA;    ]&#xA;}&#xA;

    &#xA;

    I will mention that when I ffprobe the output file the only differences I see are 1) the timing data is different, which isn't surprising, and 2) the output file has

    &#xA;

        "@has_b_frames": "0",&#xA;    "@pix_fmt": "yuv444p",&#xA;

    &#xA;

    I'm pretty confident the reader is working okay, because if I write out the data with

    &#xA;

    skimage.io.imsave(&#x27;x.png&#x27;, frame,  check_contrast=False)&#xA;

    &#xA;

    it looks good.

    &#xA;