Recent Posts

Pages: [1] 2 3 4 ... 10
1
Help / Re: Downloaded files are not named as expected
« Last post by Rdl on Today at 12:05:54 pm »
2
German (Deutsch) / Re: Hinweis an Nutzer von T-Online!
« Last post by Rdl on December 14, 2024, 08:49:17 pm »
Should be resolved.
3
Bugs / Re: NZB#2 import as paused setting does not work with new par2 volumes
« Last post by Rdl on December 12, 2024, 07:33:33 am »
Don't be fooled. This has nothing to do with the par2 program. All those mentioned programs are outputing valid par2 files with valid naming sheme. It's nzbgeek that's renaming them.

I will see how other programs handle those nzbs and act based on that.
4
Bugs / Re: NZB#2 import as paused setting does not work with new par2 volumes
« Last post by DreamJoker on December 12, 2024, 04:39:19 am »
Almost every new nzb on indexer you're using. I'm using few better ones and never had encounter with such posts.

yes like you said, I am using nzbgeek
5
Bugs / Re: NZB#2 import as paused setting does not work with new par2 volumes
« Last post by sidbib on December 12, 2024, 12:36:35 am »
I apologize but I mis-spoke earlier.

The change I noticed a while back was a modification of the "volume" naming convention for the par2 files containing repair blocks... part of which was a change from a plus "+" sign to a minus "-" sign. But those sets still contain a "small" par2 file with no volume info. And those par sets do still pause the recovery files properly in Alt.Binz. According to the MultiPar GUI, this format that I have been seeing for a while now is generated by the program ParPar (https://github.com/animetosho/ParPar).

This other par naming format (that doesn't pause the recovery files) also uses the minus "-" symbol instead of plus "+" but all files have "vol" in the name (even the small par2). At first I thought this was something new, but now I think it is something old. So far I have only seen this on nzbs I have grabbed from nzbgeek (but I will keep checking around). The oldest example I found was something I downloaded from nzbgeek in 2022, but the actual usenet post was uploaded in 2011!!! According to MultiPar, those 2011 par files were created by the program par2cmdline v 0.4 (https://github.com/Parchive/par2cmdline). The similar ones I grabbed from nzbgeek yesterday (for a new release less than 2 days old and shown in the previous screenshots) were created with par2cmdline v 0.8.1. That seems to be the newest version of par2cmdline from 2020.
6
Bugs / Re: NZB#2 import as paused setting does not work with new par2 volumes
« Last post by Rdl on December 11, 2024, 08:37:04 pm »
So, it's nzbgeek. Any more indexers?

Personally, I do not understand new format. Small par2 file that doesn't contain any recovery blocks is now named vol-1.par2? Also, there is no info on number of recovery blocks for the rest of the par2 files.
What should program do? Guess number of records? Calculate it based on filesize? Download it one by one until there is enough recovery blocks(or maybe there isn't)?

This naming doesn't make sense, whoever came up with this has questionable logic...
7
Bugs / Re: NZB#2 import as paused setting does not work with new par2 volumes
« Last post by sidbib on December 11, 2024, 08:00:43 pm »
I have seen the new /different par2 naming around for a while now, but had not noticed this pause issue myself because I no longer pause the par2 files. But today I turned the pause feature back on and tested a couple of nzbs from nzbgeek (that match the par2 naming convention listed above) and they did not pause. Screenshot attached.

I am not complaining (since I don't use the pause feature on parfiles), this post just made me curious. I could try nzbs from a few other sites as well if needed
8
Bugs / Re: NZB#2 import as paused setting does not work with new par2 volumes
« Last post by Rdl on December 11, 2024, 07:44:41 pm »
Almost every new nzb on indexer you're using. I'm using few better ones and never had encounter with such posts.
9
Bugs / Re: NZB#2 import as paused setting does not work with new par2 volumes
« Last post by DreamJoker on December 11, 2024, 07:39:55 pm »
almost every new nzb file, the par2 files are named as such
10
Bugs / Re: NZB#2 import as paused setting does not work with new par2 volumes
« Last post by Rdl on December 11, 2024, 05:54:42 pm »
Can you point me to where this new naming scheme was discussed/introduced?
Pages: [1] 2 3 4 ... 10