Nested Projects need processing

That's fine, then use my cpu power, not just 15% of it. Seems an unoptimized code here.

Is it the same with V16-17-18?

I use nested project very often and I do not see such degradation in VP18.

I tested your project.

Render time direct project: 9s

Render time nested: 8s

System in signature

About 2 months ago I carried out comparative tests for another thread that raised the same question and - like Illusion - did not come to any significant differences.

https://www.vegascreativesoftware.info/us/forum/vp18-nested-veg-render-any-faster-than-old-versions--124733/

The fault will be somewhere else.
Systematic search is the order of the day.

Now we’d need to compare PC power.

Walter, I did made the search, but only with google :) my bad

Illusion: thanks! So they fixed it sometime!!

With me on laptop and VPro 18
a 4K project with video, 2 T&T events and 1 still picture, lenght 83 sec., renders as project to FHD 50p with QSV in 96 sec.
The same project loaded as "nested" veg renders with the same rendertemplate as the former in 153 sec., a difference of 70 sec.

Hmm, interesting. So they fixed the issue or not? :)

Don't know, I never saw it as an issue while I for my own project always use "nested" vegs from the beginning of my use with version 10.

The issue:

"i7-2600 cpu"

With me on laptop and VPro 18
a 4K project with video, 2 T&T events and 1 still picture, lenght 83 sec., renders as project to FHD 50p with QSV in 96 sec.
The same project loaded as "nested" veg renders with the same rendertemplate as the former in 153 sec., a difference of 70 sec.

Did you try any non-QSV templates? What about CPU only?

john_dennis 

Really? Old yes, but why nested project use 15% while default project use 80%?

That's not the cpu fault.

With me on laptop and VPro 18
a 4K project with video, 2 T&T events and 1 still picture, lenght 83 sec., renders as project to FHD 50p with QSV in 96 sec.
The same project loaded as "nested" veg renders with the same rendertemplate as the former in 153 sec., a difference of 70 sec.

Did you try any non-QSV templates? What about CPU only?

Yess also with Nvenc the same 153 sec.
Don't know how I could use the Magix AVC rendertemplate for FHD to render with CPU only, but probably you know it. So please tell me.

"It will render in 0:56 sec to Full HD Sony AVC best quality template."

Other people here get 9 seconds. You're asking the system to do extra work, but not giving it any help. Is your source on SSD or NVMe drive? Nesting involves I/O from different parts of the dirive.

@RogerS
I am able to render it with the old Mainconcept codec, but that rendering take 2% of my Intel and 2% of the Nvidia so it is not CPU only. Rendertime is in that case 284 sec. and the rendered file takes a lot more space. What could be a gain?

"It will render in 0:56 sec to Full HD Sony AVC best quality template."

Other people here get 9 seconds. You're asking the system to do extra work, but not giving it any help. Is your source on SSD or NVMe drive? Nesting involves I/O from different parts of the dirive.

John, please read carefully my original post:

"a very simple project with one jpg"

Do you think does it matter if that jpg is on HDD, SSD or NVME in this case? No way..

Yes, other user with 6x faster cpu than mine, get 6x less render time. Simple math.
But slower cpu cannot be the reason why a nested project takes 3:12 and default 0:56.

Should be slow-slow (roughly equal time). A few percentage difference is acceptable but we talk here abour 3.5x rendertime increase..
Nested rendering work with only 15% cpu usage. You say, Vegas use less percentage with slower cpu? :)

@RogerS
I am able to render it with the old Mainconcept codec, but that rendering take 2% of my Intel and 2% of the Nvidia so it is not CPU only. Rendertime is in that case 284 sec. and the rendered file takes a lot more space. What could be a gain?

Hi J-v, just trying to minimize variables esp. with QSV.

So it came out to 284 seconds with Mainconcept whether nested or not?

2% Intel and Nvidia is CPU- they aren't doing any encoding but maybe are doing some decoding or processing Fx. File size should also depend on render settings. CPU encoding should be higher quality, though I haven't used Mainconcept in a while. (I'm using x.264 in Voukoder, though that's irrelevant for these purposes, we're just testing nested renders vs not nested).

So it came out to 284 seconds with Mainconcept whether nested or not?

Nested

@relaxvideo

Drive speed will probably not make much difference in this case. It does make a difference when the source clips are longer and more complex.

I get 8 seconds for the stoki.veg

and 9 seconds when nesting stoki.veg into another project with the 4 year old system from my signature in Vegas Pro 14.

I ignored Vegas 15-18 to keep GPU out of the equation. I also have useful work to do and have posted my last comment on this subject.

Unlike what some others have reported, I also found that nested projects were unacceptably slow. One commenter (sorry, don't remember who but I can search later) reported that nested projects render single-threaded and this was the cause for the difference in speed.

This was with VP 17-452 so ymmv with other versions.

John: thanks for testing, so we know that V14 is fine :)

Michael: yes, it seems like single threaded rendering.

So it came out to 284 seconds with Mainconcept whether nested or not?

Nested

and not nested with Mainconcept? This is a comparison...