You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And it stops there. Maybe there's a genuine error, which would be fine, but it doesn't get back to the caller. Or maybe it's the lack of feedback mentioned in issue #2.
The text was updated successfully, but these errors were encountered:
Just tested the same torrent, is working here. The 'tracker_error_alert' is not a critical error, but an informative one, in case the tracker fails too many times, such tracker is dropped. See the libtorrent documentation.
You need to be patient with the torrent :). Even if the buffering says it is 0%, there's no way to increase the buffering level by bytes received from trackers, I had to do it by completed pieces received, the current number of pieces to get a 100% is 3, so you'll see the buffering increasing by 33% each time, but nothing in the middle. Of course depending on the bandwidth you might end having to wait a lot before the three pieces are completed.
For testing purposes, I downloaded http://yts.to/torrent/download/726E8B9C912596AD21278BBEF45C3C460900F35D.torrent
And tried with both the command-line mentioned in the README, and through gst-play-1.0 to start the playback, and I got:
And it stops there. Maybe there's a genuine error, which would be fine, but it doesn't get back to the caller. Or maybe it's the lack of feedback mentioned in issue #2.
The text was updated successfully, but these errors were encountered: