Graphics

So, here's a new one...

I have a group of scenes I am testing in sequencer. As I am putting things through their paces, something will 'break', meaning I must have an issue in my VL somewhere. So, I go back to Layout, call up the same condition set as that which broke in sequencer, and all is working fine there. Then without actually adjusting anything, I toggle back to sequencer, and boom, it works again.

Um.. what?

Update. This issue I am seeing seems to limited to sequencer's preview panel. If I take a seemingly broken condition online, it plays fine. So the issue - or perhaps it is a bug - seems to be that Preview is only accurately displaying whatever state the element is in in Layout mode. Since I am using a virtual output when I take online, this inconsistency concerns me as I don't know if a 'proper' output will reflect the virtual output, or the preview. It also could mislead an operator into not taking an element because the preview looks 'broken' even if it would play out fine, they would have no way of knowing that.

This issue only popped up today, and only seems to be affecting the optional topline element of the L3rds at the moment, but it is wholly disconcerting none the less
#XPression

To be more specific, its the telescoping of the topline in conjunction with the bounding box width scaled parameter of the topline text which is giving me this issue. I've restarted both the software, and the computer but the issue persists. I took a video of it with my phone, but I cannot get it below 120mb without the quality making it useless, so I can't very well attach it here.
#XPression

I've had a similar problem where the width doesn't expand in preview with a top line that telescopes. It plays out perfectly fine though. I haven't found a solution to it yet.
#XPression

Well, it gives me some relief to know - based om your experience - that it holds up even on proper 'non virtual' output. I may have to just make sure the operators are informed, so they don't hesitate when the TD says go, and they're looked at a right knackered preview...
#XPression

Seems to be the same issue that was described in this thread : https://discussions.rossvideo.com/forum/default-forum-gc1/xpression-cg-and-graphics-system-gc12/15689-bounding-box-width-question .

#XPression

Seems to be the same issue that was described in this thread : https://discussions.rossvideo.com/forum/default-forum-gc1/xpression-cg-and-graphics-system-gc12/15689-bounding-box-width-question .

No, not really.. though I have encountered the issue of driven text not behaving in the Sequencer the same way it does in Layout, the issue I am speaking to is different. The issue in the thread it's worth noting beaks on both preview and output, but can be quite simply resolved in Logic. The issue I am talking about involves a scene which works correctly in both Layout and Sequencer Output, but not in Sequencer Preview, and appears to have no immediate work around. The scene works, but the operator is not going to be able to guage this correctly in their preview.

#XPression

The issue I am talking about involves a scene which works correctly in both Layout and Sequencer Output, but not in Sequencer Preview.

Check this sample project : TYT_Text_ToUpper.zip

There is an "Author" text object that is converted to upper case with Visual Logic , and "Title" text that should be displayed at the right of "Author" (position calculated from bounding box width ).
It doesn't work on preview, but works in layout and sequencer.
Maybe I've done it wrong in VL ?

#XPression

Great Tip ! Thank you Simon.
#XPression

So, I found the solution, and the underlying reason for the problem. It does, in fact involve Simon's tip about putting a portion of the logic in another window, but it is important to understand why.

Essentially, it has to do with the order of execution of VL. VL is read from Left to Right... Both the individual tabs, and the content within them. So, in my case, I looked at what was displaying incorrectly in Preview - it was the 'telescoping' action of the topline driven by the bounding box width scaled of the text within it. Both the logic covering the autosquueze width of the topline text, and the telescoping action of the topline itself were in the same VL tab. Taking the autosqueeze logic and placing it in the tab BEFORE the telescoping resolved the issue. If I put that tab AFTER the tab with the telescoping logic, it displays broken in preview.

Therefore, when faced with this issue, the key is making sure your logic is executed in the correct order.

Shout out to Andrew Sampson at Rocket Surgery for the insight into the order of execution paradigm
#XPression

Amazing! I already had my logic for determining the text and telescoping the bar separate, but the telescoping tab was left of the text logic. Simply swapping them fixed this problem that I've had for two years! Thanks for the tip Willie (and Andrew Sampson).
#XPression