![]() 16:37:48 : D:\DVDRip Work Files\Programs\RipBot264v1.24.0\Updates\ffmpeg.zip has been correctly extracted! 16:37:39 : D:\DVDRip Work Files\Programs\RipBot264v1.24.0\Updates\core.zip has been correctly extracted! 13:38:26 : CRC32 value has not changed for. ![]() 13:38:26 : File D:\DVDRip Work Files\Programs\RipBot264v1.24.0\Updates\lsmash.zip saved! 13:38:25 : Downloading file to D:\DVDRip Work Files\Programs\RipBot264v1.24.0\Updates\lsmash.zip it then quickly proceeds to Gathering information and Extracting Frame and only take 3 or so mins now. ![]() and you can tell that when it compressed it because just right after indexing and before Gathering information, you see the ripbot status bar briefly shows Compressing Index. so instead of the massive 1.25GB index file. i also noticed that it compressed the index with the new update. either way, Lmash got updated, and now when it gets to Gathering Information/Extracting frames, it does so much faster. so i looked into the update log, and looks like either Atak may have enabled a new update for Lmash pushed a new version update to ripbot. i launched ripbot again and it udpated itself. there's a new update that just rolled out a few mins ago. FFProbe was already launched once when demuxing was taking place but why now again? 1.25 when it gets to the Gathering Information and extracting frames, it takes like 5~10 or so mins? i checked the task manager while it's doing its thing to find out why it's taking this longer, and looks like it's launching the ffprobe AGAIN to do something. 1.23.1, after demux and index, gathering information only takes about 5 seconds on my Nvme doing HDR H265 source, now with v. I confirmed the performance difference by comparing to v. i built my encoding machine purposely with all Nvme drives to speed up the demux and index process, but it seems with the latest Lmash update, after the demux, and after index (which btw you can tell that sequential disk read/write are both at max), "gathering information/Extracting Frames" seems to be doing some additional CPU crunching without much disk usage or if at all and that "gathering information/extracting frames" process now takes wayyyyyy longer than before. I got a bit of an odd question for the author, i noticed that ever since v 1.25, with Lmash decoding i assume, the indexing process takes twice as long than before.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |