9

For those out there using VPN's to torrent, do you prioritize a lower latency over higher bandwidth or higher bandwidth over lower latency when selecting your server/region?

Bandwidth is pretty self explanatory but I'm not sure how latency impacts torrenting (mainly for seeding). If anyone can shed some light on this, I'd really appreciate the input!

[-] blixo@lemmy.fmhy.ml 1 points 1 year ago

Aah, dang - thanks for trying!

[-] blixo@lemmy.fmhy.ml 1 points 1 year ago

Hi - just curious if you were able to look at the release notes for these releases (the NTb and FLUX ones) and whether or not you found out anything. If not, no worries, but I thought I'd check in.

Also, I'm particularly interested because I noticed that the FLUX version has a season REPACK out there where the REPACK size is similar to the NTb file size, which makes me all the more curious about the original FLUX versions with the increased file size / bitrate (and whether that means better quality or not in this instance).

[-] blixo@lemmy.fmhy.ml 1 points 1 year ago* (last edited 1 year ago)

Aah, makes sense. Thanks for the example! That really helps to put it into perspective. So REPACK on a P2P file doesn't necessarily mean somethings wrong with the original version, but the REPACK's will generally be improved in some way. That's really helpful to know.

Really appreciate you and the other commenters providing these insights.

[-] blixo@lemmy.fmhy.ml 1 points 1 year ago* (last edited 1 year ago)
28

After searching around online, it seems REPACK (for TV Shows and Movies) means something different when used by Scene groups vs P2P groups.

From what I've gathered:

  • Scene REPACK means something was wrong with the original (non-REPACK) upload. The original Scene release group then releases a fixed version and labels it as a REPACK.

All I've been able to find on P2P REPACK's is that it means something different than it does for Scene. Does anyone have any additional context on what REPACK means when used on P2P releases of TV Shows/Movies?

[-] blixo@lemmy.fmhy.ml 1 points 1 year ago* (last edited 1 year ago)

Thanks for the reply and the link! I agree, based on everything I'm learning in this thread, seems like the FLUX version is the way to go for the added bitrate.

[-] blixo@lemmy.fmhy.ml 1 points 1 year ago

Oh, good call. I didn't even consider that!

[-] blixo@lemmy.fmhy.ml 4 points 1 year ago* (last edited 1 year ago)

That makes sense and helps to conceptualize the impact of the bitrate difference. I guess I was under the impression that bitrate would be set at the source and not by the release group, but seems I may have been wrong in that assumption. Thanks for the info!

[-] blixo@lemmy.fmhy.ml 2 points 1 year ago

Ohh, I didn't realize the release groups would set the bitrate. I figured that was set at the source. But that makes sense. Thanks for helping to clear this up! I was at a loss trying to connect the dots on the size differential here.

[-] blixo@lemmy.fmhy.ml 1 points 1 year ago

Gotcha. Any idea why the bitrate would be different on a WEB-DL from the same source? I figured bitrate would remain the same if the file is being downloaded and DRM stripped, with all else (source, resolution, etc...) remaining equal.

[-] blixo@lemmy.fmhy.ml 1 points 1 year ago

Process, meaning like encode? Or can it be processed in other ways that doesn't alter the quality?

I noticed that the smaller file is longer, interestingly enough. So there does appear to be some level of trimming I'm assuming, but I wouldn't have expected the longer file to be the smaller one.

15
submitted 1 year ago* (last edited 1 year ago) by blixo@lemmy.fmhy.ml to c/piracy@lemmy.dbzer0.com

Hello - I need some help understanding something. I'm looking at two WEB-DL files from reputable groups that are identical in nearly all ways (see details below), except one file is noticeably larger than the other (2.8GB vs 3.47GB, for example). I thought WEB-DL's should be the same size if they're from the same source (AMZN in this instance), so I'm a little confused as to why there's such a disparity in size when all else appears equal.

Any idea's what could explain the difference in file size here? I'm assuming the FLUX file is older based on when it was first uploaded vs the NTb one. Could this have something to do with it?

Bonus question: Which file would you choose in this situation?

(1) 1080p.AMZN.WEB-DL.DDP2.0.H.264-NTb

  • FileSize......: 2.80 GiB
  • Duration......: 42 min 35 s
  • Video.........: High@L4 | 1920x1080 @ 9 197 kb/s
  • Audio.........: English Dolby Digital Plus | 2 CH @ 224 kb/s
  • Subtitle......: English / English.

(2) 1080p.AMZN.WEB-DL.DDP.2.0.H.264-FLUX

  • FileSize......: 3.47 GiB
  • Duration......: 42 min 12 s
  • Video.........: High@L4 | 1920x1080 @ 11.3 Mb/s
  • Audio.........: English Dolby Digital Plus | 2 CH @ 224 kb/s
  • Subtitle......: English.

Edit: Thanks for all the replies! For anyone who stumbles upon this later on with a similar question, there's some really great replies in the comments below worth checking out. In my case, the file size difference was due to the difference in bitrate, where the bitrate differential is likely due to either (A) the region where the AMZN WEB-DL occurred (with different regions having different bitrates), or (B) the release group modifying the bitrate to fit a specific need (like limiting the file size). Knowing both release groups here tend to prioritize quality, I'm guessing the region is likely the main driver in the difference in bitrate size.

blixo

joined 1 year ago