Batch rendering code help needed

Jack S wrote on 2/28/2024, 9:59 AM

@jetdv Edward, I have a problem with my batch render module in my application extension and it's driving me crazy. I'll explain what's happening and see if you can help me.
In my module there's a 'RenderStatus. RStatus = myVegas.Render(args);' statement. The equivalent module in a Forms script works perfectly. In my application extension, VP crashes when it reaches that statement.
The weird thing is, if I place a MessageBox(""); statement just before the RenderStatus statement, the batch render completes with no problem. It seems that the action of clicking OK in the MessageBox allows the render to complete without crashing. I did enclose the render statement in an Undo block but this didn't solve it. The only thing that solves it is the MessageBox statement. The problem with this solution is that it's no good having a batch render tool if you have to click OK before each render.
Any ideas?

Thanks in advance.

Comments

Jack S wrote on 2/28/2024, 10:56 AM

Problem solved (for now anyway). If I use the myVegas.OpenProject(); statement instead of the myVegas.OpenFile(); statement the module works as it should. The problem is, in the API, the OpenProject statement is classed as obsolete. I presume this means that when a new ScriptPortal.Vegas.dll is released the OpenProject statement will be omitted. It seems that there is some conflict between a project that's opened with OpenFile and the same project opened with OpenProject that breaks the render process and causes a crash. This crash is so severe that it's not trapped by a try/catch sequence.

jetdv wrote on 2/28/2024, 11:32 AM

You might try a myVegas.UpdateUI(); statement before the render call.

Jack S wrote on 2/28/2024, 12:45 PM

Thanks, I’ll give it a try.

Jack S wrote on 2/29/2024, 5:03 AM

I reverted to the OpenFile(); statement, then tried placing the myVegas.Update(); statement before the render call. The fault still exists. Then I tried placing it just after the OpenFile(); statement because I check for project content/render type compatibility before doing the render (this batch render tool renders projects from multiple locations so I need to check that the user hasn't selected a project whose content is incompatible with the render template chosen). The fault still exists.
What puzzles me, is that the tool works fine with the OpenFile(); call when compiled as a Form script, but with the exact code base (except, of course, the different code that's required for a custom command), the OpenFile(); call causes a crash. The OpenProject(); call however, doesn't cause a crash.
Could this be an API fault? I'll let others more qualified than me decide on that.
Thanks anyway Edward.