[John Rofrano]

I get why you’re buying 12 but GoPro footage was troublesome with either 11 or 12 (I forget which) and fixed in 13. That’s all I was pointing out.

Your graphics card should not affect the quality of a render (only the speed) but sometimes it does. Not because of the quality of the card, but because of bugs in the render engine. It will have no affect on stabilization.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[will stanton] “There is absolutely no evidence that the GPU is doing any work other than updating the preview window.”

What GPU acceleration are you talking about. Timeline Playback? Rendering? or both? I was referring to Timeline Playback which has absolutely nothing to do with any particular render engine.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[William Mims] “When I looked at the blade I don’t recall Atomos advertising: “This will not work with Sony Vegas/Windows platforms.””

Let’s be very clear: It works with Vegas Pro you just can’t use a lot of QuickTime files due to the 32-bit memory limitation. I would not use it for a project with a lot of files but if you were shooting an event that was one or two long recordings you should be fine.

Atomos would be incorrect if they said that it didn’t work with Vegas Pro.

[William Mims] “Only works with a Mac.””

This has nothing to do with PC vs Mac. Adobe has their own QuickTime libraries on the PC so they don’t have the problem that Sony has. This is a Vegas Pro limitation because Sony uses the 32-bit QuickTime libraries. I’m sure it would have cost them some licensing fees to develop their own and since none of their cameras shoot Quicktime, why would they?

So saying it only works with a Mac would also be false advertising on Atomos’ part. They advertised correctly. You just need to know the limitations of your own software which Sony does not advertise. That’s why there are user supported forms like the Creative COW. 😉

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Shawn Miller] “Even 3D camera and object tracking is used in motion graphics projects now, projects that would have been considered VFX work 15 years ago.”

You could use a narrow definition based on the term “graphics”. If you are superimposing a graphic on the screen, and it’s “moving”… it’s a Motion Graphic. If you are just tracking a background on a green screen shot, or adding smoke, that is a visual effect. To me, motion graphics requires a graphics designer or at least “a graphic”. Everything else is a VFX.

I would say that tracking a 3D object that is “unnatural” such as 3D text over a moving landscape is considered motion graphics while tracking a 3D object that is supposed to look like it’s naturally part of the scene (e.g., a car that wasn’t originally there) is a VFX. The same skills and tools can be used to complete each task, but from the perspective of the audience, one is a moving graphic while the other is a visual effect meant to trick them into thinking that it is “real”.

To me it all depends on whether you are adding text and logos, or smoke and fire. If someone asked me to add a motion graphic my first questions would be to send me the graphic and describe the motion. 😉

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[George Dean] “First step in my workflow is to render the originals in CineForm (Filmscan 2 [yes, I know this is overkill]) in an .avi container. From there I keep it in CineForm until the delivery format selected.”

This is exactly what buying the Atomos Samurai Blade avoids if you own a Mac. It shoots edit ready files for Mac editors. No transcoding required.

For many years the Mac workflow was to take whatever format the camera shoots natively, and transcode it to ProRes 422 as the first step. Now camera manufacturers are making cameras and recorders that shoot ProRes 422 directly so there is no need for the transcoding step on the Mac anymore.

If you are a PC editor, however, you should do exactly what George is doing… convert the QuickTime files to a PC friendly format. CineForm AVI is a great choice for Vegas Pro editors.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[James Magda] “I just ordered an Atomos Samurai Blade to edit its output on Sony Vegas Pro 13 based on this link of yours:

https://johnrofrano.com/training/video-tutorials/avid-dnxhd-template-for-veg...

But now in this forum you’re saying NOT to. Which is right?”

If you read the explanation in my link, I was recommending that Avid DNxHD is a good format for editors who are on a PC and need to collaborate with editors on a Mac. I never said it was a good format for editors on a PC to just use for themselves or to buy a camera that shoots QuickTime.

Here are my *exact* words from the opening paragraph of that tutorial:

