[Marco Baer]

Arrghh, isn’t there really any way to edit a comment after having posted it?

[Marco Baer]

I’m not aware of a simple way to do this.

What you can do is, if you have adjusted your FX, just save as preset, then apply the FX as often as needed and recall the preset in each FX of the chain. Or use a script to apply a certain FX with a certain preset directly (and repeat recalling the script).

[Marco Baer]

Aaarrgghh – vice versa.

Original size: 601-to-709 corrected
Resized: 709-to-601 corrected

And pre-correction probably: 709-to-601

[Marco Baer]

I’d say: Bingo, that’s it (the false interpretation of color space by the players).

If you do a 709-to-601 channel blend conversion in Vegas Pro to your original sized footage, colors look exactly same.
Or –
If you do a 601-to-709 channel blend conversion in Vegas Pro to your resized footage, colors look exactly same, too.

So the easiest way for you to correct in a way the players will work as expected, is to pre-correct via an appropriate channel blend ajustments (I’m struggling through my brain getting the right order – I think your pre-correction then should be a 709-to-601 correction).

[Marco Baer]

Then it is very likely it’s the players which decodes the files differently while the files actually all have same color. Besides different players use different video level management, some also interpret different color spaces. And what your demo pictures above show, really looks like a color space decode mismatch.

I only wonder why this happens. It may be the players take their color space base from the frame size and e.g. they use rec. 601 for any size below1280x720 and rec. 709 for sizes of 1280×720 and above.

Curious whether the differences of your renders adapt to the differences of rec. 601 and rec. 709. I’ll do some tests later.

[Marco Baer]

“Imported mp4 file that vegas did on his own(with it’s own codecs), rendered 1280×694 file which is correct copy of source file. Rendered with sony avc internet template …”

I tried same now (in an 8 bit project because using 32 bit floating point full level linear doesn’t make too much sense here). I ran the test twice, one time with Vegas Pro 13, one time with Vegas Pro 14. One time cropped and zoomed to adjust source media, one time untouched – with black bars.
But in none of the cases I can cause such a color shift. I analyzed the colors via several control instruments and the colors are same.

Did you also check the rendered results inside Vegas Pro with its internal preview?

[Marco Baer]

That color drift is really strange.

Do you see same drift if using a technical color bar (like the ones provided in the Vegas Media Generators) if using same size and applying same resizing?

Or could you offer a sample project with an small media file which for download for testing purpose?

[Marco Baer]

You should try disabling GPU support in both Options/Preferences/Video and in your render settings. GPU boost could cause strange trouble (though I wouldn’t get too far from K-Lite as troublemaker).

[Marco Baer]

Yes, that’s a reported bug.

There are two workarounds to overcome.

1. If Movie Studio 13 is available, import these files with MS13, save the project file, open the project with VMS14 and save again. Now in this certain new VMS14 project the 5.1 files will work.

2. If the original folder structure of the video files or the SD card where the files are stored are still available, import into VMS14 using the Device Explorer. Save project again and the files work within this project.

[Marco Baer]

Sergei’s concern is not to use the mouse and it must work within the basic version of Movie Studio, which is limited in the editing feature set (e. g. there is no Shift+Q command).

Though in the thread I linked above he already got two solutions. Don’t know why these were disregarded.