u/k-r-a-u-s-f-a-d-r

MiniMax released MiniMax-Music3 today (Aug 13, 2026), with open weights on Hugging Face, GitHub, and ModelScope.

The gist:

Give it a creative concept and optional lyrics, and it composes, arranges, performs, and produces a complete song in one generation, up to five minutes long. (MiniMax) Output is 32 kHz, 16-bit stereo. (ComfyUI Blog)

Architecture is a hybrid: an 8B "Global LLM" (initialized from Qwen3-8B) handles long-range structure, a 0.6B "Local LLM" fills in frame-level acoustic detail, and a 2.4B flow-matching synthesis stage fuses both models' hidden states instead of decoding from discrete tokens alone. (ComfyUI Blog)

Weights are under the MiniMax-Music3 Community License, and ComfyUI already has native support with an official text-to-music workflow (ComfyUI) — requires ComfyUI 0.33.0 or newer.

TL/DR: The dildo of justice always arrives unlubed

...

Last updated: August 2026.

Before you share anything

This information doesn't constitute legal advice or encouragement to engage in fanediting or filesharing. It's worth being clear eyed about the situation: distributing a fanedit of a commercially released film is copyright infringement in essentially every jurisdiction. This has criminal penalties. Our community's "you must own the source" rule is an ethical commitment we make to studios and filmmakers, not a legal defense. No court recognizes it, and it's never been tested successfully. Fair use and fair dealing arguments for transformative edits exist in theory, but they get much weaker once you're distributing a full length version of a commercial product.

If you decide to engage in this activity, make a few sensible choices:

• Every host will take your file down if the rights holder asks. Plan for it rather than being surprised by it. You don’t want to lose your only copy of an edit.
• Account termination is the realistic worst case for most editors. Legal action is rare but not zero, and it has tended to find people who got loud, monetized, or hosted publicly at scale.
• Never charge money. Selling or Patreon gating a fanedit is the most reliable way to turn "studio ignores you" into "studio sends a letter." It's also the fastest way to lose the community's goodwill, which is harder to get back. EVEN IF YOU RATIONALIZE YOU ARE ONLY ACCEPTING DONATIONS TO COVER HOSTING FEES, THIS IS STILL MONETIZATION AND YOU WILL BE PERMANENTLY BANNED FROM THE FANEDITS SUBREDDIT.
• Don't use studio logos on your fanedit artwork.
• Add a disclaimer to the beginning of your fanedit so it could not be mistaken for the original version.
• Steer clear of leaked workprints and pre release material. That's a different risk category entirely, and the major communities won't list edits made from them.
• Consider giving a new commercial release some breathing room to make its sales before rushing your release out the door. Good edits take time, and there's no prize for being first with a rushed one. The edits people still talk about years later are the ones that took their time to do a good job.

Container and codec:

• MKV is the default. It carries multiple audio tracks, subtitles, chapters, and attachments. Use it unless you have a specific reason not to.
• MP4 works if your audience is on Apple TV, older smart TVs, or Plex clients that choke on MKV. It can't hold everything MKV can, so it's a compatibility trade rather than an upgrade.
• H.264 (x264) gives you maximum compatibility; it plays on everything, at the cost of larger files.
• H.265 (x265) gets you roughly 40 to 50% smaller files at equivalent quality, though older hardware and some older TVs won't direct play it.
• AV1 is viable on modern hardware now, but it's still a compatibility gamble with a general audience.

Sharing:

Torrent

A seedbox (a rented server, around $5 a month) is the usual solution for the technically inclined.

MEGA

Still the community's default, largely for one structural reason: the decryption key lives in the URL fragment after the #, and fragments are never sent to the server. MEGA physically cannot see what's in your file unless someone hands them a working link, which means no proactive content scanning.

• Free: 20 GB base storage. No per file size cap within your storage.
• Download quota is the sticking point. Free downloaders are limited by IP address to roughly 5 GB per rolling six hour window, so a 12 GB edit takes them multiple sessions. Worth mentioning when you send a link, otherwise people can assume it's broken. Using a VPN and switching the VPN server mid download can circumvent this restriction.
• Paid: transfer quota is tied to the account, and Pro tier effectively removes sharing limits, so no more pause at the 5GB mark.
• Link structure: MEGA/file/XXXXXXXX#KEYKEYKEYKEY. Many editors send the file ID and the key separately, or ask recipients to reassemble them, which keeps a complete working link out of crawler reach.
• MEGA does honor valid takedown requests, and repeat reports get accounts terminated along with everything in them. Keep another copy elsewhere.

Google Drive (Consider Avoiding)

Convenient and integrated, but this is the one popular beloved host to consider avoiding for fanedits specifically.

• Free: 15 GB shared across Drive, Gmail, and Photos. The individual file cap is enormous (5 TB), so size isn't the issue.
• Google actively scans and fingerprints uploaded content, private files included, against known work databases. A full length film derived from a commercial release is close to the exact thing that system was built to catch. Detection usually means the file gets flagged and access restricted, and repeated hits can put your entire Google account at risk, email, photos, everything. That's a lot to have riding on one upload.
• To make matters worse, "Download quota exceeded" happens even when a file isn't flagged, a popular share gets locked for around 24 hours once enough people pull it. There's no setting to adjust this, and it tends to hit right when your release is getting attention. Downloads from free Google Drive are faster than free Mega, until Google Drive freezes up unexpectedly.

MediaFire

• Free: 10 GB storage.
• Downloads are ad supported with no bandwidth cap, which is a real advantage: no quota walls for your audience. The tradeoff is a download page cluttered with fake download buttons that can confuse less technical users, so a quick "click the green one" in your message goes a long way.
• MediaFire removes data from accounts it considers abandoned after two warning emails over roughly 15 days. Logging in periodically keeps your archive alive.

Pixeldrain (Avoid free tier)

Increasingly popular, and pleasantly simple, but avoid using the free version since your fanedit will be flushed down the drain.

• Free uploads up to 20 GB per file.
• It uses a shared bandwidth pool per file rather than a hard cap: each file gets an allotment of free transfer, and once that's drained, downloads throttle hard for everyone until it resets or someone buys transfer credit. Popular files get slower over time, which is the opposite of what you want on release day.
• Free files expire after a period of inactivity (roughly 60 days, extended by access). Pro (~€2 to 12/month depending on tier) keeps them indefinitely.

Gofile (Avoid free tier)

Avoid the free version since it will quickly delete your file.

• No account required, and no stated file size limit.
• Files are deleted after about 10 days with no downloads, so it's not somewhere to leave things.
• Free downloads are throttled and served with ads.

1fichier (Avoid free tier)

Popular in the European scene. Large per file limits, generous free storage for registered users, and files expiring after roughly 30 days of inactivity on free tiers. Free downloads are throttled with wait timers to push premium, so the experience isn't lovely, but it's durable in practice and less aggressively policed than the US majors.

Dropbox / OneDrive (Avoid)

Both scan content, and both cap shared link bandwidth. Dropbox Basic links get suspended after roughly 20 GB of traffic per day. OneDrive also ties everything to a Microsoft account that probably holds things you'd rather not lose. There are better options above.

Internet Archive (Avoid)

It's fully public, indexed by search engines, and receives DMCA notices constantly, so it won't serve you well. More importantly, it's a preservation nonprofit under significant legal pressure right now, and putting infringing material there does real harm to an institution that a lot of media preservation depends on including, eventually, the films we all edit.

https://preview.redd.it/f1jk08v808hh1.jpg?width=1824&format=pjpg&auto=webp&s=a95fe87b656e5c86042d6bb5b36d93e6f090b446

Standing beside Iraq's prime minister last week, President Trump said the war in Iran was bringing the Middle East together "like it's never come together before."

He said this in the same week officials from the Gulf Cooperation Council, the alliance of six Arab monarchies that has anchored American power in the region since 1981, were telling reporters the organization had stopped functioning. He said it three months after one member quit OPEC on the morning another member was chairing a summit devoted to unity. He said it while Saudi Arabia and the United Arab Emirates, the two pillars of the whole arrangement, were backing opposite sides in Sudan, trading recriminations over Yemen, and declining to answer questions about whether they were still speaking to each other.

Americans deserve a clearer accounting, because the bill for this comes due long after the shooting stops.

Start with the detail that should trouble you most. Over the past five months, four Gulf states sent their own aircraft to strike targets inside Iran. Emirati jets destroyed a refinery on Lavan Island. Saudi pilots hit missile launch sites. Bahraini and Kuwaiti jets went after drone depots in July. Not one of those governments has admitted it.

These were countries willing to take enormous risks on our side. What they would not do was be seen doing it. Association with this administration had become dangerous enough. With their own public, with Tehran, with their own arithmetic about how long American backing lasts, that they preferred to fight in the dark. That is a relationship where the partner is managing its exposure to you, and it is worth a great deal less than the one we had in February.

We got there through a sequence of specific choices, each avoidable.

We bombed during our own negotiations. Oman convened indirect talks in early February, and its foreign minister reported real progress with Iran willing to concede ground. The president said he was "not thrilled." Three weeks later the missiles flew. Whatever you think of the Iranian regime, this taught every government watching that talking to Washington offers no protection from Washington.

Then we threatened the mediator. When Oman (the neutral, the back channel, the one place both sides would sit down) worked out an arrangement with Iran over the Strait of Hormuz, the president told reporters Oman would behave like the others or we would have to destroy them. Oman was the most useful friend we had in this war.

We also threatened to disarm an ally under fire. Saudi Arabia declined to host an American operation to force shipping through Hormuz, judging correctly that it would draw more Iranian missiles onto Saudi soil. The White House responded by threatening to withhold the interceptor missiles Riyadh needed to shoot those missiles down. The Saudis relented. American officials then said the damage was permanent, and began studying how to reduce our presence in the kingdom. We threatened to take away a partner's air defense while it was being bombed, to make it accept more bombing. Every capital in the Gulf drew the obvious conclusion about what American protection is worth and how quickly it can be withdrawn.

When the UAE walked out of OPEC , a deliberate humiliation of Saudi Arabia, executed on the day the Saudi crown prince was chairing a unity summit, the president publicly endorsed the move. He was, at that moment, asking both countries for help.

In March he told reporters that regional allies were "fighting with us." They were. That was the precise thing they were risking their security to keep quiet.

And he kept announcing the end of it. There have been several declared halts since February, each of which unraveled. The war's stated goals have shifted repeatedly. On August 1 he announced the outline of a deal, one day after saying he was close to resuming heavy strikes. Iran has agreed to nothing. Allies cannot plan around a policy that changes with the news cycle, and they have stopped trying.

The costs are not abstract. A Tomahawk missile hit a school in Minab, Iran, killing 168 people, most of them children. A preliminary American investigation reportedly found we were responsible and had fired on outdated targeting data. Forty-six senators wrote asking about the rules of engagement and whether artificial intelligence had been used in targeting. Process failures of that kind are a leadership responsibility, and nobody has been held to it.

Meanwhile the region is quietly building its way around us. Kuwait is negotiating to send its oil through Saudi and Emirati pipelines. Abu Dhabi is laying new pipe to the Indian Ocean. Governments do not spend billions bypassing a waterway they expect America to keep open.

The clearest signal came on July 30, when Saudi Arabia announced a new maritime security alliance for the Red Sea with fourteen founding endorsements, from Turkey to Pakistan to Egypt to Somalia. The United States is not among them. Riyadh built a regional security architecture and did not invite the country that has guaranteed regional security for fifty years.

Iran, for its part, lost its Supreme Leader, much of its military, and enormous stretches of its infrastructure; and has seen its standing rise among Arab publics, because it was the one we were bombing.

Two-thirds of Americans oppose this war. That gets read as war-weariness. It is better understood as accuracy.

The measure of a war is not whether you destroy what you aimed at, but the position you hold when it ends. Five months in, our allies fight beside us anonymously, hedge toward Beijing openly, build infrastructure to reduce their dependence on our protection, and convene without us. The alliance we spent forty-five years assembling to contain Iran has been hollowed out by the campaign meant to defeat it.

Alliances are capital. They accumulate slowly, they are spent instantly, and they are very hard to borrow again.

 Sources:

The covert Gulf strikes on Iran are documented by the Wall Street Journal (May 11, 2026), Bloomberg (May 12), and the New York Times (May 14), the last citing three U.S. officials on both Saudi and Emirati operations; Reuters confirmed the Lavan Island refinery strike through Iran's own refining company on April 8. The Bahraini and Kuwaiti strikes rest on a single Wall Street Journal report in late July.

The account of GCC dysfunction and Saudi–Emirati estrangement comes from Politico (July 25), with the UAE's OPEC withdrawal analyzed by the Middle East Council. Project Freedom, the threat to withhold interceptor missiles from Saudi Arabia, and the resulting review of U.S. force posture were reported by the Wall Street Journal and carried widely, including by Euronews; neither Washington nor Riyadh has confirmed the threat. Trump's warning to Oman is on the record via Politico (May 27).

The Minab school strike and the subsequent Senate letter are drawn from the Congressional Research Service (March 26). The Red Sea alliance and its fourteen founding endorsements were announced by the Saudi Press Agency on July 30. Shifting war aims, the collapsed ceasefires, and the August 1 announcement are from the Associated Press; regional opinion data is from Arab Barometer, and American polling from Fox News and RealClearPolling.

Any editor who's finished many edits has some moments they are especially proud of. Please share those moments you've created yourself or watched in the comments. Try to keep it to one major moment per edit.

