@gentbajko/slopify 3.0.6 → 3.0.8

package/dist/slices/rebuild/runtime-subtitles.js

@@ -16,6 +16,7 @@ import { speakerColour } from "../voices/palette.js";
 import { speakerPanelEvents, usesSpeakerPanel } from "../voices/panel.js";
 import { panelPortraits } from "../voices/portraits.js";
 import { attributeWords } from "../voices/timing.js";
+import { narrationRetryLimit, requestNarrationRetry } from "./narration-retry.js";
 import { exportSnapshot, retainedOutput, revisionAudio, revisionTranscript, revisionTurns, } from "./runtime-export-inputs.js";
 import { narrationChunks, narrationTextParts, } from "./runtime-narration-text.js";
 import { preparedResult, preparedText, publishResult } from "./runtime-publication.js";
@@ -77,7 +78,7 @@ async function timing(deps, context, piece, snapshot) {
         context.signal.throwIfAborted();
         const { path, kind } = segment;
         if (path !== null && spoken(kind)) {
-            const aligned = await located(snapshot, kind, () => alignSubtitles({
+            const aligned = await located(deps, context, snapshot, kind, () => alignSubtitles({
                 audioPath: path,
                 text: revisionTranscript(deps, snapshot, kind),
                 aliases: narrationAliasesOf(snapshot.view.revision.config),
@@ -250,45 +251,86 @@ async function files(deps, context, piece, snapshot) {
 }
 // A mismatch names the place to fix: the time in the narration, the chunk that holds it (as
 // the Narration editor numbers them) and what was expected against what was heard. The
-// usual cause is a TTS request that skipped or reworded a sentence.
-async function located(snapshot, segment, align) {
+// usual cause is a TTS request that skipped or reworded a sentence, which a second request
+// almost always reads right, so a chunk made by a voice is first recorded again by itself
+// (`narration-retry.ts`); the message says so, and says when its tries are used up.
+async function located(deps, context, snapshot, segment, align) {
     try {
         return await align();
     }
     catch (error) {
         if (!(error instanceof SubtitleMismatch))
             throw error;
-        throw new Error(mismatchMessage(snapshot, segment, error), { cause: error });
+        const chunks = mismatchChunks(snapshot, segment);
+        const at = mismatchChunk(chunks, error);
+        const chunk = at === -1 ? undefined : chunks[at];
+        const retry = chunk !== undefined && retryable(snapshot, chunk.key)
+            ? {
+                chunk: at + 1,
+                try: requestNarrationRetry(deps.db, {
+                    projectId: context.work.projectId,
+                    chunkKey: chunk.key,
+                    now: deps.clock.now().toISOString(),
+                }),
+            }
+            : undefined;
+        throw new Error(describeMismatch(chunks, segment, error, retry), { cause: error });
     }
 }
-export function mismatchMessage(snapshot, segment, mismatch) {
-    let chunks = [];
+// A chunk a voice made from the text: not uploaded audio, not captions edited by hand (their
+// remake waits for the person) and not a multi-voice turn, whose key the regeneration list
+// can't hold yet.
+function retryable(snapshot, key) {
+    if (snapshot.view.revision.content.subtitleCues !== undefined)
+        return false;
+    if (/:turn:\d+$/.test(key))
+        return false;
+    return snapshot.plan.recipes.some((row) => row.input.kind === "tts" && row.input.logicalKey === key);
+}
+function mismatchChunks(snapshot, segment) {
     try {
-        chunks = narrationChunks(narrationTextParts(snapshot.view, snapshot.plan, segment));
+        return narrationChunks(narrationTextParts(snapshot.view, snapshot.plan, segment));
     }
     catch {
         // Without a readable plan the message still gives the time and the words.
+        return [];
     }
-    return describeMismatch(chunks, segment, mismatch);
 }
-export function describeMismatch(chunks, segment, mismatch) {
+export function mismatchMessage(snapshot, segment, mismatch) {
+    return describeMismatch(mismatchChunks(snapshot, segment), segment, mismatch);
+}
+// The chunk that holds the words the audio stopped matching, by index; -1 when none does.
+export function mismatchChunk(chunks, mismatch) {
     const probe = comparable(mismatch.expected).split(" ").slice(0, 6).join(" ");
-    const at = probe === ""
+    return probe === ""
         ? chunks.length - 1
         : chunks.findIndex((chunk) => comparable(chunk.spokenText).includes(probe));
+}
+export function describeMismatch(chunks, segment, mismatch, 
+// Set when the chunk is one a voice made: `try` is the automatic try just asked for, or
+// undefined once its tries are used up.
+retry) {
+    const at = mismatchChunk(chunks, mismatch);
     const chunk = at === -1 ? undefined : chunks[at];
     const where = chunk === undefined
         ? `${clock(mismatch.at)} into the ${segment} narration`
         : `${clock(mismatch.at)} into the ${segment} narration, in narration chunk ${String(at + 1)} of ${String(chunks.length)} (it starts "${opening(chunk.spokenText)}")`;
     const expected = mismatch.expected === "" ? "the end of the text" : `"${mismatch.expected}…"`;
     const heard = mismatch.heard === "" ? "no more speech" : `"${mismatch.heard.toLowerCase()}…"`;
+    const stopped = `Subtitles stopped matching the audio at ${where}. The text expected ${expected} but the audio has ${heard}`;
+    if (retry !== undefined) {
+        const n = String(retry.chunk);
+        return retry.try === undefined
+            ? `${stopped} Slopify already recorded narration chunk ${n} again ${String(narrationRetryLimit)} times and the audio still doesn't match there, so the voice probably reads something its own way (a year, an abbreviation or a name). Listen at ${clock(mismatch.at)}: if words are missing or wrong, reword that sentence in Edit project → Narration → narration chunk ${n}, save, then Continue the run. If it says them right, use Download diagnostics in Settings and report it.`
+            : `${stopped} The voice probably skipped or garbled words there, so Slopify is recording narration chunk ${n} again by itself (try ${String(retry.try)} of ${String(narrationRetryLimit)}) and carries on with the video when it's done. If this message is still here in a few minutes, regenerate narration chunk ${n} in Edit project → Narration, then Continue the run.`;
+    }
     const fix = chunk === undefined
         ? `Listen at ${clock(mismatch.at)}: if words are missing or wrong, regenerate that part in Edit project → Narration, then Continue the run.`
         : `Listen at ${clock(mismatch.at)}: if words are missing or wrong, regenerate narration chunk ${String(at + 1)} in Edit project → Narration, then Continue the run.`;
     // A voice that reads a year, an abbreviation or a name its own way reads it the same way
     // again, so a remake would cost a chunk and fail here once more.
     const same = "If it says them right, only another way (a year, an abbreviation or a name read its own way), regenerating gives the same reading: use Download diagnostics in Settings and report it.";
-    return `Subtitles stopped matching the audio at ${where}. The text expected ${expected} but the audio has ${heard} The recording there probably skips or changes words. ${fix} ${same}`;
+    return `${stopped} The recording there probably skips or changes words. ${fix} ${same}`;
 }
 function comparable(text) {
     return text

package/dist/slices/schedules/service.js

@@ -90,7 +90,8 @@ export function updateSchedule(deps, input) {
             : previous.nextRunAt === null
                 ? null
                 : nextOccurrence(parsed.data.cadence, parsed.data.timezone, now);
-        const value = summary(parsed.data, next?.toISOString() ?? null, now.toISOString(), previous.status, previous.version + 1, 
+        // The version it was saved against, for the record; runs use the newest.
+        const value = summary({ ...parsed.data, templateVersion: checked.value }, next?.toISOString() ?? null, now.toISOString(), previous.status, previous.version + 1, 
         // Saving clears a recorded generation failure, so the next tick tries again.
         { ...previous.topics, failedAt: null, error: null });
         if (!updateScheduleRow(deps.db, value, parsed.data.mutationId, hash, parsed.data.baseVersion))

package/dist/slices/storage/backup-format.js

@@ -57,6 +57,7 @@ export const projectTables = [
     "project_uploads",
     // Since 2.5.0. Left out on purpose: plan_limit_waits and plan_limit_waiters (an account's
     // current wait, a lease of this install) and prompt_softening (a pending one-off request).
+    // Since 3.0.8, narration_retries is left out too: the tries of a run, not of the project.
     "review_verdicts",
     "provider_usage",
     "plan_limit_readings",

package/dist/slices/youtube/answer.js

@@ -23,7 +23,7 @@ export function descriptionMessages(brief) {
                 `- The pinned comment is plain text without links, at most ${String(pinnedCommentMaxCharacters)} characters.`,
                 `- Titles are exactly ${String(alternativeTitles)} other titles for this video, for YouTube's title A/B test beside the video's own title: each at most ${String(titleMaxCharacters)} characters, one line, different from the video title and from each other.`,
                 "",
-                "The pinned comment is what the channel pins under the video, unless the instructions below say otherwise: thank the viewer in one line, ask one question a viewer can answer from their own experience of the subject, point to the chapters in the description, and end by inviting a suggestion for the next video. Two to four short paragraphs, in the same voice as the summary.",
+                "The pinned comment is what the channel pins under the video, unless the instructions below say otherwise: one or two short sentences, at most 200 characters, in the same voice as the summary. Ask one question a viewer can answer from their own experience of the subject, and invite a suggestion for the next video.",
                 "The other titles try different angles on the same video (a question, a stake, a surprising fact) while staying true to it and in the video title's language and tone.",
             ].join("\n"),
         },

package/dist/slices/youtube/model.js

@@ -17,8 +17,9 @@ export const descriptionMaxCharacters = 5000;
 // these alternatives. YouTube's limit on a title.
 export const alternativeTitles = 2;
 export const titleMaxCharacters = 100;
-// YouTube's limit on a comment is 10,000; a pinned comment people read in full is far shorter.
-export const pinnedCommentMaxCharacters = 1500;
+// YouTube's limit on a comment is 10,000; a pinned comment people read in full is a line or
+// two. The model is asked for 200; this is the most a hand-picked prompt may make it.
+export const pinnedCommentMaxCharacters = 500;
 // What a project uses when no Description prompt from the library is picked. No keywords,
 // so it never asks Play for a field.
 export const defaultDescriptionPrompt = [

package/dist/tutorials/Document-Themes.md

@@ -57,7 +57,7 @@ Sizes are in millimetres (mm) unless marked pt (points; 1 pt is about 0.35 mm).
 
 ### Fonts
 
-Each font has three controls: the family, its weight or italic, and **Letter spacing (mm)** from −0.5 to 2. The families are **Cinzel** (bundled; four weights, no italics) and **Times**, **Helvetica** and **Courier** (built into every PDF reader).
+Each font has three controls: the family, its weight or italic, and **Letter spacing (mm)** from −0.5 to 2. The families are **Cinzel** (bundled; four weights, no italics), **Literata** (bundled; a text face made for long reading, in regular, bold, italic and bold italic) and **Times**, **Helvetica** and **Courier** (built into every PDF reader).
 
 | Setting | Where it is used | Default |
 |---|---|---|

package/dist/tutorials/Home-and-Projects.md

@@ -19,7 +19,7 @@ From top to bottom:
 | Destinations | **Home**, **Projects**, **Calendar** (also lit on Schedules), **Channels**, **Library** (Prompts, Intros & Outros, Templates, Document themes, Narration aliases), **Settings** (also lit on Usage). |
 | **N running** | Shown while runs are going. It links to Running now on Home. |
 | **Channel** | The channel picker (see below). |
-| **New video** | Opens Play (`C` from anywhere). |
+| **New project** | Opens Play (`C` from anywhere). |
 | Links | **GitHub**, **Patreon** and **Buy Me a Coffee**, each opening in a new tab. |
 | Foot | "Free. Your keys, your machine.", the updates button (circular arrows, see [Updating and Patch Notes](Updating-and-Patch-Notes)) and the tutorial button (question mark, **Start interactive tutorial**). |
 
@@ -33,7 +33,7 @@ In every list, a press anywhere on a row or tile opens or picks it, not only on
 
 ### The command palette
 
-Press `Ctrl+K`, or click **Search or run a command**, to jump anywhere or run an action by typing. The **Go to** group has **Open home**, **Open projects**, **Open calendar**, **Open schedules**, **Open channels**, **Open library**, **Open settings**, **Open usage and costs** and **Show patch notes**. **New video** opens Play. The **Channel** group has **Show all channels** and **Switch to <channel>**. See [Keyboard Shortcuts and Command Palette](Keyboard-Shortcuts-and-Command-Palette).
+Press `Ctrl+K`, or click **Search or run a command**, to jump anywhere or run an action by typing. The **Go to** group has **Open home**, **Open projects**, **Open calendar**, **Open schedules**, **Open channels**, **Open library**, **Open settings**, **Open usage and costs** and **Show patch notes**. **New project** opens Play. The **Channel** group has **Show all channels** and **Switch to <channel>**. See [Keyboard Shortcuts and Command Palette](Keyboard-Shortcuts-and-Command-Palette).
 
 ### The Channel picker
 
@@ -43,7 +43,7 @@ The **Channel** picker near the foot of the sidebar (at the top of Home on a pho
 
 **Where to find it:** the sidebar → **Home**.
 
-The page title is the channel you picked (or **Home**), under today's date. At the top right are **Open calendar** and **New video**.
+The page title is the channel you picked (or **Home**), under today's date. At the top right are **Open calendar** and **New project**.
 
 On a fresh install, Home sends you to the first-run screen once. See [First Launch and Welcome](First-Launch-and-Welcome).
 
@@ -98,7 +98,7 @@ See [Costs and Run Cost](Costs-and-Run-Cost).
 
 **Where to find it:** the sidebar → **Projects**.
 
-Every run ever started, newest first, for the channel picked in the sidebar. The heading says how many projects there are and for which channel. **New video** opens Play.
+Every run ever started, newest first, for the channel picked in the sidebar. The heading says how many projects there are and for which channel. **New project** opens Play.
 
 ### Search and filter
 

package/dist/tutorials/Keyboard-Shortcuts-and-Command-Palette.md

@@ -7,7 +7,7 @@ The command palette lets you reach every screen, every project and the frequent
 ## Use the command palette
 
 1. Press `Ctrl+K`.
-2. Type a few letters of what you want, such as `set` for **Open settings** or `back` for **Back up now**. Letters only need to appear in order, so `nwv` finds **New video**. Commands also match other words, for example `keys` finds **Open settings**. Several words match in any order across the command's name, the project it acts on and its other words: `cleopatra regenerate image 3` finds **Regenerate image 3 in Cleopatra**.
+2. Type a few letters of what you want, such as `set` for **Open settings** or `back` for **Back up now**. Letters only need to appear in order, so `nwv` finds **New project**. Commands also match other words, for example `keys` finds **Open settings**. Several words match in any order across the command's name, the project it acts on and its other words: `cleopatra regenerate image 3` finds **Regenerate image 3 in Cleopatra**.
 3. Use `Up` and `Down` to move through the list, `Home` and `End` to jump to the first or last, and `Enter` to run the highlighted command. You can also click a command.
 4. Press `Esc` (or `Ctrl+K` again) to close the palette without running anything.
 
@@ -23,7 +23,7 @@ Press `?` anywhere (outside a text field) to see **Keyboard shortcuts**: every k
 |---|---|---|
 | `Ctrl+K` / `Cmd+K` | Anywhere | Opens or closes the command palette. |
 | `?` | Anywhere | Shows the keyboard shortcuts. |
-| `C` | Anywhere | **New video** (opens Play). |
+| `C` | Anywhere | **New project** (opens Play). |
 | `G` then `H` | Anywhere | Go to Home. |
 | `G` then `P` | Anywhere | Go to Projects. |
 | `G` then `C` | Anywhere | Go to the Calendar. |
@@ -70,7 +70,7 @@ Commands are grouped under headings in the palette. Group names below are the he
 
 | Command | What it does |
 |---|---|
-| **New video** (`C`) | Opens Play. |
+| **New project** (`C`) | Opens Play. |
 | **Show all channels** | Shows every channel's projects, schedules and costs. |
 | **Switch to <channel>** | Shows one channel only. There is one command per channel. |
 

package/dist/tutorials/Play-Overview.md

@@ -2,7 +2,7 @@
 
 Play is the screen where you set up a new video and start it. You pick a template (or none), type what the video is about, check the setup rows, and press the Play key. You get a project that writes the article, records the narration, draws the images and renders the video, plus any extra outputs you switched on.
 
-**Where to find it:** **New video** in the sidebar, **New video** on Home or Projects, `Ctrl+K` → **New video**, or press `C` anywhere. The page header reads **What's the video about?**
+**Where to find it:** **New project** in the sidebar, **New project** on Home or Projects, `Ctrl+K` → **New project**, or press `C` anywhere. The page header reads **What's the video about?**
 
 ## How Play is laid out
 

package/dist/tutorials/Schedules.md

@@ -134,9 +134,9 @@ Pick a schedule in the list to see its detail: **When**, **Timezone**, **Next ru
 
 **Run history** lists each run with its status (running, done, failed, skipped and so on), the time it was due, and either the project it made or the reason it didn't run. Deleted schedules are listed under **Deleted schedules** at the bottom; pick one to see its history.
 
-## Use a newer template version
+## When you edit the template
 
-A schedule keeps the template version it was set up with, so saving a newer template doesn't change what the schedule makes. To switch, edit the schedule, pick the template again in **Template**, and save.
+A schedule always uses its template as it is now: save a change to the template and the next run, the Calendar and topic generation use it. If the change adds a keyword the schedule has no value for, fill it in under the schedule's topics or every-run values.
 
 ## Tips
 

package/dist/tutorials/YouTube-Description.md

@@ -12,7 +12,7 @@ Slopify can write your video's YouTube description for you: a short summary, cha
 | **Chapters** | Timestamped lines such as `0:00 Introduction`, at the narration's real times. YouTube turns them into chapters. |
 | **Hashtags** | The hashtags at the end of the description. YouTube shows the first three above the title. |
 | **Tags** | Search tags for YouTube Studio's **Tags** field, kept separate from the description. Viewers don't see them. |
-| **Pinned comment** | A comment to post under the video and pin: a thank-you, a question viewers can answer from their own experience, a pointer to the chapters and an ask for the next topic. Your Description prompt can say how you want it. |
+| **Pinned comment** | A comment to post under the video and pin: a line or two asking viewers a question they can answer from their own experience, and what to cover next. Your Description prompt can say how you want it. |
 | **Other titles** | Two more titles for YouTube's **A/B Testing** (Test & compare), beside the project's own title: each a different angle on the same video, one per line. |
 
 Slopify lays out the description itself (summary, blank line, one chapter per line, blank line, hashtags), so the layout YouTube needs never depends on the model's spacing. The files are saved in the project as `description.txt`, `tags.txt`, `pinned-comment.txt` and `titles.txt`.