2/11/2024 0 Comments Ripbot264 nvenc![]() I use the batch encoder distributed among two servers (one on the main encoding PC and the other in a VM on my gaming PC). I've been having some issues recently with encodes hanging after completing the chunks. Both original videos are the same exact format as each other, one's 15 minutes, one's 1.5 hours. Confirmed all threads are being used by Ripbot264 as well and "Use Multiple processing threads" is checked.Įdit 2: New observation is that smaller videos seem to encode at roughly the same speed in Ripbot264 but longer videos just encode incredibly slow right away. Couldn't find anything in the forum giving me any indication why Ripbot264 would be up to 10x slower.Įdit: Resolution was set to 720p in both Ripbot264 and Handbrake from original 1080p (same clip used). Tried Intel and AMD CPU powered machines, same issue. Tried GPU decoding and CPU decoding in settings for Ripbot264 and doesn't make much if any difference on any Nvidia or AMD machine. ![]() Example, Faster preset for HEVC in Ripbot264 = like 12 fps. Tried multiple machines and they all are acting the same way. I'm trying to figure out for the life of me why Handbrake is encoding about 8x-10x faster with the exact same x265 settings and presets on both GUIs. Good luck, I might even do the same myself. ![]() You can go one step further if you like and grab this :-Īnd customise your "bloated" nVidia driver package to install only what you really need. RipBot has a long history with certain elements of nVidia drivers, so you really only need to do a "Custom" install, and then probably only choosing the main graphics driver, maybe the audio driver, and maybe Physics, but NOTHING else, and DON'T use the "Express" install option !!! Yes, there it is, and like Atak said (above post). RipBot, Windows and all other software are latest versions, as is motherboard bios (Gigabyte Aorus B550 Pro V2)Īvisynth+ is 3.7.0 and the Nvidia software is The machine is dual boot and the same problem whether I run on Win 11 current version or latest insider release (dev channel). No change from above, if EncodingServer.exe tries to run then RipBot will hang. So, there must be something you need to re install, as your RipBot work OK with W10, so just check, are you using the latest build of RipBot ?, maybe a newer build of Avisynth, or VC_redist.圆4. I ran RipBot with a very early Beta build of W11, with no issues at all, however, W11 itself started to piss me off, so I went back to W10.īut I am about to upgrade one PC to "proper" W11 in the next day or so, so hopefully there'll be no problem's. Otherwise when run in local mode ripbot264 works as expected, other then the failure to close fully on exit. EncodingServer loads normally in safe mode. Trying compatibility mode did not help (tried 8 and 7, there is no Windows 10 mode). (2) EncodingServer no longer works, I can see it in Task Manager, but there is no gui and trying to run in distributed mode does not work - no connections are made. (1) ripbot264 no longer closes cleanly - it continues to be visible in task manager as 'not responding'. I have recently migrated to Windows 11 (from Win 10 Pro 64 bit).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |