Isotropix Forums

[crender] general questions

Clarisse related tips and tricks

[crender] general questions

Unread postby Mikros_Licensing » Thu May 18, 2017 6:32 pm

Hello,

I have several questions about the crender application we use to render images on our render farm.

1 - render 1 layer of 1 image per command
I would like to export a render archive, and run as many crender commands as (images x layers) in my scene. So each task on the render farm will output one image. Is it an interresting workflow? My idea is to avoid too long rendering on a single computer on the farm (this is the case if I have one task per image, and an example of a scene with 18 layers for an image). But is there a possible duplicate of a too important time taken to load the scene maybe?

2 - Strange progress in logs
I cannot explain the following logs, which is the result of a rendering task:
crender scene.render -license_server xxx -image project://scene/image.cam_001 -image_frames_list 1001 -sampling_quality 1.0 -output /path/to/output -format exr16 -stats -verbose -log_width null

00:08:05 11033/11034MB VM(13.58/13.71GB) Progress for 'project://scene/image' : 1%
00:08:08 11046/11046MB VM(13.65/13.71GB) Progress for 'project://scene/image' : 2%
00:08:10 11061/11062MB VM(13.65/13.77GB) Progress for 'project://scene/image' : 0%
00:08:22 11061/11062MB VM(13.65/13.77GB) Progress for 'project://scene/image' : 1%
00:08:29 11062/11080MB VM(13.65/13.77GB) Progress for 'project://scene/image' : 0%
00:08:40 11062/11080MB VM(13.65/13.77GB) Progress for 'project://scene/image' : 1%
00:08:53 11082/11082MB VM(13.77/13.77GB) Progress for 'project://scene/image' : 0%
00:09:07 11083/11083MB VM(13.77/13.77GB) Progress for 'project://scene/image' : 1%
00:09:22 11125/11125MB VM(13.71/13.77GB) Progress for 'project://scene/image' : 0%
00:09:33 11125/11125MB VM(13.71/13.77GB) Progress for 'project://scene/image' : 1%
00:09:57 11153/11159MB VM(13.77/13.83GB) Progress for 'project://scene/image' : 2%
00:09:58 11156/11159MB VM(13.77/13.83GB) Progress for 'project://scene/image' : 0%
00:10:05 11156/11159MB VM(13.77/13.83GB) Progress for 'project://scene/image' : 1%
00:10:33 11173/11174MB VM(13.77/13.90GB) Progress for 'project://scene/image' : 2%
00:10:37 11181/11182MB VM(13.77/13.90GB) Progress for 'project://scene/image' : 3%
00:10:43 11202/11202MB VM(13.77/13.90GB) Progress for 'project://scene/image' : 0%
00:11:00 11204/11204MB VM(13.77/13.90GB) Progress for 'project://scene/image' : 1%
00:11:16 11205/11206MB VM(13.77/13.90GB) Progress for 'project://scene/image' : 2%
00:11:19 11206/11207MB VM(13.77/13.90GB) Progress for 'project://scene/image' : 3%
00:11:27 11215/11215MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 0%
00:11:28 11215/11215MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 1%
00:11:46 11218/11220MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 2%
00:12:04 11224/11226MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 3%
00:12:24 11251/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 1%
00:12:24 11252/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 2%
00:13:01 11258/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 3%
00:13:02 11258/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 4%
00:13:06 11258/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 1%
00:13:33 11258/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 2%
00:13:44 11258/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 3%
00:13:49 11258/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 4%
00:13:59 11263/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 1%
00:14:33 11266/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 2%
00:14:36 11266/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 3%
00:14:45 11266/11267MB VM(13.83/13.90GB) Progress for 'project://scene/image' : 4%
00:15:19 11279/11279MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 1%
00:15:53 11281/11281MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 2%
00:15:55 11281/11281MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 3%
00:16:04 11281/11281MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 4%
00:16:36 11282/11282MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 5%
00:16:54 11288/11291MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 2%
00:17:04 11288/11291MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 3%
00:17:30 11288/11291MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 4%
00:17:48 11288/11291MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 5%
00:17:49 11288/11291MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 6%
00:17:59 11289/11291MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 7%
00:18:19 11291/11291MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 3%
00:18:20 11292/11292MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 4%
00:18:58 11297/11297MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 5%
00:19:29 11298/11299MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 6%
00:19:40 11299/11299MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 7%
00:19:40 11299/11299MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 8%
00:19:41 11299/11299MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 9%
00:19:52 11299/11300MB VM(13.90/13.96GB) Progress for 'project://scene/image' : 10%
00:20:29 11305/11306MB VM(13.96/14.02GB) Progress for 'project://scene/image' : 11%
00:20:58 11308/11315MB VM(13.96/14.02GB) Progress for 'project://scene/image' : 12%
00:21:06 11308/11315MB VM(13.96/14.02GB) Progress for 'project://scene/image' : 13%
00:21:07 11308/11315MB VM(13.96/14.02GB) Progress for 'project://scene/image' : 14%
00:21:07 11308/11315MB VM(13.96/14.02GB) Progress for 'project://scene/image' : 15%
00:21:14 11311/11315MB VM(13.96/14.02GB) Progress for 'project://scene/image' : 16%
00:21:58 11323/11323MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 17%
00:22:07 11334/11334MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 6%
00:22:07 11335/11335MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 7%
00:22:08 11335/11335MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 8%
00:22:56 11335/11335MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 9%
00:23:29 11336/11337MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 10%
00:23:33 11336/11337MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 11%
00:23:33 11336/11337MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 12%
00:23:34 11336/11337MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 13%
00:23:41 11336/11337MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 14%
00:24:28 11337/11338MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 15%
00:24:50 11339/11340MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 16%
00:25:16 11339/11340MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 17%
00:25:41 11339/11340MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 18%
00:25:42 11339/11340MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 19%
00:25:42 11339/11340MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 20%
00:25:43 11339/11340MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 21%
00:25:45 11339/11340MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 22%
00:26:00 11349/11349MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 23%
00:26:01 11354/11354MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 10%
00:26:02 11354/11354MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 11%
00:26:19 11355/11355MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 12%
00:26:31 11355/11355MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 13%
00:26:49 11355/11355MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 14%
00:26:55 11355/11355MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 15%
00:27:12 11356/11357MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 16%
00:27:14 11356/11357MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 17%
00:27:15 11356/11357MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 18%
00:27:15 11356/11357MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 19%
00:27:15 11356/11357MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 20%
00:27:16 11356/11357MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 21%
00:27:41 11359/11359MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 22%
00:27:50 11359/11359MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 23%
00:28:00 11359/11359MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 24%
00:28:13 11361/11361MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 25%
00:28:20 11361/11361MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 26%
00:28:21 11361/11361MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 27%
00:28:24 11361/11361MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 28%
00:28:37 11362/11363MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 29%
00:28:51 11362/11363MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 30%
00:29:05 11366/11366MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 31%
00:29:21 11366/11366MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 32%
00:29:22 11366/11366MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 33%
00:29:25 11372/11372MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 34%
00:29:35 11373/11374MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 35%
00:29:55 11375/11375MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 36%
00:30:08 11376/11376MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 37%
00:30:08 11376/11376MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 38%
00:30:12 11376/11376MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 39%
00:30:18 11377/11377MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 40%
00:30:36 11378/11378MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 41%
00:30:50 11380/11380MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 42%
00:30:51 11380/11380MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 43%
00:30:52 11380/11380MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 44%
00:30:57 11380/11380MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 45%
00:31:17 11381/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 46%
00:31:35 11381/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 47%
00:31:36 11381/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 48%
00:31:36 11381/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 49%
00:31:41 11381/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 50%
00:31:57 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 51%
00:32:08 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 52%
00:32:09 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 53%
00:32:12 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 54%
00:32:20 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 55%
00:32:40 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 56%
00:32:53 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 57%
00:32:54 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 58%
00:32:55 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 59%
00:33:04 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 60%
00:33:19 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 61%
00:33:36 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 62%
00:33:37 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 63%
00:33:37 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 64%
00:33:42 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 65%
00:33:51 11382/11383MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 66%
00:34:11 11383/11385MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 67%
00:34:12 11383/11385MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 68%
00:34:13 11383/11385MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 69%
00:34:21 11383/11385MB VM(14.03/14.03GB) Progress for 'project://scene/image' : 70%
00:34:33 11383/11385MB VM(14.03/14.03GB) raytrace: rendered in 512.091 s...
00:34:33 11383/11385MB VM(14.03/14.03GB) Progress 100%


Why does not the progression reach 100%? And why can I see the same percent several times? Is it related to the number of running threads?

3 - crender and the "Project's overridable arguments"
Can crender use the -sampling_quality option? Because it does nothing according to my test. My command is:
crender input.render -license_server xxx -image project://scene/image -frames_list 0 -output /tmp/output -format exr16 -rendering_log_tick 60 -stats -verbose -log_width null
Should I use cnode to do that? Because it's confusing to have thoses options in the crender command line help...

4 - WARNING: ParserValue.get_as_int: type mismatch, value type is 'TYPE_STRING'
I have this warning message with this command line:
crender input.render -license_server xxx -image project://scene/image.Cam_001 -frames_list 1001:1001 -output /tmp/output -format exr16 -stats -log_width null -preview
Do you know where does this come from?

Thank you for your advice :)

Cheers,
Clement
Mikros_Licensing
 
Posts: 7
Joined: Tue Dec 22, 2015 7:59 pm

Re: [crender] general questions

Unread postby isoyann » Fri May 26, 2017 10:45 am

Hi,

About the question 1, this is really not a recommended workflow. There is no advantages of doing this, because the archive generation is very fast and it is very lightweight, so there is no reason to split it per frame. About the question 2, the QA will investigate to reproduce the issue..

Thanks!

Yann
User avatar
isoyann
 
Posts: 601
Joined: Mon Jan 28, 2013 12:11 pm

Re: [crender] general questions

