Currently Being ModeratedJun 12, 2013 12:14 PM (in response to mynameisearl)
I'm having a similar issue.
I have a 3min 18sec video I'm trying to create using iMovie '11. I'm using my Macbook Pro late 2011 model with 4GB RAM, and I have about 200GB of free HD space. The total components used in the creation of the video are about 140MB of data. This isn't a big project.
If I export the video as a medium file (640x360), I can create the video with no problem. I want to create a 720p video, and when I do, I get the error -108.
I don't have Time Machine enabled, and have never used it. I'm trying to create the video with nothing else open. The small video files I'm using are quicktime .mov format, the audio is aac, and the images are jpg.
I've spent a week playing around with it, trying to get it to work, with no success.
Currently Being ModeratedJun 15, 2013 7:57 AM (in response to mynameisearl)
I have the same -108 error while trying to export a 5 minutes movie in 1080p...
I tried with time machine turned off.
My computer is a 2013 MBPr w. 8go ram, more than 100Go of free space.... this is crazy,
I am actually trying in HD 720p and it worked well...
Currently Being ModeratedJun 15, 2013 8:10 AM (in response to mynameisearl)
hi CRobock & vvdesign.fr
Make sure you disable time machine from the command console. Disabling in settings does not disable the local time machine backups. Read this article. I have found that when I do this then it certainly helps and I can render HD projects upto around 30 mins in length.
Hope this helps.
Currently Being ModeratedJul 16, 2013 4:23 AM (in response to mynameisearl)
I am just having the same issue as "mynameisearl". Around 55 mins video, lots of hours working on it, and having the same -108 error.
Could you please confirm whether you could finally sove the problem? was it in the end a problem of memory space, or was it rather a problem on the type of file formats?
Any orientation and guidance would be highly appreciated!
Currently Being ModeratedJul 17, 2013 12:07 PM (in response to carverher)
Unfortunatly not - I tried everything, my largest movie is pretty simple, straight forward Video and Stills with music from iTunes - I wish I could say it was complex - it certainly is not. I have had to split my large project into two projects keeping them around the 39 min in length - any longer and I seem to get the dreaded -108 - splitting into two projects is the only way I can get them to render in 720p or 1080p.
I really wish Apple would at least comment on this. As you will have seen on the forums lots of people complain but nothing from Apple.
Out of interest - are you using a Macbook or an iMac?
Currently Being ModeratedJul 30, 2013 6:07 AM (in response to carverher)
I would be interested to know how you get on with the iMac - I migrated to a Macbook couple of years ago. I dont recall having these issues before but then I am pretty sure I only ever created my movies at 360p prior to this. Even now if I create at 360p I dont have any issues.
Just for info when I started having these issues I upgraded my Mac Book to 16GB Memory thinking this was a memory related issue. However when im rendering my files this hardly gets touched so I dont think this is a memory. When I look at activity monitor during iMovie creating the HD 720P movie it only uses around 1.4GB of memory - Im not sure if there is a way to make it use more perhaps.
Currently Being ModeratedSep 21, 2013 11:13 AM (in response to mynameisearl)
I have the solution. It isn't a problem of memory... but just a bug to render the movie.
Select all elements of your movie and launch an optimization. It will take some time and some place...
After your export will work
Currently Being ModeratedDec 9, 2013 9:00 AM (in response to Julien Dufrenne1)
I have tried 3 times today to export my iMovie project with quick time and am getting the -108 error. How do I launch an optimization? My project is 58:15 long and I have 73.43 GB available.
Currently Being ModeratedDec 10, 2013 9:49 AM (in response to Julien Dufrenne1)
Whew thanks Julien. It worked! Was confused as you said it would take time and in fact the optimization took less than 5 minutes. It asked if I wanted large or original format and I chose original. Was that right? You also said it would take space but I did not notice that it did. Am so happy..however realized as usual I forgot the put in the chapter markers so I need to Quick Time it again after I insert them. But now that I know it will work, no sweat. I have the impression that putting in those markers before a project is finished slows down the Mac. Is that just an illusion or is it valid? I have been using iMovie since 2008 when I got my first MacBook. Since I have an iMac and have changed from the old iMovie HD version to the iMovie'11. I am dreaming for a new Mac so I can install and attack Final Cut. I am enrolled in "One to One" but at the point where most of the time the instructors can't answer my questions and during my lesson go online to find the solution. Thanks to you Julien and to mynameisearl and carverher and CRobok and vvdesign.fr.I can sleep soundly tonight!
Currently Being ModeratedJan 29, 2014 11:14 AM (in response to Julien Dufrenne1)
Love how Apple keeps taking segments of the previous version and making them disappear. Overall I can't say I am thrilled with '13 version. Titles have become increasingly limited in terms of being able to chose your preferred font and positioning of text. In many cases you get only the font they start with and NO chance to center, or right or left justify.
Now to this problem and in my case a 2010 iMac with latest iMovie '13 (10.0.9) and latest OS Mavericks.
I made a couple of movies with a single 60-90 second strip of home movies.....no edits and a single title. No problems.
But then I put together a nearly 7 minute movie with lots of interview segments and photo and video overlays and titles and some music at open and close.
Went to render the first draft to YouTube and got the -50 video render error. Went searching here and found some people speculating that the problem might be using video clips less than five seconds. Checked and adjusted those....same problem. Called Apple tech support (had to pay for it and they claimed they weren't even aware of the problem (as of today....astounding given the number of messages posted here about this problem.)
One of the big hassles is trying to figure out WHAT element of my production is causing the render problems and I do have one item here which could help community members who have the same hassle.
Go ahead and SHARE the movie and export it to a selected file location on your computer (not YouTube or Vimeo)
The render will begin and if you are having render problems, at some point the process will halt and you will get the dreaded -50 error message.
However, I discovered that I DID get an output file in my specified location. But, it was only about two minutes and 20 some seconds long instead of the full movie length of nearly 7 minutes.
So I went to the end of the truncated video file I had created and THAT pointed me to where, in the movie, the render problem was arising.
Went back to my movie and found the potential problem clip which was the next one after my shortened video ended. First, I tried detaching the audio and keeping the photos I had been using as cutaways....I assumed that would be getting rid of possible problem video, but that didn't work either.
So, I then simply cut out the whole clip (fortunately the rest of the narrative repeated most of the information in what cut deleted) and tried another render. This time it worked.
So bottom line....go ahead and render your full movie....if there is a render error you will get a video file that runs only to the point where something in your movie is causing render problems. It is a pretty quick way to zero in on the problem clip. However, if there are additional problem clips downstream, you may have to do this more than once. Fortunately, I only had to do it this one time. Hope this helps, although it still doesn't explain what the problem was with the clip that was causing the error, and Apple sure seems to be less than aware or interested in solving the problem.