New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stuck in "opening stream" window #569
Comments
Try with one provider at the time and reduce the number of results in each provider from. 10 to 5 |
Also getting this, but only with episodes... Using the "magnetizer" gets around the issue, so I'm looking into Quasar's resolver for trackers, which is around where it seems to get stuck, but I have the impression that Magnetic is doing something funky with the results it's sending back to Quasar... |
@scakemyer, you are right. Some providers need to do two or more request to get the torrent or magnet information. Initially, those providers were too slow more than 8s. Then, they were not practical. As solution, I've create a service inside the Magnetic to read the information and provide a torrent which reduces the response time below 3s. The problem is that Magnetic cannot give a magnet in the second call. It needs to be torrent file. However, some places uses itorrent.org as torrent storage or there is not more information than the hash (Magnetic creates the torrent from that site too). For some reason, sometimes, itorrent.org doesn't provide the torrent, but a webpage. It could be publicity or a type of blocking. I used to use torcache, but it is gone for good. The difference with Magnetizer is that Magnetic can send magnet information. Then, the problem with the itorrent.org is not present. Conclusion, not to use the providers which have the open subpage enable with Quasar. |
Didn't know the "magnetizer" workarround! Thanks anyway! |
Fixed for 0.9.37 so we won't depend on Magnetic or trackers playing nice :) |
Quasar always get stuck in "opening stream" window when trying to play something. After almost 5 minutes it fails and here it is the log:
The text was updated successfully, but these errors were encountered: