Staff Blogs

Getting to know the Terminal Part 1: Basic File Operations

The Terminal is an application that drives fear into the heart of a lot of Mac users - an application they only dream of using in their worst possible nightmares.

It's really not that scary - in fact, it can actually be a very useful timesaving device. You can perform operations on a large number of files at once in a fraction of a second, saving a lot of time.

Although the GUI is prettier and more intuitive, constantly moving, clicking and dragging the mouse around the screen wastes time - not to mention that rendering the GUI takes away precious processing cycles from the operation you are trying to perform. And you don't even need to constantly type things either - you can write a shell script to perform a task and set it to run automatically.

If you are thinking of entering the visual effects industry, most employers will expect basic command-line knowledge and shell scripting abilities. While most VFX houses use some form of Linux, Mac OS X's Terminal is almost identical with the exception of a small number of proprietary commands.

So let's get started.

Setting up

First of all, open up the Terminal by navigating to /Applications/Utilities and double-clicking the Terminal application. I find it useful to ctrl-click the dock icon and select Keep in Dock so it is always there for convenience, but this is up to you.

A window like this will appear:

The title bar of my window says "Terminal - bash - 80x24".

bash refers to the shell I am using. There are various different shells available, each with minor differences. We will just concentrate on bash. Incidentally, if your title bar doesn't say "bash", type bash and press enter.

80x24 refers to the number of characters that can be displayed on screen at once - 80 horizontally and 24 vertically. If you resize the window these numbers will change. It doesn't matter if yours has a different value to mine.

Directory navigation

You will see something like this on screen:
Last login: Mon Jan 5 15:27:17 on ttys000
MacBook:~ Jon$

MacBook is the name of my machine, Jon is my username. The ~ indicates that the current directory is my user directory. To view the full path of the current directory, type:

pwd

This stands for Print Working Directory and on my machine outputs the path /Users/Jon. The working directory is the directory the shell will perform all commands in unless specifically told otherwise.

To change to a different working directory use the cd command like so:
cd Documents

The prompt changes to MacBook:Documents Jon$.

It's worth noting at this point that all commands are case-sensitive, so cd Documents is not the same as cd documents, and cd is not the same as CD.

There are some specific shortcuts you can use with the cd command that are summarized below.



It's worth mentioning here that shell commands are easily confused by spaces in a file path. If you must type a path with spaces, you must either:

a) Surround it in quotes
cd "~/Desktop/My Spaced Filename.doc"

or b) Use escape characters
Escape characters are characters placed before a potentially conflicting character (a space in this case) so that the shell knows to treat it as text and not as a command. The escape character for the Unix shell is \ (backslash).

cd ~/Desktop/My\ Spaced\ Filename.doc

Viewing directory contents

