I'm not sure how much ram it should be using. Sounds like your ram usage might be on the low end, but I suppose x264 is using what it needs.BasharOfTheAges wrote:How much more RAM should it be using? I'm running Win7(pro)x64 using the 64 bit version of x264 and my entire system (including having firefox, Pidgin, etc. up) isn't breaking 2.5GB useage. I'm encoding a 15GB uncompressed 720p video too, so it's not like the file in question is tiny.
Sorry, I must have missed this post before. I am aware that a few people have been having this issue, though I have no idea what might be causing it (I am on windows 7 x64 myself, and have never ran into this problem). My gui used to use AVISource for AVI files, but I changed this behavior in order to provide compatability with DV-AVIs output from Windows Movie Maker (they don't typically work with AVIsource). Because the people using WMM (believe me, there are a LOT of them) are probably the people least likely to know how to create their own AVS script, I designed it to work in their favor.Bakadeshi wrote:a problem I found on my sister's windows 7 PC (was helping her encode her video to upload), Directshowsource seems to cause x264gui to stop responding (IE if I add the file as an avi and let your program create the avs files, it just hangs. if I try again to open the avs file it creates, it still hangs. When I edit it and change to avisource, it works fine. Directshowsource seems to hang in virtualdub also, so it could be some problem with the version plugin i have and windows 7. Shouldn't opening an AVI in your program default to AVIsource instead of Directshowsource?
Also, because I'm not completely satisfied with the way ffms2 handles the DV AVIs, I'm not using x264's new direct file loading features yet, until I work out a solution that I am satisfied with.