Motion tracking titles in Premiere Pro CC 2014?

I love the addition of motion tracking to effects in Premiere CC 2014 — but does anyone have a way of using them to track a clip (in my case a title)? I've got a promotional mini-doc I'm working on for a client, and have nice little animated titles popping up next to interview subjects (no lower thirds because there will be subtitles). I think pinning those to a visual element in the background would look great.
I tried putting a garbage matte as an effect on the title, then turning on the tracking feature, and creating a box around the item I wanted the title to track to. No dice.
Anyone have any suggestions, or do I need to go through third party software for this to work?

Hi misidunai,
Use the 3D Camera Tracker in After Effects. Check out this video tutorial.
Thanks,
Kevin

Similar Messages

  • Jerky Titles in Premiere Pro CC 2014

    The rolling titles I have created are very 'jerky' / stuttering / jittery.  I tried using various methods to avoid this that have been posted on these boards, but nothing has helped. I used rolling titles, the pre-set version, and that was bad. I tried easing in / easing out and that did not work.  I did not adjust the clip's length on the timeline.  I then used a Photoshop file w/ the credits and used Keyframing and Motion effects and it still jittered, even with bezier lines, auto or continuous - tried both. And yes, I rendered the files, every time, to check and that did not work. 
    Link to example: Jittery Credits Test on Vimeo
    On a side note, PP CC 2014 is crashing at least once a session, whereas PP CC was very stable. What gives?
    Using PP CC 2014
    I have virtually the entire CC suite and the CC 2014 suite, mainly use PP and AME
    All updates have been installed
    Mac OS 10.9.3
    CC membership subscription on desktop
    The source footage is H.264 in quicktime container
    No error messages, just no response once the window to import a project closes, after one is selected
    The problem is occurring w/ any project file that I try.
    Did not have this problem in PP CC
    The only other software I am using is Chrome
    No third party codecs installled
    Computer is a 2013 Mac Pro, 3.5 Ghz 6-core, 16 GB memory, AMD FirePro D500 3072 MB graphics card, No third party I/O hardware

    Hi misidunai,
    Use the 3D Camera Tracker in After Effects. Check out this video tutorial.
    Thanks,
    Kevin

  • How do I create Arabic Titles in Premiere Pro CC 2014?

    I have a word document with Arabic text. However, if i copy & paste into Premier Pro titler it appears as a strange (unicode?) font.
    Is there anyway to copy / paste Arabic text into titler and have it display properly?
    Thanks

    You'll need to reverse it so it looks correct in Premiere, here's a website that does it for you:
    http://omar84.com/docs/taw/arabic_writer.html
    Paste the Arabic text to INPUT, choose Process Input, then Select Output and copy (CMD + C), then paste in Premiere, and choose a font that supports Arabic (Example: Adobe Arabic).
    Here's another website that does the same thing:
    http://www.arabic-keyboard.org/photoshop-arabic/
    Good luck

  • What font works best for Hindi titles in Premiere Pro CC 2014?

    I'm attempting to subtitle a video in Hindi.
    I've installed a few fonts but nothing is working 100%.
    When I copy/paste from a translated script (PDF) random characters do not show up in the title tool (they appear as spaces).
    I'm wondering if Adobe recommends any Hindi fonts that are Premiere friendly?
    Thanks!

    Hi misidunai,
    Use the 3D Camera Tracker in After Effects. Check out this video tutorial.
    Thanks,
    Kevin

  • When clicking an audio clip on the timeline in Premiere Pro CC 2014, it duplicates it on a different track and makes it impossible to work.

    I'm experiencing a disturbing issue as it actually prevents me to do the work in Premiere. I will put as much info as possible:
    1) Project started on a different computer (the editor), PC with Premiere Pro CC,
    2) Now opened on my Imac with Premiere Pro CC 2014,
    3) I am not editing, simply trying to move audio clips on different tracks to export audio tracks only,
    THE ISSUE:
    1) Here is my timeline:
    2) When I select an audio clip to highlight it, Premiere creates a duplicate on a different track:
    Note that the clip highlighted in the previous screen cap is the duplicate and I didn't click it, Premiere highlights it as soon as it is duplicated.
    3) When I click out of the timeline or scroll up or down on the timeline, the duplicates disappear. However, when I try to move the original clips, it doesn't do anything, they are stuck in place.
    ANTICIPATED ANSWERS:
    1) You work on 2 different computers with 2 different versions of Premiere Pro CC, what do you expect? --> The amazing thing about Adobe CC is that it shouldn't be an issue and now I have to deal with it in this way,
    2) Try and save an updated version of your project from your computer. --> Already done that.
    Thank you for your help. I usually use the customer support chat but I am on the other side of the globe and it is now closed. This issue prevents me to work so I need to solve it quickly.
    Kind regards,
    Aurelien

    This sounds to me like it could be a graphics related problem are you on the latest driver. Something else you could try, start a new project and import the one from the PC into that rather than directly opening it in the MAC

  • Can't Move Audio Clips in Timeline After Expanding to View Waveforms (Premiere Pro CC 2014.2)

    So, this seems to be a bit of a weird one, and I'd be pretty stoked if it ended up being something silly that I'm doing wrong, but I can't for the life of me figure out what that might be.
    As the title suggests, I can't use the mouse to move some audio clips in a timeline once I expand the track to view the waveforms. This appears to only happen with independent audio clips (WAV. AIFF, MP3, etc), and not with clips attached to video. Also, it's worth noting that I don't have track keyframes turned on. I was hoping that was it, but it wasn't.
    So, what happens is this:
    1) I drag an audio clip down to the timeline (I can drag it onto an existing track, or drag to the bottom of the sequence and create a new track. Neither option seems to get a different result.).
    2) So long as the track isn't expanded and the waveform isn't visible, I can move the clip left, right, or up and down to a different track.
    3) As soon as I expand the track to view the waveform this functionality goes out the window. When this issue happens I can use the keyboard to nudge left and right, but that's about all the movement I have.
    4) It's almost as though the track becomes corrupt. The lanes for the track don't redraw properly, and the track is pretty much unusable. I can't put anything into it, and I can't take anything out. All I can do is delete the track and start again.
    Complicating issues is that this doesn't always happen, but instead is one of those "vast majority of the time" issues. I can't see any rhyme or reason for why it works or doesn't. I seem to do the exact same thing, but occasionally get different results. It doesn't matter what type of file I'm using (WAV, AIFF, etc), and this only happens with independent audio clips.
    Once again, I don't have track keyframing turned on when this happens. Believe me, I wish that was it.
    I have already filed a couple of bug reports about this over the last month or so, but haven't heard anything yet. I was wondering if anyone else was having the same issue, and if so, whether they had any workarounds.
    Mandatory system info:
    Windows 7 Professional SP1 (64-Bit)
    Intel i7-3820
    32GB RAM
    Nvidia GTX 980 (350.12)
    Premiere Pro CC 2014.2

    Update:
    I was just looking to post a screenshot of the timeline when I discovered something interesting. As soon as I use the vertical scroll bar to the right of the sequence, the tracks start to work again. Close off the waveform and the clip goes haywire. Move the scroll bar a tiny bit (or a lot), and suddenly the clip starts working.
    Pretty bizarre.
    The good news is that for the time being that could be a workaround, though it would be great for this to not happen at all.

  • Open Adobe Premiere Pro CC 2014 project   in Adobe Premiere Pro CC

    Hi everyone,
    Did somebody knows how to open Adobe Premiere Pro CC 2014 project   in Adobe Premiere Pro CC ?
    Best regards, Alex

    This method is not good for me, because I lost stuff  like titles with its settings of motions and effects (I try to open my templates for video clips ).
    Maybe there is another way to do it ?

  • Re-interpreted footage metadata is lost when moving Premiere Pro CC 2014 project file to different computer

    Hi guys,
    I believe this is just a bug in Premiere Pro CC 2014 (and other versions in the past), but I wanted to make sure it was on the PP team's plate for the next update, since it's detrimental to a workflow that include more than one computer or more than one editor on a project.
    My team shoots a lot of footage in slow-motion (for instance, 59.94 for 23.976). Premiere's process to conform this footage is great. Modify -> Interpret Footage -> Assume this frame rate: "23.976".
    Unfortunately, when we move this project file to another system, even if we are using a hard-drive that is synced to have the exact same source media files with the exact same file structure, we lose the footage interpretation metadata. Premiere Pro CC thinks this footage is 59.94 again, and our sequences are in shambles. All clips where the interpretation metadata is lost have "zebra pin stripes" on them wherever they exist in our sequences.
    We have to manually re-interpret the footage, and then sometimes manually re-select in and out points. This is a work-around that enables us to push forward, but it's a barrier that makes collaborative editing extremely challenging and opens up rampant possibility for error. It's hard to locate every clip we need to re-interpret in some of our more complex projects, and even harder to avoid re-interpreting the wrong clips.
    Looking forward to a resolution to this problem.
    Daniel Lichtenberg
    [ad/link removed by moderator]

    Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
    I came across this thread
    Premiere Pro CC error message and crash
    which had the suggestion -
    "Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
    This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
    I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case

  • Error installing update in Premiere Pro CC 2014.2, error code U44M1I210

    Tried several times to update Premiere Pro CC 2014.2 with the same error code U44M1I210. Tired to contact customer but their site is down.

    Got the same Error. Previous I worked with a GTX 760, and was hoping to get it fixed with using a GTX 780 6GB. But just as you, didn't solve the Problem.
    Usually I got the Problem solved, with exiting Premiere, restarting it, reset my Workspace. Then the Problem of having the bugged Workspace was gone. And also the Problem of the missing Video Tracks.
    At the moment I started on a new Project. Pretty simple, with only a 21 second DV footage. And here I was switching tabs with my Browser, came back to the Project, and the Video Tracks were gone. I saved, closed Premiere, restated and the Video Tracks are still  missing.
    So I made a new Sequence, voilá the Video Tracks are there. Thus I need to copy and paste the Tracks onto the new Sequence.
    But that is not really a solution!
    I was on the Phone with Adobe, and on Chat, but they couldn't help me. They suggested to get a Tesla or Quadro Card, or at least a GPU that got confirmed as working on their page. I did that, but obviously, that is not the issue.

  • Premiere Pro cc 2014 do not import After Effects composition. Inside Premiere Pro CC 2014 is not possible call back After Effects, is not possible to work with After Effects. Thank you

    Premiere Pro cc 2014 do not import After Effects composition. Inside Premiere Pro CC 2014 is not possible call back After Effects, is not possible to work with After Effects. Thank you

    You haven't given us much to go on here.  What exactly are you doing and what exactly happens when you try?  Which specific version of each program are you using?  (Go to Help>About...)
    On a side note, a simple, brief thread title is all that's needed.  Something like "After Effects Issue" would be fine.  You don't need the full question there.

  • Why is Dynamic Link between Premiere Pro CC 2014 and After Effects CC 2014 not syncing audio changes?

    When I try to use a Dyamic Link between something I've cut in Premiere and a composition in After Effects, if it is simply an audio level change it will not update in AE.  Only if I alter the Video track does it then take the changes reflected.  Any suggestions as to what is causing this?
    Running Adobe Premiere Pro CC 2014 and After Effects CC 2014.

    As Dave alludes, AfterEffects is all about the visual changes ... or at least, mostly. For changes to the audio outside of PrPro's internal controls, highly suggested you use Audition instead. It is all about the sound ... and yes, will update PrPro when used correctly.
    Neil

  • Premiere Pro CC 2014 with NVIDIA system freezes (Win7x64)

    It appears after perhaps the last update Premiere Pro CC 2014 started freezing during editing. It appears to happen mostly with 4K material and using the Ultra key and alpha blending but may also occur with 4K titles. The sequences are 23.976 1080p, with mixed footage from the Sony A7S (50 Mbps XAVC-S/H.264) and GH4 (4K 100 Mbps H.264). There are also frequent crashes with GPUFoundation.dll (Mercury + CUDA). No freezing with software only rendering. I tried a variety of drivers when using a Quadro 5000 with no change in freeze behavior. I tried a new GTX 770 (clean driver install) and the freeze behavior and GPUFoundation.dll crashes are the same, however now even the mouse freezes. With the Quadro 5000, the entire Windows GUI would freeze (become inactive), however the mouse would still move. Thus, it appears there are issues with both NVidia drivers and Premiere Pro CUDA code path on Windows (app errors shouldn't be able to lock up the entire GUI). GPU Meter shows low GPU and GPU memory utilization during the freezes. The freezes typically occur when switching between clips during playback or scrubbing (more often with fast scrubbing). As a developer, it feels like some kind of semaphore lock / race condition, since during the freezes CPU, GPU, and memory utilization are very low. Additional hardware info: 2010 MacPro 12-Core, 24GB RAM running Win7x64 (with latest updates). Side note: PPro used to hang in memory on exit, but stopped after a recent Microsoft forced update (PPro now crashes sometimes on exit but no longer hangs in memory (used to have to kill it after exiting every time)). Has this been reported before? (A7S XAVC & GH4 4K footage is relatively new)

    This crash occurred when dragging Black Video with Noise and other effects on top of alpha composited layers (+3 layers). CUDA turned the rendered area black, so I switched to OpenCL. This crash happened a few minutes later. While this would appear to be an Nvidia driver error (OpenCL), perhaps the developers can investigate. The system is very stable except when doing complex operations in PPro (and only PPro crashes). A tried and true Quadro 5000 crashed in the same way (totally different hardware and drivers).
    The full debug info wouldn't post, edited shorter:
         Application Specific Signatures:
         Graphics hardware encountered an error and was reset: 0x0000001f
    Process:         Adobe Premiere Pro CC 2014 [380]
    Path:            /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Identifier:      com.adobe.AdobePremierePro
    Version:         8.0.1 (8.0.1)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [191]
    Responsible:     Adobe Premiere Pro CC 2014 [380]
    User ID:         501
    Date/Time:       2014-10-01 03:13:25.803 -0700
    OS Version:      Mac OS X 10.9.5 (13F34)
    Report Version:  11
    Anonymous UUID:  3E030FD4-F38F-857C-3EB9-85D10E36AB49
    Crashed Thread:  11  Dispatch queue: opencl_runtime
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    abort() called
    Application Specific Signatures:
    Graphics hardware encountered an error and was reset: 0x0000001f
    Thread 0:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
    1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
    2   com.apple.CoreFoundation       0x00007fff8bb10f15 __CFRunLoopServiceMachPort + 181
    3   com.apple.CoreFoundation       0x00007fff8bb10539 __CFRunLoopRun + 1161
    4   com.apple.CoreFoundation       0x00007fff8bb0fe75 CFRunLoopRunSpecific + 309
    5   com.apple.HIToolbox           0x00007fff8d375a0d RunCurrentEventLoopInMode + 226
    6   com.apple.HIToolbox           0x00007fff8d3757b7 ReceiveNextEventCommon + 479
    7   com.apple.HIToolbox           0x00007fff8d3755bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
    8   com.apple.AppKit               0x00007fff86c7424e _DPSNextEvent + 1434
    9   com.apple.AppKit               0x00007fff86c7389b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
    10  com.apple.AppKit               0x00007fff86c6799c -[NSApplication run] + 553
    11  com.adobe.Frontend.framework   0x00000001000ca38d FE::MacApplication::RunSelf() + 45
    12  com.adobe.Frontend.framework   0x000000010004898a FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
    13  com.adobe.Frontend.framework   0x00000001000cbc44 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 276
    14  com.adobe.Frontend.framework   0x00000001000d2e25 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
    15  com.adobe.AdobePremierePro     0x00000001000018ac main + 508
    16  com.adobe.AdobePremierePro     0x00000001000016a4 start + 52
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib         0x00007fff8bcc4662 kevent64 + 10
    1   libdispatch.dylib             0x00007fff8a0c2421 _dispatch_mgr_invoke + 239
    2   libdispatch.dylib             0x00007fff8a0c2136 _dispatch_mgr_thread + 52
    Thread 2:
    0   libsystem_kernel.dylib         0x00007fff8bcc464a kevent + 10
    1   com.adobe.dvatransport.framework 0x0000000100e294fc boost::asio::detail::kqueue_reactor::run(bool, boost::asio::detail::op_queue<boost::asio::detail::task_io_service_operation>&) + 236
    2   com.adobe.dvatransport.framework 0x0000000100e291a7 boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost:: asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) + 375
    3   com.adobe.dvatransport.framework 0x0000000100e28d18 boost::asio::detail::task_io_service::run(boost::system::error_code&) + 552
    4   com.adobe.dvatransport.framework 0x0000000100e18157 SkyConnectionEnv::MainLoop() + 167
    5   com.adobe.dvatransport.framework 0x0000000100e17c09 SkyConnectionEnv::StaticThreadFunc(SkyConnectionEnv*) + 9
    6   com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
    7   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
    8   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
    9   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
    Thread 3:
    0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x00007fff8c0d0c3b _pthread_cond_wait + 727
    2   com.adobe.dvacore.framework   0x000000010036a0ab boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost:: asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) + 139
    3   com.adobe.dvacore.framework   0x0000000100369e18 boost::asio::detail::task_io_service::run(boost::system::error_code&) + 552
    4   com.adobe.dvacore.framework   0x0000000100369bda boost::asio::detail::posix_thread::func<boost::asio::detail::resolver_service_base::work_ io_service_runner>::run() + 42
    5   com.adobe.dvatransport.framework 0x0000000100e29bb3 boost_asio_detail_posix_thread_function + 19
    6   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
    7   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
    8   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
    Thread 4:
    0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x00007fff8c0d0c3b _pthread_cond_wait + 727
    2   com.apple.CoreServices.CarbonCore 0x00007fff824bc800 TSWaitOnCondition + 108
    3   com.apple.CoreServices.CarbonCore 0x00007fff824bc9ff TSWaitOnConditionTimedRelative + 172
    4   com.apple.CoreServices.CarbonCore 0x00007fff8248d145 MPWaitOnQueue + 192
    5   com.adobe.dvacore.framework   0x00000001003a359d dvacore::threads::ThreadSafeDelayQueue::PopWithTimeout(std::auto_ptr<dvacore::threads::Al locatedFunctionT<boost::function<void ()> > >&, int) + 141
    6   com.adobe.dvacore.framework   0x00000001003a1500 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 160
    7   com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
    8   com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
    9   com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
    10  libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
    11  libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
    12  libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
    Thread 5:
    0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x00007fff8c0d0c3b _pthread_cond_wait + 727
    2   com.adobe.GPUFoundation.framework 0x000000010941b8d6 void boost::condition_variable_any::wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&) + 70
    3   com.adobe.GPUFoundation.framework 0x0000000109419705 GF::Device::AcquireExclusiveAccess() + 117
    4   com.adobe.PlayerMediaCore.framework 0x0000000129518684 AdobePlayer::PlayerDisplay::UpdateWindow() + 372
    5   com.adobe.PlayerMediaCore.framework 0x000000012952b2a5 AdobePlayer::PlayerMain::OnUpdate() + 21
    6   com.adobe.PlayerMediaCore.framework 0x0000000129530501 PrPlayModule<AdobePlayer::PlayerMain>::PlayEntry(int, pmStdParms*, void*, void*) + 241
    7   com.adobe.PlayerMediaCore.framework 0x0000000129530390 xPlayEntry + 16
    8   com.adobe.PlayerHost.framework 0x00000001057238c4 ML::CallPlayerModuleGuarded(int (*)(int, pmStdParms*, void*, void*), int, pmStdParms*, void*, void*, int*, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 276
    9   com.adobe.PlayerHost.framework 0x0000000105721669 ML::PlayerModule::CallPlugin(int, void*, void*) + 153
    10  com.adobe.PlayerHost.framework 0x0000000105745c36 ML::VideoPlayer::CallPlayModuleSelector_Update() + 86
    11  com.adobe.PlayerHost.framework 0x000000010573421d ML::VideoPlayer::ForceDisplayRedraw(ML::PlayerOutputQuality) + 205
    12  com.adobe.PlayerHost.framework 0x0000000105728a34 ML::PlayModuleThreadQueue::ExecuteDeferredCall(ASL::ObjectPtr<ML::DeferredCallBase, ASL::AtomicValue>) + 340
    13  com.adobe.PlayerHost.framework 0x0000000105727935 ML::PlayModuleThreadQueue::ServiceQueue() + 293
    14  com.adobe.dvacore.framework   0x00000001003a159e dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 318
    15  com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
    16  com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
    17  com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
    18  libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
    19  libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
    20  libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
    Thread 6:
    0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x00007fff8c0d0c77 _pthread_cond_wait + 787
    2   com.apple.CoreServices.CarbonCore 0x00007fff824bc9e7 TSWaitOnConditionTimedRelative + 148
    3   com.apple.CoreServices.CarbonCore 0x00007fff8248d145 MPWaitOnQueue + 192
    4   com.adobe.dvacore.framework   0x00000001003a359d dvacore::threads::ThreadSafeDelayQueue::PopWithTimeout(std::auto_ptr<dvacore::threads::Al locatedFunctionT<boost::function<void ()> > >&, int) + 141
    5   com.adobe.dvacore.framework   0x00000001003a1500 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 160
    6   com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
    7   com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
    8   com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
    9   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
    10  libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
    11  libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
    Thread 7:
    0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
    1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
    2   libcuda_334.01.03_mercury.dylib 0x00000001223f85a2 cuosEventWait + 210
    3   libcuda_334.01.03_mercury.dylib 0x000000012233e922 intHandlerMain + 114
    4   libcuda_334.01.03_mercury.dylib 0x00000001223f9479 cuosPosixThreadStartFunc(void*) + 41
    5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
    6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
    7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
    Thread 8:
    0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
    1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
    2   libclh.dylib                   0x000000011ae0fe19 0x11a800000 + 6356505
    3   libclh.dylib                   0x000000011a8c5df2 0x11a800000 + 810482
    4   libclh.dylib                   0x000000011ae10c69 0x11a800000 + 6360169
    5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
    6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
    7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
    Thread 9:
    0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
    1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
    2   libclh.dylib                   0x000000011ae0fe19 0x11a800000 + 6356505
    3   libclh.dylib                   0x000000011a8c5df2 0x11a800000 + 810482
    4   libclh.dylib                   0x000000011ae10c69 0x11a800000 + 6360169
    5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
    6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
    7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
    Thread 10:
    0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
    1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
    2   libclh.dylib                   0x000000011ae0fe19 0x11a800000 + 6356505
    3   libclh.dylib                   0x000000011a8c5df2 0x11a800000 + 810482
    4   libclh.dylib                   0x000000011ae10c69 0x11a800000 + 6360169
    5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
    6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
    7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
    Thread 11 Crashed:: Dispatch queue: opencl_runtime
    0   libsystem_kernel.dylib         0x00007fff8bcc3866 __pthread_kill + 10
    1   libsystem_pthread.dylib       0x00007fff8c0cf35c pthread_kill + 92
    2   libsystem_c.dylib             0x00007fff8c131bba __abort + 145
    3   libsystem_c.dylib             0x00007fff8c131b29 abort + 140
    4   libGPUSupportMercury.dylib     0x00007fff89db41ca gpusKillClient + 111
    5   libGPUSupportMercury.dylib     0x00007fff89db4b51 gpusQueueSubmitDataBuffers + 155
    6   libclh.dylib                   0x000000011a90ee26 0x11a800000 + 1109542
    7   libclh.dylib                   0x000000011a8b104a 0x11a800000 + 725066
    8   libclh.dylib                   0x000000011a8b10a1 0x11a800000 + 725153
    9   libclh.dylib                   0x000000011a8b4394 0x11a800000 + 738196
    10  libclh.dylib                   0x000000011a910425 clhCtxSynchronize + 21
    11  com.nvidia.web.GeForceGLDriverWeb 0x00001234402e627d gldFinishQueue + 234
    12  com.apple.opencl               0x00007fff87917abe 0x7fff87911000 + 27326
    13  com.apple.opencl               0x00007fff87931123 0x7fff87911000 + 131363
    14  com.apple.opencl               0x00007fff8793414a 0x7fff87911000 + 143690
    15  libdispatch.dylib             0x00007fff8a0c028d _dispatch_client_callout + 8
    16  libdispatch.dylib             0x00007fff8a0c6a18 _dispatch_barrier_sync_f_slow + 460
    17  com.apple.opencl               0x00007fff87933faa 0x7fff87911000 + 143274
    18  com.apple.opencl               0x00007fff8792a202 clEnqueueMapBuffer + 631
    19  com.adobe.RendererGPU.framework 0x0000000111714245 GF::ScopedRecordedHostMemory::Map() const + 133
    20  com.adobe.RendererGPU.framework 0x00000001117685ea RendererGPU::PointwiseFilterHostNode::ApplyConcatenatedPointwiseFilters(ASL::InterfaceRef <MF::IVideoFrame, MF::IVideoFrame> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame> const&, boost::shared_ptr<RenderResults> const&, std::vector<RendererGPU::PointwiseFilter, std::allocator<RendererGPU::PointwiseFilter> > const&) + 826
    21  com.adobe.RendererGPU.framework 0x0000000111767daf RendererGPU::PointwiseFilterHostNode::Process(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&) + 831
    22  com.adobe.RendererGPU.framework 0x000000011171d2b8 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 1448
    23  com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
    24  com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
    25  com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
    26  com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
    27  com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
    28  com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
    29  com.adobe.RendererGPU.framework 0x00000001117194d5 RendererGPU::CompositorNode::Process(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&) + 1413
    30  com.adobe.RendererGPU.framework 0x000000011171d2b8 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 1448
    31  com.adobe.RendererGPU.framework 0x000000011170f36f RendererGPU::(anonymous namespace)::RendererGPU::ProduceFrame(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, std::string*, ASL::ParamRect<int>) + 1279
    32  com.adobe.PlayerMediaCore.framework 0x0000000129535bf0 AdobePlayer::RenderRequest::ProduceFrame(ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, RenderParams const&, std::string*, ASL::ParamRect<int>) + 96
    33  com.adobe.PlayerMediaCore.framework 0x000000012951cefd AdobePlayer::PlayerDisplay::PresentRenderRequestImpl(boost::shared_ptr<AdobePlayer::Rende rRequest> const&) + 1901
    34  com.adobe.PlayerMediaCore.framework 0x00000001295204db AdobePlayer::PlayerDisplay::PresentLastCompletedRenderRequestImpl() + 267
    35  com.adobe.dvacore.framework   0x00000001003a159e dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 318
    36  com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
    37  com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
    38  com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
    39  libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
    40  libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
    41  libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
    External Modification Summary:
      Calls made by other processes targeting this process:
        task_for_pid: 319
        thread_create: 0
        thread_set_state: 0
      Calls made by this process:
        task_for_pid: 0
        thread_create: 0
        thread_set_state: 0
      Calls made by all processes on this machine:
        task_for_pid: 56776
        thread_create: 1
        thread_set_state: 0
    VM Region Summary:
    ReadOnly portion of Libraries: Total=679.6M resident=223.0M(33%) swapped_out_or_unallocated=456.6M(67%)
    Writable regions: Total=19.5G written=15.6G(80%) resident=14.2G(73%) swapped_out=3.0G(16%) unallocated=5.3G(27%)
    REGION TYPE                      VIRTUAL
    ===========                      =======
    ATS (font support)                 32.0M
    ATS (font support) (reserved)         8K        reserved VM address space (unallocated)
    CG backing stores                  23.8M
    CG image                            584K
    CG raster data                       48K
    CG shared images                    204K
    CoreImage                             8K
    Foundation                            4K
    IOKit                              78.3M
    IOKit (reserved)                    268K        reserved VM address space (unallocated)
    Image IO                           1032K
    Kernel Alloc Once                     8K
    MALLOC                              1.5G
    MALLOC (admin)                       32K
    MALLOC_LARGE (reserved)             512K        reserved VM address space (unallocated)
    Memory Tag 241                      128K
    Memory Tag 242                       12K
    Memory Tag 249                      192K
    Memory Tag 251                       24K
    OpenCL                              1.0G
    OpenGL GLSL                        1664K
    STACK GUARD                        56.8M
    Stack                             113.7M
    VM_ALLOCATE                        52.6G
    VM_ALLOCATE (reserved)             30.4M        reserved VM address space (unallocated)
    __DATA                             71.6M
    __IMAGE                             528K
    __LINKEDIT                        225.7M
    __NV_CUDA                           456K
    __TEXT                            453.8M
    __UNICODE                           544K
    mapped file                        84.0M
    shared memory                        68K
    ===========                      =======
    TOTAL                              56.3G
    TOTAL, minus reserved VM space     56.3G
    Model: MacPro5,1, BootROM MP51.007F.B03, 12 processors, 6-Core Intel Xeon, 2.93 GHz, 24 GB, SMC 1.39f11
    Graphics: NVIDIA GeForce GTX 770, NVIDIA GeForce GTX 770, PCIe, 2048 MB
    Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
    Memory Module: DIMM 2, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
    Memory Module: DIMM 3, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
    Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
    Memory Module: DIMM 6, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
    Memory Module: DIMM 7, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.22)
    Bluetooth: Version 4.2.7f3 14616, 3 services, 15 devices, 1 incoming serial ports
    Network Service: Ethernet 1, Ethernet, en0
    PCI Card: NVIDIA GeForce GTX 770, Display Controller, Slot-1
    PCI Card: pci1095,3132, SATA Controller, Slot-2
    PCI Card: NVIDIA GeForce GTX 770, NVDA,Parent, Slot-1
    PCI Card: pci1b73,1100, USB eXtensible Host Controller, Slot-4
    Serial ATA Device: HL-DT-ST DVD-RW GH61N
    Serial ATA Device: WDC WD1001FALS-41Y6A0, 1 TB
    Serial ATA Device: OWC Mercury Extreme Pro SSD, 240.06 GB
    Serial ATA Device: OWC Mercury Extreme Pro SSD, 240.06 GB
    Serial ATA Device: WDC WD4001FAEX-00MJRA0, 4 TB
    USB Device: Scarlett 2i2 USB
    USB Device: Keyboard Hub
    USB Device: USB-PS/2 Optical Mouse
    USB Device: Apple Keyboard
    USB Device: My Passport 0741
    USB Device: My Passport 0820
    USB Device: USB3.0 Media Reader
    USB Device: BRCM2046 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: Logitech RumblePad 2 USB
    USB Device: Mobile Keys 49
    FireWire Device: built-in_hub, Up to 800 Mb/sec
    Thunderbolt Bus:

  • Performance Issue Premiere Pro CC 2014 with Late 2013 Mac Pro

    Hi all!
    Im working Premiere Pro CC 2014 on a Late 2013 Mac Pro 6 core D700s and 32GB RAM on OSX 10.9.4
    After the 2014 update i have experience some drop frames and hangs with a new 1080p timeline project.
    And it later results in software hang and crashing . even after a quit (force quit) and re-poen, it seems to happen again and again.
    Even after a system reboot seems to be fine at first, but it still crashes on the project.
    Tired to render the timeline and still the same. Also tried to delete rendered file and play right with timeline with yellow bar, same.
    Even drop the preview playback to 1/2 and still..
    files are mixed 1080p footage from Canon 5d3, 60D, T2i.
    I have 3 layers (interview video with different angles) and a title layer (hard subtitle)
    had some light color correction with fast color corrector and a sharpening on the 5d3 layer.
    Ive work with the CC premiere pro before with mac pro and everything is fine and never hand an issue.
    All my memory setting are set for performance and i have open GL on my D700s
    Im not sure if this a software issue or someone my hardware is not working right?!
    Thanks in advance!

    I am having the same issues.
    Im working on a late 2012 iMac, 3.4 GHz Intel Core i7. 32 Gb ram, NVIDIA GeForce GTX 680MX, OS X 10.9.4.
    I'm editing RED footage, about 3 TB worth for this project from a Promise Pegasus drive.
    The software really slows down when using the TYPE tool and also when scrubbing through footage.
    When I attempt to quite the software and restart, the interface goes away but the app is still running but says "not responding" when I attempt to force quit.
    If you've figured it out since then Id love to know what works.
    Thanks!
    G

  • Creating a vignette in Premiere Pro CC 2014

    In another thread, I was criticised for the way I chose to create a frame vignette in Premiere Pro.
    I've always created a vignette using the circle effect on a transparent video layer, inverting it and applying a feather.  The result can be made fairly subtle if you choose, and the vignette I use the most looks like this (applied over white video so it can be seen easily):
    As someone rightly pointed out, the effect isn't GPU accelerated, and with the arrival of Premiere Pro CC 2014, there's a new way to create a vignette using masks, i.e. create a Black Video layer, under Opacity click the ellipse mask, stretch it out to fill the frame, invert it, apply a feather, etc.
    The problem is, I cannot find a set of parameters that create a vignette with this new method that approaches the look I am after.  This appears to be mainly because the mask feather is applied to the entire frame and not just to the circle shape of the mask.  That means you end up with a vignette that looks something like this:
    Notice the black blobs in each for the four corners.  Also notice that the feathering is being applied to the vignette from the outside of the frame as well as from the inside, i.e. the black blobs are feathered towards the edges of the frame as well as towards the inside.
    Of course, you can crank up the feathering to try to remove the blobs, but then the result is that the centre of the frame is now grey:
    I've tried using Mask Expansion to push the blobs further out, but the feathering is still applied to the edges of the frame, so you end up with something like this:
    Looking closely at the corners (although it doesn't seem to show up very well once saved as JPEG), the vignette goes from white gradually to grey, then starts to head towards white again.
    Does anyone think they can find a set of parameters for this new method that recreates a vignette similar to my original?

    Those "edge effects" (where "the vignette goes from white gradually to grey, then starts to head towards white again") are caused by the way that Gaussian Blur handles intersections of the mask with the edge of the media.
    So "making the mask larger then the frame" (as suggested by Ann Bens) unfortunately won't work because this causes the "edge" to be inside the mask, which is the problem.
    But you CAN make the frame larger than the sequence dimensions, and thus avoid these edge effects altogether by using "Motion : Scale" to scale the media (your Black Video Layer) to (say) double the size of your sequence. Now you can create a mask that doesn't hit the edges of the frame, and thus produces no edge effects, and so feathers smoothly all the way out to the edges of your sequence.

  • Premiere pro cc 2014 is crashing due to after effects plugins being installed in the mediacore. Is there a solution to this issue?

    The title honestly says it all. I recently purchased CC 2014 and have been updating and transferring plugins from prior versions of adobe after effects. When installing those plugins as I did in previous versions of after effects none of the plugins were recognized/loaded. I eventually found a solution to this issue by simply installing the plugins into the media core. They have all successfully loaded, but due to their presence in the media core premiere pro is now crashing upon start up. Does anyone know a work around for this?
    Image showing crash:
    Specs:
    OS: Windows 8.1
    RAM: 8GB
    CPU: Intel 5 4670k
    GPU: GTX 980 sc
    Premiere Pro CC 2014 and After Effects CC 2014 are both updated to their most recent versions

    First ... have you checked that these are all updated to work with the CC versions? I'd check with the makers of each plugin, the software has MANY differences.
    Next ... if say you removed all but one, do any of them work? It might be worthwhile to remove them from the folder, then add one by one until you find one that is crashing things. That would at least get you part way forward.
    And ... you might list which ones you have, in what versions. Folks around here might be able to help just seeing that.
    Neil

Maybe you are looking for