Vegas Pro 15 + NeatVideo 4.7 as Media FX/Event FX -- no frames

fifonik wrote on 3/9/2018, 4:55 PM

In VP15 (build 311, have not checked in previous builds) when NeatVideo plugin applied as Media FX or as Event FX before Pan/Crop there are no frames displayed in NeatVideo profile configuration page (marked with red rectangle on the attached screenshot).

If NeatVideo applied as Track FX, Output FX or as Event FX after Pan/Crop -- everything works as expected.

In VP13 there is no such issue and frames displayed in all cases.

Is it Vegas or NeatVideo bug?

Thanks.

Comments

Grazie wrote on 3/11/2018, 12:43 AM

@fifonik : Repro-ed.

Hmm... I'm running W7 and NV4.6 on VP15 Build321. So it is a consistent error over the two OS and with different NV releases. In which case we have convergence, and indicates a BUG.

Is it possible that the Cache requirement for Prior to Pan/Crop hasn't been updated either by NV and/or MAGIX? But yes, this isn't how I'd expect it to behave compared to VP13.

Very odd behaviour indeed.

Good catch!

fifonik wrote on 3/11/2018, 1:26 AM

@Grazie thanks for checking.

I've reported this into NeatVideo forum as well.

However, as there is no the issue in VP13, I think this a VP15 bug (I do not have VP14 to check).

Grazie wrote on 3/11/2018, 3:56 AM

However, as there is no the issue in VP13, I think this a VP15 bug (I do not have VP14 to check).

@fifonik : I have VP14 - re-proed too. I'd think this is kinda serious? Unexpected behaviour points to some breakdown in communications.

@fifonik : I'll nip over to VLAD's Pad ! 😎

Grazie wrote on 3/11/2018, 4:06 AM

Done!

Grazie wrote on 3/16/2018, 7:03 AM

Vlad has responded. NV have reproed the issue.

fifonik wrote on 3/16/2018, 9:41 PM

Reported to Magix, Ticket#2018031717000854

NickHope wrote on 3/29/2018, 3:38 AM

Does the GPU acceleration of video processing setting have any effect on this?

fifonik wrote on 3/29/2018, 5:32 AM

Nope.

Disabling GPU in VP15 Preferences does not resolve the issue.

I do not have VP14 to check.

In VP13 the GPU is enabled with no the NeatVideo issue.

P.S. I'm afraid that the issue not only cosmetic. NeatVideo could have bigger problems as it might not have access to next/prev frames and so the Temporal filtering does not work as expected.

UPDATE:

NeatVideo developers confirmed that this is the only "cosmetic" issue and internal processing is not affected.

matthias-krutz wrote on 3/29/2018, 6:25 AM

The error also occurs in VP14. In MSP12, it still seems to work. Tested with Neat Video 4.6.0.

fifonik wrote on 5/25/2018, 6:39 AM

The issue still not fixed in VP15 build 361

Grazie wrote on 5/25/2018, 10:27 AM

The issue still not fixed in VP15 build 361

Well, it would appear it is fixed in B361 with NV 4.7:

Looks as if MAGIX and NV have done something. All the Identifying Frames are revealed.

fifonik wrote on 5/25/2018, 5:16 PM

Hm. Have you moved NeatVideo plugin before Pan/Clop in filters chain?

Grazie wrote on 5/26/2018, 12:05 AM

Hm. Have you moved NeatVideo plugin before Pan/Clop in filters chain?

Oops! 😬 I’ll go and check ...

Grazie wrote on 5/26/2018, 12:37 AM

Ugh . . Still the same - apologies . . . 😞 :

Grazie wrote on 5/26/2018, 1:24 AM

I've just updated the NeatVideo Forum and requested another knock on MAGIX's door. It's now 2 months and 2 Build Updates later.

NickHope wrote on 10/27/2018, 1:54 AM

This is fixed in VEGAS Pro 16 Update 2 (build 307).

Grazie wrote on 10/27/2018, 3:22 AM

Cheers Mate!

fifonik wrote on 10/27/2018, 5:08 PM

Thanks.

I wish they backported the fix to VP15.

fifonik wrote on 11/29/2018, 7:33 PM

Confirming that the issue is fixed in VP15 build 416 as well.