Clone Your Windows Boot Drive
Friday October 14th 2016, 6:11 am
Filed under: Windows

I. Prepare the New Disk
1. Connect your new disk as a secondary disk.
2. In DiskManager, create a 200MB hidden NTFS partition (no drive letter) on your new disk.
3. Right-click the hidden partition and mark it Active.
4. Then create a regular NTFS partition (with drive letter) filling the rest of the space.

II. Clone Old Disk to New
5. Install DriveImage XML and choose Drive to Drive or Restore and clone your disk. Ignore warnings.

III. Make the New Disk Bootable
6. Follow these instructions to create a Windows recovery usb and use it to make the new drive bootable.

IV. Cleanup
11. Scan your new boot disk for errors.
12. If the cloned disk complains about not having a genuine version of Windows, open a prompt as Administrator and type:

Further Reading:

Comments Off on Clone Your Windows Boot Drive

Types of Anti-Aliasing
Tuesday September 22nd 2015, 12:06 pm
Filed under: Concepts

1. FXAA (Fast Approximate): Post-processes the final rasterized image to smooth edges. Very fast but poor quality, adding blurriness. Aka MLAA (Morphological).

2. SMAA (Subpixel Morphological): Like FXAA, but compares across multiple frames. Substantially reduces blurriness at a modest performance cost.

3. SSAA (Super-Sample): Renders the scene at a larger resolution and downsamples. High-quality with no artifacts, but extremely slow. Aka FSAA (Full Screen).

4. MSAA (Multi-Sample): Detects the edges of geometry, renders only those areas at a higher resolution, then downsamples. Good balance between speed and quality but sometimes has inconsistencies between frames; hardware support can be limited. Aka EQAA (Enhanced Quality), CSAA (Coverage Sample).

5. TXAA (Temporal): Like MSAA, but compares the edges of geometry across multiple frames, delivering greatly improved quality with comparable performance. However, currently has extremely limited hardware support.

Comments Off on Types of Anti-Aliasing

Motion Capture: Kinect 1 vs. 2
Sunday February 08th 2015, 11:40 am
Filed under: Kinect

The Kinect 2 is supposed to have superior skeleton tracking, so I tested it against the Kinect 1 in a single-camera setup of iPi Studio.

Conclusion: a single camera is always going to have trouble when the actor doesn’t face front, so both tests show obvious glitches. However the Kinect 2 does seem to capture more subtle movements.

Kinect 1 is purple, Kinect 2 is green:

Download FBX files.

Comments Off on Motion Capture: Kinect 1 vs. 2

Scanning Clay Models
Monday September 08th 2014, 8:08 pm
Filed under: Kinect

Step 1. Build a model with armature wire and air-drying clay.

Step 2. Scan… (to be continued)

Comments Off on Scanning Clay Models

Safe Mode in Windows 8
Friday January 10th 2014, 11:45 pm
Filed under: Windows

In earlier Windowses, if you pressed F8 at boot time, you’d go to a special “Safe Mode,” which was very useful for repairing a damaged install that otherwise wouldn’t boot. Safe Mode still exists in Windows 8, but it’s disabled by default. To enable it:

Step 1. Run a Command Prompt as Administrator.

Step 2.Type:

bcdedit /set {default} bootmenupolicy legacy

That’s it! Pressing F8 at boot should now bring up the traditional Safe Mode menu.

Comments Off on Safe Mode in Windows 8

Windows 8.1 Desktop Fix
Friday January 10th 2014, 8:13 pm
Filed under: Windows

The new tile interface in Windows 8 has its fans, but if you don’t like it then it’s possible to completely get rid of it as of Windows 8.1.

Part I: Upgrading Windows 8.0 to 8.1

Step 1. Go to the Windows Store in the tile menu; a Windows 8.1 upgrade tile should appear.

Step 2. If the tile doesn’t appear, install this update.

Step 3. Return to the Store in the tile menu and install the Win 8.1 upgrade.

Part II: Once you’re running Windows 8.1

Step 1. Right-click on the taskbar and choose Properties > Navigation.

Step 2. To enable booting to desktop, uncheck everything in the top pane and check everything in the bottom pane:

Step 3. Next, to restore the traditional Start Menu, install the Classic Shell utility.

