Is there a place where I should submit a bug report or is this fine?

hey, is it already possible to create a DNS CNAME to get a custom subdomain that points to the customer unique subdomain?

Surfacing here is great. This is really useful bug report - it is super helpful to learn about the HLS.JS version upgrade change and how it caused regression - knowing what changed on their end will help us address. We're investigating

Exactly what I've been getting for multiple stream recordings! Been using 1.2.1 for the time being for this exact reason.

@himoc @B4154 would yall mind letting me know if you still see an invalid initial audio DTS for newly created live streams? There should be a fix in place that will address this going forward (not yet for already created inputs)

Oh this tied to the Live Input itself? I'll create a new one and test that.

Yep, that seems to work

Although, I did notice a skip in the audio of the first fragment.

As it transitioned to the second one.

Lemme see if it does it on another stream.

Yeah it consistently occurs

At roughly 7-8 seconds in.

Hmm ok, I'll call this two-steps-forward-one-step-back then.

The skip is between the two audio segments (specifically, between the first and second one)?

yeah

gotcha, will dig in!

And the timestamps do line up to where I hear the skip

Out of curiosity, what are you using to send your input stream? (OBS, FFmpeg...)

OBS

huh

ok, still investigating on our end, but improvements are underway!

There's gaps in these timestamps. From what I've seen on other hls examples, this should not be the case.

This is what it should be. The ending DTS of the previous fragment should be the starting of the next one.

can i use stream for storing and playing audio instead of vidoes?

I made an open source live streaming client on the web using WHIP protocol: https://live.longern.com/#studio

WHEP hasn’t been working for me for playback. Does it only work if the streamer is streaming with WHIP?

I believe currently thats the case

Correct. For now WHIP/WHEP must be used together: https://developers.cloudflare.com/stream/webrtc-beta/#limitations-while-in-beta

We have works in the pipeline that will unify all the protocols, but that's at least 2Qs away

Ah ok. Thanks