Indigo 1.0.4
well call me thick if you like but I am still confused about this...
what are the units of offset, radius and start angle? metres and deg I presume
so this is like a mask behind the aperture radius specified round 'hole'? and blade offset should be small enough that all the cut out white bit fits inside that hole?
when the mask is an image it is scaled inside indigo according to the image size so that one side equals what relative to the aperture radius...twice?
sorry
EDIT: how about we just have a menu to choose from a supplied mask library and use f-stop as the basis?
say 3,4,5,6,7,8 and circular
what are the units of offset, radius and start angle? metres and deg I presume
so this is like a mask behind the aperture radius specified round 'hole'? and blade offset should be small enough that all the cut out white bit fits inside that hole?
when the mask is an image it is scaled inside indigo according to the image size so that one side equals what relative to the aperture radius...twice?
sorry
EDIT: how about we just have a menu to choose from a supplied mask library and use f-stop as the basis?
say 3,4,5,6,7,8 and circular
Last edited by Big Fan on Thu Nov 29, 2007 7:38 pm, edited 2 times in total.
The unit of blade_offset is normalised image distance. 1.0 = from left to right of aperture image.
Same with blade_curvature_radius. Start angle is measured in radians.
Yup, the blade offset should be small enough so the white part fits in the image without being clipped at the edge.
Yup, the image is effectively scaled down so that the width of the scaled image = aperture_radius * 2.
Same with blade_curvature_radius. Start angle is measured in radians.
Yup, the blade offset should be small enough so the white part fits in the image without being clipped at the edge.
Yup, the image is effectively scaled down so that the width of the scaled image = aperture_radius * 2.
ok so heres the lay of the land Big O
increasingly we are moving away from general, non specific, easy to set - doesnt matter too much, parameters to quite specific data and instances.
really the existing blendigo exporter is not set up for to this although it can be adapted some..
if this is to be the future direction I would rather cull a lot of this detail stuff even though you can specify anything you like with your xml and just model say a top line Nikon and Canon digital SLR with some drop down menus for materials and settings etc
I would rather hide all this stuff away from having to worry users about it all. Sort of a point and shoot equivalent of what we are heading to presently. KISS philosophy
What do you think?
increasingly we are moving away from general, non specific, easy to set - doesnt matter too much, parameters to quite specific data and instances.
really the existing blendigo exporter is not set up for to this although it can be adapted some..
if this is to be the future direction I would rather cull a lot of this detail stuff even though you can specify anything you like with your xml and just model say a top line Nikon and Canon digital SLR with some drop down menus for materials and settings etc
I would rather hide all this stuff away from having to worry users about it all. Sort of a point and shoot equivalent of what we are heading to presently. KISS philosophy
What do you think?
Last edited by Big Fan on Thu Nov 29, 2007 7:02 pm, edited 1 time in total.
perhaps...my feeling is we should restart development with a different emphasis... wonder what other people think about that
I guess blenderheads should indicate what sort of exporter they want
-simple to use with an artistic bent
-or complex with a scientific bent
-or simple with complex presets
or...
I guess blenderheads should indicate what sort of exporter they want
-simple to use with an artistic bent
-or complex with a scientific bent
-or simple with complex presets
or...
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
itd be nice to have all the options available in the exporter so that making changes/saving settings in the scene would be easier.
how about a 'basic' mode and an 'advanced' or 'hardcore' mode? like have the basic mode have all them presets you were talking about. just cuz for some people each setting changes per scene and its frustrating having to edit the XML each time you export after making a change.
right now it IS getting a bit clunky, especially when you realize ISO and shutter speeds only affect the rendering when camera tonemapping is on (i think). but a very good exporter nonetheless!
in fact, its saving my ass right now...
how about a 'basic' mode and an 'advanced' or 'hardcore' mode? like have the basic mode have all them presets you were talking about. just cuz for some people each setting changes per scene and its frustrating having to edit the XML each time you export after making a change.
right now it IS getting a bit clunky, especially when you realize ISO and shutter speeds only affect the rendering when camera tonemapping is on (i think). but a very good exporter nonetheless!
in fact, its saving my ass right now...
I wouldn't be able to do anything without the exporter. Hand-editing the XML for me just isn't an option. It would bring me over a threshold where I would just simply leave it, I think. So a good exporter is completely vital to me. And - apologies in advanced to our techies here - I would vote for a relatively easy to use, artistically bent exporter. I do like the latest additions but find some of the implementation intimidating...
But that's just my humble opinion...
EDIT: I may be talking nonsense here, but I wonder if it wouldn't make things easier if most of the tonemapping options were migrated from the exporter to a super-beefed-up version of violet - essentially all the parameters that can be modified in post with in the igs image...
This would allow us to cook a relatively generic image and tune it once its cooked with maximum flexibility rather than having to go through millions of trials and errors with zillions of parameters before you launch the main render...
But that's just my humble opinion...
EDIT: I may be talking nonsense here, but I wonder if it wouldn't make things easier if most of the tonemapping options were migrated from the exporter to a super-beefed-up version of violet - essentially all the parameters that can be modified in post with in the igs image...
This would allow us to cook a relatively generic image and tune it once its cooked with maximum flexibility rather than having to go through millions of trials and errors with zillions of parameters before you launch the main render...
One thing Ono mentioned earlier was that the new aperture diffraction stuff when run within indigo has the advantage of working on the full-spectrum light data, whereas I get the impression that an IGI file contains less info than that (only XYZ color).BbB wrote: EDIT: I may be talking nonsense here, but I wonder if it wouldn't make things easier if most of the tonemapping options were migrated from the exporter to a super-beefed-up version of violet - essentially all the parameters that can be modified in post with in the igs image...
This would allow us to cook a relatively generic image and tune it once its cooked with maximum flexibility rather than having to go through millions of trials and errors with zillions of parameters before you launch the main render...
Can anyone confirm if I understood this correctly?
Correct.dougal2 wrote:One thing Ono mentioned earlier was that the new aperture diffraction stuff when run within indigo has the advantage of working on the full-spectrum light data, whereas I get the impression that an IGI file contains less info than that (only XYZ color).BbB wrote: EDIT: I may be talking nonsense here, but I wonder if it wouldn't make things easier if most of the tonemapping options were migrated from the exporter to a super-beefed-up version of violet - essentially all the parameters that can be modified in post with in the igs image...
This would allow us to cook a relatively generic image and tune it once its cooked with maximum flexibility rather than having to go through millions of trials and errors with zillions of parameters before you launch the main render...
Can anyone confirm if I understood this correctly?
I vote for StompinTom's idea
easy: artistical
advanced: further control (could for example be, that in easy mode, you have all the nks as presets and in advanced, you have your number field...)
and
"hardcore": EVERYTHING in it, tweakable by user - just like the current exporter
So, you're planning to rerelease an exporter-version of yours, BigFan?
Is radiants meant as normalized and pi will be multiplied by Indigo (1 = 180*) or is it pi=180° ?
easy: artistical
advanced: further control (could for example be, that in easy mode, you have all the nks as presets and in advanced, you have your number field...)
and
"hardcore": EVERYTHING in it, tweakable by user - just like the current exporter
So, you're planning to rerelease an exporter-version of yours, BigFan?
Is radiants meant as normalized and pi will be multiplied by Indigo (1 = 180*) or is it pi=180° ?
Who is online
Users browsing this forum: No registered users and 52 guests