Step 4. Right-click the Start Button and choose Settings. In the Start Menu Settings tab, click Aero and Windows 7 style to get the familiar Win7 layout. Or customize to taste.

Step 5. If the Start Button shows the Classic Shell logo, uncheck Replace Start Button to return to the regular Windows logo.

Comments Off on Windows 8.1 Desktop Fix

RGBD Sequences in Maya
Tuesday October 08th 2013, 9:22 am
Filed under: Kinect

This will be expanded soon. In the meantime—can you edit the camera position of an RGBD Toolkit sequence in Maya?

1. You have a virtual camera in Maya that you can place however you want, so the simple answer is: yes.

2. However! If you shot the RGBD scene with a real-life moving camera, then your material has real-life camera movement permanently baked into it. If you want to work in Maya and freely reposition a virtual camera, best to shoot the real-life scene on a tripod.

3. Unless! You want to be really clever and use match-move software (Maya and After Effects both come with trackers) to track the calibrated RGB video from the DSLR camera. (Kinect depth images are useless for that kind of tracking; way too weird-looking for match-move software to understand.) You could then create a virtual camera in Maya that matches the real-life camera you shot the scene with. Then anything you animate in Maya moves in sync with your original recording. (You’re still stuck with the original real-life camera move, however–remember that’s always permanently baked into the RGBD data.)

Comments Off on RGBD Sequences in Maya

Depth Camera Roundup
Tuesday October 01st 2013, 2:14 pm
Filed under: Kinect

Cameras that can use…

