Reid Caulfield
Forum Replies Created
-
maybe roll your own Alpha transition?
https://www.wonderhowto.com/how-to-make-alpha-transitions-from-scratch-final-cut-pro-7-375854/
Reid C
-
-
I know this is an older thread, but re suggestion #2 above – in other words, converting all XDCAM material to Pro Res, then re-conforming those new clips to what has already been cut, what’s the best way to maintain the editorial work already done?
Reid C
-
there is, actually, technically speaking. I saw a similar spec a few years ago where the client wanted different AC3 streams on each channel of their master. AC3, of course, is a data stream that holds multiple channels of audio information. So we did a stereo domestic stream to channel 1 of an HDCAM master, M&E to channel 2, etc. Crazy, but it’s possible.
-
And how about non-regressive Undo? I use Nuendo as my main pro audio app and it does this. Basically, you can bring up a history of actions and choose which to undo without going back step by step. Very handy.
-
I’m a fan of the Wiebetech RTX as well but I’ve never done a bare-drive RAID in a multibay dock. How is it that way, Walter? You like?
-
” Profiles are stored in /Library/ColorSync/Profiles/Displays/ or /Home/Library/ColorSync/Profiles/Displays/ folder depending upon whether you’ve saved the profile for only your use or for all users. ”
-
Sounds like FW bus overload.Are your media drives running on the same firewire bus? Is this new behavior for this setup? Have drives changed recently for some reason (system crash & restore, new driver install, etc)?
-
But to answer your question without prejudice, the wiebe RTX units are great, functional and they do what they say they do. I have an early unit which was not as ruggedized as the newer versions. But for RAID 5 I’m not sure they offer real benefit, unless you need to change all x number of drives at the same time as you change projects. If a drive fails they make it super easy to install a new one, but how often will that happen? I use mine for swapping bare drives for backup, mostly.
-
Years ago I built a relational FMPro database to keep track of everything; jobs, notes, job details, client info, reporting- it’s very complex, has dozens of screens crazy reporting functionality, multi-level security & screen access. Not pretty to look at, sadly.
What we found out fairly quickly is that it wasn’t a great idea to give our editors & mixers even simple record-level access to the database. They’re too busy doing their jobs to move between screens. But we finally cut off access when we realized that the system could be used to – how to say – “massage” the data, for a variety of reasons. So we kept the database but put a small piece of software on all the workstations that was a simple timeclock. It had job name, client, specific task descriptions and a simple way of punching in & out on a given task. Our personnel were happier with it, and while it was still prone to bad data entry, we noticed that they tended not to engage in data massage. I never understood the psychology there. A few times a day, our facilities manager would pull a report from the clock and transcribe the date into the FMPro database for detailed reporting & job tracking.
Bottom line: If you build a proper database, you need to keep the data as pure as possible & make its interface simple to navigate for your users.