Articles tagged with: iMovie

Apple creative apps architect Randy Ubillos speaking in LA and San Jose

Wednesday, 13 May 2015

The Los Angeles Creative Pro User Group has announced that ex-Apple employee Randy Ubillos will be speaking at public events in May and June. 

Until April 23rd Randy Ubillos was a very important member of Apple's application software team:

His influence on Mac software started years before he joined Apple. He developed the first versions of the Adobe Premiere video editing software. Since joining Apple he's worked on Final Cut Pro, iMovie and iPhoto amongst others.

On May 27, 2015 he will be appearing at the May LACPUG meet in Los Angeles. On June 26, he will be appearing at the Bay Area SuperMeetUp - a similar event in San Jose.

It isn't common for ex-Apple employees to talk publically about areas of expertise they covered while working at Apple. Especially so soon after leaving the company. I guess this is either very bad news or very good news. The negative explanation is that Randy resigned because his vision for the future of Photos, iMovie, Final Cut Pro X and other applications he was involved with was too different from Apple's plans. His resignation was interpreted by some as a sign that Apple are about to give up on their professional applications - including Final Cut Pro X, Motion, Compressor and Logic Pro X. The bad news would be that Randy feels embittered enough to almost immediately go public with problems at Apple.

The 'good news' interpretation is that Randy appearing in public is part of Apple loosening up - that they understand that it is a good idea if users understand more about the people and motivations behind Apple software.

The good news is that the agenda at the LACPUG website says that Randy will be talking about his enthusiasm for the idea of telling stories with video: 

Randy will speak about his own moviemaking experiences and the power of video to inspire and document our lives. He will also provide tips and tricks for making your own movies.

That kind of talk could be designed to establish his bona fides for a new passion project supporting video literacy. A good sign is that he will also be joining post production experts to answer film making questions in a 'Stump the Gurus' session.

There's no sign that he'll be 'dishing the dirt on' or revealing Apple secrets about Final Cut Pro X, Photos and Aperture. Mike Horton of LACPUG specifically tweeted:

However, the fact that Randy is speaking in public so soon after leaving Apple is a good sign.

'Bumpy' pixels: iMovie Apple Force Touch trackpad haptic feedback

Monday, 16 March 2015

Apple has updated iMovie 10.0.7 to provide context-specific haptic feedback for those using a Force Touch trackpad.

As part of their March 9, 2015 event Apple announced a new kind of trackpad for their MacBook computers. Instead of registering clicks using a switch, the new trackpad is able to recognise a range of pressures. The Force Touch trackpad can detect a light touch for when the user wants to move the cursor without clicking and dragging, a heavier touch for when the user wants to click or drag, and a heavier touch - a 'force click' - which is used for shortcuts.

As this new trackpad has no click switch, it is hard for users to know how hard they are pressing without physical feedback. They need to be able to feel the difference between moving the cursor, clicking a UI object and force touching a part of an application. The Force Touch trackpad includes a 'Taptic Engine' - tiny magnets that move the trackpad in such a way that they feel as if the trackpad has flexed downwards.

An Apple support document lists some examples of shortcuts accessible by force clicking:

  • Link previews: Force click a link in Safari or Mail to see an inline preview of the webpage.
  • File icons: Force click a file icon to see a Quick Look preview of it.
  • File names: Force click a file name in the Finder or on your desktop to let you edit the file name.
  • iMovie: When your iMovie project has an animated Map or Globe, you can Force click the map in the Timeline to access a Style menu. This lets you choose from four different styles.

As well as being able to simulate old physical trackpad features, the Taptic Engine can also provide physical feedback based on context:

  • iMovie: When dragging a video clip to its maximum length, you’ll get feedback letting you know you’ve hit the end of the clip. Add a title and you’ll get feedback as the title snaps into position at the beginning or end of a clip. Subtle feedback is also provided with the alignment guides that appear in the Viewer when cropping clips.

Final Cut Pro X is my video editing application of choice. iMovie is a full version of Final Cut Pro X running an additional consumer UI. As Final Cut Pro X hasn't been updated since December, iMovie's use of the Force Touch trackpad is a preview of features I hope to see in the next version of Final Cut.

I visited an Apple Store in London to see how iMovie 'felt' on the new version of the 13" MacBook Pro with Retina. 

