Recherche avancée

Médias (91)

Autres articles (45)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • 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

  • 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 (5327)

  • Registration free (sxs) COM DirectShow filter

    21 septembre 2015, par caesay

    There are questions asking on how to get Registration free COM working, and this is not one of those. I have a DirectShow video source filter (catagory 860BB310-5D01-11d0-BD3B-00A0C911CE86) implemented in .Net with the help of an edited version of the code available here : Pure .Net DirectShow Filters by Maxim Kartavenkov.

    I need to get ffmpeg to recognize my .Net DirectShow filter as a video source using Registration Free COM (Side by Side / sxs). Built into the .Net framework is support for COM component servers, so theoretically as long as the manifests are correct, ffmpeg should detect the filters.

    Here is a snippet of the relevant sections of my manifest files currently.

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <assembly manifestversion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1">
    <assemblyidentity version="1.0.0.0" type="win32" processorarchitecture="*"></assemblyidentity>
    <dependency>
    <dependentassembly>
     <assemblyidentity version="1.0.0.0" publickeytoken="26A05D7C90FBA3E8"></assemblyidentity>
    </dependentassembly>
    </dependency>
    </assembly>
    &lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestversion="1.0">
      <assemblyidentity version="1.0.0.0" publickeytoken="26A05D7C90FBA3E8"></assemblyidentity>
      <clrclass clsid="{65722BE6-3449-4628-ABD3-74B6864F9739}" progid="DShowVideoFilter.VideoCaptureFilter" threadingmodel="Both" runtimeversion="v2.0.50727"></clrclass>
      <file>
      </file>
      <file>
        <typelib tlbid="{B618E67B-64C8-48E9-9F94-F13214B76808}" version="1.0" helpdir="" flags="hasdiskimage"></typelib>
      </file>
    </assembly>

    So, I get no errors when running ffmpeg (like you would if there was a manifest error) - and I am confident that everything that is configured correctly (related to traditional sxs com loading), the problem I think (unconfirmed) is that ffmpeg loads DShow filters via DirectShow’s intelligent connect system, which requires the filter and pins to be registered. Here are some documents that talk about how filters need to be registered that I’ve found :

    Now, in Maxim Kartavenkov’s DShow base classes, he takes care of #2 automatically. Here is a significantly shortened version of the method that registers the filters implementing BaseFilter.

    [ComRegisterFunction]
    public static void RegisterFunction(Type _type)
    {
       AMovieSetup _setup = (AMovieSetup)Attribute.GetCustomAttribute(_type, typeof(AMovieSetup));
       BaseFilter _filter = (BaseFilter)Activator.CreateInstance(_type);
       string _name = _filter.Name;
       DsGuid _category = new DsGuid(_setup.Category);
       IFilterMapper2 _mapper2 = (IFilterMapper2)new FilterMapper2();

       RegFilter2 _reg2 = new RegFilter2();
       _reg2.dwVersion = (int)_setup.Version;
       _reg2.dwMerit = _setup.FilterMerit;
       _reg2.rgPins = IntPtr.Zero;
       _reg2.cPins = 0;

       IntPtr _register = Marshal.AllocCoTaskMem(Marshal.SizeOf(_reg2));
       Marshal.StructureToPtr(_reg2, _register, true);

       hr = _mapper2.RegisterFilter(_type.GUID, _name, IntPtr.Zero, _category, _instance, _register);

       Marshal.FreeCoTaskMem(_register);
    }

    That is the method (particularly mapper2.RegisterFilter) that allows ffmpeg to find the DShow filter when it is registered traditionally (with RegAsm) into the registry, which creates registry keys for the filter and pins as described by #2 link.

    tldr ;
    So the question is, how to emulate the function of RegisterFilter or the intelligent connect registry entries this within a manifest file as to allow the sxs context to find my DirectShow filter when ffmpeg searches for it.

  • FFMPEG Encoding MP4 for iOS

    3 août 2015, par Ryan K

    I am using the gem streamio-ffmpeg to convert an .mp4 file to another .mp4 file that conforms to iOS standards. I want to put that file in an HTML5 video tag. The video plays well on desktop and Android devices. However, no matter what I do, the iPad Mini 2 that I’m using will not play the video.

    My options hash looks like this :

    options = {video_codec: "libx264", resolution: "480x320", frame_rate: 30, video_bitrate: 500,
                x264_vprofile: "baseline", x264_preset: "slow", audio_codec: "aac", audio_bitrate: 56, aspect: 1.333333,
                audio_sample_rate: 44100, audio_channels: 1, custom: "-strict -2"}

    When I load the new .mp4 file back into streamio-ffmpeg, this is the object (and metadata) returned :

    #

    I’ve tried just about everything I could find, with different bit rates, codecs, resolutions, etc. What are the correct options to play an .mp4 on an iOS device ?

    BTW, streamio-ffmpeg allows pure ffmpeg options, so I’m ok with that.

  • avcodec/jpeg2000dec : Use 32x32->64bit for 9/7i dequantization

    24 juin 2015, par Michael Niedermayer
    avcodec/jpeg2000dec : Use 32x32->64bit for 9/7i dequantization
    

    Like the 5/3 case this is needed to avoid overflows and similarly for 16bpp
    output pure 32bit operations are insufficient if high quality is wanted

    Note, this code-path is only used in bitexact mode, so this should not
    affect the speed of any real use-case

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavcodec/jpeg2000dec.c