i see a gpu encoding when i can't see the encoding settings used. https://nyaa.si/view/1329000#com-4 just letting ya know [here](https://mirror.animetosho.org/file/ssa-shingeki-no-kyojin-final-season-65v0-720p-mkv.810162)

where is the subsplease version

will you be uploading the subsplease subtitles?

@Edge, in HEVC there's an option to remove encoding settings `-vf no-info=1`, I removed it on purpose so that no one steals my work. Documentation here: https://x265.readthedocs.io/en/3.2.1/cli.html#cmdoption-info

> Removes Settings Insecure much? Steal your releases? Wow pirates getting entitled over re encodes

> Steals the video and audio from crunchyroll > steals DDY's subs > "I hope no one steals my work"

I understand your views, trust me when I say I was once a person who did the same comment as yours on others work @StazCherryBlood and @SeaSmoke, leaving aside that fact that nothing in the file's original source is mine (video, audio and subs are from Subsplease and subsplease got it from CR) but these settings can easily be copied, atleast for now I want to have the privilege of an encoder who properly delivers small sized files. Maybe in the future when I stop encoding I'll publish the encoding settings. And there's a whole project that I built especially to only deliver these, and it's costing me $300/month totally, Though my profit is nearly nothing at all, I don't want the money I'm giving out of my own pocket to go to waste. So I'm keeping the encoding settings to myself. Atleast for now.

>first ever torrent = 1 month 4 week ago >>(From https://ssanime.ga/) >>I won't encode series with large number of episodes because it takes more than an hour to encode 1 episode to 3 resolutions i.e. 1080p, 720p, 480p. The server can handle maximum of 5 encodes in parallel, the number of episodes being encoded in parallel is proportional to time taken in encoding but it's not like 5 parallel encodes will end after 5 hours, but for every episode being encoded parallelly about 15 minutes extra is added to all the encoding running at the same time. >>>number of torrent uploaded =1359 >>>>2 months has total = 1460 hours >>>>>Something feels off <<<< You are just encoding stuff in real time and even being proud of that while ii can see blocking and banding in each screenshot . there is like screenshot in artifacts mess you created with 300USD Imagine spending $300 every month only to make memes. Saying they are Mini doesn't make u qualify to create more artifacts .

You can't expect it to be 100% perfect, lose something to gain something. I'll become better. It takes time.

that's good but can you encode and wait for anime to be encoded nicely in like per 10 hour for one encode instead of storming wiht 20 mii per encode . i don't think so with very fast preset (number of torrent uploaded =1359 2 months has total = 1460 hours)

I'm using slow preset, with rather the parameters I have used can't be done faster than this. Though yea for more better results it would be better to make it slower.

@_Edge_ , if you don't like it go and download someone else's posting . No-one is forcing this on you and going by the statistics hundreds of people choose to download [SSA] files because they get the results they want .

While downloading others is also an option, I also do need to make my encodes better, so I would be grateful if you list out some episodes that have banding, @Edge.

Yours are just denoised randomly, not debanded. And this release is full of banding there is ss in banding, and yes I don't think slow can do encode in 20mins per ep, what a meme, so i will go with believe its nvenc or very fast preset. Anyway yours are unfiltered bit starved releases I don't have much to say here.

I don't know how much you know about encoding @Edge, the server I'm using and paying about $220 (the other $80 is for seedbox) is an AMD Epyc 32 cores/64 threads, do you think it's impossible for it to be so fast?

if you can't see the bit starving you are doing or banding its not my fault that you aren't experienced enough or can't see clear enough

Sounds like some lazy handbrake/ffmpeg cli settings on an EC2 instance. I have 3 machines with 40 core / 80 threads each, 2 of which have a P2000 and one with dual P4000s, if you are doing real filtering + encoding the output to x265 with CPU not GPU, after ~8-10 cores/threads that is all x265 will really bang on for the most part, so clock speed is king. VS likes Real cores and not HT/SMT threads so splitting your workload out to like x265 perams pools=10 and VS to core.num_threads = 22 you might wind up in highish single digit FPS counts for a single encode depending on settings. To be doing 3 rez, 5 in parallel, sounds more like a GPU encode and bumping into the video memory limit of the card you are using, for now, until the HW gets better a GPU encode will just not look as good and be far larger than a CPU/Vulkan/OpenGL encode, so I am guessing you are using a constant bitrate to keep the file sizes down and that is probably leading to the blocking, banding and general grossness. With all that said, there are people who don't care/using it to watch on a phone, have shit satellite internet with bandwidth caps worse than mobile data caps, etc that this may be what they are looking for, so, more power to SSA. It's like cars, some people need a $1k shitbox and others a Lambo, just grab what fits your needs.

I'm using frame-thread=3, no GPU is used, since I can't afford it. If you still think this is shitty, don't come to post it, I've heard enough.


seems like too good encode for you using those advanced scientific encoding values whatever u are using?

seems like too good encode for you using those advanced scientific encoding values whatever u are using?

Come here you piece of crappy patty 

Stop @Edge. I understood, you pause at that exact moment to make it look bad..

dw those are quite few per 30 frames u didn't even bothered to fix

@SSA : sorry but if he can pause something at a frame and it looks bad: it fucking looks bad. Hell, if you can spot the place to pause it, it was bad while it was playing...that's how obvious it is. Just fix the damn thing.

pops the corn