Fast Hours

Drew and Rory are back for episode 69, which is legally required to begin with at least one immature joke before immediately collapsing under the weight of Google’s latest AI product avalanche.This week, they dig into Google Omni, Gemini 3.5 Flash, Google Flow, Google Pics, Nano Banana, Veo, and whatever else Google launched before anyone had time to make coffee. The big question: are these actually meaningful creative upgrades, or did Google just throw 19 AI names into a blender and call it innovation?They break down early Omni and Flow tests, why video physics still feel weird, where Seedance and Kling may still be ahead, and why Runway Aleph 2.0 feels promising but imperfect. Rory shares hands-on examples with character swaps, driving videos, golf swings, agent mode, and Flow’s new tool-building features. Drew tries to keep the conversation coherent while quietly wondering if every AI product now needs a map, glossary, and mild sedative.The episode also gets into Gemini as a search replacement, creepy context awareness, privacy tradeoffs, AI tools connecting to personal data, the fuzzy definition of “agentic,” the limits of auto-clipping tools, GPT Image 2’s SynthID watermarking, metadata headaches for client work, and the universal pain of wasting $15 trying to make an image model spell “stump.”If you’re trying to understand what Google’s AI updates actually mean for creators, marketers, AI video workflows, image generation, creative direction, and the future of agentic media tools, this episode is half useful breakdown, half group therapy for people with too many tabs open.---⏱️ Fast Hour00:00 Cold open00:32 Google’s AI naming avalanche01:39 AI hype vs actual workflow value02:34 Why AI launches feel like iPhone upgrades06:12 Google’s “throw everything” strategy07:08 Omni vs Veo 4 expectations07:43 Video physics and speed problems09:03 Google Pics, Flow, Omni, and Flash10:04 How Rory actually uses Gemini11:51 Gemini 3.5 Flash breakdown12:38 AI benchmarks feel like marketing13:42 Gemini as a better search layer15:18 Creepy Gemini context awareness17:35 Why AI data connections feel too early19:15 The privacy tradeoff gets darker21:19 Google Omni vs Runway Aleph 2.022:12 Google Omni testing starts rough23:39 Google Veo 3.1 feels forgettable25:21 Why Omni feels early26:19 Higgsfield clipper test fails27:59 Why auto-clipping still misses31:30 Rory tests Flow and Omni live32:41 Omni character swap struggles33:33 Runway Aleph panda test34:07 Flow’s new interface and tools35:02 Building custom tools inside Flow36:10 The joy of making tools from nothing37:39 Agent mode for still-image workflows39:05 Batch creative directions in Flow40:03 Omni turns six images into video40:47 Driving physics still feel off41:55 Why consistency matters for adoption43:03 Kling, Seedance, and the update race43:59 Seedance handles complex camera motion45:42 GPT Image setup for golf video46:53 Testing the same prompt in Flow49:25 Why agentic platforms can feel thin51:10 The need for visual design systems52:21 Flow’s golf swing result53:56 Everyone is racing toward agentic54:18 What “agentic” actually means56:03 Claude feels more genuinely agentic57:04 Josh Hart quote analysis detour58:44 Reverse-engineering creative patterns59:53 Pizza, calzones, and prompt structure01:00:26 SynthID and GPT Image 2 watermarking01:01:47 Metadata problems for client work01:02:51 Google Pics enters the chat01:04:03 Too many image models to track01:04:52 Midjourney color still hits different01:06:01 GPT Image 2 quality frustration01:06:59 Image models still struggle with scale01:08:26 Bad AI weeks happen too01:09:20 Midjourney 8.2 speculation01:10:01 Tell your florist

