[JapDubOnlyPlz] Boku Dake ga Inai Machi (Erased) (Season 1) [BD 1080p][HEVC x265 10bit][Eng Subs]

Category:
Date:
2020-08-21 03:25 UTC
Submitter:
Seeders:
0
Information:
No information.
Leechers:
0
File size:
1.9 GiB
Completed:
336
Info hash:
d9bba974445bb3bb984795b7ed2a83add19b8023
This is a remake of the torrent linked below. This remake only leaves the Japanese audio as this is my preference. This also helps to reduce the file size. If these are of interest to you, do let me know, as that will decide whether I will continue to upload these remakes. Also, if you like the torrent, please consider seeding to help everyone out! https://nyaa.si/view/1190306 If you have any animes that can be found here on nyaa that you would like to be re-maked to only include japanese audio, do let me know also and I shall try to do so if I have the time!

File list

  • Boku Dake ga Inai Machi (Erased)
    • [Judas] Erased - 01.mkv (195.3 MiB)
    • [Judas] Erased - 02.mkv (168.4 MiB)
    • [Judas] Erased - 03.mkv (160.5 MiB)
    • [Judas] Erased - 04.mkv (151.2 MiB)
    • [Judas] Erased - 05.mkv (174.7 MiB)
    • [Judas] Erased - 06.mkv (176.2 MiB)
    • [Judas] Erased - 07.mkv (143.6 MiB)
    • [Judas] Erased - 08.mkv (143.3 MiB)
    • [Judas] Erased - 09.mkv (146.6 MiB)
    • [Judas] Erased - 10.mkv (148.7 MiB)
    • [Judas] Erased - 11.mkv (146.6 MiB)
    • [Judas] Erased - 12.mkv (142.1 MiB)
Your idea is well meant but could be executed better: **This is the problem:** By uploading practically the same files again you take away seeds from the original just to save a couple MB per episode. The best thing in a torrent environment is to channel all peers through one single download. Multiple uploads are justified if they differ enough which these do not. Now people start downloading two seperate releases which practically are the same quality wise and less and less seeds are available for each of them until they are both underseeded. The original encoder put in much time and effort and it would be a shame if the whole HEVC release went underseeded because of this. **The solution:** If you wan't to continue this might I suggest the following. There is this programm called xDelta which compares two files and then notes down all the differences. If you let this compare the release you remove the English tracks from to what comes out after you do, then you get a small file that only contains the difference (the missing English track) as data. You then post this **xDelta Patch**, which is only the size of all the English audio tracks (because thats the difference) in the comments of the original release for people to download. This guarantees that the originilal release keeps its seeds and people can remove English audio tracks with ease. All you have to do is: 1. Get xDelta 2. Download the [Dual Audio] release like you do now 3. Remove the English track like you do now 4. Run original and your file through xDelta 5. Post the resulting patch in the comment of the original release This is the link where you can get xDelta: https://sourceforge.net/projects/xdelta3-gui/ The people applying the patch don't need anything else installed, only your patchfiles that you can provide.
The difference in size between the original and your release is so small, you might as well go with the dual audio option.
it would make sense if you were removing FLAC, but lossy codecs are already so small in the first place; plus now you have torrents you have to seed and maintain.

JapDubOnlyPlz (uploader)

User
Thanks for this @qwerty105. I've tried the XDelta approach but sadly I cannot get this to work as I am not very tech savvy. When I am trying to apply the patch I made, I am constantly getting the following error: The process cannot access the file because it is being used by another process. I have tried to copy the source file to its own folder to ensure that no programs are using the video file to be patched, but this constantly comes up and I am not happy to post something which I myself cannot get to work, as I wouldn't be able to advise anyone who has the same issues. If you know a fix for this, I'd highly appreciate it though as I can then reconsider using this. @Glordit @Simplistic, I don't normally upload torrents, but I thought that considering I'm going ahead and changing the files and can no longer upload the original unless I keep two copies of the files, I thought I might as well help out the community by uploading the changed version I am storing. Though, you make a very valid point about the file size difference being almost redundant for lossy codecs, which I shall take note of. Do you all think it'd be worthwhile if I upload these remakes for Lossless videos only? If not, I may just shelf the idea if it isn't really helping out the community.
What comes to mind with "file in use" is that your download is still active in your torrent client.This also prevents deletion of files because they are seeding. Have you checked that you deleted your download? Should be cleared by creating new copies though. Also to apply the patch you got to **move** the files to the patch folder that alone shouldn't be possible when they are "in use". I have never encountered this problem before. Creating the patch worked though? xDelta should tell you with a little popup saying "Success!". I understand that you hesitate uploading that patch when you can't even test it for yourself.

JapDubOnlyPlz (uploader)

User
@qwerty105 Ah, after a bit more tinkering, I think I figured out what the problem was. my source file and fixed file is the same name and it doesn't seem to like this. So, the resolution would be to have all my fixed files named differently from the source. I'm guessing the reason for this is that when applying the patch, it tries to write a new file with the same name, thereby resulting in the issue I was having. I'll go ahead and do this from now on with any other series I would like to provide the jap only alternative to. I note that it is not possible to post files in the comments directly. Would you suggest that I make a new torrent then for the patches I make, where I provide the link in the comments, or to use a cloud based provider to share the fixes? My only concern with cloud based providers is they sometimes randomly take things down. Thanks for your help in this and kindly informing me how I can best help the community without damaging it!
Oh yeah I forgot about that. Even though xDelta moves the old files to the "old" folder I think it does so after creating the new file. That's why it can't be created. They should just move the old file first and then create but hey can't have everything I suppose. You could name your new files with a suffix _JapaneseOnly or so then people also know it worked. There are many little utility software which let you rename many files at once and suffix something like that to every file in one go. Google some Batch Rename Software for that. I'd upload these Patches to Google Drive / Mega.nz / or even Dropbox. I think dropbox doesn't delete files automatically even if not used for quite some time. Google does have more free space though and Mega even more. I could imagine that MEGA deletes after long time no download. Google I don't know. But could storage would be my way to go because such a torrent will never have enough seeds even if you seed it 100% 24/7. There's many people who simply won't connect to you even if they try once you end up as the only seeder. Wouldn't go with torrent.

JapDubOnlyPlz (uploader)

User
@qwerty105 Hiya, just thought of something about the XDelta approach. Wouldn't this approach be redundant also, and actually even worse in the long run? I was about to fully jump on board with this plan, when I realised that there's a glaring issue. Once a person has applied the patch, the torrent would no longer be seeded anyway, unless they choose to keep two copies (one source and one Japanese only audio). For most normal users, this isn't really an option. Wouldn't it therefore be better if I just upload a remake with the Japanese audio only? As at least in this way, rather than a leech becoming a hit and run, they could instead keep seeding whilst only keeping one copy and saving HDD space. Don't know if I'm reading too much into it, but I would indeed appreciate your input. I've found your constructive criticism very helpful and I'd like to bring benefits to this community rather than negatives. If you agree with my opinion above, I will then only focus on larger encoded where the savings are more of worth unless a torrent is specifically requested. Otherwise, I will consider continuing with the XDelta approach.