On a positive note, we found that Sling’s remote control gave us control over the application running on the computer. While our trailer was running in Windows Media Player, we could pause and rewind it. We could even restart the video after stopping it, which was great. However, once we started messing with the playback, the stream’s bit rate plummeted to under 1,000 Kbps. This didn’t affect the audio, but video playback dropped to seemingly only one or two frames per second. Further study revealed this to be a problem on our PC. With several apps already open, playing the HD trailer put our CPU (Intel Q6600) utilization at around 25%. Starting SlingProjector doubled this to roughly 50% with peaks pushing 60%. Under this load, video playback on an Nvidia Quadro NVS 440—built for multi-monitor support, not blistering graphics and video performance—suffered, sometimes dropping to a stream well under 300 Kbps and stopping to buffer frequently. We quickly learned with the SlingCatcher that what you see on the PC is what you get on the TV. You may want to limit your computer’s workload while you run SlingProjector.