Weird filenames will be automatically renamed.Weird download names will automatically be renamed.You can now rename downloads: will be shared to other users.We think we have found a solution: we will make the NZBVortex clients work together and help each other! Some examples of what NZBVortex Cloud will offer: Nieuw in versie 3.0 is onder meer NZBVortex Cloud en ondersteuning voor OS X 10.10 Yosemite NZBVortex CloudĪs we all know usenet gets a little harder now as downloads have weird names, are passworded and downloads are taken offline regularly. Een licentie kost 16 euro en tijdelijk is dat de helft. NZBVortex wordt uitgebracht als shareware. Het heeft alles wat je van een moderne usenet-client mag verwachten, waaronder ondersteuning voor verschillende servers, verbindingen en threads, notificaties via Growl, de mogelijkheid om gebruik te maken van rss-feeds en een nzb-watch folder, verificatie en reparatie van par-bestanden, en ga zo maar door. Dit programma is een van de meest gebruikte usenet-clients voor OS X. Unfortunately SABnzbd failed again!ĭon't know if there's something weird going on with my Docker container, but I think that should be fine.Versie 3.0.1 van NZBVortex is uitgekomen. Same NZB I've sent you per mail and same Usenet providers I mentioned before. However, I tried it again a few minutes ago. So I think this wasn't a "temporary issue" of the Usenet provider. I tried NZBVortex right in advance and directly after SABnzbd failed and it worked flawlessly both times. However, NZBVortex succeeded while SABnzbd failed. It was the same NZB and it was the same Usenet provider (same host, port, credentials) and both clients (NZBVortex and SABnzbd) had to repair the downloaded files. What's weird is that I've used the exactly same NZB and Usenet providers with NZBVortex where it worked, while SABnzbd had issues :/ Sometimes par2 files are malformed in such a way that SABnzbd is thrown off-track.Ĭan you also email which Usenet provider(s) you're using? It could be that different parts are missing on different servers. There were malformed articles and repair was needed. Shypike wrote:I downloaded your NZB with both 0.7.20 and 0.8.0Beta3.īoth succeeded, resulting in an oddly named MKV file. Is it possible to switch back from develop to master? SABnzbd runs on a Debian machine in a Docker container with Python 2.7.9.Īny things I can try to fix this or narrow down the issue? I'm currently running on the develop git tree on commit 583c233bd282cfef3480948c69eef0055e1828bd. However, NZB Vortex always succeeded without any problems.Īs I already wrote, it's always the same NZB file and the same Usenet server in SABnzbd and NZB Vortex. Unfortunately SABnzbd wasn't able to download & repair my files in all cases. I've tried the download via NZB Vortex in advance and after SABnzbd.I've disabled Enable Quick Check and enabled Download all par2 files.I've 3 Usenet providers (Astraweb, UsenetServer, ExtremeUsenet) and I manually switched through all providers (e.g. So to make sure it's SABnzbd and not a "ghost", I tried the following things: I already searched these forums a lot and I found some users with the same issues. The file wasn't complete and even NZBVortex had to repair it, but it worked! Today I manually fetched an NZB which failed on SABnzbd and fed it NZBVortex 3 on my Mac. Unfortunately I've a lot of "Repair failed, not enough repair blocks" lately. First of all, awesome job with SABnzbd guys This thing is pretty awesome and my trusted Usenet client for many years
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |