@RedRob-CandlelightProdctns Does it matter which Preview option is chosen? I don't have Neat but I know Boris recommend (Full) for Vegas & AE when using Mocha ..

I have it set to Best (Full), and I haven't changed that value in any of my tests.

Project setting also has Full-Resolution Rendering Quality set to Best, and render templates are set to use the project settings.

Curiously after changing it to Preview (Auto) after reading your question, I forgot to change it back to Best (Full) and timeline playback started doing that same 1/4-preview jumping thing -- on a 1080p (not 4K!!) clip, while legacy decoding was turned on.

So maybe there are two different problems at play here?
 

@RedRob-CandlelightProdctns Ok, it was just a thought 👍

@RedRob-CandlelightProdctns Sorry you added to your msg,, yeah something fighting something else.🤷‍♂️.

Just another thought ... I rarely use the Preview (Auto etc.) option, my PC is happy @ Good (Half) for UHD media & proxies are turned off. But occasionally I'll test someone else's file that struggles in VP, I'll turn proxies on or create proxies for that file & then put the display to Preview (Auto etc.) .

Like I say I rarely use proxies so.. are they a lower res.? Do you use proxies?

What happens when project settings are 4k and what happens when you render that 4k project with a 2k rendertemplate?

Like I say I rarely use proxies so.. are they a lower res.? Do you use proxies?

@Gid Are you asking if this project is using proxies?

No -- this project isn't using any proxies.

When we have a lot of 4K media and 8 cam running editing MC, I'll sometimes build lower-rez 720p proxies and swap them in, then swap back to the originals later (not using Vegas-built proxies due to meh-quality and slow speed-to-build)
 

What happens when project settings are 4k and what happens when you render that 4k project with a 2k rendertemplate?

@3POINT Well at minimum it'll be upscaling the 4 cameras which were shot 1080p.

When you say "what happens when...." -- what are you looking to have me inspect? Are you asking if I don't use the legacy decoder and set the project/render that way, if it still has the 1/4-screen problem show up? Or wondering what Neat Video will show in its general properties?

I'm working on it --- just takes me 5 minutes each time I reconfigure Vegas's "legacy I/O" settings since most of the time after applying the changes and exiting Vegas, it lingers and I have to kill the process which results in my config changes not saving. So I repeat until it finally saves and I can run the test.

 

I have the same problem with twixtor. What i found best to work for me, except changing the decoder, is moving the effect after the pan/crop.Try that out.

It will treat the video as 1080 not 4k , but hopefully show the video in fullscreen and not 1/4.

There is definitely something wrong with the new decoder.

What happens when project settings are 4k and what happens when you render that 4k project with a 2k rendertemplate?

• Project set to 4K 29.97.
• Legacy Decode is not being used

@3POINT

Here's what I see -- and I can't explain or understand why I'm getting these results:

1. Neat reports my 4K event as being 4K (3840x2160)
2. Neat reports my 1080 clip as 1920x1080
3. Rendering using "Internet UHD 2160p 59.94 fps" (AMD) template gave an error immediately.
   
   
   Tried again without using the AMD version and that rendered. Result was not good. There are 3 events being rendered in the sequence
   1. first event (1080p Canon G70 source) has Neat, Vegas Video Stabilization and Sharpen. The image is completely frozen (single frame), but moves around a bit (the stabilization)
   2. the second event (4k Canon G70 source) has Neat, rendered mostly OK but glitched somewhat
   3. the 3rd event (1080p Canon G60 source) does not have Neat and rendered OK
      
      Here's how it rendered:
      
      
      For perspective, here's how it *should* have rendered. This one is from earlier with legacy AVC decoding enabled, 1080p60 project and 1080p60 render:
      

I tried neat video also. As i always use it after all other effects or at track level , i have never seen that behavior.

But moving it before pan/crop as in your image, it indeed shows the behavior you described above. So moving it after pan/crop solves the problem until a better version of the new codec become available.

