<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>API on James Montgomery</title>
    <link>https://ja.mesmontgomery.co.uk/categories/api/</link>
    <description>Recent content in API on James Montgomery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 13 Jan 2021 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ja.mesmontgomery.co.uk/categories/api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>API Diversions</title>
      <link>https://ja.mesmontgomery.co.uk/2021/01/api-diversions/</link>
      <pubDate>Wed, 13 Jan 2021 00:00:00 +0000</pubDate>
      <guid>https://ja.mesmontgomery.co.uk/2021/01/api-diversions/</guid>
      <description>TL; DR Recently reinvigorated with my new UI work, I set myself to task with simplifying the front end player code. No matter how I looked at it, I&amp;rsquo;d needed to rewrite the back end API to support a front end rewrite. But what if I didn&amp;rsquo;t precisely need to do that? Enter stage left, Cloudflare Workers.&#xA;Below I explain how I arrived at this. If you would like to view the Worker code, you can do so here.</description>
    </item>
    <item>
      <title>Introducing async to my serverless text-to-speech player for jokes and quotes</title>
      <link>https://ja.mesmontgomery.co.uk/2020/04/introducing-async-to-my-serverless-text-to-speech-player-for-jokes-and-quotes/</link>
      <pubDate>Thu, 30 Apr 2020 00:00:00 +0000</pubDate>
      <guid>https://ja.mesmontgomery.co.uk/2020/04/introducing-async-to-my-serverless-text-to-speech-player-for-jokes-and-quotes/</guid>
      <description>TL; DR In this post, I revisit my serverless &amp;ldquo;jokes and quotes&amp;rdquo; player. The purpose was to remove the tight coupling between the client request and audio playback API source. To explore the issue, I have introduced DynamoDB to store pre-generated results.&#xA;Challenge overview Logically, all the components of my existing solution depend on each other to succeed to deliver audio to the client. You can visualise it as follows:</description>
    </item>
    <item>
      <title>A Serverless text-to-speech player for jokes and quotes</title>
      <link>https://ja.mesmontgomery.co.uk/2020/03/a-serverless-text-to-speech-player-for-jokes-and-quotes/</link>
      <pubDate>Tue, 31 Mar 2020 00:00:00 +0000</pubDate>
      <guid>https://ja.mesmontgomery.co.uk/2020/03/a-serverless-text-to-speech-player-for-jokes-and-quotes/</guid>
      <description>TL; DR I decided to dust off my text-to-speech list, implementing a serverless solution delivering random jokes and quotes. You may visit it at this address:&#xA;https://tts-ja.mesmontgomery.co.uk/&#xA;You can get a preview of the joke quality here:&#xA;Your browser does not support the audio element.&#xA;Note: I can&amp;rsquo;t affect the humour quality 🤣.&#xA;Solution overview Upon visiting the page, an event triggers calls to the API routes for their relative jokes and quotes.</description>
    </item>
    <item>
      <title>TTS project update 1 - adding texture to my generated speech</title>
      <link>https://ja.mesmontgomery.co.uk/2019/03/tts-project-update-1-adding-texture-to-my-generated-speech/</link>
      <pubDate>Thu, 14 Mar 2019 00:00:00 +0000</pubDate>
      <guid>https://ja.mesmontgomery.co.uk/2019/03/tts-project-update-1-adding-texture-to-my-generated-speech/</guid>
      <description>TL; DR In this post, I&amp;rsquo;d like to share an update on work to address some of the limitations in my text to speech project for Elite Dangerous.. Namely:&#xA;Single voice is used for the synthesis; and Pitch, tone and emphasis are unchanged from defaults. If you&amp;rsquo;d like to see the result of the work so far, here is a brief overview video, I&amp;rsquo;ll describe how we got here below:</description>
    </item>
    <item>
      <title>Google Cloud Text-to-Speech with PowerShell</title>
      <link>https://ja.mesmontgomery.co.uk/2019/02/google-cloud-text-to-speech-with-powershell/</link>
      <pubDate>Sun, 10 Feb 2019 00:00:00 +0000</pubDate>
      <guid>https://ja.mesmontgomery.co.uk/2019/02/google-cloud-text-to-speech-with-powershell/</guid>
      <description>TL; DR In this post, I&amp;rsquo;ll walk through the basics of using PowerShell to interact with the Google Cloud Text-to-Speech API. Partly a documentation exercise and somewhat a guide I&amp;rsquo;d like to have been able to read when I started on my Elite Dangerous Google Cloud Text-to-Speech project.&#xA;As such, we&amp;rsquo;ll start with a basic script to produce an audio file and explain how that works. Later I&amp;rsquo;ll walk through some parameters of interest to affect the response.</description>
    </item>
    <item>
      <title>How to base64 decode on Windows 10 without base64.exe</title>
      <link>https://ja.mesmontgomery.co.uk/2019/01/how-to-base64-decode-on-windows-10-without-base64.exe/</link>
      <pubDate>Thu, 10 Jan 2019 00:00:00 +0000</pubDate>
      <guid>https://ja.mesmontgomery.co.uk/2019/01/how-to-base64-decode-on-windows-10-without-base64.exe/</guid>
      <description>TL;DR You can call certutil from PowerShell to produce the required file.&#xA;Introduction There is a moment in life where you get stuck in a quick start guide - we&amp;rsquo;ve all been there. At the start of my Google Cloud text-to-speech project it arrived quickly and unexpectedly at step two of this two-step quick start guide.&#xA;I had successfully returned my first base64 encoded speech audio, onward to the last step:</description>
    </item>
  </channel>
</rss>
