Page 1 of 2

Bug Neat Video with Premiere CS6

Posted: Fri May 18, 2012 10:24 am
by DMD
Good day.
I have a problem with Premiere CS6, before asking for help to this forum I have done several tests on 2 different PCs, and the problem has always been noted. (Using the latest version 3.2)

test No. 1
The problem is that by applying the plugin to a video sequence that runs smoothly with no problems.
But if I make the cutting of the same sequence with the plugin applied, I get artifacts that never existed before.

Test no. 2
I imported the video sequence in the tme line, I made ​​the cutting and after I applied the plugin, getting the same problem.

test No. 3
I imported 2 sequences in the time line, then I made ​​the union (nesting) and then I applied the plugin, found the same problem.

This roblema can be solved?

These are the screen:

Screen before the cutting
Image

Screen after the cutting
Image



Screen before the cutting
Image

Screen after the cutting
Image




THANKS

Posted: Fri May 18, 2012 11:36 am
by NVTeam
We will need to see a reproducable test case (or cases) that we can run our test computers to directly see the issue.

Please prepare one or two test projects with 1-2 short clips (you can use our testkit's clip if you like) and with NV applied. Pack the project files and clips used in the projects into a single ZIP (please keep it below 20MB) and e-mail it to support [at] neatvideo.com. Please also include a step-by-step instruction on how to reproduce the problem(s) using the test projects, after opening them in Premiere CS6.

Please also check the same projects in CS5.x to see if the problem is specific for CS6 or not.

Thank you,
Vlad

Posted: Fri May 18, 2012 12:41 pm
by DMD
OK!
I sent the two reference clip with extension (. M2v), the noise profile, which I took as a reference and the screen of Premiere CS6.

Image


In version CS5/5.5 everything works properly, the problem does not exist.

THANKS

Posted: Fri May 18, 2012 3:12 pm
by NVTeam
Thank you for the test data, we could reproduce the issue. We will look into it in more details to find out who is causing the problem. There is no problem in CS.5 indeed. Might be a bug in CS6, as we could reproduce it without NV as well, using another plug-in.

Vlad

Posted: Fri May 18, 2012 3:54 pm
by DMD
If indeed it were proved that it is a bug in CS6 and given the importance of the work it does the plugin.
Neat Video would be appropriate, as official leader and manufacturer of the plug, must convince Adobe to release an update patch as soon as possible.

Posted: Fri May 18, 2012 4:16 pm
by NVTeam
I have reported this issue to Adobe. Convincing a big corporation to do something is a completely different matter. :-)

Vlad

Posted: Sat May 19, 2012 4:32 pm
by DMD
There is also another important aspect, if Adobe does not solve the problem, Plugin can not be said for working Premiere CS6.
So in the characteristics must specify which version works properly, and this is a serious limitation.

Posted: Fri May 25, 2012 9:35 pm
by NVTeam
Adobe confirmed that they could reproduce the problem with Premiere CS6 and one of the Premiere filters. No Neat Video was used at all, the problem was reproducable using Premiere alone, which indicated a bug in Premiere. Now that Adobe is aware of the problem, I think they will fix it in one of the regular updates of CS6.

Vlad

Posted: Fri May 25, 2012 10:32 pm
by DMD
THANK YOU for having the problem with ADOBE. :)
Neat Video as an important partner, could not remain unheeded.

Posted: Sat Jun 02, 2012 10:47 am
by DMD
Same problem with the 6.0.1 update :(

I await the next upgrade, while continuing to work with version CS5.5

Posted: Sat Sep 08, 2012 5:29 pm
by DMD
It seems that Adobe does not want to solve the problem.

Even with the patch 6.0.2 the problem remains :roll:

Posted: Mon Oct 08, 2012 7:14 am
by DMD
This fact I'm sorry. :cry: :x

Even with the third patch (6.03) the problem is not solved, so I can officially say that NeatVideo with Premiere CS6 generates artifacts, so is not compatible with this version.
This limitation must be specified in the characteristics

Posted: Mon Oct 08, 2012 9:37 am
by NVTeam
Lets remember that it is Premiere who generates the problem.

I repeat, we reported the issue to Adobe and they confirmed that they could reproduce the problem with Premiere CS6 and one of the built-in Premiere filters, without any Neat Video at all. Which clearly indicates a bug in Premiere CS6 itself.

Please write to Adobe, let them know that you are unhappy about the way bugs in Premiere are not fixed for so long. You are their customer, they must be interested in your opinion.

I agree that if they don't fix it then Adobe should specify that bug in the documentation of Premiere CS6.

Thank you,
Vlad

CS6 bug with neatvideo

Posted: Wed Nov 20, 2013 12:48 pm
by imagine11
Did adobe ever address this? If not, does anybody know which of Adobe's own internal filters exhibit this problem? I'm thinking that if we are going to ask Adobe to address this issue, it'll be a lot easier to get them to make their own filters bug free before they consider fixing it to make a third party plugin work.
Thanks,
Andy

Posted: Wed Nov 20, 2013 1:27 pm
by NVTeam
That bug initially found in Premiere CS6 was reported by Neat Video team to Adobe back in May 2012. Adove reproduced and acknowledged the bug at the time. It was filed by Adobe staff as bug BG133583. After that, we several times reminded Adobe about that bug and asked them about its current status.

At the time of the release of CS7 (CC), the bug was still not fixed neither in CS6 nor in CS7. I can see that it is still present even in the latest update of CS7.

The other plug-in that allows to directly reproduce the problem is the Simple Video Filter from Premiere SDK - the software development kit provided by Adobe to developers of plug-ins to help them build their plug-ins using examples created by Adobe engineers.

The bug seems to be is in a specific part of Premiere's API that is used by certain class of plug-ins, so it is only affects Premiere when a plug-in from that class is used. Still, the bug is in Premiere itself and there is no other way to fix it than to fix it in Premiere itself.

Vlad