MPEG 2 failure on compressor export

I Have recently changed from using single layer DVD to dual layer DVD and I've got some great results Using the send to compressor route and changing bit rates to suit.
however after about 4 successful projects burnt to DVD I'm now getting failures on all the mpeg2 ( video ) during the compression process from FCP 7 to comp 3.
the AC 3 audio comes out fine but every time the. Video is now failing and I can't see why.
MY route is this:
1. Export using send to compressor in FCP 7.
2. In compressor I select preset apple DVD 150 mins all
3. I then select video file and change max & min bit rates to 7.2 & 5.5.
4. Submit.
audio takes about 25 mins to complete and video fails every time.
cant work out where I'm going wrong as the first 4 projects were fine, now nothing !
dont want to go back to 4.7 GB's discs as the quality is so much better with dual layer.
can anyone help with this strange problem?
these are wedding DVDs and are both 2 hr 30 mins long roughly
thanks in advance

In order to troubleshoot, first, fully render your sequence in fcp, then export a selfcontained quicktime with current settings from frcp (file: export: quicktime movie NOT quicktime conversion) and bring that file into compressor. This will hopefully help isolate the source of the problem.
The other advantage of using this workflow is that you can enable qmaster to greatly speed up the processing time in compressor
http://www.digitalrebellion.com/blog/posts/using_compressor_with_multiple_cores. html

Similar Messages

MPEG-2 Fails in Compressor

I have searched the forums long and hard and have been unable to find anything regarding this problem. I am creating a short 2 minute HD video that involves exported (QT - Animation 1920x1080) motion files and still images (I have tried TIF, PSD and even JPEG) and Cross Dissolves. Nothing more. I have been making similar projects involving the same material just different content for about 6 months now with no problems. But now I am having a consistent problem and constant failure when exporting.
My Sequence settings are Apple ProRes 422 (HQ) 1920 x 1080 29.97 fps with Square Pixel Aspect. Everything renders wonderfully and exports wonderfully using any other format but the MPEG-2 Program Stream in Compressor. Unfortunately this is the format I need for our video productions playback for HD material. I'm almost positive the problem is within Final Cut because I have even tried exporting as a stand alone QT File and dragging into Compressor. I have even tried using MPEG Streamclip to convert my exported QT File to many different formats before using Compressor to do the MPEG-2 conversion. Every time in Compressor it says it failed with the log error 3x crash service down: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<services></services>
Any insight on to what is occurring would be helpful, its just so weird that it only has this fail log when I convert it to MPEG-2 Program Stream. I am already exploring other formats that may work with our video production team.

Has the trial for After Effects CC expired?
You are allowed to launch After Effects CC one time after the 30-day trial period has expired, but when you do so a a bug exists in this state: MPEG2 files can not be read or written.
The only solution for this bug is to license After Effects CC; ex. purchase a subscription. My apologies for the problems you're having with the payment system. As Rick says, please contact customer support for help with this.

Can I use Final Cut During Compressor Export?

Hi,
This is my first time using compressor and I'v read that you can use Final Cut while Compressor exports. When I start to export from Compressor, I get a message on Final Cut that says Frame X (what ever frame the export is on) and I can't use Final Cut when Compressor is exporting. I have rendered everything in Final Cut's timeline. Can I use Final Cut while compressor exports?
Thanks,
Zevie

Zevie,
You would not lose any quality. You will speed things up considerably.
To set up compressor to use all your free cpu, you need to enable sharing with qmaster. On your system preferences, there should be a qmaster item.
There are lots of posts about how to set it up. Do a search on it. I think even apple has instructions on how to do it. You can read the compressor manual as well.
It is called distributed processing, and you will want to set up a quick cluster.
Here is an article about it. The only thing that I know is different is on Snow Leopard, you may have to select "Managed" in the services box for compressor. This will allow you to select the number of instances.
http://www.devia.be/news/article/setting-up-a-virtual-cluster-to-speed-up-compre ssor/
Good luck
Ken

3x failures on Motion exports to Compressor

Does anyone else have issues with Motion projects failing to export through compressor??? I find that 2/3 of my projects just wont ever export through compressor. I can always do it through a direct export from Motion.
I typically have my project set up in DVCPROHD720p24 and will export as the same or as Animation codec for alpha channel.
The projects are typically 30-60 seconds long and have no major sizing issues. It just seems that this is always an issue I hit and my work-around is always to have to direct export. It works fine, but MAN it totally messes up my workflow.
Message was edited by: Adam - Trigger Studios

