FWIW, I installed 311 and just did a very simple project and it went smoothly.

I had X-AVC HD clips from two cameras displayed simultaneously with audio mixed in from 3 sources. The new (I think?) NVENC encoder chewed through 1.5 hours of footage in 45 minutes, which really impressed me. The description of it is mistaken though and says Intel quicksync.
Before I was using the Intel encoder which still works fine but is about 20-30% slower than my 1050 graphics card. The bug where generated text, etc. didn't show while the dialgo box was open with a Nvidia card enabled didn't appear this time, so maybe it is fixed. I also enabled socompound for the first time in Vegas Pro 15 and it seemed to function. So far so good and I'll try it with a more demanding project soon.

Just to add here I have the UI slowdown as well (and it can lead to a complete hang of Vegas). And it is easy to reproduce and it does not need 4k source nor plugins to get in this state.

Just drag a few clips (4 will do, 50p full HD XAVC-S) on the timeline have some gap between them, overlap 2 of them, open /close event pan crop a first time to observe initial opening speed.

Next Play a bit with track height via expand track layers, press keypad 5 a few times, zoom in track height slider (bottom right) a few times, goof around a bit, and then open close event pan/crop. You see the difference in opening speed from the first time. With some luck you can slow down the UI in minutes ...

Thanks for confirmating it’s a UI bug, versus what’s on he timeline or how fast your PC is. I reported this back last September, but now that more users are confirming it, maybe it will get fixed.

Just so you all know that the problems with the slowdown are not falling on deaf ears, we on the VEGAS team are trying very hard to uncover this slow down some of you are seeing in VEGAS 15. The main reason we have not been able to remedy this is mainly because we are having a difficult time reproducing the issue here. I would like to thank all the people who have posted details about what specifically they are seeing and what they are doing to reproduce the problem. The more specific details we get, the more likely we will be able to narrow down the cause of this problem. It is my hope that we will be able to find a solution to this problem in the near future.

I reported this test with build 261 for debugging. Win7, AMD and Intel Graphic.

If I close all the windows except for the timeline and then call the default window layout again, everything goes back to normal speed. As a workaround, I have created a window layout "GUI Reset", which contains only the timeline. Partially, this trick leads to a crash.

I hope this helps.

@MagixDerek THANK YOU!!!
Here is detailed a list of what always reproduces it for me:

1. Windows 10 new install last August on new PC, updated to current level.
2. Has happened on the 15 base, 216, 261 and 311 builds.
3. Editing 4 to 6 video tracks in multicam mode. Probably in other cases, but this is my normal case.
4. Example from 2 days ago on 331, I was able to make about 30 cuts and use pan/crop tool to create motion with usually just the beginning and an ending keyframe on each event(a.k.a take).
5. Usually added a crossfade.
6. I made the cuts first, and no slow down until I went back and did the pan/crop.
7. I usually leave pan/crop window open and just click on the next event - versus closing it after each event.
8. I go back and forth frequently between showing all tracks, to showing just the selected track.
9. Switch between Preview Full showing all tracks, and Best Full showing just selected track.
10. No external monitor/tv, just 2 HD0180 monitors.
11. I'm using 2 HD0180 monitors, but I think i happened back when I only used one, too.
12. Slow down is most noticable in pan/crop window being slow to open, but moving the crop window around is also very slow, and even moving to a new point on the timeline.
13. Hardware probably doesn't matter, but it's Threaddripper 1950x, Fury x, 500GB m.2, 16GB RAM.
14. Not a lot of other software on this PC, but Vegas 13 is there.
15. And I have that plugin where you can select Orig/PC/TV mode in the preview window, and an extra detailed progress window when rendering. Sorry, I'm not at the PC to give exact software name. But it is also used by version 13 which doesn't have the problem.
16. I doubt the media type matters, but it's a mix of HD1080 and 4k .MP4 and Canon (.mts) from prosumer cameras. The total size varies from 5 min to 2 hours. Length of video and number of tracks doesn't seem to make it happen faster/slower. Seems related to how often a pan/crop or fx window is used.
17. I don't see a huge change in memory used.

Hope this helps.

Richard

Thanks for working on the GUI issue. I had made/posted a video comparison w/ the last build & V14 (Reattached). NVidia 960gtx, Windows 10 (Fall Creators and previous), 16gb Ram, SSD/7200HD.

It's the same in build 311 from a quick run through I gave it the other day in my office.

Has this been addressed in the new release?

[VP15,14] Paste Event Attributes wrongly adjusts Pan/Crop settings.

I updated to build 311 and as a test for a problem in another forum, I had Vegasaur do a background render based on 19 minute regions to create a five part 1080P video segments for SmugMug (they limit video to 20min). Anyway, it rendered the ~1.5h of soccer video with Boris Title Studio intro and some tracks to display the game time and current score for a little over 3h with no crashes. I acknowledge this did not involve any real editting other than trimming the beginning and end of the video, since the coach uses this for game analysis. It also is not 4K and I used MainConcept with no GPU.

