Hi @Kinvermark

I find it very difficult. I've tried everything you can think of with Vegas's native color tools, and you may believe believe that none of them gave such an efficient, rapid and satisfactory result. It may even be my lack of knowledge in using the native Vegas tools of the color tab, but in my point of view the Vegas does not have a very efficient color treatment system. I am very satisfied with 3D Luts, it allows me to make the changes I want, the way I want and with Vegas I was limited in some situations.

I made the post so that vegas users can see that it is possible to do a great colorization in Vegas using the 3d luts without having to change video editor as many have done by migrating to Davince Resolve.

This definitely appears to be far more powerful than Vegas' tools, but for $200, it's only $100 cheaper than the full version of Resolve and doesn't come with motion tracking or some of the other cool tools it features, so I'm a bit torn on which I'd prefer. Not having to leave Vegas is a definite plus.

@Kinvermark watch the video on that page, you'll see it do things you couldn't dream of doing with Vegas CC tools.

@Former user

Thanks for following up. Good info. Quick workflow question: do you make a different LUT for each clip? If so, how do you manage the large quantity of LUT files ( ie folders & naming conventions).

@fr0sty

I guess if one was interested in a LUT based CC workflow, but didn't want to spend $200 or go to Resolve, one could make LUTS I'm something like Affinity Photo.

@Kinvermark

The creation of the Luts will depend on what you want. By inserting a LUT into a Track FX the effect is applied to multiple clips at the same time. If you want to apply to clips individually you should apply on an event fx or FX media. You can create folders for the Luts anywhere on your PC or bins inside the vegas to organize your projects.

@fr0sty I've noticed the Davince tracking which is a great tool, but 3d luts has a mask tool that does not require the use of a drag, since the mask has the function of isolating a specific color without the need of tracing. However, if automatic motion tracking is required, you can also use the Mocah Pro Plugin for Vegas which is a great tool.

Mocha is great, if you can afford it. As for LUTs at the track level, be aware there is a Vegas bug that will cause your fades to look wrong if you use a LUT at track level. Best to use at media or event levels for now until that gets fixed.

@fr0sty

This luts bug in Track FX in Vegas is exclusive to version 15 and only if you use the native LUT Filter fx from vegas. I use versions 13 and 14 that do not have this feature and therefore I do not have this bug because I use Ignite LUT to apply the Luts. VisionColor Luts and Magic Bullet Looks also work but they also have some bugs that made me give up using them. Ignite LUT works super good here and still has GPU acceleration.

I am a long time vegas user. Use since version 6. Here at the producer we only buy what is really necessary in production and lately customers have demanded a lot in the field of colometry. We really enjoyed Vegas, but we had a lot of problems with version 15, which forced us to go back to previous versions that worked well. We hope that mistakes are corrected. We had never thought about migrating, but due to the latest developments we raised the possibility of migrating to Davince Resolve for a number of reasons, mainly the cost benefit issue and the fact that it meets almost all our needs. Vegas is an excellent software - practical, dynamic, efficient - but it stopped in time and did not adapt to the current technologies or the new needs of the market. Let's hope that Vegas is truly reborn and has its value recognized, but it needs to work well, that mistakes are corrected and that it does what it was meant to do. Before doing a Vegas 16 I believe that it is more important to correct all the errors of version 15, from there may be a plan to deploy new features in version 16.

This luts bug in Track FX in Vegas is exclusive to version 15 and only if you use the native LUT Filter fx from vegas. I use versions 13 and 14 that do not have this feature and therefore I do not have this bug because I use Ignite LUT to apply the Luts. VisionColor Luts and Magic Bullet Looks also work but they also have some bugs that made me give up using them. Ignite LUT works super good here and still has GPU acceleration.

In my testing, the VisionColor LUT Plugin has the same bug as the VEGAS LUT Filter has. Just tried it again in VP14 to check.

@Nick Hope

Confirmed problem with VisonColor in version 15. However here in Vegas Pro 14 Build 244 I do not have this problem with VisionColor. I tested again on Vegas Pro 14 just to confirm.

Why are you not on build 270?

This might not affect all LUTs. Is it possible to share that "1.cube" LUT or direct me to where I could download it?

My testing was like in my comment here: https://www.vegascreativesoftware.info/us/forum/vp-15-v-321-lut-color-bug--111092/#ca686533

@NickHopeTestAccount

I do not use the build 270 of Vegas 14 because of an error that occurs at the end of the rendering of the ac3 pro files. This message hangs the Vegasaur transcoder that I use to render multiple projects and this slows down my work. Vegas Pro 13 Build 453 and Vegas Pro 14 Build 244 serve me well. This CUBE file was created in 3dLUT Creator pro V1.44. Follow the link with the file 1.CUBE

https://drive.google.com/file/d/1RuBNVkYj2w1-a9e0enefAW9xgPtAjwyI/view

Thanks. I've tested it by measuring RGB values on a mid-grey solid color event with a 4 second smooth fade out. Very difficult to draw conclusions with this particular LUT, as the differences are very minor. I don't know which of these is "correct". Note that GPU acceleration of video processing makes a difference for me on the VisionColor plugin in VP14, but not VP15. I think it's probably "more correct" without GPU acceleration, but can't be sure.

I usually create LUTs in Photoshop for multi camera angles so I can see all the angles and grade them at a time. Then create a different LUT for all the cameras and then import it into Vegas Pro. Excellent results. :)

That's kind of what I wanted to know - workflow. So, if you have four cameras, you make four LUTS - which is easily manageable - and then if you need to handle differences between clips (say, from an exposure change e.g. clouds) you would handle this with the standard Vegas CC fx?