I have the same problem with twixtor. What i found best to work for me, except changing the decoder, is moving the effect after the pan/crop.Try that out.

It will treat the video as 1080 not 4k , but hopefully show the video in fullscreen and not 1/4.

There is definitely something wrong with the new decoder.

Good info. as a candidate of a workaround.

My thinking has been that it's best to remove the noise in its native 4K resolution, apply temporal sharpening within Neat and then add a touch of extra sharpening if desired back in Vegas. Seems to me that shrinking it along with its noise to 1080, then reducing noise and sharpening, wouldn't be as clean and sharp a result. (maybe I once tested this.. or maybe it's just in my head???!)

I'm editing without legacy enabled then enabling legacy for the render for stability.. seems to be the best combo I've found so far.


WHAT CAN WE DO to Help the Vegas Team continue to improve the decoder, and if this indeed is a bug/findings, get them what they need to find and fix it?
 

> Neat Video v6.5

There is no such version yet, did you mean 6.0.5? :-P

P.S I'm having the same issue

Also i forgot to mention another solution. If you don't want to move after pan/crop, then however strange it sounds do this, it works.

Keep neat video as you have it before pan/crop, but go to pan/crop and zoom just a little, a few pixel. Then the 1/4 screen stops, and neat video shows 4k video instead of 1080.

Its super strange what is going on regardless the new decoder and pan/crop.

> Neat Video v6.5

There is no such version yet, did you mean 6.0.5? :-P

@fifonik  Hey.. I can't help that YOU don't have a TARDIS too 😬

Is this only become an issue with the release of the newest NeatVideo?

@VEGASDerek I honestly don't like tagging you since I suspect it's not proper protocol... and... any insights?

Is this only become an issue with the release of the newest NeatVideo?

I've just tried Neat Video v5 and do not see this behaviour. Somehow they managed to avoid this trap while in General the resolution is still shown as 1920x1080 (wrong, so it is possible that their noise reduction does not work as it should).
We may have better luck asking them to fix this for VP in the same way they doing this for version 5. In my experience they are really good with that (resolved all issues I reported unlike Magix)

Is this only become an issue with the release of the newest NeatVideo?

Great question @RogerS!

With "Use Legacy Decoder" UNCHECKED --

Neat V5 TEST -- On the same 4K event I've been using, I removed V6 and added V5, same position on the FX chain. As expected, Neat detected the frame size as 1920x1080p.

I rendered using the same render settings, and it rendered perfectly.

Neat V6 Re-Test -- For sake of completeness, I removed the V5 version and re-added Neat V6 and re-rendered. The 1/4 secreen problem happened.

SO --

1. it does appear related to Neat V6 and not Neat V5
2. It only happens when using the non-legacy Vegas decoder, but not the legacy decoder

Is this only become an issue with the release of the newest NeatVideo?

I've just tried Neat Video v5 and do not see this behaviour. Somehow they managed to avoid this trap while in General the resolution is still shown as 1920x1080 (wrong, so it is possible that their noise reduction does not work as it should).
We may have better luck asking them to fix this for VP in the same way they doing this for version 5. In my experience they are really good with that (resolved all issues I reported unlike Magix)

I agree that the Neat folks are great and quick to respond; some of their responses to me in the past, however, have essentially said "we take the frames and info Vegas gives us -- if it gives us the wrong info we don't have a way of knowing."

Maybe this will be different? It seems repeatable, which means it should be fixable, ya?

4:30am.. I'm done for now... zzzz

If you haven't reported it to Neat, please do, especially since something has changed. A fix may require engagement from both sides.

If you haven't reported it to Neat, please do, especially since something has changed. A fix may require engagement from both sides.

Done, referencing this thread for info.

@RogerS Can/should you get peeps involved in your Beta circles?

Thanks for doing that.

Problem is who if anyone has version 6. I don't yet.

Get some rest : )

Thanks for doing that.

Problem is who if anyone has version 6. I don't yet.

Get some rest : )

A side note: Neat Video v6 is much faster then v5. I like it very much.