So far so good for my use case on this build. I will start my next project with this build since the deadline is a month from now. I'm definitely not going to Premier Pro as I just ditched Lightroom after several years as a customer and the last few as a cc photography plan customer. I really did not appreciate the doubling of my subscription and splitting the feature set with the new Lightroom and classic Lightroom.

I updated to build 311 and as a test for a problem in another forum, I had Vegasaur do a background render based on 19 minute regions to create a five part 1080P video segments for SmugMug (they limit video to 20min). Anyway, it rendered the ~1.5h of soccer video with Boris Title Studio intro and some tracks to display the game time and current score for a little over 3h with no crashes. I acknowledge this did not involve any real editting other than trimming the beginning and end of the video, since the coach uses this for game analysis. It also is not 4K and I used MainConcept with no GPU.

So far so good for my use case on this build. I will start my next project with this build since the deadline is a month from now. I'm definitely not going to Premier Pro as I just ditched Lightroom after several years as a customer and the last few as a cc photography plan customer. I really did not appreciate the doubling of my subscription and splitting the feature set with the new Lightroom and classic Lightroom.

I rendered to a single file with the Magix AVC with NVENC Internet HD 1080 29.97 and the GPU utilization stayed around 24% on the GTX 970. The render completed in less than half the time at 1h 19min.

Just so you all know that the problems with the slowdown are not falling on deaf ears, we on the VEGAS team are trying very hard to uncover this slow down some of you are seeing in VEGAS 15. The main reason we have not been able to remedy this is mainly because we are having a difficult time reproducing the issue here.

Maybe you can invite the people in this forum to your beta testing programme that are passionately telling you about the bugs they are seeing . It seems like the current group of people aren't very good at noticing these things

The description of it is mistaken though and says Intel quicksync.

Which description and where do you see that description?

When you go to file/render as, each option has "template info" describing the template. Under Magix AVC there is a HD NVENC setting 1080p 24 fps.

The text states "Use this setting to create an MP4 (AVC/AAC) file for progressive internet downloads using Intel QSV encoder.
Audio: 192 Kbps, 48,000 Hz, 16 Bit, Stereo, AAC
Video: 23.976 fps, 1920x1080 Progressive, YUV, 18 Mbps"

The text for the actual Intel one states:
"Use this setting to create an MP4 (AVC/AAC) file for progressive internet downloads using Intel QSV encoder.
Audio: 192 Kbps, 48,000 Hz, 16 Bit, Stereo, AAC
Video: 23.976 fps, 1920x1080 Progressive, YUV, 18 Mbps"

If you click on the setting you can edit the note where this description resides. I assume it's just an oversight on Magix's part.

Has this been addressed in the new release?

[VP15,14] Paste Event Attributes wrongly adjusts Pan/Crop settings.

No

If you first import XAVC-S videos with the So4 Compound plugin disabled, you will get to see Time Code In/Out.
 

Re-tested, TRUE.

Meaning, So4compoundplug.dll still has a BUG reading timecode correctly from XAVC-S files. Thanks for picking this up @Dr Zen!

Have been poking my finger into the shifted-preferences..saw this:

Tried to change 'Autocalculate Video Memory 64Bit' to TRUE but it doesn't stick, whatever graphics card (or none) I have selected..including nVidia GTX1060..

Have also noticed VP/64bit memory is restricted to 1024 Byte (search: mem); allocating 2048 has made no difference it seems, same with open CL memory..is this all only future music?? does someone know if this should work (ie. is it broken?) or what stops Vegas using system resources effectively?

Uhm.. anyone noticed a video/audio desync with Magix AVC/AAC MP4 Nvidia NVENC renderer since last update ? i am still processing same geforce experience share (shadowplay) 1080p/60fps/50Mbit to 1440p/60fps/24Mbit but with so4 enabled (previous version was disabled) and i am noticing a clear desync in output files..

Later edit: just disabled this monstruous so4 thingie and everything seems working great in sync again.. what is going on with the development..

I have just tested build 311 and it is quite disappointing.

First of all, Magix seems to act just like Sony... both have forgotten for ages to update the GPU support. No matter how much the users ask you to do it, you just keep on ignoring like we are invisible. Thank you! :D

Second of all, so4compound fix is not such a good fix after all... LOAD TIMES, PREV. PERFOMANCE(both in trimmer and in timeline) ar still very, very, very bad compared to how it all works with so4compound disabled from internal menul. When you disable so4... everything works tens of times faster and sharper.

Sorry magix, but you are not doing such a good job as expected. Also it woud be better if you woud listen to our requirements from time to time.

ps. vegas is extremely unstable with gpu acceleration ON..... for the love of listening to us.... please fix it... it's been years we've asked you this....

