Compressor Failed Quicktime Error 2
Contents |
a title. You can not post a blank message. Please type your message and try again. gld Level 1 (0 points) Q: Failed: QuickTime Error: -108 Everytime I try to use Compressor to create a file using the 'HD compressor quicktime error 50 for Apple Devices (10 Mbps). it fails within seconds with an error message compressor quicktime error 120 of 'Failed: QuickTime Error: -108' . I only get this on my MacPro 12 core. The Macbook doesn't have this issue. final cut pro quicktime error 50 I guess the error lies within Quicktime itself. Any suggestions appreciated! Mac Pro, Mac OS X (10.7.2), 12 core, 16GB RAM Posted on Mar 7, 2012 7:22 AM I have this question too
Final Cut Pro Video Rendering Error -50
by Russ H,Solvedanswer Russ H Level 7 (21,825 points) Quicktime A: Start with these troubleshootingsteps : Reset Background Processing; Trash preferences; Run this repair tool.Russ Posted on Mar 21, 2012 11:32 AM See the answer in context Close Q: Failed: QuickTime Error: -108 All replies Helpful answers Page 1 Next by roggesound, roggesound Mar 21, 2012 7:27 AM in response to gld Level 1 (0 points) Mar 21, 2012 7:27 AM in response to gld I've been having this problem, too. I had 5 files in a batch to convert, and they did exactly what you said. Then this morning, when I turned on the computer and loaded the same batch, one file went through correctly, and the others failed. Then I shut down compressor and share monitor, and opened disk utility. I clicked on repair for both volumes that I was using (an external holds the source material, and another external is the destination). Loaded my batch again, and it's currently chugging away at the first file, with the others waiting nicely. Neither disk seemed to have any problems, and they verified correctly, but I clicked repair anyway. It seems to have done the trick.Before this, I tried doing what it says here: http://osxdaily.com/2011/11/15/repair-user-permissions-in-mac-os-x-lion/, but didn't see any change. Helpful (0) Reply options Link to this post by roggesound, roggesound Mar 21, 2012 9:17 AM in response to roggesound Level 1 (0 points) Mar 21, 2012 9:17 AM in response to roggesound Of course, at the end of the first file of this batch, the other three files failed. I will continue to poke at
Share -> Send to Compressor option to render them within this application, Compressor would fail randomly during the process with a QuickTime Error -50. I couldn't really make sense of the error as it happened randomly, meaning sometime the rendering would be successful, sometime not. It also appeared to be independent from the encoding parameters utilized. Tweaking with them did not help at all. Looking up on the Internet I found many others with the same problem, but none of the recommended solutions worked for me, so I had to look for my own! Long story short, here is what worked for me. Are you ready? Well the solution is: do not close Final Cut Pro X after having issued the Send to Compressor command and switched https://discussions.apple.com/thread/3785901?tstart=0 to Compressor! Apparently Compressor needs Final Cut Pro X still up and running in the background in order to be able to render successfully. Folks with not enough RAM/CPU power may think to free up some memory by closing Final Cut Pro X once the Send the Compressor command has been issued (it was so for me, before I upgraded my Mac Book Pro to 8 GB of RAM). Closing Final Cut Pro X while Compressor still has to render/encode the movie causes it http://marcoghislanzoni.com/blog/2012/06/29/solved-apple-compressor-fails-with-quicktime-error-50/ to fail with the cryptic QuickTime Error -50. Since I have been leaving FCPX open in the background, Compressor never failed once! Hope this helps! Previous Post Next Post You may also like 6 Jul 2012 Final Cut Pro X: How to copy and paste audio keyframes 21 May 2010 Picture Resolution vs Printing Size 23 Oct 2012 [SOLVED] Update XDebug in MAMP to work with Netbeans (Mac OS X) 9 Comments Ben says: 10 May 2013 at 9:02 pm Omg thank you so much, this was driving me mad! Reply Marco Ghislanzoni says: 13 May 2013 at 12:01 pm You are welcome! Reply Luca says: 14 Jun 2013 at 3:16 pm Ciao mi potresti spiegare la procedura nei dettagli per favore. Grazie Reply Marco Ghislanzoni says: 14 Jun 2013 at 11:22 pm Ciao Luca, In pratica l'errore e' causato dal fatto di mandare il filmato in rendering tramite Compressor e, una volta lanciato, di chiudere Final Cut Pro con l'intento di liberare memoria e risorse. Per lavorare correttamente, Compressor ha bisogno che Final Cut Pro resti aperto. Chiudendolo mentre Compressor lavora, si causa l'errore Quicktime -50. Spero ti sia utile. Ciao! Reply luca says: 15 Jun 2013 at 10:07 am Il problema è che io final cut pro x non lo chiudo e l'errore mi si crea lo stesso. Ora ho esportato da final cut con codec ProRes e mi ha generato tranquillamente il file .mov (da 35GB) in pochi minuti senza nessun errore, ora cosa mi consigli
days) Photoshop - Illustrator Video Production Training DaVinci Resolve Training SketchUp Training Lumion 3D Training ScreenFlow Training Live Online Training On-Site Training http://www.geniusdv.com/news_and_tutorials/2009/12/quicktime_error_-120_in_compressor.php contact Contact Us About us Directions-Hotels Phone Support Instructors Testimonials F.A.Q. Privacy Policy GeniusDV Training Training for SketchUp, Screenflow, Final Cut Pro, Avid Media Composer, https://www.iskysoft.com/quicktime/troubleshoot-quicktime-errors.html After Effects, and Photoshop. After we upgraded some of our classroom machines to Snow Leopard (Mac OS X 10.6), an old problem reared its head when we quicktime error tried to use Compressor to render H.264 video. When we would submit jobs directly from FCP using the Share -> Using Compressor option in Final Cut Studio 3, the Compressor jobs would fail with "Quicktime Error -120." And once one job failed, all the jobs that came after would fail too.Asking around the compressor quicktime error office, nobody could say for sure what Error -120 stood for – but one of our old-timers did suggest a fix. Simply pick "Reset Background Processing" from the Compressor application menu, and Compressor will flush out any old flotsam from its background rendering pipeline.After the jump, a little bit about what Reset Background Processing does ... In basic terms, Compressor offloads its compression jobs to a background distributed rendering engine called QMaster. Incidentally, this engine can also power background rendering for Maya and Shake if you want it to. The catch is that, even though you may only be using your local workstation to render your video, QMaster still goes through the motions of setting up shared folders and job lists and chunking out the render for distribution.Normally, this just means that Compressor is insanely easy to set up for a distributed render. Unfortunately, it also introduces an awful lot of moving parts to the render pr
More Music iOS DVD Photo Review Free Business Alternative iPod iPad Camcorder Apps Mobile Computer OS X Entertainment Movies Game Technology Software Infographic Hardware Tips Homemade Streaming Troubleshoot QuickTime Errors Easier, Faster and Better Contents 1. About QuickTime 1.1 For Mac 1.2 For Windows 2. QuickTime Player 2.1 Play AVI 2.2 Play WMV 3. QT Broadcaster 4. QuickTime Plugin 5. Screen Recording 6. QuickTime Errors 7. Free QuickTime Pro 8. QT Movie Editor 9. QuickTime Trailers 10. QuickTime for Mobile 11. QuickTime AirPlay Although Apple is responsible for a lot of beneficial products and software, it has also created some of the most frustrating technological innovations in the modern world. A great example of that is iTunes, which is a necessity for anyone who has Apple products. The program isn't irredeemably bad, of course, but it has a number of different issues that crop up from time to time. One of those issues is with QuickTime. The relationship between QuickTime and iTunes is important. iTunes often requires QuickTime to run properly, but sometimes things don't go as planned. Below, you'll find a list of some of the most common QuickTime-iTunes errors and how to fix (or at least troubleshoot) them. Part 1: For Mac: iTunes and QuickTime Errors and Troubleshooting Part 2: For Windows: iTunes and QuickTime Errors and Troubleshooting Part 3: QuickTime for 64 Bit Errors and Troubleshooting Part 4: List of QuickTime Errors and Troubleshooting Part 1: For Mac: iTunes and QuickTime Errors and Troubleshooting Although Macs and iTunes both come from the same company, they may still run into errors. Some of the most common errors include: • Videos Unable to Play • iTunes won't open • Podcasts Not Playing • Music not Playing/QuickTime Crashing • Playback Language Changes Of course, some of these problems might not be exclusive to iTunes and QuickTime, but there may be a QuickTime error that fixes each of these problems. So, how do you go about fixing these problems? 1. Videos Unable to Play If you have a Mac and you use iTunes a lot, then the most common problem you're going to face is that your videos won't be able to play. The error message that pops up in this situation is often "This movie requires QuickTime, which is not supported by this version of iTunes." This can seem frustrating and confusing especially considering that QuickTime is likely installed on your computer and worked perfectly beforehand. If you receive this error message, then there are a few different problems that could be plaguing your version of iTunes. In some cases, the 64-bit version of iTunes has trouble with Qu