See no problem at all. If the filename, extension and total length of time is the same, then the file substitution should be fine. You should see the color difference when the projected is loaded in PD15.

You can always save a backup of the original in case you don’t like the processed file or is not confident of this in the beginning.

Thanks! Been experimenting and kindof came to the same conclusion! It's going to take some file management at this point with duplicate copies of everything and segragating the graded versions. Easier to do on the front end, but at least it can be doneat this stage.

I do something similar all the time. Just come up with a naming convention with a few characters that are easily replaced. For instance, video1_LR_.m2ts (LR=low res) and video1_CC_.m2ts (CC=color corrected) and so on. Then use any basic text editor and replace _LR_ with _CC_ in the PD pds file. I use a couple of old dos scripts as it gives one more flexibility to easily change names without lots of typing and always work on a backup copy of the pds file. I’ve had very few issues with approach.

Approach has many applications, a good manual way to generate lower res editing files to ease CPU requirements when working with very HQ source video. Originally discussed back in the sone ages here http://forum.cyberlink.com/forum/posts/list/20203.page#post_box_106809 and rebranded many times as here http://forum.cyberlink.com/forum/posts/list/43102.page#post_box_222623 with a nice step by step guide.

I've even used the approach to create a "standard" slide templete pds file that I'd like to reuse and then simply create a orig pic > new pic file translation table and perform the change on the pds file. A little scripting capability helps a lot. When one is changing out 100's of pics it's much easier than manually editing the timeline and changing out photo's without loosing all the edits.

Jeff