
Recherche avancée
Autres articles (52)
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
Mise à disposition des fichiers
14 avril 2011, parPar défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...) -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)
Sur d’autres sites (8743)
-
JavaCV on Android with ARMv6
26 février 2014, par xoidbergI got problems getting JavaCV (http://code.google.com/p/javacv/) to run on my Samsung Galaxy S5570i device. According to this site http://www.gsmarena.com/samsung_galaxy_pop_plus_s5570i-4544.php this device has an ARMv6 CPU. I tried several deprecated versions of JavaCV that still include builds for ARMv5, because I had problems building it on my own. None of this versions worked on my device. I also tried running this on a virtual device which should simulate ARMv5 as long as I know. I always get exceptions that libraries couldn't be found, e.g. : "Caused by : java.lang.UnsatisfiedLinkError : Cannot load library : reloc_library[1312] : 1306 cannot locate '_ZNK2cv6KDTree14findOrthoRangeERKNS_11_InputArrayES3_RKNS_12_OutputArrayES6_S6_'.
I know that it is not recommended to use JavaCV on ARMv5 or ARMv6 CPUs, but I want to implement a feature in my app and provide it also for older CPUs, even if it's slower than on newer ones.
So what could be the problem ? Did I use wrong versions or what versions should I use ?
Hope to get an answer here.Thanks in advance !
xoidberg
-
compiling ffmpeg and chromaprint for android with success on some devices
4 août 2016, par D LiebmanI am following the recommendations of this site :
https://bitbucket.org/phorton1/chromaprint
From the site I have copied the
multi-configure
andmulti-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=rawvideoHere 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: 21EDIT :
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.
-
tests/ffserver.regression.ref : update ffserver checksums
28 novembre 2016, par Michael Niedermayer