VP17 and a lot of major bugs. Like every year

pierre-k wrote on 8/10/2019, 6:13 AM

It's the same every year. The first version and we are betatesters!

1. Event-level stabilization often does not work with GTX970. Black screen and flicker. Cannot use rendering. Frequent freezing of Vegas. Collapse.

Works when GPU is turned off.

2. SlowMotion does not work with GTX970. Black screen. Occasionally low GPU memory alert. Cannot use rendering. Frequent freezing of Vegas. Collapse.

When you turn off the GPU it works, but it does not work properly. The video is full of artifacts, pixels and strange cubes. If I cut the video somewhere, the whole thing shifts nonsensically and continues from another part. When using SlowMotion FX, I cannot use Dynamic Ram Preview for any other events. The selected part disappears when in use.

SlowMotion must be analyzed before use. Waste of time. This effect must work realtime as Twixtor.
Must be automatic for Velocity and TimeStretch with CTRL key.

Solution:

3. Loading project with lots of files is slow. We know about this bug.

4. Screen Capture does not save the recorded video. The file .vegcap has 1,5kb
Features window is not nice, it looks amateur. Why is the program missing a captured playlist? I could drag them to Timeline in Vegas. Without Import.

For several years I have been sending and publishing suggestions for improvement. Without any results.

How many users wanted Screen Capture?
And how many users want stable software?

Sorry my English

My pc:
Win 10 Pro 1903
Intel Xeon cpu e3-1231 v3 3.40GB
Ram 16GB
GTX 970 - drivers Game 431.60. Studio Drivers not Support for this GPU

Comments

Marco. wrote on 8/10/2019, 6:22 AM

"4. Screen Capture does not save the recorded video. The file .vegcap has 1,5kb"

The file *.vegcap is not the recorded media file but a metadata file only. Your recorded clips will be found at:

C:\Users\user name\Captures\

pierre-k wrote on 8/10/2019, 6:35 AM

"4. Screen Capture does not save the recorded video. The file .vegcap has 1,5kb"

The file *.vegcap is not the recorded media file but a metadata file only. Your recorded clips will be found at:

C:\Users\user name\Captures\

Thanks Marco. You're right.
This method is confusing for the ordinary user. What is the export button for? The program is missing the option to select a folder and playlist.

Marco. wrote on 8/10/2019, 6:46 AM

I think that *.vegcap file is meant for a simplified re-import of screenrecordings into Vegas Pro. But it does not yet work.

While there is not yet a way to set the path to the recording folder inside the tool's GUI, you could set your own path by modifying the file config.json which is in C:\Users\username\.VEGAS Capture.

I'm sure this screencapture tool will improve a lot soon.

D7K wrote on 8/10/2019, 8:46 AM

"4. Screen Capture does not save the recorded video. The file .vegcap has 1,5kb"

The file *.vegcap is not the recorded media file but a metadata file only. Your recorded clips will be found at:

C:\Users\user name\Captures\

Only if you are one of the lucky ones Marco. I have put in a support request with the details of my Desktop and Laptop because it writes the *.vegcap and nothing else. And like all releases we should just note the issues so they can be fixed. However some folks are not adult enough or had enough experience with Magix to know that they will work to get the bugs squashed but it takes time. I'm never sure if some of the posts sound the way they do because of translation or that people just need to grow up.

I also notice that because I get a black screen in the video section of screen capture it writes a video file that is always the same size and does not open in VP17 (on both of my computers).

Marco. wrote on 8/10/2019, 11:10 AM

There may be cases where the folder "Captures" did not autocreate. So see if such a folder exists at C:\Users\user name\. If not, create yourself.

fr0sty wrote on 8/10/2019, 3:19 PM

Pierre, are you using the latest Nvidia studio driver?

pierre-k wrote on 8/10/2019, 3:37 PM

Pierre, are you using the latest Nvidia studio driver?

I use Game drivers 431.60. Studio Drivers not Support for this GPU

Timo-Mank wrote on 11/21/2019, 2:57 AM

why is there a button to import the screen captures directly into the project... and why does it not work?

Rednroll wrote on 11/21/2019, 7:30 AM

Sorry my English

If your native speaking language is not English, then you are to be commended since your posts are always well laid out, concise and easy to understand. Native English speaking people could learn a lot from you. 😉

pierre-k wrote on 11/21/2019, 12:36 PM

google translator has improved a lot over the years 😂

fr0sty wrote on 11/21/2019, 3:01 PM

