Recherche avancée

Médias (1)

Mot : - Tags -/university

Autres articles (44)

  • 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

  • Déploiements possibles

    31 janvier 2010, par

    Deux types de déploiements sont envisageable dépendant de deux aspects : La méthode d’installation envisagée (en standalone ou en ferme) ; Le nombre d’encodages journaliers et la fréquentation envisagés ;
    L’encodage de vidéos est un processus lourd consommant énormément de ressources système (CPU et RAM), il est nécessaire de prendre tout cela en considération. Ce système n’est donc possible que sur un ou plusieurs serveurs dédiés.
    Version mono serveur
    La version mono serveur consiste à n’utiliser qu’une (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (12706)

  • Using a Web-based installer to retrieve (not distribute) 3rd party GPL or non-free software

    25 août 2013, par user1493918

    I am developing a software product which is able to communicate over a command line interface with GPL-covered software (specifically, my software can feed commands to FFMpeg). I understand that a crucial aspect of the GPL license is whether or not you distribute GPL-covered applications. My goal is to allow my users to have a seamless experience installing both my software and 3rd party GPL software. But I am trying to do this without my software actually including the the 3rd party (GPL-covered) software. To do this I am considering Web-based installers. I could use a Web-based installer to allow the end-user the option to retrieve a GPL-covered or non-free software app from a totally different server, independent of my own and outside my control. The user would be the one to install the software simply by making a decision (i.e. pressing "Next" in my installer). If they chose to do so, then my software's Web-based installer would retrieve the 3rd-party software, decompress and install it, then move on to installing my own application. In this way, my installer doesn't ship any GPL-covered or non-free software, and yet from the user's perspective all they had to do is click Next... Next... Next... Done !

    I have read about the GPL allowing you to distribute GPL-covered apps as part of an "aggregate..."
    http://www.gnu.org/licenses/gpl-faq.html#MereAggregation

    ...but this scenario isn't that. It's allowing the user to retrieve applications or libraries at his own discretion, using his own bandwidth, downloading from a server that has nothing to do with me.

    I can't seem to find information anywhere about the GPL-related licensing implications of using a Web-based installer. My goal is simply to give the end user every high-quality transcoding option possible within FFMpeg without stepping on anybody's toes legally.

    Possible ? If so then I'm hoping someone might be able to point me to a software installer program that would facilitate this. Thank you in advance for any replies.

  • compiling ffmpeg and chromaprint for android with success on some devices

    4 août 2016, par D Liebman

    I am following the recommendations of this site :

    https://bitbucket.org/phorton1/chromaprint

    From the site I have copied the multi-configure and multi-make scripts for the ffmpeg and chromaprint libraries. I have used them with recent clones of ffmpeg 3.0 and chromaprint 1.3.2 . I get working ’.so’ files for arm, x86 and armv7. I don’t have compillation problems. I load them into my app (a very simple app just to test this library) and I try it on my two devices. One is a Samsung Galaxy TabPro (SM-T320, api 19), and one is the Samsung S4 (api 21). I get the program to run on both. I can use the ’-version’ command to get the chromaprint version info. When I try to fingerprint a audio file, the software works on the older tablet, but not on the s4. On the s4 the error message is ’error decoding audio’.

    I have tried ffmpeg 0.9 as the bitbucket site suggests. I have the same problem. I have tried ffmpeg 2.7 and I thought this was working. Now I cannot get 2.7 to work. As before the code works on the api 19 device and not the s4.

    The Tab is an armeabi-v7a device and the s4 is an armeabi/armeabi-v7 device, so I thought by removing the ’armeabi’ binary I would have the same file on both machines, and they would have to work. This attempt did nothing. I am using android studio.

    Below is a list of some of my ffmpeg configurations. They are taken from the multi-configure script.

       --enable-static
       --disable-shared
       --disable-doc
       --disable-txtpages
       --disable-iconv

       --enable-memalign-hack
       --enable-debug
       --disable-avdevice
       --disable-avfilter
       --disable-swscale
       --disable-ffmpeg
       --disable-ffplay
       --disable-ffserver
       --disable-network
       --disable-muxers
       --disable-demuxers
       --enable-rdft
       --enable-demuxer=aac
       --enable-demuxer=ac3
       --enable-demuxer=ape
       --enable-demuxer=asf
       --enable-demuxer=flac
       --enable-demuxer=matroska_audio
       --enable-demuxer=mp3
       --enable-demuxer=mpc
       --enable-demuxer=mov
       --enable-demuxer=mpc8
       --enable-demuxer=ogg
       --enable-demuxer=tta
       --enable-demuxer=wav
       --enable-demuxer=wv
       --disable-bsfs
       --disable-filters
       --disable-parsers
       --enable-parser=aac
       --enable-parser=ac3
       --enable-parser=mpegaudio
       --disable-protocols
       --enable-protocol=file
       --disable-indevs
       --disable-outdevs
       --disable-encoders
       --disable-decoders
       --enable-decoder=aac
       --enable-decoder=ac3
       --enable-decoder=alac
       --enable-decoder=ape
       --enable-decoder=flac
       --enable-decoder=mp1
       --enable-decoder=mp2
       --enable-decoder=mp3
       --enable-decoder=mpc7
       --enable-decoder=mpc8
       --enable-decoder=tta
       --enable-decoder=vorbis
       --enable-decoder=wavpack
       --enable-decoder=wmav1
       --enable-decoder=wmav2
       --enable-decoder=pcm_alaw
       --enable-decoder=pcm_dvd
       --enable-decoder=pcm_f32be
       --enable-decoder=pcm_f32le
       --enable-decoder=pcm_f64be
       --enable-decoder=pcm_f64le
       --enable-decoder=pcm_s16be
       --enable-decoder=pcm_s16le
       --enable-decoder=pcm_s16le_planar
       --enable-decoder=pcm_s24be
       --enable-decoder=pcm_daud
       --enable-decoder=pcm_s24le
       --enable-decoder=pcm_s32be
       --enable-decoder=pcm_s32le
       --enable-decoder=pcm_s8
       --enable-decoder=pcm_u16be
       --enable-decoder=pcm_u16le
       --enable-decoder=pcm_u24be
       --enable-decoder=pcm_u24le
       --enable-decoder=rawvideo

    Here is some information about the s4 that I got from a system info app.

    Build Info
       Build.BOARD: MSM8960
       Build.BRAND: Verizon
       Build.DEVICE: jfltevzw
       Build.DISPLAY: LRX22C.I545VRUGOF1
       Build.PRODUCT: jfltevzw
       Build.HARDWARE: qcom
       Build.FINGERPRINT: Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRUGOF1:user/release-keys
       Build.CPU_ABI: armeabi-v7a
       Build.SUPPORTED_32_BIT_ABIS: [armeabi-v7a, armeabi]
       Build.SUPPORTED_64_BIT_ABIS: []
       Build.SUPPORTED_ABIS: [armeabi-v7a, armeabi]
       Build.HOST: SWDD6122
       Build.ID: LRX22C
       Build.MANUFACTURER: samsung
       Build.MODEL: SCH-I545
       Build.PRODUCT: jfltevzw
       Build.TAGS: release-keys
       Build.TIME: 2015-07-15T03:39:01.000-0400
       Build.TYPE: user
       Build.USER: dpi
       Build.BOOTLOADER: I545VRUGOF1
       Build.TAGS: release-keys
       Build.VERSION.CODENAME: REL
       Build.VERSION.INCREMENTAL: I545VRUGOF1
       Build.VERSION.RELEASE: 5.0.1
       Build.VERSION.SDK_INT: 21

    EDIT :

    This is the complete source for my project minus the api-key which is personal. https://github.com/radiodee1/awesome-fpcalc The code is arranged in parts inside the git repository. The ’fpcalc-testapp’ part just has the Android Studio project. The ’fpcalc-build’ part is my attempt to use the latest versions of ffmpeg, chromaprint, and kissfft. The ’fpcalc-build-complete’ part is a series of scripts that reproduces the P. Horton ffmpeg 2.7 scenario. Bye the way I believe the best libraries are produced in the ’build-complete’ folders.

  • configure : Include the armcc build number in the compiler identification

    28 juillet 2014, par Martin Storsjö
    configure : Include the armcc build number in the compiler identification
    

    This tries to find the most expressive part of the output of
    armcc —vsn to include, giving a compiler identification of
    "ARM Compiler 5.04 update 2 (build 82)" instead of just
    "ARM Compiler 5.04" for armcc 5.0.

    4.x versions of armcc output the following, for "armcc —vsn" :
    ARM C/C++ Compiler, RVCT4.0 [Build 925]
    For evaluation purposes only
    Software supplied by : ARM Limited

    ARM C/C++ Compiler, 4.1 [Build 894]
    For evaluation purposes only
    Software supplied by : ARM Limited

    5.0 versions output this :
    Product : ARM Compiler 5.04
    Component : ARM Compiler 5.04 update 2 (build 82)
    Tool : armcc [5040081]
    For evaluation purposes only
    Software supplied by : ARM Limited

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DBH] configure