Saturday, November 21, 2009

RE: [Avid-L2] Re: Mac Smoke Official

Hmmm... I have to be very careful what I say here. So choosing my words with
said care...

A (non Avid) developer that I know has suggested to me that if Mr Sunglasses
would allow deeper access to .r3d files than is currently permitted through
the SDK then with current PC and GPU technology it would be possible to have
far faster and more effective access to the files, and MUCH quicker
processing (including debayering). Assimilate have already shown what they
can achieve with direct access to .r3d files but the same developer reckoned
that processing could be an order of magnitude faster than that achieved by
Scratch... "You just need to think laterally" he told me.

Maybe he was wrong. Maybe he wasn't. Either way, for those companies not
in bed with Red, the SDK is undoubtedly the crippling factor right now, and
not GPU/CPU speed.

Tony


HD Heaven Limited (company no: 04620550) is registered in England and Wales
at Branston Court, Branston Street, Birmingham BL8 6BA

-----Original Message-----
From: Avid-L2@yahoogroups.com [mailto:Avid-L2@yahoogroups.com] On Behalf Of
oliverpetersvidy
Sent: 21 November 2009 14:38
To: Avid-L2@yahoogroups.com
Subject: [Avid-L2] Re: Mac Smoke Official

Ian,

I think the whole resistance we have to the RR idea is because it goes in
the opposite direction of everything being done by every NLE (and other
video gear) manufacturer. Everyone is moving towards - or being pushed
towards - "off-the-shelf" hardware + custom software. And they are all doing
it for the obvious reason that it is the only sustainable business model if
you aren't a boutique developer. This means that more and more of the heavy
lifting is being done by CPUs and to a greater extent GPUs. This means
NVIDIA, ATI and potentially Matrox.

In order for RR to work within the NLE video stream, it basically has to
function in the same way a GPU inside an NVIDIA or ATI card does now.
Multi-stream commands have to be decompressed, combined with effects,
displayed and ultimately re-encoded. Currently it's the software+CPU that's
doing the decoding and re-encoding and the CPU+GPU does the rest. You are
now expecting the RR card to do both and I just don't see that happening.
ATI's and NVIDIA's advancements come because of video game development - a
mass market driver. NLEs reap the benefits of that work.

You may be right that ultimately RED has to build its own special purpose
NLE. If so, I wouldn't expect it to be very viable for anything other than
exclusively REDCODE media projects. Think in the context of your own case.
You have discussed using P2 and Canon media with your RED. How does that
work in the native REDCODE/RR world? I don't think it does.

Don't expect Smoke on Mac to be the answer to this. Autodesk/Discreet has
never made there own hardware. Going to the Mac means embracing even less
customized gear than Smoke on Linux. If anything, I'd place my bets on
Quantel. They are more likely to still tinker with the "off-the-shelf"
products and blend those with proprietary tools to get advanced results.

So the bottom line for me is that RR will probably be a fast decoder to go
to displays or an intermediate codec for quite some time. At best, it may
become the core of a DVS or Assimilate-style assembler/grader.

- Oliver

------------------------------------

Search the offical complete Avid-L archives at: http://archives.bengrosser.com/avid/

Everything you MUST know about Color Correction in one book: http://tinyurl.com/ColorCorectionforvideo Get your copy todayYahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/Avid-L2/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/Avid-L2/join
(Yahoo! ID required)

<*> To change settings via email:
Avid-L2-digest@yahoogroups.com
Avid-L2-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
Avid-L2-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

No comments:

Post a Comment