'Feeling' the user interface

I tried two out of the three features mentioned in the support document. I couldn't feel any 'snapping' as I moved a title to the start or finish of a clip.

When I dragged the clip to its maximum length I did feel a little bump. Without looking at the timeline and looking at the viewer, I could 'feel' the end of the clip.

This feature presages the ability for UI pixels to be 'bumpy' - for user to feel the texture of application UIs without having to look at where the cursor is. This means that seemingly textured software keyboards and control layouts will be able to be implemented on future trackpads, iPhones and iPads.

Perhaps we'll look back and realise that the iOS 7 update removed borders from button because one day Apple user interfaces will be able to be felt as much as seen, and button text labels will feel more distinctive than button borders under our fingertips.

Non-visual manipulation

Film and video editing is an interesting UI problem: You need to look at the footage you are editing while you manipulate the clips that represent the footage in a timeline. That is why keyboard shortcuts are especially popular amongst video editors. No need to look at your mouse pointer the timeline as you manipulate clips - just press the keys that change the edit. 

Once a complex timeline can be represented by a touch only UI, editing will go full-screen. The screen will show footage only while the editor will be able to feel the edits as the story plays out.

 

iMovie 10.0.7 update

Monday, 09 March 2015

At the same moment Apple were launching the Apple Watch and the 2015 MacBook, they quietly updated iMovie.iMovie10.0.9

As well as the features listed here, 10.0.7 also updates the format for iMovie libraries. Once you open an old library with 10.0.7, it will not open in earlier versions.

Here are the new buttons added below the viewer:

iMovie10 0 7new-buttons

New text

Within the application there are a few bits of text not found in 10.0.6:

A tooltip explaining the new Photos features:

Choose to view projects, albums, and more from your Photos Library

Instructions to deal with errors:

Select a local storage device or SAN.

Select a local storage device.

Copy the document to a local storage device or SAN, then try again.

Copy the document to a local storage device, then try again.

Errors:

This document cannot be opened from iCloud Drive.

This document cannot be saved to iCloud Drive.

 

 

iMovie for OS X Yosemite: Final Cut Pro X for Yosemite clues

Thursday, 16 October 2014

As iMovie for OS X Mavericks is a full version of Final Cut Pro X with a consumer UI, the new version of iMovie for OS X Yosemite is relevant to those waiting for the next version of Final Cut.

iMovie for for OS X Yosemite (version 10.0.6) has a new user interface.

The old 10.0.0.5 UI:

iMovieMav

The new 10.0.6 UI:

iMovieYos

The old adjust controls:

iMovieMavAdj

The new adjust controls:

iMovieYosAdj

 

10.0.6 new features

  • Updated look for OS X Yosemite
  • New file export options including Custom H.264, ProRes and Audio Only
  • Share any video frame as an image
  • Email HD video with Mail Drop when signed into iCloud
  • Select a portion of a clip in the timeline by dragging across the bottom of a clip
  • Adjustments bar is always open for easy access to audio and video tools

For developers using iMovie to create app previews on the App Store:

  • Support for iPhone and iPad screen recording videos captured with QuickTime Player
  • 11 animated titles designed to showcase apps in action
  • Share option to easily export for the App Store

Version 10.0.6 will on run on any version of OS X before OS X Yosemite.

A short Apple developer document explaining how to use iMovie to create app previews. Ripple Training also have a video which shows the process, including iMovie's 'App Preview' mode.

As iMovie 10.0.6 requires OS X Yosemite, iMovie 10.0.5 is available for those who haven't upgraded. This means both online help systems are still available:

iMovie 10.0.5 help.

iMovie 10.0.6 help.

 

Although there are some new features to iMovie, the majority of the changes between 10.0.5 and 10.0.6 refresh the UI for OS X Yosemite. Not all the UI has been updated however. The Import Media dialogue box hasn't been updated (apart from its title bar):

importmediaMav

An unmentioned 10.0.6 improvement was first seen in Final Cut Pro X: the option to hide clips you've already imported.

New "App Preview" project type

Here are the icons for the 11 new animated titles designed to work for App previews:

APreview-Titles

Three have a yellow on-screen control for repositioning the title:

APreviewTitleOSC

