[CinCV TNG] Debugging motion blur

Einar R√ľnkaru einarry at smail.ee
Sun Apr 12 18:59:37 CEST 2015


Nicola, you asked for help.

On 04/10/2015 01:35 AM, Nicola Ferralis wrote:
> Hi,
> There is more. The method in the get_camera call in automation.C is
> empty. This means that get_camera shouldn't do absolutely nothing. In
> fact if you remove it completely, the crash doesn't obviously occur, but
> nothing happens either (no motion blur). Interestingly, an identical
> call in vautomation.C has a meaningful method for get_camera, that I
> would think it should be also replicated in automation.C as well. One
> could copy over the short piece of code in get_camera in vautomations.C
> into the blank get_camera call in automation.C, but that obviously
> doesn't prevent the crash, which, as I stated above, takes place
> *before* the get_camera is ever started.

Automation is base class of vautomation (video) and aautomation (audio). 
As there is no camera for audio, get_camera for audio is pointless.
> What i am trying to say is that the crash takes place immediately before
> get_camera is initiated in automatic.C. If that crash is solved, there
> may still be an issue with the blank call in get_camera.

How did you crash the program? My test case does not crash.

IMHO tho goal of the effect is to blur only moving objects in frame. 
Just guessing.


More information about the Cinelerra mailing list