Jump to content


  • Posts

  • Joined

  • Last visited

GrantleyC's Achievements


Novice (1/7)



  1. Thanks for checking the project. I also couldn't fault it on my 24" (iMac) but that has a more normal, lot lower, resolution of 1920x1200pixels (less than a sixth of the pixels of the 27"). I had made sure that the version I was using of MacOS 10.11.6 was fully updated. I cannot find how to further update the graphics driver. One forum stated "On Mac OS X the graphics driver is part of the operating system. You can only upgrade by upgrading to a newer version of the operating system." Following up on that lead, on another partition of the SSD, I have installed the latest MacOS 10.15 (Catalina), and installed VideoPad. VideoPad does not falter even when I make the Sequence Preview very large. However, even when I had not undocked the Sequence Preview and so it is kept at a more reasonable size, I feel that the preview is not quite as smooth as when it is on 10.11.6. In general, I feel that computers will often run the best/fastest when they have the version of the operating system that was installed on the computer when it was manufactured (updated to the last sub-version), rather than the current and often larger operating system. I think I will continue to use VideoPad under MacOS 10.11.6 but make sure I don't exceed the window size that it is happy with. Many thanks for your response. Greatly appreciated.
  2. Thanks Borate for your reply. I have sent a project to you in a personal message. The problem doesn't seem to be project or videos related. On further tests the problem doesn't seem to be directly related to the overall VideoPad window but rather the Sequence Preview window. If I increase the overall VideoPad window the Sequence Preview automatically increases and that sets off the memory runaway. If I undock the Sequence Preview and keep it small, I can increase the overall VideoPad window as large as the monitor will do and everything is fine. But even with the smallest overall window for VideoPad as soon as I increase the Preview Sequence over about 1166x1000 pixels the memory runaway starts. Because of the high pixel density of the Retina display that preview size is physically not very large (approximate image size of 135mmx75mm). I had used VideoPad for a short time on an Early 2009 24" iMac and had no troubles. It was only when I started work on the 27" iMac Retina that I immediately hit the difficulty but when I swapped the file back over to the older iMac it ran without difficulty. The iMac 24" monitor is 1920x1200pixels whereas the 27" has 5120x2880pixels. My guess is that the problem will not occur on any computer (Windows or Mac) that does not have a very high resolution screen, or multiple monitors, because it would not be sensible (or possibly even possible) to have a preview window large enough to cause the problem and still be able to work VideoPad.
  3. Using paid for VideoPad version 8.40 on iMac 27", Late 2015, Retina Display, i7, 32GB RAM, AMD Radeon R9 M395X 4096 MB video card, MacOS X 10.11.6. If the VideoPad window is made larger than about half the area of the screen the VideoPad application memory (as shown by the Activity Monitor) slowly but continuously builds up until the Force Quit Applications warning message displays with "Your system has run out of application memory." (Activity Monitor showing VideoPad (Not Responding) with 88+GB memory used. If the window is kept slightly smaller or if "Open in low resolution" box ticked in VideoPad get Info then the memory usage shown in Activity Monitor fluctuates but rarely (if ever) exceeds 1GB. Full Screen 5120 x 2880 pixels. A VideoPad window size of 3364 x 2146 pixels is OK but much larger fails. Even a relatively short 2min 30 sec 1080p file once in Sequence and being played can make VideoPad fail is a larger window is used.
  • Create New...