Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

iMovie '11 Optimize on Import

When I was using iMovie '09, I made a habit of not optimizing (transcoding) events on import so that I could import a ton of stuff fast, take what I need and put together the final movie, and then do the transcoding during the rendering phase. This is absolutely essential for importing large events that I only want to use several clips out of, because it keeps me from wasting a ton of time upfront (what's the use of transcoding 4 hours worth of raw video for a 10 minute final render?) for all of my projects.

Now, with iMovie '11, even when I don't check the box for optimizing on import, it seems to do it anyway. What's going on here? Is there anything I can do about it, or will I just need to go back to iMovie '09?

Intel Macbook Pro 3rd Generation, Mac OS X (10.6.4)

Posted on Nov 7, 2010 7:49 PM

Reply
32 replies

Nov 23, 2010 10:44 PM in response to kfoggy1

Because iMovie will no longer read H.264 files without converting them to AIC. PLEASE be sure to send your findings and shortcomings to Apple it is the only way to get things noticed and hopefully fixed http://www.apple.com/feedback/imovie.html

--
Daniel C. Slagle
Keeper of the
"Unofficial" iMovie FAQ I may receive some form of compensation, financial or otherwise, from my recommendation or link

Nov 27, 2010 6:23 PM in response to Tom Wolsky

I'm using iMovie. I had used final cut for a film and exported it using quicktime at a fairly high data rate. Ended up with a very good quality film. Now I've lost use of final cut and had some editing to do and had to use iMovie. I'm using clips from the original and exporting using Apples export option 720p HD. The quality is very good and nearly impossible to differentiate from 1080p on a computer screen. My use is primarily sharing films online, facebook, vimeo etc. The quality is still more than sufficient for Apple TV on a large television screen. The other option is to export using quicktime at 1080p with a 16,200 data rate. I'm not sure what use optimizing the movie is. If someone can explain that?

Tom, what do you mean h.264 is not designed for production? Production of what exactly? What codec is standard? Assuming one is not going to transfer to back to film.

Nov 27, 2010 7:19 PM in response to fero7

H.264 is a interframe compression codec. It's used in acquisition and in delivery. Because compression is spread across multiple frames it's not suitable for production. Either a system converts the media to an intraframe compression, where every frame is encoded separately and can be edited with precision, or the system does this on the fly. No Apple applications do it on the fly. It is simply too great an expenditure of processor resources and makes the editing application a dog, i.e. see Premiere Pro struggling to edit this media.

Jan 18, 2011 7:06 PM in response to Nate Lee

Someone has found any good workaround for this issue? I'm trying to import mp4 files, NTSC 30fps, 720x480, from some vhs tapes i intend to write do dvds. So first i'm capture the video to mpeg2 because the software i use cant do it to mp4 directly. Then I convert mpeg2-mp4 video using handbrake. When I import the video to imovie it optimizes it, even if the optimize video box is unchecked.

Thanks,

Andre.

Jun 8, 2011 9:50 AM in response to Atrophius

I found a workaround using ffmpeg to copy the video from the camera into a mov container this is quick since the video and audio streams are just copied into a new container format. Unlike mp4 or avi, the mov is then accepted by iMovie 11 for import without recode.

Here is how I did it:

  1. Download Miro video converter and install it into you applications folder.
  2. open a terminal and type (withour the quotes): "cd /Applications/Miro\ Video\ Converter.app/Contents/Resources"
  3. type (without the double quotes but with the single quotes. tip: you can get the path of your source video by selecting it in the finder, pressing cmd c and then cmd v in the terminal): "./ffmpeg -i '/Path to your source video' -strict experimental -f mov -vcodec copy -acodec copy '/Path to your target video.mov'"
  4. open iMovie, select import->movie, choose the new .mov file and make sure the optimize checkbox is turned off. Voila you have a small file in your library without long waits during import but with slower processing by iMovie.
  5. In principle this can be easily written into a bash script that does batch conversion.


one disadvantage is that the new files have the date when you did the conversion and not the date when the original clip was taken. this can be worked around using touch.

in a terminal type (again without double but with single quotes): "touch -r '/Path to your source video' '/Path to your target video.mov'"

enjoy

Sep 27, 2011 9:29 PM in response to thawn1

