I have the same problem. The page file grow bigger and bigger.
I hope that Magix fix bug tle page file because I have this problem with files m2ts with camera sony ax2000e, with mov files Vegas 14 works ok.
I load mxf files and like everybody else, notice the memory leak. I close the project but not the Vegas, load an empty new project, put mp4 files on the timeline (which should not show high memory behavior) and the insanely high commit charge is still there.
Magix should definitely fix this very soon.
Every time I try to send an error report I get this message. How do one communicate with Magix?
"Unfortunately there was an error during sending your request, please try again later."
I try to send this.
Vegas 14 seems to have a paging file problem. I have a 16GB internal memory and normally let windows look after the size of the page file.
When trying to run Vegas 14 using a project created in Vegas 13, Vegas 14 crash with a out of Memory report. Running the task manager I can see that Vegas 13 uses only 10.8 GB of 31.9GB. When running Vegas 14 I have to manually extend the page file to cover at least 51GB (I set mine to 123GB).
More worrying seems to be that when I close Vegas 14 the 51 GB will not be released, 51GB is indicated as still committed. If I open Vegas 14 again I have a 97 GB page file and when closing Vegas 14 I still have 97GB committed
If I start Vegas 14 again it will crash when it have used all the 123GB of the page file, however the 96 is still committed.
Every time I try to send an error report I get this message. How do one communicate with Magix?
You're doing it the right way but the support request system has been down for a day now. I have reported it.
Incidentally, in your support request I suggest you also include what format media you are using.
Hi, I think one should stay with the facts! With vegas pro 13 one could load 300 clips> including FX's and transistions without any problems at an acceptable speed and very few people (if any) had problems! One was also able to run other programs in the background during rendering AVCHD!!!
With Vegas 14 pro, loading the same project is a lot slower and then crashes due to "Out of memory Error" with a lot of people, in addition it is not possible to run other programs in the background!!!
Conclusion: A new release should be an improvement on performance, or still be the same as the previous version but with additional features. One should not be forced to find all sorts of workarounds and be faced with deteriorated performance to utilize the product. VEGAS 14 PRO is not yet ready to be used in an production environment!
VEGAS 14 PRO is not yet ready to be used in an production environment!
With professional UHD ProRes files from my Shogun but also the professional XAVC I Files from my FS7 Vegas Pro 14 can be used in my production environment.
Especially with ProRes it is now great, because here VP13 cannot be used at all!
So lets stay with facts as you suggest: that seems to be an issue with specific formats like the consumer AVCHD but maybe also HDV files. That are clear bugs that should be fixed. I assume that the development team will do that.
But that is exactly the fact, it is good that it works for you, but for many it does not, whereas 13 did! Just do a search on the internet and as you say it may also not work for other HDV files. AVC files also give problems and why the sudden extremely high resource requirement? It is a fact that the possibility exists, that at this stage there might be a crash late into an extensive project. With 13 there is more stability. Of greater concern is that "Magix" seems rather quiet...... one would have at least expected them to comment by now, as these crashes are not isolated cases?
If I rememer correctly, when version 13 first came out there were as many if not more complaints, and lots of people were saying "just stay with 12" Vegas 13 is not worth the hassle, etc. By the final build it was a LOT more
stable and people were happier. My view is that this is typical of older software, and I am optimistic the same pattern will apply with version 14. You may need to wait for the next build or find a work-around if there is something you really need/want immediately in version 14.
I have been testing version 14, and have found ways around my main hurdles. For me this means transcoding legacy HDV into cineform, but mostly I am happy to have very good playback with GH4 4k 24p DCI files.
As an aside, HDV has a long history of causing problems in Vegas. I remember specifically purchasing Cineform NEO in order to get a workable solution.
As an aside, HDV has a long history of causing problems in Vegas. I remember specifically purchasing Cineform NEO in order to get a workable solution.
How long ago was that? For me, HDV has been rock solid since SCS introduced a new HDV decoder in VP8.0c in 2008.
+1 nick - out of all the formats / codecs i've used in vegas hdv was the most stable
Ya, could have been quite a while ago... time flies 😃 Don't really remember which version. Do remember the constant crashes when loading large numbers of HDV clips. Probably irrelevant, but the current behaviour reminded me of that earlier experience.
This morning I tried a possible workout: from VP 13 I saved my project in EDL (txt) format, then I loaded in VP 14 and I succedeed. I hadn't time to check if everything was OK, but I hope I can do this soon. Stay tuned! 😁
Alessandro
No way. I can open the project, but it is impossible to edit it.
🙁
I also can load format txt long project m2ts in VP14.
edl should not make any difference... the problem is the loading of the video which is being memory mapped and therefore gets added to the commit pool. edl is just an instruction of what to load and where to put on timeline it does not affect how it is loaded. Just adding clips to an empty project as project media (ie not even putting on timeline) causes the problem. The avail memory pool which can be seen in task manager clearly shows this and can be different on each machine based on memory, disk and vm setup.
It remains to wait for a new builds Vegas Pro 14,I hope that this will happen soon.
Did you try latest build 178?
Did you try latest build 178?
Have the forum users been informed about this other than by Quitter auf Deutsch?
B178? Eh?
NB: ANY WHITE PAPERS FOR B178
Wow! Now that's a different way of notifying us.
I followed Mr Quitter's instructions and installed the latest Build178. Any White Papers saying what was corrected or added?
Have the forum users been informed about this other than by Quitter auf Deutsch?
...
Any White Papers saying what was corrected or added?
I think the missing information in terms of release notes about this b178 will be published next week. Funny enough that the downloader finds the b178 by now.
Any White Papers saying what was corrected or added?
No, even the release notes where the same as b161