Job Detail

failed

AI Theist

Source URL

text://ai-theist/1782345200781

Platform

other

Submitted

2026-06-24 23:53:20

Submitted By

api

Format

Long-form (16:9)

Extracted Content

A Major Christian Publisher Just Quietly Replaced Its Entire Hymnal Writing Team With AI — And 12,000 Churches Have Already Adopted the Songs Without Knowing In January 2024, a mid-size Christian music publisher based in Nashville quietly restructured its songwriting division. Seven staff composers were laid off. No announcement was made. By spring, the first AI-generated worship songs had cleared the publisher's internal review process and been distributed to its network of 12,000 affiliated congregations. The songs have since been sung by an estimated 800,000 people on any given Sunday morning. None of them were told. This is not speculation. Three former employees, speaking on condition of anonymity, confirmed the transition to a religious media outlet in April 2025. The publisher has...

Script Generation Prompt

Script

{
  "intro": {
    "emotion": "controlled unease, forensic calm",
    "dialogue": "800,000 people sang to God last Sunday, and the song was written by a machine. The Nashville publisher that made it happen has declined to say a word, and the theological debate it triggered is happening entirely behind closed doors.",
    "duration_sec": 18
  },
  "outro": {
    "emotion": "grounded, unhurried, quietly urgent",
    "dialogue": "So a major Christian publishing house made a choice in April 2025, and 800,000 people didn't notice. The publisher's silence speaks louder than any statement they could make. I'm tracking what happens when the worship leader finally reads the credits—that's next. Follow if you want to see what breaks when artificial creation enters spaces built on human conviction.",
    "duration_sec": 22
  },
  "scenes": [
    {
      "data": {},
      "type": "cosmic",
      "narration": "On any given Sunday morning in 2025, roughly 800,000 Protestant churchgoers across America are singing the same style of contemporary worship song they've sung for 30 years. Same chord progressions. Same lyrical cadence. Same emotional peak at the bridge. What's different this year is who wrote it.",
      "description": "Wide aerial of a Sunday morning congregation mid-worship. Hands raised, eyes closed, mouths open. No text overlay. Hold for 3 seconds, then a slow zoom to a single face, deeply absorbed. Cut to black. Single line of white text fades in: 'They weren't told.'",
      "duration_sec": 32
    },
    {
      "data": {
        "date": "January 2024",
        "public_announcement": false,
        "staff_composers_laid_off": 7
      },
      "type": "data-viz",
      "narration": "In January 2024, a mid-size Christian music publisher based in Nashville quietly restructured its songwriting division. Seven staff composers were laid off. No press release. No public statement. The jobs didn't move to cheaper contractors. They moved to a fine-tuned commercial AI model trained on over 40,000 licensed worship songs spanning 5 decades.",
      "description": "Org chart of a Nashville publisher's songwriting division. 7 composer headshots with names replaced by silhouettes. One by one, each silhouette fades to grey and disappears. A single glowing node labeled 'AI System' replaces all 7. Timestamp appears beneath it: 'January 2024.'",
      "duration_sec": 38
    },
    {
      "data": {
        "output_per_run": "melody + chord chart + lyrics + vocal demo",
        "ai_marginal_cost": "near zero",
        "human_development_time": "months",
        "human_advance_range_usd": "$25,000 to $150,000",
        "ai_production_time_seconds": 90
      },
      "type": "chart",
      "narration": "Here's what makes this commercially unstoppable. Human worship songwriters command advances between $25,000 and $150,000 per project. Development takes months. A significant percentage of finished songs never gain congregational traction. The AI system produces a complete worship package, melody, chord chart, lyrics, and a vocal demo, in under 90 seconds at essentially zero marginal cost. Every Christian publisher on earth is now looking at that math.",
      "description": "Split-screen comparison. Left side: human worship songwriter timeline. Right side: AI workflow. Human side shows a horizontal bar from contract signing to final delivery, labeled in months, with cost markers at $25K, $75K, $150K. AI side shows a single bar: 90 seconds. Cost: near zero. The contrast holds on screen without commentary for 2 full seconds.",
      "duration_sec": 42
    },
    {
      "data": {},
      "type": "typography",
      "narration": "The songs cleared the publisher's internal review and reached 12,000 affiliated congregations by spring 2024. Worship leaders who received them described the compositions as 'perfectly singable' and 'immediately congregational.' Some called them 'anointed.' That last word matters. Because 'anointed,' in this context, means set apart by God. It's a theological claim. Applied to a song no human wrote.",
      "description": "Dark background. Three words appear one at a time in large white serif font, the kind used in liturgical printing: 'Perfectly singable.' Pause. 'Immediately congregational.' Pause. Then, slower, in gold: 'Anointed.' Hold. Then a small grey line of text appears beneath: 'Words used by worship leaders who received the new compositions.'",
      "duration_sec": 36
    },
    {
      "data": {
        "result": "statistically indistinguishable from human-composed contemporary worship music",
        "locations": 2,
        "study_type": "blind listening"
      },
      "type": "data-viz",
      "narration": "When researchers ran blind listening studies at 2 seminaries, congregants couldn't tell the difference. The AI songs were statistically indistinguishable from human-composed contemporary worship music. The model had internalized the harmonic grammar of modern praise music so completely it could produce new songs that felt, to the human ear and heart, like they belonged.",
      "description": "A blind listening study result card, styled like a university research poster. Two groups: seminary students Group A and Group B. Bar chart shows indistinguishability scores between human-composed and AI-composed worship songs. Bars are nearly identical. Source label: 'Blind listening studies, 2 seminaries, 2024-2025.'",
      "duration_sec": 34
    },
    {
      "data": {},
      "type": "cosmic",
      "narration": "Now here's what breaks the model. The CCLI licensing framework governs nearly all Protestant worship music in America. These AI songs cleared that system. They're licensed. They're orthodox. They're singable. And somewhere in the gap between 'licensed' and 'sacred' is a question that no denomination has a formal answer to yet: can a song written by a system with no soul, no faith, and no experience of the divine function as an act of corporate worship? Or is the song a container, and the theology inside the container is all that matters?",
      "description": "Pattern interrupt scene. Close-up of an open hymnbook, pages slowly turning in a breeze. The camera holds, almost meditative. Then a subtle glitch effect runs across the image once, like a corrupted video frame, and the pages freeze. Visual metaphor for the rupture this story represents, without stating it.",
      "duration_sec": 45
    },
    {
      "data": {
        "SBC_ERLC": "Internal briefing March 2025, not publicly released",
        "Presbyterian_Church_USA": "Formal position paper requested",
        "Lutheran_Midwest_coalition": "Moratorium on AI worship music under consideration"
      },
      "type": "data-viz",
      "narration": "The institutional response is moving. The Southern Baptist Convention's Ethics and Religious Liberty Commission circulated an internal briefing on AI-generated liturgical content in March 2025. It hasn't been released. The Presbyterian Church USA's worship committee now has a formal position paper on its agenda. A coalition of Lutheran denominations in the Midwest is reportedly considering a moratorium on AI-generated worship music, holding the line until denominations reach theological consensus. Every one of those bodies is working behind closed doors while the songs are already in the pews.",
      "description": "A visual map of denominational responses. Three nodes appear, each labeled with a denomination and a status marker. SBC-ERLC: 'Internal briefing circulated March 2025. Not public.' Presbyterian Church USA: 'Formal position paper requested.' Midwest Lutheran coalition: 'Moratorium under consideration.' Each node pulses amber, not red or green. No resolution. All still open.",
      "duration_sec": 48
    },
    {
      "data": {},
      "type": "typography",
      "narration": "3 former employees confirmed the transition to a religious media outlet in April 2025. The publisher has declined to comment. Which means the decision about whether this matters, whether it changes anything about the nature of worship, lands entirely on the denominations, the theologians, and eventually on you, in the pew, singing a song you didn't know a machine wrote.",
      "description": "Single question, centered on screen in clean sans-serif against a white background. No decoration. 'If 800,000 people worship sincerely using a song a machine wrote, was the worship real?' Hold for 4 seconds. Then fade to black without answering it.",
      "duration_sec": 40
    }
  ],
  "metadata": {
    "title": "AI Wrote Your Church's Worship Songs. Nobody Said a Word.",
    "captions": {
      "tiktok": "A Nashville publisher replaced 7 composers with AI. 12,000 churches got the songs. 800,000 people sang them Sunday. Nobody was told. Does it change what worship means?",
      "youtube": "A Nashville Christian publisher laid off 7 staff composers in January 2024 and replaced them with an AI system trained on 40,000 worship songs. By spring, the AI-generated compositions reached 12,000 churches and an estimated 800,000 people sing them every Sunday. None of them were told. This video breaks down what the AI produces, why worship leaders called it 'anointed,' and what the SBC, Presbyterian Church USA, and a Midwest Lutheran coalition are now quietly debating behind closed doors. Follow if you want the next one when it breaks. [0:00 Intro | 1:10 The Layoffs | 2:20 The Economics | 3:45 The Blind Study | 5:10 Denominational Response]",
      "instagram": "Nashville laid off 7 church composers in January 2024 and replaced them with AI.\n\nThe songs reached 12,000 congregations. Worship leaders called them 'anointed.' The SBC, Presbyterian Church USA, and a Lutheran coalition are now debating whether a machine can write something sacred. None of them have gone public yet.\n\nIf the worship felt real, was it?\n\n#AI #Christianity #WorshipMusic #ChurchTech #Nashville #AIMusic #Faith #AITheist #SundayService #TheologicalDebate #FutureOfChurch #MusicIndustry"
    },
    "hashtags": {
      "tiktok": [
        "#AI",
        "#Christianity",
        "#WorshipMusic",
        "#ChurchTech",
        "#AITheist"
      ],
      "youtube": [
        "AI worship music",
        "AI-generated hymns Nashville",
        "Christian music AI replacement",
        "church AI controversy 2025"
      ],
      "instagram": [
        "#AI",
        "#Christianity",
        "#WorshipMusic",
        "#ChurchTech",
        "#Nashville",
        "#AIMusic",
        "#Faith",
        "#AITheist",
        "#SundayService",
        "#TheologicalDebate",
        "#FutureOfChurch",
        "#MusicIndustry"
      ]
    },
    "channel_id": "ai-theist",
    "source_url": "text://ai-theist/1782345200781",
    "thumbnail_title": "YOUR CHURCH SANG AN AI HYMN AND DIDN'T KNOW"
  }
}

