Well, we are not the makers craneman, We cannot fix it for you! We are all equal end users just like you, trying to assist with the knowledge we have why Vegas Pro 18 works well for us..... So if you shoot down everything we suggest for you to try, then this thread is pointless and going nowhere.

1. If you read what I have actually said, I have not asked the community to fix anything. I have shared my experience. Walter-i enjoys some mild trolling, but there is no value in his comments in this post.
2. I did not 'shoot down everything'. Again, if you take the trouble to read what I have actually said, I have tried the suggestions initially made by RogerS here, and by others elsewhere in these forums.
3. I think it is clear enough that the import media is not the cause my problem based on my reports above so I don't see any point in wasting my time or the time of others on it, even if kindly offered.

I do appreciate that some have a short attention span or aren't concerned to read fully to understand an issue, but that's no excuse to jump to the wrong conclusion and attack the individual.

I am happy that your experience with V18 is good. Mine is not, and attacking me for it won't make V18 work better at my end.

As I wrote above I use the Dell XPS 15 with the i7-7700HQ, 32GB ram and GTX 1050. VP 18 performs better than 15 at this point, with the media and types of edits I do.

So there must be some other variable causing issues on your system rather than a fundamental flaw in the software. The test I proposed was to help identify what the variable might be.

(I don't use proxies for editing 4K media generally)

Thank you, but given the same media and project performs slower for me in V18 than in V15, I discount that as the issue. I think you are right that something else is causing sluggish performance for me in V18 on basic editing and loading tasks. I can't imagine it affects everyone as I am sure it would be deemed unacceptable, but as it stands V18 is a failed upgrade for me.

The performance issue here seems to be typified by the amount of CPU V18 is using just to make the most simple editing action of positioning the cursor at a different point on the timeline. Is it possible you could use Task manager please, and see if that occurs when you are editing?

It would be easier to have a sample project to test, not because I think the project or clips are the problem (I do not) but because it would be easier to compare performance apples to apples.

So for a 4K timeline with 2 4K 24p clips, while not playing back I get 5% and it spikes to around 12% when I click somewhere on the timeline.

While playing back it averages ~47% CPU usage and that spikes up to around 53% while playing back (a bit higher the first time).

This is X-AVC S footage that works with the Intel GPU decoder.

In VP 15, same timeline and clips, base usage is around 5% CPU and it spikes to 35-40% when I click around the timeline. No GPU decoding activity.

In VP 15 while playing back average CPU usage of 67% while playing back. Spikes up to 76% while clicking around the timeline, though it varies. No GPU decoding.

Well, we are not the makers craneman, We cannot fix it for you! We are all equal end users just like you, trying to assist with the knowledge we have why Vegas Pro 18 works well for us..... So if you shoot down everything we suggest for you to try, then this thread is pointless and going nowhere.

 

1. If you read what I have actually said, I have not asked the community to fix anything. I have shared my experience. Walter-i enjoys some mild trolling, but there is no value in his comments in this post.
2. I did not 'shoot down everything'. Again, if you take the trouble to read what I have actually said, I have tried the suggestions initially made by RogerS here, and by others elsewhere in these forums.
3. I think it is clear enough that the import media is not the cause my problem based on my reports above so I don't see any point in wasting my time or the time of others on it, even if kindly offered.

I do appreciate that some have a short attention span or aren't concerned to read fully to understand an issue, but that's no excuse to jump to the wrong conclusion and attack the individual.

I am happy that your experience with V18 is good. Mine is not, and attacking me for it won't make V18 work better at my end.

It's not short attention span it just dealing with individuals who don't understand the tools they use. You know what they say about repeating the same thing over and over and getting the same results. People are just trying to help you understand why you are not getting the results you want.

 

It's not short attention span it just dealing with individuals who don't understand the tools they use. You know what they say about repeating the same thing over and over and getting the same results. People are just trying to help you understand why you are not getting the results you want.

Thank you. My response was replying to the comment that I 'shoot everything down', which was just a lazy opinion which can be disregarded by reading the whole thread.

As for "dealing with individuals who don't understand the tools they use", I have been using Vegas since V12 so I have enough experience under my belt. But actually I said in my opening post that I was a long time user, so it seems your comment is another for the lazy opinion category.

Actually again, if you made the effort to read through the post you will see I have said thank you for the help. In particularly to RogerS, who it is clear is trying to help. Others like you, are making a comment that adds nothing useful to anyone.

It would be easier to have a sample project to test, not because I think the project or clips are the problem (I do not) but because it would be easier to compare performance apples to apples.

So for a 4K timeline with 2 4K 24p clips, while not playing back I get 5% and it spikes to around 12% when I click somewhere on the timeline.

While playing back it averages ~47% CPU usage and that spikes up to around 53% while playing back (a bit higher the first time).

This is X-AVC S footage that works with the Intel GPU decoder.

In VP 15, same timeline and clips, base usage is around 5% CPU and it spikes to 35-40% when I click around the timeline. No GPU decoding activity.

In VP 15 while playing back average CPU usage of 67% while playing back. Spikes up to 76% while clicking around the timeline, though it varies. No GPU decoding.

Thank you for this. I will run some more checks for comparison.

And about RAM and how it affects the performance of Vegas 18.

Here is a video testing the results of adding more RAM to your computer.

That's correct caneman, i have a very lazy opinion about you.... Your responses have proven that my conclusions are actually 100% accurate my friend!

Thank you for confirming your opinion is lazy. I appreciate your acknowledgement.

C'mon guys, insulting one another doesn't help anybody.

Craneman, if you want my attention going forward, please use @ to tag me as otherwise I may miss it.