Quicktime rendering error

Hi, whenever I render footage with speedgrade, using the H.264 Quicktime setting, the Quicktime player can not open the file up. It always says: 'Error -2048: Couldn't open the file .MOV because it is not a file that Quicktime understands. I don't get this cause Quick Time does understand .MOV files. Thoughts?

I'm guessing you are on Windows. It could be that your QuickTime needs an upgrade. Could you check if you can play the file in VLC?
But, please, when asking these questions it would be very helpful if you gave basic system info like:
- Processior type
- Ram amount
- Operarting system and version
- QuickTime version
- SpeedGrade version
- GPU and possably driver
Jzt

Similar Messages

After Effects CS5 and CS6 Quicktime Rendering Error

Hi there
Recently I have a challenge with rendering in Quicktime output, one day my AE just stopped rendering my videos in Quicktime formats, specially "Photo Jpeg", I had AE CS5.5 on that moment. I shift to CS6 and yet the problem exists. The error number is: -1610153464 and for better understanding here is a screen capture of the error:
I went through all the existing discussion and forums but sadly no one was helpful, I tried evrything and no result. Surprisingly rendering in other formats are perfectly fine and fast, only Quicktime seems has problem.
Please someone help me out here, it just stops me from my daily works and projects, thank you so much.

I shift to CS6 and yet the problem exists.
How can you? It's not even released yet.
Please someone help me out here, it just stops me from my daily works and projects, thank you so much.
Again, how can it? If you are already using CS6, you are either using a prerelease version and discussions about bugs and issues have no place on a public forum or on the other hand you are simply using it illegally. Everything else - yes, that's a Quicktime error, but since you did not provide any more information, nobody can help you. we need to know exact settings, system specs, file storage options, Quicktime version etc.
Mylenium

Rendering error while writing to file...Quicktime

Hi all,
I am brand new here and have an urgent question. I have been getting an error in After Effects CS6 whenever I try to render to a quicktime movie that says "Rendering error while writing to file...An output module failed. The file may be damaged or corrupted."
I have spent days trying to fix this and I have read other peoples posts with the same question but I have cleared my disk cache and reinstalled quicktime without success.
Any help would be great I am not super technology advanced so try to keep it simple if you can.
Computer Specs:
750gb Hard Drive
8gb Ram
Intel Core i5
Nvidia Geforce GTX 660M graphics

Start by going through all of the troubleshooting suggestions here:
http://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime-errors-with-after-ef fects.html
If you need additional help, please provide answers to all of the questions listed here: "FAQ: What information should I provide when asking a question on this forum?"

Rendering Error: CS6 Quicktime crash- error (-1610153464)

Hello,
My employer recently purchased Adobe Suite CS6. I mainly Use After Effects for my job. I have been getting the following error whenever I attempt to render into Quicktime format.:
"After Effects error: Rendering error while writing to file "C:\Users\User1\Desktop\File_Name.mov". An output module failed. The file may be damaged or corrupted. (-1610153464)"
I have searched for solutions to this online. Rebooted my machine after reinstalling the latest Quicktime; deleted queued renders; made sure to switch the compatibility for "AfterFX.exe" to Windows 7. I have also grabbed any recent updates.
One of our clients has asked for files to be delivered in Quicktime format. It would be nice to find a resolution for this issue soon. Thanks for any aguidance with this issue in advance.
I will be glad to provide any machine specs if necessary.

Don't worry, K-Lite did not cause this problem. Dave just likes to blindly blame K-Lite for every problem on earth. This is a QuickTime problem as obvious by the error itself and also by the fact that DaftlyPunkish is getting the same error on MacOS.
Try this
1) Uninstall QuickTime
2) Search the Windows ProgramData folders for left-over QT files such as quicktimepreferences.qtp and remove them.
3) Install QuickTime
4) Make sure that AE and QT are not blocked by your firewall. Test with your firewall completely disabled.

CS5 quicktime "MooV" error - can't render or preview...

