2016-06-29, 19:45
Are you running 15.2 on the PI as well?
EDIT: Just tested windows on 16.0, works fine. Maybe 15.2?
EDIT: Just tested windows on 16.0, works fine. Maybe 15.2?
(2016-06-29, 19:44)learningit Wrote:(2016-06-29, 19:40)hewligun Wrote: No COX. As I said I have a setup in another room and it works just fine. The other setup is on a rpi2. This is a windows box.No idea then. You need to create a detailed debug log by enabling debug logging and specific logging for cURLib and ffmpeg. It's something to do with https, I think, which shouldn't be a problem on Windows.
(2016-06-29, 19:55)hewligun Wrote:(2016-06-29, 19:44)learningit Wrote:(2016-06-29, 19:40)hewligun Wrote: No COX. As I said I have a setup in another room and it works just fine. The other setup is on a rpi2. This is a windows box.No idea then. You need to create a detailed debug log by enabling debug logging and specific logging for cURLib and ffmpeg. It's something to do with https, I think, which shouldn't be a problem on Windows.
Here you go. http://pastebin.com/3W5GpJKG
10:52:36 T:6216 ERROR: ffmpeg[1848]: [tls] An unexpected TLS handshake packet was received.
(2016-06-29, 20:06)learningit Wrote:Thank you I will try that. HTTPS is ok. I was able to look at the log and find the actual filename and it plays fine direct in VLC. So that lets me rest a little easy. Will Upgrade to 16.1. Hope that fixes it. Thanks.(2016-06-29, 19:55)hewligun Wrote:(2016-06-29, 19:44)learningit Wrote: No idea then. You need to create a detailed debug log by enabling debug logging and specific logging for cURLib and ffmpeg. It's something to do with https, I think, which shouldn't be a problem on Windows.
Here you go. http://pastebin.com/3W5GpJKG
Your problem is on line 799;
Code:10:52:36 T:6216 ERROR: ffmpeg[1848]: [tls] An unexpected TLS handshake packet was received.
I'm not sure why, but https is an issue with your ffmpeg build. AFAIK all windows builds above 15.1 are ok for ffmpeg with https and you're not using a VPN, so I'm at a loss for answers.
My current best answer is to upgrade to 16.0 or 16.1.
(2016-06-29, 20:09)hewligun Wrote: Thank you I will try that. HTTPS is ok. I was able to look at the log and find the actual filename and it plays fine direct in VLC. So that lets me rest a little easy. Will Upgrade to 16.1. Hope that fixes it. Thanks.
(2016-06-29, 20:11)learningit Wrote:(2016-06-29, 20:09)hewligun Wrote: Thank you I will try that. HTTPS is ok. I was able to look at the log and find the actual filename and it plays fine direct in VLC. So that lets me rest a little easy. Will Upgrade to 16.1. Hope that fixes it. Thanks.
Probably a weird build of ffmpeg without/incomplete https support. 16.0 or above will definitely have that.
(2016-07-26, 06:42)jessicawise Wrote: I have updated my app, and it works, but it's still stopping to buffer every 10 seconds (literally). I've checked all my plugs and everything is working well, including my Internet. When I looked on the Add-On settings, it say "This add-on could not be configured." Should I just give the app more time to adjust to the update? Did I update it wrong?There's no such thing as "adjust to the update". The Bravo streams are fairly high speed and require a reliable 6-7 Mbps internet link. If you don't think that's your problem you need to post a debug log to xbmclogs.com.