VEGAS Pro 15 Update 3 (build 311) - General Discussion


Reyfox wrote on 5/21/2018, 5:28 AM

@Lukasz I thought you can download VP15 to test and see if it's good for "you". I don't edit anything as long as 3 hours, but certainly, way more than 2 minutes.

Lukasz wrote on 5/21/2018, 9:09 AM

I did not quite understand you. But for me, 2 minutes with so many problems as vegas is not enough. I do not buy a cat in a bag anymore :)

Wolfgang S. wrote on 5/21/2018, 9:44 AM

There is nothing blocked for projects longer then two minutes, also not in the trial. And as mentioned by Gary, another free update is foreseen for Vegas Pro 15.

Last changed by Wolfgang S. on 5/21/2018, 9:44 AM, changed a total of 1 times.

Desktop: PC AMD 3960X, 24x3,8 Mhz * GTX 3080 Ti * Blackmagic Extreme 4K 12G * Atomos Sumo * QNAP Max8 10 Gb Lan * Blackmagic Pocket 6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED (ProArt Studiobook 16 OLED (i9 12900H with i-GPU Iris XE, 32 GB Ram. Geforce RTX 3070 TI 8GB) with internal HDR preview on the laptop monitor
HDR monitor: ProArt Monitor PA32 UCG

vkmast wrote on 5/21/2018, 10:31 AM

@Wolfgang S. has this (reported often on the forum) been changed now?

Kinvermark wrote on 5/21/2018, 11:26 AM

Clearly some confusion between project length and render time limits; certainly you can load large projects into the v15 trial (I have opened very complex 30 minute timelines for example). Working with a large project and limited render time should still give you a pretty accurate picture of performance on your system.

fr0sty wrote on 5/21/2018, 12:38 PM

Magix (very wisely) put a render time limit on the demo version of Vegas to stop users like the one vkmast linked to, who like to try to exploit the system that we all pay good money to exist by making new accounts to get new demo versions of the software, so they can edit for free.

I regularly edit 2-3 hour projects in Vegas 15. 15 has no more bugs than any previous version did, in fact many of the most annoying bugs from 14 got fixed, even if a few new ones got introduced with some of the new features.

As someone who has been using Vegas 15 since launch day, I can confirm beyond a shadow of a doubt that Magix isn't "hiding something" with the 2 minute render time limit. They're just trying to keep from getting ripped off by people not willing to pay for their product. This is especially troublesome when there are an ever-increasing number of free and open-source editing apps out there that will do the same thing without ripping off someone who is trying to make a living.

Last changed by fr0sty on 5/21/2018, 12:38 PM, changed a total of 1 times.



AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10


ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Reyfox wrote on 5/21/2018, 12:42 PM

@frosty I didn't know there was an imposed render limit on the trial software, considering I never went that route. I bought VP14Edit, then upgraded to VP15 Suite.

There are always people looking for a "free ride", so understand it completely, the limit of 2 minutes.

Last changed by Reyfox on 5/21/2018, 12:47 PM, changed a total of 1 times.


Vegas Post 365 (Currently VP21)

Win 11 Pro

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 22.5.1, testing 23.11.1

Gigabyte X570 Elite Motherboard

fifonik wrote on 5/21/2018, 6:55 PM

... to exploit the system that we all pay good money

True. However, I payed quite big money to bought VP15 upgrade to get better preview frame rate. Still, I cannot use it normally (it is almost a year passed since it was released). My quite simple workflow that works fine in VP13 I own (as well as VP11 & 12) is broken in a number of ways so workarounds required and I'm not 100% sure that all these workaround works as I'm expecting.

So, I understand why some people do not want to spend money on such "upgrade".

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 5700X, RAM: G'Skill 16 GB DDR4@3200, Graphics card: MSI RX6600 8GB, SSD: Samsung 970 Evo+ 1TB (NVMe, OS), Samsung 870 Evo, HDD Seagate 3TB, HDD Toshiba 4TB, OS: Windows 10 Pro 22H2

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17, 18, 19

fr0sty wrote on 5/22/2018, 12:06 AM

I've had my fair share of hair-greying frustrations out of VP, trust me... but I still believe that if you are going to use it at all, pay for it, or use something that is free.

Lukasz wrote on 5/22/2018, 3:28 AM

Hello, this is not about using magix. This is about fully testing the product. Vegas has a time limit for tests and you can put a logo on the rendered image for this and that's enough security. Limiting the rendering to 2 minutes where I had many problems eg at 2 hours or at a different time interval for me, 2 min is some mockery. Nobody respects the project to the customer with the company logo as it was in the times of Sony Vegas.

Lukasz wrote on 5/22/2018, 3:33 AM

I will add that there are many ways to protect your work, but limiting the tests is not the right way. Vegas still has a bad patch so this type of practice does not bode well.

Kinvermark wrote on 5/22/2018, 11:57 AM

I suspect it has something to do with codec licensing. Vegas now licenses codecs as they get used, presumably so magix only pays royalties for those codecs a user actually uses. For the trial, it may be that a 2 minute limit satisfies the codec owners that no royalty is due.