I know Premiere and Resolve play these files, so a non elegant approach would be to use Davinci Resolve (free version) to encode to a high quality intermediate and use that in Vegas. You will be limited to a resolution of 4K in free version.
That's true. Davinci Resolve 18 reads Canon Raw files easily without dropped frames. I was surprised that my VEGAS Pro 20 can't read the files. I own both paid versions so I'll keep using Resolve.
Canon has worked with its partners to ensure that the Cinema RAW Light file format is supported natively by a range of popular non-linear editing systems (NLEs),
But not VEGAS. Canon made a plugin for FinalCut.
Former user
wrote on 12/14/2023, 1:53 AM
@Edward-Hill Hi, I just happen to have a sample file 'canon_c200_review_-_4k_raw_footage (Original)' that I downloaded at some point, it plays fine in VP20 & 21,
Would you share a sample of your videos on Google Drive or another file sharing site? 👍
Vegas 21 can open them but seems to see them as still images. Fwiw, ffmpeg cannot decode crm so no transcoding with that. It will repackage to a mov, but Vegas won't read that at all.
@Reyfox I just transcoded them both to mov avc and hevc with Resolve Studio. If I had a camera that shot crm, I think that's what I'd do. Just tried the Canon Cinema Raw Development Kit but that only seems to export a dpx image sequence which I don't know how to import.
Gid, Howard and Reyfox. I had the same experience. Canon Cinema Raw Development Kit only exports a dpx image sequence, which is useless. I've been using VEGAS since it was a Sony product. Shooting with the C200 has forced me to use Resolve Studio. Else the work flow takes too long.
Former user
wrote on 12/14/2023, 7:12 PM
@Howard-Vigorita Ah! Thanks for those, the file I have is an MP4 which is how it came when downloaded, the name of it is also what it came with 🤷♂️, I don't remember where it came from. Your CRM files don't import at all into my VP21, it looks like it's dragging in but there's nothing on the screen & a black preview window. Free Resolve played them no problem.
PS, neither Boris Silhouette or Mocha Pro standalone versions will open those CRM's.
-------------
I found the link where I got my vid from, the post is dated June 9th, 2017. He'd converted it with Resolve 🤦♂️
To see how the RAW footage performs, I created a very strong grading look that would heavily play with colors and contrast. First, I converted the Canon C200 CRM files (which are single files by the way, not photo sequences) into Apple ProRes 4444, so I had a format I could easily work with. The reason is that CRM is currently only compatible with a limited number of software applications, so I converted inside DaVinci Resolve 14 Beta and then went on to edit my footage in Adobe Premiere Pro. Canon recommends to use their own conversion tool, which allows you to select one of their log gamma profiles. I was told that Adobe apps will support CRM natively in the near future too.
I think I worked out a way to get CRM clips into Vegas for test purposes. But it's not really practical for actual shoots unless they're very short. But it will let me evaluate how Resolve quality compares to both Vegas and ffmpeg. It's done with ffmpeg which cannot read CRM clips directly but can read DPX clips made by the Canon utility.
step1: Run the CRM clip through the Canon Cinema Raw Development utility. That will output a single dpx file for each video frame and one wav file for each audio track.
step 2: Use ffmpeg to convert each dpx file to a lossless hevc clip. I did this with a Windows cmd script which processes the folder with the dpx files and uses ffmpeg to output lossless hevc clips into an mov sub-folder. This is the cmd I stored in and ran from dpx folder... I wired in the frame rate I shot and matched the pixel format to the color sub-sampling of the Canon c70 camera sensor I'm now testing:
(for %%i in (*.dpx) do ffmpeg -i %%i -c:v libx265 -crf 0 -r 29.97 -pix_fmt yuv420p10le -y mov/%%i.mov)
step 3: Place and the following cmd script into the mov folder and run it from there. I name it CAT_LIST.CMD. It creates a cat_list.txt file which is a list of the mov clips it finds:
for %%i in (*.mov) do @echo file '%%i') | sort > cat_list.txt
step 4: Place and run this 2nd cmd script in the mov folder. I name it CAT.CMD It reads the cat_list.txt file created in the previous step and uses ffmpeg to merge the listed clips into a new clip name CAT.MOV.
I used ffmpeg v6 and got this result from the short 6-second test clip I used for development... I'll shoot a 30-second clip tomorrow when I get a chance.
General
Complete name : D:\MISC\test clips c70 crm\A001C001_240220PJ_CANON\mov\cat.mov
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 0000.02 (qt )
File size : 404 MiB
Duration : 6 s 7 ms
Overall bit rate mode : Variable
Overall bit rate : 564 Mb/s
Writing application : Lavf60.16.100
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
Codec ID : hev1
Codec ID/Info : High Efficiency Video Coding
Duration : 6 s 7 ms
Bit rate mode : Variable
Bit rate : 564 Mb/s
Width : 4 096 pixels
Height : 2 160 pixels
Display aspect ratio : 1.896
Frame rate mode : Variable
Frame rate : 29.970 (29970/1000) FPS
Minimum frame rate : 29.895 FPS
Maximum frame rate : 29.970 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 2.126
Stream size : 404 MiB (100%)
Writing library : x265 3.5+111-c0af18dd5:[Windows][GCC 13.2.0][64 bit] 10bit
Encoding settings : cpuid=1111039
Color range : Limited
Codec configuration box : hvcC
Former user
wrote on 2/23/2024, 6:16 PM
I think I worked out a way to get CRM clips into Vegas for test purposes. But it's not really practical for actual shoots unless they're very short. But it will let me evaluate how Resolve quality compares to both Vegas and ffmpeg.
Also interested in your opinion that Voukoder gives low quality encodes when Vegas is in 32 bit processing mode, maybe you have already made a post about that. I want to see the facts, not hear your opinion based on finding you don't share.
Peer reviewed papers work on that principal. You show your working so others can show your errors when coming to your conclusion (if you made an error)
I think I worked out a way to get CRM clips into Vegas for test purposes. But it's not really practical for actual shoots unless they're very short. But it will let me evaluate how Resolve quality compares to both Vegas and ffmpeg.
When may you be posting your results for that?
@Former user I've only had the c70 two days. And only just now worked out how to losslessly convert CRMs. I noticed that the ffmped concat filter turns constant frame rate into variable so I'd rather not use that as a reference. Turns out its an old bug and the only workaround is to repackage into mkv instead of mov or mp4. Luckily, Vegas can read that lossless mkv so I think I'm good. Just waiting for the sun.
@Former user While the above scripts did work, I settled on a 2-step process that gave me better results. Step #1 is the same as before. Used the Canon Cinema Raw Development utility to generate a 16-bit RGB dpx per frame. My test crm was approximately 32-seconds which yielded 945 ntsc frames. For Step #2, I went with an ffmpeg image-sequence to ProRes script. I tried all the combos and got the best results transcoding to 12-bit ProResHQ. I tried lossless-hevc 1st, which was absolutely perfect, but Vegas could not read it. Would have liked to try MagicYUV but I don't have a stand-alone app or ffmpeg build that includes it. 12-bit ProResHQ isn't absolutely lossless but it's pretty close on ssim and totally there if you believe in vmaf. Here's the script, run from the folder with the dpx images in it. I named the export from the Canon utility so files are numerically sequenced starting with: rgb16_00000001.dpx
Here's the ffmetrics analysis of all the renders I tested beginning with Magix av1. The Vegas project was 32-bit full. vp21 build 208 only seems to render av1 8-bit at 20 mbps. Avc and hevc were rendered with Magix MainConcept and Voukoder, 10-bit at 20 and 50 mbps. Got some strange results rendering full to limited from psnr & ssim which I double checked to confirm. Oddly, I could not find the option to render Voukoder avc/x264 to limited. Here it tis; the 1st dpx frame is on top and represents the upper limit of quality:
I'll upload the crm that I shot as soon as the space becomes available...
Former user
wrote on 2/28/2024, 12:40 AM
@Howard-Vigorita It looks like you've proved your case which is unfortunate for us voukoder users. Your segmentation of VMAF results look better than mine too, I was getting so many results in high 90's with the VMAF 4K model that I changed to 1080P testing with the non 4K model, it gave a better more realistic range but still very high. I have to be doing something wrong.
And I think it was you who mentioned that you not only test with software such as this but you also view on a large screen 4K tv, and you can see the differences as well, it's more than just numbers on a spreadsheet to see quality difference
It occurs to me that the lossless-hevc clip that's perfect across the board on the 1st dpx frame would be a better ffmetrics reference than the ProResHQ clip. Even though Vegas cannot read it. I'll give that a run tomorrow and see if it changes anything. And reference Resolve which I think can read both the lossles-hevc as well as the crm directly.
Here's the quality analysis re-run using a 12-bit lossless-hevc reference. Since I couldn't load the reference in Vegas, the renders with 12-bit ProResHQ, which is slightly less than lossless, come out slightly lower in quality. I think this will be fairer when I get to comparing output from Resolve Studio which can load the CRM clip directly.
I also threw a 10-bit lossless-hevc render into the mix for comparison and find it interesting that the 12-bit ProResHQ scored higher on psnr and ssim. Here's the ffmpeg command I used to create 12-bit lossless-hevc from the 16-bit rgb dpx image-sequence:
@Howard-Vigorita your prores file is 422 10bit (written on your 1st metric screenshot). Your hevc file is 420 12bit. To compare them correctly they should be both in 422.
Former user
wrote on 2/28/2024, 6:05 PM
Here's the quality analysis re-run using a 12-bit lossless-hevc reference. Since I couldn't load the reference in Vegas, the renders with 12-bit ProResHQ, which is slightly less than lossless, come out slightly lower in quality. I think this will be fairer when I get to comparing output from Resolve Studio which can load the CRM clip directly.
@Howard-Vigorita Trying to do this comparision with Raw or 4444 12bit is quite annoying due to incompatibilities with Vegas and FFMETRIC. With Resolve Voukoder the interface looks to default to 420 8bit, it seems obvious you don't want to use that, but which one did you use?
Another problem with Resolve is that where possible it won't re-encode your file if not necessary, think it's called smart copy or something, Vegas used to have that feature. Go to advanced encoding settings , untick "Bypass re-encode where possible"
Former user
wrote on 2/28/2024, 8:45 PM
@Howard-Vigorita Looks like the problem is only with Vegas's version of Voukoder, it must be as you say Vegas delivers a compressed output to Voukoder, while Resolve doesn't
your prores file is 422 10bit (written on your 1st metric screenshot). Your hevc file is 420 12bit. To compare them correctly they should be both in 422.
@GJeffrey Did I mention that my 4k camera sensors are all physically striped for 4:2:0? So I think a 4:2:0 reference is more in alignment with reality. And interestingly enough is 100% in agreement with rgb16 dpx, frame by frame, which is an ffmpeg pix_fmt of rgb48be. Doing hevc in both 4:2:0 and 4:2:2 demonstrates that the ssim difference is minimal and that vmaf is perfect for both.