If you want to view the contents of a directory inside the Terminal window, use the ls command. ls is short for "list" (you'll notice that shell commands are generally quite short as they need to be typed often).

cd /
ls

Returns:


Notice that ls returns system files and folders that would normally be hidden by OS X, except for files and folders that have a dot at the front of their name such as .DS_Store. You can show these by typing ls -a (short for "all").

You can also specify a directory as a parameter such as ls /usr/bin and it will list the contents of this directory instead of the current one.

You can set several options when you call ls such as:



You can combine as many of these parameters as you like such as:
ls -l -R

Or more simply:
ls -lR

(note: some parameters automatically override others)

These are just a few parameters of many. For exhaustive details of the parameters available, type:

man ls

This is an important Unix concept that also translates to OS X. Man (manual) pages are documentation files easily accessible from the shell using the man command. They will tell you everything you could possibly want to know about the command such as its syntax, parameters, compatibility and return values (more on that in the upcoming scripting tutorial).

You can use man with any command such as man cd, man ls, man echo. With the man page open, press Space to go to the next page and press q to quit and return to the shell.

This gives you documentation instantly at your fingertips, even if the machine you are using doesn't have an internet connection.

Basic File Operations

Use the cp command to copy files like so:

cp [source file] [destination path]

Here's an example on my system:
cd ~/Desktop
cp UntitledDoc.txt ../Documents

This will set the working directory to my desktop. It will then copy UntitledDoc.txt to my Documents folder (remember that .. refers to the parent directory).

You can also create a duplicate of a file within a directory by changing the destination filename:
cp UntitledDoc.txt UntitledDocDupe.bak

To copy a folder and all its subfiles and subfolders, use cp -R. Type man cp to learn about the other parameters.

To move a file, use the mv command with the exact same syntax as the cp command.

To rename a file, you can either use the rename command (same basic syntax as cp) or use mv like so:
mv myfile.txt mynewfile.txt

To delete a file, use rm:
cd ~/Desktop
rm myfile.txt

Some useful rm parameters are listed below:



That's it for the first tutorial. In Part 2 I will be covering more file operations, working with directories, wildcards and permissions.

Categories: Apple, Software
2 comments Posted Monday January 5 2009 4:28 PM Permalink

Pro Applications Update 2008-05 is out

Apple just released Pro Applications Update 2008-05. This is identical to Pro Applications Update 2008-04 except it now comes with Color 1.0.4.

The news is still hot off the press so Apple haven't gotten around to updating their release notes at this point in time, however, given the timing and the fact that only one application was modified, it is safe to say that this patch was released solely to fix the dreaded XDCAM bugs in Color 1.0.3.

If you are currently running 1.0.3 and suffering from the XDCAM bug I would advise updating to this version. If not, the Golden Rules (TM) apply as usual:
* Never update in the middle of a project.
* Don't update if you don't actually need any of the features included in the update.
* Always clone or backup your system beforehand.
* Wait for at least a week to see if there are any reported problems with the patch.
* Wait even longer if you're using third party hardware or plugins e.g. the AJA Kona card or FXFactory plugins.

Update: Changelog is now up:

XDCAM Clip Relinking Is Fixed
XDCAM EX, HD, and 422 clips now relink properly.

ISO Changes in the RED Tab Appear Correctly
Instances where the Color UI did not accurately reflect changes made to the ISO parameter in the RED tab of the Primary In room have been fixed.

Improvements to the Blur Node in the Color FX Room
Adjusting the spread parameter of the Blur node no longer causes the clip to scale up.

Categories: Apple, Software, Final Cut Studio
1 comment Posted Wednesday December 17 2008 11:44 AM Permalink

Mac OS X 10.5.6 released

Apple just released Mac OS X Leopard 10.5.6. Here are the most relevant changes for video professionals (not many as we're frequently overlooked unfortunately):

Graphics

* Includes general improvements to gaming performance (I think they are referring to improved OpenGL performance in general, which affects applications like Motion and hopefully will boost poor GeForce 8800GT performance).
* Includes fixes for possible graphics distortion issues with certain ATI graphics cards.

Networking

* Improves Apple File Service performance, especially when using a home directory hosted on an AFP server. Important: If you are using Mac OS X 10.5.6 (client) to connect to a Mac OS X Server 10.4-based server, it is strongly recommended that you update the server to Mac OS X Server version 10.4.11.
* Improves the performance and reliability of TCP connections.

General

* Includes Mac OS X security improvements (always good).
* Adds a Trackpad System Preference pane for portable Macs.

See the full list here.

The changelog (which I don't have access to but was leaked on the net) for one of the beta versions of this patch listed a fix for various hiding bugs. I know several people have had a problem with Final Cut Pro where they have been unable to show it again after hiding, so it would be interesting to see if this fixes the issue.

Once again, don't install this update until it's been out for at least a week (minimum) and you've checked around internet forums to see if people have experienced any issues. When you do update, always assume the worst WILL happen and clone or backup your hard disk first. Never update in the middle of a project and don't update early if none of the issues fixed affect you.

However, it is good to install security updates as soon as possible (again, wait to see if people report problems, although this is normally rare with security updates). Luckily Apple have included the security content of this update as a separate download for those who don't want to risk upgrading their OS. It is available in Intel and PowerPC versions.

P.S. It's good to know that Apple aren't rushing to patch the XDCAM bug with Color 1.0.3 as, clearly, improving the performance and reliability of Chess is far more important ;)

Update 12/16/08: Lots of people reporting problems with this update.

Categories: Apple, Software
0 comments Posted Monday December 15 2008 1:00 PM Permalink

Solving missing framework errors in Final Cut Studio

If one of your Final Cut Studio applications crashes the minute you open it, chances are it's down to missing frameworks. If you click the Report button on the crash dialog, it will tell you the reason. Alternatively you can fire up the Console in /Applications/Utilities to see the message.

You'll probably see a message like this:


Here's how to copy that file back:

1. Firstly, if you have another machine running Final Cut Studio, it's much easier to take the file from that machine (in this case /System/Library/PrivateFrameworks/BrowserKit.framework) and copy it to the same location on the current machine.

2. If you don't have that luxury, you will need to extract it from your installation DVD. Put the disc in the drive and open up the Terminal in /Applications/Utilities.

3. If you are using Final Cut Studio 3, type the following:


If you are using Final Cut Studio 2, type the following:


Press enter after typing cd /System/Library/PrivateFrameworks, then paste the next part as one whole line. After typing the sudo gunzip... line you may be prompted for your password.

If you are using Logic Studio, substitute Logic Studio for Final Cut Studio. If you are missing a different file, replace BrowserKit.framework with the other file's name (ProKit.framework is another common missing file).

4. If this doesn't work, replace the cd /System/Library/PrivateFrameworks line above with:


Then copy the same sudo gunzip... command from above. This will copy the file to your desktop. In the Finder, browse to /System/Library/PrivateFrameworks and copy the file from your desktop to that folder. You may be prompted for your password.

5. If problems still persist after copying the file, it is likely that Final Cut Studio is expecting a later version of the framework than the one on the DVD. The only solution in this case is to copy it from a machine running the same version of Final Cut Studio as you, or to uninstall Final Cut Studio and then reinstall it from the DVD and patch it to the latest version.

Categories: Apple, Software, Final Cut Studio
13 comments Posted Friday December 12 2008 2:39 AM Permalink

Pro Applications Update 2008-04

Yesterday Apple posted a big ProApp update containing updates for several applications.

Final Cut Pro 6.0.5

Improved High-Precision Rendering
If you render sequences using the high-precision video processing setting, make sure to update to Final Cut Pro 6.0.5 for improved reliability when rendering still images and footage in high-resolution formats.

Extended Metadata Support for the Panasonic AG-HMC150 Camcorder
Final Cut Pro 6.0.5 captures the additional metadata for footage recorded with the Panasonic AG-HMC150 professional AVCHD camcorder.

Improved Support for the Panasonic HDC-SD9 Camcorder
Final Cut Pro 6.0.5 provides enhanced precision and reliability when ingesting files from the Panasonic HDC-SD9 camcorder.

Improved Support for Metadata Imported from P2 Cards
Final Cut Pro 6.0.5 provides support for extended metadata that is captured on P2 cards.

However, one of the biggest features doesn't even come from Apple. RED have posted their Final Cut Studio Installer that adds native .R3D file support to FCP 6.0.5.

Compressor 3.0.5 and Qmaster 3.0.5

Using QuickClusters and Back to My Mac on the Same Computer
The QuickCluster feature of the Apple Qmaster distributed processing system is a simple and automated alternative to creating and configuring clusters manually. In previous versions of Compressor, enabling the Back to My Mac feature in Mac OS X v10.5 Leopard would remove any existing QuickClusters. This issue has been resolved. For more information about QuickClusters, see the Distributed Processing Setup guide.

Color 1.0.3

Improved Format Support

Color 1.0.3 provides support for XDCAM 422 media and for the RED plug-ins for Final Cut Studio.

The RED plug-in and accompanying documentation can be downloaded at http://www.red.com. For workflow suggestions and more information about this format, see HD and Broadcast Formats, available from the Final Cut Pro Help menu.

Improved Application Reliability
Overall application reliability has been improved, including in the following areas:

* Using trackers in the Geometry room
* Using the Reconform command
* Adjusting the Minimum and Maximum nodes in the Color FX room

Improved EDL Handling
Accuracy and reliability during EDL import have been improved.

Application of Display LUT Now Indicated Consistently
Color 1.0.3 consistently indicates when a display LUT has been applied to a project in the Project Settings tab of the Setup room.

Improved Handling of DPX Image Sequences
Color 1.0.3 provides improved reliability when reading and outputting the header information of DPX image sequences, including timecode, frame size, aspect ratio, and transfer code.

The Fix Headers Button Now Works Properly
The Fix Headers button, which appears in the clip bin of the Setup room when you select an image sequence, now correctly alters the header information of DPX image sequences.

Improved Handling of Interlaced Media
Interlaced clips with Pan & Scan adjustments in the Geometry room correctly render the exact range of clip media.

Tangent Control Surface Mappings Are Improved
The HSL qualifier and reset control surface mappings for the Tangent CP100 control surface have been fixed.

Shake 4.1.1

* This update addresses compatibility issues for QuickTime codecs greater than 8 bits.

I don't think anyone expected Shake updates but yes, you read that correctly. Apple later posted a knowledge base article clarifying that the fix was for the QuickTime component only so Shake itself will still display 4.1 as its version number. It's also worth noting that this only applies to people who applied for the Shake 4.1 crossgrade or purchased it after 4.1 came out - 4.0 owners will not be able to upgrade.

Pro Applications Update 2008-04 Release Notes

I know you're probably dying to install these updates but first, make note of the Golden Rules (TM):
* Never update in the middle of a project.
* Don't update if you don't actually need any of the features included in the update.
* Always clone or backup your system beforehand.
* Wait for at least a week to see if there are any reported problems with the patch.
* Wait even longer if you're using third party hardware or plugins e.g. the AJA Kona card or FXFactory plugins.

Categories: Apple, Software, Final Cut Studio
1 comment Posted Friday November 21 2008 3:31 AM Permalink

11-16-08 - New AppleCare articles

Apple just posted some new ProApp-related AppleCare articles.

Final Cut Pro / Express

Final Cut Pro: Choosing a Hard Disk - The disk that contains your computer's operating system is called the startup disk or boot disk. In addition to the operating system, the startup disk also stores your applications (such as Final Cut Pro), your application preferences, system settings, and documents. Because the files on the startup disk are your most critical data, maintaining the startup disk is vital. Because digital media (especially high data rate video) makes your disks work harder, you should use dedicated disks for capturing and playing back your digital video and other media files. Consider your media disks as storage units that work long, hard hours, while your startup disk keeps your system properly organized. If a disk is going to malfunction, it's better if your critical data is separate from your replaceable media files. Depending on what kind of computer you are using, you may be able to use internal and external hard disks to store your media files. Each has benefits and drawbacks.

This is a very detailed article with a lot of useful technical information about the required minimum seek times, spindle speeds, etc for Final Cut Pro. Well worth checking out.

Final Cut Express 2: How to Delete the Preference Files - Learn how to resolve issues caused by unusable preference files in Final Cut Express 2.

Final Cut Express HD 3.0: Configuration error when using with iMac G5 (iSight) and Power Mac G5 (Late 2005) - If you open Final Cut Express HD 3.0 on certain computers, you'll get a "Configuration Error" message that indicates that your computer is missing certain hardware or software, or possibly an AGP graphics card.

Final Cut Pro and Final Cut Express: Convert MP3 and AAC audio files for compatibility before importing - This document explains how to import MP3 and AAC-encoded audio files into Final Cut Pro 3, Final Cut Pro 4, and Final Cut Express.

Final Cut Express HD requires a Quartz Extreme AGP graphics card - To use Final Cut Express HD, you need a computer with an AGP graphics card that is capable of handling Quartz Extreme.

Final Cut Server

Final Cut Server: Unable to launch the specified application - In some cases the Final Cut Server client application may not open when you double-click the Final Cut Server.jnlp icon or Final Cut Server.app icon. This may happen after switching user accounts or restarting your computer from a volume other than the one you used to download the Java Web Start Final Cut Server client.

Soundtrack Pro

Soundtrack: How to Configure Digidesign Audio Devices - Learn how to use Digidesign audio devices with Apple's Soundtrack music application.

I guess they're talking about Soundtrack Pro here, not Soundtrack, as the original Soundtrack was discontinued 5 years ago.

Qmaster

Apple Qmaster: Optimizing cluster storage capacity - By default, the Apple Qmaster distributed processing system saves temporary process files in the /var/spool/qmaster directory on the cluster controller's startup disk. Computers in the cluster will access this location as needed. If you are processing large source media files that exceed the available storage space on the startup disk, you may run out of storage space on that disk.

Logic Pro / Express

Logic 8: How overlapping recordings are assigned to take folders - The Takes feature in Logic Pro/Express 8 is a powerful way to organize multiple recordings of a part in your projects. Here are some tips and explanations of what it will do in various situations.

Logic Express 8: Troubleshooting Basics - If Logic Express 8 isn't starting up properly or performing normally, try these basic troubleshooting steps to remedy the situation. Please note that these steps aren't exhaustive, and are not intended to cover any specific issue. They are fundamental, basic steps that are most effective in getting Logic Express 8 into good working order, and are the steps most often suggested by AppleCare Technical Support.

Categories: Apple, Software, Final Cut Studio
0 comments Posted Sunday November 16 2008 12:20 PM Permalink

Using Compressor with multiple cores

Here's a quick tip that a lot of people still don't know about. So you've just bought that shiny new Mac Pro, you finish your Final Cut Project, export to Compressor and wait.... and wait... and wait. Hang on a second, that brand-new 8-core machine is only utilizing one core!

Welcome to the world of Final Cut Studio, which is completely unaware of multiple cores in your system. Hopefully this will change in future versions but in the meantime, here is a trick to using those cores in Compressor.

1. Go to System Preferences and open the Apple Qmaster section.



2. In the Setup tab, click Stop Sharing if Qmaster is already activated.



2. Select QuickCluster if it is not already selected.

3. Under Services, select the service marked Compressor and select the checkboxes for Share and Managed.

3. Then click Options for Selected Service.

4. Now you need to select the number of instances to use for the cluster. This is the number of copies Qmaster will spawn to compress the job, and is a question that's open to debate.



Apple's official advice is that the number of instances should be half the number of cores. So if you have a quad-core machine, you should select two cores and four if you have an 8-core machine.

However, newer Mac Pros (early 2009 onwards) and MacBook Pros (early 2010 onwards) support a feature called HyperThreading which allows each core to act as two separate "virtual cores", allowing two tasks to run simultaneously on a single core. So for these models you should match the instances to the number of cores - i.e. four instances for a quad-core and eight for an 8-core.

Some people have suggested setting the instances to the total number of cores (or virtual cores on the newer machines) minus one. I find that this depends on the format you are compressing. If you are compressing a "light" format like DV, you could probably get away with it. However, more processor-intensive formats like H.264 will need a lot more headroom. You would also need at least 1 GB of RAM per instance.

Another point to bear in mind is that Compressor needs to stitch the separate pieces of the file together once processing is complete. More instances mean more pieces to assemble, which adds to the time taken. Consequently, the time saved by increasing the number of cores may be offset by the increase in the time taken to assemble the final file. I would therefore recommend sticking with Apple's advice of half the number of cores for early Mac Pros and matching the number of cores for later models.

5. If you are using Shake. Maya or have any other command-line renderer set up with Qmaster, select the Rendering item in the list and click Options for Selected Service.

6. Click the + button and add as many "Local machines" as necessary (see step 4 for details), then click Ok.



7. Under the QuickCluster section, type a name for your new virtual cluster.

7. Click Start Sharing and close System Preferences.

8. In Final Cut Pro, export your sequence as a QuickTime movie. This is important. Do not choose File > Export > Compressor, as this will fail.

9. In Compressor, import the movie, set up your batch and click Submit.

10. Instead of "This machine", select the name of your new cluster in the Cluster list and click Submit. The movie clip will be processed by multiple cores in your machine.



This is called Virtual Clustering, and it is achieved by launching a new version of Compressor for every instance. This is much easier from the perspective of Compressor's programmers but it takes up more memory and is less efficient than if they were to implement true multi-core capabilities into the application.

So be aware that using this method will require considerably more memory than rendering on a single instance. Apple recommends 1 GB RAM per instance but again, this depends on the media you are transcoding to. If you set too many instances and don't have enough memory, your machine would slow down (or worse, crash) thus undoing the whole point of setting up the virtual clusters in the first place. For best results, follow the recommendations in Step 4.

See the article Speeding up Compressor for more tips on improving Compressor performance.

Categories: Apple, Software, Final Cut Studio
18 comments Posted Friday November 14 2008 7:04 AM Permalink

How to reinstall Compressor and Qmaster

We recently released Compressor Repair, which aims to fix some of the most common problems with Compressor - but it can't help you if you've got missing or corrupted files. Sometimes a reinstall of Compressor and Qmaster is needed (although these steps apply to any software in the Suite). Here's how to do it properly.

1. Download FCS Remover and run it.

2. Select "Compressor and Qmaster Only" as the preset.



3. Click Remove and enter your admin password.



4. Restart your machine, and when it boots up again, empty your Trash.

5. Insert your Final Cut Pro or Logic DVD (I'm using Logic here), ctrl-click on "Install Logic Studio" or "Install Final Cut Studio" and select Show Original.



If you are running Final Cut Studio 3 (FCP 7), perform Step 6. If you are running Final Cut Studio 2 (FCP 6), skip to Step 7.



7. Run Compressor.pkg (if using Final Cut Studio 3) or Compressor.mpkg (if using Final Cut Studio 2 - note the extra "m").



8. When that finishes, run Qmaster.pkg (FCS 3) or Qmaster.mpkg (FCS 2 - again note the "m").



That's it! At this point, it is a good idea to update Final Cut Studio. Several users have reported that this method did not work until they had updated Compressor and Qmaster to the latest versions after reinstalling.

(Note: I've seen other people recommend Pacifist as a way of installing the files again once they've been removed. Pacifist is a great piece of software but if you make a mistake, it's possible to seriously screw things up unless you know what you're doing. I think this method is a lot safer and less susceptible to user error. However, if the above steps don't work for you, try Scott Simmons' Pacifist method here.)

Categories: Apple, Software, Final Cut Studio
36 comments Posted Tuesday November 11 2008 2:00 PM Permalink

Vue 7 xStream and Infinite shipping now

e-on Software today released Vue 7 xStream and Vue 7 Infinite. Vue is a 3D landscape generation product that has been used on many features including Pirates of the Caribbean 2 and 3. Infinite is the stand-alone version and xStream integrates fully into 3D modeling packages such as Maya and Cinema 4D.

The best feature in my opinion is the Ecosystem technology. This allows you to change a few parameters and automatically create a forest or some grassland or a desert, complete with random plants and rocks. Each object is varied slightly to give the impression that each rock and tree is completely unique. This makes it very realistic. It can also be used for other tasks, such as the vast robot army in the Vue 7 trailer.

Vue 7 takes this even further with Ecosystem III, which intelligently places objects according to the shape of the terrain. For example, it places fewer trees on a slope than on a flat area, as they would grow in reality. You can also create dynamic Ecosystems that stretch into the horizon without slowing your machine to a crawl. The Ecosystem Painter gives you precise control over your Ecosystem.

What's great about Vue is just how much you get "for free". If you add an Ecosystem to your terrain and then create some global wind, the plants will animate realistically with no input from you. Animating the sun and clouds creates realistic shadows on the terrain below.

There's also Solid Growth IV which minimizes flicker on far-off vegetation, the ability to render 360 degree panoramas (I love this), and something I've been waiting for - a water editor. Water was always pretty realistic but now you have a lot more control. You can now import camera tracking information from Boujou, MatchMover and SynthEyes (but not PFTrack it would seem) which is a big bonus.

Finally, it incorporates a new OpenGL engine that can render up to 4 times faster and the application has been optimized to take full advantage of multi-core systems.

e-on has released a cool trailer showing what Vue 7 can do. Well worth checking out.

Categories: Software, Visual Effects
0 comments Posted Tuesday November 4 2008 1:30 PM Permalink

Upcoming Snow Leopard features you should know about

Snow Leopard is the name of the next version of Mac OS X, due next year. The idea behind Snow Leopard isn't to add a lot of features but instead to overhaul and optimize the OS for maximum performance. Developers are already receiving pre-release versions - here are some of the biggest features:

* No PowerPC support - This operating system will be Intel-only I'm afraid.

* Full 64-bit support - This was somewhat rudimentary in previous versions and consequently developers didn't really take advantage of it.

* New default display gamma - This one is very important for editors. With previous versions of Mac OS X, the default gamma was 1.8 which was great for print work. The default display gamma in Snow Leopard is now 2.2, which brings it closer to most TVs and Windows computers.

* Cocoa rewrites for all applications - "Almost all" of the visible applications (including Finder) have been rewritten in Cocoa. Cocoa and Carbon are two different application programming interfaces (APIs). Basically, Apple has decided that it wants to transition developers away from Carbon (which is more convenient if you are also developing for Windows) and towards Cocoa instead. Consequently, Cocoa tends to get all of the new features (such as 64-bit support) while Carbon gets left behind.

Ars Technica speculates that Carbon applications in Snow Leopard could be "wrapped" in Cocoa. I imagine this would affect performance and it should be noted that Final Cut Pro is currently written in Carbon. A Cocoa rewrite of FCP is inevitable (and much appreciated) but of course, no-one knows when that will occur.

* And then of course, all the features mentioned in the original press release - Grand Central for more efficient multi-core processing, OpenCL for using the GPU as another processor (must be why the new MacBook Pros have two GPUs) and QuickTime X which offers "optimized support for modern codecs and more efficient media playback" which would imply some kind of acceleration.

So all in all, this looks to be a promising update for people in the film and TV industries.

Categories: Apple, Software, Analysis
0 comments Posted Monday October 27 2008 3:20 AM Permalink