Create Ari Sardius media workflow report

2026-06-29 13:45:55 -04:00
parent 0f0bb49ef1
commit 4c6ad998fc
5 changed files with 753 additions and 0 deletions
@@ -0,0 +1,365 @@
 <!doctype html><html><head><meta charset="utf-8"><title>livestream_media_system_report_for_ari_sardius</title><style>
@page { size: Letter; margin: 0.62in 0.58in; }
 * { box-sizing: border-box; }
 body { font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; color: #1f2933; line-height: 1.48; font-size: 10.4pt; }
 h1 { font-size: 28pt; color: #0f2f4f; margin: 0 0 10px; letter-spacing: -0.03em; padding-bottom: 14px; border-bottom: 5px solid #2f80ed; }
 h2 { font-size: 17pt; color: #0f2f4f; margin-top: 27px; padding: 8px 12px; background: linear-gradient(90deg,#eaf3ff,#ffffff); border-left: 5px solid #2f80ed; break-after: avoid; }
 h3 { font-size: 13pt; color: #164b7a; margin-top: 18px; border-bottom: 1px solid #d6e4f0; padding-bottom: 4px; break-after: avoid; }
 h4 { font-size: 11.5pt; color: #2f5f8f; margin-top: 14px; break-after: avoid; }
 p { margin: 7px 0; }
 ul, ol { margin-top: 5px; padding-left: 22px; }
 li { margin: 3px 0; }
 blockquote { margin: 14px 0; padding: 12px 16px; border-left: 5px solid #f2c94c; background: #fff9e6; color: #3d3200; font-size: 11pt; }
 code { background: #eef4fa; padding: 1px 4px; border-radius: 4px; color: #0b456f; font-family: "SFMono-Regular", Consolas, monospace; font-size: 8.7pt; }
 table { width: 100%; border-collapse: collapse; margin: 12px 0 18px; font-size: 8.2pt; page-break-inside: auto; }
 th { background: #0f2f4f; color: white; text-align: left; padding: 7px 6px; }
 td { border: 1px solid #d9e2ec; padding: 6px; vertical-align: top; }
 tr:nth-child(even) td { background: #f7fbff; }
 a { color: #1a73e8; text-decoration: none; }
 strong { color: #102a43; }
 .cover { border: 1px solid #d6e4f0; border-radius: 16px; padding: 20px; background: linear-gradient(135deg,#f7fbff 0%,#ffffff 55%,#f8fbff 100%); }
 .footer-note { margin-top: 24px; font-size: 8.3pt; color: #64748b; border-top: 1px solid #d9e2ec; padding-top: 8px; }
@media print { h2, h3, h4 { break-after: avoid; } table, blockquote { break-inside: avoid; } }
 </style></head><body><div class="cover"><h1 id="emi-livestream-and-media-workflow-report-for-ari-sardius">EMI Livestream and Media Workflow Report for Ari / Sardius</h1>
 <h2 id="purpose-of-this-first-draft">Purpose of This First Draft</h2>
 <p>This report is a first-draft briefing for a conversation with Ari Burt / Sardius Media. It is intended to give enough context for meaningful strategic advice without asking for a simple gear shopping list.</p>
 <p>The central question is:</p>
 <blockquote>
 <p>How can EMI design the simplest sustainable media workflow that reliably captures services and events, supports multilingual audiences, archives content intelligently, and turns selected teachings into outreach content without overwhelming volunteers?</p>
 </blockquote>
 <h2 id="why-ari-sardius-is-a-good-fit-for-this-conversation">Why Ari / Sardius Is a Good Fit for This Conversation</h2>
 <p>Sardius Media appears to focus on live and on-demand broadcast workflows for mission-driven organizations. Public research found that Sardius works around live streaming, video on demand, distribution workflows, encoder management, analytics, AI-powered discovery/metadata, live subtitles/translations, multi-language experiences, and multi-track interpretation support.</p>
 <p>Ari Burt is listed as a Co-Founder of Sardius Media. Public company context suggests he is best approached as a broadcast workflow and platform strategist rather than only as a camera/video production person.</p>
 <p>For that reason, the most valuable conversation is likely around:</p>
 <ul>
 <li>workflow architecture,</li>
 <li>livestream reliability,</li>
 <li>multilingual delivery,</li>
 <li>automation,</li>
 <li>AI-assisted metadata/search,</li>
 <li>archive structure,</li>
 <li>on-demand content reuse,</li>
 <li>volunteer-sustainable operations,</li>
 <li>when to stay simple and when to professionalize.</li>
 </ul>
 <h2 id="executive-summary">Executive Summary</h2>
 <p>EMI / the Florida local ministry currently livestreams Sunday services and special events through Subsplash. Subsplash also provides the local ministry website at https://florida.emmint.com/ and automatically posts a replay in the app shortly after each livestream ends.</p>
 <p>The current local production setup uses a Canon M50 Mark II, ATEM Mini, iMac, OBS, Zoom, WorshipTools, and a Behringer X18 audio mixer. OBS provides a higher-quality local recording, while Zoom is used as a resilient live video layer and allows phones to join as extra cameras. The team does not currently livestream directly to YouTube or Facebook.</p>
 <p>The system works, but the ministry is in a transition season. Sunday meetings happen in a rented school building, which creates setup/tear-down burden, Wi-Fi dependency, lighting limitations, and limited ability to improve quality. International EMI gatherings add a different challenge: remote locations, inconsistent internet, and multiple language needs.</p>
 <p>The highest-value areas for expert help are:</p>
 <ol>
 <li>Multilingual livestream and in-room translation.</li>
 <li>Reliable livestream architecture for local and international settings.</li>
 <li>Volunteer-friendly mobile production setup.</li>
 <li>Lower-third lyrics/slides instead of full screen-share workflows.</li>
 <li>NAS-first archive, metadata, and searchable media library.</li>
 <li>AI-assisted post-production for clips, captions, summaries, translations, and content reuse.</li>
 </ol>
 <h2 id="ministry-context">Ministry Context</h2>
 <h3 id="current-services-and-events">Current Services and Events</h3>
 <p>EMI currently records or streams:</p>
 <ul>
 <li>Sunday services,</li>
 <li>special events,</li>
 <li>larger EMI family gatherings and international meetings,</li>
 <li>outreach teachings prepared intentionally for public sharing.</li>
 </ul>
 <h3 id="audiences">Audiences</h3>
 <p>The audience is broader than a local church replay audience:</p>
 <ul>
 <li>local Florida congregation,</li>
 <li>remote viewers through Subsplash,</li>
 <li>international EMI-connected ministries and families,</li>
 <li>English and Spanish audiences,</li>
 <li>additional language audiences connected to France, Denmark, Africa, and other regions,</li>
 <li>public outreach audiences through YouTube, Facebook, and The Walking Voice Media.</li>
 </ul>
 <h3 id="publishing-channels">Publishing Channels</h3>
 <p>Current channels/platforms:</p>
 <ul>
 <li>Subsplash livestream and app archive,</li>
 <li>local ministry website through Subsplash: https://florida.emmint.com/,</li>
 <li>The Walking Voice Media YouTube channel: https://www.youtube.com/@TheWalkingVoiceMedia,</li>
 <li>KingdomEMI YouTube channel: https://www.youtube.com/@kingdomemi,</li>
 <li>Facebook page: https://www.facebook.com/kingdomemi/.</li>
 </ul>
 <p>Current policy:</p>
 <ul>
 <li>Every Sunday full service is automatically available through Subsplash.</li>
 <li>YouTube is selective: only publish when a teaching is well prepared and intended for public outreach.</li>
 <li>When a new YouTube teaching is published, create 3–5 short clips per week for YouTube and Facebook.</li>
 <li>Walking Voice Media target cadence: 1–2 outreach pieces per month.</li>
 </ul>
 <h2 id="current-local-sunday-workflow">Current Local Sunday Workflow</h2>
 <h3 id="current-signal-flow">Current Signal Flow</h3>
 <p>Audio path:</p>
 <p><code>Microphones / instruments → Behringer X18 mixer → XLR output → audio interface → iMac / livestream computer → OBS local recording + Zoom/Subsplash live workflow → Subsplash replay/archive</code></p>
 <p>Video path:</p>
 <p><code>Canon M50 Mark II → HDMI → ATEM Mini → iMac / livestream computer → OBS local recording + virtual webcam → Zoom/Subsplash live workflow → Subsplash replay/archive</code></p>
 <p>Flexible camera path:</p>
 <p><code>Phone cameras → Zoom directly → live stream contribution without routing through ATEM/main computer</code></p>
 <p>Lyrics/slides path:</p>
 <p><code>WorshipTools → local screen + Zoom screen share → livestream view, with camera reduced to small window during screen share</code></p>
 <h3 id="equipment-and-software">Equipment and Software</h3>
 <table>
 <thead>
 <tr>
 <th>Category</th>
 <th>Current Tool</th>
 <th>Purpose</th>
 <th>Main Limitation</th>
 </tr>
 </thead>
 <tbody>
 <tr>
 <td>Camera</td>
 <td>Canon M50 Mark II</td>
 <td>Main video feed</td>
 <td>Wired HDMI and setup burden</td>
 </tr>
 <tr>
 <td>Switcher</td>
 <td>ATEM Mini</td>
 <td>Camera ingest</td>
 <td>Audio reliability issues and wired camera constraint</td>
 </tr>
 <tr>
 <td>Computer</td>
 <td>iMac</td>
 <td>OBS, Zoom, livestream operations, X18 control</td>
 <td>Single point of failure</td>
 </tr>
 <tr>
 <td>Recording</td>
 <td>OBS</td>
 <td>High-quality local recording</td>
 <td>Current workflow not always used as direct livestream path</td>
 </tr>
 <tr>
 <td>Live contribution</td>
 <td>Zoom</td>
 <td>Resilient video layer, phone cameras, captions experiments</td>
 <td>Screen-share layout reduces camera view</td>
 </tr>
 <tr>
 <td>Audio</td>
 <td>Behringer X18</td>
 <td>Main audio mix</td>
 <td>Headless; depends on network/software control</td>
 </tr>
 <tr>
 <td>Presentation</td>
 <td>WorshipTools</td>
 <td>Lyrics/slides locally and through Zoom</td>
 <td>Current screen share blocks much of the video</td>
 </tr>
 <tr>
 <td>Archive</td>
 <td>8TB home NAS</td>
 <td>Long-term storage</td>
 <td>Filling up; not well organized or indexed</td>
 </tr>
 <tr>
 <td>Internet</td>
 <td>School Wi-Fi</td>
 <td>Current Sunday connectivity</td>
 <td>Reliability and bandwidth constraints</td>
 </tr>
 </tbody>
 </table>
 <h3 id="team-roles">Team Roles</h3>
 <ul>
 <li>Worship team: sets up audio board and building speaker connections.</li>
 <li>Adolfo: livestream setup lead, audio feed connection, camera/ATEM/computer setup, simple trims, some Final Cut editing.</li>
 <li>Dzidula Boney: lyrics.</li>
 <li>Sara Gianelli: lyrics trainee, livestream computer helper, sometimes translation.</li>
 <li>Sinae Gianelli: camera trainee.</li>
 <li>Gary Collins: previous camera/livestream support; currently less active.</li>
 <li>Brother Gino Gianelli: editing support on Windows, likely using DaVinci Resolve.</li>
 <li>Eli Lastra: overall content creator supervisor and quality reviewer.</li>
 <li>Apostle David: higher-level ministry/message approval when needed.</li>
 </ul>
 <h3 id="current-local-pain-points">Current Local Pain Points</h3>
 <ol>
 <li>The Sunday setup depends heavily on Adolfo.</li>
 <li>The rented school building requires setup and tear-down every week.</li>
 <li>Livestream depends on Wi-Fi.</li>
 <li>The iMac is a single point of failure.</li>
 <li>Lighting is limited because the team cannot fully use the building lights.</li>
 <li>Zoom screen share for lyrics/slides reduces the camera to a small window.</li>
 <li>Wired HDMI camera routing limits camera placement and increases setup time.</li>
 <li>Audio through ATEM has shown brief dropout problems, so the team routes audio separately.</li>
 </ol>
 <h2 id="international-event-workflow-challenge">International Event Workflow Challenge</h2>
 <p>International EMI gatherings are a different problem from the local Sunday workflow.</p>
 <p>Common constraints:</p>
 <ul>
 <li>meetings often happen in remote areas,</li>
 <li>internet reliability varies significantly,</li>
 <li>apostles and leaders travel globally and may not want bulky equipment,</li>
 <li>audiences may need multiple languages at once,</li>
 <li>local in-room translation has worked in some cases but has not been optimal,</li>
 <li>phone/headphone-based access may be ideal in some locations but not universal.</li>
 </ul>
 <p>Desired international translation model:</p>
 <ul>
 <li>When internet and audience devices allow: people connect with their own phone/headphones and choose a language.</li>
 <li>When internet is weak: provide local off-stage translation directly to people in the room.</li>
 <li>Long term: design a hybrid model that can adapt by country, venue, internet quality, and number of languages.</li>
 </ul>
 <h2 id="translation-and-captioning-highest-priority-problem">Translation and Captioning: Highest-Priority Problem</h2>
 <p>Translation is currently the biggest pain point.</p>
 <p>Current state:</p>
 <ul>
 <li>English and Spanish are the main large audiences.</li>
 <li>Human translation still makes sense for English ↔ Spanish.</li>
 <li>Additional languages are needed for connected ministries in France, Denmark, Africa, and other places.</li>
 <li>Zoom Caption Auto-Translation is being tested again and seems better than in the past.</li>
 <li>Automatic captions/translations struggle when both English and Spanish are present in the same audio stream.</li>
 </ul>
 <p>Likely direction:</p>
 <ul>
 <li>Keep human translation for English and Spanish where quality matters most.</li>
 <li>Explore automatic captioning/translation for additional languages.</li>
 <li>Investigate sending a clean English-only feed into the caption/translation system to improve accuracy.</li>
 <li>Determine what tools can provide selectable captions or language experiences during a livestream.</li>
 </ul>
 <p>Key question for Ari / Sardius:</p>
 <blockquote>
 <p>What is the most realistic and reliable multilingual workflow today for a ministry that has both local Sunday services and international events in remote locations?</p>
 </blockquote>
 <h2 id="desired-future-state">Desired Future State</h2>
 <p>The desired future system should be:</p>
 <ul>
 <li>reliable enough for Sunday services,</li>
 <li>mobile enough for a rented school building,</li>
 <li>flexible enough for international events,</li>
 <li>understandable enough for trained volunteers,</li>
 <li>strong enough to produce quality outreach content,</li>
 <li>organized enough to preserve and search years of media,</li>
 <li>simple enough not to overwhelm the team.</li>
 </ul>
 <p>Desired capabilities:</p>
 <ul>
 <li>Lower-third lyrics/slides instead of full Zoom screen share.</li>
 <li>Mobile cart/case setup for fast Sunday deployment.</li>
 <li>Multiple DSLR/mirrorless-style cameras using wireless HDMI.</li>
 <li>Reliable audio path independent of ATEM audio issues.</li>
 <li>Redundancy plan if the main computer fails.</li>
 <li>English/Spanish human translation plus AI captions/translations for additional languages.</li>
 <li>International event playbook for strong internet, weak internet, and hybrid scenarios.</li>
 <li>NAS-first archive with metadata and transcript search.</li>
 <li>AI-assisted workflow for transcription, clip selection, captions, summaries, translations, and social repurposing.</li>
 </ul>
 <h2 id="decision-areas-where-we-need-expert-help">Decision Areas Where We Need Expert Help</h2>
 <h3 id="1-translation-multilingual-experience">1. Translation / Multilingual Experience</h3>
 <p>Questions:</p>
 <ul>
 <li>What is realistic today for live translated captions?</li>
 <li>What is realistic today for multi-language audio or interpretation channels?</li>
 <li>How should we handle English/Spanish human translation while also supporting other languages through AI?</li>
 <li>What should be local/offline vs. internet/cloud-dependent?</li>
 <li>Are there tools that allow selectable captions or language experiences during live streams?</li>
 </ul>
 <h3 id="2-encoding-livestream-reliability">2. Encoding / Livestream Reliability</h3>
 <p>Questions:</p>
 <ul>
 <li>When should we stay with OBS/Zoom/Subsplash?</li>
 <li>When should we consider dedicated encoders, managed broadcast workflows, SRT/RTMP/HLS designs, or Resi-like reliability?</li>
 <li>How should we think about backup internet and backup computer options?</li>
 <li>How can we improve reliability without making the workflow too complicated for volunteers?</li>
 </ul>
 <h3 id="3-volunteer-friendly-mobile-setup">3. Volunteer-Friendly Mobile Setup</h3>
 <p>Questions:</p>
 <ul>
 <li>What should be pre-wired into a mobile cart/case?</li>
 <li>What should stay modular?</li>
 <li>How should power, networking, ATEM/interface, computer, camera receivers, and monitoring be arranged?</li>
 <li>What is the smallest setup that still gives room for quality improvement?</li>
 </ul>
 <h3 id="4-lyrics-slides-lower-thirds">4. Lyrics / Slides / Lower Thirds</h3>
 <p>Questions:</p>
 <ul>
 <li>Should we solve lower-third lyrics with WorshipTools, OBS, Zoom, or a different workflow?</li>
 <li>How can lyrics be visible without sacrificing the camera feed?</li>
 <li>How should preaching slides be handled differently from worship lyrics?</li>
 </ul>
 <h3 id="5-archive-search-media-asset-management">5. Archive / Search / Media Asset Management</h3>
 <p>Questions:</p>
 <ul>
 <li>How should we organize the 8TB NAS media archive?</li>
 <li>What folder and naming convention should we standardize?</li>
 <li>What metadata should be captured from day one?</li>
 <li>What NAS-based tools can provide transcript/quote search?</li>
 <li>How should AI transcription and summary data be stored for long-term reuse?</li>
 </ul>
 <p>Desired searchable fields:</p>
 <ul>
 <li>speaker,</li>
 <li>date,</li>
 <li>event name,</li>
 <li>scripture/reference,</li>
 <li>topic/theme,</li>
 <li>language,</li>
 <li>people in video,</li>
 <li>quote/transcript search.</li>
 </ul>
 <h3 id="6-ai-assisted-post-production">6. AI-Assisted Post-Production</h3>
 <p>Questions:</p>
 <ul>
 <li>What AI tools are mature enough to use now?</li>
 <li>Can AI reliably help identify sermon clips?</li>
 <li>What should be automated vs. reviewed manually?</li>
 <li>How should captions, translations, summaries, thumbnails, titles, and descriptions be generated?</li>
 <li>What review process should protect quality and theological/message accuracy?</li>
 </ul>
 <h2 id="what-we-are-not-asking-for-yet">What We Are Not Asking For Yet</h2>
 <p>We are not primarily asking for a shopping list.</p>
 <p>Before buying more equipment or software, we want to understand:</p>
 <ul>
 <li>the right workflow architecture,</li>
 <li>what should be standardized first,</li>
 <li>what should remain simple,</li>
 <li>what should be automated,</li>
 <li>what should stay manual,</li>
 <li>what purchases should wait until the process is clearer.</li>
 </ul>
 <h2 id="focused-questions-for-ari-sardius">Focused Questions for Ari / Sardius</h2>
 <ol>
 <li>If you were designing this from scratch for a mobile church/ministry, what would you standardize first?</li>
 <li>What should we keep simple and volunteer-friendly versus what should be professionalized?</li>
 <li>What is the best realistic path for multilingual livestream and in-room translation today?</li>
 <li>How would you structure our media archive so it becomes searchable and reusable instead of just stored videos?</li>
 <li>What AI workflows are mature enough to use now for captions, metadata, clips, summaries, and translations?</li>
 <li>At what point does OBS/Zoom/Subsplash stop being enough?</li>
 <li>What equipment/software do churches commonly buy too early?</li>
 <li>What would you measure to know whether the media workflow is improving: stream health, watch time, engagement, clip performance, volunteer load, archive reuse, or something else?</li>
 </ol>
 <h2 id="recommended-first-priorities">Recommended First Priorities</h2>
 <h3 id="priority-1-translation-prototype">Priority 1: Translation Prototype</h3>
 <p>Test a controlled Sunday workflow where only a clean English feed is sent into auto-caption/translation. Compare results against the mixed English/Spanish audio scenario.</p>
 <h3 id="priority-2-lower-third-lyrics-prototype">Priority 2: Lower-Third Lyrics Prototype</h3>
 <p>Test whether WorshipTools, OBS, or another workflow can generate lyrics as lower thirds while preserving the full camera feed.</p>
 <h3 id="priority-3-mobile-cart-case-design">Priority 3: Mobile Cart / Case Design</h3>
 <p>Design a simple pre-wired mobile system for the rented school setting. Include power, computer, ATEM/interface, audio interface, wireless HDMI receivers, network gear, and monitoring.</p>
 <h3 id="priority-4-nas-archive-structure">Priority 4: NAS Archive Structure</h3>
 <p>Create a folder/naming/indexing standard before adding more media. Start with date, event, speaker, language, and transcript fields.</p>
 <h3 id="priority-5-ai-post-production-pilot">Priority 5: AI Post-Production Pilot</h3>
 <p>Choose one strong teaching and test a full pipeline:</p>
 <p><code>recording → transcript → summary → clip candidates → reviewed clips → captions → title/description → YouTube/Facebook/Walking Voice publishing</code></p>
 <h2 id="proposed-attachments-examples-to-add-before-sending">Proposed Attachments / Examples to Add Before Sending</h2>
 <p>Before sharing this report, add links to:</p>
 <ul>
 <li>one recent Subsplash Sunday service replay,</li>
 <li>one strong teaching suitable for public outreach,</li>
 <li>one example where lyrics/screen share reduced video quality,</li>
 <li>one international gathering example if available,</li>
 <li>one short clip or desired example style if available.</li>
 </ul>
 <h2 id="related-working-notes">Related Working Notes</h2>
 <ul>
 <li>Livestream and Video Generation Process</li>
 <li>EMI Media Outreach and YouTube Strategy</li>
 <li>kenya trip 2026</li>
 <li>Technology for the Kingdom of God</li>
 </ul></div><div class="footer-note">Generated from: /home/adolforeyna/brain/projects/livestream_media_system_report_for_ari_sardius.md</div></body></html>
@@ -0,0 +1,41 @@
 from pathlib import Path
 import re, html, sys
 import markdown
 src = Path(sys.argv[1]) if len(sys.argv) > 1 else Path('/home/adolforeyna/brain/projects/livestream_media_system_report_for_ari_sardius.md')
 out_dir = Path('/home/adolforeyna/brain/exports')
 out_dir.mkdir(parents=True, exist_ok=True)
 slug = src.stem
 text = src.read_text(encoding='utf-8')
 text = re.sub(r'^---\n.*?\n---\n\s*', '', text, flags=re.S)
 text = re.sub(r'\[\[([^\]|]+)\|([^\]]+)\]\]', r'\2', text)
 text = re.sub(r'\[\[([^\]]+)\]\]', lambda m: m.group(1).replace('_',' '), text)
 text = re.sub(r'(?m)(^[^\n#][^\n]*:\s*)\n(-\s+)', r'\1\n\n\2', text)
 body = markdown.markdown(text, extensions=['extra','toc','sane_lists','smarty'])
 css = r'''
@page { size: Letter; margin: 0.62in 0.58in; }
 * { box-sizing: border-box; }
 body { font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; color: #1f2933; line-height: 1.48; font-size: 10.4pt; }
 h1 { font-size: 28pt; color: #0f2f4f; margin: 0 0 10px; letter-spacing: -0.03em; padding-bottom: 14px; border-bottom: 5px solid #2f80ed; }
 h2 { font-size: 17pt; color: #0f2f4f; margin-top: 27px; padding: 8px 12px; background: linear-gradient(90deg,#eaf3ff,#ffffff); border-left: 5px solid #2f80ed; break-after: avoid; }
 h3 { font-size: 13pt; color: #164b7a; margin-top: 18px; border-bottom: 1px solid #d6e4f0; padding-bottom: 4px; break-after: avoid; }
 h4 { font-size: 11.5pt; color: #2f5f8f; margin-top: 14px; break-after: avoid; }
 p { margin: 7px 0; }
 ul, ol { margin-top: 5px; padding-left: 22px; }
 li { margin: 3px 0; }
 blockquote { margin: 14px 0; padding: 12px 16px; border-left: 5px solid #f2c94c; background: #fff9e6; color: #3d3200; font-size: 11pt; }
 code { background: #eef4fa; padding: 1px 4px; border-radius: 4px; color: #0b456f; font-family: "SFMono-Regular", Consolas, monospace; font-size: 8.7pt; }
 table { width: 100%; border-collapse: collapse; margin: 12px 0 18px; font-size: 8.2pt; page-break-inside: auto; }
 th { background: #0f2f4f; color: white; text-align: left; padding: 7px 6px; }
 td { border: 1px solid #d9e2ec; padding: 6px; vertical-align: top; }
 tr:nth-child(even) td { background: #f7fbff; }
 a { color: #1a73e8; text-decoration: none; }
 strong { color: #102a43; }
 .cover { border: 1px solid #d6e4f0; border-radius: 16px; padding: 20px; background: linear-gradient(135deg,#f7fbff 0%,#ffffff 55%,#f8fbff 100%); }
 .footer-note { margin-top: 24px; font-size: 8.3pt; color: #64748b; border-top: 1px solid #d9e2ec; padding-top: 8px; }
@media print { h2, h3, h4 { break-after: avoid; } table, blockquote { break-inside: avoid; } }
 '''
 full = f'''<!doctype html><html><head><meta charset="utf-8"><title>{html.escape(src.stem)}</title><style>{css}</style></head><body><div class="cover">{body}</div><div class="footer-note">Generated from: {html.escape(str(src))}</div></body></html>'''
 html_path = out_dir / f'{slug}.html'
 html_path.write_text(full, encoding='utf-8')
 print(html_path)
@@ -3,6 +3,7 @@
 - **[[Projects]]:** Active things we are working on.
  - [[EMI Media Outreach and YouTube Strategy]]: Build an EMI-branded global content outreach system for the message of the Kingdom.
  - [[Livestream and Video Generation Process]]: Document current livestream/video workflow and prepare for media producer advice.
  - [[EMI Livestream and Media Workflow Report for Ari / Sardius]]: Shareable first-draft brief focused on workflow architecture, translation, archive/search, and AI-assisted media production.
  - [[reMarkable Hermes Communication App]]: Tablet/Hermes communication app over reMarkable Paper Pro.
  - [[PARA Brain MCP Server]]: Server-side MCP/search layer for the Reyna family brain.
 - **[[Areas]]:** Ongoing responsibilities and household maintenance.
@@ -0,0 +1,346 @@
 ---
 Date: 2026-06-29
 Author: Hermes
 Tags: [project, emi, media, livestream, report, sardius, ari-burt, workflow]
 ---
 # EMI Livestream and Media Workflow Report for Ari / Sardius
 ## Purpose of This First Draft
 This report is a first-draft briefing for a conversation with Ari Burt / Sardius Media. It is intended to give enough context for meaningful strategic advice without asking for a simple gear shopping list.
 The central question is:
 > How can EMI design the simplest sustainable media workflow that reliably captures services and events, supports multilingual audiences, archives content intelligently, and turns selected teachings into outreach content without overwhelming volunteers?
 ## Why Ari / Sardius Is a Good Fit for This Conversation
 Sardius Media appears to focus on live and on-demand broadcast workflows for mission-driven organizations. Public research found that Sardius works around live streaming, video on demand, distribution workflows, encoder management, analytics, AI-powered discovery/metadata, live subtitles/translations, multi-language experiences, and multi-track interpretation support.
 Ari Burt is listed as a Co-Founder of Sardius Media. Public company context suggests he is best approached as a broadcast workflow and platform strategist rather than only as a camera/video production person.
 For that reason, the most valuable conversation is likely around:
 - workflow architecture,
 - livestream reliability,
 - multilingual delivery,
 - automation,
 - AI-assisted metadata/search,
 - archive structure,
 - on-demand content reuse,
 - volunteer-sustainable operations,
 - when to stay simple and when to professionalize.
 ## Executive Summary
 EMI / the Florida local ministry currently livestreams Sunday services and special events through Subsplash. Subsplash also provides the local ministry website at https://florida.emmint.com/ and automatically posts a replay in the app shortly after each livestream ends.
 The current local production setup uses a Canon M50 Mark II, ATEM Mini, iMac, OBS, Zoom, WorshipTools, and a Behringer X18 audio mixer. OBS provides a higher-quality local recording, while Zoom is used as a resilient live video layer and allows phones to join as extra cameras. The team does not currently livestream directly to YouTube or Facebook.
 The system works, but the ministry is in a transition season. Sunday meetings happen in a rented school building, which creates setup/tear-down burden, Wi-Fi dependency, lighting limitations, and limited ability to improve quality. International EMI gatherings add a different challenge: remote locations, inconsistent internet, and multiple language needs.
 The highest-value areas for expert help are:
 1. Multilingual livestream and in-room translation.
 2. Reliable livestream architecture for local and international settings.
 3. Volunteer-friendly mobile production setup.
 4. Lower-third lyrics/slides instead of full screen-share workflows.
 5. NAS-first archive, metadata, and searchable media library.
 6. AI-assisted post-production for clips, captions, summaries, translations, and content reuse.
 ## Ministry Context
 ### Current Services and Events
 EMI currently records or streams:
 - Sunday services,
 - special events,
 - larger EMI family gatherings and international meetings,
 - outreach teachings prepared intentionally for public sharing.
 ### Audiences
 The audience is broader than a local church replay audience:
 - local Florida congregation,
 - remote viewers through Subsplash,
 - international EMI-connected ministries and families,
 - English and Spanish audiences,
 - additional language audiences connected to France, Denmark, Africa, and other regions,
 - public outreach audiences through YouTube, Facebook, and The Walking Voice Media.
 ### Publishing Channels
 Current channels/platforms:
 - Subsplash livestream and app archive,
 - local ministry website through Subsplash: https://florida.emmint.com/,
 - The Walking Voice Media YouTube channel: https://www.youtube.com/@TheWalkingVoiceMedia,
 - KingdomEMI YouTube channel: https://www.youtube.com/@kingdomemi,
 - Facebook page: https://www.facebook.com/kingdomemi/.
 Current policy:
 - Every Sunday full service is automatically available through Subsplash.
 - YouTube is selective: only publish when a teaching is well prepared and intended for public outreach.
 - When a new YouTube teaching is published, create 3–5 short clips per week for YouTube and Facebook.
 - Walking Voice Media target cadence: 1–2 outreach pieces per month.
 ## Current Local Sunday Workflow
 ### Current Signal Flow
 Audio path:
 `Microphones / instruments → Behringer X18 mixer → XLR output → audio interface → iMac / livestream computer → OBS local recording + Zoom/Subsplash live workflow → Subsplash replay/archive`
 Video path:
 `Canon M50 Mark II → HDMI → ATEM Mini → iMac / livestream computer → OBS local recording + virtual webcam → Zoom/Subsplash live workflow → Subsplash replay/archive`
 Flexible camera path:
 `Phone cameras → Zoom directly → live stream contribution without routing through ATEM/main computer`
 Lyrics/slides path:
 `WorshipTools → local screen + Zoom screen share → livestream view, with camera reduced to small window during screen share`
 ### Equipment and Software
 | Category | Current Tool | Purpose | Main Limitation |
 | --- | --- | --- | --- |
 | Camera | Canon M50 Mark II | Main video feed | Wired HDMI and setup burden |
 | Switcher | ATEM Mini | Camera ingest | Audio reliability issues and wired camera constraint |
 | Computer | iMac | OBS, Zoom, livestream operations, X18 control | Single point of failure |
 | Recording | OBS | High-quality local recording | Current workflow not always used as direct livestream path |
 | Live contribution | Zoom | Resilient video layer, phone cameras, captions experiments | Screen-share layout reduces camera view |
 | Audio | Behringer X18 | Main audio mix | Headless; depends on network/software control |
 | Presentation | WorshipTools | Lyrics/slides locally and through Zoom | Current screen share blocks much of the video |
 | Archive | 8TB home NAS | Long-term storage | Filling up; not well organized or indexed |
 | Internet | School Wi-Fi | Current Sunday connectivity | Reliability and bandwidth constraints |
 ### Team Roles
 - Worship team: sets up audio board and building speaker connections.
 - Adolfo: livestream setup lead, audio feed connection, camera/ATEM/computer setup, simple trims, some Final Cut editing.
 - Dzidula Boney: lyrics.
 - Sara Gianelli: lyrics trainee, livestream computer helper, sometimes translation.
 - Sinae Gianelli: camera trainee.
 - Gary Collins: previous camera/livestream support; currently less active.
 - Brother Gino Gianelli: editing support on Windows, likely using DaVinci Resolve.
 - Eli Lastra: overall content creator supervisor and quality reviewer.
 - Apostle David: higher-level ministry/message approval when needed.
 ### Current Local Pain Points
 1. The Sunday setup depends heavily on Adolfo.
 2. The rented school building requires setup and tear-down every week.
 3. Livestream depends on Wi-Fi.
 4. The iMac is a single point of failure.
 5. Lighting is limited because the team cannot fully use the building lights.
 6. Zoom screen share for lyrics/slides reduces the camera to a small window.
 7. Wired HDMI camera routing limits camera placement and increases setup time.
 8. Audio through ATEM has shown brief dropout problems, so the team routes audio separately.
 ## International Event Workflow Challenge
 International EMI gatherings are a different problem from the local Sunday workflow.
 Common constraints:
 - meetings often happen in remote areas,
 - internet reliability varies significantly,
 - apostles and leaders travel globally and may not want bulky equipment,
 - audiences may need multiple languages at once,
 - local in-room translation has worked in some cases but has not been optimal,
 - phone/headphone-based access may be ideal in some locations but not universal.
 Desired international translation model:
 - When internet and audience devices allow: people connect with their own phone/headphones and choose a language.
 - When internet is weak: provide local off-stage translation directly to people in the room.
 - Long term: design a hybrid model that can adapt by country, venue, internet quality, and number of languages.
 ## Translation and Captioning: Highest-Priority Problem
 Translation is currently the biggest pain point.
 Current state:
 - English and Spanish are the main large audiences.
 - Human translation still makes sense for English ↔ Spanish.
 - Additional languages are needed for connected ministries in France, Denmark, Africa, and other places.
 - Zoom Caption Auto-Translation is being tested again and seems better than in the past.
 - Automatic captions/translations struggle when both English and Spanish are present in the same audio stream.
 Likely direction:
 - Keep human translation for English and Spanish where quality matters most.
 - Explore automatic captioning/translation for additional languages.
 - Investigate sending a clean English-only feed into the caption/translation system to improve accuracy.
 - Determine what tools can provide selectable captions or language experiences during a livestream.
 Key question for Ari / Sardius:
 > What is the most realistic and reliable multilingual workflow today for a ministry that has both local Sunday services and international events in remote locations?
 ## Desired Future State
 The desired future system should be:
 - reliable enough for Sunday services,
 - mobile enough for a rented school building,
 - flexible enough for international events,
 - understandable enough for trained volunteers,
 - strong enough to produce quality outreach content,
 - organized enough to preserve and search years of media,
 - simple enough not to overwhelm the team.
 Desired capabilities:
 - Lower-third lyrics/slides instead of full Zoom screen share.
 - Mobile cart/case setup for fast Sunday deployment.
 - Multiple DSLR/mirrorless-style cameras using wireless HDMI.
 - Reliable audio path independent of ATEM audio issues.
 - Redundancy plan if the main computer fails.
 - English/Spanish human translation plus AI captions/translations for additional languages.
 - International event playbook for strong internet, weak internet, and hybrid scenarios.
 - NAS-first archive with metadata and transcript search.
 - AI-assisted workflow for transcription, clip selection, captions, summaries, translations, and social repurposing.
 ## Decision Areas Where We Need Expert Help
 ### 1. Translation / Multilingual Experience
 Questions:
 - What is realistic today for live translated captions?
 - What is realistic today for multi-language audio or interpretation channels?
 - How should we handle English/Spanish human translation while also supporting other languages through AI?
 - What should be local/offline vs. internet/cloud-dependent?
 - Are there tools that allow selectable captions or language experiences during live streams?
 ### 2. Encoding / Livestream Reliability
 Questions:
 - When should we stay with OBS/Zoom/Subsplash?
 - When should we consider dedicated encoders, managed broadcast workflows, SRT/RTMP/HLS designs, or Resi-like reliability?
 - How should we think about backup internet and backup computer options?
 - How can we improve reliability without making the workflow too complicated for volunteers?
 ### 3. Volunteer-Friendly Mobile Setup
 Questions:
 - What should be pre-wired into a mobile cart/case?
 - What should stay modular?
 - How should power, networking, ATEM/interface, computer, camera receivers, and monitoring be arranged?
 - What is the smallest setup that still gives room for quality improvement?
 ### 4. Lyrics / Slides / Lower Thirds
 Questions:
 - Should we solve lower-third lyrics with WorshipTools, OBS, Zoom, or a different workflow?
 - How can lyrics be visible without sacrificing the camera feed?
 - How should preaching slides be handled differently from worship lyrics?
 ### 5. Archive / Search / Media Asset Management
 Questions:
 - How should we organize the 8TB NAS media archive?
 - What folder and naming convention should we standardize?
 - What metadata should be captured from day one?
 - What NAS-based tools can provide transcript/quote search?
 - How should AI transcription and summary data be stored for long-term reuse?
 Desired searchable fields:
 - speaker,
 - date,
 - event name,
 - scripture/reference,
 - topic/theme,
 - language,
 - people in video,
 - quote/transcript search.
 ### 6. AI-Assisted Post-Production
 Questions:
 - What AI tools are mature enough to use now?
 - Can AI reliably help identify sermon clips?
 - What should be automated vs. reviewed manually?
 - How should captions, translations, summaries, thumbnails, titles, and descriptions be generated?
 - What review process should protect quality and theological/message accuracy?
 ## What We Are Not Asking For Yet
 We are not primarily asking for a shopping list.
 Before buying more equipment or software, we want to understand:
 - the right workflow architecture,
 - what should be standardized first,
 - what should remain simple,
 - what should be automated,
 - what should stay manual,
 - what purchases should wait until the process is clearer.
 ## Focused Questions for Ari / Sardius
 1. If you were designing this from scratch for a mobile church/ministry, what would you standardize first?
 2. What should we keep simple and volunteer-friendly versus what should be professionalized?
 3. What is the best realistic path for multilingual livestream and in-room translation today?
 4. How would you structure our media archive so it becomes searchable and reusable instead of just stored videos?
 5. What AI workflows are mature enough to use now for captions, metadata, clips, summaries, and translations?
 6. At what point does OBS/Zoom/Subsplash stop being enough?
 7. What equipment/software do churches commonly buy too early?
 8. What would you measure to know whether the media workflow is improving: stream health, watch time, engagement, clip performance, volunteer load, archive reuse, or something else?
 ## Recommended First Priorities
 ### Priority 1: Translation Prototype
 Test a controlled Sunday workflow where only a clean English feed is sent into auto-caption/translation. Compare results against the mixed English/Spanish audio scenario.
 ### Priority 2: Lower-Third Lyrics Prototype
 Test whether WorshipTools, OBS, or another workflow can generate lyrics as lower thirds while preserving the full camera feed.
 ### Priority 3: Mobile Cart / Case Design
 Design a simple pre-wired mobile system for the rented school setting. Include power, computer, ATEM/interface, audio interface, wireless HDMI receivers, network gear, and monitoring.
 ### Priority 4: NAS Archive Structure
 Create a folder/naming/indexing standard before adding more media. Start with date, event, speaker, language, and transcript fields.
 ### Priority 5: AI Post-Production Pilot
 Choose one strong teaching and test a full pipeline:
 `recording → transcript → summary → clip candidates → reviewed clips → captions → title/description → YouTube/Facebook/Walking Voice publishing`
 ## Proposed Attachments / Examples to Add Before Sending
 Before sharing this report, add links to:
 - one recent Subsplash Sunday service replay,
 - one strong teaching suitable for public outreach,
 - one example where lyrics/screen share reduced video quality,
 - one international gathering example if available,
 - one short clip or desired example style if available.
 ## Related Working Notes
 - [[Livestream and Video Generation Process]]
 - [[EMI Media Outreach and YouTube Strategy]]
 - [[kenya_trip_2026]]
 - [[Technology for the Kingdom of God]]