We're Officially a Podcast!!

It took me 3 days of pretty heavy Opus 5.5 usage. Didn't hit my limit. Insane. Command AI We are officially a podcast now. We are officially yes. a podcast. So, if you like to listen and and we can get into the tech side actually for it because it's not newsworthy, but it's interesting nonetheless cuz I think people want to know how we do things. How do we use AI? Anyway, people were asking for the podcast and so I've been really getting into having Claude edit my videos, my personal YouTube videos. And but also actually it started out taking the stream and then editing the clips from the stream. And what Claude does and you've just got to ask Claude to do this. It's not It's nothing clever about Well, there is, but like you just You you download your files, you point Claude at that folder, and you say "Edit this thing." And you give it a load of direction. So, I tell Claude to edit this video and here are the topics that we covered this week. And it does an amazing job at really understanding things. Because before I would just We do a little intro. You You'll notice it now again if you're new here. We do a little intro and then we talk about the news. What I tend to do when I was editing, which took loads of time by the way, I would just use that intro as the intro, but sometimes sometimes a bit of gold comes out at the end or in the middle something like that. And and Claude knows to use that as the intro because that's more interesting than the original intro that we we wrote in the first place. So, all that to be said, we've got our clips. We've transcribed the stream, the entire 2-hour stream. We've got that in transcriptions because that runs on my local machine. Whisper transcribes it. So, we've got all these in points and out points and all the rest of it. So, we have all of that really useful data. So, now we've moved on to creating shorts, like vertical format shorts, from that as well. So, we create the clips and then we create the shorts cuz all that data is in there as well. We can tell it to put intros in. I I I formatted it and all the rest of it. And then from that, because we have everything, it was like, "Well, why don't we now just put it up as a podcast?" And with slight direction, because if again, you'll know if you hear hear a lot, we do a lot of screen shares. We do a lot of like things and sometimes we sit back and we watch something. And on a podcast, that ain't that interesting. So, in my prompt for the podcast or later skill, um I say that be aware of a lots of watching. If we're watching something or whatever, get to the good bit. Get to the conversation. Like a example would be our um Roads to Coverage last week. On the podcast, you don't really hear that. We just talk about the talk about what's going on. Cleans it all up and now and then it automatically uploads it to our feed, which is we're self-hosting the feed, the XML, the RSS feed, which which um uh powers all of the podcasting platforms. You have an XML feed. And all of the Apple uh Spotify can do it, but we don't do that. Um what else? Amazon. They all read from this XML file that we publish on our own URL. So, all we do, we put push it up to our website. We host it on our website. All of it's done on our website and then all of the all of the podcasting platforms point to that. And then when they see a new episode, they link to it and then show up on your Apple Podcasts app. Fires is a bit different because they want you to they want you to upload it directly to them. You can do it through there, but it removes the ability to monetize on Spotify if if you read from an external RSS feed. So, it's like, "Well, we don't really want to do that." So, we'll upload it directly to Spotify. And remember, this this is all through prompts. I'm I'm just asking Claude. I pointed it at the video files and I'm asking Claude to just do what I want it to do with with a little bit of direction. A couple of weeks ago it was just the edit. Last week it was the edit plus the shorts. This week it'll be the edit plus the shorts plus the podcast. And it's this iterative thing where you you ask Claude to do it, you watch it back, and then you tweak it because it's like, "Oh, it forgot this." Or, "Make sure you do that." Or whatever. And then when I'm happy with it, that goes into a skill. I say, "Let's make a skill out of what we've just talked about here." And now we have this master skill that just churns through, point it at an episode, churns through everything, does it bit by bit, and at the end of it we've got podcast up on our website. And and this is the beauty of the iterative thing is that you you come up with a new idea, you mentioned about having a little outro in our in our shorts. Uh you just add it to the skill. Add it to the skill and it will do it next time. And you So, it it It's only three skills that we have. I think the Command AI design skill, the caption skill, cuz that needs to be that I want that to be separate. Technically, we could work it into the design skill, but whatever. We have a caption skill. And then we have a um edit skill. The master edit skill, which is is pretty large, but it just takes a it takes a raw set of clips, creates uh sorry, raw set of video files, creates clips from them, creates shorts from them, creates podcasts from them, upload them, and then now we can add that layer of of API [snorts] access to just automatically upload them. So, what what's an amazing workflow is certainly for my personal channel videos is I get Claude to edit it, and then sometimes I want to tweak it. I want to like tweak this, move this, clip that cuz sometimes it doesn't cuz it's just reading raw words. It's not listening. So, I ask it to create a Final Cut XML file. So, then I open that up, and I make the little edits here or there. I want to be able to edit it, and then I want it to take my edit, and then work on that, you know? So, I I know how to do this. So, I literally asked Claude, "I want to do this. All right, what happens? What's the best format for me to give you an edit that I've done in Final Cut?" Maybe it's the first edit. And it said, "You don't need to do anything. Don't render anything. Export the XML and give that back to me, and I will make those edits, and then we'll just we can just pass back and forth. Even I don't know how to do some of these things, and it's just through of talking, that's where you get to it." When you mentioned the XML, at the end of the day, it is a file, right? And I think this is the mind shift switch that people need to do. People don't know that it's all through files. But what changes everything is knowing that AI can create any file or pretty much read any file. A lot of these files, I don't know yet now specifically for one specific file, but this is what I did this week as well. I started creating file types without having the programs for them. This is Like as you didn't have Photoshop, but you created a Photoshop file as an example. Exactly. And all you have to understand is just point Claude to a folder. Don't use Claude Chat. If you use ChatGPT, it does like the same thing. Don't use the chat interface. Let them have access to a folder, and then give them a task to do it on that folder. The only other thing that I think is important to know is it's helpful to know what is possible. Yeah. To to you know, to But that comes back to asking the question, "Can we do this? What is the best way to do this?" And then reading its output. We we've been going on about reading its output for a little while now. Yeah. Reading its output about what it should do. So, I bet people didn't realize People think that, "Oh, what Claude opens up Final Cut and then edits it in Final Cut and then this and that and the other." Claude knows that if it can you know, if you know that it's just got to transcribe, and you can do transcriptions with local AI. That's already an unlock there from your perspective on what you can do. So, you unfortunately you don't know what you don't know, but it's through your curiosity and your inquisitiveness that you unlock what is possible, which then in turn makes you think, "Oh, it's just a file. It's just a file at the end of the day, so I'll just point Claude at that file." The price I spent to get all 70 episodes edited, podcast edit edited, which is mostly the same process. It took me 3 days of cons Well, not constant, but 3 days of pretty heavy Opus 5.5 usage. Didn't hit my limit. Insane. The one thing that took the most amount of time, which is what I said to you earlier in in in our chat, Bazza, the Claude transcribes our episodes using local AI. That's what took a lot of time. So, all Claude's got to do is just tell Whisper to transcribe this file. When it's done, it just reads that file. So, not really a lot of, you know, input and and token usage there, cuz it's waiting. It's just waiting a lot of the time. Yeah. Created a whole series of clips. I created a whole series of shorts from last week's episode, and I created all the podcasts all before my weekly reset after a week of working. So, very, very token efficient is Claude. This is part of a larger conversation on my show, Command AI, which we stream live every single week. We discuss the news and all things related to AI in the world of design and web. Catch us next week and join in the banter. Command AI.