9/23/2023 0 Comments Ripbot264 preserve modified date![]() I am happy to know that you would have been interested in trying my "stuff".it doesn't mean that you can't still try it, but I doubt that I will post it again on the Forum. I can understand your frustration and - although I didn´t use your stuff - wanted to say thanx for your efforts and files. In the last year, I have not had enough time to visit doom9 on a regular basis, so I didn´t even download your stuff or played with it. Might be able to use the function introduced some time ago to run the "Job finished successfully.cmd" to automate some script / cli. The only process that is probably an option would be to let RipBot do it's complete process, then before deleting the Temp files, to manually re-encode the files generated by RB, using NVEnc, so basically doubling the time taken to get the desired result. The same probably applies to wanting to use NV Decoding. So even if Atak took the time to implement this, only limited users would take what ever advantage GPU encoding might offer, if the spped of DE isn't there, and let's face it, DE is the most impressive function of any of the main available Encoding apps. So, not everyone has compatible nVidia GPU's, and also the fact that Distributed Encoding couldn't be used, then there's not really any point !! If you don't need segmented encoding, possibly distributed across a network of many PCs encoding different parts of a video, then you may not really need RipBot264. ![]() ![]() Furthermore, x265 can be controlled in many more different ways than NVEnc, so it is suited much better for segmented encoding, and also it can run in several parallel instances (your GPU encoder chip can be used only by one process at a time). NVEnc uses your Nvidia GPU to encode H.265 video, x265 does not. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |