V12 Color Match performance issue

TeeTime wrote on 11/20/2012, 8:26 AM
I like the new Color Match fx, but here is a caveat to be aware of. Performance really degrades with multiple color matched events on a single track. Move each color matched event to their own track and performance is not impacted.

To demonstrate, I did this:

1. Placed a 15 minute AVCHD clip from my HMC150 as the only clip on the timeline.
2. Split the clip into 15 events on the same track.
3. Applied color match to one event and copied/pasted the attributes to the remaining 14 events.
4. Adjusting the edge of an event would take 10-15 seconds for Vegas to respond, whereas before the color match it would be instaneous.
5. Duplicating the track required about 12 minutes for Vegas to respond.

I then repeated the experiment except I put each of the 15 events on their own track, and then applied the color match to each. Adjusting the edge of an event was near instaneous as was duplicating a track.

I discovered this because I edited a 23 minute video that had approximately 25 events on a single track. I then color matched all to a single frame and editing performance severely degraded.

My system specs here are current.

/jerry

Comments

videoITguy wrote on 11/20/2012, 9:45 AM
TeeTime: This is a very interesting finding you have made. HAVE YOU noticed the corresponding file size of your project VEG.

In other word applying colormatch to a single track would generate HUGE file size in the saved project VEG.

What is the difference in size of your treatment of color match in the corresponding VEG?
BruceUSA wrote on 11/20/2012, 9:49 AM
I found that you cannot copy and paste event, the color match will degraded badly. What I did is to color matched one event and then saved that as a preset, then you can just drag and drop that preset onto your new video clips. Hope this help.
set wrote on 11/20/2012, 9:52 AM
You may want to consider using half size quality instead of FULL size, this also differ the file size of VEG project.
Peter Riding wrote on 11/20/2012, 10:57 AM
Thanks for the heads up Jerry, I think I'm going to leave Color Match alone until the next update (re our other recent thread discussion). I also noticed a huge increase in the .veg file size plus it would take several seconds to complete a simple save as instead of being instant.

Pete
TeeTime wrote on 11/20/2012, 8:46 PM
Bruce, in my original project (not the test project I described here) I was not copy and pasting events. Instead, I put my source frame in the trimmer, then applied color match to each of my timeline events separately. I did experience the slow down using this approach. Is this different from what you are experiencing?

/jerry
BruceUSA wrote on 11/20/2012, 9:15 PM
Jery,

I did in fact experienced very painful slow rendering color match at first. I kinda gave up. I later decide to update my nivida driver (gtx260) all the certain I now got gpu working which never worked before. On top of that , now color match rendering is normal and is fairly fast as well. I am running an old i7 920 with 12gb of ram. Perhaps you should update your video card driver. Just a thought.
TeeTime wrote on 11/21/2012, 7:08 AM
I may do that Bruce. But one difference for me - the rendering wasn't slow, just the editing. Vegas would go "not responding" with any attempt to change any of the color-matched events. For a simple change to the end fade of an event it might take 10 seconds to respond.

/jerry
Tom Pauncz wrote on 11/21/2012, 9:26 AM
Jerry,
I really think that the the VEG file bloat is the cause of the slow changes.
Tom
Peter Riding wrote on 11/22/2012, 4:52 AM
I have a project comprising 6 sub-projects which are then nested into the master project. Each of the sub-projects has many events from up to four cams on different tracks. Separate audio as well. The initial edits were done using Multi-Cam. Total project length around 85 minutes.

One of the sub-projects had Color Match FX applied to the clips for one camera on one track. I was able to render this sub-project as an MP4 on its own.

But rendering the master project was hopeless. Would freeze after many hours of rendering. I was not doing anything I have not done many times, the only variable was that it is the first project in which I've used Color Match FX.

I went back in and removed the Color Match FX from all clips.

Now the master project renders fine. So I reckon Sony has some work to do on that new feature.

Pete
Poppieworks wrote on 12/5/2012, 5:45 PM
I love the Color Match plug-in, but as observed above it does have performance issues. It took me a while to figure out that Vegas Pro 12 responded extremely slowly moving events on the timeline after I used the plug-in a few times.

I believe it has to do with the file size of the .veg. To give you a comparison, I saved two versions of a file: one with Color Match and one without.

The .veg without Color Match Is 398 KB. The file with Color Match is 97,602 KB (97 MB)!

I hope that Sony will find a solution to this. For the time being, I finalize the editing of a video and then I save a copy of the .veg to apply Color Match. This is certainly not ideal, but perhaps a good workaround while Sony is looking for a solution to this problem.

Cheers,

Gregory
set wrote on 12/6/2012, 6:19 AM
My only guess is that Color Match need to store the reference image for matching INSIDE the VEG project file.
If I can suggest the solution, perhaps by saving image and just 'link' the image, just like Gradient map transition reference image.

