Welcome to our community

Be a part of something great, join today!

  • 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 :)

Sony Vegas Support?

Just Jpeg. THe file size is so small compared to uncompressed, while the image quality remains excellent even after heavy gradings.

The only issue with vegas is the 8bit limit.


MacGregor, you should get ahold of Sony development (at madison) and see if they will let you get the beta version of 8 that supports importing OpenExr to the time line. No 8bit limit on that. PM me and I'll give you the email.
 
Had to move over to FCP once we got our HVX, although I still cut long form stuff on Vegas.

Vince, I cut HVX footage on the Vegas timeline all the time using RayLight by dvfilm.com. Drag&drop the native files or transcode them with the RayLight tool as needed.

best,

Michael
 
Just wondering if there were any updates on Vegas workflow.

I'm a FCP guy, but this next project will be cut on Vegas. My job is to take the R3D files and give him the best quality files I can for an online edit. I'm not sure if there are any new supports that weren't mentioned since the last post in this thread.

Any suggestions are appreciated.
 
You can render QT uncompressed 8bits, or aja 10bits RGB. VEgas will ingest both.

Sorry for the ignorance. I'm a Vegas users who hasn't taken delivery of my camera yet. Does the camera render QT uncompressed 8 bits or 10 bit RGB or is another piece of software needed? Thanks!
 
The camera writes Redcode R3D files and quicktime proxy files (very small, basically just header info), that is all. Any rendering to other compressed or uncompressed formats would have to be done on a separate computer using software such as Red Alert or Redcine.
 
i thought i would liven up this thread again, now that there's an SDK and Adobe support is next week, i believe there will be a solution. Although vegas only supports up 2048 by 2048 for now. Editing 2k files or lesser should be possible
 
Trying ask SonyVegas about upcoming features is like trying to teach a pig
to sing. It's a waste of time and it annoys the pig.
 
Vegas does (did) have their own SDK to provide for 3rd-party plugins.
http://www.sonycreativesoftware.com/dl/dl.aspx?dwnid=47

Unfortunately, it dates back to 2003 (!) and lacks important features. In particular, it does not support the 32-bit mode in Vegas 8. The only other option is 8 bit video. There is a more-current scripting SDK but it does not give any access to the framebuffer which would be needed to write any external codecs for Vegas.

I wrote to SCS last year and expressed the need for an updated SDK. They said they appreciated my feedback. Take that for what it's worth.
 
Sony Vegas Pro is rumored to be working on 4K compatibility in their next version.
That makes me wonder: Is Sony secretly planning a 4K version of F35 in the near future?
 
Anyone's guess, I suppose. I do know that Sony Creative Software and the Sony camera divisions are separate, and from what I've seen they don't seem to talk much to each other.
 
they do occasionally talk to each other, especially when the PMW EX1 came out.
 
Vegas does (did) have their own SDK to provide for 3rd-party plugins.
http://www.sonycreativesoftware.com/dl/dl.aspx?dwnid=47

Unfortunately, it dates back to 2003 (!) and lacks important features.

This SDK is for developing DirectX video filters. It's not for writing CoDec/File import plug-ins. Also, it was updated in 2006, not 2003.

Anyway, with the Red SDK release, hopefully we will soon see some kind of support for Vegas. I have used it several times and it is usually fast and efficient for editing, even though the newer version seems to be a bit slower at start-up.
 
SonyVegas does have an SDK for doing more than DirectX filters, but it's beta and they are discouraging using it until the new 64bit version comes out this fall. The DirectX sdk has bascally been replaced with the .net based scripting interface. Still it would be nice if they supported DX9 and newer.
 
Anyone here tried the latest Cineform tools with Vegas 8 yet? Is there still an 8-bit color limit and, if so, does anyone know if the upcoming Vegas update (supposedly due in September) will support Cineform's 12 bit color? (And, oh by the way, what's the use in having supposed 32-bit float point precision internally if you can't ingest files greater than 8-bit? Still trying to figure that out since 32 bit color was trumpeted with the release of Vegas 8.)

