Mark Raudonis
3
COW Coins
Forum Replies Created
-
We’re regularly pushing 150-200 Mb. 350+ is where we start seeing significant problems.
146… not that bad.
Mark
-
Travis,
146 Mb is NOT that big, so there’s probably something else going on here.
Since you mentioned that you’re coming from Avid, the biggest difference to note is that the “project” in FCP is irrelevant. You can have multiple projects open simultaneously. We will typically have “projects” that only contain a sequence and pass that around amongst the team.
In your case, I’d suggest you create a new project with ONLY your current sequence in it. This should open quite quickly, and speed your process along. You can also REMOVE all of the sequences from the old project and put them in a different project. This will lighten the load on the big project and speed up your opening time.
I think much of the slowness is due to your system. That’s pretty old.
Good Luck.
Mark
-
James,
I’ve NEVER hired anyone based on their “sizzle reel”!
At a certain level of accomplishment in this business, we assume that you can “edit”. After that,
who gets the job depends more on other skills like: communication, conversation, collaboration, common sense, creativity etc. These traits are not easily conveyed via a sizzle reel. They can only be discerned through face to face meetings.So, my advice to you is have a good “sizzle reel”, but spend your time, effort and resources interacting with
potential employers on a personal level. It’s that one to one connection that will get you hired.Good luck.
Mark
-
Yep. I said that. I also added, save “mobile-ly”… meaning to a USB thumb drive, as an extra added measure of protection. Locally. Globally. Mobile-ly and you won’t go wrong.
As for why opening and working with FCP projects on the SAN can go wrong… there are just too many reasons to bother trouble shooting. Therefore, you can store your projects “globally”, but pull them to your local client computer and open them “locally”. You want to archive in at least two places anyway, so there’s really no problem working this way. It actually encourages you to keep two copies. Use a logical naming convention that includes the DATE in the file name and it’s easy for everyone to know what is the latest project.
Good luck.
Mark
-
There’s no easy answer here. For most efficiency, get a big enough raid and be done with it. Cheapest cost, just buy 3tb drives and put them in the Mac.
Good luck.
Mark
-
Mr. Zelin
As always, you hit the nail on the head.
2011 has to go down in history as THE most tumultuous year in post EVER!
Plenty of change. Plenty of opportunity. Plenty of uncertainty.
I abandoned “plan A, B, C, and D” months ago. Improv is good. Instinct is good. Doing nothing is good.
But, as you point out, with NAB just around the corner, next year is when all the action will take place.I’m looking forward to a very exciting year next year. Some of the dust will have settled and we can focus again more on the “show” and less on the “business”.
Mark
-
There’s a company called “Pluraleyes” that has a product called “Presto”.
https://www.singularsoftware.com/presto.html#presto_fcp
If you ever have to do this kind of production, I strongly suggest you take a look. It’s cheap, and can
save you hours of work in post.Mark
-
Larry,
I can assure you that the classic “low rez to hi rez” workflow is still alive and well.
We’ve been using it forever, and there are plenty of reasons why it’s the right choice. Unfortunately, there are also plenty of reasons why it’s a pain in patootie. Only you can decide if the benefits outweigh the costs. In our case, with the amount of media we’re dealing with, the number of editors on our team, and the number of multi-camera streams flowing around, the off-line proxy workflow is essential.
There is NO easy way to make this work. You have to pay attention to details. You have to set some hard and fast rules and make sure EVERYONE abides by them. You have to plan for, allocate, and accept the time involved in “reconnecting” from Low to Hi-Rez. It’s NEVER just one click. Something always goes wrong.
If you can accept these realities, then it’s a very helpful workflow. If, like most everyone, you just want an “EASY” button to solve your problems, then this is NOT the way to go.
Good luck.
Mark
-
This probably has less to do with “multiclip” and more to do with the throughput of your drives.
You don’t say how many streams of multiclip you’re trying. 3? 5? 15?
More info needed to trouble shoot.
Mark
-
I sense a business opportunity here for a plug-in developer:
“Bark be gone”
mark