<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Audio.phoni.es</title>
    <link>/dev/</link>
    <description>Recent content on Audio.phoni.es</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>dev</language>
    <lastBuildDate>Tue, 25 Jul 2023 08:12:30 +1000</lastBuildDate><atom:link href="/dev/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Step 1 : Testing archive.org audio player</title>
      <link>/dev/doc/v1/</link>
      <pubDate>Thu, 03 May 2018 20:12:30 +1000</pubDate>
      
      <guid>/dev/doc/v1/</guid>
      <description>Archive.org provides embedded player
Demo: Source code: &amp;lt;iframe src=&amp;quot;https://archive.org/embed/chmob&amp;amp;playlist=1&amp;quot; width=&amp;quot;100%&amp;quot; height=&amp;quot;300&amp;quot; frameborder=&amp;quot;0&amp;quot; webkitallowfullscreen=&amp;quot;true&amp;quot; mozallowfullscreen=&amp;quot;true&amp;quot; allowfullscreen&amp;gt;&amp;lt;/iframe&amp;gt;j Positive:
shows all audio files in a single player play all responsive can be open in a dedicated window: https://archive.org/embed/chmob&amp;playlist=1# Negative:
heavy: 1.4 Mo JS + 100 Ko CSS iframe (security, compatibility, no CSS customization) requires to enable Hugo&amp;rsquo;s HTML in Markdown (with markup: &#39;unsafe&#39;) inject (minimal) analytics from archive.org no comments on files </description>
    </item>
    
    <item>
      <title>Embed media files from archive.org</title>
      <link>/doc/media/</link>
      <pubDate>Thu, 03 May 2018 20:12:30 +1000</pubDate>
      
      <guid>/doc/media/</guid>
      <description>Table of content Embed a single audio file Embed multiple audio files Embed a video file Embed a single audio file Usage: {{&amp;lt; audio &amp;quot;https://archive.org/download/foo/bar.mp3&amp;quot; &amp;gt;}} Demo: Main features supports WAV, FLAC, OGG, MP3, M4A based on standard HTML element does not require Javascript supports remote audio files provides a download link nice UI, lightweight: 180 Ko keyboard navigation Caveats allows to embed only a single file at a time.</description>
    </item>
    
    <item>
      <title>Step 2 : Embed individual audio file from archive.org</title>
      <link>/dev/doc/v2/</link>
      <pubDate>Thu, 03 May 2018 20:12:30 +1000</pubDate>
      
      <guid>/dev/doc/v2/</guid>
      <description>See /media
Demo:
Usage:
{{&amp;lt; audio &amp;quot;https://archive.org/download/foo/bar.mp3&amp;quot; &amp;gt;}} Details Pros based on standard HTML element supports WAV, FLAC, OGG, MP3, M4A does not require Javascript supports remote audio files provides a download link nice UI, lightweight: 140 Ko keyboard navigation Cons allows to embed only a single file at a time References Documentation Source code Issue tracker </description>
    </item>
    
    <item>
      <title>Notes about Derivatives generation</title>
      <link>/dev/derivatives/</link>
      <pubDate>Sun, 03 May 2020 20:12:30 +1000</pubDate>
      
      <guid>/dev/derivatives/</guid>
      <description>Notes The data is fetched and updated at each build. Folders modified/updated on archive.org = data updated on Phoni.es
Let&amp;rsquo;s see if this slows down the build on the long run
A bunch of special files need time to be generated by archive.org (metadata files, derivative/converted files, OCR).
Unfortunately, Archive.org does not provide a notification/webhook to trigger a new build when this generation is done.
To investigate:
a detailed API to list pending &amp;ldquo;Tasks&amp;rdquo; is available a field &amp;ldquo;pending_tasks: true&amp;rdquo; is displayed in the JSON file the CLI provides ia tasks foo-bar | yq A note about the metadata formats: When files are uploaded to Archive.</description>
    </item>
    
    <item>
      <title>Step 3 : Load data from local JSON files</title>
      <link>/dev/doc/v3/</link>
      <pubDate>Thu, 03 May 2018 20:12:30 +1000</pubDate>
      
      <guid>/dev/doc/v3/</guid>
      <description>As explained in Hugo Documentation, JSON files are downloaded in /data/audio/ and fetched with
{{ range $.Site.Data.audio }} &amp;lt;ul&amp;gt; {{ range .files }} &amp;lt;li&amp;gt;{{ index .name | markdownify }}&amp;lt;/li&amp;gt; {{ end }} &amp;lt;/ul&amp;gt; {{ end }} (The related layout file is layouts/fetchLocal/single.html)
Drawbacks JSON files must be downloaded manually Synchronisation between local JSON files and updated folders on archive.org will be a pain </description>
    </item>
    
  </channel>
</rss>
