Bug report - RenderFinished event Vegas 18 (builds 284 and 334)

mickhardy wrote on 9/24/2020, 3:13 AM

The RenderFinished event fires twice, the first time with args.Status == RenderStatus.Complete and a second time with args.Status == RenderStatus.Rendering.

This does not happen for Vegas 9 through 17.

Comments

mickhardy wrote on 10/7/2020, 11:13 PM

The workaround is to unhook the event from within the handler.

I've simplified the steps to reproduce it. It also occurs using the asynchronous BeginRender method.

Save the included script as "C:\Program Files\VEGAS\VEGAS Pro 18.0\Script Menu\RenderFinishedIssue.cs"

  1. Copy an mp4 file to "C:\Test\Test.mp4"
  2. Open Vegas 18
  3. Run the script | Tools | Scripting | RenderFinishedIssue
  4. In Vegas 18, two messages are displayed, "completed" and then "rendering"
  5. In Vegas 9 through 17, only the first message, "completed" is shown.
using ScriptPortal.Vegas;
using System.Windows.Forms;

public class EntryPoint
{
    public void FromVegas(Vegas vegas)
    {
        const string testMedia = @"C:\Test\Test.mp4";
        const string testRender = @"C:\Test\Rendered.mp4";
        const string testRenderer = "MAGIX AVC/AAC MP4";
        const string testTemplate = "Internet HD 1080p 25 fps";
        
        var videoTrack = new VideoTrack();
        vegas.Project.Tracks.Add(videoTrack);
        videoTrack.AddVideoEvent().AddTake(new Media(testMedia).GetVideoStreamByIndex(0));
        
        var template = vegas.Renderers.FindByName(testRenderer).Templates.FindByName(testTemplate);
        var renderArgs = new RenderArgs(vegas.Project) {RenderTemplate = template, OutputFile = testRender};
        
        vegas.RenderFinished += RenderFinishedHandler;
        vegas.Render(renderArgs);
        vegas.RenderFinished -= RenderFinishedHandler;
        
    }    

    private void RenderFinishedHandler(object sender, RenderStatusEventArgs args)
    {
        MessageBox.Show(args.Status.ToString());        
    }
}

 

altarvic wrote on 10/8/2020, 7:18 AM

I confirm

@VEGASDerek

VEGASDerek wrote on 10/8/2020, 7:35 AM

We are already aware of this problem and have a fix which will be in the next update.