1. …either OpenNI (PrimeSense) or Microsoft drivers:

  • Microsoft Kinect 1 for Xbox (original version) … $80
  • Notes: You can’t beat the original on price and flexibility–although it has the noisiest depth data, and it always needs to be plugged into AC power. I’ve heard that it’s possible to open it up and cut the power to the little motorized platform, after which it’ll run off USB alone.

    2. …only the newest OpenNI drivers, or Microsoft drivers:

  • Microsoft Kinect 1 for Windows (revised version) … $250
  • Notes: Despite the higher price, the Kinect 1 for Windows is practically the same hardware as the Kinect 1 for Xbox. It comes with a license to sell commercial software written with the MS drivers, which isn’t really relevant to most filmmakers. Although the very latest release of the OpenNI drivers can work with the Kinect for Windows, many apps haven’t been updated to support this yet.

    3. …only OpenNI drivers:

  • Asus Xtion (all versions) … $150
  • Primesense Carmine (all versions) … $200
  • Notes: The Xtion gets cleaner depth info than the original Kinect 1 for Xbox, but I can’t recommend it for everyone because it has problems with Windows and USB3. The Carmine is supposed to be excellent, although I haven’t tried one myself yet–I will soon. Neither the Xtion nor the Carmine needs AC power; they can run off USB alone.

    4. …only Microsoft drivers:

  • Microsoft Kinect 2 (probably) … $400?
  • Notes: We don’t know much about the Kinect 2 yet, but it uses a completely different sensor than the one in the Kinect 1, Xtion, and Carmine. It’s supposed to be lower-resolution, but a lot cleaner.

    Comments Off on Depth Camera Roundup

    Image Sequence to Movie
    Wednesday June 26th 2013, 9:46 am
    Filed under: Video

    Using the free utility MPEG Streamclip, you can turn a sequence of image files into a Quicktime movie without any other software:

    Step 1. Go to Files / Open Files.

    Step 2. From the drop-down menu, choose All Files.

    Step 3. Select an image sequence and click Open. (Many image formats are supported; I recommend PNG.)

    Step 4. You may get a confusing message saying “File open error: unsupported file type.” Just click Open Anyway.

    Step 5. At this point you should be able to see your image sequence in the viewer window.

    Step 6. Now choose File / Save As.

    Step 7. Leave the drop-down menu set to MOV, a Quicktime movie file, and click Save. (If you’d like a different video format, I recommend saving out the .mov file and converting it later as a separate step.)

    Comments Off on Image Sequence to Movie

    Encoding WebM on a Mac
    Wednesday April 10th 2013, 9:12 am
    Filed under: Video

    Terry Hancock’s Lib-Ray initiative is a great alternative to Blu-ray, using high-quality HTML5 video and plain HTML/CSS and JavaScript that can play back online or from an SD card. To support all the major browsers (Firefox, Chrome, and Safari), you need to include WebM versions of your video as well as H.264—but at present the site only offers tutorials for command-line encoding tools, which are challenging for less experienced users. So I’ve created this guide to encoding WebM video using GUI utilities on OS X.

    Step 1: Download your tools. You’ll need:

    • WebM QuickTime component (free): adds WebM support to your Mac system.
    • Xiph Vorbis Quicktime component (free): adds Vorbis audio support.
    • Quicktime 7 Pro (USD $30): creates the video track. This might seem like a strange choice—but in my tests it seems to be the only GUI-based Mac tool right now that can reliably encode high-quality HD WebM video for under $100. For now, other common utilities that claim WebM support are either glitchy or have fixed low-quality settings.

    Optional extras:

    • Audacity (free): A great all-purpose audio editor that can export Vorbis audio files if you’re using separate audio tracks.
    • MKVToolnix (free): Losslessly add and delete audio and video tracks from a WebM file.

    Step 1: Install the audio and video codecs. Drop them into the /Library/Quicktime/ folder, and they should immediately become available.

    Step 2: Prepare your materials. Like H.264, WebM is a highly compressed codec, so you’ll need to start with a high-quality original to get good results. I recommend using a Quicktime movie with the PNG, ProRes, DNxHD, or PhotoJPEG codecs. Be aware that WebM doesn’t appear to support nonsquare pixels; for example, you’ll need to convert 720×480 DV video to true 4:3 or 16:9.

    Step 3: Open your video in Quicktime Pro and choose Export, then Options.

    Step 5: Video settings.
    Frame rate: You’ll have to manually match your original frame rate.
    Keyframe every: Your frame rate rounded to the nearest whole number. (If your original video is 23.976 fps, put 24).
    Data rate: Your choice—be aware this is measured in kilobytes, not bits. I use 3500KB/s for an HD original (approximately Blu-ray bitrate) and 1000KB/s (approximately DVD bitrate) for SD.
    Quality: I don’t think this affects anything, but I always set it to Best for good luck.
    One Pass/Two Pass: Two-pass encoding takes more time but gives better results. However, WebM already encodes very slowly, so if it’s not an overnight render you might want to leave this off.

    Step 6: Audio settings.
    Channels: Usually you want Stereo.
    Rate: 48Khz is standard.
    Quality: Confusingly, this is sample rate conversion quality, not compression quality. Always choose Best.
    Encoding quality: 10 is best, on a scale of 1 to 10. (Decrease if file size is important.)

    Step 7: HTML5 video lets you specify multiple sources for your video. Here’s some sample code.

       <source src=”test.mp4″ type=”video/mp4″/>
       <source src=”test.webm” type=”video/webm”/>

    You might be asking at this point—why is this odd-duck video format worth all the hassle? Well, it’s about more than just supporting Firefox—WebM was created more from legal necessity than anything else. The very popular H.264 video codec and its main physical-media distribution format, Blu-ray, are caught in a series of conflicts of interest between various giant media and technology companies. (The issues are too complex to summarize easily, but you can read more about them here.)

    These fights affect you in numerous subtle ways—licensing squabbles are why, for example, it’s so difficult to play back Blu-ray discs on a computer. H.264’s license terms allow you to give your work away for free, but they don’t let you sell it without paying royalties to the MPEG-LA, the consortium that owns the codec. To be clear, this rule isn’t currently being enforced—it’s very unlikely that anybody plans to stop you selling home-burned Blu-ray copies of your own work—but it leaves the MPEG-LA with far too much control over the livelihood of video producers. And the they could change their license terms at any time. So Google created the WebM video format to have an open-source, (theoretically) patent-unencumbered video codec to fall back on if H.264 became legally impractical to use. (Since YouTube is the world’s largest user of H.264 video, they would be extremely vulnerable to unfavorable licensing changes.) TL;DR—Including WebM as an alternative format protects your right to distribute your own work however you want. It’s an important format to be aware of, especially if you’re an individual artist selling physical copies of your work to collectors or exhibitors,