“Quite often I’m asked what’s the best format to work with in Vegas Pro when you need to collaborate with Final Cut Pro editors on a Mac. The best codec I have found is the free Avid DNxHD QuickTime codec. The reason I use this codec in addition to it’s superior quality for mastering, is because it doesn’t suffer from the gamma shifts that some other PC codecs have when transferred to the Mac. With Avid DNxHD, you get the gamma levels you expect, and the quality you need.“

The rest of the tutorial shows you how to create a Render Template, so the recommendation is to render to Avid DHxHD to send to a Mac.

Here are the facts:

• Vegas Pro chokes on too many QuickTime files.
• Does Vegas Pro work with editing QuickTime? Yes (to a point).
• Can you render to QuickTime Avid DNxHD? Yes (if you make a template like in my tutorial).
• Should you use QuickTime as your main editing format with Vegas Pro: No! Absolutely NOT!!!

QuickTime is the native format on a Mac. If you want to buy a camera that shoots QuickTime, my advice is to also buy a Mac. Camera manufacturers build cameras that shoot Apple ProRes 422 to make a Mac workflow easier. If you buy one of these cameras and don’t have a Mac, you are defeating the purpose of owning a camera that shoots QuickTime ProRes which is all ready to drop onto your Final Cut Pro timeline without any transcoding.

If you need to edit QuickTime on a PC and you don’t have too many files, Vegas Pro is fine. For example, I usually shoot stage performances. Last weekend, I shot a coffee house style performance where the musician played 2 sets. I had exactly two 45 minute files to edit (I just kept the camera rolling during each set). Had these been QuickTime files I would have been fine with these 2 files (they were not). Had I had a lot of QuickTime files from starting and stopping the camera, Vegas Pro would have had problems.

So I never recommended that PC editors work with QuickTime. My recommendation was, that if you had to collaborate with Mac editors, then you need to send them QuickTime files, and Avid DNxHD is the QuickTime format that is closest to the Apple ProRes 422 that Mac editors use but PC editors can’t create.

Hope that clears things up.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

I thought it sounded like a flicker so I Googled “Canon C100 flicker”. I found some posts in another forum but I don’t believe that the COW allows links to other forums (at least it use to be not acceptable). If it’s not a flicker then perhaps it’s not the same problem but the post I saw was from people working directly with Canon support and support couldn’t fix it.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

I tried to find examples of the game but all of the screen shots from the game on their web site had no hud showing.

If you really want to get crazy, there is a VirtualDub plug-in called LogoAway that will remove logos from broadcast recorded video. It might work in this case. It blends surrounding pixels to try and erase a logo but it does not plug into Movie Studio or Vegas Pro. You have to process your video with VirtualDub first and that only works with AVI files.

It might not be worth the trouble and a simple Pixelate + Gaussian Bur might be just as good.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

You did everything correctly. What you are seeing is the fact that from the middle of the screen you are looking at the panel off to the right from an angle. So the distortion that you perceive is just the angle of motion as the panel rotates into view. This is a perspective that Vegas gives objects that are to centered.

Notice that when you look at the 3D view from the top and position the panel exactly 90 degrees perpendicular with the screen in the top view, which should make it invisible, it is already visible in the perspective view. If you move the track position to the middle, it disappears from view at a 90 degree angle as you would expect.

The only way to correct for this is to use a Nested project. Create a separate project to rotate from the middle of the screen and then drop that project into your main project and position it to the right, it would do what you want.

In this separate project, the Track Motion would Position the frame at X: -960 to move the pivot edge of the frame to the center of the screen. Then change the Rotation on the Y: from -90 to 0. This will make the panel rotate exactly in the center of the screen like a door. Finally, drop this project into your other project and move it to the right where you want it.

It will look the way you want because the perspective will be from the front and not from an angle off to the side.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

If you just want to crop off the top or bottom of the display you can use the Pan/Crop tool which is on every event on the timeline.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com