Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

What are my options for export to other software?

Jeremiah McLamb

Jeremiah McLamb

Well-known member
Joined
Apr 18, 2007
Messages
206
Reaction score
0
Points
16
Age
43
Website
www.jerfilm.com
What are my options for getting my cut out of Vegas and into a color correcting and grading program such as color, scratch, lustre while still utilizing the r3d file?

Jeremiah
 
very slim ( or should that be zippo , none, zero ,forget it ) .... i have never heard of any successful EDL, AAF from Vegas to CC app using r3d files .. Vegas use to claim that you could use the export EDL ( no more then 2 video tracks 2 audio, no compositing , simple transitions ) to AVid ...

i use to render out to a HD file to take into CC app
note: the only 10 bit i/o of vegas is using the 10bit sony YUV codec ...

using 3rd party 8/10/16 bit codecs
yes, it can process using 32bit float but in the end ( rendered data to hard drive) it all goes back to 8 bit ..
currently i CC in Vegas , then out to bluRay ..

sony did have a hi-end NLE , can't remember the name of it but it could take in the Vegas Veg file into its TL = perhaps from there you could get a EDL or other?, out of it to take into CC app ??
 
Jeremiah McLamb said:
What are my options for getting my cut out of Vegas and into a color correcting and grading program such as color, scratch, lustre while still utilizing the r3d file?

Jeremiah
Click to expand...

Considering that Vegas works naitivly with R3Ds i would have high hopes about importing the cut to Scratch. In the Vegas tools menu there are the options to EXPORT EDL and EXPORT XML. The export EDL works very well but i don't have a Scratch so i can't give it a try.

You can also export DPX or EXR frame sequences from Vegas at any resolution you want.
 
Miltos Pilalitos said:
Considering that Vegas works naitivly with R3Ds i would have high hopes about importing the cut to Scratch. In the Vegas tools menu there are the options to EXPORT EDL and EXPORT XML. The export EDL works very well but i don't have a Scratch so i can't give it a try.

You can also export DPX or EXR frame sequences from Vegas at any resolution you want.
Click to expand...

I've wondered why there haven't been more people using the EXR/DPX options. Those file types are industry standards. Essential for a VFX heavy feature.
 
donatello b said:
very slim ( or should that be zippo , none, zero ,forget it ) .... i have never heard of any successful EDL, AAF from Vegas to CC app using r3d files .. Vegas use to claim that you could use the export EDL ( no more then 2 video tracks 2 audio, no compositing , simple transitions ) to AVid ...

i use to render out to a HD file to take into CC app
note: the only 10 bit i/o of vegas is using the 10bit sony YUV codec ...

using 3rd party 8/10/16 bit codecs
yes, it can process using 32bit float but in the end ( rendered data to hard drive) it all goes back to 8 bit ..
currently i CC in Vegas , then out to bluRay ..

sony did have a hi-end NLE , can't remember the name of it but it could take in the Vegas Veg file into its TL = perhaps from there you could get a EDL or other?, out of it to take into CC app ??
Click to expand...

Ithought you could maintain a 10bit pipeline with dnxhd (QT)
 
the only 10 bit i/o of Vegas 9c is using sony YUV 10 bit codec ...
all QT in Vegas is currently 8bit , you can select 10/16bit QT/AVI codec's but vegas will only do 8 bit when it lays the data to file on disc ( you can use 32bit float to process that info into the 8bits, which helps with heavy CC/FX) ...

the DPX's Vegas creates are 8bit too ...

if i recall correctly , Lucas Wilson( scratch ) used Vegas in the past .. you might ask him about Vegas to scratch ...
 
donatello b said:
the DPX's Vegas creates are 8bit too ...
Click to expand...

No they are not.

Go to your project properties and select 32bit float in the Pixel Format selection. When you export your DPXs they will be 16bit int.

Edit: To be sure, i just exported some DPX and EXR frames with Vegas 9.0c (64bit version). They are both 16bit.
 
Miltos is correct .. switch to 32bit float and you will not get 8bit DPX's DPX's ... same with Tiff's , .... from the test i just did it didn't matter for EXR , 8bit or 32bit float they all came out 4k X 2k x128

the 10bit i/o using sony YUV 10 bit codec is up to & including V 9c ...since that is current version then it appears nothing has changed since the last email i received last fall about 8/10/16 bit video codec's ...

when a new version is released to public i'll ask them again about 8/10/16bit video codec's ...
 
Vegas to FCP =
must have automatic duck pro import FCP 2.0 on Mac

in vegas 9 use AAF ( avid) for export ...
then on MAC use automatic duck .. it will create a file for FCP ...
open that file in FCP and lead it to media ...

NOTE: have not tried this using R3D clips ... it has worked using mix of dv, HDV, HD , P2 clips
 
As far as issues with memory during rendering on Vegas, I ran across this a while back and tried it, works great. However, I'm on V8 and not working with Red footage. It would be interesting if this helped for that case. works wonders for H264.

There's a post on the vegas forum for a 'memory modification'. You can find it if you search part of the text below. Normally I would just paste the link but the site's down as I write this. My apologies to the original author..I'll try to remember to add the original post.

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

Most 32 bit exe and dll files have a 2 gig maximum memory cap. I've been playing around with CFF EXPLORER (free download) which is a program that allows you to easily open the exe or dll and click the 2 gig memory switch that allows it to use more than 2 gig.

I reset the memory flags in
vegas80.exe
m2tsplug.dll
mcstdh264dec.dll
sonymvd2pro_xp.dll
to "greater than 2gig" and did a render of which I almost always crash on (avchd at 1920 render to m2ts 1920@16Mb/s with AC3 audio)

It didn't crash!
In fact memory usage shot up higher than i had ever seen vegas use (it shot up to 5gig and leveled off.... usually it climbs no higher than about 3.5 gig and creeps a little)

....
open the program
goto file\open
then find the file... in this case it would be Vegas.exe
On the left side you'll see "NT HEADER".... "DOS HEADER"... etc
Highlight "FILE HEADER" under "NT HEADER"
On the right side you'll see a chart and in the bottom right corner you will see "CLICK HERE"
Click on that and a check box menu system will open.
Scroll down the menu list until you see "app can handle > than 2gig address space" and check that.
Save the file and close.

Open the others and do the same.

MAKE SURE YOU DO A BACKUP COPY OF THE FILE BEFORE CHANGING IT JUST IN CASE YOU GET INTO TROUBLE!!!

On another note.... rendering stability has CLEARLY and MOST DEFINITELY improved DRASTICALLY
.
.
.
As long as the files work with that flag set they can get access to 3GB of RAM instead of 2GB. It sounds like that's enough to make a difference - for now. You can expect them to run out of memory again pretty soon I'd imagine. A truly 64-bit executable or dll would probably have access to more than 3 GB of RAM.

One of the things that probably needs to be stressed is that you should be running all of this under a 64bit OS so that real RAM can be made available. Otherwise you're increasing the need for swap space. (If you're running 8.1 then of course you're also in a 64-bit OS).
 
Here's the link <http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=647907>
 
You must log in or register to reply here.
Back
Top