In episode 68 of Fast Hours, Drew and Rory return from a two-week hiatus to prove that yes, the AI news cycle did continue without their permission. Rude.
They dig into Freepik changing its name to Magnific, why enterprise AI image tools are starting to feel more like creative operating systems, and how brands may be better off using approved model aggregators instead of building weird internal Franken-tools that immediately become outdated.
Then things get nerdier. Obviously.
Rory breaks down how he’s using Codex, GPT-Image-2, Claude Code, MCPs, Higgsfield, Seedance, and visual style reference sheets to create repeatable image systems, character references, and bulk creative workflows without living inside a giant text prompt forever. Drew pushes into where Midjourney V8.1 still dominates, especially photorealistic faces, color, texture, and images that do not look like corporate stock photography that lost the will to live.
They also talk about Midjourney’s upcoming 8.2, 8.3, V9 roadmap, edit model ambiguity, personalization drift, Luma Uni comparisons, Pinterest’s internal AI image model, Salesforce going headless, and why AI video audio still sounds like it was recorded inside a cursed podcast booth.
And because no episode is complete without accidentally getting philosophical, they close with the viral Claude Monet AI social experiment, the weird bias people bring to AI-generated images, and why “how it was made” keeps hijacking whether people can actually see what’s in front of them.
Basically, it’s an episode about the future of AI creative tools, with two guys trying to sound calm while the ground turns into soup beneath them.
--
⏱️ Fast Hour
00:00 Cold open01:12 AI news fatigue is real01:44 Claude Code runs the day now03:11 Remote work and coffee shop crimes08:21 3 Ninjas nostalgia break10:09 Freepik becomes Magnific11:47 Why Magnific works for enterprise13:00 Model aggregators vs internal tools18:01 Pinterest builds its own AI image model22:11 Salesforce goes "headless"24:08 Higgsfield, MCPs, and Meta ads29:51 Codex for GPT-Image-2 workflows32:45 Pulling style from video frames34:05 Building visual style reference sheets37:36 Codex and textured illustration systems39:34 The evolution beyond text prompts41:50 Seedance storyboards and visual prompts43:01 Reference images as reusable seeds44:51 AI video still has an audio problem46:13 Audio reference hacks in Dreamina50:52 Omni-reference for video control52:37 Midjourney V8.1 updated take53:28 The blue and pink problem returns55:37 Midjourney still owns realistic faces58:56 Reworking old prompts with Describe01:01:10 Luma Uni vs Midjourney color01:02:11 Midjourney 8.2, 8.3, and V901:03:46 Midjourney edit model questions01:07:13 Midjourney plus Seedance films01:09:03 Midjourney’s strange lane01:12:28 The Monet AI social experiment01:15:13 Why people over-detect AI01:20:09 AI backlash and disclosure debates01:22:50 AI as a career unlock01:24:30 Keep making weird stuff01:25:45 Wrap-up and seamstress CTA

Fast Hours has entered the witness protection program. Same Drew. Same Rory. But fewer syllables and more chaos.In this episode, Drew Brucker and Rory Flynn officially drop “Midjourney” from the podcast name and relaunch as Fast Hours, a broader home for the creative AI ecosystem: image models, video models, LLMs, vibe coding, Claude, ChatGPT, Midjourney, and whatever tool drops five minutes after they hit publish. Naturally, the rebrand lasts about four minutes before they’re elbows-deep in GPT-Image-2, OpenAI’s new ChatGPT image model that quietly showed up and immediately started making designers question their calendar, career choices, and relationship with kerning.The big topic: GPT-Image-2 is shockingly good with text, typography, brand systems, visual decks, product mockups, and multi-image outputs. Rory walks through how he used ChatGPT and Claude to create a custom typeface from visual references, generate a premium typography presentation, extract geometry, and turn the whole thing into usable font files. Drew then shows how he turned his own handwriting into a working typeface, because apparently “personal brand” now includes making your lowercase g file a tax asset.They also dig into the uncomfortable middle ground of AI creative work: when it saves time, when it still needs human judgment, why anti-AI panic and AI hype both miss the point, and why the real advantage is context. Not prompts. Not magic buttons. Context.The episode also covers GPT-Image-2 vs Nano Banana Pro, richer color rendering, micro-text improvements, AI-generated sports graphics, brand kit concepts, Freepik settings, Claude Design, 4K video generation, Kling, Veo 3.1, Seedance, and the strange reality that a custom brand typeface can now go from “that’ll be $150K” to “Rory did it before lunch.”Basically, it’s an episode about the exact moment creative production stops feeling like a tool demo and starts feeling li ke a factory someone accidentally left unlocked.---⏱️ Fast Hour00:00 Fast Hours is (re)born03:36 Going tool-agnostic04:34 GPT-Image-2 quietly drops05:31 Text becomes the unlock07:31 The AI backlash returns10:57 Hype, fear, and the middle12:10 Typography gets weird14:50 What custom fonts cost15:43 GPT-Image-2 vs Nano Banana17:39 Rory’s font experiment18:47 Fiddleheads become a typeface19:39 Building the type deck20:36 The nine-slide image unlock21:14 Geometry, spacing, and logic22:11 Turning images into font files23:02 Micro-text gets better24:19 Claude builds the font package26:41 The revision loop changes27:50 Context is the silver bullet32:11 Drew makes a handwriting font35:35 Why designers obsess over type37:52 Reverse-engineering prompts39:51 Richer color and sports graphics41:27 Fixing artifacts and details42:37 Nano Banana vs GPT-Image-2 tests44:26 Sports realism gets scary good45:27 Why teams need this now46:43 Freepik settings and ratios48:36 Testing, tokens, and limits49:44 Brand kits and rebrand concepts53:19 Google I/O and the next model53:48 Veo 3.1 falls behind55:04 Kling adds native 4K56:40 Character sheets and macros58:07 Rebrands as visual prototypes01:00:53 Building a reference library01:01:36 Three weeks in a row01:02:58 Claude Design tease01:03:37 Tell your local [fill in the blank] spam finale