Here are my proudest moments from some of my edits:

Blade Runner Special Edition

Deckard's fight with Leon recut and ends with new VFX when he is shot in the head. Makes this sequence feel much stronger.

Dune The Mindkiller Cut

Meticulous rotoscoping to make all the Fremen's eyes bluer like the book. Whew!

Hannibal's Requiem (Hannibal Rising)

Moving the flashback of Hannibal as a boy being rescued in the snow to just after he gives the detective his actual testimony about what happened to him a a child creates the hard hitting dramatic edge that gets you right in the feels.

Léon - The Refined Cut

Cloning Leon's voice with the actor's French accent intact was difficult. Placing and blending in new dialogue of him telling Mathilda she is too young and that he could never love her in a romantic way was a tiny moment but felt momentous.

Maximus (edit of Gladiator)

Recutting material to make it clear that Commodus was actually sleeping with his sister, hits much harder. He lies down with her, but she doesn't leave. Yuck!

Terminator 2 Dehanced Edition

The completely redone opening sequence to set the stage in a non spoiler way followed by recreating the blinking cursor credits style from the original felt like a completely new movie.

The Terminator Enhanced Edition

Recutting and adding blood VFX to the police station massacre made this feel even more cold blooded and dark.

True Romance: A Hyperviolent Cut

The new VFX so the female lead blows James Gandalfini's head off with a shotgun was something I never thought I'd be able to do. I knew what I wanted to accomplish and figured out how to do the VFX in Resolve.

Starting July 5, I'm stepping back from editing or providing my fanedit info as an editor, but I'm staying on as a huge fan and viewer (and occasional reviewer over at FE.org), enjoying the great work everyone here puts out! More info on my Reddit profile under INFO if you're curious and want info on any of these before they disappear.

A Killer of Ducks and Presidents (edit of In The Line of Fire w/ The Red Apple Crew)

Babayka (edit combining John Wick 1 + 2)

Beyond the Wall (TV to Movie Edit of The Last of Us Season 1)

Blade Runner Special Edition

Charlie and the Chop Chop Factory (R-rated edit of Charlie and the Chocolate Factory)

Dinner With Hannibal (edit of Movie Version of Hannibal)

Django Runs From No One (edit of Django Unchained w/ The Red Apple Crew)

Do Androids Dream of Funkadelic Sheep (Blade Runner Grindhoused)

Dune - The Mindkiller Cut (edit of Dune Pt 1)

Hannibal's Requiem (edit of Hannibal Rising)

JL1 - Daughter of Themyscira (edit of Wonder Woman)

JL2 - Son of Krypton (edit combining Man of Steel and Batman v Superman)

