Motion Generator - Cross Dissolve Changes Speed
Wow, this software is really, really buggy.
I have a simple sequence I created in Motion 5 and published as a generator. I bring it in FCP X and it's at about 60% size (already created a thread about that). I just do a Transform and enlarge it to work around this bug.
The new bug I just discovered is when I add a Cross Dissolve transition to fade out the Motion 5 sequence, it makes the timing of the Motion 5 sequence a lot faster. So the zoom blur treatment and the text animation sequence from Motion 5 get sped up about 200%.
Anyone else getting this?
Thanks!
OK, so it appears that what is happening is if you trim a Motion generator in FCP, it retimes it so that all of the sequence happens in the shorter time, since you have cut it, versus elimating anything in the sequence that happens beyond where you trimmed.
So does this mean I have to go back to Motion to do a simple thing like trim a Motion sequence? If so, what is the point of merging Motion sequences with FCP X footage? It seems it would be easier to just take all the footage into Motion and then export that out as a QT ProRes movie and import that (like I did with AE back in 1995).
Thanks!
Scot
Similar Messages
-
Reverse Speed clip with Cross Dissolve Causing jumpy video
Hi,
I have encounter a strange promblem when add Cross Dissolve Between 2 clip that the speed of them is changed.
the first clip is 50% , the second is -50% ,both of them have Frame Blending.
during the transition the playback is jerky (evan in the export), my field order of the sequence/Footage is Lower Filed (DV PAL 4:3).
withou the Cross Dissolve it play fine.
i have checked with diffrent footage and stii i have the problem .
any idea ?System spec:
Asus x58 P6-Delux
i7-950
12GB RAM(1600Mhz)
1 System drive 500GB
1 TB (RENDER+Project)
2X1TB Raid 0 (For Footage)
Nvidia GTX 570
OS win 7 64 bit (Professional)
PrPro CS5 (5.0.3)
Media Encoder 5.0.1.0
NO Extended Desktop (1 Display)
Project Setting : DV PAL (4:3 1.097PAR) 48Khz Lower Field First
Footage :20 Min DV PAL 4:3 1.097PAR 48khz Lower Field First
All Driver are update (cheked at the manufactor website)... -
Cross Dissolves dont work on Variable Speed clips?
Whenever I add a cross dissolve a the end of a clip with variable speed the dissolve doesn't work. Any reason?
A workaround:
1) Put your variable speed clip on V1
2) Overlap the incoming clip on V2 so there are the same number of frames of overlap as the desired length of the dissolve
3) Using the Pen Tool in the Timeline, add two Opacity keyframes to the clip on V2 and, placing the first KF on the first frame of the clip, ramp the Opacity up over the number of frames of the desired dissolve
4) If you need the clip that is on V2 to end up on V1 for further editing in the Timeline, create an Add Edit in the clip and Shift-drag the second portion of the clip down to V1 so it doesn't change its horizontal position in the Timeline -
How to change cross dissolve alignment in PP CC 2014??
I've updated to Premiere Pro CC 2014 and now I can't change the alignment on my cross dissolve from the effect controls panel - or anywhere else for that matter. Is that function gone in 2014?? Or did I miss something?
Screendump from the effect controls panel:I dont understand this part ( what am I missing?)
'm looking to keep the length of the dissolve and skip ahead or rewind with each clip
but ...
This method only changes the length of the dissolve one end at a time
Dragging the Transition Box in the Timeline works like this.
Drag one end and the total duration extends or contracts.
Shift Drag either end... affects that end only.
Drag in the middle of the box ..repositions (off centres) the transition (Assymetrical).
All adjustments are shown in a Info Box overlay. -
Cross Dissolved Motioned Slideshow Image "Jumpy"
I am working on a slideshow, and as I've done in the past, followed Tom Wolsky's Motion Control suggestions. ( http://www.fcpbook.com/MotionControl_inFCE.html ) The motion on the pictures looks great - except during the cross dissolve transitions. The image becomes "jumpy," kinda like when you import VHS video. The filters I've tried are: De-interlace, Flicker Filter and Stop Motion Blur, and they didn't help.
The photos are scanned jpg images at 400dpi. If I remove the motion, the pictures look fine with the cross dissolve transition.
I have exported the video and using iDVD made a movie, hoping it just looked that way on my monitor. Still jumpy on my sweet standard definition TV.
Render Control framerate and resolution are at full 100%. And this is just a standard definition sequence.
I need this for a wedding for a friend for next Saturday, so I'm sweating here a little. Slideshows like this have always worked for me in the past. Am I missing something?
DaveDavid - They are all checked, and then running the render again doesn't render anything new.
Searching around Google, I found this "solution" which appears to work. It's tedious, and I'm having trouble believing that everyone else can add motion and transitions, and it works fine. Or do other people really have to do this when keyframing:
(excerpt from http://forums.creativecow.net/thread/8/967086#967094)
+If you re-position graphics or any video image in FCP, make SURE the VERTICAL setting for each KEY-FRAME (start, stop or hold) is always a EVEN INTEGER (Even Whole Number). Examples: 4, not 3 / -144, not -143.27 / 336, not 335.62 / 12 not 11.+
+The positioning settings/info (as well as many other settings) are found under the "Motion" tab in the Viewer.+
+Vertical position is the number in the RIGHT window in the area called "Center" (the horizontal position is displayed in the LEFT window).+ -
I can't change the length of an cross dissolve in iMovie
I can't change the length of a cross dissolve in iMovie 10.0.1
I do the right things but 1.0 second stays 1.0 second
Who has the solution of this problem?»Pass Through« indicates that Adjustment Layers will affect lower Layers outside the Group and that contained Layers with different Blend Modes will affect Blending with underlying Layers outside the Group accordingly.
If you change it to Normal or any of the other Blend Modes everything contained within the Group will basically act as one flattened Layer and Adjustments only affect the Group’s pixel content.
Could you post a screenshot of the document with the Solid Color Layer’s Color Picker and the Layers Panel visible? -
Premiere Pro CS 5.5 can't do a simple cross dissolve with MPE enabled?
When adding cross dissolves to a project that I'm working on, I've come across an odd problem. I say odd because this should be dirt simple, but Adobe seems to have messed this up. Please advise on any solution or work around, or perhaps simply see if you can recreate the issue so we can get Adobe to fix this.
Problem:
Cross dissolves transitions don't seem to work consistently in cs 5.5. Note: I know how transitions work, and I'm not doing something stupid like trying to apply a transition to a cut without actually removing any video between the two clips (assuming the clips came from the same source video.). I'm able to recreate this issue on two different systems with premiere pro cs 5.5 by doing the follwing:
Create a new project and and sequence with the default settings.
Enable the Mercury Playback Engine if it isn't already enabled.
I import the Wildlife.wmv video that comes default with Windows 7 systems.
Drop it the video into the sequence.
Ripple delete about a 2 second section of the video. be sure to do this in the first half of the video, and make sure the the video changes the scene during this period so that you will notice the cross dissolve transition when it is applied.
Apply the default cross dissolve transition to the edit.
Review the edit. For my test, this edit always seems to work fine.
This is a screen capture of the working cross dissolve transition.
Now let me show you what happens when I do a similar edit somewhere in the second half of the video clip.
As you can see, for the duration of the transition, only the clip to the left is shown. At the end of the transition effect the program out preview jumps to displaying the clip to the right. There is no transition.
Additional notes:
This second transition works fine with MPE disabled, but because if of my other problem http://forums.adobe.com/message/3725642 that I have with MPE disable it is not a viable work around.
Help?
-TedI too am experiencing this issue. AVCHD footage, GPU Acceleration, trying to apply a cross dissolve, and instead it randomly seems to see it as a simple cut. The Cross Dissolve is simply ignored... Adjusting the footage length, removing the CDissolve, re-rendering, etc. have no effect. For whatever reason, in that specific location on the timeline, a cross dissolve with GPU acceleration is impossible. Yet, in other sections of the timeline, it is just fine.
(The Fast Blur trick mentioned above worked (Thank you!) however, when I changed my playback resolution on the screen display, that broke the fix. Deleting the fast blur, and applying it to the clip on the other side of the cross dissolve, re-enabled the work around)
I also see an issue when a clip changes in the timeline, (cut from one piece of footage, to another) the video will begin to studder, dropping frames. Framerate seems to drop to about 2fps. To get smooth playback back, I have to pause and resume the playback. Even if this is done very very rapidly, it still fixes the playback issue. it's just really annoying to have to constantly stop and resume playback everytime a video clip changes in the timeline.
I have a dedicated hard drive for video, and a dedicated mirrored array for the OS. the video drive is a 7200rpm SATAII drive, and I'm using AVCHD footage. I really don't think it's a disk speed issue... particularly as pausing and resuming (even if you do it as fast as you can possibly hit the keys) fixes it. I'd rather not spend the $ to set up a RAID 10 for video, if I can avoid it and particularly if it's not needed.
-Jason -
Please, I need help with cross dissolve!
I've posted this before with no replies and I've done a ton of research online trying to find an answer for this problem, with no luck. Surely I am not the only one having this problem with iMovie! When I put in cross dissolves in a movie, some of them are jumpy and have visual flashing and stuttering between clips. Does anyone know why this is and what I can do? I am pretty stuck with my projects until I can find a solution. Any help would be appreciated!
In a codec like h.264, it achieves compression by shooting 1 full frame of video. This is followed by 24 or so partial frames which contain information like what has changed since the full frame, the direction of motion, etc. This is called a "Group of Pictures" compression. This compression is great for playback, but is difficult for editing.
For example, in a cross dissolve transition, it needs something like every other frame to create the transition. In a compressed format, all these frames do not exist. They have to be calculated. If you optimize the video clip, all the grames will be converted to full frames, and the cross dissolve can easily get the frames it needs without a lot of calculations. -
Compressor adds digital artifacts on cross dissolves
Hi can anyone help me?
I have exported a sequence (10-Bit Unconpressed PAL, Upper) using the compressor preset DVD Best quality, 2 pass, VBR.
When i play the exported M2v, some of the cross dissolves seem to have some kind of digital artifacts in the middle of the dissolve taking place (which is not there on the source material on the timeline in FCP 5)
can anyone help me?
Cheers, SimonSimon, I had the same problems. Export as quicktime self-contained, include DVDSP markers and DON'T check the recompress all frames box! Including the DVDSP markers makes sure the compression markers are exported as well. It makes sense to insert and name DVD chapter markers as well in FCP, as they will be included in the mv2 file you eventually import into DVDSP.
Then import the quicktime into compressor, and create a new preset that is 1-pass, NO VBR, 7.2 bitrate, motion estimator BEST. If you drag your movie into the preview window you can see all the compression markers that FCP automatically included, as well as the chapter markers (different color).
Submit the job. You can compress the audio to AC-3 the same time as you compress the video by adding the Dolby 2 function to your new 1-pass preset. All your audio must be 48K 16bit in FCP before you export, or it will go into the center channel on 5.1 sound systems.
Import the finished m2v and audio files into DVDSP. Notice how your chapter markers you inserted in FCP magically appear! Do your menus and buttons etc., then build the job. I don't use build/format as I have had better luck just dragging the master build folder that contains the VIDEO_TS folders into TOAST 6 and burning it at 1X DVD setting just to be safe.
All my previously artifacted movies, which are heavily effected with lots of transitions. NOW HAD NO ARTIFACTS WHATSOEVER! My thought of suicide or at least a Ben & Jerry's binge had passed!
All I did was a little tweaking, basically encoding using compressor's "lower quality" 1-pass setting, not the usual DVD 90-min. best setting, which the manual says to use for the best possible quality.
You can bypass Compressor stand-alone completely, because DVDSP uses Compressor to encode imported quicktimes as well, and you can change the settings to 1-pass 7.2 bitrate there as well. Compressor just has more advanced settings available.
FCP also uses Compressor when you "export using quicktime conversion." So it's hard to get away from using it unless you have a third party mpeg2 encoder. I'm thinking about BitVice, which markets its product as "Probably the best software MPEG2 encoder in the world" -
Motion Generator seems to be crashing FCPX
I am having problems when I load a Motion generator into my FCPX project. It seems to be crashing the FCPX. It seems to stay open fine until i select the motion generator in my timeline then it just closes and brings up a crash report.
The only thing I can say is that when previewing the generator to drop it into FCPX it is showing a blue screen and not the animation and then when its dropped in the same thing happens if i scroll through the timeline. Then as I saidd, when I click on the generator it crashes FCPX completely.
I have to admit I dont know much about these crash reports and determining where its gone wrong but I wondered if anyone could advise?
This is the error report...
Process: Final Cut Pro [33128]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCut
Version: 10.0 (179114)
Build Info: ProEditor-179110400~1
App Item ID: 424389933
App External ID: 3491984
Code Type: X86-64 (Native)
Parent Process: launchd [212]
User ID: 501
Date/Time: 2013-02-13 11:43:08.675 +0000
OS Version: Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report: 625550 sec
Crashes Since Last Report: 83
Per-App Interval Since Last Report: 4231 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: F999BE30-AF72-9DFA-6F71-295664B4B763
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000278
VM Regions Near 0x278:
-->
__TEXT 0000000100000000-00000001000c2000 [ 776K] r-x/rwx SM=COW /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.prochannel.framework 0x0000000102308226 OZChannelBase::setInspectorCtlrClassName(__CFString const*) + 22
1 com.apple.Motion.effect 0x000000010b1ef7ea -[FFMotionEffect inspectableChannelsForIdentifier:] + 79
2 com.apple.Flexo 0x0000000100b3cbc8 -[FFAnchoredGeneratorComponent inspectableChannelsForIdentifier:] + 840
3 com.apple.Flexo 0x0000000100966df0 -[FFInspectorModuleChannels _setupChannelInspector] + 640
4 com.apple.Flexo 0x0000000100963633 -[FFInspectorModuleChannels setCurrentItems:] + 307
5 com.apple.Flexo 0x00000001009777fe -[FFInspectorTabModule _finishSetCurrentItems] + 2622
6 com.apple.Flexo 0x00000001009568b1 ExecuteProcrastinated + 193
7 libdispatch.dylib 0x00007fff91d240b6 _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff91d2896f _dispatch_after_timer_callback + 22
9 libdispatch.dylib 0x00007fff91d240b6 _dispatch_client_callout + 8
10 libdispatch.dylib 0x00007fff91d2629b _dispatch_source_invoke + 691
11 libdispatch.dylib 0x00007fff91d25305 _dispatch_queue_invoke + 72
12 libdispatch.dylib 0x00007fff91d29091 _dispatch_main_queue_callback_4CF + 220
13 com.apple.CoreFoundation 0x00007fff928500fe __CFRunLoopRun + 1614
14 com.apple.CoreFoundation 0x00007fff9284f6b2 CFRunLoopRunSpecific + 290
15 com.apple.HIToolbox 0x00007fff8da6f0a4 RunCurrentEventLoopInMode + 209
16 com.apple.HIToolbox 0x00007fff8da6ee42 ReceiveNextEventCommon + 356
17 com.apple.HIToolbox 0x00007fff8da6ecd3 BlockUntilNextEventMatchingListInMode + 62
18 com.apple.AppKit 0x00007fff9455e613 _DPSNextEvent + 685
19 com.apple.AppKit 0x00007fff9455ded2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
20 com.apple.AppKit 0x00007fff94555283 -[NSApplication run] + 517
21 com.apple.prokit 0x00000001002f8324 NSProApplicationMain + 378
22 com.apple.FinalCut 0x0000000100002138 start + 52
Thread 1:
0 libsystem_kernel.dylib 0x00007fff9801d6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff91675eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff91675cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff9801d336 __select_nocancel + 10
1 libdispatch.dylib 0x00007fff91d26b93 _dispatch_mgr_invoke + 284
2 libdispatch.dylib 0x00007fff91d269ee _dispatch_mgr_thread + 54
Thread 3:: Dispatch queue: com.apple.root.low-priority
0 libsystem_kernel.dylib 0x00007fff9801dd16 kevent + 10
1 com.apple.Flexo 0x00000001009a1cac __-[FFStorageManager _createKernelQueue]_block_invoke_1 + 28
2 libdispatch.dylib 0x00007fff91d27f01 _dispatch_call_block_and_release + 15
3 libdispatch.dylib 0x00007fff91d240b6 _dispatch_client_callout + 8
4 libdispatch.dylib 0x00007fff91d251fa _dispatch_worker_thread2 + 304
5 libsystem_c.dylib 0x00007fff91675cab _pthread_wqthread + 404
6 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff9801d6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff91675eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff91675cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.progl.framework 0x000000010289b7ea (anonymous namespace)::threadFunc(void*) + 70
3 com.apple.procore.framework 0x00000001001594fc PCThread::startup(void*) + 18
4 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
5 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 6:: com.apple.flexo.throttled-scheduled-io
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.Flexo 0x0000000100864858 Synchronizable::Wait() + 56
3 com.apple.Fig.provider 0x00000001090a50a8 0x109078000 + 184488
4 com.apple.Flexo 0x000000010086d65a Thread::RunHelper(void*) + 42
5 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 7:
0 libsystem_kernel.dylib 0x00007fff9801d6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff91675eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff91675cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff9801d6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff91675eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff91675cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 9:: MIO Mounting Thread
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677fc3 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff91323933 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff91323789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proapps.MIO 0x00000001015bb89c -[PluginLockPair scanPaths] + 284
5 com.apple.Foundation 0x00007fff912f8612 __NSThread__main__ + 1345
6 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
7 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 10:: MIO Mounting Thread
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677fc3 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff91323933 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff91323789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proapps.MIO 0x00000001015bb89c -[PluginLockPair scanPaths] + 284
5 com.apple.Foundation 0x00007fff912f8612 __NSThread__main__ + 1345
6 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
7 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 11:: MIO Mounting Thread
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677fc3 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff91323933 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff91323789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proapps.MIO 0x00000001015bb89c -[PluginLockPair scanPaths] + 284
5 com.apple.Foundation 0x00007fff912f8612 __NSThread__main__ + 1345
6 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
7 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 12:: MIO Mounting Thread
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677fc3 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff91323933 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff91323789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proapps.MIO 0x00000001015bb89c -[PluginLockPair scanPaths] + 284
5 com.apple.Foundation 0x00007fff912f8612 __NSThread__main__ + 1345
6 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
7 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 13:: MIO Mounting Thread
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677fc3 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff91323933 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff91323789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proapps.MIO 0x00000001015bb89c -[PluginLockPair scanPaths] + 284
5 com.apple.Foundation 0x00007fff912f8612 __NSThread__main__ + 1345
6 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
7 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 14:: com.apple.dvdplayback-DDPTask
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.AVCHDPlugin 0x000000011fed5eb7 semaphore_wait(viona_semaphore_t*) + 55
2 com.apple.AVCHDPlugin 0x000000011fee3460 WinPortServer::ProcessMessages() + 768
3 com.apple.AVCHDPlugin 0x000000011fe678a3 DDP_Init + 723
4 com.apple.AVCHDPlugin 0x000000011fed56c0 ST20Thread::Run(PThreadRunParams*) + 32
5 libsystem_c.dylib 0x00007fff91676dea _pthread_body + 54
Thread 15:: com.apple.flexo.player-render (playback)
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677fc3 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff91323933 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff91323789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.Flexo 0x000000010071b0b5 -[FFPlayer _waitForAttention] + 37
5 com.apple.Flexo 0x000000010071d8a4 -[FFPlayer playerRenderThreadMain:] + 324
6 com.apple.Foundation 0x00007fff912f8612 __NSThread__main__ + 1345
7 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 16:: com.apple.flexo.time-rate-change-controller
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.Flexo 0x000000010072779b TimeRateChangeController::threadFunction() + 299
3 com.apple.Flexo 0x000000010072ff7d TimeRateChangeController::thread_routine(void*) + 61
4 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
5 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 17:: com.apple.audio.IOThread.client
0 libsystem_kernel.dylib 0x00007fff9801b686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9801ac42 mach_msg + 70
2 com.apple.audio.CoreAudio 0x00007fff9578217a HALB_MachPort::SendMessageWithReply(unsigned int, unsigned int, unsigned int, unsigned int, mach_msg_header_t*, bool, unsigned int) + 98
3 com.apple.audio.CoreAudio 0x00007fff95782108 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 42
4 com.apple.audio.CoreAudio 0x00007fff957808db HALC_ProxyIOContext::IOWorkLoop() + 1209
5 com.apple.audio.CoreAudio 0x00007fff95780391 HALC_ProxyIOContext::IOThreadEntry(void*) + 83
6 com.apple.audio.CoreAudio 0x00007fff9578024b HALB_IOThread::Entry(void*) + 75
7 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 18:: com.apple.coremedia.scheduledfileio
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.CoreMedia.ProAppsSupport 0x000000010028af39 WaitOnCondition + 14
3 com.apple.CoreMedia.ProAppsSupport 0x000000010028b105 FigSemaphoreWaitRelative + 167
4 com.apple.CoreMedia.ProAppsSupport 0x0000000100289212 FigScheduledFileIOThread + 5109
5 com.apple.CoreMedia.ProAppsSupport 0x000000010028c03a figThreadMain + 397
6 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
7 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 19:
0 libsystem_kernel.dylib 0x00007fff9801d6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff91675eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff91675cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 20:: CVDisplayLink
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677fc3 _pthread_cond_wait + 927
2 com.apple.CoreVideo 0x00007fff8f07bed5 CVDisplayLink::waitUntil(unsigned long long) + 271
3 com.apple.CoreVideo 0x00007fff8f07b23d CVDisplayLink::runIOThread() + 529
4 com.apple.CoreVideo 0x00007fff8f07b013 startIOThread(void*) + 148
5 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 21:
0 libsystem_kernel.dylib 0x00007fff9801d6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff91675eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff91675cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 22:
0 libsystem_kernel.dylib 0x00007fff9801d6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff91675eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff91675cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 23:: com.apple.helium-unit
0 libsystem_kernel.dylib 0x00007fff9801d122 __psynch_mutexwait + 10
1 libsystem_c.dylib 0x00007fff91678d9d pthread_mutex_lock + 536
2 com.apple.Helium.HeliumRender 0x0000000102ce0e42 hg_pthread_loop(void*) + 98
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 24:: com.apple.helium-unit
0 libsystem_kernel.dylib 0x00007fff9801d122 __psynch_mutexwait + 10
1 libsystem_c.dylib 0x00007fff91678d9d pthread_mutex_lock + 536
2 com.apple.Helium.HeliumRender 0x0000000102ce0e42 hg_pthread_loop(void*) + 98
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 25:: com.apple.helium-unit
0 libsystem_kernel.dylib 0x00007fff9801d122 __psynch_mutexwait + 10
1 libsystem_c.dylib 0x00007fff91678d9d pthread_mutex_lock + 536
2 com.apple.Helium.HeliumRender 0x0000000102ce0e42 hg_pthread_loop(void*) + 98
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 26:: com.apple.helium-unit
0 libsystem_kernel.dylib 0x00007fff9801d122 __psynch_mutexwait + 10
1 libsystem_c.dylib 0x00007fff91678d9d pthread_mutex_lock + 536
2 com.apple.Helium.HeliumRender 0x0000000102ce0e42 hg_pthread_loop(void*) + 98
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 27:
0 libsystem_kernel.dylib 0x00007fff9801d6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff91675eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff91675cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 28:
0 libsystem_kernel.dylib 0x00007fff9801b686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9801ac42 mach_msg + 70
2 com.apple.CoreFoundation 0x00007fff9284a803 __CFRunLoopServiceMachPort + 195
3 com.apple.CoreFoundation 0x00007fff9284fee6 __CFRunLoopRun + 1078
4 com.apple.CoreFoundation 0x00007fff9284f6b2 CFRunLoopRunSpecific + 290
5 com.apple.CoreFoundation 0x00007fff9285e371 CFRunLoopRun + 97
6 com.apple.qmaster.do 0x0000000131b6f439 swamp::CRAdReceiver2::ReceivingThread::runOnce() + 187
7 com.apple.AECore 0x000000010b01cca5 aecore::CThread::runThread() + 35
8 com.apple.AECore 0x000000010b01ac8a threadProc(void*) + 9
9 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
10 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 29:: com.apple.helium-texture-finish
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.Helium.HeliumRender 0x0000000102cc77ca textureFinishThread(void*) + 186
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 30:
0 libsystem_kernel.dylib 0x00007fff9801d6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff91675eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff91675cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 31:
0 libsystem_kernel.dylib 0x00007fff9801d6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff91675eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff91675cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 32:: com.apple.helium-render-queue-exec-unit-gpu
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.Helium.HeliumRender 0x0000000102d28b8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x0000000102c480cf HGRenderQueue::GetRenderJob(HGRenderExecUnit*, HGRenderJob**) + 207
4 com.apple.Helium.HeliumRender 0x0000000102c3f90e HGRenderExecUnit::RunLoop() + 110
5 com.apple.Helium.HeliumRender 0x0000000102c3f894 StartRenderExecUnitFunc(void*) + 20
6 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
7 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 33:: com.apple.helium-render-queue-pbo-readback-unit
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.Helium.HeliumRender 0x0000000102d28b8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x0000000102c49860 HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) + 80
4 com.apple.Helium.HeliumRender 0x0000000102c3e625 StartPBOExecUnitFunc(void*) + 85
5 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 34:: com.apple.helium-render-queue-pbo-readback-unit
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.Helium.HeliumRender 0x0000000102d28b8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x0000000102c49860 HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) + 80
4 com.apple.Helium.HeliumRender 0x0000000102c3e625 StartPBOExecUnitFunc(void*) + 85
5 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 35:: com.apple.helium-render-queue-exec-unit-gpu
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.Helium.HeliumRender 0x0000000102d28b8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x0000000102c480cf HGRenderQueue::GetRenderJob(HGRenderExecUnit*, HGRenderJob**) + 207
4 com.apple.Helium.HeliumRender 0x0000000102c3f90e HGRenderExecUnit::RunLoop() + 110
5 com.apple.Helium.HeliumRender 0x0000000102c3f894 StartRenderExecUnitFunc(void*) + 20
6 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
7 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 36:: com.apple.helium-render-queue-pbo-readback-unit
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.Helium.HeliumRender 0x0000000102d28b8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x0000000102c49860 HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) + 80
4 com.apple.Helium.HeliumRender 0x0000000102c3e625 StartPBOExecUnitFunc(void*) + 85
5 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 37:: com.apple.helium-render-queue-pbo-readback-unit
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.Helium.HeliumRender 0x0000000102d28b8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x0000000102c49860 HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) + 80
4 com.apple.Helium.HeliumRender 0x0000000102c3e625 StartPBOExecUnitFunc(void*) + 85
5 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 38:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 39:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 40:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 41:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 42:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x0000000101abd650 JVTLibDecoDispose + 479680
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 43:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 44:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 45:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 46:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 47:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x0000000101abd650 JVTLibDecoDispose + 479680
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 48:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a458c6 VTImageRotationSessionCreate + 361307
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 49:
0 libsystem_kernel.dylib 0x00007fff9801d6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff91675eec _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff91675cb3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff91660171 start_wqthread + 13
Thread 50:
0 libsystem_kernel.dylib 0x00007fff9801d322 __select + 10
1 com.apple.AECore 0x000000010b01ccd2 aecore::CThread::runThread() + 80
2 com.apple.AECore 0x000000010b01ac8a threadProc(void*) + 9
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 51:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x00007fff9801d322 __select + 10
1 com.apple.CoreFoundation 0x00007fff9288f4e6 __CFSocketManager + 1302
2 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
3 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 52:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 53:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 54:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 55:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 56:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x0000000101abd650 JVTLibDecoDispose + 479680
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 57:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 58:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 59:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 60:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x00000001019ffdc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 61:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x0000000101abd650 JVTLibDecoDispose + 479680
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 62:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a0041b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x0000000101a458c6 VTImageRotationSessionCreate + 361307
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 63:: com.apple.CoreAnimation.CAOpenGLLayer
0 libsystem_kernel.dylib 0x00007fff9801b686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9801ac42 mach_msg + 70
2 com.apple.CoreFoundation 0x00007fff9284a803 __CFRunLoopServiceMachPort + 195
3 com.apple.CoreFoundation 0x00007fff9284fee6 __CFRunLoopRun + 1078
4 com.apple.CoreFoundation 0x00007fff9284f6b2 CFRunLoopRunSpecific + 290
5 com.apple.CoreFoundation 0x00007fff9285e371 CFRunLoopRun + 97
6 com.apple.QuartzCore 0x00007fff95e7c6ec CAOpenGLLayer_render_thread(void*) + 162
7 com.apple.QuartzCore 0x00007fff95e8be76 thread_fun + 25
8 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
9 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 64:: com.apple.flexo.worker-thread
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.Flexo 0x00000001008d3599 WorkerThread::Run() + 217
2 com.apple.Flexo 0x000000010086d65a Thread::RunHelper(void*) + 42
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 65:: com.apple.flexo.player-render (playback)
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677fc3 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff91323933 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff91323789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.Flexo 0x000000010071b0b5 -[FFPlayer _waitForAttention] + 37
5 com.apple.Flexo 0x000000010071d8a4 -[FFPlayer playerRenderThreadMain:] + 324
6 com.apple.Foundation 0x00007fff912f8612 __NSThread__main__ + 1345
7 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 66:: com.apple.flexo.time-rate-change-controller
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677f89 _pthread_cond_wait + 869
2 com.apple.Flexo 0x000000010072779b TimeRateChangeController::threadFunction() + 299
3 com.apple.Flexo 0x000000010072ff7d TimeRateChangeController::thread_routine(void*) + 61
4 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
5 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 67:: com.apple.flexo.worker-thread
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.Flexo 0x00000001008d3599 WorkerThread::Run() + 217
2 com.apple.Flexo 0x000000010086d65a Thread::RunHelper(void*) + 42
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 68:: com.apple.flexo.worker-thread
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.Flexo 0x00000001008d3599 WorkerThread::Run() + 217
2 com.apple.Flexo 0x000000010086d65a Thread::RunHelper(void*) + 42
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 69:: com.apple.flexo.worker-thread
0 libsystem_kernel.dylib 0x00007fff9801b6c2 semaphore_wait_trap + 10
1 com.apple.Flexo 0x00000001008d3599 WorkerThread::Run() + 217
2 com.apple.Flexo 0x000000010086d65a Thread::RunHelper(void*) + 42
3 libsystem_c.dylib 0x00007fff91673742 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff91660181 thread_start + 13
Thread 70:: CVDisplayLink
0 libsystem_kernel.dylib 0x00007fff9801d0fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff91677fc3 _pthread_cond_wait + 927
2 com.apple.CoreVideo 0x00007fff8f07bed5 CVDisplayLink::waitUntil(unsigned long long) + 271
3 com.apple.CoreVideo 0x00007fff8f07b23d CVDisplayLink::runIOThread() + 529
4 com.apple.CoreVideo 0x00007fff8f07b013 startIOThread(void*) + 148
5 lWhat's the Motion generator? Which one? Sounds like it's broken. What are the specs of your system?
-
Cross-dissolve from white frame to adjustment layer no longer works in CC 2014
Windows 7, Premiere Pro CC 2014
I have a video clip in a nested sequence on V1 and an adjustment layer on V2.
I want to dissolve from a white frame to the clip using the adjustment layer.
In PP CC (not 2014) this was simple:
Starting with a white PNG graphic on V2, cross-dissolve to the adjustment layer.
However, in PP CC 2014, this causes a dissolve to BLACK over the duration of the dissolve and then a CUT to the video.
This behavior in CC 2014 is illogical. Why has it changed?
There are other ways to do this, but this one was quick and easy, and is required for hundreds of clips in existing sequences / projects.
Response from support via live chat:
thank you for your patience
the adjustment is layer is not functioning properly
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&loc=en
please mention it in the feature/bug request formFor me with a color matte it shows exactly the same behavior as with a PNG.
You're dissolving between the matte and the adjustment layer on V2? -
Secret for using Cross Dissolve transitions
Based on my limited experience, the most useful transition is the cross dissolve. It is pretty much the only one I use since it is doesn't draw attention to itself and bears repeated deployment for smooth scene changes. But it has a problem: If you simply make a clip split and put the transition in, it won't work. And it appears even high level people at Apple technical support don't understand what is going on. Based on the apparently incorrect background information they gave me, I have always been extremely careful about making the split precisely where the scene changes and then chopping off a small number of frames in order to make the transition work. But recently I discovered that cross dissolve transitions will always work (regardless of whether the frames on both sides of the cut are similar or even identical) if you delete precisely one frame, and it can be from either side of the split. When you do that the edges of the clip go from squared (right angles) to rounded. The cross dissolve transitions will never work between two clips that have squared edges. They will always work when the edges are rounded. And all it takes to get the edges to be rounded is the deletion one frame. The edges get rounded and cross dissolve transitions work and if you remove more than one frame, and/or do if from both sides of the split. The point is that it will work with as little as one frame. But if you don't sacrifice at least one frame, cross dissolve transitions will never work.
Of course, I am assuming that my experience with iMovie '09 and '11 is not idiosyncratic. Also: I would be interested in knowing if anybody else knew this "secret"--and whether it is widespread knowledge or in any of the books on iMovie.When one splits clips, don't split close to what will be the beginning or the end of a shot.That's why you should always start the camera BEFORE the action begins and run AFTER the action ends. It only needs to be a 1/2 second to 1 second. Now before you add a cut or a transition you will automatically trim the end and the beginning of the two clips.
I start with a two-hour clip that includes hundreds of scenes, some ending abruptly, some not. If scene one suddenly ends and scene two begins, the natural place to make the cut is where the scene changes. If it happens that there is stuff immediately on each side of the cut that is of value, you would might prefer not to lose even one frame. Usually on one of the two sides the loss of one frame is not so bad. And if you sacrifice that frame you have almost everything you want. But it turns out that the situation is better than that. Since you can also add frames (I now realize), you can end without losing any frames at all. Of course, if you happen to be in a situation where there is plenty of useless stuff on both sides of a cut, the problem the solution is trying to solve does not come up. But I wouldn't change my filming habits just to avoid this problem of adding cross dissolves, since once you know what to handle it, it's not much of a problem. As to whether it is good practice to aim to have extra footage on both sides of a shot, sure. That seems like a good rule of thumb to me. But there are many situations where you don't have that opportunity. Say you were filming John Kennedy in Dallas or life among the Taliban or your kid falling off a horse. Life may not give you the chance to put useless footage at the end or beginning of your shot. In my case, I have hours of amateur home movies that stop at all sorts of odd places. I can't go back and reshoot it.
I suspect Apple simply expected you to do this. This will inherently eliminate what may be a tiny bug that you overcome by trimming 1 frame.
Most transition types don't require the removal or addition of a frame. When I called Apple technical support about this, the person I talked to was surprised by this feature too. And he found it happening with at least one other transition, I think. He handed me over to a specialist. That specialist gave me a complicated theory for why this was happening. He said that the frames on both sides of the cut had to look fairly different for the transition to work. And sometimes when we think we have made the cut exactly where the scene changes, we haven't in fact. So we need to cut away until both sides are definitely different. And you will notice that often the thumbnail for one side will be an image from the other side. This lead me to think that I was required to make sure that on either side of the cut there was definitely a significant change of image. But all you have to do is get the edges of the clip to become rounded. And you can do this by adding or subtracting a frame at any location. Of course, if you are going to be chopping off multiple frames for any reason, you will also solve or avoid this problem. So, if Apple was thinking what you suggest, they haven't given any guidance about it in print. And the tech support people don't seem to know it.
Message was edited by: Paul Bullen -
XML not pulling color correction or Motion Generator data?
Does FCPX 10.0.8 support exporting XML data related to color correction or motion Generator templates?
If I export a project to XML and reimport the same XML film into FCPX all resources are recognized and appear in the correct place/lane. My custom motion title themes come through, but the "Whites" generator in the project reverts its settings to default (i.e., in the Generator tab of the inspector the pop up is set to Smokey (defualt) instead of "Bright White" (selected in my original project). I also loose any color work I did on any of my clips.
Anyone have a similar problem? Workaround?Hello veritasmediapro,
I was wondering if you discovered a solution for the above. I am experiencing the same as what you describe. I was hoping I could use the fcpxml format to have a 3rd party tool generate a file that changes motion generator parameter values. My plan was to use key frames. As far as my experiments tell generator parameters as well as key frames on generator parameters are not supported :-( -
Cross Dissolve, Dip to Color not working
Hello. I am having trouble applying Cross Dissolve and Dip to Color to the transition between to separate clips. It works fine when I am transitioning between two clips originating from the same raw captured file (e.g. between two pieces I cut out of Raw 1), but I am unable to apply the transition to two clips from separate raw files (e.g. between a piece of Raw 1 and a piece of Raw 2).
The timeline only allows me to place the transition just AFTER the cut between the two clips, rather than straddling the two for a smooth fade. Any idea why this might be? Thanks in advance for your help.
Using Final Cut Pro 5.1.4, Tiger 10.4.9Enough handles?
#1 Transitions "Insufficient Content"
Shane's Stock Answer #1:
You need to make sure that your clips have enough media (called 'handles') at the beginning of the incoming clip and at the end of the outgoing clip for the transition. For example, if you have a 1 second (30 frame) dissolve, your in and out point need to be at least 15 frames from the edge of the clip.
What you are running into is that you are marking an out point at the end of a clip then adding a cross dissolve, say 20 frames in duration. Since the dissolve is centered on the cut, it will start 10 frames before the cut, and try to go 10 frames AFTER the cut...which it can't do.
What you need to do is plan how long your dissolve will be and back-time your cut so that it works.
a full 1 second crossfade reaches 15 frames into each clip. So, if you want to change a cut to a crossfade, there has to be at least 15 additional frames of each clip.
Say you're trying to crossfade from one clip into the very first frame of a second clip. FCP cannot 'create' 15 more frames of the second clip to do a crossfade. If they're not there, you're out of luck.
FCP has to extend the end of your first clip by 1/2 of your transition length, and the beginning of your second clip by 1/2 of your transition length, so those frames need to be in your system. The nature of a crossfade is mixing two clips together.
Shane -
Problem with Cross Dissolve and Opacity
I've been noticing that Cross Dissolve has been acting goofey for awhile but have overcome any problems by manually adjusting opacity settings. However, this time I can't get either to cooperate. Notice the line appearing below the phrase "the nutrient recommendation map" in the image below. This line or a similar line will appear as title either cross dissolve into one another or if they are stand alone and the opacity settings fade them in and out. The blinking of the lines is sporadic and changes as I make adjustments. I'll "fix" one spot but they will start to blink at other points in the time line and in different areas.
Any ideas?I ask because I think I'm having a similar problem. Went home and updated PPro to 5.0.3 and still have the issue.
The screen shot here show the first seconds of an HDV30/60 sequence as the video fades in (bottom layer - lasts about 2 seconds). The top layer is a mask to create the effect of a cinescope camera (no fade). I've cropped the left for demo purposes.
The bottom layer is regular ol' HDV footage. The top layer was created using a Photoshop file with 2 squares using the shape tool and colored black.
For pre-view and render, you can see a light-colored hair line around the top mask. I've applied different effect to remove it, but it won't work. In fact, some effects make it stand out even more. I've also tried using other assets from the PSD (PNG, PPro black video, etc). I also tried the cropping work-around but it did not work.
The screenshot is subtle but it's there. The main thing is that it can be VERY noticable in the BD-R discs I've created played back on set-top players so I'm really hoping there is a fix for it. I did notice that it will appear when I scrub with my finger on the left mouse key. As soon as I let go it appears again.
So PPro is up to date, graphics card is up to date, and I've tried suggested fixes and a few of my own with no luck. Any ideas?
Thanks,
Erik
Maybe you are looking for
-
Upgraded from 10.6 to 10.8 and time machine is stuck on 'preparing backup'
I am running a MBP, purchased in 2011. I upgraded on Sunday from 10.6 to 10.8 and everything seemed to be working fine. Thought I would do a backup but the drive has just been stuck on 'preparing backup' for ages. Does anybody have any ideas of what
-
Error in BDC program which is creating Work Order IW31
Hi All, I am getting an error - 532 - " Specify only one start time/date " when running bdc program for txn IW31 in back ground. I run the same program in the foreground.. there is no error.. but when I run in background.. I am experienci
-
Handling boot-critical Win 7 drivers in ZCM imaging
Does anyone know how to handle boot-critical drivers with ZCM imaging? These are typically disk controller and/or NIC drivers. MS WIM seems to require that you mount the image and "reflect" the driver into the image. (Gotta love MS's way with words.)
-
Hi All, Are there any presentations or links to screenshots of sample dashboards with views of BI reports? I'm looking for samples with headcount reports in the dashboard. Thank you Amina Edited by: Amina Anjum on Mar 28, 2008 11:01 PM
-
Hey All, I just purchased a new printer about three or four weeks ago, and my black ink is running low. Every time I print something from my computer, I havet to wait throught a 15-second pause before anything will print. The printer queue dialog wil