Midjourney finally dropped v8.1, so Drew and Rory did what any responsible adults would do: generated way too many images, argued with style codes, stress-tested text, and immediately started asking whether the edit model is the part that actually matters.In episode 66 of Midjourney Fast Hours, the boys dig into why Midjourney v8.1 feels way better than v8, where it still falls short, and why this release feels less like a victory lap and more like Midjourney finally arriving at the version v8 probably should’ve been in the first place. They get into faster generations, native 2K output, mood boards, prompt depth, describe, personalization profiles, text rendering, image weight, --exp behavior, old v6 style-code weirdness, and the growing sense that the real make-or-break feature is still the edit model.They also get into how Midjourney stacks up against tools like Nano Banana, Grok, Reve, and Luma, why image generation still feels fragmented across platforms, and whether Midjourney should even bother chasing video or just go all-in on images, editing, and control.Then, because this is still Midjourney Fast Hours, the episode somehow ends with a deeply important discussion about custom Mac folder icons.If you care about Midjourney v8.1, prompting strategy, style references, AI image workflows, generative art tools, or where Midjourney is actually headed next, this one’s got the goods.---⏱️ Fast Hour00:00 Intro and v8.1 arrives01:05 Is v8.1 actually better than v8?04:09 The edit model is the real test06:22 Should Midjourney even chase video?10:07 v8.1 needs more prompt depth12:07 Mood boards feel usable again14:28 Testing the new describe tool21:00 Personalization profile matters most22:09 Text tests and object recognition23:57 “Photo” vs art and stylize tests29:54 Why v8.1 feels a bit like v630:43 Old style codes hit differently now42:08 --sv7 issue and style-code confusion45:47 Missing parameters and what still works47:26 Hidden text tests and image weight49:57 --exp tests and behavior shifts52:35 Grid view and the alpha site54:50 Office Hours, 8.2, and edit timing01:03:27 Custom Mac folder icon detour01:09:01 Wrap-up and parting nonsense

In episode 65, Drew Brucker and Rory Flynn return for another round of Midjourney Fast Hours and immediately do what they do best: poke at bleeding-edge AI tools until something breaks, gets weird, or accidentally becomes useful.They kick things off with fresh Midjourney V8 impressions, including what changed after another week of testing, why resetting personalization profiles helped, where the weird magic still shows up, and why V8 still feels like it is waiting for its real arrival. They also dig into the rumored Midjourney V8.1 update, what it could fix, and why the real test may come down to the edit model, text rendering, consistency, and whether Midjourney can pull serious users back into the platform.Then the episode takes a sharp turn into Claude, and honestly, this is where things get deliciously nerdy. Drew and Rory unpack how they are building with Claude in real life: when something should become a skill, how Claude MD files shape everything downstream, why auditing your own setups matters, how to think beyond rigid workflows, and what happens when your AI starts feeling less like a chatbot and more like a strange little operating system trained on your habits, instincts, and creative baggage.They also get into edge-case detection, memory files for collaborators and clients, private repos, Codex as backup muscle, analogy engines, and a growing obsession with building a “creative intelligence layer” that can carry more of his actual thought process into AI tools. ---⏱️ Fast Hour00:00 Intro and the boys are back01:12 Why the podcast got bigger than Midjourney03:25 Rory’s updated Midjourney V8 take04:40 Why new personalization profiles helped06:31 The weird Midjourney magic is back13:24 Midjourney 8.1 might be the real V816:36 Why the edit model really matters18:51 Claude skills: what should be a skill23:58 Why Claude MD files matter so much25:23 Building flexible AI systems, not rigid ones38:38 Rory’s edge-case detector skill41:55 Memory files for people and projects43:48 The creative analogy engine50:35 Why examples beat vague prompting53:38 Back up your Claude brain immediately55:30 Rory’s orchestrator and skill roster01:06:04 Hard-coded flows vs flexible AI judgment01:07:43 Building a creative intelligence layer01:18:01 William Shatner, Babe Ruth, and better analogies01:20:53 Outro and comment bait