Just so you all know that the problems with the slowdown are not falling on deaf ears, we on the VEGAS team are trying very hard to uncover this slow down some of you are seeing in VEGAS 15. The main reason we have not been able to remedy this is mainly because we are having a difficult time reproducing the issue here. I would like to thank all the people who have posted details about what specifically they are seeing and what they are doing to reproduce the problem. The more specific details we get, the more likely we will be able to narrow down the cause of this problem. It is my hope that we will be able to find a solution to this problem in the near future.

How to reproduce the perfomance problem... sluggish perfomance ON/OFF steps:

1. test with about 200gb of DSLR/MIRORLESS footage imported in youd media bins

1. disable so4compoundplug from internal menu an restart vegas -> now everthing is lightning fast, project loading time is a split second, trimmer and timeline playback perfomance is beautifull and thumbnails on your 'media bins' folders update in a blink of an eye.

2. enable so4compoundplug from internal menu and restart vegas -> now everthing i was talking before works tens times worst. Vegas becomes a very slow and hard to work with NLE.

So, vegas is awesome first of all because is fast....so4 makes it dead slow....If i wasn't able to disable so4compoundplug i woud have quit vegas and go for another nle. And trust me i love vegas and i edit in vegas for a very long time.

Just so you all know that the problems with the slowdown are not falling on deaf ears, we on the VEGAS team are trying very hard to uncover this slow down some of you are seeing in VEGAS 15. The main reason we have not been able to remedy this is mainly because we are having a difficult time reproducing the issue here. I would like to thank all the people who have posted details about what specifically they are seeing and what they are doing to reproduce the problem. The more specific details we get, the more likely we will be able to narrow down the cause of this problem. It is my hope that we will be able to find a solution to this problem in the near future.

How to reproduce the perfomance problem... sluggish perfomance ON/OFF steps:

1. test with about 200gb of DSLR/MIRORLESS footage imported in youd media bins

1. disable so4compoundplug from internal menu an restart vegas -> now everthing is lightning fast, project loading time is a split second, trimmer and timeline playback perfomance is beautifull and thumbnails on your 'media bins' folders update in a blink of an eye.

2. enable so4compoundplug from internal menu and restart vegas -> now everthing i was talking before works tens times worst. Vegas becomes a very slow and hard to work with NLE.

 

So, vegas is awesome first of all because is fast....so4 makes it dead slow....If i wasn't able to disable so4compoundplug i woud have quit vegas and go for another nle. And trust me i love vegas and i edit in vegas for a very long time.

 

For me, it's even with so4 disabled deadly slow :).

Just so you all know that the problems with the slowdown are not falling on deaf ears, we on the VEGAS team are trying very hard to uncover this slow down some of you are seeing in VEGAS 15. The main reason we have not been able to remedy this is mainly because we are having a difficult time reproducing the issue here.

Maybe you can invite the people in this forum to your beta testing programme that are passionately telling you about the bugs they are seeing . It seems like the current group of people aren't very good at noticing these things

+1 bob-h for the expanded Beta process.
In this era of ever-increasing complexity, I am sure Vegas' development team will benefit with increased assistance by the actual users. Possibly a private-forum based solution, akin to Ableton Beta system.
And as forums sometimes could be optimized, why not use a tree model with a few big branches (like WIN or Mac), depending on relevant criteria.

Let's have in context that only a few years ago, developers didn't need to juggle with CPU core optimization, GPU acceleration, drivers handling diverse functions, HDR and a plethora of formats (+cameras from competing vendors), changing CODECs either for imagen, audio and of course video. All at varying frequencies, frames and bits, real-time available for a multilevel grid of VSTs mapped on a timeline. Where each effect needs the possibility to demand memory access. Of course, these while managing the usual player, presets, edition, rendering, etc functions from an editor like this.

Not an easy act, particularly if it has to work IN MOST customers rigs.For a large customer base (that posts in this forum every hour, every day!) that has to be challenge.
///So a word of acknowledgement; this community is valuable, as is this responsive forum plus the open and receptive team of developers.
We didn't have that two years ago. This communication is good and we seem to need more.


 

+1 for Beta access.

And to the moderators and Magix crew, keep up your good work, even though praise is sometimes hard to find and the road ahead seems pretty tough. This is a great forum (unlike the Sony one where you can never find anyone Sony there, and moderators at best provide lipservice) and a great source of information. There's a lot of dedicated professionals here who are willing to collaborate to improve the development speed and bug hunting ;-). In the spirit of improvement

I was in the middle of a large project on build 261 with SO4 disabled. Lots of Panasonic and Canon footage. It crashed every hour or so but I was used to Ctrl+S every few minutes so I could live with that happily. But after updating to 311 no matter SO4 disabled or enabled, when I hit Ctrl+S and instantly continue to edit and moving events, everything from Preview to playback becomes too laggy and unusable.

I found that it is related to Magic Bullet Looks plugin. when I disable the FX, the playback is normal again. I hadn't have this problem in 261. in 311 this occurs when hitting Ctr+S or importing a new footage to the timeline and will not come back to normal until I restart Vegas.

Win10 latest Update - i7 7700k - 980GTX TI - 32G Ram - All footage on SSD