Hello there,
after now I made two new (bigger) projects, I found out that the solution that was solved on 04-08-2024 -
https://www.vegascreativesoftware.info/us/forum/vegas-pro-21-started-constantly-freezing--144805/
now, one other Vegas Updates later (Build 315) - one kind of error, which seems a bit familiar with the error seen in the post of me before, is occuring again:
1. Sometimes Vegas stops rendering when in a rendered Part, rendering of an additional FX Track occurs. It can be for ex. simply adjusted color Balance (so only one effect).
->> Rendering stops with the error message that not enough RAM memory is available, but due to the Vegas settings AND Windows Task Manager, there are still about 10 GB of RAM available, which Vegas does not use.
->> After that Vegas stops rendering, sometimes works afterwards, sometimes it crashes completely afterwards (Vegas Error Form occurs, which I filled out and send to supoort a few times since weeks now and with no answer until now).
- Apart from this error, Vegas renders big Parts of 2 Hours of Video-Timeline or so in 4K, 59,95 fps with no Problem. No matter if Vegas renders parts with error or working fine: Vegas is always using nearly the same amount of RAM during rendering (about 8,33 to 12,35 GB RAM). These numbers DO NOT CHANGE, NO MATTER how much RAM I provide to Vegas in the Vegas- Settings in another try of rendering.
So I think there is (still) a problem of Vegas dealing with RAM capacity!?
What is the amount of Dynamic RAM Preview max you have set in Options/Preferences/Video?
Vegas 21 crashes just like Vegas 19
I stopped using Vegas Pro 19 back in 2019 because it crashed so often. I just purchased the upgrade to Vegas Pro 21.0 figuring that the problems should be fixed by now. I’m not doing anything complicated. Simply putting 20+, 30 second .MOV files taken with my iPhone 14 onto the timeline, trimming, and putting a fade transition between them. Within the first 5 minutes of use Vegas crashed. I was not opening any other program at that time, simply moving a clip to create a fade. An autogenerated report was sent to Magix (2024-June-23). I’m now forced to try to remember to save every 5 minutes to avoid losing work. So, what can anyone tell me about the stability of Vegas 21? Thoughts?
My System
Thank you.
Scott
I’m now forced to try to remember to save every 5 minutes to avoid losing work.
No need to do that while
I upgraded from B314 to B315 and every time I try "Render As ..." Vegas Pro 21 crashes.
Hi I installed Vegas pro 21 B315. Eery 3 min it craches. Can I resolve that?
Hi I installed Vegas pro 21 B315. Eery 3 min it craches. Can I resolve that?
Maybe, but therefore we have to know your used hardware, drivers, etc.
For good answers it is better to start your own thread and give that information following this https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/
under B and C
Hello,
Since I installed the new update, I have had problems with the video files I capture using OBS.If I cut these files on my timeline, there are bugs. The cut parts do not match in the pan/crop and preview window. The video sometimes returns to a previous passage, it is not synchronized...
Did you have this kind of problem too?
@JH26 Can you share the settings you used in OBS? MediaInfo would be helpful.
These are videos that I capture from OBS to .flv (AMD hardware encoder or x264 preset software encoder) and then convert to .mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 960 MiB
Duration : 28 min 55 s
Overall bit rate : 4 641 kb/s
Frame rate : 25.000 FPS
Writing application : Lavf60.16.100
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Constrained Baseline@L5
Format settings : 1 Ref Frames
Format settings, CABAC : No
Format settings, Reference : 1 frame
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 28 min 55 s
Bit rate : 4 438 kb/s
Width : 2 560 pixels
Height : 1 440 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.048
Stream size : 918 MiB (96%)
Writing library : x264 core 164 r3106 eaa68fa
Encoding settings : cabac=0 / ref=1 / deblock=0:0:0 / analyse=0:0 / me=dia / subme=0 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=36 / lookahead_threads=6 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=0 / weightp=0 / keyint=250 / keyint_min=25 / scenecut=0 / intra_refresh=0 / rc=crf / mbtree=0 / crf=14.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=0
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : avcC
Running V21 build 315. Working fine until this morning, now when I render it just freezes and I have top kill the process. Checked my update log and see that Microsoft kindly installed Windows Configuration Update KB5035942 last night. Coincidence? Maybe, but... Anyone else see this?
@EricLNZ Win 11. This patch - from a few months ago but for whatever rwason just got installed. https://support.microsoft.com/en-us/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df
#ericLNZ thanks - no idea why it only showed up on mine a few days ago, I have Windows on auto-update (which isn't always a good idea). I narrowed it down to a problem with an audio VST that seems to have broken with the patch, or at least that was what broke and that was when it broke. Now I need to find out what is going on there, but at least Vegas is working again with the removal of the vst. So many parts all working together (mostly)... I should know better than to auto-update in the middle of a project. Also better error messages are always appreciated, and time-outs for third-party modules.
I upgraded from B314 to B315 and every time I try "Render As ..." Vegas Pro 21 crashes.
Correction: "Render As ..." works in B300 (Support kindly gave me a link to retrograde), but does not work in either B314 nor B315. So something broke in the B300 to B314 upgrade.
I am running on legacy hardware, a machine originally running Windows 7 Ultra, but now Windows 10. and various hardware upgrades such as to NVIDIA GeForce GTX 980.
I don't even get to the render properties to choose rendering on graphics card or not.
@Bockeman I have no idea what "legacy hardware" is. You have to be more specific. Specific CPU make and model along with how much system RAM you are running. Also, you will have to provide more information. VP314/315 renders anything I want with my hardware listed in my Signature below.
Screenshot of Options>Preferences>Video tab and also File I/O.
Also a screenshot of your "render properties" too might help.
But start a new post (things will get lost here since this is a general topic post, not a specific topic one) and include the necessary information.
Here is what I see when I go to Render As...
Preferences>Video, and File I/O
@Bockeman I have no idea what "legacy hardware" is. You have to be more specific. Specific CPU make and model along with how much system RAM you are running. Also, you will have to provide more information. VP314/315 renders anything I want with my hardware listed in my Signature below.
Screenshot of Options>Preferences>Video tab and also File I/O.
Also a screenshot of your "render properties" too might help.
But start a new post (things will get lost here since this is a general topic post, not a specific topic one) and include the necessary information.
Here is what I see when I go to Render As...
@Reyfox Thanks for responding.
I used "legacy hardware" to indicate a very old machine, originally purchased in 2011! But this still meets my performance and storage requirements having upgraded many componenets, e.g. GTV980. Details from the top of msinfo32 System Information are:
System Information report written at: 06/29/24 10:50:43 System Name: XXXXX [System Summary]Item Value OS Name Microsoft Windows 10 Pro Version 10.0.19045 Build 19045 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name VERIULAN System Manufacturer System manufacturer System Model System Product Name System Type x64-based PC System SKU To be filled by O.E.M. Processor Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz, 3501 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date American Megatrends Inc. 0706, 2011-08-05 SMBIOS Version 2.6 Embedded Controller Version 255.255 BIOS Mode Legacy BaseBoard Manufacturer ASUSTeK Computer INC. BaseBoard Product P8Z68-V PRO BaseBoard Version Rev 1.xx Platform Role Workstation Secure Boot State Unsupported PCR7 Configuration Binding Not Possible Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume5 Locale United Kingdom Hardware Abstraction Layer Version = "10.0.19041.3636" User Name XXXXX\XXXX Time Zone GMT Daylight Time Installed Physical Memory (RAM) 16.0 GB Total Physical Memory 15.9 GB Available Physical Memory 7.41 GB Total Virtual Memory 31.9 GB Available Virtual Memory 18.9 GB Page File Space 16.0 GB Page File E:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes
There's no point in pasting a screenshot of properties, because "Render As ..." crashes regardless.
Importantly, I never get to the render properties, it crashes before that pops up.
Sorry, I've not started a new post yet, but will if things get complicated.
@Bockeman if you can't render anything, I think that things have already gotten complicated.
And there were additional questions asked in my post, warranting a separate post.
Also, from Vegas for CPU requirements: 6th Generation Intel Core i5 (or AMD equivalent) or better with 2.5 Ghz and 4 Cores. Your CPU is a 2nd gen version.
Wanting to edit with the latest software on very outdated hardware is a "hit or miss" situation. I don't understand why you didn't download a trial version first to see how it performs on your hardware.
Please can anybody give me a Definitive answer to the Purpetial licence.
What would I get access to?
Text to Speech?
Vegas hub video and sound clips?
Mocha?
And for how long/any restrictions?
Or is it easier to say what I won't get
Mocha comes with Pro Suite (perpetual or subscription), not Edit.
The rest come with perpetual but with limited access (Suite lets you use more online resources than Edit, so more downloads, transcriptions, etc.)
From Vegas Pro's comparison webpage:
Mocha Vegas only comes with Vegas Pro Suite and Vegas Pro Post versions, perpetual or subscription.
The comparison shows that Edit and Suite only get HD stock footage but Post gets 4K footage.
And for how long/any restrictions?
The comparison page states:
What those limits are is not spelt out - not that I've seen anyway - and what happens when the text-to-speech (and vv) quota is reached for perpetual users is another unknown; for example, does another quota need to be purchased and if so at what cost? It would be great to know for sure.
From Vegas Pro's comparison webpage:
Mocha Vegas only comes with Vegas Pro Suite and Vegas Pro Post versions, perpetual or subscription.
The comparison shows that Edit and Suite only get HD stock footage but Post gets 4K footage.
And for how long/any restrictions?
The comparison page states:
- Due to ongoing cost structures, we are currently able to offer higher usage limits for subscription users than we can for perpetual users.
What those limits are is not spelt out - not that I've seen anyway - and what happens when the text-to-speech (and vv) quota is reached for perpetual users is another unknown; for example, does another quota need to be purchased and if so at what cost? It would be great to know for sure.
Please can you tell me if there would be any updates for the Perpetual (Suite) and for what period. Thanks
At present, versions are updated for approximately 1 year after first release. VP 21 was released in August 2023 so it is likely there will be no, or only minor, updates left for it.
OK, thanks for info, one more if you can spare a minute, has there been any indication of what my be coming in the next version?
No, no announcements yet.