Cmd Question

[user_deleted]

Hi Forum,

I have a quick command line question. (I dont know if it matters but right now I am sitting on a PC workstation)

So I wanna quickly view at my scans - I type in something like: shake mypath.#.cin -t 41-60 -proxyscale .5 -loglin 0 ...so far so good. - but now I wanna change lets say one setting in my loglin and leave the rest as default. Is there any tip to make a shortcut and jump over the next 10 arguments in order to change only one gamma setting or do I have to go all the way 0 0 0 0 95 95 95 683 683 683 etcetc..?? Please excuse if this has been asked before - I could not find anything..

thanx

[user_deleted]

There's no way to override just some of the parameters. However, for this purpose you could use good old delogc (I always use this one in command line since it doesn't handle rgb separate values for all parameters, so it takes less arguments to be written)

So, that would be:

shake yourfiles.#.cin -t 41-60 -proxyscale .5 -delogc 0 0 0 95 685 0.6 1.7 0

Hope that helps

[user_deleted]

OIC - I can finally stop searching. thank you -
the delogc -very nice- helps - 9 less - still 6 too much:)
but definitely makes my life easier!!!

May I ask you something else...
Whenever I use the -compare mode and add a -proxyscale
to it, only one file "A" is being affected while "B" remains still
in its original size. I tried all kind of combinations and didnt succeed.
I dont know if its me or a version issue (which is hard to imagine)
Do you have any idea?

[user_deleted]

QUOTE(grasshoppa @ 01/20/06, 02:58 AM) [snapback]225592[/snapback]
May I ask you something else...
Whenever I use the -compare mode and add a -proxyscale
to it, only one file "A" is being affected while "B" remains still
in its original size. I tried all kind of combinations and didnt succeed.
I dont know if its me or a version issue (which is hard to imagine)
Do you have any idea?

Mmm... never noticed that, but it's behaving exactly like you say. Actually, I've found no way to apply any transformation to the B buffer, they're only applied to A. This might be a bug (or a non-feature, if you'd like), but not a version issue, since I tested with 3.5 with the same results.

[mediasaurus]

If you don't want to type in all 9 values or even 6, I would think you could make a macro of LogLin and only have that one parameter be editable. Haven't tried this, but just a thought.

[user_deleted]

Hi Shakers!

I'm new to command line compositing, so I have a few basic questions.

If a create a checkerboard for example, by typing:

-shake checkerboard

a checkerboard appears in a window named "CheckerBoard1". Until I don't shut down the window I cannot type another command, but if I shut it down, the checkerboard disappears and doesn't exists any more. (I can create another one with the same name, instead of "CheckerBoard2".) How can I keep it, for further processing?

The other case is similar: the Over operation:

If I type:

-shake fg.iff over bg.iff

that works, but if I type:

-shake -colorwheel -over -checkerboard

that doesn't work.

-shake ColorWheel1 -over CheckerBoard1

won't find ColorWheel1 and Checkerboard1.

In the tutorials there are examples only with files located somewhere on your HDD, but a checkerboard exists only in memory (until you render it), you cannot type its path. So how can this be solved?

Thank you in advance

VertexX

[user_deleted]

Does anybody know how to do this?

(See above)

Thanks,

VertexX

[user_deleted]

-label...

it lets you label a previous input to reference it afterwards

Ex.

shake -checker -label chk -colorwheel -over chk