Rendering NewblueFX Time Clock plugin NOK in vegas 14

bitman wrote on 2/5/2017, 1:41 PM

The NewBlueFX TIME CLOCK works in the timeline edit/play correctly when adding it to a still picture, but after the final render, when playing the rendered result file in a media player, the clock values in the picture do not count up (or down), they keep the same begin value. I noticed during rendering, it also does not seem to count up or down. This is on Vegas 14, can someone confirm this? Or try on Vegas 13. I tried it on another NLE (Magix pro X) and there it is working. I will experiment more. Render is to 1080 50p (I am in a PAL country). I tried render with and without gpu.

Videocard: Titan-x, 16G mem, OS:win 10 (64), i7 4790k, Vegas pro 14 patched to latest.

Comments

bitman wrote on 2/6/2017, 1:41 PM

I have been experimenting a bit more, and whilst I think this is a bug in Vegas, I found a work around (other than using another NLE like Magix pro X). As said before using the NewBlueFX time clock onto a still jpg in Vegas 14 does not render counting digits up (or down), I found that Vegas 14 does seem to render movie clips correctly with time clock plugin. So the workaround I found is:

First to render the still (e.g. jpg) to a movie clip.

Next import the movie clip into the time line (and delete the still from the timeline)

Next apply the time clock plugin on the clip.

Next render again to movie (with successful count up or down).

A bit annoying, but it works.

dxdy wrote on 2/6/2017, 4:10 PM

Not sure what you are trying to achieve, but could one of Vegas' timecode FXs do what you want?

bitman wrote on 2/7/2017, 12:25 PM

Not sure what you are trying to achieve, but could one of Vegas' timecode FXs do what you want?

Yes, I know Vegas timecode FX, but it is very limited in use. It is basically a helpful frame, time or second count tool to add this info in your video. The newblueFX time clock is more a true media contend creator tool (although it is listed under videoFX tab). With newblueFX you can have different styles of digits like chalk, neon, digital, stencil, ticker etc.. I can also be located and sized anywhere, can count up and down, can start from a certain offset, mask the background, select color of foreground and background, overlay or not, select digit separator, you get the picture :)

bitman wrote on 2/9/2017, 4:06 AM

I have submitted the bug to the official magix vegas.

Marco. wrote on 2/9/2017, 7:30 AM

I would assume a still picture - by its very nature - can have only one timecode value. It is only one frame, repeated.

So maybe the FX behaviour depends on where you apply the FX and I would try using it as Track FX, instead of Event or Media FX.

Marco. wrote on 2/9/2017, 8:24 AM

Oops, just tested. Yes, there is a bug using this NewBlueFX timeclock plug-in.

Used as Event FX it works as it should only when I step through the Event frame by frame. But if I playback the Event the count suddenly stops and from then only one value will be rendered/displayed.

Used as Track FX or as Output FX it always only renders first value.

bitman wrote on 2/17/2017, 8:08 AM

Magix vegas has replied to my bug: they did not acknowledge nor deny it is a bug, but just gave another workaround - place a (any) video above the track with the still image and apply the time clock plug in on the video. Indeed this works as well, as a workaround that is...

Marco. wrote on 2/17/2017, 8:22 AM

I think the bug is in the plug-in rather than in Vegas Pro. So NewBlueFX would need to get acknowledged and fix it.

bitman wrote on 2/18/2017, 2:49 AM

I think the bug is in the plug-in rather than in Vegas Pro. So NewBlueFX would need to get acknowledged and fix it.

Maybe, but I do not think so. I tried the Newblue plug in on 2 other NLE's in my possession, Magix Pro X, and Corel Videstudio X9, both render it correctly on a still jpg... (albeit corel uses the native version, non-ofx)

pin-b wrote on 12/19/2019, 2:17 AM

you can fixde it by clik the Time Clock panel-"about" and open the "NewBlueFx App Manager",and close the disable GPU for Elements.

i just render OK in this way.

altarvic wrote on 12/19/2019, 6:05 AM

@pin-b what's the point to answer to 2+ years old topic?