George Costacovich
Forum Replies Created
-
Many thanks for your quick response Todd.
Yes 4gb is not much RAM but its the maximum supported by XP 32 bit, although the OS only sees about the first 3.25 gig. Previously with AE7 I was using Gridiron’s Nucleo and that was able to fully max out all cores to 100%, although with some delay as it took time to open many instances of AE. Clearly the Render Multiple Frames Simultaneously function is a different kettle of fish.
I had read the relevant bit in the help but hadn’t worked out to give each CPU so much RAM. If I upgrade to 12gb of RAM and Vista 64 bit will be able to use all my cores effectively?
Many thanks again.
-
Thanks for the speedy response. Just tried importing the AAF back into the avid and it worked fine, came back identically and correctly linked to the consolidated media. also it had retained sequence timecode. I don’t need individual clip TC but sequence timecode is a must.
Indeed, though Vegas seems to always be searching for the original source media, I can obivously manually tell it what media to use but it’s not a great workaround, especially if i’m dealing with something that has a lavish tracklay and lots of clips.
-
OK so just did a simple consolidation of wav audio in a sequence, about 8 tracks. I consolidated first to a fresh folder, then exported an AAF which linked to that media. Then i imported this into Vegas. I got the same messages; Vegas is looking for the original source media rather than the consolidated avid media which is completely different. As a result no media is found by Vegas. Also I noticed no timecode comes through, is it supposed too?
Ollie
-
Thanks for your reply Dr. D! I was sort of aware of the video issues so I’ve have done all my tests (but one) using wav audio media. In the one test i did with MXF DV Vegas gave an error saying it couldn’t use the file. I believe what your suggesting will be almost the same as one of the AAF export settings itself, ie copy media to new location, which I am already tried with same results. But as you suggest I will try later as a two stage process, doing a straight consolidate of the sequence to one folder and then doing an AAF which just links to that new media. Do I understand that correctly? Shame it can’t happen in one go.
Also I forgot to mention previously that though the AAF timelines themselves seemed correct and the cuts were in the right place sequentially, the media that had come though or been found by Vegas was often the wrong section of track, and parts of the same track were repeated instead of following the cuts in that track. hope that makes sense, hard to word!George
-
Have just been trying it out, amazing! well worth the cash
-
Thanks guys will try the gridiron. Have just also read about the render engine. Does nucleo work better than using a render engine on the 2nd CPU?
-
Going Cheap!
Only
-
thanks for that. i don’t have access to FCP though and thought it was probably accomplishable in AE in the mean time.
-
yes let’s hope it does change. avid always change their minds and are generally quite rubbish with releasing anything on time. and there’s a lot of peeps on the avid forum having achingly long imports and renders using DNxHD. as you say, this kind of sluggish performance is not that useful.
-
Just did some more research on this. Avid say that with Xpress Pro HD you will be able to ‘play and edit’ footage encoded with the 8 bit DNxHD codecs. This means you can import DNxHD QTs and use media that’s been digitized on an Andrenaline and you will be able to render effects in titles in DNxHD over any HD footage. But you can’t capture or digitize DNxHD or layoff back to tape.
George