Profile Picture

AI Data Collection & Denoiser Scan by iClone for an Iray Animation

Posted By TonyDPrime 7 Years Ago
You don't have permission to rate!

AI Data Collection & Denoiser Scan by iClone for an Iray Animation

Author
Message
TonyDPrime
TonyDPrime
Posted 7 Years Ago
View Quick Profile
Distinguished Member

Distinguished Member (13.4K reputation)Distinguished Member (13.4K reputation)Distinguished Member (13.4K reputation)Distinguished Member (13.4K reputation)Distinguished Member (13.4K reputation)Distinguished Member (13.4K reputation)Distinguished Member (13.4K reputation)Distinguished Member (13.4K reputation)Distinguished Member (13.4K reputation)

Group: Forum Members
Last Active: Last Year
Posts: 3.4K, Visits: 12.4K
Please pass on to parties involved in development of iClone Iray - is THIS possible:

BACKGROUND
Having used Daz Iray and 3ds Max Iray (with denoiser), iClone users are concerned with viability of rendering animations (multiple frames) using Iray, due to inability to render frames as fast as iClone's own native PBR real-time renderer..
So, when we will render a frame in Iray, even optimally, the denoiser will be starting from scratch, frame to frame, with each frame, in order to collect the information for the denoise.

As background, in such case, let's imagine I can render a batch of denoised images @1080p, for say, 6 seconds per frame.  In this case a 900-frame render winds up taking 5400 seconds, or 90 minutes, an hour and a half (1.5 hrs).

IDEA
What if, the iClone could run an initial 'Scan Pass' of some sort, where it could scan all frames in a project's timeline, to gauge AI-wise where the renders wind up being less dynamic, and more static (ie where renders are in fact duplicates, or mere duplicates, and 'stay the same')
Then, it could render frame by frame, but not be pressured to start from scratch in all frame cases, because it would have a que of info to cross-check against, (either in a buffer of active info, or off of a text-file, say), in which case it could spit out the almost 'identically-same' renders much quicker, much like if it was a single mat HDRI, or single JPG background being rendered frame after frame.

Now, it would need to collect the info first, and the initial Scan-Pass would take time to collects said info, and this would occur before render.  (almost akin to what iClone's Indigo plugin did, but in this case only as a scan to collect info)

So, if iClone could run such a Scan-Pass to collect the info first, it would then now have an optimized 'render plan' for the whole project. 

HOPE
instead of having to render and denoise on an image-by-image basis, iClone could do a scan at beginning (ie 15 minutes scan of all frames), que the info, and then tell Iray of the info that it collected, such that it could run the renders with the AI of knowledge already captured.  Let's imagine, for example, with this faster rendering, it would only have to take 45 minutes, say, as several frames would be already known by Iray as duplicates, or near duplicates, in which case frames render in 1-2 seconds vs 6 seconds.  
I am imagining such a Scan Pass could cut down the render timer for a sequence of frames cumulatively, even with the time it would take to run a scan at the beginning.
Thus, iClone users could more optimally render animations using the Iray renderer and denoiser. 
It wouldn't make denoiser or renderer itself faster, it just could give 'the iClone project' a curriculum to work off of, AI wise.
And then, like my example imagines, the project could take an hour (with a pre-info pass of collected info for 15 minutes + optimized AI render time of 45 minutes), vs and hour and a half (no info collected before hand, just independent frame-by-frame.

Any thoughts?




Reading This Topic