Hello everybody,
I'm working on a project with a imported quicktime movie file. The file works just fine in quicktime player.
But... when i try to render the project from AE CS5 i get this error:
Rendering error while writing to file "/Users/etc....
An output module failed. The file may be damaged or corrupted. (-1610153464)
I also get the error saying this type of "MooV" file is not supported.
But like i said it's just a regular quicktime movie....
I allready tried the following:
- re created the quicktime movie from AE CS4 - with different codecs (photo JPG, lossless, animation) all giving the same result
- trashed my AE CS5 prefs
- purged everything
- restarted my mac and AE
playing the quicktime movie in AE CS5 in the footage window causes AE to crash....
I'm running mac os 10.6.3
latest version of quicktime
Anybody had the same issue?
Only solution i can think of now is start over in CS4.....
Cheers,
Tony
Edit - OK i restarted for the second time and now everything seems OK....
Message was edited by: TONYWORKS-NL

The problem is that adobe after effects cs5,
is running at 64 bit and using a 32bit quicktime, this cause
a conflit. An easy way to solve this problem is simply installing itunes 64 bit
have fun

After Effects Rendering error (-1610153464)

I'm trying to render and export a short sequence that I created solely in Adobe After Effects CC. I immediately get the response: After Effects error: Rendering error while writing to file.... An output module failed. The file may be damaged or corrupted. (-1610153464). Not using any external plug ins, tried exporting to desktop and external hard drive. AE version 12.2.1.5, Mac OS X version 10.9.2, Quicktime version 10.3. I realise other people have posted this error before but I'm not using external plug ins, any advice appreciated.

Start here: http://adobe.ly/Uc4dtH

Quicktime -50 Error (New Issue for Me)

I have OS X 10.9 and FCP X 10.0.9
I'm doing a project with h.264 footage that is simple - a talking head in front of green screen, keyed, lower third in beginning, Photoshop PSD still background under. Audio is secondary WAV synced with FCP X's auto sync in Events feature.
I'm doing about 35 of these, each a separate project in FCP X. The events are on a 3TB internal hard drive on my Mac Pro that has about 2 TBs free.
What I'm experiencing is I do one of the projects, render it out using the Apple Devices 720p preset (fast encoding), and it works perfectly. I duplicate that project, change the edit point of the same exact video event, share it and about 90% in it stops and gives me the Quicktime -50 error.
If I duplicate that project (just the project file) and then share it, it renders fine. I delete the other project that gave me the error, and then I continue.
Some give me the error, some don't. It's all the same assets.
I haven't figured out why it gives me this error.
Thanks!

I have OS X 10.9 and FCP X 10.0.9
I'm doing a project with h.264 footage that is simple - a talking head in front of green screen, keyed, lower third in beginning, Photoshop PSD still background under. Audio is secondary WAV synced with FCP X's auto sync in Events feature.
I'm doing about 35 of these, each a separate project in FCP X. The events are on a 3TB internal hard drive on my Mac Pro that has about 2 TBs free.
What I'm experiencing is I do one of the projects, render it out using the Apple Devices 720p preset (fast encoding), and it works perfectly. I duplicate that project, change the edit point of the same exact video event, share it and about 90% in it stops and gives me the Quicktime -50 error.
If I duplicate that project (just the project file) and then share it, it renders fine. I delete the other project that gave me the error, and then I continue.
Some give me the error, some don't. It's all the same assets.
I haven't figured out why it gives me this error.
Thanks!

FCPX Quicktime 50 Error

This just started within the last 30 days or so.
I am getting repeated Quicktime 50 errors when I try to export a project.
The footage is shot using an Atomos Ninja / Samuria using ProRes and edited in FCPX. I have done over 50 videos prior the exact same way and now I have this error which prevents me from exporting my work.
When it first started I completely changed hard drives doing a complete clean install of the system. (minimist install) I have completed two projects prior, now again, I am getting the error.
Everything is up to date, I have attempted to find any corrupt files, of which there are no corrupt files to found. I threw out a quick teaser yesterday, flawless, today the completed project and won't export. I get 19% and it errors.
I have read the posts from the past and nothing seems to work
I am pretty invested in FCPX and at this point it is becoming unuseable to me.

Have you tried everything that's on this list?
Go to Preferences and turn off Background Rendering.
Select your project in the library and in the File menu, click on Delete project Render Files; choose All when prompted. Select your event and do the same with the event Render files. In the project use the range tool to select a short section. Try to export that as a test. Don't render before you export.
If that doesn't work, copy the project and paste it into a fresh project. Try another export test.
If that doesn't work, create a new user account.
Russ

After effects error: rendering error while writing to file. Disk full.

Hi,
I tried to render a video in AE CC 2014, with RGB + Alpha as I wanted to keep the background transparent (rotoscoped) so that I can then use it in Premiere.
I chose to export in Quicktime, with uncompressed 8bit.
After it rendered it for a little while I had a window pop-up saying
After effects error: rendering error while writing to file "E:...blabla". Disk full. The file may be damaged or corrupted. (-1610153463).
I read a thread posted in the forums but i do not understand the solution provided there.. What is a POD??
I have a Win7 Ultimate, x64. Plenty of disk space, and 16 Go ram.
Please help, I canoot go further in my project with this bug...
Jaywaii

Is the drive you are rendering to formatted FAT32 by any chance? If so you can only render up to 4Gb for one file. Try rendering out a TIFF sequence instead. Litte tip - push the LZW compression tickbox in format options for a lossless compression, this will keep you file size way down.

After Effects Error: rendering error while writing to file...Output Module failed - 1610153646

Hi – I’m currently working with someone who is running After Effects 5.5v10.5.0.253 on a PC which is running Windows 7 Ultimate. The computer has just recently been built and the software is newly installed. (ie. a couple of weeks old, max). Up until now, we have been using After Effects with no real issues. But tonight, we started to see the following error message, when trying to render something out:
“After Effects Error: rendering error while writing to file xxxxx. Output Module failed, the file may be damaged or corrupted -1610153646” – displayed during render, which meant the render failed.”
We started to review forums to see if we could come up with a fix and tried a few of the more common suggested solutions, including:
Make sure there are no third-party plug-ins or Windows incompatible elements installed - as it’s a pretty new install, we haven’t added anything except out-of-the box elements.
Clear the render queue – did this, no change.
Reinstall Quicktime – did this, no change.
Reinstall Creative Suite – also no change.
Check the default program to open .mov files is Quicktime – Quicktime was already the default.
A bit more detail about the machine...
Ram is 32gb
GPU is GeForce GTX 660ti
250gb soild states
2tb raid drive
Any help would be much appreciated. This is now happening on all AE files, even files that worked fine earlier in the week. Other than the AE and QT reinstalls mentioned above, nothing new has been added to the machine this week. On a deadline – so a quick response would be amazing, right about now. Thanks.

Hi Mylenium- thx for the quick response. We have have tried a bunch of different settings. AVIs work and we can do image sequences too. The only major problem seems to be with Quicktime files. While I appreciate your suggetion to convert with AME - this is only a workaround. Was really hoping for a solution that will fix the problem in After Effects? Heard rumor from a few friends in the biz, that this is a major bug... if possible, some feedback from Adobe product devs or someone with a technical background would be great! Thx.

Video Rendering Error -50

When ever I try to share my video off of iMovie it says "The share operation has failed, video rendering error -50" I have tried to search up on how to fix this and have found nothing. I am using the latest software update and have iMovie updated. Also I am using Quicktime player which is also up to date. But also even though it says it has failed it puts a 15 second version of my clip on my desktop (only the first 15 seconds of the video) I am not sure if it has to do with any of my settings but I can still not find to how to fix this.

same problem, don't know how to solve it...

HT5148 I am using the trial FCP 10.0.8 and I get a quicktime error when I export to any format I get a quicktime -50 error. Any idea why this could be happening?

Hi, i am using the 10.0.8 trial version and trying to export a simple project to any format and get the Quicktime -50 error. Has anyone seen this before?

Often Times the 50 error means corrupt media. What is your original media and did you optimize?
Try this. Turn off Background Rendering in Preferences. From the File menu, and with your project selected in the Library, Delete Project Render Files. Close FCP and empty the trash. Open FCP and your project, With the Range Tool, select a short section of your timeline. Without rendering, export that section as a Pro Res Master File. If that works, It's likely that your project should be OK to export.
Russ

How Can I Fix A QuickTime Codec Error?

How Can I Fix A QuickTime Codec Error?
I have several movies from 2008 that are labeled as .mov but I now get a QuickTime error saying "The document "XXXXXX" could not be opened. A required Codec isn't available."
These movies ran in QuickTime just fine until about a month ago.
All the folders in which these movies were stored in 4 folders in 2 folders in one folder. All folders at each level were encrypted with Stuffit Deluxe a version circa 2008 and decrypted with a newer Stuffit Deluxe 10.x. Other movies that are NOT .mov and in with the .mov movies still run.
If I click on the Thumbnail Preview "It" runs.
How can I fix this?
TOP image is the Error message.
BOTTOM image is the Thumbnail Preview info.
I've checked out "Tell Me More" and have not found a solution.

How Can I Fix A QuickTime Codec Error?
The basic work flow is to determine which codecs were used to create the non-playing file and then check to see if these formats are supported by your current system codec component configuration.
If the files will open in one of the QT player app, the open the inspector window to see which codecs were used to create the original file as seen here...
or here in the "Format" entry...
Or, if you have QT 7 keyed for "Pro" use, you can open the "Properties" window to gain even more information as demonstrated here...
if you file will not open in either of the QT Player apps, then you can try opening the Finder "Get Info" window for the file,
use a third-party media player that will open the file, or
use a dedicated media information utility to learn this information....
Once you know what codecs were used to create the file, post back with this information so we can deterine if the file should be natively supported by your Mac OS X install, requires an Apple Pro editing codec normally installed by the editor app, or requires a third-party codec which the user must supply.
These movies ran in QuickTime just fine until about a month ago.
All the folders in which these movies were stored in 4 folders in 2 folders in one folder. All folders at each level were encrypted with Stuffit Deluxe a version circa 2008 and decrypted with a newer Stuffit Deluxe 10.x. Other movies that are NOT .mov and in with the .mov movies still run.
Your information does not indicate whether or not the files actually played on the current system or were transferred from a different system which was properly configured for playbac, whether or not you recently upgraded your operating system/modified your codec component configuration by adding or deleting any codecs, whether your compound "Stuffing" of the files created corruption, etc.
As to MOV files the selves, this extension just implies the data was placed in the QT generic file container and the actually data could be of any compression format thathat was compatible with the codec component configuration for the system on which the files were created and could include natively supported system codecs, pro editing codecs, and/or third-party proprietary or hybrid codecs. (I.e., this is why we may need more information regarding the individual non-playing files.)
If I click on the Thumbnail Preview "It" runs.
f you are referring to QuickLook (QL) then the technology is different than QuickTime (QT). In the former case, the system is playing representative data but not actually opening the file as QT does. Thus, there is always the possibility that the problem is in the file structure (atom) information. For instance, suppose someone merely changed the MOV file extension in the Finder rather than actually copying data to a real MOV file container. Then it is possible that the QT player app may be searching for a codec that is not supposed or expected to be supported in the MOV file container and, not finding it, issues the erroneous codec error message—especially since you did not inticate the source of the file you are trying to play or, in some cases, which QT player is now not playing the file.
In short, there are several possibilities here and not enough specific information.

SSRS 2008 R2 rendering error when executing a report

The value '1' is invalid. Valid values are between '0' and '1'. (rrRenderingError)
I am receiving the above error when running the report in SSRS 2008 R2. It has run find in the 2005 version. After research, I read that this issue caused by tablix split on a new page or something. However, I have not found anything to be the resolution. I
installed the latest hotfix that I thought addressed this issue but still not working. Any suggestions outside of touching the report?Sonya

The value '1' is invalid. Valid values are between '0' and '1'. (rrRenderingError)
I am receiving the above error when running the report in SSRS 2008 R2. It has run find in the 2005 version. After research, I read that this issue caused by tablix split on a new page or something. However, I have not found anything to be the resolution. I
installed the latest hotfix that I thought addressed this issue but still not working. Any suggestions outside of touching the report?
Sonya
We too are encountering this problem with reports migrated from 2005 to 2008. We are getting the rendering error only when trying to use the paging controls to navigate forward through the report. This is on SSRS 2008 R2 running SharePoint Integration. When
the result set is empty we get the tablix errors mentioned instead. The reports ran fine prior to migration to SSRS2008.

Portal rendering errors using IE10

