![]() Plus, doing that would reduce the video quality further down the line. I wish it to be done in a single session. But since I have 8 tracks, I don't have the time to come and check the PC to render them separately. So I Googled and I found that others are able to render seperate tracks of their video and make them smaller for Vegas to work with, so the rendering naturally becomes less intensive. I am trying to render in high quality MP4, so I think the problems start from there, but since I don't mind waiting a multitude of hours to render a four-minute video, I thought: "Isn't there a way to make the renders less RAM-intensive and make them slower, so I can actually get the video done?". At this point, Vegas is already eating up 97% (!) of my RAM, but since I usually render my videos while the PC is idle, I don't mind it.īut when the more intense parts come in, the Windows message comes up and says I am low on memory and Sony Vegas Pro has just crashed, halting my render. The first few seconds of the video (which take minutes to render already) don't have very intense effects so the rendering went through well in that part. Vegas helped deliver a better insight into how media production is truly meant to be done, delivering a real Professional Grade feel that dominates anything that WLMM could've delivered to us in years prior had this switch not ever been done, my group's works would've suffered significantly and remained stuck in an era of static impact going forward, thus I wholeheartedly applaud what Sony and MAGIX have done with the software in my time of using it, Vegas Pro may not be perfect but it still gets the job done for me and my workforce far more than virtually any other software could at the speed and effectiveness that it has managed to do for north of ten years.I have composed a large project with about 8 (3 or more are usually inactive, so 5 at a time) tracks with video effects and such, and was successful with a few crashes. Reasons for Switching to VEGAS Pro: I upgraded to Vegas Pro (Version 011) from Microsoft's Windows Live Movie Maker that initially came with Windows 07, which was significantly important in assuring the improvement of production quality and file size of our works in Late 2011 and onward, with us moving away from WLMM completely in Late 2014. Overall: I have been using Vegas Pro in an official capacity since 2011, with history using it as early as 2008, currently on Version 016 (Build 0352) as of typing: This software has served as the only resource that I and many of those who make up my production team use to produce our local programming, due to its noticeably easy User Interface and extreme ability to be enhanced through Third Party extensions to help keep a user on the same build for many years before having to do a major upgrade its constant performance and stability improvements with each version and future generations of CPUs, GPUs, and RAM assures that it will continue to see ever more use as it becomes easier and faster to produce even the heaviest of workloads.Īlthough it is plagued with a plethora of Glitches and Crashes that get fixed as the software matures and CPU/GPU Driver updates arrive, Vegas Pro is significantly more affordable and accessible than Adobe's suite of software and other relevant competition, having far more community support than most other platforms optimized for Intel and AMD's modern era Sixteen+ Core CPUs and AMD's Vega II GPUs, anybody can build a High End Desktop for less than 2000$ USD and see effective results with Vegas Pro for many years to come, media producers such as myself can develop local programming without having to upgrade an HEDT system for a good while and we'll still get the most out of the software, it is ageless and will continue to deliver a powerful impact.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |