Monday, May 28, 2012

Tips for the Opteka Steavyvid Pro - Part 2

Balancing the Steadyvid Pro
  1. Strip camera to components to be flown
  2. Find the camera's weight
  3. Find the camera's center of gravity (COG)
  4. Mount camera to stage aligning for COG
  5. Mount the plate to have camera COG over gimbal
  6. Expand the stabilizer arch
  7. Attach the weights
  8. Use trim controls to adjust balance
  9. Adjust drop time
Strip camera to components to be flown
Make sure to remove the camera strap and lens cap. You want the camera to be in a ready to shoot state before attempting to balance. If there is a fold out screen set it up. If the lens is not an internal zoom you'll want it locked into position.

Find the Camera's Weight
It might be a good idea to find out what your entire camera weighs. For camcorders it's not so hard. For DSLRs and Micro 4/3 it will vary on the lens attached. Some lenses will put the camera over the weight limit. Any accessories such as a sliding mounting plate will add to the overall weight. If you're worried by the accesories you've added use a kitchen scale (paid link). You only have three available weights standard with the Steadyvid Pro. Though the box says it should take 5 lbs (2.26 kg) that might be a stretch.

Example Weights
ItemWeight
Canon 7D Body only842g
Canon LP-E6 battery77g
Canon 7D + Battery919g
Giottos MH621244g
Canon 70-200mm 4.0 + Filter + Ring924g
Canon 100MM 2.8 Macro + Filter664g
Sigma 17-50mm 2.8 EX HSM + Filter618g
Tokina 11-16mm 2.8 + Filter593g
Sigma 30mm 1.4 + Filter424g
Sigma 30mm cap14g
Canon 7D + Tokina 11-16 + Filter1512g
Canon 7D + Sigma 30 + Filter1348g
GoPro HD Hero 2 + 3D Hero Kit + Mount455g
Using metric units for the precision

Find the Camera's Center of Gravity (COG)
My technique for finding the center of gravity is to mount the camera on a plate then roll it around a cylinder like a ballpoint pen. I do this for front to back and side to side. For the Canon 7D it's toward the EOS-mount and the right edge of the viewfinder port. This is your target for the gimbal.



Another way is to support the camera with one hand and feel for the point where it starts to balance with your finger. Other cameras a regular enough shape that you could pretty much guess it should be the geometric center. The mounting hole for the camera is close to the camera's center of gravity, so it's always a good starting point.

Mount camera to stage aligning for COG
If we assume the gimbal is presently set for center of the stage, you want the camera COG right above the gimbal. The gross control for this is the mounting hole for the camera plate. There isn't an Opteka cookbook out there as of this writing. This will have to be accumulated by the user community. For this example I will be balancing the Canon 7D + Sigma 30mm + 67mm Filter. In the case of the 7D, I used the rear most position on the cross. This is not the optimal position but close enough. There is an even closer position which is the left rear hole. The trouble with that position was grip on the camera. Unless tightened enough there was a tendency for the camera to turn with heavier lenses. What matters is the camera stays in the position you set and is close enough that trim doesn't go out of range.



Mount the plate to have camera COG over gimbal
Now you should be able to mount the plate onto the stage. There is some left-to-right adjustment possible when mounting on the stage. Use the rear screw as a guide and compare it to the current gimbal position. Once your have the left-to-right position fairly close to the COG the next step is to deal with the arch. For the Canon 7D + Sigma 30mm + Filter I set the plate to align the left edge with the stage's left edge. This put the Camera COG on top of the gimbal.

Expand the Stabilizer Arch
To start with you will want the arch expanded to full. To do this turn the knob counter clockwise when you're facing its front. This arch has some flex to it which doesn't appear to affect it much in operation. But in build quality it's not quite a precise as the Blackbird I've had before.



At maximum expansion the counterweight's effect is maximized. This affects drop time. Hold that thought, more on that later.

Attach the weights
You want just enough weight to balance the camera. Too little weight and the stage will tilt-up or dive down. Too much weight and the camera will be too bottom heavy making it erratic. You only have three weights. Only the Start and Middle weights are able to attach to the arch. The minimum counter weight is 81g using the Middle Weight. This might be a challenge for very light cameras. In those cases you may want to add weight to the camera using a sliding mount like the Giottos MH621 Quick Release Adapter with Short Sliding Plate camera mount (paid link).
Counter Weights
Start Weight 335g
Middle Weights 162g (2x 81g)
Finish Weight 78g

Total 577g
So how can we find how much weight to use? I start by mounting all the weights then recombining them experimentally. The arch should still be at maximum extension at this point. For the Canon 7D + Sigma 30mm + Filter I took away the Finish weight (Start+Middle = 497g). The camera remained upright with a slight tilt. When I took out even the middle weight the camera totally tilted up (Start = 335g). When I added back the Finish weight (Start+Finish = 413g) it wasn't enough to counter the camera's 1348g. So I settled with the Start+Middle weight as the correct combination for my rig.

The intention is to have the rig slightly bottom heavy. Taking away weights or adding them back changes the COG of the entire rig. Notice the distinction! Before we were talking about the Camera's COG with respect to the gimbal. Now that you have the camera mounted you are trying to manage the Steadyvid Pro and Camera's overall COG. You want this to be slightly below the gimbal which acts as the fulcrum. Why? It has to do with Physics. Some people smarter than I am could probably work the math out for me. If you would like to take a shot here are some references:

http://www.ehow.com/how_7525395_calculate-weight-balance.html
http://www.school-for-champions.com/science/gravity_center.htm
http://www.grc.nasa.gov/WWW/k-12/WindTunnel/Activities/balance_of_forces.html

What I took away from this was the see-saw example. The heavier child, the camera in this case, has to be counteracted by the lighter child by varying either weight or distance. Now there could be cases where the camera is too heavy for the rig. My Canon 7D + Sigma 17-50mm 2.8 + Filter + Giottos MH621 could be balanced static but was too sensitive in motion. The Opteka website doesn't sell the weights separately on their catalog. You might have to get creative with washers to get more granularity.

Use Trim Controls to Adjust Balance
Now there is the infuriating part. I would find a sturdy table with empty space underneath. Merlin and WSCALTERs alike can sit on the handle when the camera is fairly close to balanced. With this you can use both hands to practice balancing. Once you get used to it, you should be able to balance it one handed while holding the camera with your dominant hand.





Keep and eye on the bubble level. If your camera has an electronic level that would be even better. For this exercise we stick to the standard equipment, hence the bubble level. If the bubble is to the right, you need to roll left a bit. Use the knob on the stage's side and twist clockwise to move the bubble left. The bubble might also be slightly back, use the knob on the rear and twist clockwise to move the bubble forward. Alternate between knobs until you get the bubble center. Move the arch out of center then let it fall to confirm it will sit center. Once you have a good balance tighten the silver locking bolts on the sides and bottom of the stage. You are almost there. This is what they call static balance.

One thing I don't like about the trim knobs is they tend to stick. I have to periodically check the gimbal to see if it's moving. The Blackbird was much smoother and precise. I'm comparing a Kia to an Audi here. Just letting you know.

When first learning to make adjustments, you should use whole rotations until the stabilizer leans in the opposite axis. Then dial it back. Over time the number of twists start to become intuitive. If you look inside the stage you will find it is manipulated by long screws. The reason for the stickiness is friction between the locking nut and the stage. This may wear down over time making it easier to move even with the silver locking bolts tightened. For alignment of the gimbal by sight, on the bottom the space between the silver bolts is center. On the side, the silver bolts are fixed to the sliding stage. When the rear silver bolt is close to the rear end of the groove you are at maximum aft.


Now pick up the handle and lift the rig from the table. It may get a bit squirrely then tilt in some odd direction. Adjust any major tilting with the same technique as you had. Now we need to work on dynamic balance and drop time all at once.

Adjust Drop time
If you move your hand left to right, then front to back you may notice it acting like a boat in rough seas. The rig is too sensitive because it is too bottom heavy. If the weights came in finer increments we could have added or removed more weights. Since we don't have this option we'll have to raise the weights/contract the arch.

Try pulling the weights to the left so the camera and weights become horizontal. This would be a good time to remember if all your silver locking and plate bolts are tight. You don't want the camera to fall off the stage! Then let go of the weights and count how long it takes for the it to cross vertical. With my rig setup it was less than 1 second. I reckon about .5 seconds it was already dropped. Yes, this is drop time.

The rule of thumb is you want anywhere from 1 to 2 seconds of drop time. On the Blackbird I liked 1.5 seconds, but when I started I did 2 seconds. For Merlin's they recommend close to 1 second. On the Steadyvid Pro, I'm still at 2 seconds. You'll have to get a feel for it depending on your camera. The end state you want is for the entire camera and arch to move together as a unit. When you stop you don't want it to overly tilt or rotate. If it does rotate as it falls then adjust the camera a bit backward then try again.

For the Canon 7D + Sigma 30mm + Filter it took about 15 clock-wise twists to get to the point where I was happy. Do a few twists at a time, move the camera around a bit, and observe how steady the head remains. Test the drop time. Then trim the balance. As you contract the arch the rig's COG changes so you have to continually adjust balance.



Whew, if you've gotten this far you should be able to walk around a bit with the footage being fairly stable. There may be some effects of inertia where it acts like a boat. Or maybe an unruly helicopter. That could mean more tuning. What it probably means is the need to practice flying the stabilizer. Here's a hint: use both hands!

On to Flying the Steadyvid Pro

Tuesday, May 22, 2012

Tips for the Opteka Steadyvid Pro - Part 1

I have, or rather had, a CMR Blackbird. No, I didn't sell it. It's on the other side of the planet with the 2nd Unit. I had the complete kit with bag, extra weights and stand. The problem was carrying it on international flights took half my luggage space. Since it had more use where I had taken it, the Blackbird stayed. In the meantime I've been using a Gorillapod SLR as a sort of compact shoulder rig. It's been all over the country as far as Hawaii. But nothing beats a handheld stabilizer for dynamic shots. The Steadicam Merlin 2 was recently announced and I was interested. Only it was quite expensive at $800. Then while browsing through Amazon I happened upon the Opteka SteadyVid Pro. Hey! $179.95. Quite tempting.

Pro:
Cheap
Compact

Con:
Poor documentation
No markers for consistent setting
Limited weight capacity
Questionable durability

There are more cons than pros. Did I mention it was cheap? I wouldn't trade my Blackbird in for the Steadyvid Pro. The Blackbird had documentation (manual, video and email support!), graduated markers and 8 lbs of capacity. It was worth the $670 for the complete kit ($470 for just the stabilizer). But what if you can't afford to spend that much for a stabilizer? You could go DIY. That's if you have the tools, skills and patience. Okay, I digress. Who would want a Steadyvid Pro anyway? If you want to dabble, the Steadyvid Pro might be a good introduction. If you want a 2nd stabilizer for infrequent use this might be for you. If you have no patience, you might want to stay away. You need to expend money, time and effort whichever stabilizer you choose. The expensive ones come with support. With the Opteka you get what you paid for. Which is probably why you're reading this. At this price point, you'll be dependent on other users to help you out. Hurray, user community!


Batteries not included, some assembly required, your mileage may vary!

Quick Control Guide and Concepts
Before going into detail on how to balance, here is a quick guide to the controls and a hint on the concepts.
The bendy-foldy part above the handle is called the gimbal. Above the gimbal is the camera stage. Between the stage and camera there is a plate onto which the camera is screwed on. There are knobs on the side and rear to adjust the gimbal position. In the above picture I've color coded the controls and the direction the stage or gimbal takes. Don't get confused by the opposite markings. The stage movement is opposite to the gimbal position. If the gimbal is moved left of center, the stage (as indicated by the bubble level) will lean right.

One double-sided sheet is all the instructions that come with the kit. Help!


The stabilizer is a really complicated looking version of a see-saw. If you remember your playground days, a heavy kid near the fulcrum of a see-saw can be lifted by a lighter child sitting further from the fulcrum. If they can find the sweet spot, both children can hang suspended off the ground. That's the state of equilibrium. With a stabilizer, the gimbal is the fulcrum. One short end of the see-saw is from the gimbal to the camera plate. The other longer end is from the gimbal to the weights on the arched shaft.

