Support for Sony Vegas - was: there goes my POST

[Kyle Mallory]

I seriously hope you guys are right... The issue here IS NOT, can you edit footage aquired with a RED camera in Vegas. But, rather, can you edit native R3D files in Vegas.

To the first: Of course, RedCine, and/or Scratch.
To the second: No. Not yet, and IN MY OPINION, based on things said AND NOT SAID, it won't happen. Please! someone from RED prove me wrong.

These are the same answers given to "Can I use Premiere, AfterEffects, Avid, Smoke, Lustre, Pirahna, Main Actor, Pitivi, Blender, Sonic, etc, etc.."

And to state once more, I have talked to multiple people at different post houses, who use different systems, who have expressed an interest in being able to edit RED footage, and who have said "We've heard that Apple and Assimilate have exclusive agreements."

I HOPE those people are wrong... But I have YET to see, hear, or read, anything to the contrary.

 

[GlennChan]

Kyle, check out the links in my previous post.

During an earlier test I did it loaded just fine. That's not a guarantee for support though! But I like Vegas a lot so its definitely on my radar. I'm hoping they'll move to more than 8-bits soon, cross your fingers!

Oh, it also has a maximum of 2K x 2K resolution at the moment....

In this instance it loaded REDCODE RAW just fine. Keep in mind that you can load RAW footage into most QT supporting applications. REDCINE is another path to process your footage more akin to the film process.

 

[Kyle Mallory]

Glen, checked out the topics. Thanks. They make me feel a little better... but just a little.

At the heart of what we are talking about is this:

Licensing is a question we haven't answered.
__________________
Code Chef @ RED

So, if I have a RED camera, and I have REDCINE, which the QuickTime reference files utilize. Cool.

But if I'm a post house, and all I got is some R3D files from a client, and possibly worse, my facility only runs Smoke on Linux... I'm screwed. Its the nature of the licensing (or the lack of it) specifically of the R3D format and REDCODE RAW codec that is on my mind.

I would be interested to hear from people with the camera about how well editing in Avid/Premiere/Vegas/etc is working with the Quicktime files.


Ooo! Speak of the Devil: http://www.reduser.net/forum/showthread.php?t=5414

 

[Stokestack]

I think it is a Sony thing. Why would Sony want to support DVCPRO (Panasonic) and Redcode (RED)? Sony wants to sell you a Sony camera. Those work great with Vegas.

The Panasonic situation is different from Red. Panasonic has failed to provide a DVCPro codec; Red IS providing a codec, which is obviously the correct approach. Panny's approach ensured that 95+ percent of the computer-using public had no way to use the footage from their cameras; imagine what would happen if Epson came out with a printer and no drivers, and then sat around waiting for everyone else to write a driver for it.

I don't blame Sony for not devoting its resources to provide something that should've come with the camera. It makes no sense for every software vendor in the marketplace to redundantly write code to pander to each hardware product, when the hardware vendor could've written that code once and delivered it with the camera.

 

[Joe Carney]

The problem is both Sony and Pana are unable to come to an agreement that satisfies both of them. Sony has stated publicly they would like to add DVCPRO HD, Pana has refused. Anything more you have to ask someone from Panasonic. It's not like DVCPRO HD is all that good, but people use it anyway.

I'm looking forward to Cineform Wavelet supporting 32bpc in Vegas myself.

 

[GlennChan]

But if I'm a post house, and all I got is some R3D files from a client, and possibly worse, my facility only runs Smoke on Linux... I'm screwed.

For onlining you'd probably want to send DPXes to Smoke. Hopefully it can conform data files from an EDL. (I don't use Smoke so I can't say. You'll likely need Redcine, otherwise you'll be manually recreating the edit.)

Or conform the edit in some other program (maybe FCP, maybe Scratch) so that you can spit the material out via SDI into the Smoke.

Presumably this is what one would do anyways.

2- Hopefully your client gives you all the necessary r3d files, any other source material, cutting copy / video reference of the offline, and a properly formatted EDL. Cross your fingers...

 

[Miguel "Macgregor" De Olaso]

GlennCHan wrote "--Import 10+-bit formats without throwing away the extra bit depth. e.g. DPX, cineform, openEXR"

When importing 16bit tifs, or 10 bit qt video files in VEgas 8, the extra bits are throwed away always? Did you get this assumption by testing or it is written somewhere?

 

[GlennChan]

When importing 16bit tifs, or 10 bit qt video files in VEgas 8, the extra bits are throwed away always? Did you get this assumption by testing or it is written somewhere?

Vegas 8 doesn't import DPX or openEXR. Cineform other people are telling me that it's 8-bit.

In my tests, PNG TIFF and PSD all import at 8 bit (even if the file is 16-bit).

I haven't checked the Vegas manual on this... I don't think it says anything about the bit depth various file types import as. (No even for "uncompressed", which is special and will input+output 32-bit float.)

2- Vegas can input/output 10-bit over SDI to the 10-bit SonyYUV codec I believe. You may need the aja cards to do this(?).