Brad Bussé
Forum Replies Created
-
Thanks Walter. I wasn’t even aware that I could output my Mac’s audio through the Kona.
-
How about the kbox for the kona 2, can I use that with the Kona 3?
-
Right it won’t, I was just curious how much better the Radeon is since it’s only a $250 upgrade, while the 6800 was quite a bit more than that when I got it a couple of years back if I remember right. Glad to hear that it’s that much better, thanks.
-
I’m looking into upgrading. My dual 2.7 is struggling between mixing DVCPro HD clips of varying frame rates in a ProRes HQ timeline, adding lots of FX like SmoothCam, 3 way CCs, 55mm plugins, and sending lots of clips out to Shake, Motion, and Color for stabilization, tracking, retiming and grading. I recently upgraded from 2.5 to 5.5 GB of RAM and I’m still paging out, but the dual 2.7 CPUs are what’s holding me back most – sometimes I’m spending almost half my time sitting around waiting for renders. The most recent FCS update from Apple said that it was further optimizing ProRes for G5s, but I think that Apple has decided to focus the large majority of their efforts on supporting the Intel architecture; something that I suspect will also be reflected in Panther.
I haven’t run Parallels before since my main workstation is G5 based. I’m just hoping to be able to run Parallels smoothly with an octo-core Intel. Eventually I’d like to use a single system for both Mac and PC. I don’t use my PC often, but I do have to have it for some apps like compressing videos w/ Rad Game Tools, or loading up assets in 3DSMax. Does anyone know if I’ll be able to access my XServe RAID with Parallels via the dual channel fibre channel card?
-
The project file itself is 2.6 MB, and the Capture Scratch for it is 59 GB, but I stripped a lot of the media out and saved a new project w/ the same lagging results. I checked on restart, and it looks like before I even open FCP my kernal_task is 1.97 GB VM, and my overall VM is 11 GB. After loading the project, my VM goes up to between 13-14 GB. And as long as I don’t load the .motn clips in my timeline, I’m okay w/ physical RAM and I’m not constantly crashing. So, maybe it’s nothing to do with the kernel_page at all, although it seems like it shouldn’t be maxed out on 2 GB. Can someone check their kernel_page VM size on a fresh restart in the Activity Monitor? Maybe I have a driver conflict?
If it’s not that, then it’s just that ProRes is not only not capturable w/ G5s, it’s also not very useful for editing at all. I have a ProRes HQ 720 24p file laid out in a ProRes HQ 720 60p timeline. The file is only 1 track for 2.5 minutes – it’s all chopped up w/ some clips being .motn files for motion blur and match moving, and the rest w/ 3 way CCs and SmoothCam. Is anyone else having load times of several minutes for ProRes based projects on G5 systems?
-
I’m familiar with the KinoFlo Divas that use PC bulbs, but I didn’t realize that they are now using T5 bulbs too until I saw some at NAB this year. Does anyone know what KinoFlo rigs are using the T5 bulbs? They have a great range of colors. I use them to light my reef tank w/ a mix from 3000K to 20,000K and a 420 nm wavelength actinic.
-
Aargh, well I’m seriously disappointed. I posted a thread about this problem in the Final Cut forum. I’m running FCS 2 on a dual 2.7 w/ a 6800 Ultra, a Kona 2, and an XServe RAID. This computer was top of the line when purchased less than 2 years ago. It can handle multiple tracks of DVCPRO HD and uncompressed w/ multiple effects applied. And now … well I’m finding out that it can’t capture more than 1/3 to 1/2 of a single 720p stream w/ ProRes.
-
Yeah, the game engine is doubling the frames. My idea was since it’s an exact 2:1 reverse pulldown it would be great for my needs to drop the unnecessary frames (kind of like capturing in 24PN does when recorded to a P2), and then I’d export the final cut as 59.94 for broadcast, and keep it as 29.97 for the game asset and let the game engine do it’s duplication again.
It appears that I just plain can’t use ProRes in HD; my G5 isn’t fast enough 🙁
Too bad since my dual 2.7 w/ 6800 Ultra and XServe RAID was the top of the line when it was purchased new less than 2 years ago…. -
Well I just took a look at the AJA Kona forum here and there’s a long thread there about this exact problem – I haven’t finished reading yet so I’m hoping there’s also a solution….
-
No, no. I’ve been capturing at 59.94. But, I’d prefer to capture at 29.97 if possible. The game renders at 29.97 and doubles each frame to meet 59.94 specs. So if I could capture at 29.97 I’d have half the data to work w/ since it’s useless data to me anyway.