Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

streamer: has a decode-length + encode-length startup time, even from a warm startup #159

Open
Wessie opened this issue Jan 2, 2025 · 0 comments
Labels
low-priority issue is not important and likely won't get resolved soon streamer issue is related to the streamer

Comments

@Wessie
Copy link
Contributor

Wessie commented Jan 2, 2025

We throw away any data when a human streamer takes over and start all over once we're asked to start again, this generally takes about 10-15 seconds before a song is ready to start playing.

This can probably be fixed by re-using the existing logic that is there for the graceful restart

The warm-startup is the more important issue, doing a song decode/encode sequence when we do a cold startup is probably not worth the complexity

@Wessie Wessie added low-priority issue is not important and likely won't get resolved soon streamer issue is related to the streamer labels Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-priority issue is not important and likely won't get resolved soon streamer issue is related to the streamer
Projects
None yet
Development

No branches or pull requests

1 participant