Inserting a VSP into VSP (VS 2020 and VS2021) - BUG REPORTED -

[cybernick]

Some imes in complicated projects I work with sub-VSP files separately. Then I edit those VSP files in a main VSP file. I do not want to render every VSP and work on rendered videos because generally every render may/possible reduce the quality. I want to render source videos once.

Sometimes inserting a VSP to the timeline may be a bit complicated, especially if your inserted VSP has multiple overlays. I realized an option that allow you to insert the VSP as a single clip. You just insest the VSP into timeline by holding the Shift key. So as long as you do not need to deepdive in to individual components of inserted VSP, this method simplifies a lot the main VSP.
The issue is that, if the inserted VSP has effects in a layer, you can not render to main VSP. The software freezes. I realized this in VS2020 but I did not report. But since it is the same in VS2021 too I just wanted to ask/communicate with the community first.

Any comment?

[cybernick]

I managed to pin point the root cause.
For a reason I do not know if the VSP inserted has vitascene 4 transition, the render freezes not in the vitascene transition part but in the following test layer ?!?!?!?
If you delete the vitascene transition the render goes fine.
You can check the attached videos. Also I am sharing the smart package of the "vsp in VSP.vsp" project file I use (VS2021 Ultimate file)

"with vitascene.mp4" is the video showing I insert the VSP as flatten media (holding shift key) while the project has the vitascene trans. RENDER FAILS
"without vitascene.mp4" is the video showing I insert the VSP as flatten media (holding shift key) and I delete vitascene trans. RENDER Successes

@lata should we report this as a bug?

[asik1]

You failed to to find the culprit, it's not Vitasene, here any trans I put will not render as nested vsp.

[cybernick]

Wav so it is a serious bug then. This feature would be very helpful in complex edits.
Can someone from Beta tester team report this for future patches?

[lata]

First the project properties of that VSP are unusual, 2560 x 1440, 25 fps I would have expected a more standard size.
The actual issue at first for me is the use of the Titles, it is those that stop the render at 22%, no files are created although the program does not crash. Then removing Vitascene allowed to render to complete as ok, so maybe a conflict between both and using the flattened vsp.

The easy fix of course is to use the nested vsp in its editable format, that is dropping to the timeline without pressing Shift.
I did replicate the issue using the Samples Lake .mp4, render then stalled with the error “Unable to Load Library”
Incidentally other A/B transition causes the problem, it is not just Vitascene

Cybernick….Yes there seems to be an issue here and you should report this to Corel Support.

[cybernick]

First the project properties of that VSP are unusual, 2560 x 1440, 25 fps I would have expected a more standard size.
The actual issue at first for me is the use of the Titles, it is those that stop the render at 22%, no files are created although the program does not crash. Then removing Vitascene allowed to render to complete as ok, so maybe a conflict between both and using the flattened vsp.

The easy fix of course is to use the nested vsp in its editable format, that is dropping to the timeline without pressing Shift.
I did replicate the issue using the Samples Lake .mp4, render then stalled with the error “Unable to Load Library”
Incidentally other A/B transition causes the problem, it is not just Vitascene

Cybernick….Yes there seems to be an issue here and you should report this to Corel Support.

Thanks Trevor. I will link this thread to the support call.
Meanwhile 2560 x 1440 is 2k. It is a trick for youtube. If you work for a youtube video and you can not go to 60P and you are in 25p or 30p, you should upscale the project and the render.
Youtube encoder is better in videos with high FPS or higher resolution then 1080p (2k or 4k). It is the trick of the day.

[cybernick]

Bug has been reported.