[Rene Hazekamp]

Hey Chris

Try to zap your pram (cmd.alt.P.R). To my surprise the realtime performance went up from 6 nodes to 11/12. This with system 10.7.3 and resolve 8.1 . I didn’t reinstall resolve 8.2 yet, (i’am not an install hobbyist)
It’s not as good as the 18 nodes i get with system 10.6.8 and resolve 8.1, but this could cover 90 percent of what i need. So it’s a step.

Why it works i don’t know, but i thought if Lion memorises all this windows positions it might as well do the same with power management. -but it’s a big ???, maybe it’s just luck-

Resolve Lite, MACPRO 4.1, 12 GB, 8*2.26 Ghz, NVIdia gt 120/470

René A. Hazekamp

https://www.renehazekamp.com

[Rene Hazekamp]

Hey Chris

Seems we have a similar problem. Cause I can’t mess with my old system ( to much going on there ), I uninstalled resolve 8.2 on systemdrive B (osx 10.7.3) and installed resolve 8.1.? . This gave me the same slow performance 6 nodes realtime instead of 18 ( i also had some memory/database problems with the memory banks (command 1/2/3etc) , but i didn’t look into that – probably an uninstall/install issue).

I have last fridays cuda driver on systemdrive B. And i would like to try to go back to an older driver version (4.0.50 preferably) , but i don’t know how (yet)

all the best

René A. Hazekamp

https://www.renehazekamp.com

[Rene Hazekamp]

yep

More or less the same problem, here in Holland.

Harddrive A has OSX 10.6.8 and Resolve 8.1 and plays back 18 nodes at 25 fpm (1080p)
Harddrive B has OSX 10.7.3 and Resolve 8.2 and plays back 6 nodes at max 22 fpm.

Both systems have this AGPM. kext thingy removed, the only difference is that i accidentally (?) updated my cuda driver at harddrive B (os 10.7.3). Harddrive A has still cuda driver 4.0.50.

I tried to change systems and versions because in OSX 10.6.8 Resolve always crashed when i wanted to render to anykind of DNX code.

Resolve Lite, MACPRO 4.1, 12 GB, 8*2.26 Ghz, NVIdia gt 120/470

answers and explanations are more than welcome

René A. Hazekamp

https://www.renehazekamp.com

(I would have bought the dongle if someone could guarantee that it would resolve all problems)

[Rene Hazekamp]

I don’t wanna spoil any remarks, but in Motion you can actually build your own double/triple- window interface and save and manage it.

So I don’t know what’s the problem if final cut X has the same approach,

Actually it would have been quite strange if the Supermeet had opened with the news that final cut X can export cmx 3400 edls AND has a multiformat magnetic time lime. And then another marketing guy pledging they would always support Grass Valley edl’s as well.
wouldn’t make much sense, wouldn’t it ?

René A. Hazekamp

portfolio https://www.renehazekamp.com

[Rene Hazekamp]

I should have checked mirror on desktop , under file / av settings etc

sorry

Rene Hazekamp

[Rene Hazekamp]

I should have checked mirror on desktop , under file / av settings etc

sorry

[Rene Hazekamp]

Hi Rod

It’s workable as long as you stick to cuts only, no effects . I’ve edited 25 minutes programs (25 fps 1080p)
on a double g5- 1.8- 2 GB ram. No problem, though the online was done elsewhere (pal sdi-digibeta).
Actually there are some realtime effects you can still use and scaling as well)

A bottleneck might be your drive system, but esata is only slightly better if it’s not a big raid system.
Another thing is memory leaking. FCP will become slower and slower after editing 5 or 6 hours, both intel and powerpc systems have this problem with fcp 6.0.4. (Version 7, I don’t know).
But after working six hours it’s time to have a break anyway, So restart and smoke a sigaret (or whatever)

So, it’s workable as long as you know what your doing and don’t need a ton of effects.

René Hazekamp
Portfolio https://www.renehazekamp.com

[Rene Hazekamp]

Hi

Your problem is caused by memory leakages of FCP. Besides restartiing ther is not much you can do about ik. Adding memory helps to a certain extend, as does quiting unneccessary programs that might run in the background. Because interframe codecs (like xdcam, avchd, eetc) tend to use more memory problems with those codecs are more severe.

On the other hand, it’s always good to take a break after a few hours editing, so why not go for a stroll while restarting your computer. (In the future with osx 10.5 , fcp 7, and a lot more memory to allocate the problem will not be noticed anymore, or maybe solved )

René A. Hazekamp
portfolio https://www.renehazekamp.com

[Rene Hazekamp]

Okay I see

With synchronize, I meant how do you get things in sync. But I think / or understand that all your xdcams have the same timecode. So I guess that’s clear.
What I never could figure out (but maybe I didn’t invest enough time in it) how you could make an online version of your program, with your offline clips. It always seemed to be a very tedious workflow and prone to many failures.
But I guess you found your solution. I just copied the darn xdcam disks to multiple harddrives (raid 5), but I had only 300 to 350 hours of material. (10, 50 minutes shows)

thanks for your insight

René Hazekamp

portfolio https://www.renehazekamp.com

[Rene Hazekamp]

So can you elaborate on your offline-online
workflow.

What works best for you ? How do you make back-ups, on what media and keep track of them,
Do you only use ex-3 camera’s or did or do you use ex-1 camera’s

How do you synchronize the stuff ? On what system are mixing how many audio tracks.

How do you edit this program (in a multicamera suite or just on a NLE)
just curious

René A. Hazekamp
portfolio https://www.renehazekamp.com