Unread postby fjutel » Mon May 29, 2017 2:29 pm

Hi Clement,

About question 2: do you have different layers in your image? That could explain why you have the same percent several times.
Do you have any empty parts in your image ?

About question 3: you can use this command with CRender. You'll find a list of all commands available with CRender if you launch crender -help.

The warning append because you wrote -log_width null while this argument only accepts integer value.

Hope this help

Cheers,
Florent Jutel
Isotropix
Clarisse QA
User avatar
fjutel
 
Posts: 264
Joined: Tue Jan 13, 2015 1:21 pm

Re: [crender] general questions

Unread postby cchampet » Tue May 30, 2017 6:33 pm

Hello,

Thanks guys for your feedback.

Question 1: I don't want to export an archive of the scene several times. My idea is to split the rendering process to write images on disk as soon as they are computed (and don't have to wait until all the 3d layers of one image are computed). So currently I have one image written per task submitted to the render farm system (no matter the number of images/layers in my scene). But this could be interesting only if I can ask to Clarisse to compute only one layer of one image in a crender command, and this may be related to the question 2.

Question 2: Indeed I have several 3d layers in my image project://scene/image: cam_001, cam_002, cam_003... In my crender command I ask to render only the cam_001, but is it the case? Because like you said @fjutel, the rendering of several 3d layers could explain the strange progress in logs...

Question 3: Glad to hear that :) I'll test again this parameter, and if it does not work I'll send you an example scene.
Question 4: Thanks, it works!

Cheers,
Clement
cchampet
 
Posts: 12
Joined: Fri May 19, 2017 9:20 am

Re: [crender] general questions

Unread postby cchampet » Wed Aug 09, 2017 6:30 pm

Hi again,

I still have issues with the crender command, related to 2 topics of which we have already spoken a bit.

3 - crender and the "Project's overridable arguments"
It seems that the crender tool does not support the -sampling_quality option, even if it is shown in its help. I attached a render archive of a scene with an image with a sampling quality set interactively to 0. Using the command line, I would like to raise the sampling quality to 100% and render it. Does my following command correct?

Code: Select all
crender test.render -license_server xxx -image project://scene/image.green -frames_list 0:0 -output /tmp/test.#### -format exr32 -sampling_quality 1


2 - Strange progress in logs
I still cannot explain the progression shown in logs in some cases:
* Why does not the progression reach 100%?
* Why can I see the same percent several times? Or sometimes it goes to 10%, and goes back to 5%, 6%, 7%...
I don't have any empty parts in my image. I have different layers for it, but I indicate to crender the exact layer of the image to compute (-image project://scene/image.green for example). Does the rendering still compute all the layers of the image when I use this syntax?

Again, thank you for your time :)

Cheers,
Clement
Attachments
test.project
(30.22 KiB) Downloaded 8 times
test_render_archive.zip
This zip includes the render archive.
(4.14 KiB) Downloaded 5 times
cchampet
 
Posts: 12
Joined: Fri May 19, 2017 9:20 am

Re: [crender] general questions

Unread postby dboude » Thu Aug 10, 2017 12:27 pm

Hi,

3 - crender and the "Project's overridable arguments"
Actually, the -sampling_quality argument works only when you render an image. I add a request in our database to make it work at layers level (ID#7280)

2 - Strange progress in logs
Have you empty tiles in your renders? The percentage of the progression is based on the whole image. So if you have empty tiles on the borders of your image it will be rendered in a few ms. That could explain the jump between XX% to 100%.

The several percentages could occur when you use rendered images to texture objects used in another image. Is that your case?

And no, the renderer compute only the layer you have set in the command line.

Cheers ;)
Démian
Isotropix
Technical Artist - Clarisse Specialist
User avatar
dboude
 
Posts: 153
Joined: Mon Jul 03, 2017 11:51 am

Re: [crender] general questions

Unread postby cchampet » Fri Aug 11, 2017 8:55 am

Thank you for your answers.

Indeed, I've just tested to use the -sampling_quality option without specifying the layer of an image, and it works. I am looking forward to use this option at the layer level, but it's already really cool :)

Have you empty tiles in your renders?

I have empty tiles in several visible layers of my image, but the layer I set to render is a full picture without any gap. So I don't think it's related.

The several percentages could occur when you use rendered images to texture objects used in another image. Is that your case?

Hum, I don't think so, but let me check ;)

Cheers,
Clément
cchampet
 
Posts: 12
Joined: Fri May 19, 2017 9:20 am

Re: [crender] general questions

Unread postby cchampet » Tue Sep 19, 2017 1:48 pm

Hi,

Have you empty tiles in your renders?

I confirm that the layer I set to render is a full picture without any gap: so this does not explain our case with jump between XX% to 100%.

The several percentages could occur when you use rendered images to texture objects used in another image. Is that your case?

I confirm that this is not our case. Do you know other possible reasons that could explain the several percentages in our log?

Cheers,
Clement
cchampet
 
Posts: 12
Joined: Fri May 19, 2017 9:20 am


Return to Tips and Tricks