Recherche avancée

Médias (1)

Mot : - Tags -/biomaping

Autres articles (92)

  • L’utiliser, en parler, le critiquer

    10 avril 2011

    La première attitude à adopter est d’en parler, soit directement avec les personnes impliquées dans son développement, soit autour de vous pour convaincre de nouvelles personnes à l’utiliser.
    Plus la communauté sera nombreuse et plus les évolutions seront rapides ...
    Une liste de discussion est disponible pour tout échange entre utilisateurs.

  • Mediabox : ouvrir les images dans l’espace maximal pour l’utilisateur

    8 février 2011, par

    La visualisation des images est restreinte par la largeur accordée par le design du site (dépendant du thème utilisé). Elles sont donc visibles sous un format réduit. Afin de profiter de l’ensemble de la place disponible sur l’écran de l’utilisateur, il est possible d’ajouter une fonctionnalité d’affichage de l’image dans une boite multimedia apparaissant au dessus du reste du contenu.
    Pour ce faire il est nécessaire d’installer le plugin "Mediabox".
    Configuration de la boite multimédia
    Dès (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

Sur d’autres sites (11669)

  • Call for Speakers : Share Your Voice at MatomoCamp 2025 !

    10 juillet, par Alex Carmona

    MatomoCamp is back for its 2025 edition — and the Call for Speakers is now open until July 31st !

    As proud sponsors of this unique, community-driven event, we’re excited to invite experts, enthusiasts, and curious minds to contribute to MatomoCamp 2025, the annual online gathering dedicated to web analytics, open source, digital privacy, and of course — Matomo. MatomoCamp is the premier free online conference for the Matomo Analytics community in Europe, sponsored by Matomo Analytics. Taking place online on Wednesday 26 November 2025 from 9:30 AM to 5:30 PM CET, this event brings together professionals passionate about ethical analytics, data privacy, and building a better web.

    Whether you’re a long-time user, developer, marketer, researcher, or just someone with a fresh perspective on ethical analytics, your voice belongs at MatomoCamp. Last year, we welcomed over 1,000 attendees from around the world. This year, we’re aiming even higher with an expanded programme designed to serve everyone from analytics beginners to enterprise architects.

    What is MatomoCamp ?

    MatomoCamp is a free, fully online event bringing together the global Matomo community. Across two days of talks, panels, demos, and workshops, participants explore :

    • Web analytics & measurement
    • Digital marketing & SEO
    • Open source projects & collaboration
    • Privacy-first data strategies
    • Case studies, experiments, and more

    With sessions in English, French, German, and beyond, MatomoCamp aims to make digital analytics more accessible, ethical, and transparent for everyone.

    MatomoCamp returns this November 2025 with an exciting new vision. For the first time, we’re expanding beyond purely technical content to welcome speakers from all backgrounds who can contribute insights on analytics, privacy, marketing, and the ethical web. Whether you’re a developer, marketer, analyst, or privacy advocate, we want to hear from you.

    Who can apply ?

    Anyone ! We’re looking for people from all backgrounds who want to share :

    • A practical tip or use case with Matomo
    • Insights into digital analytics, privacy, or open source
    • A success (or failure !) story from your own journey
    • A workshop or hands-on demonstration
    • A bold opinion on the future of web data
    • A behind-the-scenes look at your work or research

    You don’t have to be a professional speaker. We welcome first-time speakers, underrepresented voices, and community members who want to share something valuable — no matter how niche or broad.

    What makes a great talk ?

    There’s no one right formula. But here’s what works well :

    • Real-world experience
    • Specific, actionable insights
    • A clear structure (15–45 minutes)
    • Something you care deeply about
    • A story only you can tell

    And remember — this isn’t just about Matomo. Topics that touch on ethical analytics, open source values, or digital sovereignty are more than welcome.

    Key info

    • Where : Online (free & open to all)
    • When : November 2025 (exact dates to be announced)
    • Languages : English, French, German (other languages welcome !)
    • Deadline to apply : July 31, 2025
    • Submit your talk here

    Why does this matter ?

    At Matomo, we believe that data should empower, not exploit. MatomoCamp is more than just an event — it’s a celebration of what’s possible when communities come together to build a better digital future.

    As sponsors, we’re proud to support this independent, open source event. But more importantly, we want to amplify your voice — because every perspective shared brings us closer to a more ethical, transparent, and inclusive analytics ecosystem.

    Have a story to share ?

    Don’t overthink it. If it matters to you, it will matter to someone else. Apply to speak before July 31st and join us at MatomoCamp 2025 !

    Submit your session here !

    Let’s build the future of analytics — together.

    call for speaker matomocamp 2025
  • 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.

  • Zipping Conda Environment Breaks Audioread's Backend (Python/Pyspark)

    25 octobre 2017, par Tim

    I have previously build pyspark environments using conda to package all dependancies and ship them to all the nodes at runtime. Here’s how I create the environment :

    `conda/bin/conda create -p conda_env --copy -y python=2  \
    numpy scipy ffmpeg gcc libsndfile gstreamer pygobject audioread librosa`

    `zip -r conda_env.zip conda_env`

    Then sourcing conda_env and running pyspark shell I can successfully execute :

    `import librosa
    y, sr = librosa.load("test.m4a")`

    Note without the environment sourced this script results in an error as ffmpeg/gstreamer are NOT installed on my locally.

    Submitting a script to the cluster results in a librosa.load error which traces back to audioread indicating the backend (either gstreamer or ffmpeg) can no longer be found in the zipped archive environment. The stacktrace is below :

    Submit :

    `PYSPARK_PYTHON=./NODE/conda_env/bin/python spark-submit --verbose \
           --conf spark.yarn.appMasterEnv.PYSPARK_PYTHON=./NODE/conda_env/bin/python \
           --conf spark.yarn.appMasterEnv.PYTHON_EGG_CACHE=/tmp \
           --conf spark.executorEnv.PYTHON_EGG_CACHE=/tmp \
           --conf spark.yarn.executor.memoryOverhead=1024 \
           --conf spark.hadoop.validateOutputSpecs=false \
           --conf spark.driver.cores=5 \
           --conf spark.driver.maxResultSize=0 \
           --master yarn --deploy-mode cluster --queue production \
           --num-executors 20 --executor-cores 5 --executor-memory 40G \
           --driver-memory 20G --archives conda_env.zip#NODE \
           --jars /data/environments/sqljdbc41.jar \
           script.py`

    Trace :

    `Caused by: org.apache.spark.api.python.PythonException: Traceback (most recent call last):
     File "/mnt/yarn/usercache/user/appcache/application_1506634200253_39889/container_1506634200253_39889_01_000003/pyspark.zip/pyspark/worker.py", line 172, in main
       process()
     File "/mnt/yarn/usercache/user/appcache/application_1506634200253_39889/container_1506634200253_39889_01_000003/pyspark.zip/pyspark/worker.py", line 167, in process
       serializer.dump_stream(func(split_index, iterator), outfile)
     File "/mnt/yarn/usercache/user/appcache/application_1506634200253_39889/container_1506634200253_39889_01_000003/pyspark.zip/pyspark/serializers.py", line 263, in dump_stream
       vs = list(itertools.islice(iterator, batch))
     File "script.py", line 245, in <lambda>
     File "script.py", line 119, in download_audio
     File "/mnt/yarn/usercache/user/appcache/application_1506634200253_39889/container_1506634200253_39889_01_000003/NODE/conda_env/lib/python2.7/site-packages/librosa/core/audio.py", line 107, in load
       with audioread.audio_open(os.path.realpath(path)) as input_file:
     File "/mnt/yarn/usercache/user/appcache/application_1506634200253_39889/container_1506634200253_39889_01_000003/NODE/conda_env/lib/python2.7/site-packages/audioread/__init__.py", line 114, in audio_open
       raise NoBackendError()
    NoBackendError`
    </lambda>

    My question is : How can I package this archive so that librosa (really audioread) is able to find the backend and load .m4a files ?