ebra studios (4/12/2021)

---

Yes that can be as well , but the beta suddenly not opening and a green screen is kind of pain if I would use that method. So this update is really awesome for creators 

apyorick1 (4/13/2021)

---

I usually use layered image sequences from CTA when adding effects in HitFilm, so this new update was very exciting! I did a test of a small segment of a scene from one of my films to see how all of the new features work. First I rendered the scene directly out of CTA:


Then I used some of the new features, rendering groups of layers isolated with the new selection tool as .mov files and uploading to HitFilm for post production effects. I LOVE the "Isolate Selection" tool - works great and saves me from clicking/unclicking massive numbers of files. Using the .mov files as opposed to image sequences not only saves HUGELY on storage space (762 MB as opposed to 1.69 GB for the image sequences for this particular project!) but makes it a snap to load them into HitFilm as it's just a matter of selecting all the .mov files and loading them all at the same time. Using image sequences you have to load each sequence separately. There are a few problems, however, which I'll show with the following two videos.

First, here is the version rendered out of HitFilm using the .mov files:
  
You will notice lots of striation and pixellation  on the .mov files, particularly the front hair. This may not be completely visible in these unlisted YouTube versions (they will be when making them fullscreen), but is VERY visible when viewing the original file on my PC and would be unusable for a film destined for festivals or other streaming venues.

When I did the exact same segment and same effects (actually copied/pasted the effects so they are EXACTLY the same) but using image sequences instead I don't get the same problems:


All of these videos were final-rendered with exactly the same settings. I think it's a problem with the quality/size of the .mov files. These were rendered with the highest available settings in CTA. I realize if the quality were increased the size of the files would approach that of image sequences, but the result would still be so much easier to use when loading into an editor that it would be worth it. 

apyorick1 (4/18/2021)

---

Did some more tests with the .mov capabilities as this feature will be a game-changer for me. I created a very simple project with four different resolutions of the main feature and simple movement to see how it affects the .mov files.

Here is the original render out of CTA4:


I will change the resolution of the trombone and save as a .mov file to be loaded into HitFilm for effects (the notes were also saved as a .mov file).
(As in my last test, the use of the "Isolate Selection" feature made things a lot easier and faster.)

You will note the pixellation problem in the areas indicated on this still:



Here is the first render with the trombone at high resolution (2600 x 2863). (All trombone assets will be 300 DPI).


If you look carefully at the areas I indicated, there is still pixellation, even with an asset of this high resolution.

Next, at 1400 x 1542:


900 x 991:


And 500 x 551:


You will notice that the pixellation increases as the resolution of the asset decreases (which is to be expected); but even at the highest resolution (the original resolution of the asset) there is still a problem.
Any suggestions are most welcome!

Animaniac (5/6/2021)

---

Hey folks, here is my Happyslug video again, with the transparent MOV loops imported into Adobe Premiere, only this time I treated my sketchy backgrounds with one of the Photoshop Neural Filters to add some extra detail to my backgrounds. it was all done pretty quickly but has a good look to it.