Wow... This is bold.

Kommentare

JJKizak schrieb am 13.11.2020 um 22:03 Uhr

After reading this thread I got to thinking about what future full AI NLE's will be doing. You set your parameters then load all of the video and sound stuff. Hit the complete button and what we do in hours will take microseconds. Just a thought.

JJK

 

Howard-Vigorita schrieb am 13.11.2020 um 22:37 Uhr

What you're basically showing is hardware decoding and encoding is faster than software decoding and encoding, but that's obvious. Although you don't have the studio version of Resolve you must also realise it's obvious that resolve with hardware decoding and encoding will be faster for that particular test. Not always faster though, it's easy to get a 100% GPU bottleneck with resolve and a mid price card dependent on what you're doing, but again, you have a high performance card, so with your PC Resolve studio is likely always to be faster

@lenard To help get a more definitive answer to the whole free but it'll cost you shell game, I just uploaded the video to YouTube. With a download link so folks with the Studio version and/or other hardware can brag about their results. vp9 transcode may take a few moments.

YouTube link:

lenard schrieb am 13.11.2020 um 23:46 Uhr

I know you're saying Vegas Pro is faster then Davinci resolve (free) when using fastest methods to encode AVC, which is true, and I use hardware encoding most of the time, but it has it's limitations , such as when encoding quality based, rather than bitrate, hardware is less efficient so produces larger files. This can cause a lot of problems for applications that require the smallest possible files. The other problem is quality, of which there's often debate that technically software is superior but to many people's eyes watching the video like a normal person would, they look the same, but I have situations day to day where only software is permissible (quality/size) and many times I"ll do software encoding on projects for other people, as any lacking of quality with hardware encoding just makes me look bad.

