-
Notifications
You must be signed in to change notification settings - Fork 12
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
What is nature of time stamp for a .ts segment? #56
Comments
This question is answered as I investigate a related issue this morning: does the Examining the livestream from Sunset Bay via my browser, that the
Logging into the AWS console, I observe in Sunset Bay's S3 location that the current
This suggest that the first .ts segment may be created by ffmpeg 12 seconds after the latest.txt file is created on the Raspberry Pi, or that the datetime stamp of the .ts segment shown in the S3 console is actually the time the file was uploaded to S3 (12 seconds could be equal to the 10 seconds taken to create the first .ts file and 2 seconds to upload it to from the /tmp directory in the Rpi's container to the S3 bucket. Using Dataplicity to login remotely to the node, and this command to ssh into the running streaming container --
I get this precise time stamp for a .ts segment as it is being created and before it is uploaded and then removed from the
Searching for that segment back on the S3 console, I find this:
Which is again about ~12 seconds after the creation So, we can conclude that the |
Is the creation time for an HLS segment shown in the S3 streaming bucket the time the object was written to S3 or is it the time the segment was initiated by ffmpeg on the node computer?
The answer would be important for anyone trying to use the lossy data for localization (which is a worse choice than the FLAC), or for an accurate assessment of audio data gaps.
The text was updated successfully, but these errors were encountered: