[CinCV] Colour correction

2008-08-28 Thread Raffaella Traniello
Hi!

I'm experimenting with colour correction.

I found my way to correct the colours of an edit using:

Colour balance
Brightness/Contrast 
Hue/Saturation/Value
Gamma
Histogram
and Videoscope

But I can't find a good way of correcting a video made of 100 edits.
Do I have to attach 5 effects to each clip? 501 effects on my timeline??

I tried to attach just one effect for the whole timeline and using
keyframes. This way I get a nice and tidy timeline but Cinelerra keeps
interpolating my changes.

What's the recommended way to go?

Ciao!
Raffaella


___
Cinelerra mailing list
Cinelerra@skolelinux.no
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra


Re: [CinCV] Colour correction

2008-08-28 Thread Ichthyostega
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Raffaella Traniello schrieb:
 I'm experimenting with colour correction.
...
 But I can't find a good way of correcting a video made of 100 edits. 
 Do I have to attach 5 effects to each clip? 501 effects on my
 timeline??
 
 I tried to attach just one effect for the whole timeline and using 
 keyframes. This way I get a nice and tidy timeline but Cinelerra
 keeps interpolating my changes.
 
 What's the recommended way to go?

Hi Raffa,

sadly enough there is no viable solution available within Cinelerra.
It's simply not designed to do larger projects, i.e. the workflow
doesn't scale.

So, basically you can take both routes.

* attaching 5 effects separately to each clip
  pro: you don't need keyframes, and
   you can still trim your edits afterwards
  con: very much work to build up all those effects, and
   you can't use transitions (workaround: put the clips
   on separate tracks and use the fade automation)

* use 5 single effect instances spanning the whole timeline.
  pro: somewhat easier to build up,
   sort of works with transitions (not really perfect)
  con: you need carefully placed keyframes which need to be
   adjusted for every edit.


Explanation: to cope with the second solution, you need much
discipline. First of all, make your edits final, so you don't
need to trim anything further. Then start from the beginning
of the session with adjusting your effects. Use the
set keyframes while tweeking setting (the key icon).
Use the help of labels for precise setting of the cursor;
if you double click a clip, the corresponding timerange gets
selected. Then if you hit l, you get a label at the beginning
and end.

Now jump to the first label and then adjust the effects for the
first clip. This will set a keyframe onto each effect.

Then jump to the end and move the cursor exacly 2 frames to the left.
This works around the design misconception of cinelerra always
evaluating the keyframe value after the frame.
Now either paste a keyframe copied from the start, or provoke the
creation of a new keyframe by adjusting a setting of the effect
by one step and then immediately returning to the previous value.
This will give you a keyframe effectively at the end of your clip
and with the /same/ values as at the beginning.

Then go exactly 1 frame to the right (i.e. the cursor is now
at the start of the last frame of your clip, which means the
keyframe value will be used at the next frame afterwards, which
happens to be the first one of the next clip). At this point
make the adjustments for the next clip

well, there is another problem: in order to *see* the effect
of your adjustments, you'd have to enter the region of the next
clip. I'd recommend to do it as follows: first, /set/ the keyframe
at the start, then *disable* the generate keyframes when tweaking.
Now you can put your cursor at any location within the next clip.
And, assumed there is still no further keyframe to the right, any
tweaking of parameters will be stored into the next keyframe to
the left, which is what you want. And of course, don't forget
to re-enable the auto-generating of keyframes afterwards


well... now that makes me feel so sorry for you :-P

Hermann V.


PS: I am still bewildered how a developer can design a feature
this way without realizing what harm he does to its users...
Well, at second thought the case is clear: any real solution
of the problem would require more infrastructure within the
application.
But, at least even a possible workaround would be good, for
example if you could mark a timerange and then adjust and set
constant effect parameters within this range
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIttdJZbZrB6HelLIRAuMTAJ9m+dsGidMAZbAmaQcpFv7AcVHNJQCfe1T6
pLmilxNlWUMWH87VhsxZRYw=
=BBVW
-END PGP SIGNATURE-

___
Cinelerra mailing list
Cinelerra@skolelinux.no
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra