-
Notifications
You must be signed in to change notification settings - Fork 100
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
Audio file is cropped from the beginning #435
Comments
This is a bit tricky due to the subscription lifecycle. the current logic in
There isn't really a way to know when all of the the subscribers have subscribed to the track.. but I think you can modify this function to do the following:
|
Thank you, @davidzhao ! I've tested the idea and it looks like it's the way to go |
Is there a ready-to-use method to publish an audio file without missing the beginning parts? It's quite strange that this is an issue in such a large streaming ecosystem. Specifically, my case is 1-to-1 prerecorded audio file streaming |
@davidzhao Is there a way to determine when a participant has subscribed to a track when there are only two participants in the room? I tried using an additional confirmation with the OnDataPacket callback to receive an acknowledgment (sent from other side after room connection), but it still doesn’t provide a 100% guarantee that the track won’t be trimmed |
I created a very simple server that sends ogg OPUS audio files to web clients.
Basically, I did everything as described here https://github.com/livekit/server-sdk-go?tab=readme-ov-file#publishing-tracks-to-room
adapting only to audio files.
In about 90% of the cases, the first second or even several seconds are missed and I don't hear them on the client side.
It should be possible to somehow make sure that all clients subscribed to the track before publishing it.
The text was updated successfully, but these errors were encountered: