Brian Berdan
Forum Replies Created
-
Hi Elisabeth,
I’m used to the performance and flexibility of Avid’s Unity, but last summer on a Final Cut show, a young director turned me on to a really basic sharing setup that I didn’t think would work… Storage drive on one machine linked via file-sharing/ethernet cable to the other. We were both able to edit the same material at the same time- and this was 1920×1080 ProRes HQ. I just hooked up the same setup today between my MacPro and MacBook Pro and it’s working fine with ProRes LT material. Occasional dropped frames during playback, but for editing, totally fine (turn off the warning in User Settings).If you’re green on the Mac, sharing is in System Preferences/Sharing. Connected harddrives show up under “Shared Folders”, then add a user and set their access.
But obviously don’t have both of you opening the same file at the same time… That’s why Avid’s Unity is so slick…
Brian Berdan
migrant filmworkercurrently on a MacBookPro, using FCP 7.0.1, ProResLT from Firewire (4 TB of incredible footage) and a simple DVI out to the monitor- things are getting simpler.
-
Yeah, I got that… it seemed to have something to do with having turned on ‘record audio keyframes’… better now.
thanksBrian Berdan
migrant filmworkercurrently on a MacBookPro, using FCP 7.0.1, ProResLT from Firewire (4 TB of incredible footage) and a simple DVI out to the monitor- things are getting simpler.
-
7 doesn’t fix it… I seem to re-render almost every day.
Brian Berdan
migrant filmworkercurrently on a MacBookPro, using FCP 7.0.1, ProResLT from Firewire (4 TB of incredible footage) and a simple DVI out to the monitor- things are getting simpler.
-
Has this bug been fixed yet? I just had to upgrade to Snow Leopard and now the fullscreen is stuttering again.
ThanksBrian Berdan
migrant filmworkercurrently on a MacBookPro, using FCP 7.0.1, ProResLT from Firewire (4 TB of incredible footage) and a simple DVI out to the monitor- things are getting simpler.
-
Hey Shane,
Thanks… it keeps me young!Brian Berdan
migrant filmworkercurrently on a MacBookPro, using FCP 7.0.1, ProResLT from Firewire (4 TB of incredible footage) and a simple DVI out to the monitor- things are getting simpler.
-
A bit of a premature panic- a restart at least got the projects to open again, though all preferences had to be redone. Okay, back to work- sorry.
Brian Berdan
migrant filmworkercurrently on a MacBookPro, using FCP 7.0.1, ProResLT from Firewire (4 TB of incredible footage) and a simple DVI out to the monitor- things are getting simpler.
-
Interesting… I just got the same ‘Codec not found error’. I had just done a tv screen replacement in Motion, using a SnapzPro-created temp quicktime. That rendered and played fine back in FCP. I went to do the next one with one additional SnapzPro element, created the exact same way, and those comps won’t render and give the warning.
FCP 7.0.1
OS 10.5.8
ProRes LT 720The SnapzPro quicktimes are LT, but just a smaller frame size.
Brian Berdan
migrant filmworker -
Hey Shane,
Looks like the autosaves are causing the same hanging when I try to pull something out of them- even back when the size was 80MB. And while opening the project with the Media drive offline is much faster (I’m working on my laptop for another two weeks till I go down to LA) it still has the same crash.
My assistant seems to be able to pull from a randomly abridged project (deleting a bunch of the folders within)… But he’s going to hit the corrupt part of it soon, I’m sure.Brian Berdan
migrant filmworker -
Hi Nicole,
All syncing had been turned off so that wasn’t it.
And Rafael, perhaps my sentence wasn’t clear, but I moved the project files off to a USB drive, not my media… my tires are nice and firm.
Perhaps I’ll figure it out before I switch to my MacPro on monday.
ThanksBrian Berdan
migrant filmworker -
Actually, now I see the beach ball is happening more often than auto-saving (I upped the time and checked the latest auto-save)… not sure what’s going on.
Brian Berdan
migrant filmworker