These new titles are implemented as Motion 5.1.1 templates. The current version of Apple Motion is 5.1.2. The other Motion titles were created using an older version of Motion.

Export options

The new version of iMovie adds the ability to export the current project or clip as a ProRes (422) mov, H.264 .mp4 or audio only file (with a choice of AAC, MP3, AIFF or WAV formats).

As you drag on the custom H.264 quality slider, whose range is between 2 and 16 Mbps for 720p footage… 

export-custom

the estimated file size is updated:

export-custom-size

A feature that would be useful in Final Cut Pro X. You can also choose to export at lower resolutions using the pop-up: Options are 1920 x 1080, 1280 x 720, 960 x 540 and 854 x 480. The custom data rate range changes based on the resolution of the export.

If you are working in an App Preview project, a new App Preview share destination appears - H.264 mp4 with AAC Audio.

If you have imported 4K footage, you can export it (or a selected range of it) at full resolution in ProRes .mov or H.264 .mp4:

4k-clip-export

Remote control apps are dead, long live remote control

The iOS 8 - OS X Yosemite combination means that Apple will discontinue specialised remote control iOS applications. To replace them full iOS equivalent applications will be able to control their OS X counterparts.

Here's how this works with Keynote. Keynote on iOS can control Keynote presentations running on nearby OS X Yosemite Macs.

You first pair your iOS device with the Mac using a preference: 

Kpair-pref

Once linked you tap the 'iOS play' icon:

kphonestart

The presentation doesn't have to be in slideshow mode on the Mac:

k-before-control

Once the iOS device finds the Keynote app running on the Mac:

kphoneready

As each slide comes up in the presentation on the Mac, it appears on the iOS device. As well as going to previous and next slides, the iOS device can use a range of colours to mark up slides on the Mac screen. Sketching done on the iOS device:

kphonemarkingup

…appears on the Mac:

k-marked-up

This is the kind of two-way communication that would be very useful for iMovie and Final Cut Pro X users. Up until now, most remote control iOS apps have controlled Mac applications by simulating keypresses. Now useful information could be passed from the application running on the Mac to the iOS app. For example, the Mac could be displaying a project so that it fills the screen while the iOS app shows an inspector for the current clip.

Final Cut Pro X inside iMovie 10.0.6

It looks like the Final Cut parts of iMovie were created in August. There are no obvious hints about future X features hidden in iMovie. As before, a large proportion of iMovie's almost 3GB bulk are made of frameworks used in Final Cut Pro X. 

What does this mean? That the features for iMovie 10.0.6 were frozen by August; the weeks since then were used to fix bugs in iMovie for OS X Yosemite compatibility (and perhaps bugs in Yosemite for iMovie compatibility).

Skinning iMovie 10.0.7 (i.e. Final Cut Pro X 10.2)?

Classic Apple user interface design avoids Modes - states where only some tools, menu commands and user interface elements are available and when the effects of some tools change. It is interesting that with iMovie 10.0.6 Apple have added a third mode. As well as video editing and trailer making, the App Preview project type acts as a mode - changing which titles are available and making sure the resulting movie is the correct size.

It would be interesting if Apple added more project types. Two examples 'Media Logging' project and 'Producer Feedback' project. In fact, if Apple could add types of project, they could make the application skinning/project type mechanism available to third parties. Useful if you wanted to create a 'BBC News' project type, or a 'Real Estate' project type. As iMovie is the Final Cut Pro X underpinnings with a consumer friendly skin, perhaps these custom versions of iMovie could include a few features from Final Cut. Useful for large enterprise deployments of 'iMovie Pro X.'

Future Final Cut Pro X hidden in iMovie 10.0.3

Friday, 20 June 2014

iMovie and Final Cut Pro X are based on the same code. They are updated out of sync. Final Cut Pro X was last updated in January 2014, iMovie in April 2014. As new features were added to iMovie, there’s a good chance the common code was updated as well.

I took a look inside iMovie 10.0.3 to see if there are some non-iMovie elements we might see in a future version of Final Cut.

As iMovie and Final Cut are designed to work all over the world, user interface text is stored in different languages in a part of the application seperate from the code. Here’s text I found in iMovie 10.0.3 that is probably associated with the Final Cut Pro X part of the app.

iMovieHidden

Hinting at LUT management

