[Kevin Skow]

Yea, editing the registry was a joyous task. That plug-in wasn’t for the faint of heart. I don’t miss that program much at all, but I do still have the old installer files lying around for nostalgic value.

[Kevin Skow]

Thanks for the tips and help!! I’ll give these settings a whirl here in the next few days and see how they pan out. It’ll be plenty of trial and error, but that is how we learn :-). The burned pixels on the camcorder video were about 5 x 5 pixels in size, which is pretty bad. There were about 3-4 of these bad pixels in the video. The good news is that I primarily film landscapes and sky scenes, so the plug-in does perfectly fine there.

[Kevin Skow]

Ok, thanks. I’ll contact Sony about it.

[Kevin Skow]

An update to my previous post:

The only issue I’ve run into so far with the plug-in is that it can “smear” the edited area when it contains a high degree of detail, or when there is a sharp cutoff between a bright and dark region within the edited area. Adjusting the blur and blend radii down temporally over these problem areas seems to help a bit. Still, overall a wonderful plug-in.

Do you have any trips or tricks to further reduce this smearing effect? This is likely a far-fetched request, but would there be a way to have the plug-in intelligently map pixels if there is a high contrast scene under the edited region?

For example, in one of my video shots I was panning past a light pole (which was dark against a bright sky). Likewise, the dead pixel also moved across the light pole. When I applied the PixelPatcher plug-in, the region around the pixel became smeared as it moved over the light pole due to the plug-in interpolating the bright and dark areas across the entire edited region.

I just thought I’d throw this suggestion out there in case you wanted to tackle it. I’m not much of a programmer so I don’t know how hard this would be to code up.

Thanks again for making this plug-in!

[Kevin Skow]

Hi Mark-

I had a sensor issue with my Canon XH A1s camcorder last year and shot quite a bit of video with bad pixels before I realized the sensor had failed. The sensor has since been fixed (fingers crossed it doesn’t die again), but I had no real easy way of fixing the bad video.

There was a similar program that came out for Vegas Movie Studio 9 (on 32-bit OSes) called the Stuck Video Pixel remover, but the program was never updated to work with 64 bit operating systems or the later versions of Vegas Movie Studio or any version of Vegas Pro. Plus it was a very tedious program to work with, since you had to input the coordinates of each bad pixel into a text file for the program to read. The site that hosted the program has since gone offline, and I no longer use a 32 bit system to edit my videos.

I decided to give your plug-in a whirl. Since I didn’t have a completely black video frame to work with, I created a black image with the same resolution as my video project in Photoshop and transposed the hot pixels from one of my “contaminated” shots onto the image. I subsequently ran your plug-in in Vegas Pro 11 using this image and it wiped out the bad pixels with no problem!! It also doesn’t slow down the rendering process much at all, which I really enjoy.

Now I can spend hours going through my old videos and finally clean them up 😀

Thanks so much for creating this!!
Kevin

[Kevin Skow]

Steve-

By “feather”, I meant that the transition featured a gradient between the two scenes. For example, under the Linear Wipe transition folder, any of the transitions labeled with a “Soft Edge” or “Blend In” contain this gradient. The depth of this gradient is controlled by the “Feather” control in the transition’s properties dialog box.

I’ve attached a zip file containing a .veg project using one of these transitions, and a .wmv video of the same project. I made the transition quite long to emphasize the jumps at the beginning and end.

3684_transition.zip

Here are the specs of my computer system:
Asus P6X58D Premium LGA 1366 motherboard
Intel Core i7 970 Six Core Processor
24.0 GB Corsair triple channel memory
Nvidia GeForce 550Ti (1 GB) Video Card
150 GB Western Digital VelociRaptor 10,000 RPM Sata HDD
(Data is stored on two 1 TB Seagate HDD)
Windows 7 Ultimate x64

Kevin