Currently Being ModeratedApr 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)?
Currently Being ModeratedApr 9, 2013 4:42 AM (in response to Atrophius)
I found this in Mac forums this works
I know this is old, but I ran into this earlier and came across this thread in a google search. As it turns out, it takes forever because it converts the video to .mov container (DV format). I found through further searching that you can instead just drop the videos into your imovie project data folder and it will use them without converting. It still takes a few minutes to process (1 hr .m4v 1920x1080 clip took 12 minutes on my new Air, instead of 9 hours as previously estimated through normal import), I suppose indexing or something, but much better.
Specifically, in your home folder, go to Movies -> iMovie Events -> (project name), and drop in your video there. When you start iMovie it should start processing the files, but it didn't actually convert the files. They just popped up in my event library ready to use.
This has to be the stupidest thing I've come across, as the forever conversion seems completely unnecessary for the application to function. perhaps it's a safety net for certain other formats.
Currently Being ModeratedOct 12, 2013 9:54 AM (in response to buknoy3)
Ingenious. It worked like a charm my 1 hour long Optimization was completely skipped and turned into a 5 minute processing event time. All I wanted to do was to combine two video clips together. Worked like a charm.