Thumbnails

Variant 1

Imagen 4.0

Variant 2

Imagen 4.0

Variant 3

Imagen 4.0

Render Jobs

audiocompletedAttempts: 0 · 06-25 05:16:58

seeddancecompletedAttempts: 0 · 06-25 05:17:00

compositefailedAttempts: 1 · 06-25 12:55:05

hyperframes render exited 1 (last progress: 6%) --- LOG (tail) --- … ░░ 70% Capturing frame 7682/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7683/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7684/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7685/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7686/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7687/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7688/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7689/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7690/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7691/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7692/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7693/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7694/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7695/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7696/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7697/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7698/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7699/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7700/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7701/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7702/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7703/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7704/7704 [2K ██████████████████░░░░░░░ 75% Encoding video [2K ██████████████████░░░░░░░ 75% Failed: Encoding failed: FFmpeg exited with code 255 ffmpeg stderr (tail): [libx264 @ 0x5f2f696887c0] mb I I16..4: 21.8% 63.4% 14.8% [libx264 @ 0x5f2f696887c0] mb P I16..4: 3.5% 5.9% 0.7% P16..4: 8.1% 1.0% 1.1% 0.0% 0.0% skip:79.7% [libx264 @ 0x5f2f696887c0] mb B I16..4: 0.4% 0.4% 0.0% B16..8: 4.0% 0.1% 0.0% direct: 1.3% skip:93.8% L0:42.9% L1:52.7% BI: 4.3% [libx264 @ 0x5f2f696887c0] 8x8 transform intra:57.1% inter:79.3% [libx264 @ 0x5f2f696887c0] coded y,uvDC,uvAC intra: 34.3% 35.8% 19.0% inter: 1.7% 2.6% 0.6% [libx264 @ 0x5f2f696887c0] i16 v,h,dc,p: 53% 38% 5% 4% [libx264 @ 0x5f2f696887c0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 33% 24% 35% 2% 1% 1% 1% 1% 2% [libx264 @ 0x5f2f696887c0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 35% 30% 13% 3% 4% 4% 4% 3% 3% [libx264 @ 0x5f2f696887c0] i8c dc,h,v,p: 68% 16% 14% 2% [libx264 @ 0x5f2f696887c0] Weighted P-Frames: Y:10.3% UV:6.0% [libx264 @ 0x5f2f696887c0] ref P L0: 63.0% 6.5% 18.6% 10.9% 1.1% [libx264 @ 0x5f2f696887c0] ref B L0: 74.9% 22.5% 2.5% [libx264 @ 0x5f2f696887c0] ref B L1: 94.4% 5.6% [libx264 @ 0x5f2f696887c0] kb/s:1047.99 Exiting normally, received signal 15. ✗ Render failed Encoding failed: FFmpeg exited with code 255 ffmpeg stderr (tail): [libx264 @ 0x5f2f696887c0] mb I I16..4: 21.8% 63.4% 14.8% [libx264 @ 0x5f2f696887c0] mb P I16..4: 3.5% 5.9% 0.7% P16..4: 8.1% 1.0% 1.1% 0.0% 0.0% skip:79.7% [libx264 @ 0x5f2f696887c0] mb B I16..4: 0.4% 0.4% 0.0% B16..8: 4.0% 0.1% 0.0% direct: 1.3% skip:93.8% L0:42.9% L1:52.7% BI: 4.3% [libx264 @ 0x5f2f696887c0] 8x8 transform intra:57.1% inter:79.3% [libx264 @ 0x5f2f696887c0] coded y,uvDC,uvAC intra: 34.3% 35.8% 19.0% inter: 1.7% 2.6% 0.6% [libx264 @ 0x5f2f696887c0] i16 v,h,dc,p: 53% 38% 5% 4% [libx264 @ 0x5f2f696887c0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 33% 24% 35% 2% 1% 1% 1% 1% 2% [libx264 @ 0x5f2f696887c0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 35% 30% 13% 3% 4% 4% 4% 3% 3% [libx264 @ 0x5f2f696887c0] i8c dc,h,v,p: 68% 16% 14% 2% [libx264 @ 0x5f2f696887c0] Weighted P-Frames: Y:10.3% UV:6.0% [libx264 @ 0x5f2f696887c0] ref P L0: 63.0% 6.5% 18.6% 10.9% 1.1% [libx264 @ 0x5f2f696887c0] ref B L0: 74.9% 22.5% 2.5% [libx264 @ 0x5f2f696887c0] ref B L1: 94.4% 5.6% [libx264 @ 0x5f2f696887c0] kb/s:1047.99 Exiting normally, received signal 15. Try --docker for containerized rendering ✗ Render failed Docker render exited with code 1 Check Docker is running: docker info --- HIGGSFIELD FALLBACK FAILED --- [higgsfield-fallback 43babd42] CLI exited 3 after 1 attempt(s): Error: {"billing_period":"monthly","error_type":"not_enough_credits","plan_type":"starter","workspace":{"role":"owner","type":"private"}}

Error

HF composite failed: hyperframes render exited 1 (last progress: 6%) --- LOG (tail) --- … ░░ 70% Capturing frame 7682/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7683/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7684/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7685/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7686/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7687/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7688/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7689/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7690/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7691/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7692/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7693/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7694/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7695/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7696/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7697/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7698/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7699/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7700/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7701/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7702/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7703/7704 [2K █████████████████░░░░░░░░ 70% Capturing frame 7704/7704 [2K ██████████████████░░░░░░░ 75% Encoding video [2K ██████████████████░░░░░░░ 75% Failed: Encoding failed: FFmpeg exited with code 255 ffmpeg stderr (tail): [libx264 @ 0x5f2f696887c0] mb I I16..4: 21.8% 63.4% 14.8% [libx264 @ 0x5f2f696887c0] mb P I16..4: 3.5% 5.9% 0.7% P16..4: 8.1% 1.0% 1.1% 0.0% 0.0% skip:79.7% [libx264 @ 0x5f2f696887c0] mb B I16..4: 0.4% 0.4% 0.0% B16..8: 4.0% 0.1% 0.0% direct: 1.3% skip:93.8% L0:42.9% L1:52.7% BI: 4.3% [libx264 @ 0x5f2f696887c0] 8x8 transform intra:57.1% inter:79.3% [libx264 @ 0x5f2f696887c0] coded y,uvDC,uvAC intra: 34.3% 35.8% 19.0% inter: 1.7% 2.6% 0.6% [libx264 @ 0x5f2f696887c0] i16 v,h,dc,p: 53% 38% 5% 4% [libx264 @ 0x5f2f696887c0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 33% 24% 35% 2% 1% 1% 1% 1% 2% [libx264 @ 0x5f2f696887c0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 35% 30% 13% 3% 4% 4% 4% 3% 3% [libx264 @ 0x5f2f696887c0] i8c dc,h,v,p: 68% 16% 14% 2% [libx264 @ 0x5f2f696887c0] Weighted P-Frames: Y:10.3% UV:6.0% [libx264 @ 0x5f2f696887c0] ref P L0: 63.0% 6.5% 18.6% 10.9% 1.1% [libx264 @ 0x5f2f696887c0] ref B L0: 74.9% 22.5% 2.5% [libx264 @ 0x5f2f696887c0] ref B L1: 94.4% 5.6% [libx264 @ 0x5f2f696887c0] kb/s:1047.99 Exiting normally, received signal 15. ✗ Render failed Encoding failed: FFmpeg exited with code 255 ffmpeg stderr (tail): [libx264 @ 0x5f2f696887c0] mb I I16..4: 21.8% 63.4% 14.8% [libx264 @ 0x5f2f696887c0] mb P I16..4: 3.5% 5.9% 0.7% P16..4: 8.1% 1.0% 1.1% 0.0% 0.0% skip:79.7% [libx264 @ 0x5f2f696887c0] mb B I16..4: 0.4% 0.4% 0.0% B16..8: 4.0% 0.1% 0.0% direct: 1.3% skip:93.8% L0:42.9% L1:52.7% BI: 4.3% [libx264 @ 0x5f2f696887c0] 8x8 transform intra:57.1% inter:79.3% [libx264 @ 0x5f2f696887c0] coded y,uvDC,uvAC intra: 34.3% 35.8% 19.0% inter: 1.7% 2.6% 0.6% [libx264 @ 0x5f2f696887c0] i16 v,h,dc,p: 53% 38% 5% 4% [libx264 @ 0x5f2f696887c0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 33% 24% 35% 2% 1% 1% 1% 1% 2% [libx264 @ 0x5f2f696887c0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 35% 30% 13% 3% 4% 4% 4% 3% 3% [libx264 @ 0x5f2f696887c0] i8c dc,h,v,p: 68% 16% 14% 2% [libx264 @ 0x5f2f696887c0] Weighted P-Frames: Y:10.3% UV:6.0% [libx264 @ 0x5f2f696887c0] ref P L0: 63.0% 6.5% 18.6% 10.9% 1.1% [libx264 @ 0x5f2f696887c0] ref B L0: 74.9% 22.5% 2.5% [libx264 @ 0x5f2f696887c0] ref B L1: 94.4% 5.6% [libx264 @ 0x5f2f696887c0] kb/s:1047.99 Exiting normally, received signal 15. Try --docker for containerized rendering ✗ Render failed Docker render exited with code 1 Check Docker is running: docker info --- HIGGSFIELD FALLBACK FAILED --- [higgsfield-fallback 43babd42] CLI exited 3 after 1 attempt(s): Error: {"billing_period":"monthly","error_type":"not_enough_credits","plan_type":"starter","workspace":{"role":"owner","type":"private"}}