DASH : Rate based adaptation logic
Posted: 21 Aug 2015 12:37
Hi,
I am developing a dash player based on libdash. For this I was trying to understand different adaptation logic mechanisms. Then came across VLC dash component. Here rate based adaptation logic is used. I got the idea of reading the content from http::stream and then updating the download rate. After that when getRepresentation() method is called, it will use the current bps and the w, h values to get the proper representation stream. But, I didn't understand the average calculation mechanism. The cumulative time is compared to a reference value of 4*CLOCK_FREQ/stabilizer. I couldn't understand the logic behind this reference. Also, currentbps is 3/4 of the bpsaverage. Am I missing something here ? These are all hard coded numbers. Is it based on some research, we came to these values ?
Regards
HK
I am developing a dash player based on libdash. For this I was trying to understand different adaptation logic mechanisms. Then came across VLC dash component. Here rate based adaptation logic is used. I got the idea of reading the content from http::stream and then updating the download rate. After that when getRepresentation() method is called, it will use the current bps and the w, h values to get the proper representation stream. But, I didn't understand the average calculation mechanism. The cumulative time is compared to a reference value of 4*CLOCK_FREQ/stabilizer. I couldn't understand the logic behind this reference. Also, currentbps is 3/4 of the bpsaverage. Am I missing something here ? These are all hard coded numbers. Is it based on some research, we came to these values ?
Regards
HK