Hi,
We've recently patched all of our SAP systems (portal and backend) and checked we're at the requisite level for IE10 support in the PAM.
We're currently in the process of testing all of our applications for IE10 compliance and have identified two issues which someone may have experienced or can advise upon:
Issue 1) SAP Transaction iView (ITS) raising following error in popup dialog box 'The application was stopped due to a critical rendering error. The IE compatibility view is not supported (Note 1586993).'
This iView connects from our portal (EP 7.0 EHP2 SP14) to a backend SAP ERP (ECC) system patched to NW EHP3 (SP09).
Note 1586993 is not particularly helpful as it simply states 'The administrator must assure, that IE frame content is compatible and correctly configured'.
Additional research identified note 1970427 which I have applied to the backend system - subsequently I added application parameter 'sap-ie=EmulateIE8' to the iView (both within the iView config and at runtime) but this made no difference to the behaviour.
I checked the user's framework page and the 'Browser Document Mode' iView is linked in and has it's property set to 'IE=EmulateIE7'. I tried moving this iView further up the order sequence (i.e. putting it first) as well as changing it's setting to 'IE=EmulateIE8' but once again this had no effect on the behaviour.
I notice when logging into the portal, at first the F12 console shows Browser Mode = 'IE10', Document Mode = 'IE5 quirks' but when the problematic iView renders, the Document Mode changes to 'Quirks' which I'm assuming is why the error occurs.
I'm not sure what I can do to make the iView render in 'IE5 quirks' mode?
This iView is called dynamically at runtime with some URL parameters that are passed to the backend transaction so I cannot follow the advice in note 1590563.
Issue 2) BSP iView for 'CRM Web Interaction Centre' - all F4 dialog popups are displaying empty with no content, e.g. Inbox search help for classification field
This iView connects from our portal (EP 7.0 EHP2 SP14) to a backend SAP CRM system patched to NW EHP2 (SP04).
I tried setting my user parameter CRM_THTMLB_IE_COMP to 'IE8' but this had no effect.
Note, if I set the IE10 property 'Display intranet sites in Compatibility View' both issues above are resolved. We're trying to avoid this as we've had this setting in place for a number of years and it affects the correct operation of non-SAP applications. Given there are numerous ways of making SAP operate by emulating older compatible IE versions, I expected we could work around needing to do this but it may be a last resort.
Please offer any advice you can as it will be much appreciated.
Thanks,
Alan

Hi Lawrence,
We have a mixture of custom and SAP standard portal applications developed over the past 10 years.
UI technologies include: Java Server Pages, Web Dynpro Java, ITS, BSP, Web Dynpro ABAP and BEx.
Quite honestly, the portal hasn't proved to be the best SAP product in our experience, and we've tried hard to keep it patched up-to-date. OK, it offers integration and navigation but that capability is offered by the Fiori Launchpad, albeit presenting new challenges and possibly some limitations on the integration of existing applications.
We could have opted to integrate the Fiori Launchpad with the portal but decided it was cleaner to perform a standalone installation on our newly built NetWeaver Gateway server.
We're starting our Fiori journey by implementing selected SAP delivered apps for the first pilot projects then plan to replace or migrate existing portal applications.
We'll replace any custom Java apps with UI5 apps built in-house as we need to rationalise UI technologies and this one is a prime candidate given the lack of in-house skills and SAP direction.
Our expenses application is currently an SAP ITS transaction iView in the portal but will be replaced with the My Travel and Expenses Fiori app this year.
CRM Transaction Launch isn't used often so we may kill it off.
BSP's are solely in the CRM area and I read they're not supported yet in the launchpad - hopefully they will be in a future version (?).
We have quite a few Web Dynpro ABAP applications so these will take some time to rewrite if required (assuming we cannot port them).
BEx may be replaced with Business Objects or taken out of the portal in favour of the Excel version we also run (portal offers little value for massive reports so users download to Excel in any case).
My understanding is that the Fiori Launchpad does support integration of legacy SAP technologies so we'll need to gauge if and when we each a tipping point where any remaining portal applications can either be integrated with the launchpad or replaced with alternative new applications. Obviously all of the above will take time.
We're working on developing a custom Fiori/UI5 theme and have hit a few snags. We've just patched to SP09 on our development Gateway system but the UI Theme Designer is still a bit flaky (we run the tool there but could also do this on our portal). My colleague is now trying the cloud version to see if that proves a more viable route. In either case we'll be seeking SAP assistance as we really want our UI5 apps to adopt recently developed corporate branding rules. Our portal currently uses a copy of Gold Reflection with simply the SAP logo replaced for our company's logo.
If you have any further queries just let me know, or similarly advice/experience on the above.
Hope this helps.
Alan

Quicktime rendering error

Similar Messages

Maybe you are looking for