I had been using ffmpeg to convert my recorders 1080p60 content to 720p60 for use in iMovie 09. It worked very well, but now, like most others, I am pretty upset that I upgraded to iMovie 11 and it now takes EXPONETIALLY longer to import videos. I did not mind the export / encode delay, and I did not mind the "dogishly slow" performance due to working with the content in h.264 long gop. Why must iMovie 11 do this??? Unlike thawn1, my convert (with or without scaling) results in insanely long iMovie 11 imports. I find this complete unacceptable. Common Apple, don't DOWNGRADE the features in a new release!

Nov 22, 2011 7:57 PM in response to Atrophius

Another problem that I'm having that led me to find this forum: there's no way to cancel the optimizing once it has started. I made the mistake of importing three mp4 files at once, and now I can't stop it (short of killing the process in activity monitor, which i don't want to do for fear of corrupting the files).


EDIT

Aaaauuuugggghhh! Now it's generating thumbnails. Make it stop!

Jan 20, 2012 8:11 PM in response to Atrophius

Hi all, not sure if it helps but my 2 cents is the generating thumbnails bit is not that horrible, just let it run. Also, try without using MPEG Streamclip. Import full size into iMovie '11 then right click the clips and then select "Optimize Video (Full)". I was going crazy wondering why my iPhone 4S 1080p video was stuttering despite having a 7200rpm drive.


Simple fix, right click, Optimize Video. Let it do it's thing with Optimize and Thumbnails, it will make editing much smoother and easier, from what I find.


On my Core 2 Duo 2.4ghz MacBook Pro mid-2010 13" the optimisation is around realtime, ie. 2 minutes to optimise a 2 minute clip.


On the 2011 Core i5 and Core i7s it should be half of that, so, let it do its thing.


Optimize as in Optimize Video (Full) option.

Jan 20, 2012 8:12 PM in response to DaKaZ

DaKaZ wrote:


I had been using ffmpeg to convert my recorders 1080p60 content to 720p60 for use in iMovie 09. It worked very well, but now, like most others, I am pretty upset that I upgraded to iMovie 11 and it now takes EXPONETIALLY longer to import videos. I did not mind the export / encode delay, and I did not mind the "dogishly slow" performance due to working with the content in h.264 long gop. Why must iMovie 11 do this??? Unlike thawn1, my convert (with or without scaling) results in insanely long iMovie 11 imports. I find this complete unacceptable. Common Apple, don't DOWNGRADE the features in a new release!


Try to Import directly to iMovie '11 as full size (don't transcode with anything else), then in iMovie '11 right click and Optimize (Full Size) clips. I'm now using iPhone 4S 1080p video and the Optimize in iMovie '11 makes things silky smooth in one click (just have to wait for the Optimization, it can be anywhere from 30fps to 100+fps to Optimize depending on your Mac)


Optimize as in Optimize Video (Full Size) option.

Mar 21, 2013 9:20 AM in response to Daniel Slagle

Just wanted to say thanks for the suggestion about using MPEG Streamclip to convert to Apple Intermediate Codec prior to importing to iMovie. It's so, so much faster than trying to import an MP4 file straight to iMovie and waiting for it to go through the painfully long optimization process.


Drop your file onto the middle of the MPEG Streamclip window and then select the File menu and then Export to Quicktime. Set the compression type to Apple Intermediate Codec, leave the quality at 50% and sound at uncompressed, stereo, auto. Select the frame size if needed. If the source was interlaced, check the box next to Interlaced Scaling. If the source was originally 720p then you can uncheck this box. That should be it. Click Make Movie and then import the file it makes to iMovie.

Apr 5, 2013 10:56 AM in response to AJ 2010

The issue is that you are still transcoding your footage, albeit outside of iMove. Which is a great approach (compared to letting iMovie transcode for you) if you wanted to edit in intraframe. However, if I want to edit in h.264 there still doesn't seem to be a good solution. Does anyone out there know what ClipWrap does to QT containers to make them iMovie friendly and avoid forced iMovie transcoding (http://www.divergentmedia.com/blog/fullpost/clipwrap_248_imovie_secrets)? Is there a way to replicate it with any available tools (e.g. ffmpeg)?

iMovie '11 Optimize on Import

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.