JL3 - Justice League - Gods of Earth (edit of Zack Snyder's Justice League)

Kenobi (TV to Movie edit)

Kill Bill - The Bloodstained Bride

Kill Bill - The Whole Bloody Affair (Restructured)

Léon - The Refined Cut

M3gan [Recalibrated]

Matrix Resurrections DEmetaED

Maximus (edit of Gladiator)

Planet of the Apes 1968 Special Edition

Red Dragon - Definitive Cut

Shazam! The Magic Edition

Terminator 2 - Dehanced Edition

Terminator Dark Fate

Terrifier 2 - Slashed

The Batman

The Children

The Fly (1986) Special Edition

The Mist - Other Worlds Cut

The Terminator - Enhanced Edition

Titanic - Jack & Rose

True Romance - A Hyperviolent Cut

This is written from a studio engineer point of view; if you are pretty much amazed or even just content every time you push Suno's create button, this post is not for you.

Here's the real truth about about Suno versus Udio: Udio, probably even now, is still is better if you're typing in text prompts and hoping for the best. You can SOMETIMES get some genuinely impressive results that way, stuff that could potentially fool even experienced engineers after proper mastering. But most of what either platform spits out, the average output, is pretty terrible, and you need to know what you're listening for to identify the gems worth polishing.

Since Udio has started its descent into the dumpster fire that Uncharted Labs let UMG turn it into, Udio users might want to switch to Suno.

Where Suno really excels is as a music to music generator. When you feed it high quality reference tracks (not standard AI song outputs), it can SOMETIMES get surprisingly close to Udio's output quality. The key is using those references instead of relying on text prompts alone.

Let's talk about what makes AI music sound like AI music. The most obvious issue is the vocals. That fried, staticky quality is the dead giveaway, especially with Suno's text to music mode where you'll get it every time. The static can bleed into other instruments too, but vocals get hit the hardest. The other major problem is the high end, particularly on percussion. You'll hear fluttery artifacts, that swishy low bitrate sound, sometimes even rapid dropouts. Surprisingly, this is much more of an issue on Udio than it is Suno. Drums on Udio often sound very "rumpled."

Here's a trick for spotting these issues, especially the static charged vocals. Turn your volume WAAAAY down. At normal to loud listening levels, when you're really grooving, the masking effect hides that nasty static noise. But when you're listening from a technical standpoint at very low volume, it becomes really obvious. Even on very good Suno outputs, you'll often notice the verses might sound clean but the chorus reveals that static texture and also sounds thin.

Now for the actual workflow that gets you professional sounding results:

1. Always use reference songs, what Suno calls inspiration tracks. Make sure they're high quality, no artifacts, ideally not AI generated unless it's a really clean Udio output that's been polished and mastered in a DAW. Keep generating until you get BOTH a pleasing arrangement AND good sound quality. Don't settle. Even when using music references, Suno still churns out plenty of garbage sound alongside the good stuff. Model v5 is good for most modern genres. Resort to v4.5 if v5 doesn't get you what you want. Never use v5.5 unless you want a sonic mess, completely missing any normal midrange EQ, which cannot be salvaged in a DAW.

2. Check the song on different systems. Listen on headphones and speakers. Listen loud and listen quiet. Those static vocals hide at high volume but reveal themselves when you turn it down. And remember the verses can sound clean but then on the chorus the vocals are a static mess.

3. Once you've got a decent, usable output, create covers of it. Save the voice if you like how it sounds. You're not trying to change the genre here, you're basically making multiple takes of the same song (they may sound very different but you'll be surprised how easy they are to comp in a DAW). Using a saved voice helps keep the vocalist more consistent across covers. If one of the covers comes close but still has issues, use Suno Studio to isolate that part, for example a super staticky chorus, and have Studio try and redo it with better audio fidelity. You can literally put language in your Studio style prompt that tells it to make improvements like this: IMPROVE THE AUDIO FIDELITY, MAKE IT RADIO READY.

4. This is where it gets fun. Create stems to move all the best covers over into a DAW and frankenstein together the best parts from each cover. Grab the cleanest verse from one version, the best chorus from another. This is literally what professional engineers do when they're comping (compositing) different takes; with AI music, comping can now be done at the song level, not just vocal or instrument level. The best tool for creating stems for the DAW is called Ultimate Vocal Remover (you only need the standard 4 stems for great results). Don't use Suno stems; instead output the whole Suno track to WAV and then stem it yourself. Keep all four stems together when you're comping parts. Trying to swap just the vocal stem between different covers will usually give you weird artifacts and phase issues, even if you're using the other stems from another cover as the backing.

5. You'll need some DAW mixing and mastering skills, but modern plugins make this so much easier than it used to be. Check out Izotope RX11 for any cleanup work, and the Soundtoys and FabFilter collections for everything else. Here's a good example chain for the final effects bus from start of effect chain to end of effects chain:

a) STEREO CORRECTION: only if one of the stereo channels is consistently louder; in Resolve this is called "Stereo Fixer." It is sometimes needed but usually not.

b) LOW END SATURATION, PUNCH AND AMBIENCE: Soundtoys Effects Rack preset called "Tape Room." I usually remove the digital delay effect it adds though. This is the secret sauce for a bigger, better sound on an entire mix. Wet mix around 25% or to your liking.

c) STEREO WIDENING. Most outputs will benefit from widening the stereo image and Resolve has this built in called "Stereo Width". Tape Room does slight widening, but AI outputs generally need more.

d) FabFilter Pro-Q using the Subgroup Sorcery preset. Pro-Q is a dynamic EQ preset that mimics multi-band compression across the full frequency spectrum. For practical purposes, think of this as final mastering pass plus volume maximization. Change the output db depending on the volume of your material. You want to go to full red on the meter often but you don't want to live there.

e) FabFilter Pro-L. A must have step for perfect limiting without clipping. Many presets. There is also a built in limiter in Resolve that I do not recommend.

Note: I also use FabFilter and Soundtoys for reverb and delay, but this is not part of the final full mix mastering chain above; I add it to individual parts, for example the guitar solo, or the last word of a verse to give it some ping-pong delay.

The whole point is that Suno works best when you treat it like a session musician that needs multiple takes and careful editing, not a magic button that delivers finished tracks. And one of the best tips is to walk away from a song for a few days, then come back to it after the initial dopamine rush has worn off. At low volume, you'll hear what it really sounds like then.