#Slimraw similar archive#
#Slimraw similar full#
#Slimraw similar pro#

#Slimraw similar full#

An empty one starts out writing at about 160,000 Megabits/second but as it get's closer to being full slows down to at least half the speed. So this all being said the speed bottleneck of all these transfers is the speed of the drives themselves. The XML workflow would be much nicer but it's never ever worked for me. My workaround has been as I'm getting towards the end of each project I go through the ProRes files and add a letter or two to the end of the filename then reopen the file in Resolve make the adjustments I want to see and re-save the file with the original filename. I've tried over and over again only to lose days and days of time. I have never ever been able to succeed with XML round-tripping a project.

#Slimraw similar pro#

From there I usually use Premiere Pro to cut, FX, and all other art and audio from Adobe apps. I may try to shift that workflow to resolve syncing on Waveform but am not yet sure. In the past I've used PluralEyes for that pretty successfully. Once I'm through an initial grade in Resolve I output the files I'll be working with to Pro Res (I've found I like getting right to the final codec though it's not really final yet but honestly doesn't take up much space.

#Slimraw similar archive#

That Archive drive is duplicated using Chronosync about once a week with the duplicate drive being taken off premise. That job file is then archived with Chronosync and then synced each day. Once I've input all the files I copy them over to the job file on a RAID 0 drive. It's put on an internal 6G HD spinning at 7200 RPM's. I bring the footage initially into Resolve and general go through initial color. If the BMCC was RAW 3:1 I'd save about 160GB's which would over months save me quite a lot of money. I also recorded sound and shot some stills so ended up around 400 GB's. The BMCC came in at 250GB and was only used as the A Cam in the same interview. I used the micro as a B Cam in about a hour interview as well as lot's of B-roll and roving footage of the event. Yesterday I came in with about 120GB's from my Micro camera, which I set at RAW 3:1. Appreciate the advice.ДЇor clarification I'm sure like all of you every shoot is a little different. Unless you're shooting years and years of footage for a doc, I don't really see a need to use lossy re-compression and/or toss my original footage. Ideally, I keep two copies of the original DNGs from camera and a single copy of the losslessly compressed versions, and because HDDs are so affordable I tend to just keep stuff around. I don't use lossy compression but I do losslessly compress DNGs from my Bolex all the time. Also depends on how much footage you're processing and how good your machine is.

If you're copying from one RAID0 to another RAID0 then it is pretty fast. If you're copying from and writing to the same 5400RPM laptop drive then yes, it'll take a while. Compatibility is reduced as well, on account of Adobe still not having great compressed CinemaDNG support.Дepends entirely on what you're reading from and what you're writing to. You mean, besides lowering the quality of your footage? Kind of. It's sort of just become my go to process for archive and offloading my BMCC footage. I find the Lossy compression sufficient enough that I usually don't need to archive my originals, although this simply comes down to personal preference/workflow. ( that in addition to some other awesome features like 2x downscale and checksums ) I will run all my footage through it because I gain all the benefits of extra compression with negligible ( if any! ) penalties in terms of speed. So good I honestly don't ever find myself just offloading the footage on its own. Performance is also very closely attributed to Disk Speed ( both source and target disk), converting footage directly off the SDD with a SATA3 interface or USB 3 definitely helps. With a relatively modern system you can do even better, sometimes 2x-4x real-time performance. This obviously depends on your system specs, however having tested on a variety of systems I will say that for the most part you can expect at LEAST ~realtime performance ( 45 mins of RAW will be 45 mins to convert )