Recherche avancée

Médias (1)

Mot : - Tags -/net art

Autres articles (75)

  • 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 ;

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (7703)

  • Using explicit casting to solve invalid conversion from ‘int’ to ‘AVRounding’

    29 juillet 2020, par C4RN4GE

    I'm trying to follow the "learn ffmpeg the hard way" guide on github (https://github.com/leandromoreira/ffmpeg-libav-tutorial#chapter-2---remuxing) and when I try to run the remuxing code for myself using a C++ compiler I always get the error

    


    invalid conversion from ‘int’ to ‘AVRounding’[-fpermissive]


    


    The only real difference between my code and the github original is that I take the input filename and output filename as parameters instead. Doing some resarch I have found that AVRounding is a enum ? I think ? Thus I need to explicitly cast somehow. However I'm failing to understand how explicit casting works and how I would use it to solve my issue. Where would I cast it ?
Here's the line that causes the issue :

    


    packet.pts =  av_rescale_q_rnd(packet.pts, in_stream->time_base, out_stream->time_base, AV_ROUND_NEAR_INF|AV_ROUND_PASS_MINMAX);
packet.dts =  av_rescale_q_rnd(packet.dts, in_stream->time_base, out_stream->time_base, AV_ROUND_NEAR_INF|AV_ROUND_PASS_MINMAX);


    


    Could anyone explain how to solve the issue ? Sorry if it's a beginners mistake. Thanks in advance for any help.

    


  • Cutting out a part of a video in ffmpeg creates a corrupted output file

    30 octobre 2020, par lagmoellertim

    I currently have a problem with ffmpeg. I'm trying to cut out a part of a video (e.g. from 00:10:00 to 00:10:30).

    


    I use this command ffmpeg -ss 600 -to 630 -i not_working.mp4  not_working_part.mp4.

    


    I tried reencoding the video, but it is still corrupted (only first few frames working, video is multiple hours long but jumps to end if you try to skip).

    


    I use the -ss and the -to parameter before the -i parameter because it is much faster I want to cut out a part that is e.g. right at the end of the video. Moving the -i parameter infront of the other args solves the problem, but the performance is really bad for cutouts late in the video. For many other of my videos, both methods work without a problem.

    


    Here is some metadata about the video from ffmpeg :

    


    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'media\not_working.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2020-09-22T06:20:53.000000Z
  Duration: 03:03:40.04, start: 0.000000, bitrate: 537 kb/s
    Chapter #0:0: start 0.000000, end 204.120000
    Metadata:
      title           : Recording Started
    Chapter #0:1: start 204.120000, end 2045.200000
    Metadata:
      title           : Sharing Started
    Chapter #0:2: start 2045.200000, end 2056.880000
    Metadata:
      title           : Sharing Stopped
    Chapter #0:3: start 2056.880000, end 4018.280000
    Metadata:
      title           : Sharing Started
    Chapter #0:4: start 4018.280000, end 4024.760000
    Metadata:
      title           : Sharing Stopped
    Chapter #0:5: start 4024.760000, end 4096.000000
    Metadata:
      title           : Sharing Started
    Chapter #0:6: start 4096.000000, end 4101.800000
    Metadata:
      title           : Sharing Stopped
    Chapter #0:7: start 4101.800000, end 4481.920000
    Metadata:
      title           : Sharing Started
    Chapter #0:8: start 4481.920000, end 4624.480000
    Metadata:
      title           : Sharing Stopped
    Chapter #0:9: start 4624.480000, end 6902.000000
    Metadata:
      title           : Sharing Started
    Chapter #0:10: start 6902.000000, end 6906.760000
    Metadata:
      title           : Sharing Stopped
    Chapter #0:11: start 6906.760000, end 6922.880000
    Metadata:
      title           : Sharing Started
    Chapter #0:12: start 6922.880000, end 6936.800000
    Metadata:
      title           : Sharing Stopped
    Chapter #0:13: start 6936.800000, end 9140.840000
    Metadata:
      title           : Sharing Started
    Chapter #0:14: start 9140.840000, end 9145.680000
    Metadata:
      title           : Sharing Stopped
    Chapter #0:15: start 9145.680000, end 9297.600000
    Metadata:
      title           : Sharing Started
    Chapter #0:16: start 9297.600000, end 9306.040000
    Metadata:
      title           : Sharing Stopped
    Chapter #0:17: start 9306.040000, end 9572.480000
    Metadata:
      title           : Sharing Started
    Chapter #0:18: start 9572.480000, end 9620.680000
    Metadata:
      title           : Sharing Stopped
    Chapter #0:19: start 9620.680000, end 10020.760000
    Metadata:
      title           : Sharing Started
    Chapter #0:20: start 10020.760000, end 10085.480000
    Metadata:
      title           : Sharing Stopped
    Chapter #0:21: start 10085.480000, end 10781.920000
    Metadata:
      title           : Sharing Started
    Chapter #0:22: start 10781.920000, end 11020.040000
    Metadata:
      title           : Sharing Stopped
    Stream #0:0(und): Audio: aac (LC) (mp4a / 0x6134706D), 32000 Hz, mono, fltp, 53 kb/s (default)
    Metadata:
      creation_time   : 2020-09-22T06:20:53.000000Z
      handler_name    : AAC audio
    Stream #0:1(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x1080, 481 kb/s, 25 fps, 25 tbr, 30k tbn, 60k tbc (default)
    Metadata:
      creation_time   : 2020-09-22T06:20:53.000000Z
      handler_name    : H.264/AVC video
      encoder         : AVC Coding
    Stream #0:2(und): Data: bin_data (text / 0x74786574)
    Metadata:
      creation_time   : 2020-09-22T06:20:53.000000Z
      handler_name    : Text


    


    Here is a link to the -report log file from ffmpeg (on pastebin) : https://pastebin.com/i9ix3GsC

    


  • ffmpeg timing metadata values differ from the ffprobe output

    17 mai 2021, par loretoparisi

    When printing the ffmetadata metadata of an audio file with the ffmpeg command :

    


    ffmpeg -i INPUT.mp4 -f ffmetadata FFMETADATAFILE


    


    the approximation of the timing values fields start and end in the [CHAPTER] object :

    


    [CHAPTER]
TIMEBASE=1/1000
START=533975
END=586975
title=Meltdown/Spectre patched


    


    is different from the same timing metadata, obtained using the JSON output with ffprobe the command :

    


    ffprobe -i INPUT.mp4 -show_chapters -print_format json


    


    that is

    


      {
        "id": 2,
        "time_base": "1/1000",
        "start": 534000,
        "start_time": "534.000000",
        "end": 587000,
        "end_time": "587.000000",
        "tags": {
            "title": "Meltdown/Spectre patched"
        }
    }


    


    where start_time is start and end_time is end of the ffmpeg output. Is there a way to handle the timing info the ffprobe metadata output ?