Changes in DNS commands in Leopard

Prior to Leopard, if you wanted to clear out the DNS cache for web-paqe connectivity issues, you would fire up Terminal.app and type:

lookupd -flushcache

For whatever reason, beginning with Leopard, Apple has changed this command to:

dscacheutil -flushcache

Issues w/ extreme latency talking to network mounted sharepoints

End-user was reporting his brand-new Intel MacPro was taking forever to transfer files (any files) to his particular mounted sharepoint on the company's Xserve.

After verifying the problem by reproducing it (the LAN in question was gigabit), but the throughput numbers were more akin to 10 Base-T), I blew through all the usual suspect, quick 'n dirty, first line ruling out of points of failure:

— Testing his patch cable (at port and switch),
— Made sure his port on the switch was configured for 1000 Base-T,
— Verified all Server-Side configs for this user's account.
— Logged into another User Account -- was NOT able to reproduce the problem.

So I've isolated the anomaly to his User Account. What was throwing me off however, was that when logged back into the problem user account, I found I *WAS* able to mount OTHER network shares (such as my own laptop with File Sharing enabled) with normal (gigabit speeds) throughput.

So... it's now down to just HIS user account, on HIS machine, logging in ONLY to his share point on his company's File Server--other networked share points were normal. (AppleTalk was disabled on all clients, and he / they were all talking to their File Server over TCP/IP).
A protocol analysis was the only other logical Systematic Fault Isolation Procedure left that I could think of, so I launched my open-source packet sniffer, Wireshark, (formerly Ethereal) to analyze his machine's packet flow, and BINGO!

I discovered immediately, that his machine was talking to the server (and NOT the other network share points), with SSH encryption (my bad, as while troubleshooting another issue with this user's machine a few days earlier, I had selected "Do not allow communication over clear text", in the "Connect To Server" options box in his AFP client's console, and had inadvertently forgotten to UNcheck after I was done). Thus, everything the user was doing, that was Server related, was getting bottlenecked by the encryption process. Clearly, the fix was simply to UNcheck the checkbox to "Do not allow communication over clear text" options button in "Connect to Server" console / client.

DV Editing -- Notes I Took

A short and very abbreviated list of some of the notes I took at a one-night class for Digital Video Editing. I kept referring to it as an outline for most video-editing projects, so posting it here.


• DV Captures at 720 x 480 (rectangular)
• Computers display square pixels / TVs display rectangular pixels.
• You need to change video from 720 x 480, to 640 x 480. (this doesn't change the resolution, just makes the pixels square).
• Apple has it's own implementation of both H.264 AND MPEG 4 (get to it by exporting "Movie to QuickTime", rather than the first codec popups you see).
• Select "None" for RAW video
• 2 different ways to compress video:
       
        a) Temporal (between keyframes, i.e., from frame to frame to frame...)
        b) Spacial (IN each frame, i.e. looks at all the pixels in each frame to determine the best way to  compress it).
• H.264 -- NEVER go below "Medium" quality.
• When possible, use a manual bit-rate (data rate)... rather than a "variable" bit-rate.
• When compressing for iPod video, do not exceed 2400 KBPS (ideally, use manual bit-rate of 2100, allowing for audio's bit-rate; however... if using H.264 as compressor, use data-rate value of 768.
• Use "Compression" - by Ben Wagner, for pretty intuitive GUI for on the fly compression.