Recherche avancée

Médias (0)

Mot : - Tags -/flash

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

Autres articles (9)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Librairies et logiciels spécifiques aux médias

    10 décembre 2010, par

    Pour un fonctionnement correct et optimal, plusieurs choses sont à prendre en considération.
    Il est important, après avoir installé apache2, mysql et php5, d’installer d’autres logiciels nécessaires dont les installations sont décrites dans les liens afférants. Un ensemble de librairies multimedias (x264, libtheora, libvpx) utilisées pour l’encodage et le décodage des vidéos et sons afin de supporter le plus grand nombre de fichiers possibles. Cf. : ce tutoriel ; FFMpeg avec le maximum de décodeurs et (...)

Sur d’autres sites (4897)

  • lavu : add new D3D11 pixfmt and hwcontext

    6 juin 2017, par wm4
    lavu : add new D3D11 pixfmt and hwcontext
    

    To be used with the new d3d11 hwaccel decode API.

    With the new hwaccel API, we don’t want surfaces to depend on the
    decoder (other than the required dimension and format). The old D3D11VA
    pixfmt uses ID3D11VideoDecoderOutputView pointers, which include the
    decoder configuration, and thus is incompatible with the new hwaccel
    API. This patch introduces AV_PIX_FMT_D3D11, which uses ID3D11Texture2D
    and an index. It’s simpler and compatible with the new hwaccel API.

    The introduced hwcontext supports only the new pixfmt.

    Frame upload code untested.

    Significantly based on work by Steve Lhomme <robux4@gmail.com>, but with
    heavy changes/rewrites.

    Signed-off-by : Diego Biurrun <diego@biurrun.de>

    • [DBH] doc/APIchanges
    • [DBH] libavutil/Makefile
    • [DBH] libavutil/hwcontext.c
    • [DBH] libavutil/hwcontext.h
    • [DBH] libavutil/hwcontext_d3d11va.c
    • [DBH] libavutil/hwcontext_d3d11va.h
    • [DBH] libavutil/hwcontext_internal.h
    • [DBH] libavutil/pixdesc.c
    • [DBH] libavutil/pixfmt.h
    • [DBH] libavutil/version.h
  • Python script doesn't work properly when ran through terminal, but works fine in Jupyter and Visual Studio

    21 octobre 2018, par Ivan Novikov

    I have a script to extract the audio from all video files in a folder.

    The folder with videos is located at : /Users/MyName/Downloads/Video_Audio_files

    When I try to run it through terminal and I’m prompted for the folder path folder = input("Path to folder:"), I drag and drop it there (which is how I got the above path), but the script doesn’t seem to be working (stuck at 0 out of 7 and no output files).

    When I input exactly the same path when prompted in Jupyter Notebook or in Visual Studio it works perfectly !

    Edit : I think I have found the issue, when I drag and drop the folder, there is an extra space (’Downloads/folder ’ instead of ’Downloads/folder’).

    pbar = ProgressBar()
    files = []
    extensions = []
    folder = input("Path to folder:")
    #folder = 'Video_Audio_files'
    pathlist = Path(folder).glob('**/*.mp4')
    for path in pathlist:
       path_in_str = str(path)
       name = path_in_str.split("/")[1]
       files.append(path_in_str.split(".")[0])
       extensions.append(path_in_str.split(".")[1])

    os.system('cd ' + folder)

    for i in pbar(range(len(files))):
       video_format = extensions[i]
       video_name = files[i]
       output_format = 'flac'
       output_name = video_name + '_audio'

       bashCommand = 'ffmpeg -i ' + video_name + '.'   + video_format + ' -f ' + output_format + ' -ab 192000 -vn ' + output_name + '.' + output_format
    #should be of this format: bashCommand = 'ffmpeg -i Video.mp4 -f flac -ab 192000 -vn ExtractedAudio.flac'

       os.system(bashCommand)
  • lavfi : add a new struct for private link properties

    5 août 2024, par Anton Khirnov
    lavfi : add a new struct for private link properties
    

    Specifically those that should be visible to filters, but hidden from
    API callers. Such properties are currently located at the end of the
    public AVFilterLink struct, demarcated by a comment marking them as
    private. However it is generally better to hide them explicitly, using
    the same pattern already employed in avformat or avcodec.

    The new struct is currently trivial, but will become more useful in
    following commits.

    • [DH] libavfilter/avfilter.c
    • [DH] libavfilter/avfilter_internal.h
    • [DH] libavfilter/avfiltergraph.c
    • [DH] libavfilter/filters.h