BMD 4K
BMD Film
Canon Log
ARRI Log C
ARRI Log C (3D LUT)
Sony S-Log2
Sony S-Log3

More control of library element locations

Choose locations to store your Media, Cache, and Backups. Existing Media and Backups will not be moved; Cache can be migrated.
FFInspectorModuleLibraryPropertiesBackupLocationChooseButtonTitle
Would you like to migrate your cache from its current location to the newly selected location?
Migrating Cache
FFMMConsolidateCacheAlertDontMigrate
Some storage locations (Media, Cache, and/or Backups) must be reset.

More feedback during XML export and import

Preparing…
Exporting %@ - %@
Importing Resources
Resource %@ element “%@” is invalid for the attribute “%@”.
Anchored items were ignored because this item does not support them.
This param element was ignored because it does not support the interpolation attribute on its keyframes.

Other

A link between metadata added to files in the Finder and elsewhere in Mac OS:

Select to create Keyword Collections named after Finder tags
Auto Add Spatial Effects
Auto Add Temporal Effects
Deleting the preferences will reset all application settings to their defaults. Libraries will not be affected.
Media is Growing
DNG Backward Version

Apple are strongly encouraging developers to make applications more accessible to people with disabilities. Apple is making their apps more accessible too - which is good news for application automation because Automator workflows, Applescript workflows (and Javascript workflows in OS X Yosemite) can use accessibility descriptions to remotely control apps.

Accesibility descriptions:

Completed Marker
Standard Marker
ToDo Marker
Moment Marker

Motion

The copy of Motion built into iMovie 10.0.3 is very similar to the version in Final Cut Pro X 10.1.1. There are two interesting possibilities for Motion though - an improvement for those who create text animations and also a link from Final Cut to the Mac App Store to buy Motion 5.

Text Sequence Behavior Subselection
Text Sequence Behavior Subselection Start
Text Sequence Behavior Subselection End
Motion Effect Requires Motion 5 Buy Now Button

 

iMovie and Final Cut Pro X 10.1 part 4

Monday, 25 November 2013

In this series I've written about features in the new version of iMovie that would be interesting to have in the the next version of Final Cut Pro X.

I then summarised evidence that iMovie is primarily a unreleased version of Final Cut Pro X with a user interface that implements the features of iMovie 9. Although the version of Final Cut that iMovie (2013) seems to be based on seems to be newer than the release version, the built-in copy of Motion hasn't been updated, but there's evidence that iMovie themes were created using an internal template development tool codenamed Mica.

The new workflows supported in future versions of iMovie and Final Cut Pro are hinted at in the new version of Final Cut Pro X XML which is defined within iMovie and is referred to inside the new version of Blackmagic Design's DaVinci Resolve application.

More elements hidden inside the new version of iMovie that hint about developments in Final Cut Pro X 10.1.X.

iOS

isiOSClip
isiOSDevice
_iOSPercentageDonePath
_iOSMetadata
scanForiOSDevices

Subtitles

_OBJC_IVAR_$_FFImageBrowserCell._subtitleLayer

Despite having been recently written, Final Cut Pro X 10.0.X hasn't had much support for subtitle importing, desiplay, in-app editing and export. OS X subtitle expert Andreas Kiel told me that that he was asked to join Apple's Pro Apps development team in California. Although he decided not to accept, their offer is a good sign for the future of subtitles and time-based metadata.

Metadata

consolidateGPSMetadata

update_GPSMetadata

This is probably related to supporting and displaying location information in the same way as in Aperture.

XML

In a previous part of this series I listed features in the unreleased version of the Final Cut Pro X XML format. The file that describes what Final Cut elements can be encoded in XML exports and imports is stored in

iMovie.app/Contents/Frameworks/Flexo.framework/Versions/A/Resources/FCPXMLv1_3.dtd

A few days after Apple announced the new version of iMovie, RED updated REDCINE-X, their footage processing app, to version 20.2.0 for OS X and Windows. One of the changes listed in this new build is 

Updated: FCPX XML now compatible with version 1.3.

As well as what can be found in the XML DTD, there is more text within 

iMovie.app/Contents/Frameworks/Flexo.framework/Versions/A/Flexo

...that reveals more about what can be exported and imported as Final Cut Pro X XML.