IIRC, GTX 970 does not meet the minimum system requirements for Vegas 17.

karma17 wrote on 11/22/2019, 2:37 PM

I agree. That tends to be the pattern, and maybe not the best one. I think for people who are familiar with the forum and how to use the program, it is an expected annoyance, and we watch as each consecutive build gets better hopefully. But for new users, I don't think it is so great because you buy a program, not really knowing anything about it, but expecting it to work as intended, and it doesn't, and I can see people getting bent out of shape about that. Maybe Vegas should start labeling the newest version as Beta, and drop the price until the 2nd or 3rd build, then drop beta and raise the price. At least that way, everyone knows what's going on.

j-v wrote on 11/22/2019, 3:16 PM

@karma17
Not true, it is the best version ever made,
I you want to complain about the program of which you use probably not use the right settings or not have the right specifications, go elswhere but don't annoy us with that.

karma17 wrote on 11/22/2019, 6:35 PM

I respectfully disagree. I think V17 is a great upgrade, but it does have bugs and it is not just a question of not having the right settings.

john_dennis wrote on 11/22/2019, 7:37 PM

[fact]

The list of bugs in Vegas Pro 17 is > 0.

UNOFFICIAL KNOWN ISSUES

[VP17+] FXHome FX from Ignite Pro 4.0 and earlier, Ignite Express, Hitfilm Movie Essentials and Hitfilm Boost Pack do not appear.

[VP17+] Planar tracking jitter.

[VP17+] Multiple Screen Capture issues including blank preview and 0 byte recorded files on some systems (post search).

[VP17+] Lossless UHD AVC or HEVC file rendered with NVENC is zero bytes (also).

[VP17?+] NVENC rendering on some systems gives low memory error unless Dynamic RAM Preview max is set to 0.

[VP17+] Parent project loses its audio master and bus FX when switching to a nested timeline.

[/fact]

Marco. wrote on 11/23/2019, 1:14 AM

The jitter issue of planar tracking is fixed meanwhile.

karma17 wrote on 11/23/2019, 2:26 AM

I posted a response to the OP not to be annoying, but because I love Vegas and want it to be successful. And I'm concerned about the bugs, not for me, but for new users of the program. I remember very clearly a well-respected long-term forum user on here expressed frustration with a new feature in V16 that did not work, and he expressed concern for how bad this looks for Vegas when they are selling a new version with a new feature and it isn't working properly. It doesn't take much empathy to see how someone might feel if they bought a program for a new feature and were then told it isn't working right now and to check back later for the next build. This has nothing to do with settings, but with bona fide glitches and bugs.

The crux of my "friendly" suggestion, as a fan of Vegas, is that perhaps they should put "BETA" on the release. That way, new users could understand that the program is under active development and everything might not be working 100%. If Magix wanted to adjust the price too, then that would be a bonus.

I'm sure people would appreciate the transparency of that.

This isn't an original idea.

Black Magic releases Resolve under Beta all the time. I think people do like getting their hands on the new features, but realize there's going to be issues. But that's fine because they know.

And this is all coming from a strong supporter of the program, not a detractor.

pierre-k wrote on 11/23/2019, 4:59 AM

I completely agree. for example, half a year before the release of Vegas 18, a beta version could be released that would only be sent to long-term users here on the forum. Vegas internal beta testers are not enough to detect all problems. we will be happy to help them free of charge.

j-v wrote on 11/23/2019, 5:41 AM

That idea is not new.
When Sony was still the owner a new version with a lot of changes has been offered as a public beta for users who want to help the developpers.
Vegas Pro 12 is an example

wwjd wrote on 11/23/2019, 9:50 AM

I completely agree. for example, half a year before the release of Vegas 18, a beta version could be released that would only be sent to long-term users here on the forum. Vegas internal beta testers are not enough to detect all problems. we will be happy to help them free of charge.

this. full functional free for select goup expiring in a few months, THEN if all the bugs are fixed for the updated release, a special discount for the testers

fr0sty wrote on 11/23/2019, 9:57 AM

How do you know they don't already do this?

As for wider reaching betas, gotta keep in mind a small team can only respond to so many beta bug reports at once, so it doesn't make sense to have hundreds of them coming in at once when they can whittle it down to a smaller group of people with a diverse hardware configuration among them. If you have a team of say, 10 people responding to emails from 100 beta testers each day, sometimes 2-3 (or more) e-mails per beta tester as they follow up on the bug, it makes it hard to get much done.