Recherche avancée

Médias (0)

Mot : - Tags -/signalement

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

Autres articles (40)

  • ANNEXE : Les extensions, plugins SPIP des canaux

    11 février 2010, par

    Un plugin est un ajout fonctionnel au noyau principal de SPIP. MediaSPIP consiste en un choix délibéré de plugins existant ou pas auparavant dans la communauté SPIP, qui ont pour certains nécessité soit leur création de A à Z, soit des ajouts de fonctionnalités.
    Les extensions que MediaSPIP nécessite pour fonctionner
    Depuis la version 2.1.0, SPIP permet d’ajouter des plugins dans le répertoire extensions/.
    Les "extensions" ne sont ni plus ni moins que des plugins dont la particularité est qu’ils se (...)

  • Changer son thème graphique

    22 février 2011, par

    Le thème graphique ne touche pas à la disposition à proprement dite des éléments dans la page. Il ne fait que modifier l’apparence des éléments.
    Le placement peut être modifié effectivement, mais cette modification n’est que visuelle et non pas au niveau de la représentation sémantique de la page.
    Modifier le thème graphique utilisé
    Pour modifier le thème graphique utilisé, il est nécessaire que le plugin zen-garden soit activé sur le site.
    Il suffit ensuite de se rendre dans l’espace de configuration du (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

Sur d’autres sites (5030)

  • Evolution of Multimedia Fiefdoms

    1er octobre 2014, par Multimedia Mike — General

    I want to examine how multimedia fiefdoms have risen and fallen through the years.


    Medieval Castle

    Back in the day, the multimedia fiefdoms were built around the formats put forth by competing companies : there was Microsoft/WMV, Apple/MOV, and Real/RM as the big contenders. On2 always wanted to be a player in this arena but could never quite catch a break. A few brave contenders held the line for open source and also for the power users who desired one application that could handle everything (my original motivation for wanting to get into multimedia hacking).

    The computer desktop was the battleground for internet-based media stream. Whatever happened to those days ? Actually, if memory serves, Flash-based video streaming stepped on all of them.

    Over the last 6-7 years, the battleground has expanded to cover mobile devices, where Flash’s impact has… lessened. During this time, multimedia technology pretty well standardized on a particular stack, namely, the MPEG (MP4/H.264/AAC) stack.

    The belligerents in this war tried for years to effectively penetrate new territory, namely, the living room where the television lived. This had been slowgoing for years due to various user interface and content issues, but steadily improved.

    Last April, Amazon announced their entry into the set-top box market with the Fire TV. That was when it suddenly crystallized for me that the multimedia ecosystem has radically shifted. Now, the multimedia fiefdoms revolve around access to content via streaming services.

    Off the top of my head, here are some of the fiefdoms these days (fiefdoms I have experience using) :

    • Netflix (subscription streaming)
    • Amazon (subscription, rental, and purchased streaming)
    • Hulu Plus (subscription streaming)
    • Apple (rental and purchased media)

    I checked some results on Can I Stream.It ? (which I refer to often) and found a bunch more streaming fiefdoms such as Google (both Play and YouTube, which are separate services), Sony, Xbox 360, Crackle, Redbox Instant, Vudu, Target Ticket, Epix, Sony, SnagFilms, and XFINITY StreamPix. And surely, these are probably just services available in the United States ; I know other geographical regions have their own fiefdoms.

    What happened ?

    When I got into multimedia hacking, there were all these disparate, competing ecosystems. As a consumer, I didn’t care where the media came from, I just wanted to play it. That’s what inspired me to work on open source multimedia projects. Now I realize that I have the same problem 10-15 years later : there are multiple competing ecosystems. I might subscribe to fiefdoms X and Y, but am frustrated to learn that something I’d like to watch is only available through fiefdom Z. Very few of these fiefdoms can be penetrated using open source technology.

    I’m not really sure about the point about this whole post. Multimedia technology seems really standardized these days. But that’s probably just my perspective because I have spent way too long focusing on a few areas of multimedia technology such as audio and video coding. It’s interesting that all these services probably leverage the same limited number of codecs. Their differentiation comes from the catalog of content that each is able to license for streaming. There are different problems to solve in the multimedia arena now.

  • Back on the Salty Track

    12 juin 2011, par Multimedia Mike — General

    After I posted about my initial encounter and frustration with Google’s Native Client (NaCl) SDK and took a deep breath, I realized that I achieved an important proof of concept— I successfully played music using the NaCl SDK audio output interface. Then I started taking a closer read through the (C-based set of) header files and realized I might be able to make a go of it after all. I had much better luck this time and managed to create a proper Native Client interface that allows for controlling playback, presenting metadata, and toggling individual voices (a fascinating tool for studying classic game music).

    I haven’t bothered to post the actual plugin because, really, what’s the point ? I started with NaCl SDK 0.3 which requires Chrome 12, which means terribly limited reach, even among Chrome users. At least, that was true when I restarted this little project. Chrome 12 was formally released this past week. Chrome development really does move at breakneck pace.

    Anyway, here is a static screenshot of what the plugin currently looks like :



    Not pretty, but it does the job.

    Dev Journal
    Various notes based on this outing :

    • Portability : I tested my plugin using Chrome 12 on 64-bit Windows, Mac, and Linux. Mac and Linux both work ; Windows does not.
    • Build System : SDK 0.3 is still lacking in its ability to compile .cpp files (instead of .cc files) ; necessary because libgme is C++ using .cpp files. This requires some build system modification.
    • Getting the interfaces : This is where I got tripped up the first time around. get_browser_interface() from their example actually refers to a parameter passed in through the PPP_InitializeModule() function. The SDK’s template generator renames this to get_browser().
    • Debugging : I feel unstoppable once I have a printf() mechanism available to me during development. To that end, console.log() from JavaScript outputs to Chrome’s built-in JavaScript console log while putting printf() statements in the actual NaCl plugin causes the messages to show up in /.xsession-errors on Linux/X.
    • Size Matters : The binaries generated with the NaCl 0.3 SDK are ridiculously huge. The basic "Hello World" example in C compiles to binaries that are 6.7 MB and 7.8 MB for the 32- and 64-bit builds, respectively. This made me apprehensive to build a full version of SaltyGME that contains all the bells and whistles offered by the library. However, all of the GME code compiled into the binary adds very little size. Curiously, the C++ version of "Hello World" only ranges from 1.8-2.0 MB for 32- and 64-bit. Is there some kind of C tax happening here ? Note that running ’strip’ on the resulting .nexe files (they’re ELF files, after all) brings the sizes down into the C++ range, but at the cost of causing them to not work (more specifically, not even load).
    • No Messaging : The NaCl SDK is supposed to have a messaging interface which allows the NaCl plugin to send asynchronous messages up to the hosting page. When I try to instantiate it, I get a NULL. I’m stuck with the alternative of polling from the JavaScript side to, e.g., determine when a song has finished loading via the network.

    That’s all I can think of for now. I may work on this a little more (I’d like to at least see some audio visualization). Maybe Google will enable NaCl per default sometime around Chrome 21 and this program will be ready for prime time by then.

    See Also :

  • ffmpeg version conflict with other packages

    9 janvier, par susanna

    I use rpmbuild on kylin OS which is kind of linux system. The strange error message is attached below. Based on my limited knowledge, I do not know the root cause. Can you provide some suggestions ? Thanks.

    


    Requires(interp): /bin/sh
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires(post): /bin/sh
Requires: /bin/bash /bin/sh /usr/bin/bash ld-linux-x86-64.so.2()(64bit) ld-linux-x86-64.so.2(GLIBC_2.3)(64bit) libGL.so.1()(64bit) libX11.so.6()(64bit) libXext.so.6()(64bit) libXi.so.6()(64bit) libXrender.so.1()(64bit) libXtst.so.6()(64bit) libXxf86vm.so.1()(64bit) libasound.so.2()(64bit) libasound.so.2(ALSA_0.9)(64bit) libasound.so.2(ALSA_0.9.0rc4)(64bit) libatk-1.0.so.0()(64bit) libavcodec-ffmpeg.so.56()(64bit) libavcodec-ffmpeg.so.56(LIBAVCODEC_FFMPEG_56)(64bit) libavcodec.so.53()(64bit) libavcodec.so.53(LIBAVCODEC_53)(64bit) libavcodec.so.54()(64bit) libavcodec.so.54(LIBAVCODEC_54)(64bit) libavcodec.so.55()(64bit) libavcodec.so.55(LIBAVCODEC_55)(64bit) libavcodec.so.56()(64bit) libavcodec.so.56(LIBAVCODEC_56)(64bit) libavcodec.so.57()(64bit) libavcodec.so.57(LIBAVCODEC_57)(64bit) libavformat-ffmpeg.so.56()(64bit) libavformat-ffmpeg.so.56(LIBAVFORMAT_FFMPEG_56)(64bit) libavformat.so.53()(64bit) libavformat.so.53(LIBAVFORMAT_53)(64bit) libavformat.so.54()(64bit) libavformat.so.54(LIBAVFORMAT_54)(64bit) libavformat.so.55()(64bit) libavformat.so.55(LIBAVFORMAT_55)(64bit) libavformat.so.56()(64bit) libavformat.so.56(LIBAVFORMAT_56)(64bit) libavformat.so.57()(64bit) libavformat.so.57(LIBAVFORMAT_57)(64bit) libawt.so()(64bit) libawt_xawt.so()(64bit) libawt_xawt.so(SUNWprivate_1.1)(64bit) libc.so.6()(64bit) libc.so.6(GLIBC_2.10)(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.17)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.27)(64bit) libc.so.6(GLIBC_2.28)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.3.2)(64bit) libc.so.6(GLIBC_2.3.3)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.6)(64bit) libc.so.6(GLIBC_2.7)(64bit) libc.so.6(GLIBC_2.9)(64bit) libcairo-gobject.so.2()(64bit) libcairo.so.2()(64bit) libcrypt.so.1()(64bit) libcrypt.so.1(XCRYPT_2.0)(64bit) libcrypto.so.1.1()(64bit) libcrypto.so.1.1(OPENSSL_1_1_0)(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libexslt.so.0()(64bit) libfontconfig.so.1()(64bit) libfontmanager.so()(64bit) libfontmanager.so(SUNWprivate_1.1)(64bit) libfreetype.so.6()(64bit) libgcc_s.so.1()(64bit) libgcc_s.so.1(GCC_3.0)(64bit) libgcc_s.so.1(GCC_3.3)(64bit) libgcc_s.so.1(GCC_4.2.0)(64bit) libgd.so.3()(64bit) libgdk-3.so.0()(64bit) libgdk-x11-2.0.so.0()(64bit) libgdk_pixbuf-2.0.so.0()(64bit) libgio-2.0.so.0()(64bit) libglib-2.0.so.0()(64bit) libglib-lite.so()(64bit) libgobject-2.0.so.0()(64bit) libgstreamer-lite.so()(64bit) libgthread-2.0.so.0()(64bit) libgtk-3.so.0()(64bit) libgtk-x11-2.0.so.0()(64bit) libjava.so()(64bit) libjava.so(SUNWprivate_1.1)(64bit) libjli.so()(64bit) libjli.so(SUNWprivate_1.1)(64bit) libjvm.so()(64bit) libjvm.so(SUNWprivate_1.1)(64bit) libm.so.6()(64bit) libm.so.6(GLIBC_2.2.5)(64bit) libnet.so()(64bit) libnet.so(SUNWprivate_1.1)(64bit) libnio.so()(64bit) libnio.so(SUNWprivate_1.1)(64bit) libnsl.so.1()(64bit) libpango-1.0.so.0()(64bit) libpangocairo-1.0.so.0()(64bit) libpangoft2-1.0.so.0()(64bit) libpcre2-8.so.0()(64bit) libperl.so.5.28()(64bit) libprofiler.so.0()(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.12)(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) libpthread.so.0(GLIBC_2.3.2)(64bit) libpthread.so.0(GLIBC_2.3.3)(64bit) librt.so.1()(64bit) librt.so.1(GLIBC_2.2.5)(64bit) libssl.so.1.1()(64bit) libssl.so.1.1(OPENSSL_1_1_0)(64bit) libssl.so.1.1(OPENSSL_1_1_1)(64bit) libstdc++.so.6()(64bit) libstdc++.so.6(CXXABI_1.3)(64bit) libstdc++.so.6(GLIBCXX_3.4)(64bit) libstdc++.so.6(GLIBCXX_3.4.11)(64bit) libstdc++.so.6(GLIBCXX_3.4.9)(64bit) libsystemd.so.0()(64bit) libsystemd.so.0(LIBSYSTEMD_209)(64bit) libthread_db.so.1()(64bit) libthread_db.so.1(GLIBC_2.2.5)(64bit) libutil.so.1()(64bit) libverify.so()(64bit) libverify.so(SUNWprivate_1.1)(64bit) libxml2.so.2()(64bit) libxml2.so.2(LIBXML2_2.4.30)(64bit) libxml2.so.2(LIBXML2_2.6.0)(64bit) libxslt.so.1()(64bit) libxslt.so.1(LIBXML2_1.0.11)(64bit) libxslt.so.1(LIBXML2_1.0.18)(64bit) libz.so.1()(64bit) rtld(GNU_HASH)


    


    When I run the installation rpm command, the installation completed successfully.
rpm -ivh myrpm-1.0.1.rpm --nodeps --force

    


    When I run the installation command, I receive this error.
rpm -ivh myrpm-1.0.1.rpm,

    


    [root@localhost ~]# rpm -ivh myrpm-1.0-1.ky10.x86_64.rpm 
Failure:
    java>=8  mosaic-web-1.0-1.ky10.x86_64 needed
    libavcodec-ffmpeg.so.56()(64bit)  myrpm-1.0-1.ky10.x86_64 needed
    libavcodec-ffmpeg.so.56(LIBAVCODEC_FFMPEG_56)(64bit) is mosaic-web-1.0-1.ky10.x86_64 needed
    libavcodec.so.53()(64bit) myrpm-1.ky10.x86_64 needed
    libavcodec.so.53(LIBAVCODEC_53)(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavcodec.so.54()(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavcodec.so.54(LIBAVCODEC_54)(64bit) is mosaic-web-1.0-1.ky10.x86_64 needed
    libavcodec.so.55()(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavcodec.so.55(LIBAVCODEC_55)(64bit) is myrpm-1.ky10.x86_64 needed
    libavcodec.so.56()(64bit) is myrpm-1.ky10.x86_64 needed
    libavcodec.so.56(LIBAVCODEC_56)(64bit) is yrpm-1.ky10.x86_64 needed
    libavcodec.so.57()(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavcodec.so.57(LIBAVCODEC_57)(64bit) is myrpm-1.ky10.x86_64 needed
    libavformat-ffmpeg.so.56()(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavformat-ffmpeg.so.56(LIBAVFORMAT_FFMPEG_56)(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavformat.so.53()(64bit) is myrpm-web-1.0-1.ky10.x86_64 needed
    libavformat.so.53(LIBAVFORMAT_53)(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavformat.so.54()(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavformat.so.54(LIBAVFORMAT_54)(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavformat.so.55()(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavformat.so.55(LIBAVFORMAT_55)(64bit) is  myrpm-1.0-1.ky10.x86_64 needed
    libavformat.so.56()(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavformat.so.56(LIBAVFORMAT_56)(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavformat.so.57()(64bit) is myrpm-1.0-1.ky10.x86_64 needed
    libavformat.so.57(LIBAVFORMAT_57)(64bit) is myrpm-1.0-1.ky10.x86_64 needed