On to Balancing

Monday, May 21, 2012

Lenovo W520 and Photoshop CS6 Scratch Disk

Just upgraded to CS6 targeting the mSATA. On start there was an immediate error "Could not open a scratch file because the file is locked." Apparently, there is a bug in CS6 where it insists on using the C: drive, where I no longer have a Users directory. Looking across the net I found some clues.

After a bit of experimenting, one did work. I held down just CTRL-ALT then went to the Start menu to start Photoshop CS6. A menu appears to specify the Scratch Disk and I point it to D:. The picture above was edited using Photoshop, so it worked!

Wednesday, April 4, 2012

Lenovo W520 and Photoshop GPU Enhancements Disabled

After an NVidia update Photoshop CS5 kept complaining "Photoshop has discovered a problem with the display driver and has disabled GPU enhancement." A thread I found suggested to rollback the driver but that was not the correct solution. This other site gave me a clue. Optimus was assigned Intel HD graphics rather than the NVIDIA Quadro 2000M (or 1000M if that's what you have) to Photoshop. Auto is not a bad Global setting but not good for your CUDA enabled Adobe applications. You can customize the settings per program to the NVIDIA Control Panel either via Windows Control Panel or the taskbar applet for Optimus.


Start -> Control Panel -> NVIDIA Control Panel -> 3D Settings -> Program Settings (tab) -> Select A Program To Customize: Add -> Find the exact photoshop.exe path in your Program Files -> Select the preferred graphics processor for this program: High-performance NVIDIA processor -> Apply


Stop and Restart Photoshop. The error should have gone away. You can confirm you are using the NVIDIA graphics card by going to System Info.



Help -> System Info -> Scroll down until you find Video Card: NVIDIA Quadro 2000M (or Intel HD Graphics ... which is the cause of your problem)



Video Card Vendor: Intel
Video Card Renderer: Intel(R) HD Graphics Family
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 1080, right: 1920
Video Card Number: 1
Video Card: NVIDIA Quadro 2000M
Driver Version: 8.17.12.7593
Driver Date: 20110812000000.000000-000
Video Card Driver: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Video Mode:
Video Card Caption: NVIDIA Quadro 2000M
Video Card Memory: -2047 MB
Video Card Number: 1
Video Card: NVIDIA Quadro 2000M


Update: The above appeared to be a symptom of something wrong with the NVIDIA driver update as well. After fixing Photoshop I discovered that After Effects and Premier would fail to start with Sniffer_GPU.exe running a long time before Windows complains. I went through cycles of rollback and patch uninstall of Windows patches. And then putting them back when it didn't work. The final fix was to uninstall the NVIDIA Graphics Driver and rebooting. The reboot automatically reinstalled the graphics software. Another reboot later and the my favorite Adobe apps were all working again.

Sunday, January 1, 2012

Notes on Gopro Hero HD with a Parrot AR Drone

The difficulty with mounting an Hero HD on the AR Drone has to do with keeping the center of gravity. I tried mounting on the the nose, but it was so front heavy it tended to crash after a 'Too Much Angle Emergency'. I read some modification threads with counter weights but was warned of pendulum problems. Mounting it on top of the battery's velcro kept the center of gravity but made the rotors visible. The trick was to raise the camera high enough. After some experimentation I've found that the Hero HD bottom needs has to be about 14.5cm from the Drone body in 720p mode. At 14cm you could still see the tips of the rotors a bit.

I've managed to crash the Drone a few times and it survived along with the Hero HD. That was until the first live shoot, my brilliant mounting system lost its velcro and leaned right. This caused the Drone to drift right in a hover. It hit a wall and caused an auto cutoff. The Camera and Drone fell eight feet. The Camera lost the part of the long sequence after the battery flew out. I would have lost more if I hadn't copied the raw unindexed footage first before attempting the SOS recovery. Needless to say it still works. As for the Drone, it broke one of the gears which needs replacement, it won't fly for a while.

Above mount tended to pendulum.

This mount achieved level flight. The tricky part was keeping it balanced and attached to the body. Also no protection to the rotors.

Lessons Learned:
Outdoor mode and Outdoor Hull makes the drone finicky even without the wind. Don't use it.
Watch the balance of the mount.
Prepare some spare parts so your shoot doesn't get interrupted.

Spare parts you may need after a crash.

1. Spare Gear
2. Spare Rotor
3. Spare Cross Piece






Equipment used


Wednesday, May 25, 2011

Lenovo W520 for Sony Vegas Pro 10 and Adobe After Effects CS5 - Part 6

Laptop vs Desktop
After getting my plug-ins, codecs, fonts and little nick-nacks synchronized I was ready to do some test renders. To compare my desktop and new laptop I used a recent project that I edited using Sony Vegas Pro 10 and Adobe After Effect CS5. The results surprised me.


DesktopLaptop
ManufacturerHewlett-PackardLenovo
ModelHPE-380tW520
CPUCore i7 930
Cores: 4
Clock: 2.8 Ghz
Max Turbo: 3.06 Ghz
Cache: 8 MB
Core i7-2720QM
Cores: 4
Clock: 2.2 Ghz
Max Turbo: 3.3 Ghz
Cache: 6 MB
RAM24GB DDR3-1066 CL 7-7-7-20 Triple Channel16GB DDR3-1333 CL 9-9-9-24 Dual Channel
Graphics AdapterNvidia GeForce GTX 260
CUDA Cores: 192
Graphics Clock: 576 Mhz
Shader Speed: 1242 Mhz
Memory: 1792 MB GDDR3
Memory Interface: 448-bit
Nvidia Quadro 2000M
CUDA Cores: 192
Graphics Clock: 550Mhz
Shader Speed: 1100 Mhz
Memory: 2048 MB DDR3
Memory Interface: 128-bit
ChipsetIntel X58 + ICH10RIntel QM67
Primary DriveWD 3.5" 7200rpm
WDC WD1001FAES-60Z2A0 1000.2 GB
Intel 310 SSD
SSDMAEMC080G2 80.0 GB
Secondary DriveSeagate Barracuda 3.5" 7200rpm
ST31000340AS 1002.2 GB
Seagate Momentus 2.5" 7200rpm
ST9500420AS 500.1GB

The Desktop which was purchased around August 2010 as a custom configured system is the baseline for this comparison. Its WEI is 5.9 overall with 7.5 processor, 7.5 RAM, 7.1 Graphics, 7.1 Gaming Graphics and 5.9 Primary Hard Disk. The Laptop was purchased in May 2011. It's WEI when Optimus is 4.8 overall with 7.5 Processor, 7.5 RAM, 4.8 Graphics, 4.8 Gaming Graphics and 7.7 Primary Hard Disk. The WEI increases to an overall 6.9 when Discrete Graphics is switched in the BIOS. The test was done in Optimus mode because I hadn't read the threads in NBR about stability yet.

The HPE-380t was upgraded recently with an NEC USB 3.0 PCI x1 card. It shows up as a Renesas USB Host Controller which is also what appears on the W520's system information.

DriveInterface
Operating SystemPrimary DriveSATA 3.0
Target DiskSecondary DriveSATA 3.0
Project FilesSeagate Barracuda LP 3.5" 5900RPM
ST32000542AS 2000.3 GB
e-SATA on Thermaltake BlacX Duet (single-drive on HDD1)
Additional MediaSeagate FreeAgent GoFlex Ultra Portable 5400rpm
ST1500LM003-9YH148 1500.3 GB
GoFlex on USB 3.0

The Operating System contains Windows 7 Professional and applications. In the case of the W520 some executables were also stored in the Target Disk but those were not invoked for this test. The Target Disk is where I render the final output.
Project Media drive has most of the video clips, images and voice overs used for render. Additional Media contains Action Essentials 720p, Sony Motion Picture SFX and Stock20 music which I use across projects.

The same external drives were attached to e-SATA and USB 3.0 respectively. These external drives are the slower "Green" or portable versions which may limit the I/O speed somewhat. But this isn't an artificial test, I actually do store my media and work this way. It's not as optimized as a full-on RAID configuration but it is what it is. Also note that the BlacX only had one drive installed. I learned that the QM67 did not support port-multiplier so only one disk can be seen in the Disk 1 slot.

Sony Vegas Pro 10d Comparison 64-bit
I took a finished project, GoMilsim Evolution 9, and re-rendered it. The video was 08:21 long with some pre-rendered elements using a mix of 1080p and 720 clips in various formats. NeoScene was installed on the Desktop while NeoPlayer was on the Laptop. The Cineform license required disabling and reactivating when moving between computers but I didn't feel like doing it. Sorry.

Tracks
2 Overlay Tracks with Text and Video
1 Main Video Track with JPEG, WMV, AVI-Cineform 720p 24fps, and MOV-Canon 7D 1080 24fps clips of mixed resolution/frame rate
3 Audio tracks

Operations
Resize from 1080p to 720p
Bit Rate Conversion
Pan/Zoom
Color Corrector
Transitions
Audio Envelopes

Render output used codec Sony AVC/MVC with 1280x720 resolution at rate 4,000,000 Mbps. This codec had options for CPU only and CUDA when available.

DesktopLaptop
Sony AVC-CPU only22 Minutes 55 Seconds 21 Minutes 31 Seconds
Sony AVC-GPU if available25 Minutes 11 Seconds23 Minutes 55 Seconds

Oh my! The results were not expected. Not only did GPU acceleration take longer to render, this year's Laptop outperformed the Desktop. Just because GPU is used doesn't really mean it will be faster. What it does allow is for the CPU to do other work while render is in progress. Effects and transitions may not benefit from GPU acceleration depending on how they are programmed. Observing the CPU utilization, it seems to me that resize from 1080p to 720p and text overlay is all done in CPU. Transcode from Cineform to Sony AVC was level at about 33% with GPU. Windows was showing 4GB RAM used during render in both cases. That's quite a revelation to me as this Vegas is a 64-bit application. The original project was created using Sony Vegas Pro 10c 32-bit. I wonder if that has anything to do with it?


After Effects CS5 Comparison
The VFX in the closing scene of Evolution 9 was originally done with Adobe CS4 32-bit. It was re-rendered using Adobe CS5 64-bit.
The project was 00:00:14,53 long. Rendered output was to 1280x720 Lossless 60fps

Layers
Composition with 23 Layers with 8 MOV files (7 from Action Essentials, 1 Canon 7D 720p 60fps, 1 JPEG
4 Motion Tracks for Compositing

DesktopLaptop
AVI-Lossless5 Minutes 33 Seconds4 Minutes 33 Seconds

It takes quite a while to render 14 seconds of VFX. The original render on a Q6600 with 3GB of RAM took 14 Minutes 6 seconds. The 64-bit renders consumed about 13GB! Both the 380t and W520 do much better than that but I didn't expect the Laptop to do better by a full minute. I know it's a mobile workstation but I was expecting it to be slightly slower than the Desktop. If you view it negatively, you could say my Desktop sucked. Hey! That Desktop served me well. Viewed positively, I'd say the Lenovo W520 is winning!

Monday, May 23, 2011

Lenovo W520 and a Replacement Blu-Ray Drive

Getting a Blu-ray Writer



A Blu-ray drive is not a current option for the Lenovo W520. This deficiency can be alleviated by purchasing a slim drive after market. The Panasonic UJ-240 OEM SATA model is the cheapest one available at the moment. This is the bare drive capable of up to 6x BD-RE write and 8x DVD+/-RW DL. It's available from Amazon (paid link) and Ebay. To swap this with your DVD all you need is a screw driver and paper clip. Two rail guides and a bezel need to be transferred from the original. After that its plug and play.





The original Lenovo drive is a Matshita UJ8A0A which is manufactured by Panasonic so we can be confident of this replacement. Windows 7 automatically detects the new drive and finds the right drivers for it. Once you have replaced the bezels and installed it the only other reminder it's a blu-ray is the dark blue tray.