FYI : New info shows that this only happens when exporting my motion sequence through compressor using DVCPROHD.
There seems to be an issue with this preset. An odd quirk is that I lowered the gamma to .9 and it seems fine. Anyone???

Pixelated reds in MPEG-2 (and most other) exports

This is a revisitation of an issue I identified over a year ago and I still don't have a resolution. I am going to cross-post this to the Quicktime forum as well as that of FotoMagicko. I would do so at Photo-to-Movie as well if they only had such a resource. I am desperate for new ideas or techniques to try. I would be pleased to no end to be told of a simple error in my process, but I'm beginning to suspect that Quicktime is broken.
The original and still biggest problem is heavily pixelated reds in MPEG-2 movies. Turns out it exists in most other QT formats as well.
I'll step you through the workflow and then discuss observations gleaned from a number of experiments:
We start with hi-res photos and render them as motion slideshows. We have done this in iPhoto, FotoMagiko and Photo-to-Movie all with the same results. All of these applications utilize quicktime as their rendering engine and so are really irrelevant as a possible source of the problem (as will be verified later). QT does not support export directly to MPEG-2 and so an intermediary file format is required. More on this later.
The rendered QT file is then dropped into Compressor and rendered as 2-pass 8 Mbit max VBR (have also tried 8 Mbit CBR with no improvement). The resulting MPEG-2 is then imported into DVDSP4 for authoring.
The resulting DVDs all show heavy pixelation in reds.
Well the problem is out of gamut reds in your source files, obviously I hear you say.
OK, so back to the beggining - this time run all images through Photoshop's NTSC Colors filter and rerun. Same problem. Have also done this AND converted to NTSC color space - no joy. I have even ASSIGNED the NTSC color space to the image instead of converting - this munged up the colors to know end, but also did not fix the problem.
Well, maybe MPEG-2 is just not capable of handling even all of NTSC's colors, right?
Seems unlikely, but maybe. What about this then - of all of the Quicktime codecs to which to export the slideshow movie, only 1 of them produces an intermediary file that does not ALSO show the pixelated reds - the Animation codec (not Apple Intermediate, not Component, not MPEG-4, not eve Uncompressed at either 8 OR 10 bit!). Again, these are with source images whose gamut has ostensibly been reigned in to legal colors via Photoshop.
Well at least there's ONE intermediate that produces a flawless export - just use that
Ok, except that once Compressor is done with it (and I've tried every reasonable combination of parameters), the pixelation is back.
I've seen broadcast video showing these colors (or a representation of them) without this kind of artifact - how is it accomplished? About the only thing I havn't tried is importing it into Final Cut and trying to figure out their chromometer thingy. How would this differ from the NTSC Colors filter in Photoshop. That still wouldn't explain what appears to be a problem with the majority of Quicktime's codecs with saturated reds...
Any help, advice, or even guesses are appreciated.

The internet, as always. is your friend:
http://www.google.com/search?q=4:2:24:1:14:2:0&ie=UTF-8&oe=UTF-8
The 1st and second links are pretty useful. It describes how chroma (colour) is stored a lower resolution to luminance (black and white) to save space. Photos don't employ this type of colour compression, which is why they look so different when out in a video codec.
By going via NTSC DV, which is 4:1:1, to DVD MPEG2 which is 4:2:0, you end with a combination of the worst aspects of each, namely 4:1:0, which is why the MPEGS look so bad. However, you will always be limited to some chroma down-sampling with most codecs.
Bringing the photos into FCP will give you more control - but will probably be a royal pain to get them to do what you want - I would exhaust all possibilities with the packages you are already using.
What is your final out put (sorry - I skimmed you post) - DVD ? Have you exported to that and seen how it looks ? It might be okay.

Compressor exports for Bluray

OK am in danger of getting totally confused.
I'm editing HDV footage ( 1440x1080i ) in FCP by importing it as Pro res at the same dimensions, 1440x1080.
Having edited the footage I send it to Qt at the same dimensions 1440x1080 so I can impoprt it into Compressor to make mpeg2 files for Bluray..
In QT properties, QT reports that the 'actual' size of the exported Prores QT file is 1888x1062.
Now I understand that this difference in dimensions is simply because QT is using square pixels to display the actual rectangular pixels of HDV and that QT discards 'redundant' pixels to reduce the dimensions from what they should be, 1920x1080, to 1888x1062.
OK so this could get really confusing but I think I'm happy in understanding it but here's where it gets even more confusing.
I import the 1440x1080 Prores QT file into compressor to make an MPEG Elementary Stream and when I preview this in QT it tells me that the dimensions have changed again to 1440x810 pixels??
What else is going on here?
What's the point of having Full HD at 1080 vertical lines of resolution if the Bluray file is discarding 210 lines of resolution by default. Is compressor discarding these by default. I don't believe I came across an option to reduce my 1080 resolution to 810 whn using compressor. I'll do it all again just to scrutinize it but I'd be interested in some experienced users comments.

Got it.

Multiple Failures with Auto Export Private Preview for one DB

My Customer has received 7 failures so far this month for their daily exports for a specific Database. While they understand this service is in private preview,
this failure rate is abnormally high from their experience with this service and the Customer is asking for Microsoft to investigate. They are not experiencing this same failure rate on any of their other production DB exports. The
error logs show the following:
Start Time: Saturday, July 05, 2014 2:08:01 AM
End Time: Saturday, July 05, 2014 2:29:50 AM
Subscription ID: <SUB ID>
Server Name: <SERVER NAME>
Database Name: <DATABASE NAME>
Operation Name: Export
Operation ID: e8f916a6-838d-457c-be3c-83257b7c039b
Status: Failed
Details: Error encountered during the service operation.
Could not connect to database server.
Cannot open database "<DATABASE NAME>" requested by the login. The login failed.
Login failed for user '<DB ADMIN USER>'.
This session has been assigned a tracing ID of 'ebc9b95b-e777-49b1-82d8-064549c6fe95'. Provide this tracing ID to customer support when you need assistance.
Can we please have an Engineer supporting the Auto Export Private Preview review this matter and the error logs further to help us understand if the multiple failures are considered
normal or high?
Thank you,
Frank Ellero
Frank Ellero - Microsoft Corporation

Hi,
The error you have mentioned points to the connectivity issues to the database.Please have a check on the below link for more information:
http://social.technet.microsoft.com/wiki/contents/articles/1719.windows-azure-sql-database-connectivity-troubleshooting-guide.aspx
http://support.microsoft.com/kb/2980233/en-us
If the issue persists, I would recommend that you have a
Technical Support Ticket opened as it would require dedicated troubleshooting.
Regards,
Mekh.

Avid Format Compressor Export for Pro Tools

Pro Tools now has support for Avid Media Files - to play out their I/O Box - The Mojo. Unfortunately, they have to be in a proprietary format; near as I can tell, MXF, AAF, or OMF.
I can DL the Avid Codecs, and Compressor can use these, but is there a way to export from Compressor in an OMF, MXF, or AAF Format?
Thanks!

I have always found that a simple .dv file is the most user friendly in a ProTools Suite.
I use these in conjunction with OMF exports of audio and it works flawlessly.
I am on a PC so not sure how that impacts in your Mac workflow.

MPEG STREAMCLIP: I need Exact export settings please...

Does anyone have the correct settings for exporting Via MPEG STREAMCLIP. I know that there is a H.264 and MPEG-4 option in the codecs. I DO NOT want to use the 640x480 iPod settings since there is resolution loss from the DVD's.
So what setting and bit rates would I have to use to crate a video file that is playable in AppleTV without having to go through QT Pro. I know I can encode a 720P file (and I will do that so I don't lose resolution), but is there anything in between the two taht Apple TV will play at 24P. Threre is a 950x540 but is says at 30 FPS.

How do you determine the proper crop values? I'm used to using MediaFork, which crops for you.There are basically two strategies:
1) Ensure that the file is displayed at it's proper aspect ration and then crop out what you don't want. That which remains you keep and convert to your target format.
2) Decide what the target aspect ratio is supposed to be and then crop/scale the file so it will meet those requiements.
In addition, there are differing strategies in determining encode/decode efficiency as a trade off for the accuracy of your aspect ratio. MPEG Streamclip, for instance, sacrifices encode/decode efficiency for exactitude in aspect ratio while MediaFork/HandBrake is just the opposite. Ex. Streamclip will allow you to create a 720 x 405 (16:9 or 1.78:1 aspect) while MediaFork or HandBrake would default to 720 x 400 (1.80:1 aspect ration). Since 720 and 400 are both evenly divisible by 16 but 405 is not, the MeadiaFork/Handbrake application would likely conver slightly faster than streamclip with all oter factors being the same. But, the Streamclip file would have the more accurate aspect ratio for scaling by TV or your HDTV.
As to actually entering the settings, you must first decide which strategy combination you plan to use. If the movies containg scenes which are display smaller than other scenes, scrub the play head to that location and set "in' and "out" points for tests. At this point you mst decide which strategy combination you plan to use before proceeding any further.
a) In the first case, simply tick the Streamclip "Crop" option and enter estimated valus. Now press the preview button and preview the output. If not satisfied, abort the preview and modify your entries. Repeat these steps until you are satisfiled. Do this for each movie as it is common for each to be centered differently or be of a slightly differeing size.
b) In the second case, you must now determine your target dimensions. For instance, lets say you have a movie which is specified to have a 2.35:1 aspect ratio and plan to export it at a width of 854 pixels. In this case, Streamclip has probably defaulted to an 854 x 480 (16:9) screen setting in your work area. However, your movie displays with a black "letterbox" top and bottom. To calculate a proper height for you movie at this width, simply devide 854 by 2.35 and you should get an answer between 363 and 364. If you plan to go for a "most accurate" aspect rato, then simply select the "Custom" display option and enter a width of 854 and a height of either 363 or 364. Now tick both the "Crop" and "Scale" Streamclip option and process as described above. Simply enter your crop values and previed the result. In this case however, ther cropped picture will always be rescaled back to the "Custom" display size you specified for your output.
While values will be different depending on which workflow you elect to use in paragraphs "a" or "b", the final displays should by approximately the same. In the first instance, the final output will be determined by the total amount of "overscan" included in the original content over and above the aspect ratio while in the second instance, the overscan will be scaled to fit within the aspect ratio you specified. This may sound confusing at first, but the principals and procedures are quite simple in practice once you get used to applying them.

