#Sony vegas 16 and prores how to#
#Sony vegas 16 and prores pro#
#Sony vegas 16 and prores professional#

Vegas Pro 13 Edit software (MSRP $399.95), Vegas Pro 13 software (MSRP $599.95), and Vegas Pro 13 Suite software (MSRP $799.95) will be available for digital download on Apwith physical products available May 5, 2014.

#Sony vegas 16 and prores professional#

In addition to technological advancements that span the production process, from ingesting to editing to archiving, weвЂ™ve created a set of phenomenal values by bundling Vegas Pro 13 with other workflow-integrated professional applications, both from Sony Creative Software and key partners.вЂќ вЂњWe are excited to announce Vegas Pro 13 at NAB and provide live presentations and in-booth demos of the new key features. One example is the Vegas Pro Connect iPad app, which provides a remote collaborative review process for clients and team members,вЂќ said John Freeborg, vice president of Sony Creative Software. вЂњVegas Pro 13 takes giant steps toward making the total multimedia creation experience faster and easier than ever. Vegas Pro 13 brings new collaboration tools and streamlined workflows to professional content producers faced with a wide variety of multimedia production tasks.

#Sony vegas 16 and prores how to#

I sure would like to know how to fix this!.Sony Creative Software, a leading global provider of professional editing and authoring solutions, today announced the latest upgrade to its Vegasв„ў editing technology. I got the same issue on two different kinds of Mac, one having Leopard, the other having Snow Leopard,В and different versions of QuickTime on each (7.6.4 and 7.6.6) The exact DNxHD format I rendered toВ was:

It was a 720p50 project going to a 720p50 mode of DNxHD. However in contrast to kufloyd, I rendered to 720p50. Sounds therefore like an FCP pernicketiness! In that case they could at least have a more meaningful error message. However on the same machine, it plays OK in QuickTime Player. I got the error message that the codec was not found.

I rendered from Sony Vegas (9e) to DNxHD and tried to import it to FCP (7.0.2). In case it helps, I have an almost identical problem. You could try re-exporting your clip and this time make sure you don't enable the Alpha, maybe FCP is getting tripped up on that? So, I don't really think there is anything wrong with the file itself, but perhaps FCP is just unable to interpret the codec fully to 'decompress it'. If I change my Import Settings to tell Avid not to Resize it, then it actually comes in Pillarboxed and with the Letterboxing on the native file, it looks like a postage stamp.Д«ut, in the end I was able to successfully import your clip into my Avid system at DNx220X (RGB) and got it to playback etc. I can see letterboxing on the QT player file too. What I also found weird is that if I tell the clip that it is sized for the current format in my Import Settings, I get letterboxing on the image. AFAIK, FCP also works in RGB but I believe that there is a setting one can change to make it work in Broadcast. So, I'm going to assume that Vegas works with RGB color space and not Broadcast (601/709). If I change my import to RGB, it seems to work. Now, I imported your clip into a 1920x1080/59.94 Avid Project at DNx220X with 709 color space setting and I got an error. It doesn't seem to bother Avid when I import it, but FCP might not like it too much. Secondly, I notice that your clip has an unnecessary Alpha Channel ('Millions+' - the + indicates an Alpha). AFAIK, you can't have DNx220 (or 220X) in a Thin Raster format like 1440. This is saying that it's 1920, but you said your FCP guy reports 1440. Developed by Apple Inc., ProRes is a codec that was released in 2007 along with Final Cut Studio 2. This is not the case with H264 files, and they do require more processing than ProRes. So, first major thing I notice that is different from what you said above is the frame size. To scratch the surface, ProRes files are loosely compressed, and your GPU finds it easy to process them during both editing and playback. When I open it with QT Player, it shows it as beingДЎ6-bit Integer (Little Endian), Stereo, 48.000 kHz It seems as they're using DNxHD as the common denominator. IIRC, ProRes can only be read by PCs so he wouldn't be able to produce a ProRes QT for the FCP user. Every time I think there must be a simple solution for something, there's some obvious reason for the complexity and I'm just not seeing it.