Well, we could say the same about everything else that AnimeTosho fetches. You want your English translated anime, go fetch them yourself. And admin can then retire and save money...
I'm only asking about Shincaps' .ts raws, not the whole lot of raws posted on Nyaa.
He won't because he is too cheap to get a VPN or seedbox. I'd bet that after 1 or 2 people have downloaded his crap he quits seeding. Real uploaders at least have a seedbox, only crappy uploaders don't.
Why doesn't Anime Tosho fetch raws, remuxes and otherwise large files? As mentioned in the above answer, available resources are the primary concern. Large content is particularly taxing on resources, expensive to cater for, and generally unpopular, so the decision has been made to drop these high-cost, low-reward releases.
But I can not find a way to 'generate' that url from the data inside of the database export. Would it possible to get the nekobt id inside of the export? Or directly get the url slug in the export?
Thank you
Comment in Feedback 03/01/2026 17:05 — Anonymous: "John Gundam"
idk how to get in touch with them, I would've done so already
Batches are not priority here, but as admin said, you can request if there's a batch that you want but that doesn't mean it will be automatically honored. I can usually help with uploads when my seedbox isn't actively seeding releases. Just like I did here -> https://animetosho.org/view/ironclad-t...ment150158
Thanks, I understand, in most cases it might not be a large improvement, but sometimes it can be. Some batches will simply be older releases repackaged because CR changed nothing, others may have changes.
It depends on the series, CR's typesetting has varied between "nothing at all" to "\an8 bold and italics" to "minimal tasteful typesetting" (some positioning, maybe a different font) to "motion tracking and fancy typesetting", this depends on the series, no you're not going to get 8MB .ass files with vector graphics, but I sure as hell will prefer "minimal tasteful typesetting" or better when the earlier release was basically almost SRT with nothing on it. If good fansubs are available, then that should be watched, but over 50 series come out in a season, few will get graced with good fansubs, the majority of releases will be from CR, and if they do fix the subs sometimes, it's best to use that version rather than whatever first came out. If you want an example of CR doing actual typesetting, check for example, yesterday's https://animetosho.org/view/subsplease...v.n2059446 this has some motion tracking. Of course you will also find many releases that have absolutely no typesetting. CR has its limitations as to what fonts they use, but on shows that they do some typesetting, they can strike a reasonable balance, look for example at "Ruri no Houseki" or "Sozai Saishuka no Isekai Ryokouki" (later fixed version). Anyway, thanks admin, in practice most of the batches won't have major improvements to subs, but rarely some do.
Thanks for the suggestion. Generally files that have already been processed are avoided, and most of SubsPlease' batches fall under this, so get automatically excluded. If there's something you (or anyone else) want, you can put in a request and it can be reviewed.
Note that subtitle extraction/archival is not a key goal of this website.
Recently the SubsPlease batches seem to have been added to the skipping policy, unless they count as duplicates? It would be a good idea to at least keep fetching the smaller ones like 480p (that should easily be under 8GB), as SP has been trying to do batches with fixed subs where possible and these might not be available from other releasers, it's less about the release itself, and that animetosho extracts the subs and archives them, so for people that already have the releases and just want updated subs, it would be really useful. Updates subs are because CR has been doing SRT-tier subs first and then later updating with properly typeset versions, this mostly applies to subs this season, but at times they've done updates to older season subs. So if admin can at least fetch the small ones, that would be great.
I suggest choosing an image you like and setting it as your profile picture in your display settings, like I have. That way, no one can pretend to be you as "Anon" since your account would have a unique image. Fortunately, anonymous users can’t have a profile picture, so you’ll be fine.
I still don't understand what your frustrations are. No, I don't like any form of harassment here, which is why I pointed out your instance of it. I may overlook it at times (like I have with you), but it's not indicative of it being seen as favorable or accepted in any way, and I do step in if I feel it goes too far (i.e. now).
I don't give a damn about impartiality. If you don't want to be singled out, act like a reasonable person.
Thanks for confirming. Now everyone knows that only -2B- and some other favorites are allowed to harass other people. Nice job.
If you didn't do anything in the past, why would you do it now, just pretending to be impartial? Don't mind me, we can all see what's going on. Keep on with your little bullying group. Feel free to delete this comment too. Peace out.
It’s strange how you jump in to defend some users and not others, it feels like the admin have some favorites here. And no, feel free to delete my comment. Maybe fake -2B- will stop crying about it
God forbid I try to help anyone I guess. But I'm afraid you haven't addressed the x264 part.
Comment in Feedback 27/12/2025 18:21 — Anonymous: "The Real -2B-"
If you transcode and encode the same video to another codec, it will inevitably lead to quality degradation due to the nature of video compression.
So, if you have an HEVC video and transcode it to AV1, then transcode it again to HEVC, you will lose quality at each step: first from the original BD to HEVC, then from HEVC to AV1, and from AV1 back to HEVC (resulting in blurriness, pixelation, etc.). That is why a visual side-by-side comparison of sample frames is the most efficient way to assess quality loss.
The question is clear enough to understand, so be a ware of fake users just fusing around to get attention.
There is no method to determine the previous codec from the final file alone.
The only way is to get the person encoding the file to tell you that it originated from an HEVC source (in your case) but then, what tells you that HEVC used for the encode was not itself reencoded from a VP9 source? That that VP9 encode was not also reencoded from NVENC (h264/h265) source? Etc.
SOURCE => NVENC => HEVC => VP9 => HEVC : could you tell that last HEVC took this road to "be" ? Nope.
So no, there's no magical way to get any certainty, you can only assess the damage.
06/01/2026 18:22 * — ThisisLX