@Former user

That's an interesting question. Users (me included) complain that preview usually falters during transitions. While KwikPreview in HappyOtterScripts or the native RAM preview is OK, you still have to set the selection loop. The RenderEvents tool in HOS can render events, a loop region, regions, or the entire project. It would seem pretty simple to add an option to render just the transitions and add those pre-rendered events back to a new track. Even simpler, write a script to create regions for transitions and just use the existing tool. In any case, I'll give it some thought.

Sounds neat, Wayne!

I would use that.

WWAAG, that would be great. Although I am still on V12 so I don't think I can use any current scripts. As fr0sty points out, it would need to ignore any event effx and only look at transitions and maybe titles.

@Former user

HOS supports Sony V12 and V13, as well as later Magix Versions.

Sorry, I guess I haven't been paying attention. Good to hear.

@wwaag - Luv it! Stayed up and watched Recording og SUPER BOWL. Ate Popcorn, drank COKE and generally misbehaved. Best SB since I started watching back in ‘84. Now, when I’ve rested, Waynster, I’m gonna smash your ScriptZips. I do hope MAGIX recognises just the extraordinary resource they have in you. I’ve got further “cah-razie” ideas for you.

Nice script. I am not sure about the adding another track approach, but it may work. What happens if you have another track above with for example titles? In Vegas, you have to option to pre-render and it creates a temp file that plays when it reaches the effect. This is indicated by a black line above the effect but changes nothing on the timeline itself. I appreciate your efforts, just playing devil's advocate.

And continuing in that role, if you change one of the transitions after the pre-render, what happens? Do you have to manually delete the render? Does it create a new track for the new pre-render?

@Former user

"What happens if you have another track above with for example titles?"

That's not a problem.  If you look at the demo again, you will see that a temp track is created and the original events are "copied" to the temp track.  Inside of RE, there are options to choose whether pan/crop, Fx and other settings are to be maintained.  The first time you run RE, the rendered track will always be on top.  You must move that track to the desired location (usually the track above the target track).  For subsequent runs, it will first search for a track named "Rendered Video" and render to that track.

"if you change one of the transitions after the pre-render, what happens?" Simply re-render the one transition.

Here's a demo that I think addresses both questions.

Note that the option to select which regions to render will be available in the next build.

That covers some of it. You did have to manually delete the pre-rendered effect that you changed. Not ideal, but workable. I still like the temporary file pre-render idea better, but this could work.

@Former user

"You did have to manually delete the pre-rendered effect that you changed. Not ideal, but workable"

No. You don't have to. It will simply place the new transition on "top" of the previously rendered transition, but having clips "hidden" is not a good editing practice IMHO.

It then becomes a take, which may not be bad if you want to compare transitions. I am not being critical of your work, I appreciate it, just trying to think everything through. I like Vegas using the temp files so when changes are made, you just re-render, no moving of tracks or such. It is just different than your approach, not necessarily better.