My own pipeline now is to use the JSON Export script to take layers over to After Effects to do any complicated or "heavy" multiplane work . (but even AE can get very laggy if there are a lot of layers and the resolution is high , like 4K. ) I'm using the PixelBump Multiplane for AE script available here:
https://www.youtube.com/watch?v=_Ql4uftlSMI
A friend also told me that this script :
https://aescripts.com/pt_multiplane/ pt_Multiplane script by Paul Tuersley is very good. It costs $34.99. For now the free PixelBump Multiplane for AE script works for me , but I will probably download the pt_Multiplane script at some point to try it .
However, Cardin Collins came up with an interesting workaround for using the Multiplane FX in TVPaint that I hope he will share here. I've contacted him to ask if I can share it , if he doesn't want to share it.
----
EDIT: Cardin Collins says ok if I post his workaround. I've tried this and it does work . I would use it for setting up fairly straightforward , multiplane shots in TVPaint, to test the short first in the lower-res. version before re-rendering it at full-resolution. (for more complicated multiplane shots I would still tend to use AE).
(this workaround assumes you are familiar with how to use the Multiplane Camera FX in TVPaint. For tutorials on how to use Multiplane Camera , see:
https://www.youtube.com/watch?v=RyyZfcw197M and
https://www.youtube.com/watch?v=2W3sji6ZTDA
Source file used in the first tutorial -- FX_Multiplane_Camera_2.tvpp -- can be found in
https://www.tvpaint.com/v2/content/arti ... amples.php )
Here is Cardin Collins's workaround , with a few additional notes added by me:
Multiplane FX workaround:
The Field of View parameter in the Multiplane FX has a different default value depending on the resolution of the project.
For example, in a project with resolution 1280 x 960, the default FOV in the Multiplane FX is 51.282°. But at 4K size , 4096 x 3072, the default FOV is 113.868°
However, if you Modify the project and do your multiplane camera moves in the lower-res. project AND you use the Library as the source for the planes instead of the layers themselves , then I think we have a solution. I tested it and seems to work out. Let me know your results after trying the method below:
1.) All of your planes should be set up as separate layers in your hi-res project. We're going to set up the starting X,Y,Z positions of the planes in the MultiPlane Camera FX panel , but not add any camera moves yet.
2.) For all the layers that are just static images, add those to the Library, instead of using the layers as the Source in in Multiplane Camera, use the images in the Library as the source for each plane when you set up the layer positions.
3.) For the planes that are Animation layers, export them as .dip files and open them in a separate .tvpp project. In the Multiplane Camera Source menu, use that Project as the source.
4.) Next step: Modify the project to a lower resolution. For example: let's say the original project size is 4096 x 3072 , you can modify it so it is downscaled to 1280 x 960 , or 800 x 600 , even 640 x 480 , Or if the original was 2048 x 1152 , modify it so it's downscaled to 960 x 540 or 640 x 360 , anything that is in the same aspect ratio as the original project. After you downscale the project using Modify Project all the planes in the Multiplane FX should be in the same position , just scaled down. This is because we used the Library and/or the separate .tvpp Project(s) as the Source and also the Field of View from the original high res project has been carried over.
5.) Now, work out your multiplane camera moves in the lower res. project. Because it is lower res you will not experience as much lag when adjusting layers and it will render much more quickly.
6.) When the multiplane camera move is working as you want it, click on FX Bin at the top right of the Multiplane FX window and click Add. Give it a name such as SC_1_Multiplane_v1 . It is now saved in the FX Bin. (you could also choose the option to click FX Bin and EXPORT the Multiplane FX , with appropriate name such as SC_1_Multiplane_v1 , then you'll import it back to the FX Stack when you return to your high-res. project. Some people prefer to keep all their saved FX for a specific project in a dedicated folder , then re-import the FX into the FX Stack when needed , rather than store the saved FX in the FX Bin. Either way works, but if you use the Add to FX Bin function a lot you'll soon have dozens of saved FX on the list in your FX Bin and it can get cluttered. Keeping the saved FX organized in folders on your computer can be more orderly.)
7.) At this point , go back to your original hi-res project , open FX Stack > Multiplane Camera > and load the SC_1_Multiplane_v1 you had saved previously in the FX Bin. (or import it if you had saved it in a folder on your computer). Now your multiplane camera move will be applied in the high-res project, but it is now scaled correctly. Select all frames on the layer where you will render the move and click on Add FX. Wait while the Multiplane Camera FX is rendered.
The only thing that may be an issue is if you have a large number of source layers in the Library and/or many separate animation layers as sources open in separate projects. The render time may take a long time in the high res project , but because you've already previewed it in the lower res version , you know it's going to work , so go do something else while you just let it do it's thing rendering .
------
I have tried several tests of this method using between 5 - 8 layers and the render time in the high res (2K or 4K) project has not taken too long. I can imagine if you had many more layers and also many Animation layers that the render time could be much slower.
Cardin also told me:
"In addition, I intend to write a script that 1) Automatically adds all static layers to the Library and 2) Exports and then opens each animation layer as a separate project. Just a nice time saver feature." He hasn't written that script yet , but I'm sure when he does he will post it. He said he's been very busy at work at the present time.
)
Calling all you TVPaint scripting wizards:
)
