Jerod

And so the way that the chaptering works and really the way that all metadata works is every time you save that episode in our admin, it's taking the result of the episode information that's in our database. It's rewriting a brand new MP3 that has that exact same match data. So it's always the same.

And so the way that the chaptering works and really the way that all metadata works is every time you save that episode in our admin, it's taking the result of the episode information that's in our database. It's rewriting a brand new MP3 that has that exact same match data. So it's always the same.

The MP3 does not contain the chapter information until our admin contains the chapter information for that same reason. The chapters need to be outside of the MP3 because they also have to be in the RSS feed. We also use them on the website. We use them in multiple places. And so the data has to be outside of that MP3. And so the way that we get that is out of the WAV file.

The MP3 does not contain the chapter information until our admin contains the chapter information for that same reason. The chapters need to be outside of the MP3 because they also have to be in the RSS feed. We also use them on the website. We use them in multiple places. And so the data has to be outside of that MP3. And so the way that we get that is out of the WAV file.

So the MP3 gets uploaded into our admin. The WAV file is huge in comparison. MP3s range from 50 megs. Well, changelog news is like 7 megabytes. Anywhere from 10 megabytes to 100 megabytes, sometimes bigger for Adam's epic interviews. But the WAV files, that's raw audio, uncompressed. And so we're talking gigabytes, right? So we don't actually want to upload the WAV file to our admin.

So the MP3 gets uploaded into our admin. The WAV file is huge in comparison. MP3s range from 50 megs. Well, changelog news is like 7 megabytes. Anywhere from 10 megabytes to 100 megabytes, sometimes bigger for Adam's epic interviews. But the WAV files, that's raw audio, uncompressed. And so we're talking gigabytes, right? So we don't actually want to upload the WAV file to our admin.

We just want the information out of it. And so every episode post audition has four artifacts, two WAV files, two MP3 files, one for regular changelog people. And then the it's better folks get their own file. It's better. That's right. For plus plus. When you drag the WAV file into our admin, it's just dropping it into the local browser session. It's not uploading it to the server.

We just want the information out of it. And so every episode post audition has four artifacts, two WAV files, two MP3 files, one for regular changelog people. And then the it's better folks get their own file. It's better. That's right. For plus plus. When you drag the WAV file into our admin, it's just dropping it into the local browser session. It's not uploading it to the server.

And the browser via our good friend JavaScript uses, I can't remember what library we're using, wave.js or something. Something somebody else wrote to basically introspect the WAV file. which can get at the markers, pull them out, match the timestamps, and basically create for us a bunch of chapter objects in the form. And that's how that works. So the WAV file is then discarded.

And the browser via our good friend JavaScript uses, I can't remember what library we're using, wave.js or something. Something somebody else wrote to basically introspect the WAV file. which can get at the markers, pull them out, match the timestamps, and basically create for us a bunch of chapter objects in the form. And that's how that works. So the WAV file is then discarded.

When you hit save, the WAV file is not going anywhere. It just disappears. MP3 gets uploaded along with the chapter information.

When you hit save, the WAV file is not going anywhere. It just disappears. MP3 gets uploaded along with the chapter information.

Yeah, the chapter information can live in the admin episode before the MP3 does. Yep. Right? Because it's its own data set, basically, which informs the RSS feed. That's right.

Yeah, the chapter information can live in the admin episode before the MP3 does. Yep. Right? Because it's its own data set, basically, which informs the RSS feed. That's right.

And you can go back and edit it later, and it will reflect into the MP3 and into the RSS feeds. And so that's why I want that to be the source of truth versus the WAV file. The WAV file is kind of like a starter for your chapters, basically.

And you can go back and edit it later, and it will reflect into the MP3 and into the RSS feeds. And so that's why I want that to be the source of truth versus the WAV file. The WAV file is kind of like a starter for your chapters, basically.

Right, it's the... Starter's a good word, I suppose. I was trying to go with a different word. The kindling. The initial vehicle to get it there, I don't know. The transport layer. Yeah, just like the baseline data set. It's actually the conduit between Audition and Web.

Right, it's the... Starter's a good word, I suppose. I was trying to go with a different word. The kindling. The initial vehicle to get it there, I don't know. The transport layer. Yeah, just like the baseline data set. It's actually the conduit between Audition and Web.

You could completely ignore it. You could author all your chapters by hand in our admin by hitting add chapter, start time, end time. You could do that if you were a fool.

You could completely ignore it. You could author all your chapters by hand in our admin by hitting add chapter, start time, end time. You could do that if you were a fool.