Update EMI media livestream planning
This commit is contained in:
aeroreyna
@@ -0,0 +1,743 @@
|
||||
<!doctype html>
|
||||
<html><head><meta charset="utf-8"><title>Livestream and Video Generation Process</title><style>
|
||||
@page { size: Letter; margin: 0.65in 0.62in; }
|
||||
* { box-sizing: border-box; }
|
||||
body { font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; color: #1f2933; line-height: 1.47; font-size: 10.7pt; }
|
||||
h1 { font-size: 27pt; color: #12355b; margin: 0 0 8px 0; letter-spacing: -0.02em; padding-bottom: 12px; border-bottom: 4px solid #2f80ed; }
|
||||
h2 { font-size: 18pt; color: #12355b; margin-top: 28px; padding: 8px 12px; background: linear-gradient(90deg,#eaf3ff,#ffffff); border-left: 5px solid #2f80ed; break-after: avoid; }
|
||||
h3 { font-size: 13.5pt; color: #164b7a; margin-top: 20px; border-bottom: 1px solid #d6e4f0; padding-bottom: 4px; break-after: avoid; }
|
||||
h4 { font-size: 11.8pt; color: #2f5f8f; margin-top: 15px; break-after: avoid; }
|
||||
p { margin: 7px 0; }
|
||||
ul, ol { margin-top: 5px; padding-left: 22px; }
|
||||
li { margin: 3px 0; }
|
||||
blockquote { margin: 12px 0; padding: 10px 14px; border-left: 4px solid #f2c94c; background: #fff9e6; color: #4a3b00; }
|
||||
code { background: #eef4fa; padding: 1px 4px; border-radius: 4px; color: #0b456f; font-family: "SFMono-Regular", Consolas, monospace; font-size: 9pt; }
|
||||
table { width: 100%; border-collapse: collapse; margin: 12px 0 18px; font-size: 8.8pt; page-break-inside: auto; }
|
||||
th { background: #12355b; 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; }
|
||||
hr { border: 0; border-top: 1px solid #d9e2ec; margin: 22px 0; }
|
||||
strong { color: #102a43; }
|
||||
.title-card { border: 1px solid #d6e4f0; border-radius: 14px; padding: 18px; background: linear-gradient(135deg,#f7fbff,#ffffff); margin-bottom: 18px; }
|
||||
.footer-note { margin-top: 28px; font-size: 8.5pt; 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="title-card">
|
||||
<h1 id="livestream-and-video-generation-process">Livestream and Video Generation Process</h1>
|
||||
<p><strong>Prepared for EMI media/livestream planning</strong><br />
|
||||
<strong>Updated:</strong> June 29, 2026</p>
|
||||
<h2 id="purpose">Purpose</h2>
|
||||
<p>Document the Reyna / church media workflow for livestreaming and AI-assisted video generation so it can be reviewed with an important media producer and improved based on their advice.</p>
|
||||
<h2 id="current-goal">Current Goal</h2>
|
||||
<p>Prepare for a meeting with a media producer by capturing:</p>
|
||||
<ul>
|
||||
<li>The current livestream setup and responsibilities.</li>
|
||||
<li>The current video generation / post-production workflow.</li>
|
||||
<li>Pain points and quality gaps.</li>
|
||||
<li>Questions where expert feedback would be most valuable.</li>
|
||||
<li>Follow-up actions after the meeting.</li>
|
||||
</ul>
|
||||
<h2 id="known-context">Known Context</h2>
|
||||
<ul>
|
||||
<li>Adolfo has prior church media experience with Technology for the Kingdom of God, OBS, Subsplash, ChatGPT, Meta AI, and livestream workflows.</li>
|
||||
<li>Prior AV/media planning from kenya trip 2026 included multi-camera recording, dedicated internet for streaming, audio interface usage, and livestream quality/reliability concerns.</li>
|
||||
<li>This project should become the central working note for documenting the current process and producer feedback.</li>
|
||||
</ul>
|
||||
<h2 id="current-media-system-assessment-report-draft-2026-06-27">Current Media System Assessment Report Draft - 2026-06-27</h2>
|
||||
<h3 id="report-type">Report Type</h3>
|
||||
<p>Current-state AV / broadcast media assessment, combining:</p>
|
||||
<ul>
|
||||
<li>AV / broadcast current-state assessment.</li>
|
||||
<li>AV system as-built documentation.</li>
|
||||
<li>Site survey / technical discovery report.</li>
|
||||
<li>AVIXA-style performance verification framing.</li>
|
||||
</ul>
|
||||
<p>Reference: AVIXA <code>Audiovisual Systems Performance Verification</code> standard, Document 10:2013, describes a framework for determining audiovisual system elements, verification timing, criteria/metrics, and reporting procedures.</p>
|
||||
<h3 id="1-executive-summary">1. Executive Summary</h3>
|
||||
<p>The local Florida ministry currently livestreams Sunday services and special events primarily through Subsplash. Subsplash also provides the ministry website at https://florida.emmint.com/ and automatically posts a replay in the app about 5–10 minutes after each livestream ends. The team does not currently livestream directly to YouTube or Facebook.</p>
|
||||
<p>The current mobile production system is built around a Canon M50 Mark II, ATEM Mini, iMac/OBS, Zoom, WorshipTools, and a Behringer X18 audio mixer. OBS is used for high-quality local recording, while Zoom is used as a more resilient live contribution/stream layer, especially because phones can join Zoom as extra cameras and because Zoom tolerates some disconnect/network instability better than the direct OBS path.</p>
|
||||
<p>The strongest current needs are:</p>
|
||||
<ul>
|
||||
<li>reliable multilingual translation/captioning for local and international audiences,</li>
|
||||
<li>better event connectivity strategies for remote international gatherings,</li>
|
||||
<li>lower-third lyrics/slides instead of full Zoom screen share,</li>
|
||||
<li>a faster mobile cart/case setup that can support multiple wireless DSLR/mirrorless cameras,</li>
|
||||
<li>a NAS-based searchable media archive and AI-assisted post-production workflow.</li>
|
||||
</ul>
|
||||
<p>The desired future state is not simply “better livestream quality.” It is a sustainable media system that can serve local Sunday meetings, international EMI gatherings, public outreach, multilingual access, selective YouTube publishing, short-form clips, and long-term searchable media reuse without overwhelming volunteers.</p>
|
||||
<h3 id="2-ministry-use-case">2. Ministry / Use Case</h3>
|
||||
<p>Primary use cases:</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>
|
||||
<p>Audiences:</p>
|
||||
<ul>
|
||||
<li>Local Florida congregation and remote members watching through Subsplash.</li>
|
||||
<li>International EMI-connected ministries and families watching from multiple regions.</li>
|
||||
<li>English and Spanish audiences as the largest recurring language groups.</li>
|
||||
<li>Additional language audiences connected to France, Denmark, Africa, and other EMI regions.</li>
|
||||
<li>Public outreach audiences through The Walking Voice Media, KingdomEMI, YouTube, Facebook, and future short-form content.</li>
|
||||
</ul>
|
||||
<p>Expected outputs:</p>
|
||||
<ul>
|
||||
<li>Automatic full-service replay/archive on Subsplash every Sunday.</li>
|
||||
<li>Selective YouTube publishing when a teaching is prepared and strong enough for outreach.</li>
|
||||
<li>3–5 short clips per week when a YouTube teaching is published.</li>
|
||||
<li>Occasional Facebook posts.</li>
|
||||
<li>1–2 monthly outreach pieces for The Walking Voice Media.</li>
|
||||
<li>Bilingual captions and translated versions when useful/possible.</li>
|
||||
<li>Long-term indexed/searchable archive for future reuse by speaker, topic, scripture, event, and transcript.</li>
|
||||
</ul>
|
||||
<h3 id="3-current-signal-flow">3. Current Signal Flow</h3>
|
||||
<p>Current local Sunday signal flow:</p>
|
||||
<p>Audio chain:
|
||||
<code>Microphones / instruments → Behringer X18 mixer → XLR output → audio interface → iMac / livestream computer → OBS local recording + Zoom/Subsplash live workflow → Subsplash replay/archive → optional trim/edit → future clips/social content</code></p>
|
||||
<p>Video chain:
|
||||
<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:
|
||||
<code>Phone cameras → Zoom directly → live stream contribution without routing through ATEM/main computer</code></p>
|
||||
<p>Lyrics/slides path:
|
||||
<code>WorshipTools → local screen + Zoom screen share → livestream view, with camera reduced to small window during screen share</code></p>
|
||||
<h3 id="4-equipment-inventory">4. Equipment Inventory</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Category</th>
|
||||
<th>Item</th>
|
||||
<th>Model</th>
|
||||
<th>Location</th>
|
||||
<th>Purpose</th>
|
||||
<th>Notes / Problems</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Camera</td>
|
||||
<td>Main camera</td>
|
||||
<td>Canon M50 Mark II</td>
|
||||
<td>Sunday school setup</td>
|
||||
<td>Main video feed</td>
|
||||
<td>Wired HDMI to ATEM; setup/tear-down burden</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Switcher / capture</td>
|
||||
<td>Video switcher</td>
|
||||
<td>ATEM Mini</td>
|
||||
<td>Livestream table</td>
|
||||
<td>Camera ingest into computer</td>
|
||||
<td>Audio through ATEM has been unreliable, with brief dropouts</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Computer / encoder</td>
|
||||
<td>Livestream computer</td>
|
||||
<td>iMac</td>
|
||||
<td>Back/livestream table</td>
|
||||
<td>OBS recording, virtual webcam, Zoom/Subsplash workflow, X18 control</td>
|
||||
<td>Single point of failure; if it fails, stream is lost</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Audio console</td>
|
||||
<td>Headless digital mixer</td>
|
||||
<td>Behringer X18</td>
|
||||
<td>Worship/audio setup</td>
|
||||
<td>Main audio mixing</td>
|
||||
<td>Controlled from livestream computer or laptop on network</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Audio interface</td>
|
||||
<td>XLR-to-computer interface</td>
|
||||
<td>Exact model TBD</td>
|
||||
<td>Livestream table</td>
|
||||
<td>Routes X18 output into computer</td>
|
||||
<td>Used because ATEM lacks desired XLR input and has audio issues</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Presentation</td>
|
||||
<td>Lyrics/slides software</td>
|
||||
<td>WorshipTools</td>
|
||||
<td>Local screen + Zoom share</td>
|
||||
<td>Lyrics/slides for worship/preaching</td>
|
||||
<td>Screen share reduces camera to small window</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Cameras</td>
|
||||
<td>Phone cameras</td>
|
||||
<td>Various phones</td>
|
||||
<td>Flexible placement</td>
|
||||
<td>Extra camera angles through Zoom</td>
|
||||
<td>Useful in mobile/school setup</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Network</td>
|
||||
<td>School Wi-Fi</td>
|
||||
<td>TBD</td>
|
||||
<td>Rented school building</td>
|
||||
<td>Internet for stream and Zoom</td>
|
||||
<td>Current major constraint</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Storage</td>
|
||||
<td>Home NAS</td>
|
||||
<td>8TB</td>
|
||||
<td>Adolfo’s home</td>
|
||||
<td>Long-term media archive</td>
|
||||
<td>Filling up; media not well organized/indexed</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Lighting</td>
|
||||
<td>Building/temporary lighting</td>
|
||||
<td>TBD</td>
|
||||
<td>School building</td>
|
||||
<td>Visual quality</td>
|
||||
<td>Current building lights not available to team; temporary lighting adds overhead</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="5-software-platforms">5. Software / Platforms</h3>
|
||||
<p>Current platforms/software:</p>
|
||||
<ul>
|
||||
<li>Subsplash: primary livestream service, distribution, automatic replay/archive, and ministry website provider.</li>
|
||||
<li>OBS: high-quality local recording and virtual webcam support.</li>
|
||||
<li>Zoom: live video layer, phone camera contribution, translation/captioning experiments, and resilience during disconnects/network instability.</li>
|
||||
<li>WorshipTools: lyrics and slides for local screen and Zoom screen share.</li>
|
||||
<li>YouTube:</li>
|
||||
<li>The Walking Voice Media: newer outreach-focused channel.</li>
|
||||
<li>KingdomEMI: older channel to revive with new content.</li>
|
||||
<li>Facebook: KingdomEMI page.</li>
|
||||
<li>Subsplash editor: simple trims.</li>
|
||||
<li>Final Cut: Adolfo’s occasional edits.</li>
|
||||
<li>DaVinci Resolve: likely used by Brother Gino on Windows.</li>
|
||||
<li>AI editing/transcription tools: desired but not yet selected/tried.</li>
|
||||
<li>NAS-based archive/search software: desired but not yet selected.</li>
|
||||
</ul>
|
||||
<h3 id="6-internet-network">6. Internet / Network</h3>
|
||||
<p>Current local Sunday network:</p>
|
||||
<ul>
|
||||
<li>The church currently meets in a rented school building.</li>
|
||||
<li>Livestream depends on Wi-Fi.</li>
|
||||
<li>Connectivity is a major complication.</li>
|
||||
<li>The stream computer is not on a known dedicated/wired media network at this time.</li>
|
||||
</ul>
|
||||
<p>Home archive network:</p>
|
||||
<ul>
|
||||
<li>Adolfo’s home has 1GB parallel/symmetric internet.</li>
|
||||
<li>Home NAS is the preferred long-term archive location.</li>
|
||||
</ul>
|
||||
<p>International event network:</p>
|
||||
<ul>
|
||||
<li>Larger meetings often happen in remote or less-connected locations: Mexico, small-town hotels, Kenya locations outside city centers, etc.</li>
|
||||
<li>No single internet solution works globally.</li>
|
||||
<li>A cell phone with strong coverage may be useful, but it does not solve multi-language translation and streaming by itself.</li>
|
||||
</ul>
|
||||
<h3 id="7-livestream-workflow">7. Livestream Workflow</h3>
|
||||
<p>Current Sunday workflow:</p>
|
||||
<p>Before service:</p>
|
||||
<ul>
|
||||
<li>Worship team arrives and sets up the X18/audio board and building speaker connections.</li>
|
||||
<li>Adolfo connects the audio feed at the back/livestream table.</li>
|
||||
<li>Adolfo sets up the Canon M50 Mark II on tripod.</li>
|
||||
<li>HDMI is run from the Canon M50 Mark II to the ATEM Mini.</li>
|
||||
<li>ATEM Mini and audio interface are connected to the iMac/livestream setup.</li>
|
||||
<li>WorshipTools is prepared for lyrics/slides.</li>
|
||||
<li>OBS is prepared for local recording and virtual webcam.</li>
|
||||
<li>Zoom/Subsplash workflow is prepared for livestreaming.</li>
|
||||
</ul>
|
||||
<p>During service:</p>
|
||||
<ul>
|
||||
<li>WorshipTools drives lyrics/slides locally and through Zoom screen share.</li>
|
||||
<li>Zoom may receive the ATEM feed directly instead of OBS for reliability.</li>
|
||||
<li>Phones may join Zoom as additional cameras when needed.</li>
|
||||
<li>Audio is mixed from the X18 and routed through the interface to the computer.</li>
|
||||
</ul>
|
||||
<p>After service:</p>
|
||||
<ul>
|
||||
<li>Local OBS recording remains on the iMac.</li>
|
||||
<li>Zoom is not recorded because OBS local recording is higher quality.</li>
|
||||
<li>Subsplash automatically posts the replay/archive in the app within about 5–10 minutes.</li>
|
||||
<li>Simple trims may be done in Subsplash when needed.</li>
|
||||
<li>More intentional edits may be done later in Final Cut or DaVinci.</li>
|
||||
<li>Public/prayer ministry portions may be removed when appropriate before broader public sharing.</li>
|
||||
</ul>
|
||||
<h3 id="8-team-roles">8. Team / Roles</h3>
|
||||
<p>Current roles:</p>
|
||||
<ul>
|
||||
<li>Worship team: audio setup, X18/audio board, building speaker setup.</li>
|
||||
<li>Adolfo: livestream setup lead, audio feed connection, camera/ATEM/computer setup, overall workflow oversight, 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; less active currently due to job changes and transition to the school location.</li>
|
||||
<li>Brother Gino Gianelli: editing support on Windows, likely DaVinci Resolve.</li>
|
||||
<li>Eli Lastra: overall content creator supervisor and quality eye.</li>
|
||||
<li>Apostle David: higher-level ministry/message approval when needed.</li>
|
||||
</ul>
|
||||
<p>Volunteer/staffing risk:</p>
|
||||
<ul>
|
||||
<li>The setup still depends heavily on Adolfo for assembly, routing, and troubleshooting.</li>
|
||||
<li>Sara sometimes has split attention between translation and media support.</li>
|
||||
<li>More training and a simplified mobile setup would reduce fragility.</li>
|
||||
</ul>
|
||||
<h3 id="9-current-quality-pain-points">9. Current Quality / Pain Points</h3>
|
||||
<h4 id="1-translation-multilingual-access">1) Translation / Multilingual Access</h4>
|
||||
<ul>
|
||||
<li>Biggest current pain point.</li>
|
||||
<li>Current system depends heavily on human translation.</li>
|
||||
<li>Main languages for local Florida livestreams are English and Spanish, but the meetings are watched globally.</li>
|
||||
<li>EMI-connected ministries include France, Denmark, Africa, and other regions that require additional languages.</li>
|
||||
<li>No clearly reliable translation tool/workflow has been found yet.</li>
|
||||
<li>Zoom Caption Auto-Translation is being tried again and appears better than it was the previous September, but still needs validation.</li>
|
||||
<li>Need a reliable structure for bigger events and family gatherings, not only Sunday services.</li>
|
||||
<li>Possible direction: multiple microphones/headsets/channels so people can connect locally and receive translation in their language.</li>
|
||||
</ul>
|
||||
<h4 id="sunday-translation-target-good-enough-standard">Sunday Translation Target / “Good Enough” Standard</h4>
|
||||
<ul>
|
||||
<li>Technology likely has advanced enough for real-time or near-real-time automatic captioning with translation to provide useful caption quality.</li>
|
||||
<li>The missing piece is a known product/workflow that lets viewers select translated captions directly on the livestream in real time.</li>
|
||||
<li>For local viewers, captions alone may feel like a heavy reading experience compared with hearing translation; audio translation is still preferable when possible.</li>
|
||||
<li>Because English and Spanish are both large audience groups, live human translation still makes sense for English ↔ Spanish.</li>
|
||||
<li>For other languages, automatic captioning/translation would be very valuable.</li>
|
||||
<li>Current issue: when both English and Spanish are present in the same audio stream, automatic captioning/translation tends to struggle with language detection and accuracy.</li>
|
||||
<li>Possible fix: send only English into the automatic captioning/translation system. The church has the capability to route this, but it has not yet had the time/investment to make it reliable.</li>
|
||||
</ul>
|
||||
<h4 id="2-remote-international-event-connectivity">2) Remote / International Event Connectivity</h4>
|
||||
<ul>
|
||||
<li>Bigger meetings are often in remote areas around the world, such as Mexico, small-town hotels, or Kenya locations away from city centers.</li>
|
||||
<li>Internet reliability varies by event and location.</li>
|
||||
<li>There is no single connectivity solution that works for all events.</li>
|
||||
<li>Apostles and leaders travel globally, so bulky equipment may not be practical.</li>
|
||||
<li>A cell phone with strong coverage may help, but would not be enough by itself for five-language translation and streaming directly to participants’ phones.</li>
|
||||
<li>At the Kenya family gathering, local in-room translation was done simultaneously; it worked somewhat but was not optimal.</li>
|
||||
</ul>
|
||||
<h4 id="international-event-translation-target">International Event Translation Target</h4>
|
||||
<ul>
|
||||
<li>Preferred experience for most in-person attendees: participants connect with their own device and headphones, then choose the language they need.</li>
|
||||
<li>This may not be viable in every nation or setting, but those situations may be the exception rather than the rule.</li>
|
||||
<li>For events without strong internet, the ideal backup/alternative is local off-stage translation provided directly to people in the room.</li>
|
||||
<li>The long-term solution likely needs both modes:</li>
|
||||
<li>internet/device-based language access when connectivity and audience devices allow it,</li>
|
||||
<li>local/offline translation distribution for remote or low-connectivity events.</li>
|
||||
</ul>
|
||||
<h4 id="3-mobile-setup-tear-down-burden">3) Mobile Setup / Tear-Down Burden</h4>
|
||||
<ul>
|
||||
<li>Local Sunday setup currently requires many hands and significant setup/tear-down time because the church rents/uses a school building.</li>
|
||||
<li>The team hopes this will be solved once there is a dedicated building.</li>
|
||||
<li>In the meantime, the goal is a mobile setup that can be deployed quickly.</li>
|
||||
<li>The current mobile setup works, but leaves little margin to improve quality.</li>
|
||||
</ul>
|
||||
<h4 id="4-lyrics-slides-presentation-limitation">4) Lyrics / Slides Presentation Limitation</h4>
|
||||
<ul>
|
||||
<li>In Zoom, screen sharing lyrics/slides makes the camera video a small square in the top-right corner.</li>
|
||||
<li>This is acceptable for worship when lyrics are the priority, but it weakens the video presentation.</li>
|
||||
<li>Ideal future state: lower-third lyrics or other overlay where the full video remains visible and lyrics appear at the bottom.</li>
|
||||
<li>Need to explore whether WorshipTools can support this better, or whether more professional presentation software is needed.</li>
|
||||
<li>There is significant room to improve how material is presented, not only the video stream itself.</li>
|
||||
</ul>
|
||||
<h4 id="5-local-lighting-visual-quality">5) Local Lighting / Visual Quality</h4>
|
||||
<ul>
|
||||
<li>Lighting is a local pain point.</li>
|
||||
<li>The school building has lights, but the church has not been allowed to use them at this time.</li>
|
||||
<li>Adding temporary lights does not currently look great and adds setup overhead.</li>
|
||||
<li>Tripods, lights, and similar gear increase the burden because everything must be set up and taken down the same day.</li>
|
||||
</ul>
|
||||
<h4 id="local-sunday-next-improvements">Local Sunday Next Improvements</h4>
|
||||
<ul>
|
||||
<li>Highest-priority local improvement: lower-third lyrics instead of Zoom screen share, so the main video remains visible while lyrics appear at the bottom.</li>
|
||||
<li>Second major local improvement: a mobile cart/case setup that allows quick setup/tear-down and supports multiple wireless cameras.</li>
|
||||
<li>Desired wireless camera direction: more DSLR/mirrorless-style cameras, connected using wireless HDMI rather than long HDMI cable runs back to the ATEM Mini.</li>
|
||||
<li>Motivation: the current wired setup requires power and HDMI cabling from camera positions to the ATEM Mini, which adds setup burden and limits camera placement.</li>
|
||||
<li>Desired outcome: reduce setup burden while improving visual quality and flexibility in the rented school environment.</li>
|
||||
</ul>
|
||||
<h3 id="10-recording-archive-post-production">10. Recording / Archive / Post-Production</h3>
|
||||
<p>Current recording/archive pattern:</p>
|
||||
<ul>
|
||||
<li>OBS records locally on the iMac used for livestream/transmission.</li>
|
||||
<li>Zoom is not recorded because the OBS recording is higher quality.</li>
|
||||
<li>Subsplash automatically records and publishes the livestream replay in the app about 5–10 minutes after the service.</li>
|
||||
<li>Subsplash replay is the default full-service public archive for the congregation.</li>
|
||||
<li>Simple trims are done in the Subsplash editor when needed.</li>
|
||||
<li>Adolfo occasionally edits in Final Cut.</li>
|
||||
<li>Brother Gino edits on Windows, likely in DaVinci Resolve.</li>
|
||||
</ul>
|
||||
<p>Current post-production pattern:</p>
|
||||
<ul>
|
||||
<li>Editing is done only when needed for normal services, especially to remove empty spaces, non-public sections, or personal prayer/ministry time.</li>
|
||||
<li>YouTube is selective: publish only well-prepared teachings intended for public outreach.</li>
|
||||
<li>When a teaching is published to YouTube, the goal is to create 3–5 short clips per week from that content for YouTube and Facebook.</li>
|
||||
<li>Walking Voice Media should receive 1–2 outreach pieces per month.</li>
|
||||
</ul>
|
||||
<p>Current archive gap:</p>
|
||||
<ul>
|
||||
<li>Long-term files live on the 8TB home NAS, but the archive is not well organized or indexed.</li>
|
||||
<li>Needed metadata/search: speaker, date, event name, scripture/reference, topic/theme, language, people in video, and quote/transcript search.</li>
|
||||
<li>Needed next design: folder structure, naming convention, transcript/indexing workflow, backup/storage growth plan, and NAS-based media software evaluation.</li>
|
||||
</ul>
|
||||
<h3 id="11-desired-future-state">11. Desired Future State</h3>
|
||||
<p>We want a simple, reliable, volunteer-friendly workflow that captures services, streams them consistently, supports multilingual audiences, archives content cleanly, and makes it easy to create useful short-form outreach content afterward without overwhelming the team.</p>
|
||||
<p>Desired future capabilities:</p>
|
||||
<ul>
|
||||
<li>Lower-third lyrics/slides instead of full Zoom screen share so the main video remains visible.</li>
|
||||
<li>Mobile cart/case setup that reduces Sunday setup/tear-down time.</li>
|
||||
<li>Multiple DSLR/mirrorless-style cameras using wireless HDMI rather than long cable runs to the ATEM Mini.</li>
|
||||
<li>Reliable English/Spanish human translation where needed, plus automatic captions/translations for additional languages.</li>
|
||||
<li>International event model with both device/headphone-based language access and local/offline translation distribution when internet is weak.</li>
|
||||
<li>NAS-first media archive with indexing by speaker, date, event, scripture, topic, language, people, and transcript/quote search.</li>
|
||||
<li>AI-assisted editing workflow for clip discovery, captions, translation, quote graphics, and social repurposing.</li>
|
||||
<li>Clear publishing lanes: Subsplash for every Sunday replay, YouTube only for strong outreach-ready teachings, Shorts/Facebook clips when YouTube content is published, and 1–2 monthly Walking Voice Media outreach pieces.</li>
|
||||
</ul>
|
||||
<p>Recommended workstreams:</p>
|
||||
<h4 id="workstream-1-translation-and-captions">Workstream 1: Translation and Captions</h4>
|
||||
<ul>
|
||||
<li>Test Zoom Caption Auto-Translation with controlled single-language audio input.</li>
|
||||
<li>Design an English-only feed into automatic caption/translation tools to improve accuracy.</li>
|
||||
<li>Keep human English ↔ Spanish translation for major audience needs.</li>
|
||||
<li>Research livestream-compatible selectable captions and multi-language audio/caption solutions.</li>
|
||||
<li>Define separate patterns for Sunday services vs. major international gatherings.</li>
|
||||
</ul>
|
||||
<h4 id="workstream-2-local-sunday-mobile-production-upgrade">Workstream 2: Local Sunday Mobile Production Upgrade</h4>
|
||||
<ul>
|
||||
<li>Design a mobile cart/case that contains or pre-wires the iMac/laptop, ATEM/interface, power, networking, and cable management.</li>
|
||||
<li>Evaluate wireless HDMI options for DSLR/mirrorless cameras.</li>
|
||||
<li>Decide whether to keep ATEM Mini as central switcher or move toward another mobile switching/encoding model.</li>
|
||||
<li>Reduce single-person dependency by documenting setup steps and training Sara/Sinae/Gary or other volunteers.</li>
|
||||
</ul>
|
||||
<h4 id="workstream-3-lyrics-slides-presentation">Workstream 3: Lyrics / Slides Presentation</h4>
|
||||
<ul>
|
||||
<li>Investigate WorshipTools lower-third output or alternative presentation workflows.</li>
|
||||
<li>Evaluate whether OBS can composite lyrics over video while still feeding Zoom/Subsplash reliably.</li>
|
||||
<li>Decide whether a more professional presentation system is needed for lyrics, scriptures, and teaching slides.</li>
|
||||
</ul>
|
||||
<h4 id="workstream-4-archive-and-media-asset-management">Workstream 4: Archive and Media Asset Management</h4>
|
||||
<ul>
|
||||
<li>Design a NAS folder and naming standard for originals, edits, exports, thumbnails, captions, and project files.</li>
|
||||
<li>Evaluate NAS-based media asset management/search tools.</li>
|
||||
<li>Prioritize transcript/quote search and metadata fields: speaker, date, event, scripture, topic, language, people.</li>
|
||||
<li>Plan for storage growth because the 8TB NAS is filling up.</li>
|
||||
</ul>
|
||||
<h4 id="workstream-5-ai-assisted-post-production">Workstream 5: AI-Assisted Post-Production</h4>
|
||||
<ul>
|
||||
<li>Evaluate AI tools for transcription, clip selection, caption generation, translation, short-form repurposing, and quote graphics.</li>
|
||||
<li>Define a standard path from Sunday recording → transcript → selected clips → review → export → YouTube/Facebook/Walking Voice.</li>
|
||||
<li>Keep approval simple: Adolfo + Eli for most content, Apostle David when higher-level ministry/message approval is needed.</li>
|
||||
</ul>
|
||||
<h3 id="12-questions-for-ari-sardius">12. Questions for Ari / Sardius</h3>
|
||||
<ul>
|
||||
<li>What are the top 3 improvements you would prioritize?</li>
|
||||
<li>Is our biggest bottleneck audio, video, internet, workflow, or staffing?</li>
|
||||
<li>What should we standardize first?</li>
|
||||
<li>What should we avoid buying too early?</li>
|
||||
<li>What would a sustainable small-church media workflow look like?</li>
|
||||
<li>How should we think about archiving and metadata from day one?</li>
|
||||
<li>When is OBS enough, and when should we consider a dedicated encoder/platform?</li>
|
||||
</ul>
|
||||
<h2 id="current-livestream-process">Current Livestream Process</h2>
|
||||
<h3 id="services-events-covered">Services / Events Covered</h3>
|
||||
<ul>
|
||||
<li>Sunday services.</li>
|
||||
<li>Special events.</li>
|
||||
</ul>
|
||||
<h3 id="current-livestream-distribution-platforms">Current Livestream / Distribution Platforms</h3>
|
||||
<ul>
|
||||
<li>Primary livestream service: Subsplash.</li>
|
||||
<li>Subsplash is also used for distribution.</li>
|
||||
<li>Subsplash also provides the ministry website used for the local ministry: https://florida.emmint.com/</li>
|
||||
<li>Current YouTube channels:</li>
|
||||
<li>https://www.youtube.com/@TheWalkingVoiceMedia — newer channel dedicated to outreach.</li>
|
||||
<li>https://www.youtube.com/@kingdomemi — older channel that should be revived with new content.</li>
|
||||
<li>Facebook page: https://www.facebook.com/kingdomemi/</li>
|
||||
<li>Current livestream destinations: not livestreaming directly to YouTube or Facebook at this time.</li>
|
||||
</ul>
|
||||
<h3 id="current-production-setup">Current Production Setup</h3>
|
||||
<ul>
|
||||
<li>Main camera: Canon M50 Mark II connected via HDMI to an ATEM Mini.</li>
|
||||
<li>ATEM Mini feeds the main livestream computer.</li>
|
||||
<li>OBS runs on the main computer to:</li>
|
||||
<li>record locally,</li>
|
||||
<li>set/provide the virtual webcam,</li>
|
||||
<li>support higher-resolution 1080 workflow when conditions allow.</li>
|
||||
<li>Current Zoom workflow streams directly from the ATEM instead of OBS because it has proven more reliable during disconnects or network instability; if there are issues, the Zoom stream does not always drop completely.</li>
|
||||
<li>If the main computer fails, the stream is lost entirely.</li>
|
||||
</ul>
|
||||
<h3 id="zoom-flexible-camera-workflow">Zoom / Flexible Camera Workflow</h3>
|
||||
<ul>
|
||||
<li>Zoom is used as part of the livestream workflow.</li>
|
||||
<li>Phones are sometimes used as cameras directly through Zoom so their video can be included in the livestream without physically routing the phone camera through the main computer.</li>
|
||||
<li>This became more important after changing locations to a rented school building for Sunday meetings.</li>
|
||||
<li>In the previous/location-stable setup, connectivity was more reliable and multiple cameras were connected to the ATEM Mini.</li>
|
||||
<li>Direct livestreaming through OBS can push resolution to 1080, but the current rented-school setup and Wi-Fi limitations have made that harder to sustain.</li>
|
||||
</ul>
|
||||
<h3 id="current-internet-location-constraint">Current Internet / Location Constraint</h3>
|
||||
<ul>
|
||||
<li>Sunday meetings are currently in a school building.</li>
|
||||
<li>Livestream is currently dependent on Wi-Fi.</li>
|
||||
<li>Connectivity is a major complication and still needs a better solution.</li>
|
||||
</ul>
|
||||
<h3 id="current-audio-chain">Current Audio Chain</h3>
|
||||
<ul>
|
||||
<li>Mixer: Behringer X18-style headless mixer board, controlled through software rather than physical board controls.</li>
|
||||
<li>The X18 is controlled from the same computer that runs the livestream, or from any laptop connected to the network.</li>
|
||||
<li>Audio output path: X18 mixer → XLR cable → audio interface → main computer.</li>
|
||||
<li>XLR/interface path is used because the ATEM Mini does not provide the needed XLR input.</li>
|
||||
<li>The ATEM Mini has also had audio reliability issues, including brief audio dropouts of about a second, so it has not been reliable enough as the main audio path.</li>
|
||||
</ul>
|
||||
<h3 id="graphics-lyrics-slides-workflow">Graphics / Lyrics / Slides Workflow</h3>
|
||||
<ul>
|
||||
<li>Software used: WorshipTools — https://www.worshiptools.com/en-us</li>
|
||||
<li>WorshipTools is used locally to show lyrics on the in-room screen.</li>
|
||||
<li>Lyrics are also shared into Zoom through screen sharing.</li>
|
||||
<li>During worship, the priority is congregational participation, so the livestream often favors the shared lyrics even though this makes the camera shot very small.</li>
|
||||
<li>During preaching, slides are also shared through WorshipTools / screen sharing when needed, but usually only for short sections so the video is not visually reduced for too long.</li>
|
||||
<li>The local OBS recording does not include the Zoom screen-share layout, which preserves a higher-quality camera video for later editing.</li>
|
||||
</ul>
|
||||
<h3 id="recording-archive-post-service-workflow">Recording / Archive / Post-Service Workflow</h3>
|
||||
<ul>
|
||||
<li>At the end of Sunday meeting, the team has a local OBS recording on the iMac used for the livestream/transmission.</li>
|
||||
<li>Zoom is not recorded because the OBS recording is better quality.</li>
|
||||
<li>The Subsplash livestream is also recorded automatically.</li>
|
||||
<li>Subsplash automatically posts the livestream recording as an event/archive in the app, usually available to everyone about 5–10 minutes after the livestream ends.</li>
|
||||
<li>This gives the ministry an automatic public replay without extra manual publishing steps.</li>
|
||||
<li>Afterward, editing is done only when required, such as:</li>
|
||||
<li>removing empty spaces,</li>
|
||||
<li>removing sections that should not remain public,</li>
|
||||
<li>trimming personal prayer/ministry time at the end when people are prayed for.</li>
|
||||
</ul>
|
||||
<h3 id="team-roles-sunday-responsibilities">Team Roles / Sunday Responsibilities</h3>
|
||||
<ul>
|
||||
<li>Worship team:</li>
|
||||
<li>Handles audio setup in the morning.</li>
|
||||
<li>Sets up the X18/audio board and makes the required sound connections.</li>
|
||||
<li>Uses the school building’s speakers for in-room sound.</li>
|
||||
<li>Adolfo:</li>
|
||||
<li>Connects the audio feed at the back table where the livestream computer is located.</li>
|
||||
<li>Sets up the Canon M50 Mark II on the tripod.</li>
|
||||
<li>Runs HDMI from the Canon M50 Mark II to the ATEM Mini.</li>
|
||||
<li>Connects/places the ATEM Mini with the livestream interface setup.</li>
|
||||
<li>Oversees the livestream computer/workflow.</li>
|
||||
<li>Dzidula Boney:</li>
|
||||
<li>Runs lyrics.</li>
|
||||
<li>Sara Gianelli:</li>
|
||||
<li>Trainee for lyrics.</li>
|
||||
<li>Helps on the livestream computer.</li>
|
||||
<li>Sometimes translates, so she may split attention between translation and media support.</li>
|
||||
<li>Sinae Gianelli:</li>
|
||||
<li>Camera trainee.</li>
|
||||
<li>Gary Collins:</li>
|
||||
<li>Previously helped with cameras and livestream.</li>
|
||||
<li>Currently less active because of job changes and the transition to the school location, but should still be considered a possible support person.</li>
|
||||
<li>Brother Gino Gianelli:</li>
|
||||
<li>Helps with editing.</li>
|
||||
<li>Eli Lastra:</li>
|
||||
<li>Overall content creator supervisor.</li>
|
||||
<li>Provides the eye for quality and content standards.</li>
|
||||
</ul>
|
||||
<h3 id="remaining-areas-to-capture">Remaining Areas to Capture</h3>
|
||||
<ul>
|
||||
<li>Exact computer/device model and specs.</li>
|
||||
<li>Exact audio interface model.</li>
|
||||
<li>Number of microphones/instruments/audio sources normally mixed.</li>
|
||||
<li>Local OBS recording settings and file naming/storage pattern.</li>
|
||||
<li>Whether edited versions replace the Subsplash archive or are used separately.</li>
|
||||
<li>Pre-service checklist and post-service checklist.</li>
|
||||
</ul>
|
||||
<h2 id="current-video-generation-process">Current Video Generation Process</h2>
|
||||
<h3 id="desired-outputs-from-each-sunday-event">Desired Outputs From Each Sunday / Event</h3>
|
||||
<p>The desired post-production system should be able to create all of the following from each Sunday service or special event:</p>
|
||||
<ul>
|
||||
<li>Full sermon/service archive.</li>
|
||||
<li>Sermon clips and short-form videos.</li>
|
||||
<li>Quote graphics.</li>
|
||||
<li>Bilingual captions.</li>
|
||||
<li>Translated versions when useful/possible.</li>
|
||||
<li>YouTube uploads.</li>
|
||||
<li>Facebook posts.</li>
|
||||
<li>Announcement videos.</li>
|
||||
<li>Weekly outreach content for The Walking Voice Media.</li>
|
||||
</ul>
|
||||
<h3 id="current-editing-content-creation-tools">Current Editing / Content Creation Tools</h3>
|
||||
<ul>
|
||||
<li>Adolfo:</li>
|
||||
<li>Uses the Subsplash editor for simple trims.</li>
|
||||
<li>Uses Final Cut for some edits.</li>
|
||||
<li>Currently does relatively few edits personally.</li>
|
||||
<li>Brother Gino Gianelli:</li>
|
||||
<li>Works on Windows.</li>
|
||||
<li>Likely uses DaVinci Resolve.</li>
|
||||
<li>Desired direction:</li>
|
||||
<li>Explore shifting some editing work to AI-assisted editing.</li>
|
||||
<li>AI editing has not been tried yet in this workflow.</li>
|
||||
</ul>
|
||||
<h3 id="content-review-approval">Content Review / Approval</h3>
|
||||
<ul>
|
||||
<li>Most content is reviewed/approved by Adolfo and Eli Lastra.</li>
|
||||
<li>Apostle David, head of the international ministry, is included sometimes when the content needs higher-level ministry/message approval.</li>
|
||||
</ul>
|
||||
<h3 id="publishing-goals-cadence">Publishing Goals / Cadence</h3>
|
||||
<ul>
|
||||
<li>Every Sunday full service is published on Subsplash automatically after the livestream.</li>
|
||||
<li>YouTube publishing is selective: only publish when the content is strong enough.</li>
|
||||
<li>When a new YouTube piece is published, create 3–5 Shorts per week from that content, distributed to both YouTube and Facebook.</li>
|
||||
<li>Facebook posts are occasional outside of the shorts flow.</li>
|
||||
<li>The Walking Voice Media target cadence: 1–2 outreach pieces per month.</li>
|
||||
</ul>
|
||||
<h3 id="youtube-selection-standard">YouTube Selection Standard</h3>
|
||||
<ul>
|
||||
<li>A message is strong enough for YouTube when it is a well-prepared teaching with the clear intention of being shared publicly for outreach.</li>
|
||||
<li>Default assumption: ordinary full Sunday services remain available through Subsplash; YouTube is for intentional public/outreach content.</li>
|
||||
</ul>
|
||||
<h3 id="storage-archive">Storage / Archive</h3>
|
||||
<ul>
|
||||
<li>Current long-term storage is the NAS at Adolfo’s home.</li>
|
||||
<li>NAS capacity: 8TB.</li>
|
||||
<li>The NAS is currently filling up.</li>
|
||||
<li>Home internet is 1GB parallel/symmetric internet, making the home NAS a practical central archive location.</li>
|
||||
<li>Current media is not well organized and/or indexed.</li>
|
||||
<li>Need future storage plan because the current NAS is filling up.</li>
|
||||
<li>The team is interested in potential software solutions for media organization, indexing, search, and archive management.</li>
|
||||
</ul>
|
||||
<h3 id="desired-media-index-search-fields">Desired Media Index / Search Fields</h3>
|
||||
<p>The media archive should make it easy to find content by:</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 the video.</li>
|
||||
<li>Quote/transcript search.</li>
|
||||
</ul>
|
||||
<h3 id="archive-system-preference">Archive System Preference</h3>
|
||||
<ul>
|
||||
<li>Preferred archive/search system should be NAS-based.</li>
|
||||
<li>Local/private NAS storage is the desired primary home for originals, edited exports, and searchable/indexed media data.</li>
|
||||
<li>Cloud tools may still be evaluated for publishing or specific workflows, but the archive preference is NAS-first.</li>
|
||||
</ul>
|
||||
<h3 id="remaining-areas-to-capture_1">Remaining Areas to Capture</h3>
|
||||
<ul>
|
||||
<li>Source material: sermon recordings, livestream downloads, clips, photos, scripts.</li>
|
||||
<li>Specific AI tools to evaluate for transcription, clip selection, captions, and social repurposing.</li>
|
||||
<li>Editing workflow: clipping, captions, color/audio cleanup, branding, export presets.</li>
|
||||
<li>Output formats: short clips, reels, sermon excerpts, announcement videos, thumbnails.</li>
|
||||
<li>Publishing details: descriptions, hashtags, metadata.</li>
|
||||
<li>Exact folder/naming convention for originals, edited exports, thumbnails/graphics, and project files.</li>
|
||||
</ul>
|
||||
<h2 id="pain-points-open-questions">Pain Points / Open Questions</h2>
|
||||
<ul>
|
||||
<li>What parts of the livestream currently feel least professional?</li>
|
||||
<li>Are audio levels, room sound, or mix quality limiting the final video quality?</li>
|
||||
<li>Is the camera setup strong enough for both livestream and edited clips?</li>
|
||||
<li>Should we optimize for live quality, post-production quality, or both?</li>
|
||||
<li>What is the best repeatable workflow for turning one service into multiple short clips?</li>
|
||||
<li>How should branding, thumbnails, captions, and intro/outro templates be standardized?</li>
|
||||
<li>What tools or roles would make the biggest improvement without overcomplicating the volunteer team?</li>
|
||||
</ul>
|
||||
<h2 id="questions-for-media-producer">Questions for Media Producer</h2>
|
||||
<ul>
|
||||
<li>Based on our current setup, what are the top 3 improvements you would prioritize first?</li>
|
||||
<li>What should a small church media workflow look like if it needs to be sustainable for volunteers?</li>
|
||||
<li>What minimum equipment or process changes would noticeably improve livestream quality?</li>
|
||||
<li>How would you structure a repeatable sermon-to-social-clips workflow?</li>
|
||||
<li>What examples should we study for livestream quality, editing style, thumbnails, and short-form clips?</li>
|
||||
<li>What metrics should we track to know whether media quality and reach are improving?</li>
|
||||
<li>What should we avoid spending time or money on right now?</li>
|
||||
</ul>
|
||||
<h2 id="meeting-notes">Meeting Notes</h2>
|
||||
<p><em>To be filled during or after the producer meeting.</em></p>
|
||||
<h2 id="sardius-media-research-2026-06-20">Sardius Media Research - 2026-06-20</h2>
|
||||
<p>Context from Adolfo: During time in Kansas City, the family met one of the co-founders of Sardius Media. Adolfo confirmed the person is <strong>Ari Burt</strong>, listed on the official Sardius site as Co-Founder.</p>
|
||||
<h3 id="prior-mentions-in-brain">Prior Mentions in Brain</h3>
|
||||
<ul>
|
||||
<li>Search of <code>~/brain</code> for Sardius, Sardius Media, Art Burt, Ari Burt, and Kansas City found no prior direct mention of them.</li>
|
||||
</ul>
|
||||
<h3 id="company-snapshot">Company Snapshot</h3>
|
||||
<ul>
|
||||
<li>Website: https://sardiusmedia.com</li>
|
||||
<li>Focus: live and on-demand broadcast workflows for mission-driven organizations.</li>
|
||||
<li>Positioning: “Simplifying live and on-demand workflows for mission-driven broadcasters.”</li>
|
||||
<li>Based in Kansas City, with team members across North and South America.</li>
|
||||
<li>States 10+ years of media delivery experience for web, mobile, and TV.</li>
|
||||
<li>Contact listed on site: 816-727-3487; sales@sardius.media; info@sardius.media.</li>
|
||||
</ul>
|
||||
<h3 id="leadership-listed-on-official-site">Leadership Listed on Official Site</h3>
|
||||
<ul>
|
||||
<li>Jason Shore — Co-Founder & CEO</li>
|
||||
<li>Ari Burt — Co-Founder</li>
|
||||
<li>Mike Read — Co-Founder & CTO</li>
|
||||
<li>Jono Hall — COO</li>
|
||||
<li>Joshua Ruff — CDO</li>
|
||||
</ul>
|
||||
<h3 id="ari-burt-research">Ari Burt Research</h3>
|
||||
<ul>
|
||||
<li>Identity confirmed from the official Sardius Media About page: <strong>Ari Burt — Co-Founder</strong>.</li>
|
||||
<li>Publicly visible official bio detail is limited; the site lists his role but does not provide a long personal biography.</li>
|
||||
<li>Official site context implies he is part of Sardius’ founding leadership team for a Kansas City-based, mission-driven broadcast technology company.</li>
|
||||
<li>LinkedIn company page context for Sardius Media: Online Audio and Video Media; company size 11-50; privately held; founded 2014; specialties listed as live streaming and video on demand; primary location listed as 1401 E 104 St #103, Kansas City, MO 64131.</li>
|
||||
<li>LinkedIn company updates mention <strong>Jason Shore + Ari Burt</strong> speaking at a Backblaze + Qencode panel at NAB Show 2026, tied to media workflows, cloud storage, AI media, video AI, streaming, and media delivery.</li>
|
||||
<li>This suggests Ari is not only an owner/co-founder but also involved enough in industry-facing strategy/partnership conversations to speak publicly with infrastructure partners.</li>
|
||||
<li>Public sources found so far do <strong>not</strong> confirm a separate personal LinkedIn profile, education history, church affiliation, or detailed career history for Ari. Avoid over-assuming beyond official/company pages.</li>
|
||||
</ul>
|
||||
<h3 id="how-to-talk-with-ari">How to Talk With Ari</h3>
|
||||
<ul>
|
||||
<li>Treat him as a broadcast workflow/platform strategist, not just a camera/video person.</li>
|
||||
<li>Ask about process, reliability, automation, archival/search, content reuse, and sustainable volunteer operations.</li>
|
||||
<li>Since he has industry context around cloud storage, encoding, AI media, and delivery workflows, ask him to separate what a small church should do now from what enterprise broadcasters do at scale.</li>
|
||||
<li>A useful framing: “We are trying to design the simplest workflow that reliably captures a service, streams it well, archives it properly, and turns it into useful short-form content without overwhelming volunteers.”</li>
|
||||
</ul>
|
||||
<h3 id="ari-specific-questions">Ari-Specific Questions</h3>
|
||||
<ul>
|
||||
<li>From your experience building Sardius, what is the first workflow mistake churches usually make with livestream/media?</li>
|
||||
<li>If you had to design a low-complexity but future-proof setup for us, what would you standardize first?</li>
|
||||
<li>What should remain manual for a small volunteer team, and what should be automated?</li>
|
||||
<li>How should we think about archiving, metadata, and AI search from day one?</li>
|
||||
<li>What is the line between “good enough OBS workflow” and “time to use a dedicated platform/encoder system”?</li>
|
||||
<li>What would you recommend we measure: stream health, engagement, watch time, clip performance, volunteer load, or something else?</li>
|
||||
<li>Are there tools or purchases that churches commonly buy too early?</li>
|
||||
</ul>
|
||||
<h3 id="relevant-capabilities">Relevant Capabilities</h3>
|
||||
<ul>
|
||||
<li>Broadcast platform for live, simulated-live, and on-demand media.</li>
|
||||
<li>Automated encoder management and calendar-driven broadcast workflows.</li>
|
||||
<li>Integrations/compatibility mentioned: AWS Elemental MediaLive Anywhere, Haivision, SRT, RTMP, HLS, CHOP, Resi.</li>
|
||||
<li>Distribution workflows to YouTube, Facebook, broadcast partners, websites, apps, Roku, Apple TV, Fire TV, iOS, and Android.</li>
|
||||
<li>AI-powered discovery/metadata: auto transcription, keywords, summaries, searchable content, and video-library search.</li>
|
||||
<li>Live subtitles/translations, multi-language experiences, multi-track interpretation support.</li>
|
||||
<li>Analytics dashboards and API access.</li>
|
||||
<li>Live event support, including on-site support for complex events.</li>
|
||||
<li>Pulse product for multi-site/campus monitoring, rapid review, auto-archiving, quality control, and feedback.</li>
|
||||
</ul>
|
||||
<h3 id="why-they-matter-for-this-project">Why They Matter for This Project</h3>
|
||||
<p>Sardius appears to operate at a higher scale than a simple OBS/YouTube church livestream setup. Their useful advice will likely be around workflow design, reliability, automation, archive/search, multi-platform distribution, and how to make volunteer media operations sustainable.</p>
|
||||
<h3 id="strong-questions-to-ask-them">Strong Questions to Ask Them</h3>
|
||||
<ul>
|
||||
<li>If you saw our current church livestream setup, what would you improve first: audio, cameras, lighting, encoding, internet, workflow, or team roles?</li>
|
||||
<li>What is the minimum sustainable broadcast workflow for a small/medium church volunteer team?</li>
|
||||
<li>When should a church stay with OBS/YouTube/Facebook versus using a managed platform or dedicated encoder workflow?</li>
|
||||
<li>How should we structure sermon archives so they become searchable, reusable content instead of just stored videos?</li>
|
||||
<li>What is the simplest repeatable process for turning one service into sermon clips, reels, quote graphics, and announcements?</li>
|
||||
<li>What AI transcription, metadata, captioning, and translation workflows are actually worth using now?</li>
|
||||
<li>What standards do you recommend for audio loudness, camera framing, lighting, graphics, encoding bitrate, and backups?</li>
|
||||
<li>What equipment or software purchases should we avoid until the process is better defined?</li>
|
||||
</ul>
|
||||
<h2 id="advice-received">Advice Received</h2>
|
||||
<p><em>To be filled after the producer meeting.</em></p>
|
||||
<h2 id="action-items">Action Items</h2>
|
||||
<ul>
|
||||
<li>[ ] Document the actual current livestream hardware/software setup.</li>
|
||||
<li>[ ] Document the actual current AI/video generation workflow.</li>
|
||||
<li>[ ] List recent examples of livestreams and generated videos to show the producer.</li>
|
||||
<li>[ ] Capture producer feedback and prioritize next steps.</li>
|
||||
<li>[ ] Convert advice into a repeatable checklist or SOP.</li>
|
||||
</ul>
|
||||
<h2 id="related-notes">Related Notes</h2>
|
||||
<ul>
|
||||
<li>Technology for the Kingdom of God</li>
|
||||
<li>kenya trip 2026</li>
|
||||
<li>Family Timeline</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="footer-note">Generated from the Reyna family brain note: /home/adolforeyna/brain/projects/livestream_video_generation_process.md</div>
|
||||
</body></html>
|
||||
Binary file not shown.
@@ -0,0 +1,50 @@
|
||||
from pathlib import Path
|
||||
import re, html
|
||||
import markdown
|
||||
|
||||
src = Path('/home/adolforeyna/brain/projects/livestream_video_generation_process.md')
|
||||
out_dir = Path('/home/adolforeyna/brain/exports')
|
||||
out_dir.mkdir(parents=True, exist_ok=True)
|
||||
text = src.read_text(encoding='utf-8')
|
||||
text = re.sub(r'^---\n.*?\n---\n\s*', '', text, flags=re.S)
|
||||
text = re.sub(r'^#\s+(.+)$', r'# \1\n\n**Prepared for EMI media/livestream planning** \n**Updated:** June 29, 2026', text, count=1, flags=re.M)
|
||||
text = re.sub(r'\[\[([^\]|]+)\|([^\]]+)\]\]', r'\2', text)
|
||||
text = re.sub(r'\[\[([^\]]+)\]\]', lambda m: m.group(1).replace('_',' '), text)
|
||||
# Python-Markdown needs a blank line before many lists; add one after label lines ending in ':'
|
||||
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.65in 0.62in; }
|
||||
* { box-sizing: border-box; }
|
||||
body { font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; color: #1f2933; line-height: 1.47; font-size: 10.7pt; }
|
||||
h1 { font-size: 27pt; color: #12355b; margin: 0 0 8px 0; letter-spacing: -0.02em; padding-bottom: 12px; border-bottom: 4px solid #2f80ed; }
|
||||
h2 { font-size: 18pt; color: #12355b; margin-top: 28px; padding: 8px 12px; background: linear-gradient(90deg,#eaf3ff,#ffffff); border-left: 5px solid #2f80ed; break-after: avoid; }
|
||||
h3 { font-size: 13.5pt; color: #164b7a; margin-top: 20px; border-bottom: 1px solid #d6e4f0; padding-bottom: 4px; break-after: avoid; }
|
||||
h4 { font-size: 11.8pt; color: #2f5f8f; margin-top: 15px; break-after: avoid; }
|
||||
p { margin: 7px 0; }
|
||||
ul, ol { margin-top: 5px; padding-left: 22px; }
|
||||
li { margin: 3px 0; }
|
||||
blockquote { margin: 12px 0; padding: 10px 14px; border-left: 4px solid #f2c94c; background: #fff9e6; color: #4a3b00; }
|
||||
code { background: #eef4fa; padding: 1px 4px; border-radius: 4px; color: #0b456f; font-family: "SFMono-Regular", Consolas, monospace; font-size: 9pt; }
|
||||
table { width: 100%; border-collapse: collapse; margin: 12px 0 18px; font-size: 8.8pt; page-break-inside: auto; }
|
||||
th { background: #12355b; 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; }
|
||||
hr { border: 0; border-top: 1px solid #d9e2ec; margin: 22px 0; }
|
||||
strong { color: #102a43; }
|
||||
.title-card { border: 1px solid #d6e4f0; border-radius: 14px; padding: 18px; background: linear-gradient(135deg,#f7fbff,#ffffff); margin-bottom: 18px; }
|
||||
.footer-note { margin-top: 28px; font-size: 8.5pt; 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>Livestream and Video Generation Process</title><style>{css}</style></head>
|
||||
<body>
|
||||
<div class="title-card">
|
||||
{body}
|
||||
</div>
|
||||
<div class="footer-note">Generated from the Reyna family brain note: {html.escape(str(src))}</div>
|
||||
</body></html>'''
|
||||
html_path = out_dir / 'livestream_video_generation_process.html'
|
||||
html_path.write_text(full, encoding='utf-8')
|
||||
print(html_path)
|
||||
@@ -1,6 +1,7 @@
|
||||
# Brain Index (Map of Content)
|
||||
|
||||
- **[[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.
|
||||
- [[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.
|
||||
|
||||
@@ -0,0 +1,191 @@
|
||||
---
|
||||
Date: 2026-06-29
|
||||
Author: Hermes
|
||||
Tags: [project, emi, media, youtube, outreach, kingdom, international-team]
|
||||
---
|
||||
|
||||
# EMI Media Outreach and YouTube Strategy
|
||||
|
||||
## Objective
|
||||
The goal is to have the message of the Kingdom reaching all corners of the earth.
|
||||
|
||||
This media effort should not be treated only as a content channel. It should become an EMI-branded global outreach system: clear message, consistent publishing, international participation, translation, promotion, and measurable follow-up.
|
||||
|
||||
## Core Vision
|
||||
Build an EMI media presence that:
|
||||
- Proclaims the message of the Kingdom with clarity and excellence.
|
||||
- Reaches Spanish-speaking, English-speaking, and international audiences.
|
||||
- Equips leaders, churches, families, and younger generations to share the message.
|
||||
- Converts long-form teachings, services, testimonies, and events into short, shareable content.
|
||||
- Gives an international team a structured way to contribute, translate, promote, and multiply the content.
|
||||
|
||||
## EMI Branded YouTube Presence
|
||||
|
||||
### Channel Positioning
|
||||
Recommended positioning:
|
||||
- Name: EMI Global / EMI Kingdom / EMI International, depending on the official branding decision.
|
||||
- Primary identity: a global Kingdom message platform, not just a local church video archive.
|
||||
- Audience: believers, leaders, families, youth, churches, and seekers across nations.
|
||||
- Tone: apostolic, clear, excellent, warm, international, and spiritually focused.
|
||||
|
||||
### Channel Structure
|
||||
Organize the YouTube channel around repeatable content pillars:
|
||||
|
||||
1. Kingdom Teachings
|
||||
- Full teachings, conference sessions, and apostolic messages.
|
||||
- Clear titles with topic, speaker, and language.
|
||||
|
||||
2. Short Kingdom Clips
|
||||
- 30–90 second clips from sermons, meetings, and teachings.
|
||||
- Designed for YouTube Shorts, Instagram Reels, Facebook, TikTok, and WhatsApp sharing.
|
||||
|
||||
3. Testimonies and Transformation Stories
|
||||
- Personal stories from different regions.
|
||||
- Helps the message feel embodied, not only preached.
|
||||
|
||||
4. International Voices
|
||||
- Contributions from Cuba, Mexico, Chile, Panama, Aruba, the U.S., and other connected regions.
|
||||
- Short regional updates, prayers, exhortations, and testimonies.
|
||||
|
||||
5. Youth and Next Generation
|
||||
- Weekly short challenges and youth-created posts about Jesus and His Kingdom.
|
||||
- Aligns with the Latin America collaboration note: youth posting about Jesus and the Kingdom weekly.
|
||||
|
||||
6. Events and Gatherings
|
||||
- Chiapas leaders summit content.
|
||||
- Monthly virtual meeting highlights where appropriate.
|
||||
- Regional family assembly content.
|
||||
|
||||
### Branding Standards
|
||||
Create a simple EMI media kit:
|
||||
- Logo files.
|
||||
- Colors.
|
||||
- Fonts.
|
||||
- Thumbnail templates.
|
||||
- Lower-third template for speaker name, region, and topic.
|
||||
- Intro/outro options.
|
||||
- Standard title and description format.
|
||||
- Standard call-to-action: subscribe, share, comment, contact, connect with a local EMI leader.
|
||||
|
||||
### Publishing Cadence
|
||||
Start sustainable, then grow:
|
||||
- 1 full teaching per week.
|
||||
- 3–5 short clips per week.
|
||||
- 1 testimony or international voice feature per week.
|
||||
- 1 monthly regional/global update.
|
||||
|
||||
## Content Outreach Strategy
|
||||
|
||||
### One Message, Many Formats
|
||||
Each major teaching or event should become:
|
||||
- Full YouTube video.
|
||||
- 3–10 short clips.
|
||||
- Quote graphics.
|
||||
- WhatsApp shareable clips.
|
||||
- Podcast/audio version if useful.
|
||||
- Translated captions or dubbed/subtitled versions.
|
||||
- Short written summary for newsletters or posts.
|
||||
|
||||
### Distribution Channels
|
||||
Use YouTube as the central public library, then distribute outward:
|
||||
- YouTube long-form.
|
||||
- YouTube Shorts.
|
||||
- Facebook pages/groups.
|
||||
- Instagram Reels.
|
||||
- TikTok, if the team is ready.
|
||||
- WhatsApp groups and broadcast lists.
|
||||
- Church websites and Subsplash if applicable.
|
||||
- Email/newsletter for leaders and partners.
|
||||
|
||||
### Outreach Funnel
|
||||
1. Discover: short clips, reels, shared WhatsApp content.
|
||||
2. Engage: full teaching, testimony, live event, or playlist.
|
||||
3. Connect: comment, subscribe, message, join local/regional group.
|
||||
4. Disciple: follow-up series, Bible/Kingdom study, regional leader connection.
|
||||
5. Multiply: equip viewers to share clips and create local language versions.
|
||||
|
||||
## International Team Model
|
||||
|
||||
### Core Roles
|
||||
Build the international media team with clear lanes:
|
||||
- Media Director: owns vision, standards, publishing calendar, and final approvals.
|
||||
- Content Producer: identifies messages, themes, and clips worth publishing.
|
||||
- Editor(s): edits full videos, shorts, captions, audio cleanup, thumbnails.
|
||||
- Translation/Subtitles Team: Spanish-English first; expand to Portuguese/French/other languages as God opens doors.
|
||||
- Regional Contributors: send testimonies, short teachings, prayer updates, and event footage from their nation.
|
||||
- Social Promotion Team: posts and shares content on assigned platforms and groups.
|
||||
- Community/Follow-up Team: monitors comments/messages and routes genuine connection requests to leaders.
|
||||
- Analytics Lead: tracks reach, retention, subscribers, shares, comments, and international growth.
|
||||
|
||||
### Regional Representation
|
||||
Initial international team could include representatives or contributors from:
|
||||
- United States / Florida.
|
||||
- Cuba.
|
||||
- Mexico / Chiapas.
|
||||
- Chile.
|
||||
- Panama.
|
||||
- Aruba.
|
||||
- Other EMI-connected regions.
|
||||
|
||||
### Team Operating Rhythm
|
||||
- Weekly 30-minute media standup: what is publishing this week, what clips are needed, what is blocking.
|
||||
- Monthly content planning meeting: themes, events, testimonies, campaigns.
|
||||
- Shared content calendar: titles, owners, deadlines, languages, platform status.
|
||||
- Shared asset folder: raw videos, exports, thumbnails, captions, logos, templates.
|
||||
- Simple approval process: theological/message review before publishing public content.
|
||||
|
||||
## First 90-Day Rollout
|
||||
|
||||
### Days 1–15: Foundation
|
||||
- Decide official EMI YouTube channel name and handle.
|
||||
- Confirm ownership/admin access and brand account structure.
|
||||
- Gather logo, colors, photos, speaker bios, and existing recordings.
|
||||
- Create basic channel art, avatar, About section, and contact email.
|
||||
- Define title, description, thumbnail, and caption templates.
|
||||
|
||||
### Days 16–30: Content Inventory and Pilot
|
||||
- Audit existing recordings and identify the first 10 strong messages.
|
||||
- Select 20–30 short clip candidates.
|
||||
- Publish or schedule the first 4 long-form videos.
|
||||
- Publish the first 10–15 Shorts.
|
||||
- Create playlists by topic, speaker, language, and region.
|
||||
|
||||
### Days 31–60: International Team Activation
|
||||
- Invite regional media contributors.
|
||||
- Assign roles for translation, clipping, promotion, and follow-up.
|
||||
- Start collecting testimonies and regional short videos.
|
||||
- Launch a weekly sharing rhythm through WhatsApp and social platforms.
|
||||
- Begin Spanish-English subtitles for the strongest content.
|
||||
|
||||
### Days 61–90: Scale and Measure
|
||||
- Review analytics: audience countries, retention, top clips, subscriber growth, comments.
|
||||
- Double down on topics and formats that are reaching people.
|
||||
- Improve thumbnails/titles based on performance.
|
||||
- Create a monthly EMI Global Update video.
|
||||
- Prepare media plan for the Chiapas gathering and future regional family assembly.
|
||||
|
||||
## Metrics to Track
|
||||
Track both reach and fruit:
|
||||
- YouTube subscribers.
|
||||
- Views by country.
|
||||
- Watch time and retention.
|
||||
- Shorts shares and comments.
|
||||
- Number of translated/subtitled videos.
|
||||
- Number of regional contributors active.
|
||||
- Messages or comments requesting connection/prayer/follow-up.
|
||||
- Testimonies received from content impact.
|
||||
|
||||
## Immediate Next Actions
|
||||
- [ ] Decide the official EMI YouTube channel name/handle.
|
||||
- [ ] Identify who owns the channel/admin credentials.
|
||||
- [ ] Create a shared media folder and content calendar.
|
||||
- [ ] Choose the first 10 teachings/messages to publish or repackage.
|
||||
- [ ] Recruit the initial international media team.
|
||||
- [ ] Create thumbnail, lower-third, title, and description templates.
|
||||
- [ ] Define approval/review process before posting.
|
||||
- [ ] Prepare a Chiapas media capture plan.
|
||||
|
||||
## Related Notes
|
||||
- [[Livestream and Video Generation Process]]
|
||||
- [[Latin America EMI Collaboration 2026]]
|
||||
- [[Technology for the Kingdom of God]]
|
||||
@@ -34,161 +34,274 @@ Current-state AV / broadcast media assessment, combining:
|
||||
Reference: AVIXA `Audiovisual Systems Performance Verification` standard, Document 10:2013, describes a framework for determining audiovisual system elements, verification timing, criteria/metrics, and reporting procedures.
|
||||
|
||||
### 1. Executive Summary
|
||||
_To be drafted after interview._
|
||||
The local Florida ministry currently livestreams Sunday services and special events primarily through Subsplash. Subsplash also provides the ministry website at https://florida.emmint.com/ and automatically posts a replay in the app about 5–10 minutes after each livestream ends. The team does not currently livestream directly to YouTube or Facebook.
|
||||
|
||||
Capture:
|
||||
- What the church currently does for media and livestream.
|
||||
- Main platforms used.
|
||||
- Current goals: livestream quality, reliability, clips, archiving, volunteer sustainability.
|
||||
- Top 3 pain points.
|
||||
The current mobile production system is built around a Canon M50 Mark II, ATEM Mini, iMac/OBS, Zoom, WorshipTools, and a Behringer X18 audio mixer. OBS is used for high-quality local recording, while Zoom is used as a more resilient live contribution/stream layer, especially because phones can join Zoom as extra cameras and because Zoom tolerates some disconnect/network instability better than the direct OBS path.
|
||||
|
||||
The strongest current needs are:
|
||||
- reliable multilingual translation/captioning for local and international audiences,
|
||||
- better event connectivity strategies for remote international gatherings,
|
||||
- lower-third lyrics/slides instead of full Zoom screen share,
|
||||
- a faster mobile cart/case setup that can support multiple wireless DSLR/mirrorless cameras,
|
||||
- a NAS-based searchable media archive and AI-assisted post-production workflow.
|
||||
|
||||
The desired future state is not simply “better livestream quality.” It is a sustainable media system that can serve local Sunday meetings, international EMI gatherings, public outreach, multilingual access, selective YouTube publishing, short-form clips, and long-term searchable media reuse without overwhelming volunteers.
|
||||
|
||||
### 2. Ministry / Use Case
|
||||
_To be documented._
|
||||
Primary use cases:
|
||||
- Sunday services.
|
||||
- Special events.
|
||||
- Larger EMI family gatherings and international meetings.
|
||||
- Outreach teachings prepared intentionally for public sharing.
|
||||
|
||||
Questions to answer:
|
||||
- What services/events are streamed or recorded?
|
||||
- How often does media production happen?
|
||||
- Who is the intended audience: in-person overflow, online members, archive viewers, outreach, social media?
|
||||
- What outputs are expected: livestream, full sermon archive, short clips, reels, podcasts, thumbnails, announcement videos?
|
||||
Audiences:
|
||||
- Local Florida congregation and remote members watching through Subsplash.
|
||||
- International EMI-connected ministries and families watching from multiple regions.
|
||||
- English and Spanish audiences as the largest recurring language groups.
|
||||
- Additional language audiences connected to France, Denmark, Africa, and other EMI regions.
|
||||
- Public outreach audiences through The Walking Voice Media, KingdomEMI, YouTube, Facebook, and future short-form content.
|
||||
|
||||
Expected outputs:
|
||||
- Automatic full-service replay/archive on Subsplash every Sunday.
|
||||
- Selective YouTube publishing when a teaching is prepared and strong enough for outreach.
|
||||
- 3–5 short clips per week when a YouTube teaching is published.
|
||||
- Occasional Facebook posts.
|
||||
- 1–2 monthly outreach pieces for The Walking Voice Media.
|
||||
- Bilingual captions and translated versions when useful/possible.
|
||||
- Long-term indexed/searchable archive for future reuse by speaker, topic, scripture, event, and transcript.
|
||||
|
||||
### 3. Current Signal Flow
|
||||
_To be documented._
|
||||
Current local Sunday signal flow:
|
||||
|
||||
Audio chain:
|
||||
`Microphones / instruments → soundboard → livestream audio feed → computer / encoder / OBS → streaming platform → recording / archive → editing / social clips`
|
||||
`Microphones / instruments → Behringer X18 mixer → XLR output → audio interface → iMac / livestream computer → OBS local recording + Zoom/Subsplash live workflow → Subsplash replay/archive → optional trim/edit → future clips/social content`
|
||||
|
||||
Video chain:
|
||||
`Cameras → switcher / capture card / OBS → graphics / slides → encoder → Subsplash / YouTube / Facebook`
|
||||
`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`
|
||||
|
||||
### 4. Equipment Inventory
|
||||
_To be documented._
|
||||
|
||||
| Category | Item | Model | Location | Purpose | Notes / Problems |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Cameras | | | | | |
|
||||
| Lenses | | | | | |
|
||||
| Tripods / mounts | | | | | |
|
||||
| Audio console | | | | | |
|
||||
| Microphones | | | | | |
|
||||
| Audio interface | | | | | |
|
||||
| Computer / encoder | | | | | |
|
||||
| Capture cards | | | | | |
|
||||
| Network gear | | | | | |
|
||||
| Lighting | | | | | |
|
||||
| Cables / adapters | | | | | |
|
||||
| Storage drives | | | | | |
|
||||
| Software subscriptions | | | | | |
|
||||
| Camera | Main camera | Canon M50 Mark II | Sunday school setup | Main video feed | Wired HDMI to ATEM; setup/tear-down burden |
|
||||
| Switcher / capture | Video switcher | ATEM Mini | Livestream table | Camera ingest into computer | Audio through ATEM has been unreliable, with brief dropouts |
|
||||
| Computer / encoder | Livestream computer | iMac | Back/livestream table | OBS recording, virtual webcam, Zoom/Subsplash workflow, X18 control | Single point of failure; if it fails, stream is lost |
|
||||
| Audio console | Headless digital mixer | Behringer X18 | Worship/audio setup | Main audio mixing | Controlled from livestream computer or laptop on network |
|
||||
| Audio interface | XLR-to-computer interface | Exact model TBD | Livestream table | Routes X18 output into computer | Used because ATEM lacks desired XLR input and has audio issues |
|
||||
| Presentation | Lyrics/slides software | WorshipTools | Local screen + Zoom share | Lyrics/slides for worship/preaching | Screen share reduces camera to small window |
|
||||
| Cameras | Phone cameras | Various phones | Flexible placement | Extra camera angles through Zoom | Useful in mobile/school setup |
|
||||
| Network | School Wi-Fi | TBD | Rented school building | Internet for stream and Zoom | Current major constraint |
|
||||
| Storage | Home NAS | 8TB | Adolfo's home | Long-term media archive | Filling up; media not well organized/indexed |
|
||||
| Lighting | Building/temporary lighting | TBD | School building | Visual quality | Current building lights not available to team; temporary lighting adds overhead |
|
||||
|
||||
### 5. Software / Platforms
|
||||
_To be documented._
|
||||
|
||||
Include:
|
||||
- OBS or other switching / encoding software.
|
||||
- Subsplash.
|
||||
- YouTube.
|
||||
- Facebook.
|
||||
- ProPresenter / EasyWorship / slides / lyrics tools.
|
||||
- Editing software.
|
||||
- AI tools.
|
||||
- Transcription tools.
|
||||
- Storage / archive tools.
|
||||
Current platforms/software:
|
||||
- Subsplash: primary livestream service, distribution, automatic replay/archive, and ministry website provider.
|
||||
- OBS: high-quality local recording and virtual webcam support.
|
||||
- Zoom: live video layer, phone camera contribution, translation/captioning experiments, and resilience during disconnects/network instability.
|
||||
- WorshipTools: lyrics and slides for local screen and Zoom screen share.
|
||||
- YouTube:
|
||||
- The Walking Voice Media: newer outreach-focused channel.
|
||||
- KingdomEMI: older channel to revive with new content.
|
||||
- Facebook: KingdomEMI page.
|
||||
- Subsplash editor: simple trims.
|
||||
- Final Cut: Adolfo’s occasional edits.
|
||||
- DaVinci Resolve: likely used by Brother Gino on Windows.
|
||||
- AI editing/transcription tools: desired but not yet selected/tried.
|
||||
- NAS-based archive/search software: desired but not yet selected.
|
||||
|
||||
### 6. Internet / Network
|
||||
_To be documented._
|
||||
Current local Sunday network:
|
||||
- The church currently meets in a rented school building.
|
||||
- Livestream depends on Wi-Fi.
|
||||
- Connectivity is a major complication.
|
||||
- The stream computer is not on a known dedicated/wired media network at this time.
|
||||
|
||||
Capture:
|
||||
- Wired or Wi-Fi connection.
|
||||
- Upload speed.
|
||||
- Backup internet.
|
||||
- Dedicated media network or shared church Wi-Fi.
|
||||
- Known dropouts.
|
||||
- Router / switch location.
|
||||
- Whether the stream computer is hardwired.
|
||||
Home archive network:
|
||||
- Adolfo’s home has 1GB parallel/symmetric internet.
|
||||
- Home NAS is the preferred long-term archive location.
|
||||
|
||||
International event network:
|
||||
- Larger meetings often happen in remote or less-connected locations: Mexico, small-town hotels, Kenya locations outside city centers, etc.
|
||||
- No single internet solution works globally.
|
||||
- A cell phone with strong coverage may be useful, but it does not solve multi-language translation and streaming by itself.
|
||||
|
||||
### 7. Livestream Workflow
|
||||
_To be documented._
|
||||
Current Sunday workflow:
|
||||
|
||||
Before service:
|
||||
- Turn on gear.
|
||||
- Check audio.
|
||||
- Check camera framing.
|
||||
- Start OBS / encoder.
|
||||
- Confirm stream destination.
|
||||
- Test recording.
|
||||
- Worship team arrives and sets up the X18/audio board and building speaker connections.
|
||||
- Adolfo connects the audio feed at the back/livestream table.
|
||||
- Adolfo sets up the Canon M50 Mark II on tripod.
|
||||
- HDMI is run from the Canon M50 Mark II to the ATEM Mini.
|
||||
- ATEM Mini and audio interface are connected to the iMac/livestream setup.
|
||||
- WorshipTools is prepared for lyrics/slides.
|
||||
- OBS is prepared for local recording and virtual webcam.
|
||||
- Zoom/Subsplash workflow is prepared for livestreaming.
|
||||
|
||||
During service:
|
||||
- Monitor audio.
|
||||
- Switch cameras / scenes.
|
||||
- Watch stream health.
|
||||
- Operate slides / lyrics.
|
||||
- WorshipTools drives lyrics/slides locally and through Zoom screen share.
|
||||
- Zoom may receive the ATEM feed directly instead of OBS for reliability.
|
||||
- Phones may join Zoom as additional cameras when needed.
|
||||
- Audio is mixed from the X18 and routed through the interface to the computer.
|
||||
|
||||
After service:
|
||||
- Stop stream.
|
||||
- Save recording.
|
||||
- Upload / archive.
|
||||
- Clip sermon.
|
||||
- Post to social media.
|
||||
- Local OBS recording remains on the iMac.
|
||||
- Zoom is not recorded because OBS local recording is higher quality.
|
||||
- Subsplash automatically posts the replay/archive in the app within about 5–10 minutes.
|
||||
- Simple trims may be done in Subsplash when needed.
|
||||
- More intentional edits may be done later in Final Cut or DaVinci.
|
||||
- Public/prayer ministry portions may be removed when appropriate before broader public sharing.
|
||||
|
||||
### 8. Team / Roles
|
||||
_To be documented._
|
||||
Current roles:
|
||||
- Worship team: audio setup, X18/audio board, building speaker setup.
|
||||
- Adolfo: livestream setup lead, audio feed connection, camera/ATEM/computer setup, overall workflow oversight, 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; less active currently due to job changes and transition to the school location.
|
||||
- Brother Gino Gianelli: editing support on Windows, likely DaVinci Resolve.
|
||||
- Eli Lastra: overall content creator supervisor and quality eye.
|
||||
- Apostle David: higher-level ministry/message approval when needed.
|
||||
|
||||
Roles to identify:
|
||||
- Livestream director.
|
||||
- Audio operator.
|
||||
- Camera operator(s).
|
||||
- Slides / lyrics operator.
|
||||
- Stream monitor.
|
||||
- Editor.
|
||||
- Social media / posting.
|
||||
- Backup people.
|
||||
|
||||
Note whether roles are volunteer-dependent and whether too much depends on one person.
|
||||
Volunteer/staffing risk:
|
||||
- The setup still depends heavily on Adolfo for assembly, routing, and troubleshooting.
|
||||
- Sara sometimes has split attention between translation and media support.
|
||||
- More training and a simplified mobile setup would reduce fragility.
|
||||
|
||||
### 9. Current Quality / Pain Points
|
||||
_To be documented._
|
||||
|
||||
Audio:
|
||||
- Mix quality.
|
||||
- Room noise.
|
||||
- Vocal clarity.
|
||||
- Music balance.
|
||||
- Stream mix vs house mix.
|
||||
#### 1) Translation / Multilingual Access
|
||||
- Biggest current pain point.
|
||||
- Current system depends heavily on human translation.
|
||||
- Main languages for local Florida livestreams are English and Spanish, but the meetings are watched globally.
|
||||
- EMI-connected ministries include France, Denmark, Africa, and other regions that require additional languages.
|
||||
- No clearly reliable translation tool/workflow has been found yet.
|
||||
- Zoom Caption Auto-Translation is being tried again and appears better than it was the previous September, but still needs validation.
|
||||
- Need a reliable structure for bigger events and family gatherings, not only Sunday services.
|
||||
- Possible direction: multiple microphones/headsets/channels so people can connect locally and receive translation in their language.
|
||||
|
||||
Video:
|
||||
- Camera angles.
|
||||
- Resolution.
|
||||
- Lighting.
|
||||
- Focus / exposure.
|
||||
- Movement / shot variety.
|
||||
#### Sunday Translation Target / "Good Enough" Standard
|
||||
- Technology likely has advanced enough for real-time or near-real-time automatic captioning with translation to provide useful caption quality.
|
||||
- The missing piece is a known product/workflow that lets viewers select translated captions directly on the livestream in real time.
|
||||
- For local viewers, captions alone may feel like a heavy reading experience compared with hearing translation; audio translation is still preferable when possible.
|
||||
- Because English and Spanish are both large audience groups, live human translation still makes sense for English ↔ Spanish.
|
||||
- For other languages, automatic captioning/translation would be very valuable.
|
||||
- Current issue: when both English and Spanish are present in the same audio stream, automatic captioning/translation tends to struggle with language detection and accuracy.
|
||||
- Possible fix: send only English into the automatic captioning/translation system. The church has the capability to route this, but it has not yet had the time/investment to make it reliable.
|
||||
|
||||
Reliability:
|
||||
- Internet.
|
||||
- OBS / software stability.
|
||||
- Audio sync.
|
||||
- Power / cable issues.
|
||||
#### 2) Remote / International Event Connectivity
|
||||
- Bigger meetings are often in remote areas around the world, such as Mexico, small-town hotels, or Kenya locations away from city centers.
|
||||
- Internet reliability varies by event and location.
|
||||
- There is no single connectivity solution that works for all events.
|
||||
- Apostles and leaders travel globally, so bulky equipment may not be practical.
|
||||
- A cell phone with strong coverage may help, but would not be enough by itself for five-language translation and streaming directly to participants' phones.
|
||||
- At the Kenya family gathering, local in-room translation was done simultaneously; it worked somewhat but was not optimal.
|
||||
|
||||
Workflow:
|
||||
- Manual steps.
|
||||
- Lack of checklist.
|
||||
- Volunteer training difficulty.
|
||||
- Difficulty creating clips afterward.
|
||||
#### International Event Translation Target
|
||||
- Preferred experience for most in-person attendees: participants connect with their own device and headphones, then choose the language they need.
|
||||
- This may not be viable in every nation or setting, but those situations may be the exception rather than the rule.
|
||||
- For events without strong internet, the ideal backup/alternative is local off-stage translation provided directly to people in the room.
|
||||
- The long-term solution likely needs both modes:
|
||||
- internet/device-based language access when connectivity and audience devices allow it,
|
||||
- local/offline translation distribution for remote or low-connectivity events.
|
||||
|
||||
#### 3) Mobile Setup / Tear-Down Burden
|
||||
- Local Sunday setup currently requires many hands and significant setup/tear-down time because the church rents/uses a school building.
|
||||
- The team hopes this will be solved once there is a dedicated building.
|
||||
- In the meantime, the goal is a mobile setup that can be deployed quickly.
|
||||
- The current mobile setup works, but leaves little margin to improve quality.
|
||||
|
||||
#### 4) Lyrics / Slides Presentation Limitation
|
||||
- In Zoom, screen sharing lyrics/slides makes the camera video a small square in the top-right corner.
|
||||
- This is acceptable for worship when lyrics are the priority, but it weakens the video presentation.
|
||||
- Ideal future state: lower-third lyrics or other overlay where the full video remains visible and lyrics appear at the bottom.
|
||||
- Need to explore whether WorshipTools can support this better, or whether more professional presentation software is needed.
|
||||
- There is significant room to improve how material is presented, not only the video stream itself.
|
||||
|
||||
#### 5) Local Lighting / Visual Quality
|
||||
- Lighting is a local pain point.
|
||||
- The school building has lights, but the church has not been allowed to use them at this time.
|
||||
- Adding temporary lights does not currently look great and adds setup overhead.
|
||||
- Tripods, lights, and similar gear increase the burden because everything must be set up and taken down the same day.
|
||||
|
||||
#### Local Sunday Next Improvements
|
||||
- Highest-priority local improvement: lower-third lyrics instead of Zoom screen share, so the main video remains visible while lyrics appear at the bottom.
|
||||
- Second major local improvement: a mobile cart/case setup that allows quick setup/tear-down and supports multiple wireless cameras.
|
||||
- Desired wireless camera direction: more DSLR/mirrorless-style cameras, connected using wireless HDMI rather than long HDMI cable runs back to the ATEM Mini.
|
||||
- Motivation: the current wired setup requires power and HDMI cabling from camera positions to the ATEM Mini, which adds setup burden and limits camera placement.
|
||||
- Desired outcome: reduce setup burden while improving visual quality and flexibility in the rented school environment.
|
||||
|
||||
### 10. Recording / Archive / Post-Production
|
||||
_To be documented._
|
||||
Current recording/archive pattern:
|
||||
- OBS records locally on the iMac used for livestream/transmission.
|
||||
- Zoom is not recorded because the OBS recording is higher quality.
|
||||
- Subsplash automatically records and publishes the livestream replay in the app about 5–10 minutes after the service.
|
||||
- Subsplash replay is the default full-service public archive for the congregation.
|
||||
- Simple trims are done in the Subsplash editor when needed.
|
||||
- Adolfo occasionally edits in Final Cut.
|
||||
- Brother Gino edits on Windows, likely in DaVinci Resolve.
|
||||
|
||||
Include:
|
||||
- Whether there is a local recording.
|
||||
- Recording resolution and audio settings.
|
||||
- Where files are stored.
|
||||
- Naming convention.
|
||||
- Backup process.
|
||||
- How sermon clips are made.
|
||||
- Captions, thumbnails, titles, descriptions.
|
||||
- How long files are kept.
|
||||
Current post-production pattern:
|
||||
- Editing is done only when needed for normal services, especially to remove empty spaces, non-public sections, or personal prayer/ministry time.
|
||||
- YouTube is selective: publish only well-prepared teachings intended for public outreach.
|
||||
- When a teaching is published to YouTube, the goal is to create 3–5 short clips per week from that content for YouTube and Facebook.
|
||||
- Walking Voice Media should receive 1–2 outreach pieces per month.
|
||||
|
||||
Current archive gap:
|
||||
- Long-term files live on the 8TB home NAS, but the archive is not well organized or indexed.
|
||||
- Needed metadata/search: speaker, date, event name, scripture/reference, topic/theme, language, people in video, and quote/transcript search.
|
||||
- Needed next design: folder structure, naming convention, transcript/indexing workflow, backup/storage growth plan, and NAS-based media software evaluation.
|
||||
|
||||
### 11. Desired Future State
|
||||
Draft framing:
|
||||
> We want a simple, reliable, volunteer-friendly workflow that captures services, streams them consistently, archives them cleanly, and makes it easy to create useful short-form content afterward without overwhelming the team.
|
||||
We want a simple, reliable, volunteer-friendly workflow that captures services, streams them consistently, supports multilingual audiences, archives content cleanly, and makes it easy to create useful short-form outreach content afterward without overwhelming the team.
|
||||
|
||||
Desired future capabilities:
|
||||
- Lower-third lyrics/slides instead of full Zoom screen share so the main video remains visible.
|
||||
- Mobile cart/case setup that reduces Sunday setup/tear-down time.
|
||||
- Multiple DSLR/mirrorless-style cameras using wireless HDMI rather than long cable runs to the ATEM Mini.
|
||||
- Reliable English/Spanish human translation where needed, plus automatic captions/translations for additional languages.
|
||||
- International event model with both device/headphone-based language access and local/offline translation distribution when internet is weak.
|
||||
- NAS-first media archive with indexing by speaker, date, event, scripture, topic, language, people, and transcript/quote search.
|
||||
- AI-assisted editing workflow for clip discovery, captions, translation, quote graphics, and social repurposing.
|
||||
- Clear publishing lanes: Subsplash for every Sunday replay, YouTube only for strong outreach-ready teachings, Shorts/Facebook clips when YouTube content is published, and 1–2 monthly Walking Voice Media outreach pieces.
|
||||
|
||||
Recommended workstreams:
|
||||
|
||||
#### Workstream 1: Translation and Captions
|
||||
- Test Zoom Caption Auto-Translation with controlled single-language audio input.
|
||||
- Design an English-only feed into automatic caption/translation tools to improve accuracy.
|
||||
- Keep human English ↔ Spanish translation for major audience needs.
|
||||
- Research livestream-compatible selectable captions and multi-language audio/caption solutions.
|
||||
- Define separate patterns for Sunday services vs. major international gatherings.
|
||||
|
||||
#### Workstream 2: Local Sunday Mobile Production Upgrade
|
||||
- Design a mobile cart/case that contains or pre-wires the iMac/laptop, ATEM/interface, power, networking, and cable management.
|
||||
- Evaluate wireless HDMI options for DSLR/mirrorless cameras.
|
||||
- Decide whether to keep ATEM Mini as central switcher or move toward another mobile switching/encoding model.
|
||||
- Reduce single-person dependency by documenting setup steps and training Sara/Sinae/Gary or other volunteers.
|
||||
|
||||
#### Workstream 3: Lyrics / Slides Presentation
|
||||
- Investigate WorshipTools lower-third output or alternative presentation workflows.
|
||||
- Evaluate whether OBS can composite lyrics over video while still feeding Zoom/Subsplash reliably.
|
||||
- Decide whether a more professional presentation system is needed for lyrics, scriptures, and teaching slides.
|
||||
|
||||
#### Workstream 4: Archive and Media Asset Management
|
||||
- Design a NAS folder and naming standard for originals, edits, exports, thumbnails, captions, and project files.
|
||||
- Evaluate NAS-based media asset management/search tools.
|
||||
- Prioritize transcript/quote search and metadata fields: speaker, date, event, scripture, topic, language, people.
|
||||
- Plan for storage growth because the 8TB NAS is filling up.
|
||||
|
||||
#### Workstream 5: AI-Assisted Post-Production
|
||||
- Evaluate AI tools for transcription, clip selection, caption generation, translation, short-form repurposing, and quote graphics.
|
||||
- Define a standard path from Sunday recording → transcript → selected clips → review → export → YouTube/Facebook/Walking Voice.
|
||||
- Keep approval simple: Adolfo + Eli for most content, Apostle David when higher-level ministry/message approval is needed.
|
||||
|
||||
### 12. Questions for Ari / Sardius
|
||||
- What are the top 3 improvements you would prioritize?
|
||||
@@ -200,29 +313,178 @@ Draft framing:
|
||||
- When is OBS enough, and when should we consider a dedicated encoder/platform?
|
||||
|
||||
## Current Livestream Process
|
||||
_To be documented._
|
||||
|
||||
Suggested areas to capture:
|
||||
- Platform(s): Subsplash, YouTube, Facebook, Zoom, other.
|
||||
- Production software: OBS or other switching/encoding tools.
|
||||
- Cameras: number, models, placement, operator roles.
|
||||
- Audio chain: house mix, audio interface, microphones, monitoring.
|
||||
- Internet: upload speed, wired/wireless, backup connection.
|
||||
- Graphics: lower thirds, scripture, sermon title, worship lyrics.
|
||||
- Recording: local recording settings, backup recording, storage location.
|
||||
- Team roles: director, camera operators, audio, slides, stream monitor.
|
||||
### Services / Events Covered
|
||||
- Sunday services.
|
||||
- Special events.
|
||||
|
||||
### Current Livestream / Distribution Platforms
|
||||
- Primary livestream service: Subsplash.
|
||||
- Subsplash is also used for distribution.
|
||||
- Subsplash also provides the ministry website used for the local ministry: https://florida.emmint.com/
|
||||
- Current YouTube channels:
|
||||
- https://www.youtube.com/@TheWalkingVoiceMedia — newer channel dedicated to outreach.
|
||||
- https://www.youtube.com/@kingdomemi — older channel that should be revived with new content.
|
||||
- Facebook page: https://www.facebook.com/kingdomemi/
|
||||
- Current livestream destinations: not livestreaming directly to YouTube or Facebook at this time.
|
||||
|
||||
### Current Production Setup
|
||||
- Main camera: Canon M50 Mark II connected via HDMI to an ATEM Mini.
|
||||
- ATEM Mini feeds the main livestream computer.
|
||||
- OBS runs on the main computer to:
|
||||
- record locally,
|
||||
- set/provide the virtual webcam,
|
||||
- support higher-resolution 1080 workflow when conditions allow.
|
||||
- Current Zoom workflow streams directly from the ATEM instead of OBS because it has proven more reliable during disconnects or network instability; if there are issues, the Zoom stream does not always drop completely.
|
||||
- If the main computer fails, the stream is lost entirely.
|
||||
|
||||
### Zoom / Flexible Camera Workflow
|
||||
- Zoom is used as part of the livestream workflow.
|
||||
- Phones are sometimes used as cameras directly through Zoom so their video can be included in the livestream without physically routing the phone camera through the main computer.
|
||||
- This became more important after changing locations to a rented school building for Sunday meetings.
|
||||
- In the previous/location-stable setup, connectivity was more reliable and multiple cameras were connected to the ATEM Mini.
|
||||
- Direct livestreaming through OBS can push resolution to 1080, but the current rented-school setup and Wi-Fi limitations have made that harder to sustain.
|
||||
|
||||
### Current Internet / Location Constraint
|
||||
- Sunday meetings are currently in a school building.
|
||||
- Livestream is currently dependent on Wi-Fi.
|
||||
- Connectivity is a major complication and still needs a better solution.
|
||||
|
||||
### Current Audio Chain
|
||||
- Mixer: Behringer X18-style headless mixer board, controlled through software rather than physical board controls.
|
||||
- The X18 is controlled from the same computer that runs the livestream, or from any laptop connected to the network.
|
||||
- Audio output path: X18 mixer → XLR cable → audio interface → main computer.
|
||||
- XLR/interface path is used because the ATEM Mini does not provide the needed XLR input.
|
||||
- The ATEM Mini has also had audio reliability issues, including brief audio dropouts of about a second, so it has not been reliable enough as the main audio path.
|
||||
|
||||
### Graphics / Lyrics / Slides Workflow
|
||||
- Software used: WorshipTools — https://www.worshiptools.com/en-us
|
||||
- WorshipTools is used locally to show lyrics on the in-room screen.
|
||||
- Lyrics are also shared into Zoom through screen sharing.
|
||||
- During worship, the priority is congregational participation, so the livestream often favors the shared lyrics even though this makes the camera shot very small.
|
||||
- During preaching, slides are also shared through WorshipTools / screen sharing when needed, but usually only for short sections so the video is not visually reduced for too long.
|
||||
- The local OBS recording does not include the Zoom screen-share layout, which preserves a higher-quality camera video for later editing.
|
||||
|
||||
### Recording / Archive / Post-Service Workflow
|
||||
- At the end of Sunday meeting, the team has a local OBS recording on the iMac used for the livestream/transmission.
|
||||
- Zoom is not recorded because the OBS recording is better quality.
|
||||
- The Subsplash livestream is also recorded automatically.
|
||||
- Subsplash automatically posts the livestream recording as an event/archive in the app, usually available to everyone about 5–10 minutes after the livestream ends.
|
||||
- This gives the ministry an automatic public replay without extra manual publishing steps.
|
||||
- Afterward, editing is done only when required, such as:
|
||||
- removing empty spaces,
|
||||
- removing sections that should not remain public,
|
||||
- trimming personal prayer/ministry time at the end when people are prayed for.
|
||||
|
||||
### Team Roles / Sunday Responsibilities
|
||||
- Worship team:
|
||||
- Handles audio setup in the morning.
|
||||
- Sets up the X18/audio board and makes the required sound connections.
|
||||
- Uses the school building's speakers for in-room sound.
|
||||
- Adolfo:
|
||||
- Connects the audio feed at the back table where the livestream computer is located.
|
||||
- Sets up the Canon M50 Mark II on the tripod.
|
||||
- Runs HDMI from the Canon M50 Mark II to the ATEM Mini.
|
||||
- Connects/places the ATEM Mini with the livestream interface setup.
|
||||
- Oversees the livestream computer/workflow.
|
||||
- Dzidula Boney:
|
||||
- Runs lyrics.
|
||||
- Sara Gianelli:
|
||||
- Trainee for lyrics.
|
||||
- Helps on the livestream computer.
|
||||
- Sometimes translates, so she may split attention between translation and media support.
|
||||
- Sinae Gianelli:
|
||||
- Camera trainee.
|
||||
- Gary Collins:
|
||||
- Previously helped with cameras and livestream.
|
||||
- Currently less active because of job changes and the transition to the school location, but should still be considered a possible support person.
|
||||
- Brother Gino Gianelli:
|
||||
- Helps with editing.
|
||||
- Eli Lastra:
|
||||
- Overall content creator supervisor.
|
||||
- Provides the eye for quality and content standards.
|
||||
|
||||
### Remaining Areas to Capture
|
||||
- Exact computer/device model and specs.
|
||||
- Exact audio interface model.
|
||||
- Number of microphones/instruments/audio sources normally mixed.
|
||||
- Local OBS recording settings and file naming/storage pattern.
|
||||
- Whether edited versions replace the Subsplash archive or are used separately.
|
||||
- Pre-service checklist and post-service checklist.
|
||||
|
||||
## Current Video Generation Process
|
||||
_To be documented._
|
||||
|
||||
Suggested areas to capture:
|
||||
### Desired Outputs From Each Sunday / Event
|
||||
The desired post-production system should be able to create all of the following from each Sunday service or special event:
|
||||
- Full sermon/service archive.
|
||||
- Sermon clips and short-form videos.
|
||||
- Quote graphics.
|
||||
- Bilingual captions.
|
||||
- Translated versions when useful/possible.
|
||||
- YouTube uploads.
|
||||
- Facebook posts.
|
||||
- Announcement videos.
|
||||
- Weekly outreach content for The Walking Voice Media.
|
||||
|
||||
### Current Editing / Content Creation Tools
|
||||
- Adolfo:
|
||||
- Uses the Subsplash editor for simple trims.
|
||||
- Uses Final Cut for some edits.
|
||||
- Currently does relatively few edits personally.
|
||||
- Brother Gino Gianelli:
|
||||
- Works on Windows.
|
||||
- Likely uses DaVinci Resolve.
|
||||
- Desired direction:
|
||||
- Explore shifting some editing work to AI-assisted editing.
|
||||
- AI editing has not been tried yet in this workflow.
|
||||
|
||||
### Content Review / Approval
|
||||
- Most content is reviewed/approved by Adolfo and Eli Lastra.
|
||||
- Apostle David, head of the international ministry, is included sometimes when the content needs higher-level ministry/message approval.
|
||||
|
||||
### Publishing Goals / Cadence
|
||||
- Every Sunday full service is published on Subsplash automatically after the livestream.
|
||||
- YouTube publishing is selective: only publish when the content is strong enough.
|
||||
- When a new YouTube piece is published, create 3–5 Shorts per week from that content, distributed to both YouTube and Facebook.
|
||||
- Facebook posts are occasional outside of the shorts flow.
|
||||
- The Walking Voice Media target cadence: 1–2 outreach pieces per month.
|
||||
|
||||
### YouTube Selection Standard
|
||||
- A message is strong enough for YouTube when it is a well-prepared teaching with the clear intention of being shared publicly for outreach.
|
||||
- Default assumption: ordinary full Sunday services remain available through Subsplash; YouTube is for intentional public/outreach content.
|
||||
|
||||
### Storage / Archive
|
||||
- Current long-term storage is the NAS at Adolfo's home.
|
||||
- NAS capacity: 8TB.
|
||||
- The NAS is currently filling up.
|
||||
- Home internet is 1GB parallel/symmetric internet, making the home NAS a practical central archive location.
|
||||
- Current media is not well organized and/or indexed.
|
||||
- Need future storage plan because the current NAS is filling up.
|
||||
- The team is interested in potential software solutions for media organization, indexing, search, and archive management.
|
||||
|
||||
### Desired Media Index / Search Fields
|
||||
The media archive should make it easy to find content by:
|
||||
- Speaker.
|
||||
- Date.
|
||||
- Event name.
|
||||
- Scripture/reference.
|
||||
- Topic/theme.
|
||||
- Language.
|
||||
- People in the video.
|
||||
- Quote/transcript search.
|
||||
|
||||
### Archive System Preference
|
||||
- Preferred archive/search system should be NAS-based.
|
||||
- Local/private NAS storage is the desired primary home for originals, edited exports, and searchable/indexed media data.
|
||||
- Cloud tools may still be evaluated for publishing or specific workflows, but the archive preference is NAS-first.
|
||||
|
||||
### Remaining Areas to Capture
|
||||
- Source material: sermon recordings, livestream downloads, clips, photos, scripts.
|
||||
- AI tools used: ChatGPT, Meta AI, image/video tools, transcription tools, editing tools.
|
||||
- Specific AI tools to evaluate for transcription, clip selection, captions, and social repurposing.
|
||||
- Editing workflow: clipping, captions, color/audio cleanup, branding, export presets.
|
||||
- Output formats: short clips, reels, sermon excerpts, announcement videos, thumbnails.
|
||||
- Publishing flow: platform, cadence, approval, descriptions, hashtags, metadata.
|
||||
- Archiving: where original files, exports, and project files are stored.
|
||||
- Publishing details: descriptions, hashtags, metadata.
|
||||
- Exact folder/naming convention for originals, edited exports, thumbnails/graphics, and project files.
|
||||
|
||||
## Pain Points / Open Questions
|
||||
- What parts of the livestream currently feel least professional?
|
||||
|
||||
Reference in New Issue
Block a user