Handbrake is an open source video transcoder available for Windows, Mac and Linux and comes equipped with various conversion setting presets. Handbrake can convert a single video file, a queue of video files or a DVD video in a few simple steps:

1. Select the source video file or DVD title/folder
   
2. Select a destination for the converted file
   
3. Select a conversion preset or configure the specific audio/video settings
   
4. For a single file conversion click the Start button or click Add to Queue if you wish to convert multiple files. Click Start once you have added all videos to the queue
   
5. The conversion process will start and notify you once all videos in the queue are complete

Note: For greater compatibility with iTunes, enable the ‘Use iPod/iTunes friendly (.m4v) file extension for MP4′ setting

Handbrake is by far the best free MP4 video transcoder that I have come across. Let me know your opinions or alternatives that you may use in the comments.

I have been fortunate enough to have a MacBook Pro allocated to my department which I then keenly allocated to myself for some play time Two days in and so far I am liking the latest OS X iteration.

The first thing i did was to setup and install Wndows XP using Boot Camp as I knew I would need some of the useful Windows only applications I use. This process was almost easier (if not easier) than installing Windows on a PC. Simply run the Boot Camp Assitant in OS X, set the Windows partitions size, insert a genuine Windows install CD and off you go. Your Mac will then boot initiating the usual initial Windows setup screens followed by the graphical Windows setup Wizard. Once the process is complete all that’s left to do is install the required drivers using the OS X Leopard install CD and your dual boot MAC-Windows computer is complete.

Boot Camp setup guide can be downloaded here.

Boot Camp is a great feature; however having to reboot each time to use your Windows apps is a bit of a pain. Enter VMware Fusion! VMware Fusion allows you do run a virtual OS machine under OS X much like Parallels or the archaic Virtual Desktop from Microsoft. VMware fusion was able to use my already setup Boot Camp partition as a virtual machine so setup was minimal. All that was needed was to install VMware tools once logged into Windows to allow the virtual machine to run alot smoother and use Macs inbuilt devices. VMware fusion can be run in Unity mode, which allows Windows applications to be run directly from the Dock or the VMware applications menu when the virtual machine is running (examples below).

Unity mode is nice however, I prefer full screen mode so I have allocated my Windows virtual machine to the second space in OS X. This means using the shortcut keys or Expose I can switch between full screen OS X and full screen Windows XP. Below are screen shots of OS X Leopard spaces with VMware assigned to the second space. The screen cap. looks a little odd as at the time I was also playing with multiple monitors with different screen resolutions.

I like the apple dock but I also like to organise it my way. OS X Leopard has introduced dock stacks, which allow you to sort applications, documents, downloads, etc. into folders in your dock and display them using the predefined fan, grid or list effects. I love this new feature however it looked a little plain. So over to my mate Google to find out how to pretty it up. I found a bunch of icons which the author has called Drawers which look awesome as stack icons. I will post a how to on this soon…

Other useful application I have installed which I will post about in the near future include:

- iAlertU
- iRed Lite
- WinClone

The next project, OS X Leopard on a PC…

With all Mac access completely offline and LDAP authentication for some odd (and at this point unknown) reason not able to hold a constant connection, I decided to use and configure the Directory Services Active Directory (AD) plugin. I could see the advantages and disadvantages of using the AD authentication method. However, my main concern at this point was to relieve the pressure on me from the powers to be with a quick-fix solution.

The main advantages would be a single set of user credentials for all computers (Mac & PC) in the school and easy (mapped) access to the users Windows hosted home folder. The disadvantage was that with the time constraints I was unable to find a way to map the users Windows home folder, Mac home folder and possible other AFP mappings at login. The workaround I used was to create a shortcut to the servers AFP path on all the Mac computers, which allowed users to list the directories that they had access too. During the coming holiday break I will be investigating further to find a solution.

So, I bound the XServer to AD without any hassle, opened Workgroup Manager, selected AD as the search path, authenticated and the users populated from AD. My colleagues and I then went to each Mac one by one and bound them to AD using a unique name. The only problem we ran into was that AD requires that the time on the client computer be the same (or close to the same) as the Domain Controller. With the occasional hassle, we synchronized the time settings on all Mac clients to our Domain Controller, which then enabled us to successfully bind.

With that all done I am now waiting for a full class login to occur to test the server reliability and authentication method. We will be purchasing a copy of Leopard server in the not too distant future and with the installation of this server upgrade, I am contemplating rolling back to the LDAP authentication as it allows for more flexibility and customisation considering the somewhat unique options our Mac network requires.

This is definately not the last I have seen of this issue…

We are primarily a Windows based domain. The only pocket of Macs we have are for our Photography and Visual Arts departments (and an odd Mac Book here and there). The original setup was conceived well before my time at my current company so up until I was thrown into the guts of the Mac network when the whole system went down my knowledge of the server setup was on a need to know basis. The XServe had a Directory Services LDAP connection to our Windows 2003 LDAP server and had a custom binding to pull user information from Active Directory. I never completely explored the custom mappings but from what I have been told it was a fairly intense setup to provide the out of the ordinary needs at the time.

This is my first job where I have had to support Macs so my knowledge was very limited but from the start I found the setup to be somewhat odd. The Macs would always take a considerable amount of time to startup (which I worked out later was due to Directory Services taking an age to authenticate), user accounts would randomly stop working or be denied access to applications. The main method behind the madness was to allow users to maintain their Windows based home folders, but also have a network mapped home folder on the Mac server when logged into a Mac computer. I had always wanted to reconfigure the server myself but without the necessary time or expertise I stopped myself from opening that can of worms. But with the server now down for the count I was forced to commission my plan…

More blabbering to come….

To be continued…