John Rofrano
3
COW Coins
Forum Replies Created
-
[steve wilson] “That’s how you fix the gamma shift in quick time pro. Not sure if there is something similar in Vegas Pro or not.”
That fix is actually not FOR QuickTime Pro it is USING QuickTime Pro to fix the metadata in the file for ALL applications. So if you modify the file with QuickTime Pro it will be fixed for Vegas Pro too.
The caveat is that the fix you mentioned will increases CPU power required to play the file and this could causes problems with large resolution files like 4K. Otherwise it works.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
Try adding Sony Levels with the Studio RGB to Computer RGB preset and that should undo the gamma shift.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Blake Gibson] “I have an older version of Quicktime installed (7.6) because I can’t get Prores to open with any other version of Quicktime, only 7.6 works – go figure. “
This is your problem. There is no reason to use an older version of QuickTime. As I said in your earlier post, I have QuickTime 7.7.9 for Windows working fine with ProRes 422 files in Vegas Pro 12 & 13. So the latest QuickTime should work. Why don’t you try it? (although the fact that you installed a QuickTime alternative might also still be messing things up if it didn’t uninstall cleanly)
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Roger Kroksleiven] “Could this be a problem with Vegas and how it treats Lagarith Lossless Codec, as it seems like it displays the wrong colour depth of such clips under properties?”
Yup. Could just be a bug where Vegas Pro thinks it’s RGBA when it’s not.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Jacqueline Nauman] “I believe I have room for another 8gb of ram.”
Yea, I have 16GB of RAM in my 2008 Mac Pro. The extra RAM does make a difference.
[Jacqueline Nauman] “Regarding the Radeon HD 5870, how does it hold up with 4K and long formats using fcpx? Some of the other cards I’ve looked at have complaints of timeline lags.”
I’m not editing 4K so I can’t give you first hand experience but the Radeon HD 5870 only has 1GB of VRAM and I believe 3GB is suggested to work with 4K so it might not perform as well as a newer card with more video memory.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
I like to work with two portable drives when working remote. One contains all of my Camera Card Archives and the other contains my Libraries.
After a shoot, I open FCP X, insert my camera cards one at a time and select them and press the Create Archive button. This archive is saved on one of my portable drives. Then when I’m ready to edit, I plug both my Camera Card Archive drive and my other portable Project Library drive and create a new Event and Project in a Library and import the data from whatever Camera Card Archive I am working with. I always have the FCP X Import setting Copy to Library enabled so that any files I import and contained within the Library. This ensures that I always have only two copies my footage: one on the Camera Archive Drive for safe keeping and one in my project Library drive.
Not everyone works like this. In some environments the footage is stored on an external shared SAN drive and editors will leave feels in place instead. This makes sharing easy but complicates things when trying to find media but I understand that sometimes the need to collaborate or the size of the files requires external storage. Luckily my projects are short and I edit alone.
In your case I would just make a new Event for the Best-Of compilation video and create your project in that event. This will keep the project separate from any other daily events in your Library.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
You are correct. 32bit and 24bit color depth are very different which is why Vegas Pro cannot smart render the clip. Why are you recording in 32-bit. That’s overkill unless you are trying to preserve transparency somehow you are just wasting bits and drive space.
If you want Vegas Pro to render 32-bit you need to open the Configuration window on Lagarith and change the video properties from RGB to RGBA. That will create a 32-bit render.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Ron Whitaker] “Does that mean the Vegas Pro Suite, or just the regular Vegas Pro 13?”
Hitfilm 3 Pro is part of Vegas Pro 13 Suite. It is not included in the regular edition.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
I get it. I was just trying to help you understand FCP X better to perhaps solve your 4K issue especially since you were considering buying it as part of your solution, but if you feel you already have a good understanding and don’t want to discuss it, then so be it. I was just curious as to what it was you didn’t like about FCP X (and still am).
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Shane Ross] “First off, Mr. Rofrano, there are many people who don’t like FCX, and can’t get how FCX works. It’s great that you and many many others have, but there are still many more of us that don’t get it, and don’t like it. So it’s good that we have alternatives.”
Shane, I was responding to this statement from John Whiteway:
“I could, of course, learn how to edit the whole 4K thing on FCP10, but everything I’ve seen about 10 makes me want to stay with 7.”
This implies to me that perhaps John had not tried FCP X and was going by hearsay, probably from the same people, as you pointed out, that “can’t get how FCX works.” I was offering to help his understand of FCP X because it would save him a lot of angst by learning how to use it instead of avoiding it because of what “others have said”.
I was not implying that all FCP 7 users should move to FCP X. I was responding to a very specific request for help from someone who did not say that they tried and didn’t like FCP X, or that they couldn’t get how FCP X works, but that they had “heard, blah, blah, blah” about FCP X and so they were avoiding it.
I just wanted to understand what the “blah, blah, blah” was about to see if I could clear up any misconceptions as an FCP X user who understands it.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com