DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to create an instrumental song from a genre and topic with Mortiflix OSS

Use the song pipeline to get a researched genre, checked score, MIDI and mastered track you can review.

  • Content
  • Advanced
  • 1 hour
  • From the README
  • Any agent

Who it is forA music hobbyist or content maker who needs an original instrumental track for a project.

The problemGenerating music from one prompt gives no way to check harmony, timing or the instrument choices.

The outcomeAn instrumental song with a written music sheet, MIDI and a measured master, approved at the blueprint and final stages.

What you need first

  • Node 20+
  • ffmpeg
  • Either a logged-in Claude Code install (your plan pays) or an Anthropic API key (you pay per token) for real videos
  • Optional: ElevenLabs API key for narration, sound effects and music
  • Linux is the most tested platform so far; Windows and macOS are not fully tested

Steps

  1. Run mortiflix init and mortiflix setup, and set up music in the setup walkthrough.
  2. Run mortiflix new song (inferred: pipeline name taken from the README table) and give a genre and a topic. (inferred, check the README)
  3. Run mortiflix run and review the blueprint with mortiflix review.
  4. Approve the blueprint and let the run continue through the score, MIDI and instrument choices.
  5. Approve the final mastered track.

Prompt for your agent

Using GTKottman/mortiflix-oss, create a song project for the genre <genre> and the topic <topic> with `mortiflix new song` (inferred command). Run `mortiflix run` and report the blueprint gate. Verify that the output includes a blueprint review before the final track.

Caveat. Music needs the setup step for the music engine, and the README gives no fixed track length or style limits for songs.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page