I'm in the middle of a project (still using Vegas 7) and don't want to update and download the Cineform trial until I have sufficient time to play with it, but I'm very curious as to the impressions of those using this combo. Will be getting my camera probably in late October, so I'll need to make a decision on sticking with Vegas or moving to Premiere soon.
 
Anyone here tried the latest Cineform tools with Vegas 8 yet? Is there still an 8-bit color limit and, if so, does anyone know if the upcoming Vegas update (supposedly due in September) will support Cineform's 12 bit color? (And, oh by the way, what's the use in having supposed 32-bit float point precision internally if you can't ingest files greater than 8-bit? Still trying to figure that out since 32 bit color was trumpeted with the release of Vegas 8.)

I'm in the middle of a project (still using Vegas 7) and don't want to update and download the Cineform trial until I have sufficient time to play with it, but I'm very curious as to the impressions of those using this combo. Will be getting my camera probably in late October, so I'll need to make a decision on sticking with Vegas or moving to Premiere soon.

Vegas supports 10bit 4:2:2 avi files (based on the AJA developed codec) as their native format. Outside of that, they still do not support DirectShow or QT video > 8bit. Neo works, but only at 8bit 4:4:4 for now. If you can find AJAs' codecs for the Xena boards, download and install them, then you can render directly to them and use the avi in Vegas. But, they are very large.
I'm hoping the new express features of Cineform overcome this limitation.
At this point, it's useless to speculate what Vegas will or won't support with the upcoming release. I'm sure features are frozen at this point.

Cineforms' Express options actually have me interested in pulling in video to AcidPro for mixing soundtracks (up to 5.1). Both Vegas and AcidPro will output Broadcast wave files for other programs to use.
For stuff like that, 8bit is more than enough for now.
 
Anybody know of any substantial changes versus Vegas in the last VPro8.0c VPro8.1 versions? Thanks.
Thommes
 
"what's the use in having supposed 32-bit float point precision internally if you can't ingest files greater than 8-bit?"

don't know the technical stuff - can only mention my test results ...
when you have certain clips that are a bit dark ( and you lighten them) or you do heavy CC the 32bit looks much better - many times it's the difference between banding and no banding ....
i use 2k 8 bit cineform.mov clips in Vegas (red 4k clips rendered out of FCP) and i have no objections to the 8 bit them when final out is 1080 blu ray ...
every now & then i'll have a clip that needs heavy CC or i need to lighten 1-2stops - for those i go back to the 4k r3d and CC then render back to 2k with new CC = solves the problem ... i would prefer 10 bit but have no problem with the 8bit for HDTV or blu ray disc...
 
Unfortunately, it dates back to 2003 (!) and lacks important features. In particular, it does not support the 32-bit mode in Vegas 8.
You can ask SCS for this information... I did and got a reply. If you need help with this, you could ask Matthew Chaboud and he'd be the person to talk you (or he could point you to the right person). I could help you get in contact with him if need be.

(On a sidenote: Aargh... writing some Vegas plugins is on my to-do list.)

an updated SDK.
Well they have to figure out if it's worth the return time + money spent doing that. They'd also have to figure out if people would write plugins using the updated plugin architecture. e.g. you see Magic Bullet (the new version) having a Vegas-compatible version last.

That being said, there are some new features of Vegas that appeared that I don't get (e.g. features which Vegas users on the SCS forum didn't really ask for).

- It may be better to request what you're REALLY after. e.g. could you please update the SDK so that 3rd party vendors can build a good image stabilization plugin, or a noise reduction plugin (without the current workarounds).

Personally I think they should just implement a 1-point motion tracker with good control of panning the image around. These features are in AE and they work fast and pretty darn well. Optical flow approaches are a waste of time IMO (e.g. Smoothcam). Anyways I digress..

even though the newer version seems to be a bit slower at start-up.
Try disabling the media manager if you don't use it.
(I never got into it since I don't deal with large stock footage / music / image libraries, which is what it is good at.)

"what's the use in having supposed 32-bit float point precision internally if you can't ingest files greater than 8-bit?"
You can do things like linear light processing.
http://www.glennchan.info/articles/vegas/linlight/linlight.htm
 
Back
Top