No one seems to be talking about [how weak VEGAS is]

NeverUsingThisAgain wrote on 6/30/2018, 2:19 AM

UPDATE: I found out that overloading the preview with almost any plug-in can make the program crash. Absolutely pathetic. I'm going back to Sony Vegas Pro 13, no questions asked. It's funny how a version of Vegas Pro from 2014 is more operable than a modern, sleek-looking version. Still posting this for anyone who can be bothered by this.

 

UPDATE UPDATE: I can't believe this is considered a professional product. It used to be.

 

So, I'll do the honors.

 

I used to have Sony Vegas Pro 13 on my computer and it worked like a charm. 99.999% did not crash when I tried to overload source material with Sony Vegas plug-ins. I was editing a Fortnite montage one day, and some day after that, my computer was hard locked. I could not access the desktop upon booting, it would constantly get to a black screen, so I resorted to resetting my PC and re-downloading all the major apps I use for on-time creativity. Instead of downloading Sony Vegas Pro 13, I went to download VEGAS Pro 15, assuming that it would be a better option because of it's "higher number" or "newer version." I went to open my old, saved version of this Fortnite montage to open it, go through the material and see what was up. In specific areas of this project, I added in the "VEGAS Bump Map" plug-in. Apparently, when you try to put the sliders on this plugin in the very center, with the source video lasting for 90 milliseconds, in a video intended to render in 1920 x 1080 x 32 (whatever 32 is, idk) in 60 FPS, with the preview in 480 x 270 x 32 in 60 fps, VEGAS will crash. I don't think my hardware is to blame, but I will put my specs here just in case. I am running on a 64 bit Alienware laptop with a GeForce GTX 965M graphics card, 7.87 GB of RAM, and my processor's an Intel Core i5-6300HQ CPU @ 2.30GHz. I blame Magix for buying the VEGAS property and ******* up the way VEGAS processes Bump Map.

 

My first and only solution that I have thought up of myself is to uninstall VEGAS 15 and install Sony Vegas 13 so I can run on something that can handle a plug-in for it's own product. Make me think otherwise. I apologize for being so angry at 9 past midnight.

 

Is anyone out there?

Comments

Trensharo wrote on 6/30/2018, 3:10 AM

The moderators tend to come down hard on these topics. Your fine is rather provkcative, as well... Not very well stated, IMHO.

Vegas was Pro .It used to have the best Audio capabilities in the NLE market .Decent Plug-Ins bundled. It did some compositing stuff well.

But, Sony let this application whither on a vine while the competition surpassed them.

vkmast wrote on 6/30/2018, 3:22 AM

I don't think deleting one word (and hiding 6 multiple posts) according to the Community rules was "coming down hard" in this instance. And the OP was not fined, provocatively or at all. Or did you mean to say "whine".

OldSmoke wrote on 6/30/2018, 3:24 AM

I blame Magix for buying the VEGAS property and ******* up the way VEGAS processes Bump Map.

I blame your hardware and drivers for it. It works fine even on my oldest machine, an Intel Q6600 with a GTX580 which is fully loaded during preview at Full/Best and much better than VP12, and VP11 which are on the same machine.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

dream wrote on 6/30/2018, 4:15 AM

man i have i7 4700hq with 860m works fine on 13,14,15

fr0sty wrote on 6/30/2018, 5:07 AM

I wouldn't go saying software isn't built for professionals when you say things like "whatever 32 is, idk"... I imagine you're anxious to get this video game clip uploaded to your youtube channel, but you'll find you get a lot farther around here by showing a little respect. Just because your particular hardware and driver configuration caused a crash on one particular, rarely used plugin, does not warrant your whiny rant and repeated duplicate posts.

So what has changed about the bump map plugin from V12? GPU acceleration has been added since then, and Bump Map was one of the plugins that got the acceleration, so let's start there. Go into preferences and disable timeline GPU acceleration under the video tab. See if that fixes your problem. If so, try to re-enable it after updating your GPU drivers. If that still doesn't fix it, leave GPU acceleration disabled.

If that fails, post your media info, GPU driver version, and project settings. If you can, upload the media and project file for us to try to replicate it.

If that still doesn't work, (assuming you didn't pirate it), file a support ticket. Magix would be glad to help. Last time I had a bug that stopped me from finishing a project, they'd patched it in a matter of weeks and the community had helped me to find a workaround that got me through.

