Update EMI media livestream planning

projects/emi_media_outreach_youtube_strategy.md

@@ -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]]

projects/livestream_video_generation_process.md

@@ -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?