Ваши комментарии
:( The current release v3.0.0.05 is what he is talking about... Unfortunately your issue seems to be with a bad Android media framework on the custom ROM. Have you gotten any response from the ROM devs?
Awesome feedback! Thanks! Ok, something important first; When using FFMpeg stream engine you will currently not get the gray bar showing how much buffer is available. However we will add that feature to FFMpeg soon! If you haven't selected that stream engine you should be able to see the gray bar. However we automatically use FFMpeg if the stream format is other than AAC, AAC+ or MPEG.
Ok, so about the server settings you are using. Great info by the way. Smart recovery is beta but going strong to be none beta soon! Anyways! The current look back time for trying to recover is about 30 sec and if it fails to recover it just appends it to the end of the buffer. I might have to look over this logic a bit... Could you send me the URL to your server with the large burst size? You can email me privately if you like the link. jona@visualblasters.com.
By the way what you think of the smart recovery?
Just to be clear. You are streaming music and you receive a call and answer it. After the call is ended the streaming volume doesn't return?
Could you verify the player is still streaming?
Does it matter how long you are on a phone call, does the issue still occur?
Are you using a custom ROM?
What Android version is your device running? Could you download XiiaLive Beta from the Google Play Market and see if the issue still occures?
Hey sorry for not sending you the newer apk as I told you before on another post... :( It's awesome things are working better! Yes, there was a "little nasty" bug on the AAC side of things, but I'm excited that that was it and fixed your issue! The new cache is super fast and efficient compared to previous versions of Xiia. I really hope it improves CPU usage a bit.
Сервис поддержки клиентов работает на платформе UserEcho
Thanks for the email. I did test your link and was able to see the issue. I have increased the low value of 30 sec to 2 min and things are now good... Next update it will have the fix. Thanks for the feedback again!