![]() ![]() mlv) cause I liked using some of the "forbidden" ML tools (features requiring Global Draw ON which was supposed to be turned OFF for raw recording). I am a bit behind on ML developments, but back when I was shooting ML raw (MLV didn't existed yet) I would occasionally get corruption in the ML. Now, of course, you shouldn't be getting errors in the MLV in the first place, but you never know with (some) CF cards and high rate recording. And if there are errors in the MLV, these errors will translate to the DNGs. While slimRAW is, I believe, extremely reliable and can also verify the written output for you, it obviously can't verify the MLV input for errors since it has no way of recognizing them. Using MLVFS to feed MLV into slimRAW should probably be the fastest way, since this skips the original mlv->dng conversion and directly outputs compressed cdng. This is especially nice with HDDs as it can be all the difference between choppy playback and smooth playback. I believe it is only second to Resolve in terms of performance at the one of the cool things with slimRAW is that half the size means half the storage throughput needed in post. Premiere has seen some serious performance improvements in DNG raw processing in CC 2015. It seemed to crash a lot on dng playback last time I checked some months ago. A checksum error generally means the output storage device is unreliable, or RAM is faulty.ĪFAIK, mlvrawviewer doesn't read all types of lossless dng correctly. dng file, then there is no way for the software to recognize that, so it can't report it missing in the output.Ĭhecksum verification calculates the checksums of the written output (bypassing the OS file caches) and compares them to the checksums of the data in memory. Note that if the input device filesystem is messed and the OS/software doesn't see a particular input. This should never happen, if it happens then something is seriously messed up with the filesystem of the output device. "Missing file" would be any dng file present in the input folders and missing in the output folders. With CC compatibility, the Compressed footage runs smooth in Pass will check for missing files and for checksum errors. Not sure how Mlrawviewer works, might be it "expects" a certain uncompressed footage. I also see that top half of the image is "broken", only in mlrawviewer. So 12 bits is more than enough for that.Īnd another question, the Cdng's are not playable in MLRawViewer after compression, It plays a few frames and crashes. ![]() ![]() The play doesn't require any colour grade, just colour correction and some contrast to make the look natural. Is it doing the job for me, that I am doing right now? First half of the footage I didn't have the Verification Pass checked, but can you tell me what the Verification Pass actually verifies. I am looking through the Compressed footage and so far no errors or missing frames, so I will delete the MLV's when I have checked all of them. I converted to 12 bit to save space, I filled up 6 TB these last 6 months and I recorded 3 hours more of footage from the Play, so 3 hours in MLVs and converting them to 16 bit just don't fit on my drives. Only - 12 bit maximized, 16 bit and 16 bit maximized. The weird thing is that if run one single job without using the job array, it writes the log file correctly.I use Raw2cdng, so I can't convert to 14 bit. no log file is written whereas the job runs correctly. I want the log file to be written as above (using ">& test.log") instead of using the usual #SBATCH -output test.%A_%a.out directive, but it does not work, i.e. The input file jobs/jobarray.input contains a series of commands like this one: /home/fwt/CarTest /home/fwt/hummol/nf >& /home/fwt/hummol/test.log Time srun $(head -n $ jobs/jobarray.input | tail -n 1) Using job arrays with slurm, I have this sbatch file that runs the same command 10 times on different input files : File Edit Options Buffers Tools Sh-Script Help
0 Comments
Leave a Reply. |