Last changed by fr0sty on 6/30/2018, 5:23 AM, changed a total of 4 times.

Systems:

Desktop

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

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

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

Musicvid wrote on 6/30/2018, 10:26 AM

'Tis a poor workman who blames his tools.

Kinvermark wrote on 6/30/2018, 10:42 AM

Don't even bother to try to sort this guy's problems out. This is simply attention-seeking forum pollution. Should be deleted as gross misrepresentation.

Grazie wrote on 6/30/2018, 11:17 AM

Back in the day, with SoFo and then SONY on these forums, we had that IGNORE USER Button. I want it back.

Nostalgia, it’s not what it used to be.

vkmast wrote on 6/30/2018, 12:01 PM

@Grazie so you still would prefer this to this? 😎

Kinvermark wrote on 6/30/2018, 12:01 PM

Nostalgia, it’s not what it used to be.

very funny 😂

 

Grazie wrote on 6/30/2018, 1:33 PM

@vkmast Yes

Kinvermark. I thank you. And I’m here nightly till July.

Trensharo wrote on 6/30/2018, 2:26 PM

Fined should be "post." The auto correct on this device is terrible.

And the MODs tend to complain about negative posts, calling them provocative and disruptive.

I can dig up Many examples, but search works if you just plug in some of the terms used ;-)

Trensharo wrote on 6/30/2018, 2:37 PM

I blame Magix for buying the VEGAS property and ******* up the way VEGAS processes Bump Map.

I blame your hardware and drivers for it. It works fine even on my oldest machine, an Intel Q6600 with a GTX580 which is fully loaded during preview at Full/Best and much better than VP12, and VP11 which are on the same machine.

I get hardware Accelerated Encoding in V14 for H.264 on my AMD A10-5745M Laptop from 2013 - using legacy GPU Rendering. On top of that, it improves timeline performance quite a bit.

And Nothing on my i7-7700HQ + GTX 1050Ti laptop bought last October. I can't even adjust effects properly if I use the GTX card. Same issue in Vegas 15 (tried a Trial). So I have to keep the Intel 630 graphics selected in settings. However, performance comparisons tell me that it isn't even using that. Just the CPU. It simply doesn't bug out when I haven't had enabked, as it does with the GTX card. Vegas 15 has the same issue.I

My GPUs are practically worthless when using this software, and it's not a driver issue.

NVenc isn't very useful. I need better timeline performance. Rendering videos is largely a passive task. Can do That while I eat dinner, or sleep, even, with the machine set to shut down when completed.

Turning off GPU Acceleration defeats the point. GPU driver updates are usually a non-factor as AMD/Nvidia have made this trivial to manage. My drivers are updated immediately after I get the update available notification from GeForce Experience. I check the OEM website weekly for driver updates for my model. With a fast CPU and NVMe storage, the whole thing takes < 5 minutes and you don't even have to reboot.

Also, most Pro Apps have guidance for choosing hardware to run the software optimally. Premiere Pro, Avid, Resolve, Edius, etc. Are all transparent about this. Vegas is an outlier. We should not have to play Russian Roulette with components, or entire machines (those of us who use notebooks).

I'm not going to edit on an Ancient CPU or use an Ancient GPU in a desktop, because that will bottleneck all other software that can benefit from better CPU or GPU. This is a complete non solution.

Better guidance (or any at all, direct from the developers) is needed.

I don't understand why discussing been remedied.

P.S. It's trivial to rip all of the new OFX from Vegas 15 and install them into 14. They are not much of a noticeable improvement (if at all) when the GPU Acceleration in the NLE is completely broken or dysfunctional ;-)

zdogg wrote on 6/30/2018, 9:59 PM

Have you checked for viruses? I recommend Spybot, (oldie and still goodie) and the other usual suspect -adaware, etc., I like to use at least two sequentially when I suspect a bug of some sort. Worth looking into, also, I don't have Win 10, I stick with Win 7 because it is familiar and works, and we can do a write-over fresh install, which leaves files and programs intact - that in conjunction with re-install of Veg15. (maybe you did that already, that is really the FIRST thing to try, uninstall first) Maybe a "write over" install not an option on Win 10, I just don't know -- but some sort of clean install might just be what you'd have to do here, I'd hope not, but you can't leave it out as a fix option/opportunity.