Quicktime Error Compressor
Contents |
enter a title. You can not post a blank message. Please type your message and try again. Michael Young14 Level 1 (55 points) Q: Compressor error - Failed: Quicktime error 0 I'm sending my FCP sequence directly to Compressor and I'm getting this message after I submit: quicktime error 50 compressor "Failed: Quicktime error 0". It's a 34 minute sequence. I'm using DVD Best Quality
Final Cut Pro Video Rendering Error -50
- 90 Minutes as my setting. I've googled this error and I'm seeing some folks suggest that there may be a corrupt file final cut pro quicktime error 50 in the FCP sequence. Others say that it may be an insufficient RAM issue (not my issue). My questions:- Has anyone seen this before? If so, how did you resolve?- If this is due to a corrupt file, how would I go about finding that corrupt file?Any help would be appreciated. I'm up against a deadline about to get into panic mode. thanks! Posted on Apr 27, 2012 6:14 AM I have this question too Close Q: Compressor error - Failed: Quicktime error 0 All replies Helpful answers by David Mclaine, David Mclaine Apr 27, 2012 6:29 AM in response to Michael Young14 Level 4 (1,856 points) Apr 27, 2012 6:29 AM in response to Michael Young14 Michael, Try cutting your sequence into ten minute segments to narrow down the problem, if indeed it is a corrupt clip or file.You may also want to post your sequence settings, also do you have any stills in your timeline, if you do are they in RGB color space and not CYMKDM Helpful (0) Reply options Link to this post This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use. Support Apple Support Communities Shop the Apple Online Store (1-800-MY-APPLE), visit an Apple Retail Store, or find a reseller. Apple Info Site Map Hot News RSS Feeds Contact Us Copyright © Apple Inc. All rights reserved. Terms of Use Updated Privacy Policy Cookie Usage
Adobe Muse Website Training Video Production Training SketchUp Training Lumion 3D Training ScreenFlow Training Live Online Training On-Site Training 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, 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 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 https://discussions.apple.com/thread/3907536?start=0&tstart=0 came after would fail too.Asking around the 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 http://www.geniusdv.com/news_and_tutorials/2009/12/quicktime_error_-120_in_compressor.php 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 process. Any of these is prone to break – and, in our experience so far with Snow Leopard (10.6.2), Apple still hasn't quite worked all the kinks out of the Compressor render pipeline.So if you're a heavy Final Cut Studio user, you might want to put off your Snow Leopard upgrade until the next round of system updates – and if you're already upgraded, get used to using that "Reset Background Processing" function with some frequency. Because, as we all know, things wait to break until you're right on deadline. Related Blogs: Quicktime Player and Quicktime Pro on Snow Leopard"3x crash service down" Error in CompressorFinal Cut Pro to DVD Studio Pro using Compressor Categories: Compressor Tags: Compressor, Final Cut Pro, Final Cut Studio, Mac OS X, Mac OS X v10.6, Snow Leopard Listed below
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, http://marcoghislanzoni.com/blog/2012/06/29/solved-apple-compressor-fails-with-quicktime-error-50/ 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 https://www.iskysoft.com/quicktime/troubleshoot-quicktime-errors.html 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 quicktime error close Final Cut Pro X after having issued the Send to Compressor command and switched 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 quicktime error 50 Book Pro to 8 GB of RAM). Closing Final Cut Pro X while Compressor still has to render/encode the movie causes it 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 31 Jul 2012 How to discover a new virus or malware 22 Sep 2011 Pencil drawing effect in Powerpoint (any version) 4 Feb 2012 Belkin wireless router frequently disconnecting - SOLVED! 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
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