"Catastrophic Failure" trying to export from Crystal Reports Explorer v10.5

In using Crystal Reports Explorer v10.5 (add on to Crystal Enterprise v10) I am trying to export just over 211k records to MS Word.
The data is coming from a Business View (created in Business View Manager) that uses an OLEDB connection to an Oracle database.
I get the following error message:
CrystalReportVIewer
Error caught in ICrystalReportGridViewerImpl::render
webReporting.dll '0x80004005'
Catastrophic failure
line: 16031
I have no idea what's causing this or how to resolve it. Can anyone assist? Thank you!!
Edited by: AmberDoreen on Mar 21, 2009 2:03 AM

No - it doesn't work with any of the viewers and the same error occurs. I think we've determined that it's due to the amount of data and the % of resource allocation in order to export the results. The query behind the data is pretty complex, and the Oracle views that are being accessed are also pretty beefy. It's just a huge hit on resources. I've advised my client to provide more filters & reduce the amount of returned rows to see if that clears things up. I'm waiting to hear if they are successful. Thanks for responding, though! I'll update once I hear from the client.

Workaround for too-dark Compressor exports

I've seen a few threads here about video exported from FCP X (Share->Export Media...) then opened in Compressor being noticeably darker (both viewing and exporting). I started noticing the same thing about two months ago. I've tried tweaking the Gamma, Brightness, and Contrast settings when exporting from Compressor but have not found the magic combination to just retain the same look as in the FCP X timeline. Someone mentioned using Share->Export Using Compressor Settings... as a workaround - and it works! The videos come out looking the same! So far, so good.
However, there is one glitch. My Custom settings created in Compressor aren't available in that menu in FCP X. It shows the Custom folder, but says it has 0 items, when it really has 7. I CAN successfully use those custom settings from within Compressor itself. My understanding is that those Custom settings are supposed to be available from that menu - any ideas as to what would make them not accessible?
Thanks

