There were many people that helped, but giving 90% of the splits to nostr:nprofile1qqszm7l9ew24usqckahx2s4rhpuzz3xatatnty2dhxfpl5jv8v73qmgpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0twzvpk on this one for helping me understand live podcasts.

If you want to hear what I went through it's up at the link below.

https://www.bitpunk.fm/@bitpunkfm_unwound/episodes/anarchist-guide-to-live-podcasting-part-i

Reply to this note

Please Login to reply.

Discussion

Ah nice one! Will defo check that in the morning, cheers!

StevenB is the sovereign feeds, curiocaster, and thesplitkit guy. He makes a lot of useful PC2.0 tools.

TheSplitKit might be useful to you for chapters and wallet switching when you're live podcasting

Ok, what does that do, because can you have a timeValueSplit in a liveItem? I don't think so right?

Or is this updating the valueRecipients at the item level?

The Split Kit signals the podcast players to do different things (e.g. chapters, value splits) while you're live podcasting. For instance, if you decide to play a song on the show, you can go into the splitkit, pull up the song, and it will tell the podcast players listening to switch to the wallet of that song.

It's only used for live podcasting and anything you do needs to be transferred over to the RSS feed once you publish the episode.

Ok that's cool. I'm curious how this works underneath though. If it's not updating the rss how does it tell the clients? Via the podping thing? I'll have to look into it.

And he's a damn fine lover too.

Oh yeah hi Steve :) talking with nostr:nprofile1qqsyymc3xj8lpcld5t2mjpheed7ewsc8t2u9aweuzh2hlwqtfcj7c0svcm07p about this. How exactly does split kit signals to the podcast clients to change the wallet etc... where is this spec?

It's not in the spec yet, still experimental, but here's the repo for TSK.

https://github.com/thebells1111/thesplitkit

And here's a repo that shows what's going on behind the scenes, but it's just sending the json data across a socket.io, and in the feed is a liveValue tag to let the apps know what socket.io connection to connect to.

https://github.com/thebells1111/live-updates

Ok. This is both awesome and overwhelming. :) I will look into. Basically I would want to run a minimal socket.io sever, send this json data. I know I'm describing what TSK is but I want to see how the raw level works without the gui, however helpful.

Also, can I only log into TSK without alby? I don't have that all setup yet.

Nah, you can log in with email also. It's preferred. And yes, the live updates repo gives you a bare bones client and server to see what's going on behind the scenes. TSK just makes it pretty-ish (I'm no designer) and makes it easy to query the index and build out the json from the found feeds. As you know, hand coding guids is a pain.

Actually, I just realized I don't have an email registration yet. I'll have to update it to make it so you can register your email without Alby.

One nice thing about TSK, is you can just build a list of your songs with start times, and it will build something like this for you to paste into your feed. Makes building those valueTimeSplits way easier.

Ok but just to be clear, valueTimeSplit is only good for an not live.

For live, you push the json and in the destination array goes the real time split.

That is correct. With TSK, people are doing their live shows, sending the the live value block over socket.io, and there's timers and such built in so when you publish the recorded show, you can turn your live blocks into value time splits pretty easily.

Others are using TSK for their recorded shows, building out the blocks and setting the startTimes based on the recorded audio, then having TSK spit out the VTS instead of hand rolling it.

Ok, amazing. Thanks for the clarification.

Ok amazing. I'll dig in thanks!

I learned a lot listening to this! Being new to the whole streaming so much goes over my head! Finally found how I get an HLS address from Owncast. Going to try in the morning, maybe this is the secret to get Zap.Stream working? Appreciate this is probably super basic info for most folks.

Fingers crossed for tomorrow morning!

Ps. Does anyone know if there’s any docs for Zap.Stream? Can’t see anything on the GitHub.

Oh amazing. Actually, I can probably check now too, let me see if I can bring in my stream endpoint

Yes I didntcrealise the hls part was an addition to the url, I was just putting the regular url in! I did search for hls in the Owncast docs a couple of days ago but nothing came up… most likely me being daft.

Just tried it and now my details actually saved so that might just be me set for the morning!

If I go via Zap.Stream does that still mean my initial output from OBS is still a problem? OBS doesn’t natively support HLS apparently so it’s still an rmtp link to the Owncast server.

Oh it's always the basic things. 😀

Aren't you going from pc to owncast to zap? I'd do it that way.

You had mentioned at one point 2 stream keys and two endpoints. I think that's very not typical.

Aw, thanks dude! I love talking Podcasting 2.0 / RSS and greatly appreciate it. 🥰