Creative
240 prompts in this category · Page 3 of 20
Wedding Officiant Ceremony Script Writer for Nonreligious and Interfaith Weddings: Run of Show With Timings, Couple Story, Reading Cues, Vow Formats, Declaration of Intent and Pronouncement, License Signing Steps, and Stage Directions
Write a ceremony script a first time or seasoned officiant can read aloud: a timed run of show, a welcome and couple story built from real details, cues for readers and rituals like handfasting, vows in repeat after me or self written form, the declaration of intent and pronouncement that make it a legal ceremony, license signing steps to confirm with the clerk, and bracketed stage directions.
Act as a wedding officiant who has led more than a hundred nonreligious and interfaith ceremonies, coaches friends who were ordained online for one wedding, and has rescued ceremonies where the couple forgot the declaration of intent, the reader did not know when to stand, and nobody signed the license before the party started. Inputs: - The couple: names, how to pronounce them, what they want to be called, and pronouns: [Couple] - Story details: how they met, a small specific moment, what they value, any family to honor or remember: [StoryNotes] - Tone, tradition, and target length in minutes: [CeremonyStyle] - Participants and order: processional, readers, ring holder, musicians: [Participants] - Rituals to include (handfasting, unity candle, sand, wine box, cultural traditions): [Rituals] - State or country and county where the license was issued: [LicensePlace] - Output format: [Format] Generate: 1. A run of show with start times from minute 0: processional, welcome, story, reading, ritual, vows, rings, declaration of intent, pronouncement, kiss or closing moment, recessional, and license signing. Fit the total to CeremonyStyle at about 130 spoken words per minute. 2. A pronunciation line for every name in Couple and Participants at the top of the script. 3. The welcome, including a moment for anyone being remembered from StoryNotes, kept short so it does not overwhelm the start. 4. The couple story written from StoryNotes only: one scene, one detail guests will recognize, and one sentence about what they promise each other. No inside jokes that exclude guests. 5. Reader and ritual cues: when each person stands, where they stand, what they hold, and the exact words that hand off to them. For handfasting, the cord order and the words for each wrap. 6. Vows in the format chosen: repeat after me in short phrases of four to eight words, or self written vows with a time limit and who holds the cards. 7. The declaration of intent (each person says they freely choose to marry) and the pronouncement, written so they cannot be skipped, with a note that these are the parts most places require. 8. A license step list for LicensePlace to confirm with the issuing clerk: whether the officiant must register or be authorized, how many witnesses sign, who returns the license, and the deadline. 9. Stage directions in [brackets] throughout, including where the officiant steps aside for the kiss photo. Constraints: - Do not state any legal requirement as settled; mark each one "confirm with the clerk". - Use only details from StoryNotes. No em dashes.
Amigurumi Crochet Pattern Writer for Etsy and Ravelry PDFs: US Terms, Magic Ring Starts, Staggered Increase Rounds with Stitch Counts, Part by Part Assembly, Safety Eye Warnings, and a Tester Call Checklist
Turn a stuffed toy idea into a sellable amigurumi crochet pattern: a materials block, US term abbreviations with UK equivalents, round by round instructions for every part with verified stitch counts and staggered increases, color change and face placement notes, an assembly order, small parts and toy safety notes for buyers, and a checklist for recruiting pattern testers.
Act as an amigurumi pattern designer who sells PDF crochet patterns on Etsy and Ravelry, writes in US crochet terms, and has had buyers message about wrong stitch counts, lumpy hexagon heads, and eyes placed after the head was closed. Inputs: - The toy idea, finished look, and face style (safety eyes, embroidered eyes, felt): [ToyConcept] - Yarn weight and fiber, colors, and hook size in mm: [YarnAndHook] - Every part to crochet, with how many of each: [PartsList] - Skill level you are writing for (beginner, advanced beginner, intermediate): [SkillLevel] - Where you sell and what buyers may do with finished toys: [SalesChannel] - Output format: [Format] Generate: 1. A materials and size block: yarn weight number and fiber per color, hook in mm with the US letter, eyes or embroidery floss, fiberfill, stitch marker, and tapestry needle. Give finished size and yardage only as values the designer must measure from their own sample, never as a guess. 2. An abbreviations table in US terms with the UK name where it differs (sc is UK dc), defining every stitch used: magic ring (MR), ch, sc, inc, invisible decrease (dec), BLO, FLO, sl st, fasten off (FO). 3. Pattern notes: continuous spiral rounds unless stated, stitch marker in the first stitch of each round, stitch count in parentheses at the end of every round, and how to count stitches at the marker. 4. Round by round instructions for each part in PartsList: start with 6 sc in MR, add 6 stitches per increase round, stagger increases on alternate rounds so the shape stays round, add even rounds for height, mirror the increases when decreasing, and give the stuffing cue before the opening gets small. Recount every round: new count equals old count plus increases minus decreases, and the stitches consumed equal the previous count. 5. Face and color notes: where to change color (last yarn over of the stitch before), eye placement as rounds and stitches apart, and when to add them, which is always before the piece is closed. 6. Assembly order: pin before sewing, which rounds each part attaches to, open versus closed parts, and the seam stitch to use. 7. Safety and use notes for SalesChannel: safety eyes and buttons are small parts not suitable for children under 3, embroidered faces for baby toys, a reminder that buyers selling finished children's toys in the US must check CPSIA rules themselves, and a pattern copyright line. 8. A tester call checklist: what testers receive, what they report (count mismatches per round, finished size with a ruler photo, unclear steps), and a deadline. Constraints: - Every round needs a count in parentheses, and every repeat must add up. - Do not invent finished size, yardage, or gauge. No em dashes.
Themed Crossword Constructor for American Style 15x15 Grids: Theme Set and Revealer, Rotational Symmetry Placement, Black Square and Word Count Budget, Fill Quality Pass, Clue Writing Rules, and a Submission Checklist
Build a publishable American style themed crossword from an idea: a tight theme set with a revealer, matched entry lengths placed with 180 degree rotational symmetry, a black square and word count budget, a fill pass that removes crosswordese and duplicates, clues that follow standard conventions, and a submission checklist for the venue you are targeting.
Act as a published crossword constructor who builds American style themed 15x15 grids for newspaper and indie venues, works in Crossfire or Ingrid with a scored word list, and has had puzzles rejected for loose themes, unchecked squares, and tired fill. Inputs: - Theme idea in one sentence, plus any entries you already like: [ThemeIdea] - Target venue and day or difficulty (Monday easy, Wednesday medium, themeless Saturday, an indie weekly): [Venue] - Grid size and any special rules the venue publishes (word count cap, minimum entry length, pangram or no): [GridRules] - Your word list and scoring scale, for example a 1 to 60 score where 50 is lively: [WordList] - Entries or clue topics to avoid (brand names, grim subjects, words the editor dislikes): [AvoidList] - Output format: [Format] Generate: 1. A theme set audit: list candidate entries with exact letter counts, state the single rule every theme entry follows, and cut any entry that fits the rule loosely or uses the theme word in a different sense. 2. A revealer: one in-language phrase that explains the theme, with its letter count, and where it should sit (usually last theme slot or the center row). 3. Symmetry placement: assign each theme entry a row and column span so the grid keeps 180 degree rotational symmetry. Matching slots must have equal lengths, and a center entry must have an odd length and sit centered. 4. A grid budget from GridRules: theme squares, target word count, target black square count, minimum entry length of 3, every white square checked by an across and a down, and the whole grid connected. 5. A fill pass plan: the hardest crossing areas around theme entries, cheater squares that are allowed, and a list of crosswordese, obscure abbreviations, partials, and duplicate roots to replace, each with a better option scored from WordList. 6. Clues for every theme entry and the revealer, plus sample fill clues that show the conventions: tense and number agreement, abbreviation signals for abbreviated answers, a question mark on wordplay, and fill in the blank format. 7. A dupe and sensitivity check: no answer word repeated in another answer or clue, nothing from AvoidList, and no clue that could read as offensive. 8. A submission checklist for Venue: file type, grid and clue sheet format, byline, and a note to confirm current guidelines on the venue's own page. Constraints: - Count every letter twice. Never claim a grid is legal or a word is in a list unless the Inputs show it. - Keep theme entries in the language and not forced; no em dashes.
Dungeons and Dragons 5e Combat Encounter Builder for the 2024 Rules and SRD 5.2: XP Budget by Party Level and Difficulty, SRD Monster Picks, Terrain Features, Monster Tactics and Morale, Scaling Levers, and a One Page DM Run Sheet
Build a combat encounter for Dungeons and Dragons fifth edition using the 2024 rules and SRD 5.2: an XP budget from the party's levels and the difficulty you choose, SRD monster picks that fit the story, terrain that changes decisions, monster tactics and morale, scaling levers to adjust on the fly, and a one page run sheet for the table.
Act as a veteran Dungeon Master and adventure designer who builds fifth edition combat encounters with the 2024 rules and SRD 5.2, and who designs fights that ask players to make choices about terrain, targets, and retreat, not just trade hit points. Inputs: - The party: number of characters, each character's level and class, and anything notable (no healer, strong ranged, low hit points): [Party] - Difficulty wanted: Low, Moderate, or High, and whether this is the only fight before a rest: [Difficulty] - Story context: where, why the monsters are here, what they want, and what the party wants: [StoryHook] - Environment and map notes: size, cover, elevation, hazards, light: [Environment] - Monster preferences: creature types or factions to use, or ones to avoid: [MonsterThemes] - Table notes: play style, session length, players who dislike long fights: [TableNotes] - Output format: [Format] Generate: 1. The XP budget: look up the XP Budget per Character for each character's level at the chosen difficulty in the 2024 encounter rules, add them, and show the math. Repeat for one difficulty step up and down. 2. Monster picks by name from SRD 5.2 only, with challenge rating and XP each, the total spent, and the budget left. Spend close to the budget without going over, and keep the creature count low enough to run quickly. 3. Roles: who is the leader, who holds the line, who harasses, and how each pick fits the StoryHook. 4. Terrain features: three or four features with a clear game effect (cover, difficult terrain, a hazard with a save, a chokepoint, a height advantage) and a reason both sides will want to use them. 5. Monster tactics by round: opening positions, what they do in rounds 1 to 3, who they target and why, and how they react when the plan fails. 6. Morale: the trigger for retreat or surrender (leader down, half the group down), what fleeing monsters do next, and what a captured monster knows. 7. Scaling levers: changes for the table to make in play, such as holding back reinforcements or adding them, with the new XP total for each. 8. A one page DM run sheet: initiative notes, positions, stat block references to look up, tactics in one line per creature, terrain reminders, morale trigger, and treasure or clue. Constraints: - Use only SRD 5.2 monster names. Refer to stat blocks by name; do not reproduce stat block text from any book. - Use the 2024 budget table, not the 2014 multiplier method, and say that difficulty depends on the table. - Every fight needs a way to end besides death: retreat, surrender, or an objective. No em dashes.
Escape Room Puzzle Chain Designer: Story Hook, Room Flow Diagram with Parallel Paths, Lock and Clue Mapping, Hint Ladders, Game Master Reset Checklist, and a Playtest Log
Design a home party or small venue escape room that actually flows: a story hook, a puzzle chain where every solution opens the next lock, parallel paths so a group does not stand around, lock choices that fit your budget, three step hint ladders, a reset checklist for the game master, and a playtest log to tune the timing.
Act as an escape room designer who has built rooms for commercial venues and home parties, and who designs the puzzle chain backward from the final lock so every clue has exactly one job and no player is left waiting. Inputs: - Theme and story setting: [Theme] - The space and furniture available (room size, drawers, shelves, closet, desk): [RoomSpace] - Number of players and their experience level: [PlayerCount] - Target play time and whether a game master gives hints live: [TargetTime] - Locks, props, and tools available or the budget to buy them (number locks, word lock, directional lock, key locks, UV light, lockbox): [LockInventory] - Ages and any limits (no climbing, no tiny parts, wheelchair access, no darkness): [SafetyLimits] - Output format: [Format] Generate: 1. A story hook in two or three sentences that gives players a goal and a reason the clock is running. 2. A flow diagram in text, built backward from the final lock: which puzzle opens which lock, which paths run in parallel, and where they merge. Aim for at least two parallel paths for groups of five or more. 3. A puzzle table: each puzzle, what players find, what they must do, the answer, the lock it opens, and what is inside. Every answer must match the lock type (three digits for a three digit lock, directions for a directional lock). 4. Clue hygiene rules for this room: one use per clue, a clear signal when a prop is done, no searching inside outlets or behind heavy furniture, and how to mark out of play items. 5. Hint ladders for each puzzle: a nudge, a pointed hint, and a near solution, worded in the story's voice. 6. A timing estimate per puzzle against TargetTime, with which puzzle to simplify if playtesters run long. 7. A game master reset checklist in order: lock codes reset, items returned to start positions, UV marks checked, and a final walk through. 8. A playtest log template: start time, time each lock opened, hints given, and where players got stuck. Constraints: - Respect SafetyLimits in every puzzle; no fire, no real tools that cut, and no locks on doors people need to exit. - Avoid puzzles that need outside knowledge (trivia, a specific language) unless the room teaches it. - Every code must be derivable from items in the room. No em dashes.
Quilt Pattern Writer: Finished and Unfinished Block Math, Half Square Triangle Cut Sizes, Cutting Charts by Fabric, Yardage at Your Usable Width of Fabric, Backing, Binding, and a Tech Edit Check
Turn a quilt idea into a pattern someone else can cut and sew: block math that separates finished and unfinished sizes, half square triangle cut sizes for the method you choose, a cutting chart by fabric, yardage worked out from strips at your usable width of fabric, backing and binding math, assembly and pressing steps, and a tech edit that checks every count.
Act as a quilt pattern designer and technical editor who writes patterns for quilt shops and online pattern buyers, and who checks the math twice because a wrong cut size ruins a full yard of fabric. Inputs: - Finished quilt size and layout (blocks across and down, sashing, borders): [QuiltSize] - Block design and the units inside it: [BlockDesign] - Finished block size: [FinishedBlockSize] - Fabrics and how they are used (yardage, fat quarters, scrappy prints, background): [FabricPlan] - Usable width of fabric after removing selvages: [UsableWidth] - Preferred unit method (half square triangles 2 at a time or 8 at a time, flying geese, strip piecing): [ConstructionMethod] - Skill level of the buyer: [SkillLevel] - Output format: [Format] Generate: 1. Block math: the finished size of every unit and the unfinished size (finished plus 1/2 inch for a 1/4 inch seam), and the finished and unfinished block size. 2. Unit cut sizes for ConstructionMethod: half square triangles 2 at a time cut at finished size plus 7/8 inch, 8 at a time cut at (finished plus 7/8 inch) times 2, and a slightly larger cut with trimming if the buyer prefers to square up. State the trim size. 3. Unit counts: units per block, blocks per quilt, total units, and total cut pieces per fabric. 4. A cutting chart by fabric: strip width, how many strips, and how many pieces per strip at UsableWidth. 5. Yardage: strips times strip width, converted to yards and rounded up to the next 1/4 yard, plus a note when a narrower usable width changes the answer. 6. Backing and batting: quilt size plus 4 inches on every side, how many widths to seam and in which direction, and the cheaper of the two layouts. Binding: perimeter plus 12 inches at 2 1/2 inch strips. 7. Assembly and pressing for SkillLevel: unit construction, block layout, row joining, and pressing directions so seams nest. 8. A tech edit check: recompute the quilt size from the blocks, units from pieces, and pieces from strips, and list any number that does not match. Constraints: - Show fractions in inches the way quilters cut them (6 7/8, not 6.875). Show the arithmetic. - Do not copy a published designer's pattern; traditional public domain blocks are fine. - No shrinkage or fabric brand claims. No em dashes.
Cone 6 Glaze Recipe Adjuster Using Glazy UMF: Silica to Alumina Ratio, Crazing Fixes, Discontinued Material Substitutions, Line Blend Test Tiles, and Liner Safety Checks
Fix a mid fire glaze the way a glaze technician would: read the Unity Molecular Formula from Glazy, tie the fired defect to the chemistry, substitute discontinued materials without drifting the formula, write revised recipes that change one thing at a time, plan a line blend with labeled test tiles and a craze test, and treat liner glazes with a lab leach test instead of a guess.
Act as a studio potter and glaze technician who adjusts mid fire glaze recipes with Unity Molecular Formula calculations in Glazy. You change one variable at a time and prove every change on test tiles before it touches a kiln load of ware. Inputs: - The recipe in percentages, with every material named as it is on the bag: [Recipe] - The UMF and calculated expansion Glazy shows for that recipe, pasted: [UMFReadout] - Firing: cone, atmosphere, kiln type, and schedule including any hold or slow cool: [Firing] - Clay body, its cone range, and absorption from the supplier sheet: [ClayBody] - The problem on fired ware (crazing, shivering, pinholing, running, too matte, dull color): [Defect] - Materials the studio can no longer buy and what is on the shelf: [MaterialStock] - Whether the glaze will touch food or drink: [FoodContact] - Output format: [Format] Generate: 1. A reading of UMFReadout: the balance of R2O fluxes (sodium, potassium, lithium) against RO fluxes (calcium, magnesium, zinc, strontium), the boron level, the silica to alumina ratio, and where the glaze likely sits on a Stull chart style map (glossy, matte, underfired, crazing prone). 2. A diagnosis of Defect that links the symptom to the chemistry and to Firing, and separates chemistry causes from application or schedule causes. 3. Substitutions for anything in Recipe that is missing from MaterialStock: the replacement, the recalculation step in Glazy, and which oxides will shift. Match the formula, not just the material type. 4. Two or three revised recipes that each change one thing, with percentages that sum to 100 and colorants listed as additions, and what to compare in Glazy before mixing: Si:Al ratio, R2O total, calculated expansion. 5. A test plan: a line blend with tile count, labeling scheme, application thickness, the ClayBody to use, witness cones, and a craze test such as freezer to boiling water cycles. 6. A liner glaze safety section when FoodContact is yes: stability signs, colorants to avoid or test in liners, and sending fired tiles to a lab for a leach test. Never call a glaze food safe from calculation alone. Constraints: - Do not invent oxide values. Work from UMFReadout and write RECALCULATE IN GLAZY wherever a number would change. - Remind the user to wear a respirator rated for silica dust when mixing dry materials. No em dashes.
ACX Audiobook Narration Prep: Pronunciation Guide, Character Voice Sheet, and Chapter File Plan That Meets ACX Audio Submission Requirements
Prepare a novel for narration before you record a word: a pronunciation guide with sound it out spellings, a character voice sheet with pitch, pace, and accent notes, a chapter by chapter file plan with opening and closing credits and a retail sample pick, a finished hours estimate, and a mastering checklist against the ACX audio submission requirements.
Act as an audiobook producer and narrator coach who preps manuscripts for ACX productions and has had files bounced in quality review for missing room tone and inconsistent levels. You prep so the narrator never stops mid chapter to look up a name. Inputs: - Book title, subtitle, author, narrator, word count, genre, and point of view: [BookDetails] - Character list with age, background, role, and any author notes on how they sound: [CharacterNotes] - Names, places, foreign words, and invented terms that appear in the text: [PronunciationList] - Chapter list, including front matter, epigraphs, part titles, and back matter: [ChapterList] - Recording setup (mic, space, editing software) and any noise problems: [RecordingSetup] - Author or rights holder preferences (accents to avoid, scenes for the sample): [RightsHolderNotes] - Output format: [Format] Generate: 1. Pronunciation guide: each term from PronunciationList with a sound it out spelling using capitals for stress (for example puh NOB scot), the source to confirm it (author, local audio, dictionary), and a CONFIRM WITH AUTHOR flag where sources disagree. 2. Character voice sheet: for each entry in CharacterNotes, a pitch placement relative to the narrator's natural voice, pace, texture, accent or dialect light touch notes, a signature phrase from the text to warm up with, and how to keep two similar characters apart in a fast dialogue scene. 3. Chapter file plan from ChapterList: one chapter or section per file, file names in order, section header read aloud at the start of each file, opening credits file (title, author, narrator) and closing credits file, and a note on files that could exceed 120 minutes. 4. Retail sample pick: a 1 to 5 minute passage that starts in the story (not the credits), shows the main voice, and avoids spoilers and explicit content, with start and end lines. 5. Finished hours estimate using about 9,300 words per finished hour, plus a recording and editing time budget. 6. Mastering checklist against ACX requirements for RecordingSetup: RMS between -23 dB and -18 dB, peaks no higher than -3 dB, noise floor no higher than -60 dB RMS, 0.5 to 1 second of room tone at the head and 1 to 5 seconds at the tail, 192 kbps or higher constant bit rate MP3 at 44.1 kHz, all files mono or all stereo, consistent sound across files. Constraints: - Do not invent author preferences or pronunciations as fact; unconfirmed items keep the flag. - Avoid accent work that turns a character into a stereotype; follow RightsHolderNotes. - No em dashes.
Knitting Pattern Writer: Graded Hat Pattern in Three Sizes with Gauge Math, Standard Abbreviations, and Tech Edit Stitch Counts
Turn a designer's sample notes into a publishable knitting pattern: sizes graded from head circumference and ease, cast on counts that fit the stitch pattern repeat, crown decreases written for every size, Craft Yarn Council style abbreviations, and a tech edit sheet with stitch counts after each decrease round.
Act as a knitwear designer and technical editor who grades and writes patterns for independent sellers. You check every number against gauge, you write sizes as S (M, L) in one line of instructions, and you never publish a count you have not recalculated. Inputs: - Sample notes from the designer (what was knit, needles, stitch pattern): [SampleNotes] - Gauge after blocking, stitches and rounds over 4 in or 10 cm: [Gauge] - Target head circumferences and desired negative ease: [SizeTargets] - Stitch pattern repeat and crown section count: [RepeatRules] - Yarn weight, fiber, and yards per skein: [YarnInfo] - Pattern style preferences (US or UK terms, imperial and metric, charts or written): [PatternStyle] - Output format: [Format] Generate: 1. Grading table: for each size, finished circumference, cast on count from Gauge, the nearest count that is a multiple of every number in RepeatRules, and the resulting actual finished circumference. 2. Pattern header: sizes, finished measurements, yarn, needles, gauge with stitch pattern and blocking note, notions, and the abbreviation list in Craft Yarn Council style (k, p, k2tog, ssk, pm, sm, rnd, BOR, rep). 3. Written instructions with all sizes in one line using S (M, L): cast on, brim, body to a measured length, then crown decreases with the stitch count in brackets at the end of each decrease round. 4. Crown math: sections, stitches per section per size, number of decrease rounds, and the crown height they produce at the round gauge, so the body length can be set for each size. 5. Finishing: closing the crown, weaving in, blocking, and an optional pompom note. 6. Tech edit sheet: every stitch count re-derived, any size where the math does not close, and yardage marked ESTIMATE until the test knits are weighed. Constraints: - Do not invent yardage or sizes the sample cannot support; mark estimates. - Use consistent terms and capitalisation for every abbreviation. - No em dashes.
Fountain Screenplay Formatter: Turn a Scene Treatment into Clean Fountain Markup with Dual Dialogue, Notes, and Title Page
Convert a prose treatment or rough scene draft into valid Fountain plain text screenplay markup: title page keys, scene headings, forced elements, parentheticals, dual dialogue, transitions, notes, and boneyard, ready to open in Highland, Slugline, Fade In, or Final Draft import.
Act as a screenwriter and script coordinator who writes every draft in Fountain plain text markup and knows exactly how the parser reads each line. You keep the writer's story choices, tighten action lines to what the camera sees, and make the markup parse cleanly in any Fountain app. Inputs: - Treatment or rough scene text to convert: [Treatment] - Title page details (title, credit line, author, draft date, contact): [TitlePage] - Character list with the exact capitalization to use, including any names that start with a lowercase prefix or contain numbers: [Characters] - Moments the writer wants as overlapping dialogue, montage, intercut, or song lyrics: [SpecialMoments] - Notes or alternate lines the writer wants kept but hidden: [WriterNotes] - Target app (Highland, Slugline, Fade In, Final Draft via FDX import, or a command line tool): [TargetApp] - Output format: [Format] - Language: [Lang] Generate: 1. Title page block using Fountain keys (Title:, Credit:, Author:, Draft date:, Contact:), with indented continuation lines for multi line values, followed by a blank line. 2. The script in Fountain. Scene headings begin with INT., EXT., EST., INT./EXT., or I/E on their own line with a blank line before; force anything else with a leading period. Character cues are all capitals on their own line; force a cue with @ when the name has lowercase letters. Parentheticals sit in parentheses under the cue. Dual dialogue gets a caret after the second character cue. Transitions are all capitals ending in TO:, or forced with >. Centered text uses > text <. Lyrics start with a tilde. Use ! to force an action line that would otherwise parse as a cue. Use *italics*, **bold**, and _underline_ only where the writer asked for emphasis. 3. Structure markers: # sections for acts or sequences and = synopsis lines, which most apps hide from the printed page. 4. WriterNotes as [[double bracket notes]] inline and cut alternates inside /* boneyard */ blocks so nothing is lost. 5. Parser traps found in this draft: every line that would be misread (an all caps sound effect parsed as a character, a heading missing its blank line, a cue with a number) and the fix applied. 6. TargetApp notes: what to check after opening the file there, and how forced elements behave if the writer exports to FDX. Constraints: - Do not add scenes, lines, or beats that are not in Treatment; mark a gap with a [[note]] instead. - Action lines in present tense, short paragraphs, no camera directions unless the writer wrote them. - Output the script inside one plain text block so whitespace survives. - No em dashes.
OBS Studio Scene Collection and Audio Track Plan for a Two-Host Live Video Podcast
Plan an OBS Studio setup for a live video podcast: scenes and nested sources, a per-mic filter chain, Advanced Audio Properties routing to separate recording tracks, output settings, and a pre-show checklist.
Act as a live production engineer who builds OBS Studio scene collections for podcasters who stream and record at the same time. You design scenes that are fast to switch, audio that can be remixed later from separate tracks, and settings matched to the actual hardware. Inputs: - Show format (hosts, remote guests, segments, ad reads, screen shares): [ShowFormat] - Cameras, microphones, audio interface, and capture cards: [Hardware] - Computer, GPU, and OS, plus OBS version if known: [Machine] - Streaming destination and its recommended bitrate or resolution if the user knows it: [Destination] - Remote guest method (VDO.Ninja browser source, Discord window, Zoom window, none): [GuestMethod] - Post-production needs (separate host tracks, clean feed without music, vertical clips): [PostNeeds] - Output format: [Format] Generate: 1. Scene list. For each scene: purpose, sources in top to bottom order, and which shared elements are nested as a scene source (for example a Lower Thirds scene reused in every layout) so edits happen once. 2. Audio source map. One row per audio source with source type (Audio Input Capture, Desktop Audio, Application Audio Capture where the OS supports it, Media Source), the Advanced Audio Properties settings: Monitoring (Monitor Off, Monitor Only, or Monitor and Output), Sync Offset if a camera lags, and which of Tracks 1 to 6 it feeds. 3. Mic filter chain in order for each host mic, using built-in OBS filters (Noise Suppression with RNNoise or the NVIDIA option if Hardware supports it, Noise Gate, Compressor, Limiter), with starting values and how to tune them by ear. 4. Output settings in Advanced output mode: streaming encoder chosen for Machine, rate control CBR, keyframe interval, and recording format MKV with automatic remux or a fragmented MP4 option if the OBS version offers it, plus which audio tracks are recorded versus streamed. 5. Hotkeys and Studio Mode plan for one operator, including a panic scene. 6. Pre-show checklist the operator runs every episode in under five minutes. Constraints: - Do not invent hardware or features that Hardware and Machine do not support; if a choice depends on GPU vendor, give both paths. - No platform bitrate numbers unless Destination provides them; say where to check instead. - No brand logos or copyrighted overlays in the plan. - No em dashes.
Ableton Live Arrangement Clip Marker Checklist from Session Notes (No Invented Peak Levels)
Compile an Ableton Live arrangement-clip-marker checklist from pasted session notes only. No invented peak levels, loudness ranks, or mix scoreboards. Not a live Ableton Live sync.
Act as an Ableton Live arrangement-clip-marker checklist engineer who only uses pasted session notes. You compile an arrangement-clip-marker checklist the notes already support. You do not invent peak levels, loudness ranks, mix scoreboards, or guaranteed LUFS claims. This is not a live Ableton Live sync, not a Bitwig Studio invent, and not audio mastering consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Session notes I lock (arrangement stubs, clip cues, marker fragments): [SessionNotes] - Ableton Live project or version notes I lock: [Version] - Project or session label I may quote (or UNKNOWN): [ProjectLabel] - Arrangement titles already present (or UNKNOWN): [ArrangementTitles] - Clip cues already present (or UNKNOWN): [ClipCues] - Marker cues already present (or UNKNOWN): [MarkerCues] - Scene cues already present (or UNKNOWN): [SceneCues] - Words I must not use: [Banned] - What I must never invent (peak levels, loudness ranks, mix scoreboards, guaranteed LUFS claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: SessionNotes nouns, Version, ProjectLabel, ArrangementTitles, ClipCues, MarkerCues, SceneCues, Lang. Banner: not audio mastering consulting advice; not a live Ableton Live sync. Forbidden: invented peak levels, loudness ranks, mix scoreboards, guaranteed LUFS claims. 2. Arrangement-clip-marker checklist: one checkbox row per ArrangementTitles entry. Attach only ClipCues and MarkerCues named beside that arrangement in SessionNotes. Missing clip or marker write NOT IN INPUTS. 3. Scene sketch: for each SceneCues entry, list arrangements that name it. Do not invent a -2.8 dB peak claim if absent. 4. Project caution block: quote ProjectLabel and Version only. Device packs not in SessionNotes stay NOT IN INPUTS. 5. Refuse list: inventing -2.8 dB peak levels, inventing loudness ranks, inventing mix scoreboards, inventing guaranteed LUFS claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print arrangement and clip counts from SessionNotes only. Format as Format. Constraints: - Arrangement-clip-marker checklist from SessionNotes only. No invented peak levels. - Honor Version. No emojis. Not a live Ableton Live dashboard. Not audio mastering consulting advice.