Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
4.5.2 breaks some radio streams
#1
4.5.2 breaks some radio streams.
For example it breaks all my BBC streams such as:

http://a.files.bbci.co.uk/media/live/man..._live.m3u8

http://a.files.bbci.co.uk/media/live/man...three.m3u8

If I try these I get UAPP showing wrong sample rate (shows 44.1, should be 48), buffers briefly and then fails with message "No active stream"

Same bug on KitKat, MM, Nougat and Oreo on different architectures.

Reverting to previous version of UAPP solves issue.
Reply
#2
I tried 4.5.3 and it's the same. I have to go back to 4.4.1 or BBC streams don't work.
Reply
#3
Tried with 4.4.1, also gives error 403:

AV: Could not open file http://as-hls-uk-live.akamaized.net/pool...ewind.m3u8, res = Server returned 403 Forbidden (access denied), streamprovider = 0x0
Reply
#4
(11-19-2018, 05:30 PM)dwrae Wrote: Tried with 4.4.1, also gives error 403:

AV: Could not open file http://as-hls-uk-live.akamaized.net/pool...ewind.m3u8, res = Server returned 403 Forbidden (access denied), streamprovider = 0x0

You get that due to being outside the UK.  If you try via a UK proxy the stream should usually be available.  The BBC filters out clients by geolocation and also blacklists some VPNs.

The stream url is good.  I checked it and used it this minute.  If you would prefer a log from in the app I could provide you with one log from 4.4.1 and another log after upgrading to the latest version from the play store.
Reply
#5
Yes, please enable 'Logging to file' in the app, then send the file UAPP.txt file from the UAPP folder after playing from 4.4.1 and a new log file after playing from 4.5.x.
Reply
#6
(11-21-2018, 11:29 AM)dwrae Wrote: Yes, please enable 'Logging to file' in the app, then send the file UAPP.txt file from the UAPP folder after playing from 4.4.1 and a new log file after playing from 4.5.x.

Thank you. I just sent the logs to info at audio-evolution.com with subject 'Re bug report forum "4.5.2 breaks some radio streams"'
Reply
#7
The same bug persists in today's new version 5.0.1
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)