Todd, what version of Vegas was this and what kind of file? The files are labeled ProRes but it's odd they are using hardware GPU decoding in Vegas so I wonder if they are something else (HEVC?) Magix also updated the ProRes code earlier this year which made a big difference for performance.

The user was banned and the post removed so Magix are more then a little bit sensitive about this.

We (VEGAS Creative Software) and Magix do not ban users. This is a user to user forum. If a user was banned, it was probably for violating the forum rules, which are enforced by the moderators who are not Magix or VEGAS Creative Software employees. And posts are only hidden for violating forum rules, especially when they are attacking other users. If posts are entirely deleted, it is probably due to the users themselves deleting posts.

In general, we welcome comparisons and fair criticisms because it pushes our team to do better.

Welcome sentiments. But I have seen moderators close down discussions about Resolve. It was a while back so I cannot reference it.

“If posts are entirely deleted, it is probably due to the users themselves deleting posts.”

I consider the habit of moderators deleting users posts sometimes a bit cowardly. Moderators will delete a post, give no reason, and the cowardly part … the user doesn’t even know who did it. This has happened to me more than once in the past.

One other thing on this topic. I also consider it cowardly that a moderator uses the private messaging to attack a user. If they have something to say, say it in the forum, this practice should be stopped by Magix. OTOH maybe Magix agrees with and encourages it, who knows.

Welcome sentiments. But I have seen moderators close down discussions about Resolve. It was a while back so I cannot reference it.

“If posts are entirely deleted, it is probably due to the users themselves deleting posts.”

I consider the habit of moderators deleting users posts sometimes a bit cowardly. Moderators will delete a post, give no reason, and the cowardly part … the user doesn’t even know who did it. This has happened to me more than once in the past.

One other thing on this topic. I also consider it cowardly that a moderator uses the private messaging to attack a user. If they have something to say, say it in the forum, this practice should be stopped by Magix. OTOH maybe Magix agrees with and encourages it, who knows.

JN. 100% accurately said. I am a Vegas Pro user and I can't denied the facts that the two major NLE competitor is simply performs TL/Rendering far better then Vegas Pro can. But when any time some one made a post saying anything negative Vegas Pro. Bam, you got a s h i t loads of people will jump on you or delete you out etc. For that reasons, I rarely comments or participate on the forum. However I do lurk the forum on and off.

I am 50/50 of Vegas Pro and Davinci Resolve studio depends what footages I am working on. If I am working on hecv 60P and or 8K footage from my drone. I would then will use Davinci Resolve studio.

@BruceUSA I was wondering why I hadn't heard from you in quite some time. That's a pity really, you've been around here long before I started with Platinum 13.

I agree. There is another way I look on it though, when the Fanboys descend, I just stay and annoy them more. Maybe it's a combination of fanboy and Stockholm Syndrome. Anyway, don't let them get you down, great to hear from you again.

There's a huge difference between making a valid comparison, or drawing attention to a flaw in VEGAS, and making 100 posts all about the exact same thing, or interrupting other threads off-topic with the sole intent of repeating what was said 100 threads ago... incessantly. There's a point where drawing valid comparisons and constructive criticisms simply become thinly-veiled bashing of the product, and especially the team developing it, We mods carefully discuss and debate any thread closings, bans, or anything of that sort, and in all cases we give warnings, sometimes far more than we should (no joke, it's dragged out for months with some users repeatedly violating the community standards), to the affected users before we take action.

What I'm seeing here is pure constructive criticism, and as Derek mentioned, I'm all for it, as this is making VEGAS better... but let's not make a dozen more threads about it.

One other thing on this topic. I also consider it cowardly that a moderator uses the private messaging to attack a user. If they have something to say, say it in the forum, this practice should be stopped by Magix. OTOH maybe Magix agrees with and encourages it, who knows.

I have moderated many forums in my day, and in all cases it is encouraged for moderators to handle any interactions with individual users privately if possible. Not everyone likes being called out publicly. By private messaging, we give the user some privacy to resolve their issue.

If any mod is using private messages to "attack" you, this should be brought to the attention of the other moderators or administrators. However, simply requiring you to follow the community standards is not an attack. Removing posts that violate the community standards doesn't require notification (also keep in mind that sometimes posts get removed for referencing another post that violated community standards). We mods see the post that was removed, we see who did it, and why they did it. We all cross-check each other, if someone feels a post was removed in error, or disagrees with any action taken, it is debated and sometimes the action is reversed.

That said, let's please stay in line with the community standards, keep it on-topic, and talk about VEGAS vs. Premiere video decoding again. If anyone wishes to continue the above conversation in an appropriate space, feel free to DM me, or post it in off-topic so we don't derail this thread any further.

Todd, what version of Vegas was this and what kind of file? The files are labeled ProRes but it's odd they are using hardware GPU decoding in Vegas so I wonder if they are something else (HEVC?) Magix also updated the ProRes code earlier this year which made a big difference for performance.

It is a transcoded 4K60 AVC NVENC file made with handbrake. It's supposed to show a problem with Vegas decoder overloading when using portions of the clip edited together. The title of the post insinuated an incompatibility with Vegas and Handbrake encoded Nvenc files. I have not tested to see if this is true, I like to use software encoding

Todd, what version of Vegas was this and what kind of file? The files are labeled ProRes but it's odd they are using hardware GPU decoding in Vegas so I wonder if they are something else (HEVC?) Magix also updated the ProRes code earlier this year which made a big difference for performance.

It is a transcoded 4K60 AVC NVENC file made with handbrake. It's supposed to show a problem with Vegas decoder overloading when using portions of the clip edited together. The title of the post insinuated an incompatibility with Vegas and Handbrake encoded Nvenc files. I have not tested to see if this is true, I like to use software encoding

The original post in this thread seems to be 8-bit HEVC, presumably from a camera rather than Handbrake. That's pretty different from AVC from Handbrake with NVENC (which I don't use and have never tested- I also prefer software encoding for tasks like that).