I've seen a few threads here about video exported from FCP X (Share->Export Media...) then opened in Compressor being noticeably darker (both viewing and exporting). I started noticing the same thing about two months ago. I've tried tweaking the Gamma, Brightness, and Contrast settings when exporting from Compressor but have not found the magic combination to just retain the same look as in the FCP X timeline. Someone mentioned using Share->Export Using Compressor Settings... as a workaround - and it works! The videos come out looking the same! So far, so good.
However, there is one glitch. My Custom settings created in Compressor aren't available in that menu in FCP X. It shows the Custom folder, but says it has 0 items, when it really has 7. I CAN successfully use those custom settings from within Compressor itself. My understanding is that those Custom settings are supposed to be available from that menu - any ideas as to what would make them not accessible?
Thanks

Does Compressor export to HTML5?

Does Dreamweaver and Compressor 4.1 export to HTML5?

https://developer.mozilla.org/en-US/docs/HTML/Supported_media_formats
Of the format options listed here, Compressor will export MP4 h.264.
Russ

"Catastrophic failure" exception on export...

Hi,
I am working on .Net application that uses CRXIR2 embedded server as a 3rd party reports application.
I am trying to run a report based on a stored procedure, and got this "catastrophic" exception:
Catastrophic failure at CrystalDecisions.ReportAppServer.Controllers.PrintOutputControllerClass.Export(CrReportExportFormatEnum exportFormat, Int32 Reserved)...
ErrorCode = -2147418113
when i run:
crystalBytes = reportClientDocument.PrintOutputController.Export(ConvertToCrysalExportFormat(format), 0);
I tried looking up this exception and error code, and all i got was somethong related to SQL server 2000.
I'm using SQL server 2008...
Also, when running other reports based on database views, the reports ran successfully..
Does anyone have an idea?...
Thank you,
Dana.