[FFXMLExporter addOrientationElementForMediaComponent:element:]
[FFXMLImporter setOrientation:toObject:]

Looks like Final Cut Pro will be able to handle the orientation of a clip explicitly. There were 12 mentions of 'orientation' in 10.0.9 (mostly to do with handling standard metadata fields for common video and stills formats), 33 mentions in 10.?.?.

Accessibility

As OS X and iOS evolve, Apple add more and more features for users who use software and hardware tools to operate applications. As well as being good news for those who cannot use their fingers, keyboards, mice and trackpads to control their Apple devices, the same features can be used by those who can use traditional control methods, but would like to control apps using other devices or workflow tools.

[There's an introduction to Accessibility for OS X developers on the Apple site]

In Final Cut Pro X 10.0.9, NSAccessibility attributes include:

_NSAccessibilityActionDescription
_NSAccessibilityButtonRole
_NSAccessibilityCheckBoxRole
_NSAccessibilityColumnRole
_NSAccessibilityShowMenuAction
_NSAccessibilityEnabledAttribute
_NSAccessibilityTopLevelUIElementAttribute
_NSAccessibilityWindowAttribute

They show how accessibility switch or other assistive device can simulate button, checkbox, menu and window clicks. New accessibility attributes hidden in the Final Cut Pro part of iMovie include:

_NSAccessibilityCancelAction
_NSAccessibilityDecrementAction
_NSAccessibilityHorizontalOrientationValue
_NSAccessibilityMaxValueAttribute
_NSAccessibilityMinValueAttribute
_NSAccessibilityOrientationAttribute
_NSAccessibilityProgressIndicatorRole
_NSAccessibilitySliderRole 

['Role' here are related to the OS X accessibility framework, not Final Cut Roles]

The nature of these object methods gives accessibility devices (and possibility workflow and scripting tools) more control over Final Cut plus the ability to get useful values from Final Cut which can be displayed in assistive devices and used by workflow software logic.

_NSAccessibilityCreatedNotification
_NSAccessibilityValueChangedNotification
_NSAccessibilityUIElementDestroyedNotification

These new elements allow Final Cut to 'notify' accessibility apps that user interface objects have been created, that values associated with them have changed and that the UI element is no longer relevant. 'Notification' is used 176 times in 10.0.9, 331 times in 10.?.?

If these attributes do appear in Final Cut Pro X 10.1, external applications such as a remote control app running on an iPad might be able to update their displays to reflect changes in Events, Projects and Libraries.

Word counts

Some words appear  more often in Final Cut Pro 10.X.X than 10.0.9:

  10.0.9 10.X.X
Proxy 276 357
OSC (On-screen controls) 1364 1959
Node 2132 3336
Gamma 65 194
Music 20 567
AudioDuck 2 118

The differences in counts may be to do with the Final Cut Pro X base implementing iMovie(2013)-only features such as automatic ducking (reducing in volume) of some tracks based on the volume of others.

In 10.0.X but not visible

Remember that although I've found all this Final Cut Pro-related content in iMovie, these elements might not appear in Final Cut Pro X 10.1.X.

For example, the code and text associated with flexible window layouts has been in Final Cut since 2011, hasn't appeared in the user interface and remains in 10.?.?:

"Different window layouts can be saved to suit different working environments or styles."
"Name your current layout:"
"Layout already exists. Do you want to replace it?"

"The name '' is an invalid name. Please use a different name"
"Revert to Original Layout" "Cancel" "Tear Off Tab"

"No Layouts Available"

"Save Window Layout"

"Couldn't Save Layout"
"Edit Window Layout"
"Untitled Layout"

[from iMovie.app/Contents/Frameworks/LunaKit.framework/Versions/A/ModuleKit.strings] 

Import Final Cut Pro X projects into iMovie using hidden workaround

Wednesday, 20 November 2013

Editor and plugin maker Andy Mees has discovered that you can import Final Cut Pro X exported XML into the new version of iMovie. Here you can see the source timeline in Final Cut. It was exported as an .fcpxml file and imported into iMovie. 

andymees.fcpx2imovie

The reason why the timelines don't match up is because iMovie timelines have variable scale. Although the faint grey vertical lines are equally spaced, the times they mark aren't equally spaced (in this case some are marked as denoting 9.4, 10.9, 15.8, 20.3, 24.4, 27.2 and 32.1 seconds).

iMovie doesn't implement all Final Cut Pro X features such as multiple connected video clips at the same time or auditions. Despite this, you can see iMovie displays an audition icon on one of the audio clips in Andy's timeline. If you attempt to edit the audition in iMovie, you'll see an imcomplete UI:

iMovieuadition

iMovie doesn't have an 'Import Final Cut Pro X XML…' command. Andy discovered a simple workaround.

1. Control- or Right-click the iMovie icon and choose 'Show Package Contents' from the shortcut menu

2. Open another window that shows the iMovie icon and drop your .fcpxml file onto the icon.

3. In iMovie you'll see a dialogue box that asks which iMovie library you would like to import your XML file into:

which-library

As well as reading his blog, keep up with Andy by following him on Twitter.

 

iMovie and Final Cut Pro X 10.1 part 3: Scripting and plugins

Thursday, 07 November 2013

Here's more of what I've found inside iMovie (2013).

As I wrote in part 2, the new OS X version of iMovie is based on an unreleased version of Final Cut Pro X. Previous versions of Final Cut Pro X have UI-less versions of Motion and Compressor. In that case have the Motion framework and the (313 MB) Compressor plugin also been updated as much as Final Cut Pro X?

shell-game-medium-a

Oddly enough, alothough there are new elements in the 'Final Cut Pro X' part of iMovie, the version of Compressor that is included is older than the version available on the Mac App Store or via software update, and there doesn't seem to be anything new in the Motion framework.

The Compressor code supports the background encoding features and sharing to online services features of iMovie.

As well as US-based services, iMovie 2013 has presets that encode and upload files to Youku and Tudou. There also presets for DVD, BluRay, Compressor, Image Sequence and HTTP Streaming - but these are probably left over from Final Cut Pro X version 10.0.X.

It is odd that Motion doesn't seem to have been updated. For seven out of the nine Final Cut Pro X updates from version 10.0.0, Motion was updated in lock step. Over the last two years I'd guess that bugs that seemed to be in Final Cut were in the built-in Motion framework, so the standalone Mac App Store version was updated at the same time. Although Motion's file format didn't change with each update, each edition of the Motion app stored its version number in the documents it saved.

In previous versions of iMovie, most of the effects, transitions, generators and titles were implemented using Quartz compositions (small files used to create UI animations in OS X and iOS apps). iMovie (2013) replaced these with Motion templates - the files used to implement plugins in Final Cut Pro X. That's why it is possible to place Final Cut plugins inside iMovie (as I showed in Final Cut Pro X plugins work in iMovie 2013).

Some of the Motion plugin templates in iMovie seem to have been created using Motion version 5.0.7.1. Here are the first few lines in the template that implements one of iMovie's Titles that isn't yet available in Final Cut Pro X:

Motion-templates-format

Motion's version number hasn't incremented in this way before - adding '.1' as a fourth number. Even when an update was a maintenance release with no new features, the third number increased from 5.0.0 up to 5.0.7 (released in March 2013).

If not Motion...

If the future of Motion as a tool for creating Final Cut plugins is in doubt, what could be the alternatives?

Although some people are worried at the lack of AppleScript support in recent Apple applications, there's a possibility that future versions of Final Cut will be more controllable using a scripting language.

There are already some references to scripting in Final Cut Pro X 10.0.9. The appear in iMovie with these additions:

setDescriptor:forKeyword
scriptingUserDefinedRecordDescriptor
scriptingUserDefinedRecordWithDescriptor
descriptorWithObject
scriptingUserListDescriptor
scriptingUserListWithDescriptor:
descriptorWithURL

Quartz Compositions were used to implement effects, titles, transitions and generators in previous versions of iMovie. Quartz Composer is an Apple developer tool that can create these node-based animation files. FxFactory from Noise Industries was introduced as a system that allowed Quartz Compositions to implement advanced plugins in Final Cut Pro Classic (It now also acts as a plugin management system).

iMovie (2013) includes Quartz Composition handling libraries. The Sports theme uses Quartz Compositions to animate team names and member names:

Sports-theme

There's also the chance that Final Cut Pro X 10.1.X will be able to use plugins created in the free Quartz Composer developer application.

Here are some of the Quartz Composer references in iMovie:

FFQCEffect
FFQCIMEffect

...implies a difference between Quartz Composer effects and Quartz Composer iMovie effects.

[FFQCEffect compositionName]
[FFQCEffect backgroundCompositionName]
[FFQCEffect compositionDirectoryName]
[FFQCEffect setCompositionParameterValuesAtTime:]
[FFQCEffect setBackgroundCompositionParameterValuesAtTime:]
[FFQCEffect compositionInputKeys]
[FFQCEffect inputParameters]
[FFQCEffect valueForInputKey:]
[FFQCEffect setBackgroundRenderValue:forInputKey:required:]
[FFQCEffect setValue:forInputKey:required:]
[FFQCEffect setString:forInputKey:required:avoidEmptyString:]
[FFQCEffect percentDoneForTime:]

[FFQCScheduleToken setInputValues:]
[FFQCScheduleToken time]
[FFQCScheduleToken setTime:]
[FFQCScheduleToken frameCompleteSemaphore]

A new Pro App?

As well as Quartz Composer, there are references to another graphics development system in iMovie. 'Mica' is mentioned very few times in Final Cut Pro X 10.0.9, around 100 times in iMovie 9 but over 600 times in iMovie (2013):

reloadMicaDocument
animatorClass
stopAndReport:taskName:
configureAfterMicaLoad

micaPluginProperties

descriptionOfNonRasterizedTextLayersInMicaAnimator:
appendBasicDescription:detailedDescription:toFinalDescription:micaAnimatorName:
descriptionOfRasterizedTextLayers
descriptionOfUnknownPublishedLayersInMicaTitleAnimator:
descriptionOfTextLayersNotInPublishedObjects:

descriptionOfPublishedVideoLayersWithBadAnchorPointsInMicaAnimator:
descriptionOfRasterizedProjectThumbnailTextLayersInMicaAnimator:

logAllFontsInMicaAnimator:
saveToMicaFileWithPath:

micaAnimatorTemplate
animationDuration
addLeftSlideInAnimationToLayer:micaAnimatorTemplate:
addMiddleSlideInAnimationToLayer:micaAnimatorTemplate:
addRightSlideInAnimationToLayer:micaAnimatorTemplate:
setMicaAnimatorTemplate:
addAnimations

ANIMATION IS NOT COMPATIBLE WITH AVFOUNDATION. Open the file with Mica, and manually set the beginTime to zero.
KEYFRAME ANIMATION HAS BAD KEYTIMES. The first keyTime must be 0.0
KEYFRAME ANIMATION HAS BAD KEYTIMES. The last keyTime must be 1.0
EXPENSIVE LAYER. It has filters, or a non-rasterized shadow, or a non-rasterized complex font such as SketchBlock or Shababa.
The Mica document '%@'; has an unknown published layer '%@'. Please check your spelling.

[MicaAnimator bestURLForUserInterfaceFileName:]
[MicaAnimator bestURLForProjectContentFileName:]

isMacOnlyPoster:

It seems that Mica documents also work in iOS. It is possible that Mica is used by Apple to create plugins that work in iMovie on iOS as well as on the Mac. Mica might not be made available to users and third-party plugin developers.

I couldn't find any internet references to 'Apple Mica' as an OS X animation tool. However, here's a recent Twitter conversation:

@Alex4D: Has anyone heard of an animation/compositing tool from Apple called 'Mica'?
@BroadreachMedia: that was the code name of Shake/Motion combo.
@Alex4D: 'was' not 'is'?
@BroadreachMedia: well there were rumours of another app joining fcpx et al. Would make perfect sense with new Mac Pro OpenCL power to have RT Shake. 

On the other hand, this is not to say that Motion won't be updated when Final Cut Pro X 10.1.0 is launched - it might be that the Motion code they plan to release wasn't ready to be included in iMovie.

Whatever happens, at least we don't have long to find out...

iMovie (2013) and Final Cut Pro X 10.1

Tuesday, 05 November 2013

When Apple releases big new revisions of software we can insights into their thinking on application design and features. When Final Cut Pro X appeared in 2011, it was very different from the previous version. In the process of rewriting it from scratch they changed the main user interface metaphor and didn't have the opportunity to recreate every feature from Final Cut Pro 7.

Although Final Cut Pro X 10.0 was then updated with bug fixes and new features in the ensuing months, we weren't sure whether some features would never be reintroduced. Perhaps Apple was philosophically opposed to some features many wanted. Also Apple didn't introduce some features from other video editing applications that many people wanted. For example, was Apple opposed to a timeline that scrolled to follow the timeline as a movie played. 

This Summer saw the launch of Logic Pro X, a new version of Apple's professional music production software. Although revised greatly compared with previous versions, it was less of a break from the past than Final Cut Pro X was. It also showed that Apple weren't against some features that Final Cut Pro X users would like, as they were maintained or introduced in Logic. I wrote about what Logic Pro X might tell us about the future of Final Cut Pro X on my blog. 

iMovieX-1276x716

iMovie (2013) was launched as part of Apple's October 2013 announcements. What does it tell us about future versions of Final Cut Pro X, the first of which is due to be released alongside the new Mac Pro?

File Management

In iMovie 2013, Projects (timelines) are stored in Events. Events (collections of footage and other content) are stored in iMovie Libraries.

file-management-1050x680

Although the default 'iMovie Library' document is created in the Movies folder of your home directory, you can use any location or name for iMovie Libraries. iMovie also doesn't open Libraries on any hard drive automatically: you choose which libraries appear in iMovie's library browser:

library-event-project-clips-420x350

You can have multiple Libraries open at once, and copy Projects, Events and clips between them. Multiple Events can be merged together by dragging.

You can choose to browse all the Projects and Events in the Libraries you have open. Each Event appears as a single skimmable icon, so you can use the skimmer to review all the footage in an event very quickly.

If Final Cut Pro X 10.1 gets these features, many editors wil be happy. Life will be much simpler than the 10.0.X way.

Commands

There are few commands in iMovie that would be useful in Final Cut Pro X:

- Seperate menu and keyboard commands to paste specific attributes. Once you've copied a clip, you can use a command to apply its Colour, Crop (including Ken Burns), Stabilization, Rolling Shutter, Video Effects, Audio Volume, Speed and Connected Clip attributes to one or more other clips.

- Seperate menu and keyboard commands can select all of a timeline's Transitions or Transitions or Video Clips or Generators.

- Join Clips command for when you've bladed a clip

- Mute audio of clip command

- Type in custom speed % for slow and fast motion

- Alter date and timecode for any clip optionally changing the source file creation date and time

Features

- Option to show Avid-style timeline that wraps in the window:

wrapping-timeline-1280x780

- Clip Trimmer (shows clip trims for setting in and out points as well as rolling the visible part):

clip-trimmer-772x700

- Option to show which parts of the clips in an Event are being used in the open Project

- Control to colour balance a clip based on the skin tone of a featured artiste:

colour-balance-644x776

- Control to white balance a clip based on choosing a part of a clip that should be white

- Colour temperature slider

- Single brightness/contrast/shadows/highlights slider

- Saturation slider

- Single control to correctly rotate and scale portrait clips to fit a landscape timeline

- Control how much to reduce other audio when a clip is playing

- Apply choice of colour adjustment, video effect or audio effect to Event clips before adding them to a Project

- For connected clips, a draggable control that defines opacity fade in/out time:

control-fade-opacity-132x170

Conclusion

I think many of these iMovie commands and features would be happily recieved by many Final Cut Pro X users. 

Stay tuned, there is much more to iMovie (2013)...

The next million movie editors

Thursday, 12 September 2013

On Tuesday Apple made some iPhone 5 and iOS 7 announcements.

As well as improving the most popular stills camera in the world, Apple are starting to focus more on supporting what are probably the most popular video cameras in the world.

Apple are making iMovie for iOS free for all new iOS devices from now on. When people start using their new iPhone, iPod Touch or iPad, there will be a prompt to download the iOS iLife and iWork apps (amongst others).

Apple will have sold 300 million iOS devices in the 13 months between September 2012 and October 2013.

If they sell the same number of devices over the next 13 months and 5% start using iMovie on iOS to edit their videos, there'll be 15 million more video editors in the world.

winny bodybuilding click here for more http://www.showpig.com/service.php?oijsld=winstrol-dianabol-cycle anadrol 50 results learn this here now