(Havent' watched your new video yet, but I look forward to it)

animagic schrieb am 14.11.2020 um 02:54 Uhr

Never rely on sales pitches alone. Years ago I moved from Premiere (1.5 I think) to Sony Vegas, because features that were addons in Premiere were included in Vegas. Granted, my video needs are modest because all I need is the capability to import image sequences from my 3D animation program. However, sound is very important for me and I think is very well implemented in Vegas. And various video editing features already mentioned such as automated crossfades are very handy.

Also, Magix took it upon themselves to take an NLE that was more or less abandoned by Sony and advance it further, so I think they deserve some credit for that. As for the "free" argument, which is used repeatedly for various software offerings, it simply means that money comes from elsewhere. Developers need to eat, pay for housing and clothing, etc.

lenard schrieb am 14.11.2020 um 04:41 Uhr

 

@lenard To help get a more definitive answer to the whole free but it'll cost you shell game, I just uploaded the video to YouTube. With a download link so folks with the Studio version and/or other hardware can brag about their results. vp9 transcode may take a few moments.

YouTube link:

So these are the scores

Davinci Resolve (free) 42 seconds

VegasPro18 30 seconds

Davinci Resolve Studio 18 seconds

My mid range gpu from 2016 is near 100% and may be causing a slowdown, but that wouldn't happens with your GPU, so may actually be faster for you

Howard-Vigorita schrieb am 14.11.2020 um 04:49 Uhr

@lenard 18 seconds is a fantastic time but it looks like the lut may not be loaded. I had to first drop the LUT into this directory: C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\LUT\Z-Cam

Here's a screen shot of checking it in the Resolve media tab starting with a right-click on the media...

Steve_Rhoden schrieb am 14.11.2020 um 05:06 Uhr

This comparison nonsense is really old man... There are always varied NLE options, So an editor uses whatever tool works best for him or her, simple!

Also, well put animagic....

 

Grazie schrieb am 14.11.2020 um 05:41 Uhr

Never rely on sales pitches alone. Years ago I moved from Premiere (1.5 I think) to Sony Vegas, because features that were addons in Premiere were included in Vegas. Granted, my video needs are modest because all I need is the capability to import image sequences from my 3D animation program. However, sound is very important for me and I think is very well implemented in Vegas. And various video editing features already mentioned such as automated crossfades are very handy.

Also, Magix took it upon themselves to take an NLE that was more or less abandoned by Sony and advance it further, so I think they deserve some credit for that. As for the "free" argument, which is used repeatedly for various software offerings, it simply means that money comes from elsewhere. Developers need to eat, pay for housing and clothing, etc.

@animagic - Totally agree! Especially your last comment. The MAGIX <>SONY thang was good for us, and to, have the Madison Team come over too, don’t forget that. DO NOT FORGET THAT!

(Gloves off time) Comparisons without a motive become Lame at Light speed. As I asked of the OP, what was it that he wanted to have happen. I might complain about my belly, my lack of hair, so I want my body as it was when I was 23! Ain’t gonna happen. I’m good with Holding Truth To Power, but how about you saying what it is you’re wanting. Everything else is just Tumbleweed and Spitballing. And I can Spit Balls with the best, been around here for 20 years proves it.

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

lenard schrieb am 14.11.2020 um 06:11 Uhr

@lenard 18 seconds is a fantastic time but it looks like the lut may not be loaded. I had to first drop the LUT into this directory: C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\LUT\Z-Cam

 

 

Ok so I fixed it, final results after lut fix

VegasPro18 - 1:13 (software encode - 4ghz 6 core cpu)

Davinci Resolve Studio - 0:44 (software encode - 4ghz 6 core cpu)

VegasPro18 - 0:43 (hardware encode - 4ghz 6 core cpu)

Davinci Resolve (free) - 0:42 (software encode - 4.8ghz 8 core cpu )

VegasPro18 - 0:30 (hardware encode - 4.8ghz 8 core cpu )

Davinci Resolve Studio - 0:19 (hardware encode - 4ghz 6 core cpu)

Job1 hardware no lut, Job2 - hardware with lut, Job3 - software with lut,

My observation: core frequency/IPC counts with Vegas, the new AMD 5000 cpu's should help vegas performance even though they don't make much of a difference with Resolve or Premiere.

Steve_Rhoden schrieb am 14.11.2020 um 06:34 Uhr

Two thumbs up on that Grazie, You and i have been around for a long time on this Vegas train lol, and we have seen numerous pretenders over the years blowing steam at Vegas for no good and futile intentions. So sick and tired of threads that starts like this, that serves absolutely no purpose with this comparing negative blaming game that just goes on and on, and don't try to tell me that its constructive comparison and what not, no its not, its always a ranting fest of hate and nothing constructive ever comes of it!

Magix deserves a ton of credit, for taking in Vegas Pro when it was languishing badly in its later years in the hands of Sony of gross neglect. And Magix worked so hard, immediately after acquiring it, to get it back up in its glorious form, and to this day they work tirelessly everyday to implement as much modern features possible, while seriously listening to users input at every level..... Of course some features that are in other NLE's are not in Vegas, likewise many features that are in Vegas are not in other NLE's.... And yes, for example, Resolve's new Color correction/Grading features are ahead of what is implemented in Vegas. But that does not mean you cannot use Vegas to get the exact same final results, You can!

Dexcon schrieb am 14.11.2020 um 12:22 Uhr

A big +1 to @animagic, @Grazie and @Steve_Rhoden for your recent comments. Fairly much the same sentiments that I expressed earlier in this thread.

I'd be interested to learn from anyone who has been a regular reader on Resolve, Premiere and Avid forums for the last few years if this comparison obsession is commonplace on those forums.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

lenard schrieb am 14.11.2020 um 12:58 Uhr

You want comparison Dexon. well let me show you something crazy I only tried today. It's Davinci resolve's new auto frame. As a comparision, Magix talk about their AI, but use it for coloring old movies and tv shows that almost nobody will ever use, and tracking rudimentary, but what does BMD do, they bring out ground breaking AI technology, and not even mention it in their presentation of Resolve17, and this has real use for people editing multicam. and this question has been asked a number of times here.

"I film plays and concerts with a static camera at 4k, I then crop closeup and midshots, for multicam"

They will then complain about having to manually key the actors etc for the mid and closeup cameras. They ask if Vegas can help here with their tracking. Unfortunately the answer is no due to the complexity of such scenes and the limitation of conventional tracking but BMD said YES WE CAN help, and in beta1 of their new Resolve it works ok, and will only get better. I have made a closeup, and then you could go on to make a midshot, a 3 camera edit

Now wait for this Dexcon. What would you say when I tell you the following is completely 100% automated by BMD AI, I only chose the zoom level, BMD AI did every pan and tracking shot, with no manual intervention, and to my eye it only makes an obvious mistake towards the end, the rest are fine, and remember this is a single closeup cam, but in such a simulation you can keep changing shot to the best camera.

The future is here today, This is BMD AI driven auto pan

note: the updating numbers are x/y axis that the AI is choosing for the camera position

 

Dexcon schrieb am 14.11.2020 um 13:13 Uhr

@lenard  ... Thank you for the comments which relate very much to your wants and needs in an NLE. If Vegas Pro doesn't meet your needs (which apparently is the case), then move on to the NLE that does - from your comments, that is Resolve. If your future is with Resolve, then go with it and forget Vegas Pro. Based on your comment above, why are you bothering to persist with posting on this forum other than to perhaps promote Resolve rather than to add substance and positive help to those who actually want to use Vegas Pro?

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

lenard schrieb am 14.11.2020 um 13:31 Uhr

I don't like using resolve, maybe they can fix that problem one day. I had a dream that with the release of V17, BMD included 'skins' that altered the GUI completely to your choice of editor, I chose Vegas. This thread is about Magix comparing Vegas with Resolve and what they both can do, I was excited to mention something I only used for the first time today

Dexcon schrieb am 14.11.2020 um 13:51 Uhr

Now I am completely confused. You write paragraphs lauding Resolve based on your clients' requests but end up saying you don't like Resolve.

If you've read some of the previous comments on this post, many are tired of these tedious comparisons that seem to go on year after year. As an intelligent human being, make your own mind up and make a business decision as to which NLE or NLEs you wish to use.

 

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

Reyfox schrieb am 14.11.2020 um 14:13 Uhr

I think all of us are aware of Resolve, and have no problem finding their website to see what they offer, and make our own decision on whether to use it or not.

If I want Resolve information, I know where to go. And while they are innovative, I come to the Vegas forum to see, read, learn, about Vegas.

Sorry, I too am tired of this comparison. I'm a "big boy" that could buy Resolve if I wanted to or download their free version if I wanted to. I've tried Resolve several times. It's just not for "me". If it's for someone in here, fine. But I tire hearing about it. There are those that use both, and yet, they aren't constantly posting "Look at this in Resolve!!!!!!".

Posting feature requests are fine by me. Posting that Premiere now has something "new", is of no interest to me...

If these features are so important to you, use them. Use the right hammer for the right nail.

Zuletzt geändert von Reyfox am 14.11.2020, 14:15, insgesamt 1-mal geändert.

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.2

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Howard-Vigorita schrieb am 14.11.2020 um 19:10 Uhr

@lenard thanks for doing that. It shows that the pay version of Resolve Studio can be a credible performer. Which quite frankly I doubted given the mediocre performance of the free version. I've only ever used the free version for color tweaking in the last few years since Vegas began supporting luts. But not so much since the Vegas color panel appeared in v17. And even less with v18 thanks to its better levels options.

If anyone's curious why I even care about Resolve anymore, what I actually want to know is if Vegas has any measurable room for improving rendering performance. Resolve rendering faster on a similar project would confirm that. I hear allot of harping round here about how poor Vegas performs compared to competitors but I'd hate to see the Magix team spinning their wheels on a dead end road if that's not actually the case. Thanks to the constructive input from @lenard it appears there might be something there. Maybe I'll even spring for Resolve Studio myself just to see if I can hone in on any specific sticking points, like luts or particular gpus. What I'd ultimately like to see is Vegas performance so fantastic that Magix is proud to author and publish its own cross-platform benchmarks. Personally, I look at Resolve's convoluted user interface and cannot fathom how anyone could be such a glutton for punishment to use it for their workflow or get their deliverables out on time. Rendering speed being dwarfed by edit time and effort.

lenard schrieb am 15.11.2020 um 00:05 Uhr

 Personally, I look at Resolve's convoluted user interface and cannot fathom how anyone could be such a glutton for punishment to use it for their workflow or get their deliverables out on time. Rendering speed being dwarfed by edit time and effort.

Exactly this!, Dexcon that's why I try not to use Resolve as much as possible, they did improve user ability slightly in v17, it is the first beta though and I had a crash yesterday, something that doesn't happen with V16 on a day to day basis, so currently less stable

What I found really interesting is how your hardware encode on Vegas was so much faster than mine. You have a much faster cpu and gpu, but CPU and GPU according to task manager neither were a problem as far as excess loading, certainly not GPU, my CPU did get a maximum load of 76% so I thought I would be getting the fastest hardware encoding possible as such a load did not seem like a bottleneck to me yet your computer encoded in 30 seconds and mine 43 which is a huge difference. I did not check each core to see if 1 was at 100%, but that could be the problem, or Vegas really does like IPC/frequency over lower frequency multiple cores