From 92a9b605581e309a925bd43d52030b2df5a89043 Mon Sep 17 00:00:00 2001
From: Eryn Wells <eryn@erynwells.me>
Date: Fri, 21 Oct 2022 11:07:45 -0700
Subject: [PATCH] P5.js post: Wrap all the code blocks in figure shortcodes and
 fix the railroad diagrams

---
 .../2022/08/audio-scope-with-p5js/index.md    | 29 ++++++++++++++-----
 1 file changed, 21 insertions(+), 8 deletions(-)

diff --git a/content/blog/2022/08/audio-scope-with-p5js/index.md b/content/blog/2022/08/audio-scope-with-p5js/index.md
index c8928d6..142398b 100644
--- a/content/blog/2022/08/audio-scope-with-p5js/index.md
+++ b/content/blog/2022/08/audio-scope-with-p5js/index.md
@@ -23,11 +23,13 @@ visualizations. By the end, we'll have something like this:
 HTML has the ability to [embed audio][mdn-audio-tag] in a page with the
 `<audio>` tag. This one declares a single MP3 file as a source.
 
+{{< figures/code >}}
 ```html
 <audio id="amen">
     <source src="amen.mp3" type="audio/mpeg">
 </audio>
 ```
+{{< /figures/code >}}
 
 In this form, the `<audio>` element doesn't do anything except declare some
 audio that can be played. It's invisible and the user can't interact with it or
@@ -47,6 +49,7 @@ destinations could be your computer's speakers or a file.
 Here's the entire code snippet that sets up the audio processing I need for the
 sketch:
 
+{{< figures/code >}}
 ```js {linenostart=2}
 let analyzerNode = null;
 let samples = null;
@@ -67,6 +70,7 @@ let audioContext = (() => {
     return audioContext;
 })();
 ```
+{{< /figures/code >}}
 
 The [`AudioContext`][mdn-audio-context] is the object that encapsulates the
 entire node graph. On line 10, I create a new `AudioContext`.
@@ -85,19 +89,20 @@ the audio context's `destination` node that routes to the computer's speakers.
 Our audio processing graph looks like this:
 
 {{< figures/railroad id="audioContextDiagram" >}}
-    return rr.Diagram(
-        rr.Sequence(
-            rr.Terminal("<audio>"),
-            rr.Terminal("Analyzer"),
-            rr.Terminal("destination")));
-{{< /figures/railroad >}}
-
-{{< figures/railroad id="audioContextDiagram" class="narrow-only" >}}
+    {{< scripts/railroad >}}
+        return rr.Diagram(
+            rr.Sequence(
+                rr.Terminal("<audio>"),
+                rr.Terminal("Analyzer"),
+                rr.Terminal("destination")));
+    {{< /scripts/railroad >}}
+    {{< scripts/railroad narrow=1 >}}
     return rr.Diagram(
         rr.Stack(
             rr.Terminal("<audio>"),
             rr.Terminal("Analyzer"),
             rr.Terminal("destination")));
+    {{< /scripts/railroad >}}
 {{< /figures/railroad >}}
 
 By itself the AudioContext doesn't actually play any audio. I'll tackle that
@@ -109,6 +114,7 @@ Next up is starting playback. The following snippet creates a Play button using
 P5.js's DOM manipulation API, and hooks up the button's `click` event to start
 and stop playback.
 
+{{< figures/code >}}
 ```js {linenostart=29}
 const playPauseButton = p.createButton('Play');
 playPauseButton.position(10, 10);
@@ -131,6 +137,7 @@ playPauseButtonElement.addEventListener('click', function() {
     }
 });
 ```
+{{< /figures/code >}}
 
 Something I found odd while working with these audio components is there isn't a
 way to ask any of them if audio is playing back at any given moment. Instead it
@@ -147,12 +154,14 @@ The last bit of playback state tracking to do is to listen for when playback
 ends because it reached the end of the audio file. I did that with the `ended`
 event:
 
+{{< figures/code >}}
 ```js {linenostart=53}
 audioElement.addEventListener('ended', function() {
     playPauseButtonElement.dataset.playing = 'false';
     playPauseButtonElement.innerHTML = '<span>Play</span>';
 }, false);
 ```
+{{< /figures/code >}}
 
 This handler resets the `playing` flag and the label of the button.
 
@@ -160,6 +169,7 @@ This handler resets the `playing` flag and the label of the button.
 
 Now it's time to draw some waveforms! The main part of a P5 sketch is the `draw` method. Here's mine:
 
+{{< figures/code >}}
 ```js {linenostart=57}
 const amplitude = p.height / 2;
 const axis = p.height / 2;
@@ -184,12 +194,15 @@ for (let i = 0; i < samples.length; i++) {
     p.point(i, axis + amplitude * sampleValue);
 }
 ```
+{{< /figures/code >}}
 
 The most interesting part of this function starts at line 66 where we get an array of samples from the analyzer node. The `samples` variable is a JavaScript `Float32Array`, with one element for each pixel of width.
 
+{{< figures/code >}}
 ```js {linenostart=30}
 samples = new Float32Array(p.width);
 ```
+{{< /figures/code >}}
 
 Once the sample data is populated from the analyzer, we can render them by
 plotting them along the X axis, scaling them to the height of the sketch.