![]() ![]() I'm stuck.Īlso with the old Windows Server, compability problems arise when I'm searching for (modern) tools on video encoding. Always the latest versions of the Xvid Codec for Windows (Windows XP SP3 and newer) including the GUI frontends (Video for Windows (VfW) and DirectShow. Right now I'm back using avisynth and it works great on 8bit sources, even UHD ones. And doing 4K UHD encodes is killing the memory after a few minutes. I'm sorry if this is a stupid question, but I've read this thread (albeit speedily) and I cant find an answer to my problem.īTW I'm doing encodes on a few (old, I know) Windows Server 2008 with 4GB RAM each. Sometimes it's as small as 100MB with 50 frames, and the largest I've seen is 6GB with 500 frames on UHD videos (on my 16GB RAM machine). How is this calculated? My guess is it's about the GOP size or something, I don't really understand how it works, sorry. It keeps eating RAM even doing full encodes in batch mode, which if I remember reading somewhere, should disable the caching, CMIIW.Īlso, using the caching driver, when opening different video files it shows different max RAM / frames to cache for each video. Virtualdubs external encoder feature supports both of these encoders. There is absolutely no reason why Virtualdub needs a VFW 265 encoder since the addition of the external codec feature and x265s support of stdin. x264 VFW can do both AVC/H264 encoding and AVC/H264 decoding. Not sure why anyone uses Virtualdubmod since it has not been upgraded in years. I keep reaching my max RAM when doing full encodes, and seeing "out of memory", "thread not cycling", "stuck when trying to abort" and other errors. x264 VFW Codec, use x264 in for example Virtualdub or other that supports Video For Windows(VFW) Codecs. Is there an option to the caching input driver to limit the amount of RAM to be used, or maybe how many frames it can cache?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |