-
All replies
-
Helpful answers
-
Feb 12, 2011 4:39 AM in response to Arno Peetersby MacReady4U,It's a shame that none of the other workarounds worked for me.
(First major issue for me since starting with final cut in 2001)
If you're looking for instructions about how to remove and reinstall compressor, try here ...
http://support.apple.com/kb/TS1888 -
Feb 15, 2011 2:43 PM in response to Dr Videoby beansontoast,I too have been struggling with this "3 x" problem on and off for about 6 months.
Some of the solutions I have found in the forums have repaired it temporarily but nothing stuck.
Here is a link to an 18 step process that worked for me, finally I can encode with all cores blazing again.
No switching on and off frame controls just works like it should.
Note Compressor was working fine for me but if I tried to use a cluster it would fail.
http://owen-norling.com/stuffandthings/archives/3 -
Mar 16, 2011 2:08 PM in response to beansontoastby ibobi,I don't know if it's of any help at all for you lot, but I experienced the same error and found out that in my case it was related to the frame controls tab, but turning frame controls 'off' and 'on' again did not work. What did work was setting the 'output fields' to 'same as source' instead of progressive. (Not very handy if you want to move from interlaced video to deinterlaced of course).
The sequences were ProRes 422 1920 50p and transcoded to H264 AVCHD 1920 25p, and with these setting mentioned above the error did not appear anymore for at least 10 transcodes up till now.
Regards,
Bob -
Apr 5, 2011 6:52 AM in response to hiproductionsby WilkumStudios.com,Worked for me also: in extras clicked "include chapter markers only"
I had also tried a small snippet of my sequence with a default Apple MPEG2 preset, and it worked fine. However when trying to encode the entire sequence, it failed unless I clicked "include chapter markers only"
I am assuming there is a marker that isn't playing nicely with compressor. I use a lot of markers. -
Jul 20, 2011 10:12 AM in response to Dr Videoby David Mcclain1,Same issue here. I have a short clip (49 seconds) that I have to burn to DVD. Any effort to add AA to the burn process in Compressor results in in a Faile: 3x crash service down.
I've tried turning on 'Include chapter markers only'
No perian installed
Various settings in the Resizing Controls section of the frame controls
So, my solution is just to take the hit and deal with the complaints about jagged graphics. Thanks Apple.
-
Aug 31, 2011 12:37 PM in response to Dr Videoby Brian Semotiuk,Same issue with Final Cut Pro X.
When I wanted to share from within Final Cut Pro and either do the preset renders (like Apple Devices) it would give me that 3x crash service down error. Same if I export to compressor - compressor would fail.
Now if I just share, sent to compressor then it would work and compressor would be fine.
But to fix the problem, I uninstalled Perian (like a previous poster suggested) and that solved the issue - no more errors.
-
Sep 9, 2011 11:08 AM in response to Dr Videoby LisaRobinsonFilms,This problem definitely occurs when the ant-aliasing is on. Why do they give this option when you can't even use it? Turn these controls off and it will compress.
-
Sep 15, 2011 1:26 PM in response to Dr Videoby w.pasman,My latest impression on this issue is that there is a bug deep down in compressor. Sometimes making the tiniest changes can fix the issue or bring it up. I once had it resolved after changing the length of a frozen frame. Another time by changing a few things in the compressor settings. The best I can suggest here is to estimate where in your video the problem occurs and to change that place just a bit...
-
Sep 28, 2011 4:42 PM in response to Dr Videoby qap15,From what i'm seeing, this could be an effect or timeline problem, because it is only through transconding to DVD files that i see this problem. When i use "make quicktime movie" and import the file again as a single file to the timeline the problem is gone, now i can share to DVD or use Compressor.
Compressor has nothing completely to do with this problem, because Share to DVD has the same problem. Something is happening in the timeline.
-
Oct 3, 2011 12:01 AM in response to qap15by w.pasman,But 'share to DVD' probably uses the compressor libraries? And the error message points to Compressor, right?
-
Oct 18, 2011 5:44 PM in response to Dr Videoby vk1kcm,In another post on Macrumours http://forums.macrumors.com/showthread.php?t=847410 it mentions Perian can effect compressor.
I've disabled Perian here and the encode seems to be working now.
-
Nov 13, 2011 1:01 PM in response to vk1kcmby MusicPat,For what it's worth, I found that creating a droplet from within Compressor and using that, as opposed to opening the Compressor, have been the solution for some people, myself included.
This is just for those who uses Compressor in 'stand alone' mode... But I figured it might be worth looking into. It worked for me, and working ever since!
-
Dec 20, 2011 7:37 AM in response to Dr Videoby TeamScottSmith,Lots of efforts here to workaround this issue. Many different things work for different people.
My scenario:
- Anti-alias was always off for me.
- No Chapter Markers.
- No Perian Installed.
- Tried turning on and off Frame Controls. No help.
- Happened on Compressor 3 and Compressor 4.
- Not sending to a cluster.
- Very new computer and installation.
- Worked fine on dozens of other compressions prior to and after this failure.
- Tried trashing Compressor Preferences using Preference Manager. No help.
- Treid the Droplet method. No help.
What did work for me was trimming the head and tail of the video. I was doing a straight compression to ProRes422 from a file, so FCP was not involved. I trimmed a half second off head and tail using inpoints and outpoints in compressor, and it worked.
I think with all of the variety of issues and workarounds, it is safe to say this is a pretty general error that occurs when compressor runs into a problem, and isn't a specific setting. I think there must have been something corrupt in my particular video file. By trimming the head and tail, I skipped over the corrupted part.
Good luck to you all.
-
Oct 3, 2013 8:19 AM in response to Dr Videoby w.pasman,I found that there are crash reports stored in
/Library/Logs/DiagnosticReports/
If we would post the details of crashed threads here we might be able to spot a pattern? The entire report is rather big so we must make a selection I guess. Howe about the creashed thread
Here is one I have currently.
Thread 6 Crashed:
0 libSystem.B.dylib 0x902cff75 usleep$NOCANCEL$UNIX2003 + 0
1 libSystem.B.dylib 0x902f16f0 abort + 105
2 ...pple.compressor.transcoding 0x0083ee98 CreateAudioFFT + 0
3 ...pple.compressor.transcoding 0x0085aa39 M2V::MuxingClient::writeEncodedData(M2V::EncodedData const&) + 811
4 ...pple.compressor.transcoding 0x0084f6ca M2V::EncoderImpl::encode_gop() + 1488
5 ...pple.compressor.transcoding 0x007f7539 stomp::CM2VEncoderWrapper::encodeSequence(int, bool) + 559
6 ...pple.compressor.transcoding 0x007f9ca2 stomp::CM2VTranscoder::run() + 5666
7 ...pple.compressor.transcoding 0x007ec7be stomp::CStompTranscoder::_processRequest(swamp::IServiceRequestRef const&) + 5006
8 ...pple.qmaster.ServiceControl 0x00caed8e swamp::CServiceControllerThread::runOnce() + 2332
9 com.apple.AECore 0x000a0fd4 aecore::CThread::runThread() + 34
10 com.apple.AECore 0x0009e681 threadProc(void*) + 17
11 libSystem.B.dylib 0x90215259 _pthread_start + 345
12 libSystem.B.dylib 0x902150de thread_start + 34
I have some 10 crashes, always having this particular stacktrace pointing to CreateAudioFFT. So this case seems to have a problem with the audio in my video.
Sometimes I get this
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000010
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.apple.AECore 0x0001f2ba aecore::CString::compare(aecore::CString const&, bool) const + 176
1 com.apple.AECore 0x0001f3b4 aecore::CString::operator==(aecore::CString const&) const + 32
2 com.apple.qmaster.JobControl 0x00850cec swamp::CServiceMgr::serviceUnavailable(swamp::IAdvertisementRef const&) + 162
3 com.apple.qmaster.do 0x00665c10 swamp::CServiceManager::sendServiceUnavailableNotification(swamp::IAdvertisemen tRef const&) + 58
4 com.apple.qmaster.do 0x006660fb swamp::CServiceManager::adUpdate(std::map<aecore::CStringRef const, swamp::IAdvertisementRef, aecore::CStringLess, std::allocator<std::pair<aecore::CStringRef const, swamp::IAdvertisementRef> > > const&) + 867
5 com.apple.qmaster.do 0x00654915 swamp::CAdReceiver::updateListeners() + 201
6 com.apple.qmaster.do 0x00657d5a swamp::CDNCAdReceiver::receive(swamp::CAdvertisementRef const&) + 348
7 com.apple.qmaster.do 0x00657fe1 swamp::CDNCAdReceiver::receivedUpdate(__CFNotificationCenter*, void*, __CFString const*, void const*, __CFDictionary const*) + 255
8 com.apple.CoreFoundation 0x97d15aeb __CFXNotificationHandleMessage + 587
9 com.apple.CoreFoundation 0x97d1583e __CFXNotificationReceiveFromServer + 270
10 com.apple.CoreFoundation 0x97cbe702 __CFMachPortPerform + 338
11 com.apple.CoreFoundation 0x97cba46b __CFRunLoopRun + 6523
12 com.apple.CoreFoundation 0x97cb83f4 CFRunLoopRunSpecific + 452
13 com.apple.CoreFoundation 0x97cb8221 CFRunLoopRunInMode + 97
14 com.apple.Foundation 0x9a41a227 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279
15 com.apple.Foundation 0x9a41a104 -[NSRunLoop(NSRunLoop) run] + 76
16 com.apple.qmaster.SwampService 0x006e8fb6 swamp::CSwampService::run(int, char const**) + 2298
17 qmasterqd 0x00003875 0x1000 + 10357
18 qmasterqd 0x00002a22 0x1000 + 6690
19 qmasterqd 0x00002949 0x1000 + 6473
but this seems a higher-level crash where the transcode already failed.
-
Oct 5, 2013 12:51 AM in response to w.pasmanby w.pasman,Regarding the crash in CreateAudioFFT, I believe the problem occurs when the compressor tries to inject an I-frame in an infortunate location. What I suspect is that the AudioFFT can not handle some block sizes (guess: block of size 1). You then often can work around the problem by changing the length of the scene right before the crash by 1 frame.
(you can see where the crash happens by playing back the written part of the video, at least on my computer it often remains on the drive after the crash and VLC can play it back)