Ok thanks
|
|
Hmm,
I just noticed that the 5600 is listed on the Assimilate website as 'in process'.
Lucas, now that the SDI versions are out, I was thinking of getting a 5600 1.5gb sdi for our planned Scratch suite, do you know if they are supported yet ? I really want to go with the 80 series gpu and it's miles above the old chipset.
Cheers,
S.
Music to my ears :)
Hi Lucas,
I recently received a quote for an indecent workstation: 4x4 cores on new AMD, FX 5600 SDI, 8x146 sas 15K, 12 gig ram, controller raid card, bluefish 2K card.
Is Scratch 64 bit : 12 gig of ram should be wecome.
Are multicores usefull when process the final print (is GPU is for realtime and cores for final output?)
Does Scratch would support I/O directly with batch conform, etc...
thanks again, mathieu
Hi Mathieu,
To answer your questions...
SCRATCH is not currently 64-bit.
Multicores are only useful when processing Plugins, or dealing with REDCODE. All color processing is done on the GPU, and the cores are mainly traffic cops moving bits around.
SCRATCH does not do direct video ingest. For that, we typically partner with Bluefish, as the Lust card will batch digitize an EDL to DPX files and insert proper metadata into the header. In addition, Symmetry (the software that comes with the Lust) will also populate a SCRATCH Construct with clips via the background XML engine in SCRATCH.
Cheers,
Lucas
-----
ASSIMILATE, inc.
LA, CA, USA
and tested by us - all good - however, you should know that all that extra TEXTURE processing doesn't do anything for Scratch performance. 4600 SDI kicks the same ass in Scratch as the 5600 SDI - however, if you use the workstation for other apps (3D, etc.) then cool - and I am not even sure you can still find the 4600 SDI cards around - anyway, 5600 worked great for us in all of our tests with BOXX.
good to know. Thanks o lot lucas. Hope scratch will go on 64 bit and multi GPU.
And Lucas, we have a discreet smoke here. We thinking about adding a FCP and a scratch to make our offline and grading. Have you worked on a similar workflow?
Smoke can handle directly XML from FCP. It take the XML and the footage too (but can't handle R3D footage). A cool workflow is to replace the footage of the offline with the footage of the graded material from Scratch in DPX. So when importing in Smoke, the XML "track" the graded material in image sequence. And then we can add effect on it. There is a lot of issue here (QT vs Images sequences, head and tail management, media management) but the big picture is there.
Thanks
| « Previous Thread | Next Thread » |