I have 2 "out of memory" problems:
1. I create a project with 1920/1080 - 60fps m2ts clips.When I try to render this fairly large project VP freezes because of memory problems.
2. When I later try to load that project Windows 10 gives me an out of memory message after loading about 32% of the project although the Task Manager shows I only used 4 Gb out of 16 Gb available.
got the same problem while loading
Magix can't reproduce the problem, i sent them my files
[Ticket#2016092117003023]
I created a similar project with VP13 and that loads properly w/o memory problems. I was also able to render that project but the first few seconds have blackout/stutter problems before contnuing normally. It is a 35 min project that took about 90 min to render.
When I loaded this VP13 project into VP14 it loaded completely but at the end of the load Win10 requested to close VP14 because of not enough memory.
I have no problems with VP13 but the same problems with VP14
Thats why i'm oppened a support ticket
I think my rendering issues are the same thing... a memory problem. Back in version 13 they gave me a work around where I could go in and manually set the amount of memory that Vegas can use... Which fixed it back then. Not sure how to do the same thing with the new system and windows 10...
I have 32 gigs or ram so no way should I be getting ram rendering issues.
There have been various threads that all point to the same memory handling problems:
This desperately needs fixing in the first patch. Submit a support request at https://support2.magix.com/customer/en/vegas/form
This is from the VP14 release notes:
"Improved playback and editing performance when using a Dynamic RAM Preview cache size greater than 200 MB."
It seems likely to me that whatever changes they made to the code to make that happen, also caused these new problems that we're experiencing.
"Improved playback and editing performance when using a Dynamic RAM Preview cache size greater than 200 MB."
I have not seen any improvement in playback either; not any different then VP13 or even 12. Setting the preview ram on my system higher then 200 will cause it to slow down, same as always.
There was also discussion and testing on this thread: https://www.vegascreativesoftware.info/us/forum/opening-a-project-simply-destroys-my-ssd-disc-space-what-should-i-do--103705/?page=last#ca640680
I've been doing some testing here with simple projects consisting of a single track of small HDV video (no audio) with a single color curves FX on them.
The most I can get VP14 to open is about a 30-minute timeline. Anything longer than that and it's out of memory.
My system specs are on my profile. Here are the comparative times and memory usage of 3 versions of Vegas approximately during the last 30 seconds of the project opening and the first 30 seconds of it staying open:
VEGAS PRO 12.0 BUILD 770
Project opening: 161 seconds
VEGAS PRO 13.0 BUILD 453
Project opening: 47 seconds
VEGAS PRO 14.0 BUILD 161
Project opening: 60 seconds (just before the graph topped out and caused an out-of-memory error)
Has anyone tried opening a project file they are experiencing this issue with after unchecking "close media files when not the active application" in prefs, and setting dynamic RAM preview to 0?
Has anyone tried opening a project file they are experiencing this issue with after unchecking "close media files when not the active application" in prefs, and setting dynamic RAM preview to 0?
Yes. Just made those 2 changes in the preferences, restarted VP14, and tried my same 30-minute HDV project again. Exactly the same result as above. When I try a 35-minute project, I get the out-of-memory error.
Yes. No change, Vegas crasches
Futher information... I can put 4 hours (400 events) of Panasonic GH4 UHD 30p progressive footage in a VP14 project with a color curves FX on every event. The project opens almost instantly and there is no "memory usage ramp" like seen in my above screenshots of an interlaced HDV project. This issue certainly seems to be format-dependent, despite compoundplug.dll being the decoder in both scenarios. I'm wondering if it's related to interlaced footage, although some of the formats others have tried sounds like they're not interlaced. I have tried with both "disable resample" and "smart resample" set in the project and on all the clips and no difference.
If you have Media Manager active try disabling it.
If you have Media Manager active try disabling it.
Same result. But thanks for the suggestion.
I also tried a project with 1300 interlaced PAL DV clips totally nearly 4 hours and that behaves normally. Opened in 25 seconds with no memory-usage ramp in the resource monitor.
I just tried a project that is 1 hour and 45 minutes. I rendered it and it worked fine. I have the GPU on. Memory use was a max of 20%
I created a similar project with VP13 and that loads properly w/o memory problems. I was also able to render that project but the first few seconds have blackout/stutter problems before contnuing normally. It is a 35 min project that took about 90 min to render.
I rendered the same project but w/o a simple text title at the beginning and it rendered w/o blackouts/stutter. This problem goes way back to at least VP12 and was never fixed. This might be also memory usage related. And, if I recall properly, VP12 did not return all memory after being closed.
I too am having the memory error happen when I try to open a wedding project that has about 17 minutes worth of video from 3 cameras on the timeline, maybe 30-40 minutes more in the media bin. AVCHD video.
My issue was not so much about how long the projects were, but how many projects were open. I could easily open up around 8 projects at once in 13 and render them all (supported or not) simultaneously without a problem.
In version 14, as soon as I open a second project alongside the second, it crashed (Windows memory issue alert as well as a Vegas crash).
There was definitely a change in the memory usage.
fr0sty, I have the same type of issue. I can start a new project just fine, but when I add avchd clips to a bin, my resource monitor show the memory usage climb until VP creashed or my machine crashes. If I only have a few clips, things seem fine. I haven't even tried to render anything yet. EXAMPLE:
32 GB of RAM gone in a minute or two.
Maybe a patch will fix this, but at this point considering Adobe PP or sticking with VP13 for another year.
After some further investigation i noticed that the committed memory level increased every time I added a clip... I have 64Gb of mem and nothing on the timeline as simply adding clips to media bin... Thre is no paging... BUT when the committed mem hits the commit limit everthing is affected not just Vegas... and usually things crash. At the moment with nothing on the timeline and just clips in the media bin I have 80Gb committed... so got to go and allocate more VM so I can proceed... not sure why that needs to be the case - need to allocate a space on paging disk (which won't be used by the looks of it since the files are pulled from their own disk anyway) of at least 150Gb for this project...
Have tried to log a ticket for this severla times today but just keep getting try later - anyone elsable to log things?
Hi!
I was affected by the issue. After reading a couple of last posts here, I started to play with virtual memory settings.
I have an SSD, so I configured my VM to a minimum after I've installed the system. I decided to change the setting to "Managed by system". After this started V14- the problem project did crash, but much later, than before. So I just moved the page file to the HDD with plenty of space (disabled it on the SSD system drive, on the HDD it is set to "Managed by system", because I thought that page file size is limited on SSD because of overall free space there. The project loaded with no crash. Could this be a solution or at least a tip for Vegas programmers?
Marcin
Could this be a solution or at least a tip for Vegas programmers?
I thought I would test this on Windows 7 Professional while I'm running the Vegas 14 trial. I loaded 269 (over 3 hours) AVCHD files on to the Vegas Pro 14 timeline and watched the memory usage climb. I never experienced an "out of memory" error although that's not the way I would usually like to work. I have 16GB of memory and I let Windows manage paging on my SSD only.
Just because I'm easily entertained, I added .MOV files until even I got bored at almost 7 hours on the timeline.
Edit: See my future post before drawing conclusions.