John Rofrano
3
COW Coins
Forum Replies Created
-
[Ole Kristiansen] “Native ProRes support! I lack the ability to export the prores.”
Yea, it’s read-only and I question how good this first generation technology is.
I have to agree, people who shoot ProRes should buy a Mac. You should not be using ProRes with Windows. Its just asking for trouble.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Jon Muro] “Yes I have QuickTime 7 installed. I can drop most .mov files on Vegas timeline but then I get some that will only show the audio. “
What codec does the QuickTime file contain? I believe that Vegas Pro (any version) cannot display ProRes 4444 no matter what you do.
Open the file with QuickTime Player and use the Inspector Windows (Ctrl+I) to see what video codec it’s using. If it’s ProRes 4444 you are out of luck.
Let’s us know what it uses.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Steve Rhoden] “Yeah, but what happen when you are a Pro editor, and the Television station requires all content submitted to them be in .mov format or another flavor of the Quicktime format to go on air!”
At some point you have to face the fact that most of the industry professionals are using a Mac and if you want to be compliant you should use one too. This is one of the reason’s I moved to the Mac. I have no problem sending ProRes 422 MOV files to broadcast stations from Final Cut Pro X. It’s a simple matter of using the tool that is compatible with everyone else’s tool. Why fight it? This has nothing to do with Vegas Pro being Pro or not. It’s about collaborating with other professionals using compatible tools and formats.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Ross Stark] “What file sharing system do you guys use/recommend?”
I deliver digital files via DropBox. Don’t make it public. Give each client the link and no one else can see it except them. Of course, they could share it, but they could have shared copies of your DVD’s as well. Everyone knows how to copy a DVD these days.
[Ross Stark] “What file container, compression, other settings would you recommend?”
I would use MainConcept AVC with either the Internet 720p or 1080p setting. I’ve seen some people charge more for the 1080p version than for 720p which gives you price flexibility (i.e., high price for higher quality).
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
Do you have QuickTime for Windows installed? If not, Vegas Pro 13 and earlier cannot work with the files. Vegas Pro 14 added native support for reading QuickTime files so it doesn’t need to have QuickTime for Windows installed. So yes, Vegas Pro 14’s support for QuickTime is better.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[marcel gächter] “Is there a difference in the render engine of Movie Studio and Vegas Pro?”
Not for the same version but possibly yes for different versions. So Movie Studio 11 and Vegas Pro 11 are probably the same rendering engine, but Movie Studio 11 and Vegas Pro 13 might not. I noticed that Vegas Pro 13 performance is slower than Vegas Pro 12 for me so I never bothered to use Vegas Pro 13 for any serious work.
[marcel gächter] “Will I have smooth videos using a camera which records at 50p instead of 25i?”
Yes, the more frames per second the smoother the motion.
~jr
-
Well… in fairness to MAGIX, if I was a Windows developer and kept my tools updated each year by investing in new ones, everything would have been compatible. I don’t even own a Windows computer anymore (I’m on the Mac now). My Windows development tools are from 2008 but they still worked with Vegas Pro 13. It is Vegas Pro 14’s use of .Net 4.0 that broke the tooling. My tools only support up to .Net 3.0. ? So it wasn’t anything MAGIX did that is causing my problem. It is more of a Microsoft tooling issue with .Net Framework.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
Do you know how to use Pan/Crop and make Keyframes? Is that what you need more details on?
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
Make sure that your project settings in Vegas Pro and Movie Studio are the same. In fact, if you want to do a fair comparison, open the Movie Studio project in Vegas Pro and render the same project. You should get the same results if the render template is exactly the same.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Steve Rhoden] “John, MAGIX chose to make Vegas Pro 14 incompatible or was it unavoidable due to legal reasons of the change of ownership where the namesake “Sony” had to be stripped from everything entirely?”
Rebranding something is one thing. Breaking backward compatibility of an API that no one will see except developers is, IMHO, going too far. Now everyones favorite plug-ins stopped working because of it and developers must bear the burden of fixing it. It was a bad idea regardless of who’s idea it was.
[Steve Rhoden] “I know you have a lot of work ahead of you to update all those tools for Vegas 14 compatibility, but hope its accomplished soon for the many users of this new Vegas Pro….”
I’ll be honest with you, I still don’t have a way forward. This change broke all of my development tools because it required upgrades to .net 4.0 that some of my tools are not compatible with. So I’m not sure how I’m going to solve this dilemma.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com