• 0 Posts
  • 22 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • My network has reset several times and I’ve narrowed it down to an apparent DDOS attack

    It’s not. You will need to lower your torrent client’s incoming connections limit and/or set lower limits to your incoming/outgoing bandwidth in your torrent client. It is clear your network router is unable to handle too much torrent traffic hitting it at the same time, hence the issues you are experiencing.

    For qB

    Tools / Options / Connection / Global Maximum Number Of Connections

    Tools / Options / Speed / Global Rate Limits

    There’s no specific number to enter there, you just have to experiment a bit and set lower numbers until the problem goes away and your network is stable.

    shutting down the client doesn’t help

    It will, eventually. It does take a bit for other torrent clients to realize you’re no longer online and stop sending you traffic / sharing your IP with other peers.







  • What software are you using? Most modern software can already do HDR tonemapping so it would look normal during playback.

    I think the issue for you is that you are downloading files that are DV only, no HDR fallback, and AFAIK media with DV only cannot be played back with tonemapping (hence why you are seeing it all pink/puple/green). To properly play DV media you’d need DV compatible hardware - I don’t have that type of hardware so someone else may be better able to explain those constraints. My desktop is a bit on the old side LOL.

    But anyway in the future you should download media with the HDR tag or media without any DV/HDR tags.

    PS - If you run your media through something like mediainfo and give us the output that should give a more accurate idea of your issue but I’m pretty sure you just happened to have downloaded a DV only file.

    EDIT - On second thought some playback software seems to support DV tonemapping nowadays. It’s been a while since I tried testing that myself, seems easier just to avoid DV only media. Maybe double-check that the playback software you are using supports DV tonemapping and figure out how to enable it.




  • LibreTorrent is the standard if you’re looking for an open source client that works well. You can install from the Google Play Store but from what I’ve read it works better if you install it from elsewhere / sideload the .apk so it can better access the Android storage.

    BiglyBT is also open source and available on Android (never used it myself).

    There’s also FrostWire, it is open source though it tries to do a bit more than just torrents so it’s not always quite what people are looking for. I remember the main dev used to be active over on Reddit not sure if he ever made it over to the Lemmyverse.

    A lot of people do like Flud, not open source or anything like that but it does have its fans.




  • I’m getting the “moov atom not found” error even though the file is at 100%. The whole torrent isn’t at 100% yet, but I enabled sequential downloading.

    Either the .mp4 is corrupt, or you need to wait for the torrent itself to finish 100% complete.

    You are downloading in sequential mode, and it sounds like these .mp4 files were generated with the moov atom at the end of the file. Which means the file is cut off at the very end (aka corrupt) or the torrent itself just never finished downloading the last pieces of that .mp4 file.

    At least that’s how I’m understanding your question… you’re saying the file is at 100% but you’re also saying the torrent isn’t at 100%, to me that sounds like there’s torrent pieces missing to complete the rest of the .mp4 file maybe.

    EDIT: Just to add, technically encoding software can write that moov atom at the beginning of the .mp4 file which would avoid this problem entirely but it sounds like these files you’re downloading aren’t encoded that way. In encoding software usually that means “optimizing” the file or making it “web” ready for a web browser to play immediately as it downloads sequentially… I forget what ffmpeg calls it specifically.

    EDIT 2: Thinking about it, if you’re desperate to play this file as-is maybe you can run it through ffmpeg to create a new .mp4 file and then play it that way. It’s not a real fix since the original source seems to be broken but you may be able to get something playable at least.



  • Torrent swarms need at least one connectable (port forwarded) peer for any torrent data to transfer. In large torrent swarms you won’t notice this too much since there are usually plenty of connectable peers available.

    The effect tends to be more noticeable in smaller swarms.

    In practice you may not notice unless you try to download those torrents with one lone seed who also happen to have no port forward. In those cases you’ll see there’s a seed but no torrent data ever transfers over to you. (note that the same happens in reverse if you’re the lone seed on many torrents)