-
still driving me nuts
-
[David Lawrence] “Jeremy, this is very helpful, thank you.
I get where you’re coming from but as you might expect still disagree. ;)”
I also get where Jeremy is coming from, but I too disagree… I’m prepping a brief “diatribe” on the whole nomenclature discussion now and hope to post it here in a few days.
FYI David, I’m again using a keyboard analogy, kin of like the one you quoted in your last article, but different.
David Roth Weiss
Director/Editor/Colorist
David Weiss ProductionsDavid is a Creative COW contributing editor and a forum host of the Apple Final Cut Pro forum.
-
[Walter Soyka] “None of the classic reasons for keeping assets/media/cache/whatever off your boot drive (except perhaps capacity) are valid anymore. Rethink your disk use.”
Take that advice from Walter (and Jeremy) with some degree of caution. There are still many good reasons for keeping media files and certain other files on a separate media drive or RAID.
David Roth Weiss
Director/Editor/Colorist
David Weiss ProductionsDavid is a Creative COW contributing editor and a forum host of the Apple Final Cut Pro forum.
-
[David Lawrence] ”
Compound clips are basically fancy nests, and as far as nests go, I only use nests when I absolutely have to. I don’t like nests because they make the timeline unreadable, just as your first screen grab doesn’t give any visual indication of the complexity buried inside.
“These aren’t nests, though, they are Auditions and they work completely different than nests.
When a client asks, “can I see a different take?” I can hit a keystroke, which selects the next take and moves everything else around to fit to time. Even if I adjust time, that time adjustment is saved with that instance. Auditions don’t work like nests at all. My exploded Project gif is all the Audirins and relevant audio. There are no compounds used.
[David Lawrence] “I do this all the time with sequences. If I string out five different versions of a scene or piece on a timeline and use I/O marks to export each, is that sequence by your definition now a project?
“I guess it could be if those five sequences contained every single take of every scene, and all the relevant synced audio. Sure. But with X you don’t have to make five versions on a timeline, you work on your project, and the other options are stored right there, easily accessed without having to create a new version of everything.
[David Lawrence] ” From your perspective it does make sense.”
It only started to make sense after Libraries and Snapshots came to be. Before Libraries, the organization definitely made less sense, but those were just foundational building blocks.
-
[Jeremy Garchow] “It only started to make sense after Libraries and Snapshots came to be. Before Libraries, the organization definitely made less sense, but those were just foundational building blocks.”
You mean back when FCP X only had one library per root level of a drive?
Huge improvement to allow each ahem “project” to be stored in its own library.
Mac Pro, macbook pro, Imacs (i7); Canon 5D Mark III/70D, Panasonic AG-HPX170/AG-HPX250P, Canon HV40, Sony Z7U/VX2000/PD170; FCP 6 certified; FCP X write professionally for a variety of media; teach video production in L.A.
-
[Craig Alan] “You mean back when FCP X only had one library per root level of a drive? “
When it was a sneeze of Event files and you had to use Event Manager X to keep them and the Projects all sorted.
It seems like so long ago, but it wasn’t all that long ago.
-
[Walter Soyka] ” “None of the classic reasons…..are valid anymore…..”
and
[David Roth Weiss] Take that advice from Walter (and Jeremy) with some degree of caution. There are still many good reasons….”
A caged deathmatch: None vs. Many!
They’ve made the case for None. What’s your case for Many?
(Note that I’m not one of the combatants in this caged deathmatch. Just a mullet with a credit card who can’t wait to watch the PPV carnage.)
-
[Tim Wilson] “(Note that I’m not one of the combatants in this caged deathmatch. Just a mullet with a credit card who can’t wait to watch the PPV carnage.)”
If I’m going to rumble with DRW, we’re both going to need cool rumblin’ nicknames and cool rumblin’ catchphrases.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Put your cache where your apps……is?
-
“Except perhaps capacity ”
My system drive in a Mac Pro was always fast enough for editing.
But was never a good practice.
media takes up space. Lots of it. Filling up your system drive is a bad idea.
I also think that managing this media would be more difficult if kept on the system drive. I can back up entire project s when I’m done editing and wipe a fast raid clean to start the next. Don’t really want to wipe my system drive clean unless it’s gotten slow and buggy which is more likely if I start asking it to hold and process media.
SD drives are still more expensive and tend to hold less than disc drives.
You can always daisy chain a single cheaper drive to hold the render files if you want.
Mac Pro, macbook pro, Imacs (i7); Canon 5D Mark III/70D, Panasonic AG-HPX170/AG-HPX250P, Canon HV40, Sony Z7U/VX2000/PD170; FCP 6 certified; FCP X write professionally for a variety of media; teach video production in L.A.
-
I agree with Walter “Rethink Your Drive Use” Soyka, that capacity is the only limit. If you had a 16TB PCIe SSD boot drive, you are saying you wouldn’t use it? Why?
[Craig Alan] “You can always daisy chain a single cheaper drive to hold the render files if you want.”
This completely dissolves the point, that I, Jeremy “Put Your Cache Where Your Apps….Is” Garchow was trying to make. The Cache, where little tiny files, and sometimes bigger, but still small in relation to original media benefits from the enormous speed that that SSD provides. This speed also allows a lot of read and write multitasking. This is not a spinning disk head where a drive head needs to read and also write. Also, with an external drive, you are limited to the bus speed of whatever that is. With USB3, it’s going to be about 120MB/sec. With PCIe SSD, it’s about 800-900+ MB/sec on both a MacPro or MacBook Pro. If capacity isn’t holding you back, there really is no reason not to use it at least for a Cache drive.
And if you use Macs, there’s really no reason to stick a Time Machine drive on to your system. It’s easy, updates constantly, and provides an easy to restore a system from multiple points in time (or reach back and get only the files you need/want).
Jeremy
Reply to this Discussion! Login or Sign Up