JN-, your post was hidden to keep this thread on-topic, as I requested. I will DM you a response, or we can make a thread in the off-topic section to further discuss, but it does violate the community standards to steer a thread off-topic, so let's please avoid that.

@RogerS: The original post in this thread seems to be 8-bit HEVC, presumably from a camera rather than Handbrake. That's pretty different from AVC from Handbrake with NVENC (which I don't use and have never tested- I also prefer software encoding for tasks like that)

Two of Vegas' weaknesses are HEVC source video and Transparency so combining them compounds the problem. I downloaded the project, changed the source HEVC to 4K intermediates, and my preview FPS never dropped below 30, which is good-enough for previewing & editing this project...

@BruceUSA:  I am 50/50 of Vegas Pro and Davinci Resolve studio depends what footages I am working on.

YES, it's good to know how to use more than one NLE and then just pick the right tool for the job... For my paid work involving lengthy historical archival footage, I mostly use Vegas because I get paid by the job & Vegas' superior workflow helps me accomplish more per hour of labor-time... However, for anything involving simulated Zoom video call grids or a lot of animated text, I use FCP... For video slideshows I typically use Premiere & Photoshop. I didn't like the free version of Resolve, but if I get the studio version for free with an upcoming hardware purchase, I may try it again using (2) GPUs...

For my paid work, I edit one project after another & don't want background renders using system resources.... So..., I copy my final VEGs to another workstation that already has a copy of the clients' source video, open (4-6) instances of Vegas, and have them batch-render all of the clients' requested file types while I start the next project on my main editing rig. It's hard to get the other NLEs to function like that...

Premiere Pro and Vegas Pro are two separate beasts, and cannot be compared full-on side by side. Their weaknesses and strengths lies in different areas...... One thing for sure, they are equally both great tools !

Premiere Pro and Vegas Pro are two separate beasts, and cannot be compared full-on side by side. Their weaknesses and strengths lies in different areas...... One thing for sure, they are equally both great tools !

Yes. Agree, Vegas has great basic workflow and no Resolve nor Premiere is that good. Its easy to chceck when switch to them from Vegas. But here on this topic we're talking about performance (code optimization) which is not realated to features.

Todd, what version of Vegas was this and what kind of file? The files are labeled ProRes but it's odd they are using hardware GPU decoding in Vegas so I wonder if they are something else (HEVC?) Magix also updated the ProRes code earlier this year which made a big difference for performance.

It is a transcoded 4K60 AVC NVENC file made with handbrake. It's supposed to show a problem with Vegas decoder overloading when using portions of the clip edited together. The title of the post insinuated an incompatibility with Vegas and Handbrake encoded Nvenc files. I have not tested to see if this is true, I like to use software encoding

The original post in this thread seems to be 8-bit HEVC, presumably from a camera rather than Handbrake. That's pretty different from AVC from Handbrake with NVENC (which I don't use and have never tested- I also prefer software encoding for tasks like that).

Hi @RogerS

It was an original post about Handbrake Nvenc files and problem with Vegas, not a comment in an existing post . Post removed, user banned . I made a trans-code using handbrake Nvenc. Details

Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Main@L5.2
Format settings                          : CABAC / 3 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 3 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 2 min 20 s
Bit rate mode                            : Variable
Bit rate                                 : 49.5 Mb/s
Maximum bit rate                         : 120 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 60.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.099
Stream size                              : 827 MiB (99%)
Color range                              : Limited
Color primaries                          : BT.709
Writing application                      : HandBrake 1.3.3 2020061300

I get the same results with Ryzen 5900x CPU and Nvidia 3070 GPU , GPU use shown is the decoder

Today I will test Resolve with exactly the same clips as in my test projcts with transparency. From my first observations Resolve has no lags and stutters in typical crossfades and uses gpu fx very well. Resolve Denoise plugin works in real time in full framerate on 1080p 24fps project on RTX 2060. Wow.

Found stupid things about Resolve - can't change project framerate after importing clips on timeline (!!) and can't apply FX on tracks. There also no master track for video FX. Why they didn't found that obvious solutions?

Just goes to show, all NLEs have their drawbacks and advantages. That's why there is no single "best" one to use, and many of us use many as a result, based on what the job calls for.