I like the feature, but if I have to copy-paste to so many events on the project...
Poppieworks wrote on 8/2/2013, 9:34 AM
With the latest Sony vegas pro 12 maintenance build 670, the problems with the color match plugin have been resolved:

"Improved the Color Match plug-in to prevent an issue that could cause .veg file sizes to grow significantly for each instance of the Color Match plug-in."

If you have large .veg files because of the color match plugin, all you need to do with the new build is to load them in Vegas Pro and press ctrl-s to save and the size of the .veg file will be back to normal.

Greg
missionrec wrote on 8/2/2013, 5:39 PM
Is anyone seeing color match create changes in color during fade outs? For instance, whit candles going blue during a fade? If I do hard cuts, no problem. Only fades.. ???

fr0sty wrote on 4/17/2017, 2:50 AM

I'm having this issue in VP14. If I use the color match plugin, any fades turn a blue color during the transition. The only workaround is to fade using composite rubber bands, however that method is very time consuming. Here's how it should look vs. how it currently looks.

Marco. wrote on 4/17/2017, 4:04 AM

Did you try using color match as Media FX instead of Event FX?

Christian de Godzinsky wrote on 4/17/2017, 4:12 AM

Hi,

The same color issue here with the color match filter!! Fading in/out a clip is unusable. Workaround (using envelopes) is possible but very cumbersome and slow. Color error during fades makes this filter useless. Only 0 and 100% gives correct results! Arranging the order in the filter chain (before/after the composite) does not help. Amazing that such a basic function is dysfunctional. Makes me wonder about if testing is done thoroughly enough before releases? Not very pro...

Would have added a pic but when this forum only supports it by linking I did not have time. Maybe later.

VP14 b.252 on WIN10 Pro N 64-bit. 24GByte RAM. Ati Radeon R9 280X GPU.

Would like to get it confirmed that this is on the bug list and will be fixed in the next build... Seems to be many of us that can confirm a problem here.

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

NickHope wrote on 4/17/2017, 5:24 AM
Would have added a pic but when this forum only supports it by linking I did not have time. Maybe later.

NickHope wrote on 4/17/2017, 5:40 AM

In my brief testing it's working well for me in VP14 build 252 with UHD GoPro footage, even during cross dissolves. The veg file does increase from 12 to 284KB however.

Would like to get it confirmed that this is on the bug list and will be fixed in the next build... Seems to be many of us that can confirm a problem here.

To achieve that you'd almost certainly have to submit a report request. That's still the best way of drawing the devs' attention to bugs. Yours is only the 3rd report that I know of (after the 2 above yours), so there's every chance it's not on their radar or in their backlog yet.

Christian de Godzinsky wrote on 4/17/2017, 7:48 AM

Hi,

Thanks Nick for the comments. Here's the picture:

This video is from GoPro Hero 5, 1080p 50fps. Left side is fade in at 50%, right is how the original image looks like (100%). I will certainly submit a report. Thanks.

Christian

 

PS: My color match filter is on the TRACK level (the only clever place where to put it in this project).

Last changed by Christian de Godzinsky on 4/17/2017, 7:56 AM, changed a total of 1 times.

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

fr0sty wrote on 4/17/2017, 10:04 AM

I should point out my footage is AVCHD coming from a panasonic HMC-40, I've seen it happen to footage from a GH4 as well as GH2, both MP4 and AVCHD. I have not tried using it on anything but Track FX. However, using it on Media or any other FX chain would not be practical, I need all of the video on that track to be affected by it, otherwise I'm stuck having to re-apply the effect every 4.4GB file I get from that camera, which would be time consuming.

NickHope wrote on 4/17/2017, 9:23 PM

Could someone possibly upload to a cloud service a small zipped .veg project that demonstrates the problem? Other users could test/verify it and it would be useful for the developers.

fr0sty wrote on 4/17/2017, 9:37 PM

Here's an example. The two shots on the timeline were both shot by the same camera in the same room, so of course there isn't anything for the color match plugin to do, but it does showcase the glitch none the less. During the transition the colors will all shift towards blue, almost inverted looking.

 

https://drive.google.com/open?id=0BwKM6eSvC3wqekJsSTVJWWtCZ3c

 

Edit: I just realized I faded the same shot onto itself, and color matched the same shot onto itself as well, lol. Either way, it still illustrates what happens when editing using different cameras and clips.

NickHope wrote on 4/17/2017, 9:49 PM

Thanks. It's caused by GPU acceleration of video processing. When that's turned off there's no issue:

My GPU is AMD Radeon HD 6970.

I submitted a support request, [Ticket#2017041817002145].

fr0sty wrote on 4/17/2017, 10:23 PM

Ok, that's a pretty easy workaround as well, just turn off the GPU before rendering. I wish I had known that the other night, it would have saved lots of time! lol. Thanks!