Is this GL bug?

offonoll's picture

Hi kineme lovers!

I am experimenting a bug with no crashes. Is regarding a GL patches...(I think) so I made a video demonstration to show what's going on on my system.

About the last comment showing a cube, the problem is due to a refresh. You know better than me that if nothing happens to a composition, even I delete a patch it remains the last frame until new data goes through the composition. this is happening to me. don't know if that should be normal or no. And also with GL look at patch, I see the image cuz its the first frame but once the composition runs a number, it goes black.

Also to let you know, I got a mbpro with the latest upgrades.

If you come up with any idea of what happen, that would be very helpful. Thank you mates!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

cwright's picture
Re: Is this GL bug?

This isn't a GL bug, it's a QC "optimization" bug -- if the fps says "N/A", it won't update the viewer even if you've removed renderers. This is wrong, and you should file a bug report.

A work around is to use an LFO somewhere attached to a renderer to give your composition a framerate (remove it when you're done to improve performance).

offonoll's picture
Re: Is this GL bug?

You express it right! and sounds logic about the refreshing. my fault.

I already report a bug, Problem ID: 7542977. I just wanted to know if someone has same problem even they don't know they have it. Normally people don't perform 2 compositions same time.

Thank you chris.

cwright's picture
Re: Is this GL bug?

it happens even if you only have 1 composition open -- I'd be willing to bet that most users have experienced it once or twice on 10.6 ...

gtoledo3's picture
Re: Is this GL bug?

Exactly... take a Sprite while the Viewer is running, and delete it. Whoops...still there! Filed a bug on this long ago.

offonoll's picture
Re: Is this GL bug?

Just to make things clear about the video, there are two issues. A refreshing bug, whitch Chris explained why it happens that;

it's a QC "optimization" bug -- if the fps says "N/A", it won't update the viewer even if you've removed renderers.

and the first part of the video where A and B aren't showing same time.

I guess both are diferent things.