Premiere Pro CC 2014 cropping issues

I am trying to create a sequence where I have multiple shots in a single frame. Much like the multiple frames seen in the show 24. I used a combination of crop and position to achieve this effect. It worked flawlessly, that is until I rendered the sequence. Now all my cropped footage has been cropped to reveal a large black space at the bottom of the video frame, as if Premiere cropped even more than I wanted, yet when I adjust it, the unrendered portion returns itself to normal. What is going on here? This is a huge 4K film project and time is of the essence. Anyone else experience this issue? Thanks for the help!

i would do a mask crop and all would look well until rendered out
how I achieved my desired mask crop was to keep the mask crop as it was and also crop the complete image away with either the right or left 'regular' crop. That was two crops - first one Premiere called Mask (1) which I inverted and then 100% crop of the image with the crop tools below that mask.
Not sure if that is proper way, but that is how I got mine to work

Similar Messages

  • Premiere Pro CC 2014 encoding issues due to graphic opacity settings?

    Our marketing team has been working on some instructional video content in Premiere Pro CC 2014 and have encountered issues with encoding the completed sequences. Our output format is HD video with the H.264 codec, 1920 x 1080, 30 FPS.
    The symptom of the problem is that the encoding process cannot proceed beyond 50%, and in some cases, does not start at all. Simply put, we can't encode any videos to completion.
    We think we have isolated the issue, which we initially believed was due to video format differences between the two cameras used to shoot the footage. An EPS logo was present throughout the video with reduced opacity (80%). When we removed the logo, the videos began encoding properly, and to completion. When the EPS logo was included at 100% opacity, the videos also encoded properly and to completion.
    Has anyone else been encountering similar issues in Premiere Pro or After Effects CC 2014? If so, what was the resolution? Is there a known issue with the opacity of graphic assets in video encoding?

    I've occasionally seen problems with say multiple masks & final render-out/exporting, but I've not seen one here on a graphic's opacity causing a problem. It's a very common part of the tool-kit, of course, for most pro/semi-pro editing. Even a lot of amateur stuff.
    Which leads me to wonder what would happen if you created a fresh graphic of some sort, applied it a partial & full opacity, on a SHORT clip ... just to test things. Trying to establish if it's graphic opacity in general as your problem, or this specific graphic and/or its settings.
    Neil

  • Premiere Pro CC 2014 Playback Issue / Crash Mac Pro 2011

    Hi,
    I've been having a big crash issue on Premiere Pro CC 2014, since the 2014.1 update.
    2014.0 has been working fine this year but the update has crashed some of my biggest current projects.
    Programs just starts fine, workspace responds, but anything related to playback just crashes or freezes Premiere.
    My config:
    Mac Pro Mid 2010
    Processor : 2x2,93 6-core Xeon
    Ram : 24Go 1333
    2x ATI Radeon HD 5770.
    I've been reading all major topics on this, this i did :
    - disable Mercury Transmission
    - Flushes Premiere cache
    - Reinstall premiere
    - Updated to Mavericks (issue happened both in 10.9 and 10.10 - thought updating drivers+opencl would help, then again no)
    - Repaired permissions
    - Tried with another user session
    … and so on.
    Nothing yet has solved my issue, anyone to help me on this major trouble ?
    Thanks in advance, best regards !
    Paul

    Hi Paul,
    Try the following:
    Sign out from Creative Cloud, restart Premiere Pro, then sign in
    Update any GPU drivers
    Trash preferences
    Ensure Adobe folder preferences are set to read/write in all 3 locations.
    Delete media cache
    Remove plug-ins
    Repair permissions
    In Sequence Settings > Video Previews, change the codec to one that matches your footage
    Disconnect any third party hardware
    Disable App Nap
    Reboot
    I placed the chief culprits in bold.
    Report back if anything here worked for you.
    Thanks,
    Kevin

  • Premiere Pro CC 2014 RAM issues, audio dropouts and export failures

    So I've upgraded to PP CC 2014, it worked fine for a while. Then I've noticed that while editing audio starts to dropout (I'm getting PP system message in the low right corner). I tried to dig up some info on the subject, but the only explanation I see that after couple of hours of editing PP eats up nearly all of my RAM.
    Any solutions?
    My specs:
    i7-2600K 3.4 GHz
    Quadro 2000
    32 GB RAM

    Take a look at your GPU usage with something like GPU-Z to see if both Premiere versions are using the same amount of MPE GPU hardware acceleration.  Actually with CC 2014 it might work faster because Adobe added in more 4k effects/features for GPU acceleration.
    You might want to download our Premiere Pro BenchMark (PPBM) and run it on both versions.  The H.264 very complex timeline has 4K material in it and usually shows Premiere Pro 8.xxx take about only half the time that Premiere Pro CS6 take to export that same timeline.

  • Multi Cam Flicker Issue - Premiere Pro CC 2014

    Multi Cam Flicker Issue - Premiere Pro CC 2014 can any one help me pls

    Hi,
    This might help :
    Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
    Thanks,
    Rameez

  • ICanon C100 playback issue premiere pro cc 2014

    I am having playback issues in Premiere Pro CC 2014 with footage shot on my Canon C100 (29.97 fps).  It was happening after doing a straight import and creating a sequence using "new item".  Then, after reading some other threads here and elsewhere,  I interpreted the footage so premiere would see it as progressive (no fields) rather than interlaced, but that doe not seem to help.  It is even doing it when I play at 1/4 resolution.  The only solution seems to be to quit and restart and reopen the project.  Then it works temporarily for a little while but not long enough to actually edit.  I have done projects in Premiere with C100 footage in the past and have not experience this level of difficulty.
    My Media Cache is not going to the startup diskc(it is gong to the right place)
    I am on a Mac 2.66 Ghz Quad-Core Intel Xeon
    OS X 10.8.5
    10GB 1066 MHz DDR3
    NVIDIA GeForce GT 120 512 MB
    Please help - very frustrated.  If the solution is to transcode, it sort of kills the value of premiere in many ways.

    Hi,
    This might help :
    Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
    Thanks,
    Rameez

  • 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

  • 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

  • H.264 encoding issues with Premiere Pro CC 2014

    After updating to Premiere Pro CC 2014 yesterday, I see encoding artifacts on my H.264 exports.
    Same source video imported into CC v2014 and v7, and exported using the YouTube 1080p 29.97 fps settings. The artifacts manifests itself as softness/blurriness in parts of the image every few seconds, especially notice the area with a red circle below.
    Here are the source file (GoPro HERO3 Black Edition), the v2014 render and the v7 render.
    Original: https://drive.google.com/file/d/0B2rJe0xgMTxFYXJiMjZpZ0stUzQ/edit?usp=sharing
    CC v2014 render: https://drive.google.com/file/d/0B2rJe0xgMTxFQ1B0Z09GS3I0a1E/edit?usp=sharing
    CC v7 render: Premiere Pro CC.mp4 - Google Drive
    [Version numbers corrected.]
    Message was edited by: Jim Simon

    Mark Mapes wrote:
    This is a known issue introduced in CC2014.0. Some h.264 encodes have blurriness or noise periodically in some areas of the frame. The problem is most pronounced in regions of the frame with very little detail, like grass or pavement--or the T-shirt in the sample frame. We are working on a fix. Before you ask when the patch will be forthcoming, I'm not authorized to even hint at the timeframe.
    Unfortunately, the only real workaround is to export to a format other than h.264. If that's not an option for you, then your best bet is probably to keep working in CC7.2.2 until the patch is released.
    Sorry, but thats not completely true and by far not the correct answer:
    The problems with random artifacts occurred with the introduction of a new version of H264 in CS6 but there you still had the option to export with the previous H264 Version via Media Encoder. 
    Since the previous H264 version is not available in CC, using CC7.2.2 is not a solution either.
    BTW
    Updating to CC and using the new Mac Pros with Mavericks is currently a total mess - no open cl rendering, random crashes, no usable h264 ... thanks adobe!!
    ... but we can track masks in premiere now ... wow!

  • Membership expired issue!!! Premiere pro CC 2014 issue generated from this error

    Hi Guys!
    I have an urgent matter. I keep having this message. I have no issues with the membership since it's paid until may 2015.
    Also in premiere pro cc 2014 I am having this error: this project contained a sequence that could not be opened. no sequence preview preset file or codec
    I've understand that this two problems are related.
    I've also searched the entire google for a solution, nothing out there works.

    Creative Cloud chat support (all Creative Cloud customer service issues)
    http://helpx.adobe.com/x-productkb/global/service-ccm.html

  • Flickering footage in Premiere Pro CC 2014 but not in Premiere Pro CC 2013

    Hi guys,
    I've been having repeated issues with Premiere Pro CC 2014 on Windows. Basically my footage has a weird strobe/flicker when in the suite and when rendered off even although the footage looks fine, unaltered out of the camera. I rendered off the same footage in the 2013 edition of the software and there is no flicker/strobing going on. I've included one of the worst effected shots in CC 2014 and CC 2013 for comparison.I also experience graphical glitches occasionally when rendering. Please watch below:
    Premiere Pro CC 2014 - strobing (300% speed, cropped 15%, RGB curve adjustment, software rendered)
    YouTube
    Premiere Pro CC 2013 - strobing (300% speed, cropped 15%, RGB curve adjustment, software rendered)
    Premiere Pro CC 2013 - no flickering - YouTube
    The footage was shot on a Nikon D3200 at 1080p 25fps, aperture 3.5, shutter 1/50, ISO 400.
    Editing on a
    Dell Optiplex 9020
    Intel i5-4570 3.2 Ghz
    4 gb Ram
    Intel HD Graphics 4600
    Windows 7
    Has anyone else experienced this issue? My suspicion is an issue with either my graphics card or insufficient RAM.

    Thanks for posting that info.  This mirrors the issues I'm seeing with DSLR footage.
    It's so hit or miss if it's going to flicker.  I'll delete renders and re-render and certain clips will be fine, others are now flickering.  I tried to make a test project that demonstrated this issue, but couldn't reproduce the effect.  RGB Curves and Three Way CC are in my list of effects, as well, where I see the issue.
    Just curious, is anyone else working on projects started in other versions/computers?  I've seen it on project started in PPro CC and finished in CC'14.  Saw it again on a project started on Mac in FCP7, converted to CC'14 Win7.  Quite honestly, I haven't been starting projects myself in CC'14 because of the flicker issues.
    As a workaround, I was hoping to import the CC'14 project back into CC or Media Encoder CC, but no luck there.
    Another issue I've had with CC'14 includes converting a CC project to CC'14, giving it to a CC'14 Mac user and the A/V sync is lost.  We abandoned that collaboration all together because of the issues.  CC'14 has been incredibly unproductive to my workflow, despite the great interface update and various other features added.  I haven't had mystery issues like this since CS4.  I'm keeping our post team in CC as much as possible until the issues are resolved.
    -JB

  • Adobe Premiere Pro CC 2014 Crashing very often! Please Help!

    Hello,
    I am currently editing my first feature on Adobe Premiere Pro CC 2014 and it is currently up to date.
    I am editing on a iMac 27in, late 2013 brand new computer.
    Processor: 3.5 GHz Intel Core i7
    Memory 32GB 1600 MHz DDR3
    Graphics: NVIDIA GeForce GTX 780M 4096MB
    System: OSX Yosemite V 10.10.1
    The project is located on a 8TB G Drive
    7200 RPM
    High Performance ThunderBolt drive.
    Details of the project:
    I am currently working on a fine cut of 5K Red Footage that is being cut in the RAW.
    I work at 1/2 quality settings and have no lag.
    The timeline includes limited stacked video files and various mp3 audio files.
    The Problem:
    Lately, the program will randomly quit or freeze up 4-5 times during an 5-6 hour edit session.
    Many times it is random, however, it seems to happen often if I accidentally click on the end of a clip on the timeline and it goes to switch into trimming mode. 
    Also, it will randomly go into the "pinwheel of death" out of nowhere followed by "Adobe CC is not responding."
    My project file is just about 15MB now.
    What is causing this reoccurring problem?
    How can I make it happen less?  I have scoured the forums and found similar articles but no helpful solutions.
    I have recently turned auto save on to save every 2 minutes because there have been more than one occasion where I lost A LOT of work because of this issue.
    I am about two weeks out from picture lock delivery and this issue is driving me crazy and loosing me a ton of time.
    Please help or let me know if any more additional information can help solve the issue.
    I have sent in well over 25 error reports already.
    Thanks,
    Thomas.

    I think I may have found the solution...
    I completely removed the Premiere Pro folder under User > Documents > Adobe and so far it seems to have solved the problem.
    I of course backed up my projects and than deleted this folder. So far it seems it worked.
    I'll know for sure in a day or two, but after constantly crashing, Premiere hasn't crashed for the last 4-5 hours of work.
    Goran

  • What is the problem with Adobe Creative Cloud Premiere Pro CC 2014, why it freezes often?

    I Purchased the Adobe Creative Productive Premium Suite CS5 in early 2010 and I was very satisfied with it all this time, I can say that I never had a problem while using any of the Production Premium applications. Few weeks ago, I asked Mr. Philip Bloom about a technical issue regarding the best method to use a 50 FPS clip with a 23.976 FPS project, and I got his kind help but he recommended me too that I should upgrade to the latest Adobe Cloud CC 2014 which has many new features added to the different programs. I took his kind advice and downloaded a trial version of all the Adobe Cloud CC programs which I use for my filmmaking business.
    Today is the 20th day of my trial period and I have 10 days left to take the decision of continuing with CC 2014 or not. The past 20 trial days were not very pleasant. I want you to share with me the following details which I'll list them as bullet points and I would appreciate diagnosing the problem if you can and suggest a solution for it  to re-try the Adobe Cloud CC 2014 for the 10 remaining days with no further problems.
    I used to have the Gigabyte graphics card GTX 470 for about 4 years and it malfunctioned last year and I replaced it with a humble Geoforce GT 610 card, but it worked fine with the Adobe Suite CS5 programs.
    My system configuration is Intel Core I7   950@  3.07GHz , installed memory 12 GB. , Windows 7 Ultimate, 64 bit Service pack 1, 3 hard drives 1TB. each (one of them is dedicated for Adobe asset files and the editing work)
    For the first 2 or 3 days I used mainly the Premiere Pro CC 2014 establishing short projects for a max. of 5 minutes each and it was working normal. But, later, as soon as I started to build a project which reached about 24 minutes of length and I began to edit those before I add more clips to the timeline, unfortunately, the PrPro CC 2014 started to freeze on any of the frames every time I try to edit normally as I used to do with the CS5, so, I had to wait for 2 or 3 minutes every time it freezes, then it works for seconds then freezes again!!  and during the 20 days mentioned above it crashed once.
    The movie files of my project are the Nikon's .Mov files and the editing work which I performed included effects such as Color correction (levels) color correction (fast) color correction (Auto) sharpen effect, and stabilizing effect.
    I installed the Magic Bullets Suite trial version, and the Neat Video trial version, aiming to purchase either the DeNoiser or the Neat Video (but I tried their effects without saving them to the project).
    I used to export parts/ or whole project before finalizing the editing process to be able to monitor on a TV screen (mp4 file format) some of the changes I made in PrPro before being freezed.
    Based on my previous 5 years experience using the CS5 Suite I have a strong trust in Adobe, I never thought the problem was in the PrPro application, but rationally I thought it was the graphic card (GT610), and accordingly I purchased yesterday a new Zotac Geoforce GTX 770 (listed by Adobe as an approved card) and I installed it and checked that it is running fine and I checked the processor temperature which was within the normal level.
    Only today, I began to think that it might be something wrong with the Adobe Cloud CC 2014 ( a bug or something) and as a result of searching on the internet I could see lot of users since 2014 who were having freezes and crashes with the CC and the CC 2014 versions. That was a shock for me, could it be that until Feb. 2015 the same severe problem still occurs???
    Sorry for any inconvenience, looking forward to seeing a solution for that serious problem.

    Hello Ashraf,
    Sorry you didn't get any help on this post. In the future, please contact Adobe Support for 1-1 assistance on issues like this: Contact Customer Care
    Thanks,
    Kevin

  • How to work on the same project on two machines at the same time and also exchange progress seamlessly using Adobe Premiere Pro CC 2014?

    We are working on a film project on Adobe Premiere Pro CC 2014. Two editors are working on the same film project (same pproj file ) on two machines. As a result the bin structure and the file structure is exactly the same. We even bought two licenses for the respective machines to make matters simple (at least we thought it would).
    Now when we share a sequence between the two machines, every time we have to import and re-link media. Also each sequence import comes with its own set of files, which are actually already present in the project. Basically the new sequences are looking to re-link the media to the original/ source files only and are completely ignoring the file structure present in the project.
    In all editing softwares, timeline/ sequence sharing is a very common practise when working on multiple machines. Why is it so tedious in CC 2014? Every time we share a sequence between the two machines the media gets doubled and tripled in the project. As a result the project file size is increasing perpetually. Already Premiere CC 2014 is extremely laggy and slow, and this stupid bug is making it more difficult for us to finish our work on time.
    Has anybody ever faced this issue? How do we solve it? We are willing to try out any workflow that you can suggest.

    Concurrently working on the same project it requires a specific implementation in all editing programs like Avid's Unity/ ISIS shared storage. That's what you are simply not considering. none of your issues would be any problem if your projects resided on a commonly accessed server or something like that. Check respective hardware solutions.
    Mylenium

  • Premiere Pro CC 2014 crashes when loading project file

    Hi guys, any help on this is much appreciated as I have a job due in 18 hours and I'm in big trouble if I can't fix this.
    I've been editing a project in Adobe Premiere Pro CC 2014 (updated to the latest version) and when I tried to access the same file today it is giving me the error message:
    'Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.'
    I had saved other version files and they all seem to be working properly so I know it's not my HD that is corrupt. In fact my suspicion is that it has something to do with a blur effect i'm using. The only problem is, I can't even access the file to delete the effect as the project file won't open.
    Information about my computer:
    I am using a Macbook Pro
    OS X version 10.9.4
    2.6 Ghz Intel Core i5
    Memory 16 GB, 1600 MHz DDR3
    Any suggestions/comments would be appreciated.

    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

Maybe you are looking for

  • How to Find the file in UNIX?

    Hello Team, I Have below list files and i have to find the file with latest date and time CHECK_300914_200747_xxaa_account_name_20140930195924.txt CHECK_300914_203213_xxaa_account_name_20140930203055.txt CHECK_300914_205625_xxaa_account_name_20140930

  • Standby Database fails to read dictionary from redo log

    hi, I am attempting to create a Logical standby database on same machine as the primary database. I have executed the steps outlined in Oracle Documentation several times, but end up with the same error. Detailes of setup and error are provided below

  • Performances Problem in XI using RFC

    Hi All, I have some doubts about XI performance: Does anybody knows if there is any performance restrictions to do RFC calls to XI ? What's the best performance Solution in XI ? iDoc Adpater or RFC Adapter, File Adapter or RFC Adapter ? Is it possibl

  • Classic WT To Extended WT

    Dear SAP Experts, I am working on upgrade project from SAP 4.7 to ECC 6.0. My client uses the classic withholding tax and they want to go for extended withholding tax. What would you suggest me to configure EWT from first or should I go for Migration

  • WCS 6.0.132 compatibility

    Is this version of WCS compatible with a Controller using 5.2.193? I've checked the released notes and for Controller 5.2.193 it says it needs WCS 5.2.130, but is 6.0.132 WCS also compatible? Thanks in advance!