Recompute bug after resizing project

[Sewie]

Hello Dear TVP friends,

So I did the following:

I had a TVP-project of 1024x576 (about 6MB) wich I resized to 2048x1152:



After TVP did it's calculations, it ended up with a scene full of added exposures which weren't there in the original. When I select these frames and hit 'recompute' (through either 'Layer>Exposure>Recompute Exposure' or the Animator Panel) it won't work. I don't get the original timing of my instances back...
As a consequence of this I am left with layers that are not very manageable because of all the exposure (many of which are exact copies of each other) and a huge file on my hard disk when I save it: +400 MB !!



So what did I not see, or do, right ?
I've noticed that this problem does not occur when the "Resize to New Size" box is unchecked...

Help me out please, please !

[Fabrice]

it could be a silly question, but did you change the framerate ?

[Sewie]

No, I left it at 25 fps.

[Paul Fierlinger]

It sounds to me that you just want to recompute Exposures, using the R button. You are seeing repeated frames where you had instances before .
EDIT: Sorry, I just noticed the second part of your post. Perhaps you are not using the Recompute button properly?

[Sewie]

I tried to 'Recompute Exposures', but it doesn't seem to work. I tried it in the main menu through the Layers-pulldown tab ('Layer>Exposure>Recompute Exposure'), in the Animator Panel and I tried using the keyboard shortcut 'R'.

But TVP just won't listen...

Most of the frames in the screenshot of the timeline above are just repeated frames.

Edit:

Perhaps you are not using the Recompute button properly?

I just hit it on the keyboard and in the panel and the menu's... (?) Is there a better way ?

[Paul Fierlinger]

There does seem to be a bug. I have always used modify to make my clips smaller and everything works as expected, but I now tried blowing up a clip and get the same results Sewie describes; Recompute does not work, whereas it does when you reduce the size.

[Elodie]

Did you think to select your frames before recompute ?

If you're using the new animator panel, the Recompute button is situated into "Exposure" It's a green button, on the right of the yellow S

recompute.png (22.32 KiB) Viewed 21171 times

[Sewie]

Did you think to select your frames before recompute ?

Yes, I did select them before hitting recompute.

If you're using the new animator panel, the Recompute button is situated into "Exposure" It's a green button, on the right of the yellow S

That's the one I used, and the one in the Main Menu pulldown and the keyboard shortcut.

[Elodie]

Which version are you using ? You seems to be on PC, isn't it ? I cannot reproduce this bug on my mac.. =/

[Sewie]

That's strange.
I am indeed on a PC with vista 64bit. Using TVP-pro 9.5.3

[Peter Wassink]

Which version are you using ? You seems to be on PC, isn't it ? I cannot reproduce this bug on my mac.. =/

No No no!

This is an old bug! and maybe hard to reproduce since it is not clear what causes it exactly. But it has happened to me quite often.

So i'm sorry to see everyone throwing all these suggestions at Michael when this is clearly a problem with TVP.

My experience is that it usually happens with larger resolution formats or very data intense layers, and in cases like these when modifying to a new and bigger size it happens regularly.
i tried it just now i created a two layer 10 frame complex anim of 1920X1080 resolution using the CTRL command and the red paintbrush from the toolbins classic tools, then added a timing and modified it to twice the resolution, result a broken timing that is not recomputable.

So Michael for now:
You could copy the timed layer from your unscaled project and use that to manually drag all holds according to your original layer... its literally a drag but unfortunaltely if you use the transform tool on this imported layer you are back at the same problem, because the transformtool will break the layer into instances and these again cannot be recomputed because of the TVP bug.
The other option is to only aply the transform to the headframes, depending on how many frames you have it could be faster... but i think retiming it according to the imported layer is probably the fasted workaround

[Elodie]

So i'm sorry to see everyone throwing all these suggestions at Michael when this is clearly a problem with TVP.

Peter, I've never doubted it was a TVP's bug, but I need complementary description to know exactly what's happening (that's why I ask him questions). Btw, as we say "the most of the time, bugs are situated between the chair and the keyboard That's why I always ask in first if the customer didn't miss a step or make an error =)

We've just tried again, Hervé and I, and I was right : it's a bug only on PC, not Mac (I cannot reproduce it, Hervé can... or Peter, give me your file and I will test it).

So, Hervé is searching from where this bug comes ^^

[ZigOtto]

yeap, this kind of bug is very puzzling, because hard to reproduce systematically ...
I've reported it the last month, but I can't reproduce it now, so I thought it has been fixed,
apparently not fully fixed ...

[Sewie]

I'm very glad everyone's pitching in and trying to help. (Not so happy with this bug, though...)
I'll try and see if I can find a way around it using your suggestions, Peter. Thanks.

[Peter Wassink]

Btw, as we say "the most of the time, bugs are situated between the chair and the keyboard

hehe...

i'll send TVP the bug project and hopefully this can be solved!