luminarys/kawa

Radio streamer

kawa's Issues

Trust timestamps less

Really weird timestamps currently screw up kawa badly (way too slow/fast). We should probably switch to approximation via samples/sample rate, maybe only if we detect something really weird though.

ICY Metadata

Since the current metadata situation sucks, try adding in ICY metadata.

Track changes on Opus cause stream interruption on Chrome

While playing back OGG/Opus streams, a new track will bring the playback to a stop.
To workaround this problem, I have a JS listener on error that tries to restart the stream.

These are the errors that get printed to the console if you log them:

PIPELINE_ERROR_DECODE: Failed to send audio packet for decoding: timestamp=93126542 duration=960000 size=19 side_data_size=0 is_key_frame=1 encrypted=0 discard_padding (ms)=(0, 0)
PIPELINE_ERROR_DECODE: Failed to send audio packet for decoding: timestamp=93126542 duration=960000 size=19 side_data_size=0 is_key_frame=1 encrypted=0 discard_padding (ms)=(0, 0)
PIPELINE_ERROR_DECODE: Failed to send audio packet for decoding: timestamp=1028188 duration=960000 size=19 side_data_size=0 is_key_frame=1 encrypted=0 discard_padding (ms)=(0, 0)

Using latest kawa, tested in multiple radios

User agent modes

Even though mpv and other players more or less work fine, ffmpeg complains about the chained file approach we have to take due to mpd. We should alter operational modes based on the user agents to ensure all clients have a better experience.