Hi,
I think I've found the problem.
I changed my stored procedure parameters, from int to bigint.
I ran the report in the designer, using the new stored proc - it worked ok.
when i run it using RAS, i first set parameter values using :
reportClientDocument.DataDefController.ParameterFieldController.SetCurrentValue("", parameter.Name, this.logId);
where logID is of long datatype.
when i change it to int, i don't get the exception.
Is it not possible to set a report parameter value to long datatype?

Quicktime export (fast) vs Compressor export (slow)

I have an 8 minute ProRes file at 1920 x 1080. It takes about 20 minutes on my machine If I export this as a full res 1080p H264 file (10 Mbps) using Quicktime 10.1. Why does it take 2 hours, with the same setting using Compressor 3.5.3?

Name: H264 1920 x 1080 @ 10Mbps
Description: H.264 video with stereo AAC audio. Settings based off the source resolution and frame-rate.
File Extension: mov
Estimated size: 4.61 GB/hour of source
Audio Encoder
          AAC, Stereo (L R), 48,000 kHz
Video Encoder
          Format: QT
          Width: 1920
          Height: 1080
          Pixel aspect ratio: Square
          Crop: None
          Padding: None
          Frame rate: (100% of source)
          Frame Controls: Automatically selected: Off
          Codec Type: H.264
          Multi-pass: On, frame reorder: On
          Pixel depth: 24
          Spatial quality: 75
          Min. Spatial quality: 25
          Temporal quality: 50
          Min. temporal quality: 25
          Average data rate: 10.24 (Mbps)

FPC 5 compressor exporting problem--like 4.5 feature better.

I am doing a batch export using fcp 5. I never used compressor before, liked the 4.5 way of exporting, but since I need to use mpeg2 for DVDSP-i have no other choice that i know of. Anyways, I am doing the batch export using compressor. Im using the same settings as i did using batch export in 4.5 (two bypass, sliders set to 5 and 7 for good quality). But now its taking 2 full days to rendor what normally takes an overnight job to rendor 1 hour 20min video. What am i doing wrong? Also, I tried to reinstall 4.5 and it would not install it full. AND, if i do reinstall 4.5, will a .fcp version 5 open in version 4?
Thanks,
Tony
g4/933 mhz quicksilver desktop Mac OS X (10.4.6)

Some would say the quality is better the way you do it (hanumang, e.g., I think), but try exporting as a referenced QT movie, then start Compressor directly and feed it the QT file. It's a lot faster. Maybe you could do a quality comparison and report back.

MPEG 2 failure on compressor export

Similar Messages

Maybe you are looking for