[Terry Hogan]

With futher testing I have found that in Windows 10 if I go into Display settings, select monitor 2 and then Advanced and set it to 100%(see attached picture) then Vegas can put the Preview on the secondary monitor. But all the menus are extremely tiny. I had this advanced setting at 200% and then most menus were a reasonable size. At a setting of 150% a little corner of the preview window shows up on the lower left edge of the secondary monitor. It is like Vegas is sending the Preview to the secondary monitor but it is off the center of the secondary monitor and is only partially or not at all visible unless this advanced setting is at 100%.
See imbeded Advanced Display setting screenshot. Anyone have a suggestion or does VP15 fix this issue?

i7 5930k 3.5 GHz overclocked to 4.0 Ghz water cooled processor, 32 GB RAM, Nvidia Geoforce GTX 980 4GB RAM, C: drive and render to drive are SSD, project and media drive is WD Black.

[Terry Hogan]

https://drive.google.com/drive/folders/0B5bgT6TyHVt6cjlWaWRfNFZDcG8 I believe 4k shooters still has a Cinema RAW Light file for download available at this link.

i7 5930k 3.5 GHz overclocked to 4.0 Ghz water cooled processor, 32 GB RAM, Nvidia Geoforce GTX 980 4GB RAM, C: drive and render to drive are SSD, project and media drive is WD Black.

[Terry Hogan]

Grazie what did you find to be a revelation when you moved from VP14 to 15?

i7 5930k 3.5 GHz overclocked to 4.0 Ghz water cooled processor, 32 GB RAM, Nvidia Geoforce GTX 980 4GB RAM, C: drive and render to drive are SSD, project and media drive is WD Black.

[Terry Hogan]

My prerendered files location was set to C:\Users\Terry Hogan\AppData\Local\VEGAS Pro\13.0\ which is on an SSD drive with 751 GB of free storage space. So I have now changed it to C:\Users\Terry Hogan\AppData\Local\VEGAS Pro\14.0\ . I have also changed the file type for the prerendered files to xavc s long. The preview seems to be stable now with no crashes.

i7 5930k 3.5 GHz overclocked to 4.0 Ghz water cooled processor, 32 GB RAM, Nvidia Geoforce GTX 980 4GB RAM, C: drive and render to drive are SSD, project and media drive is WD Black.

[Terry Hogan]

I messaged too soon. Today previewing Build Dynamic Ram Preivew caused VP 14 to crash. So previewing prerendered video by either method causes VP 14 to crash. Could it be that I am trying to prerender too much of the project all at one time and need to just prerender a couple of clips at a time?

i7 5930k 3.5 GHz overclocked to 4.0 Ghz water cooled processor, 32 GB RAM, Nvidia Geoforce GTX 980 4GB RAM, C: drive and render to drive are SSD, project and media drive is WD Black.

[Terry Hogan]

Thanks

i7 5930k 3.5 GHz overclocked to 4.0 Ghz water cooled processor, 32 GB RAM, Nvidia Geoforce GTX 980 4GB RAM, C: drive and render to drive are SSD, project and media drive is WD Black.

[Terry Hogan]

I now have tried using the Build Dynamic Ram Preview of all three tracks after boosting the Dynamic Ram maximum setting to 10,000 and that previews smooth and stable. But I suppose I will lose the dynamic ram preview when I shut down FP 14 and will have to rebuild it each time I go to do some editing on this project. Any comments regarding Selective prerender vs Build dynamic ram preview would be appreciated.

[Terry Hogan]

I really think the way that Canon Cinema RAW Development works for Windows is unacceptable. It takes one Canon Cinema Raw Light file that you can make some RAW adjustments to and then outputs numerous small DPX files and puts the audio in numerous WAV files. Then in a program like Resolve you have to import all the numerous DPX files from just one Cinema RAW Light clip and line them up on the timeline. Then line up all the audio WAV files under the corresponding DPX file. Then render that to a DNxHR file to get just one usable clip that can be further edited and graded in Resolve or in Vegas Pro. Canon has always seemed to disregard the Windows PC user vs MAC users. Canon should make Cinema RAW Development output a DNxHR or DNxHR HQ file directly. I can’t imagine doing this process for a project where I have a hundred clips or more to edit.

[Terry Hogan]

I spoke with Canon’s 1-855-CINE-EOS (1-855-246-3367) technical support. The representative told me that I was the first one to complain about the C200’s RAW file and problems on a Windows PC. She said that she believed that Premiere can now process the DPX files and assemble them with audio WAV files back into complete clips. She also said if I had a MAC computer the Cinema RAW Development program could output a ProRes 444 clip. She had never heard of Vegas Pro. I asked that she submit a request to the Canon development team that they program Canon Cinema RAW Development to output a DNxHR 444 for Windows (since they output a ProRes file for MAC) and that they add to the firmware update coming out in February the ability for the C200 to record an XF AVC 10 bit 422 file internally for those of us who don’t want to deal with the current RAW file problems. I know DaVinci Resolve can output DNxHR on a Windows computer so Canon should be able to as well. Maybe if others message Canon and Vegas Pro development teams they will do something for us.

[Terry Hogan]

https://tbf.me/a/1U1FQ Here are a couple of DPX files with separate WAV files that have to be manually synced to the video files.