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.

Similar Messages

  • Any way to create extended markers in Premiere Pro CC 2014.1???

    One of the great features of FCP7 was that it allowed us to create extended markers.
    I'm currently viewing a long documentary interview and I'd like to be able to set extended markers rather than simple markers.
    Is there any way to do this in latest version of Premiere Pro CC???

    Hi Ninose11,
    ninose11 wrote:
    One of the great features of FCP7 was that it allowed us to create extended markers.
    I'm currently viewing a long documentary interview and I'd like to be able to set extended markers rather than simple markers.
    Is there any way to do this in latest version of Premiere Pro CC???
    Opt. + drag the marker.
    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

  • Adobe Premiere Pro CC not opening an xml file created in Adobe Premiere Pro CC 2014

    Hello,
    I had created a project using Adobe Premiere CC 2014 which had some minor changes, which were going to be done by my boss, who uses Premiere Pro CC. However the project file of Adobe Premiere CC 2014 was not getting opened in Premiere Pro CC giving a message of type that as this file was created in a newer version of Premiere, it cannot be opened. After searching on this forum I found that we have to convert the Premiere Pro CC 2014 project file to XML file which can be then imported onto Premiere CC. So I created a XML file by selecting File-> Export -> Final Cut Pro XML and sent it to my boss. However even the xml file is not getting opened after being imported onto Premiere Pro CC giving an error of sorts, Cannot open the file since there is a problem with the codecs.
    Have I done something wrong? Please guide me since I am a beginner to the Adobe environment and would very much appreciate any help.
    Thank you.

    Indeed..... but are they fully documented, includuing Adobe's implementation of Multicam?  
    Collapsing them should really be no more than a day or two of work for an Adobe engineer and a day of beta testing.  Seriously.  Lots of people want this - it only takes a few minutes with google to find people struggling with this exact problem.   Premiere Pro Multicam --> Resolve.
    Since we do a lot of multicam work it's something that's important to us.
    Lots of other people never go near multicam, so I guess for them it's something they really don't care about.
    I currently have > 22 hours of multicam sequences that need primary colour correction and follow on grading..... resolve would be the best choice by far. 

  • Premiere Pro CC 2014 (8.0.1.21) crashes when opening or creating a project

    I just downloaded the trial for Premiere Pro CC (2014), and the program keeps crashing every time I open or create a new project. I can idle at the "Startup Screen" but as soon as I open a project the program closes without warning. I've re-installed all Adobe products I have, re-installed the Microsoft Visual C++ Redistributable 2012 and 2013 to get new MSVCR110.dll files (which seems to be the file causing the crash) but nothing is helping. I've also looked in every thread I've found on this forum and a lot of people seem to be having the same problem, but no one had got any answers for how to solve the problem.
    Anyone have a clue on what to do? According to others formatting the hard drives don't seem to solve the problem either.
    Here's the crash log:
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 8.0.1.21
      Application Timestamp: 53c7b17f
      Fault Module Name: MSVCR110.dll
      Fault Module Version: 11.0.51106.1
      Fault Module Timestamp: 5098826e
      Exception Code: 40000015
      Exception Offset: 00000000000740da
      OS Version: 6.1.7601.2.1.0.256.48
      Locale ID: 1053
      Additional Information 1: dac8
      Additional Information 2: dac844fabf0ae09d193ac750f70263ad
      Additional Information 3: 6e8b
      Additional Information 4: 6e8b89b059d1639bd5ba176e9f652c56
    I'm running a:
    Intel i7-3770K, not overclocked
    ATI Radeon 7850, not overclocked
    16gb RAM
    64-bit Windows 7 Professional with Service Pack 1

    Me too with this one have it randomly when just opening the same project and begining to edit
    had it happen about 4 times now.
    Latest update
    Microsoft Visual C++ Runtime Library
    Program C:\Program Fi...
    R6025
    - pure virtual function call
    [ok]
    Adobe Premiere Pro CC 2014.1 has stopped working
    roblem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 8.1.0.81
      Application Timestamp: 5426694c
      Fault Module Name: MSVCR110.dll
      Fault Module Version: 11.0.51106.1
      Fault Module Timestamp: 5098826e
      Exception Code: 40000015
      Exception Offset: 00000000000740da
      OS Version: 6.1.7601.2.1.0.256.1
      Locale ID: 2057
      Additional Information 1: a22a
      Additional Information 2: a22a26525c716a6a7fdf0a84944bf385
      Additional Information 3: 9245
      Additional Information 4: 9245cf38809b383bd6a86e3f052c9114
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

  • Why does Premiere Pro CC 2014 renders incredibly slow?

    Dear Premiere Pro experts
    I created a movie with Adobe Premiere Pro CC 2014 and I have serious performance issues when it comes to export the movie.
    The first 10% renders pretty fast and takes 1 hour. Then it takes for every additional 1% about 4 hours! (never rendered it to finish so far, 14% max so far)
    Here are some facts that might help to isolate the problem:
    Project:
    Length: 24 minutes in total, splitted into several sequences (up to 4 minutes) and arranged on a "main-sequence"
    Input: Cineform AVI files, 1080p, 59fps (I converted GoPro 3+ footage (3D!) using GoPro Studio to the Cineform format for further processing)
    Desired Output: Same as input, preserving 3D (Render 3D Intermediate)
    Effects used: Warp-Stabilizer (default settings) and Auto-Color (smoothing 1-2 sec) on almost every clip.
    Hardware / Software:
    i7-3770K @3.5 GHZ (Quadcore)
    16 GB RAM
    NVIDIA Geforce GTX 970 (also tried with a ATI Radeon R9 290X)
    Windows 8.1
    SSD for OS and programs, RAID 0 for media files and project, separate drive for rendering output.
    Then I tried to render using AME using the same settings. The whole video rendered in about 14 hours what is acceptable in my case. There problem here is that the 3D gets lost, even if I selected "Render 3D Intermediate". The picture for the left eye is the same as the one for the right eye. This is not happening when I do a direct export. But the direct export get almost stuck at around 10%.
    There is almost no difference in choosing Software-Rendering and GPU. Also, the GPU has almost no load. Premiere Pro uses the CPU for about 45% (total usage 65%) and takes up 5-9 GB of memory (total usage 65%). Disk usage at around 14b/s.
    I think there are two problems. One is that AME renders differently (no 3D) and the other is that the direct export takes way too long.
    Can someone help me with any of these problems?
    Thank you,
    Martin

    I did some additional research and found out, that the slow rendering happens with this combination:
    - Auto-Color using Temporal Smoothing
    - Render 3D Intermediate
    Without rendering the 3D intermediate, Temporal Smoothing is not a problem. And without temporal smoothing, Rendering 3D Intermediate is not a problem.
    Might this be a problem in the codec or in Premiere?

  • 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

  • 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.

  • Exporting to Media Encoder crashes Premiere Pro CC 2014

    Greetings,
    I am experiencing a problem with premiere off and on. Right now it is an on problem. When I am exporting from Premiere Pro CC (and CC 2014) it will intermittently crash Premiere. I have tried this with several different audio and video formats (AVI [Lagarith and uncompressed], WAV, H.264, MPG2, AAC, etc). At the moment, every time I go to export to queue it locks up and hangs on the "Preparing data for export..." Media Encoder Launches and then it just freezes. I get "Problem Even Name: AppHangB1" over and over. Sometimes a full restart will fix this temporarily and sometimes it goes away for a long while. I managed to get a few sequences exported and then it just kept freezing on every PP CC restart.
    Here are my system specs:
    Premiere Pro CC (up to date)
    Win 7 64bit (up to date)
    i7 970
    24GB Ram
    NVIDIA 470GTX (driver up to date)
    3 x 1.5TB internal
    4TB internal
    3TB internal
    12TB RAID 5 via USB 3.0
    USB 2.0 and 3.0 drives
    FireWire audio device (M-AUDIO FireWire1814)... although, I am not using it for playback. It is connected.
    Footage is from C100 H.264 .MTS, H.264.mov from 7D, and H.264 .MOV from iPhone.
    All stock video plugins with a few third party audio plugs.
    This problem happens with and without third party plugs, but it happens that this project uses them.
    I have chatted with Adobe help twice about the matter and nothing has come of it. Log out, log in = same. Restart = same (sometimes), create new user account = same, and so on. The only thing I haven't done is completely re-install premiere, which seems a bit overkill. One of the reps said he would get back to me in a few days after he watched the issue via screen share. Never heard back.
    I get the sense that this has something to do with PProHeadless.exe not launching or not running properly. When the crash happens on a fresh restart of PP CC 2014 PProHeadless is not running. I can start PProHeadless and it will send sequence to media encoder. When I try to export another sequence from the same project it crashes and I see another instance of PProHeadless launched.
    Also, once the projects are exported to Media Encoder, I can encode them to any format with no problem. The problem is getting the sequences there!
    Is there anything that I am overlooking here?
    Thanks for the help!

    Hi
    Premiere pro cc 2014  8.0.1 (21) build
    Encoder CC 2014 8.0.1.48
    I use CC for Teams so it updates all the time.
    Again when I tried to use it today by letting premiere open it by sending an output into Queue it crashed both Encoder and Premiere.
    In order to shut down Encoder and Premiere I had to go into Task Manager and "End Process Tree" on everything adobe I could find because just ending Encoder did not work it would not close. I remembered that years ago when Premiere would crash we had to end a photoshop process. I found photoshop open even though it was not "alive" on my task bar. I had used it yesterday but had closed it. I also had to close dynamiclinkmanager.exe *32 as well as one of the three Adobe CDF Helper.exe*32. They popped back on but Encode closed and then I got a message that Premiere needed to close and did when I clicked the button to let it close.
    After all this I re-opened Encoder by itself and checked the Preferences finding that Import Sequences Natively option was again checked.
    By the way for me, "Launch AME manually, then drag the sequence from PPro's Project panel to AME's Queue (or to a preset in the Preset Browser). That uses a different code path than the File>Export>Media workflow." won't work most of the time because I do live events of panel interviews that may run 2 or more hours. I need to break them down to chapters for the web
    Also I know this isn't part of this problem but I and many others would still love dynamiclink to work to Encore because the DVD is not dead yet. The current work path is a drag.
    Looks like some programers and engineers have some work to do.
    Thanks
    Dennis
    My computer:
    Self built PC windows 7 Professional 64 bit Build 7601 SP 1 I use auto update so it is up to date.
    ASUS P6x58D Premium Motherboard
    Intel (R) Core i7 930 @ 2.80 Ghz
    Installed Memory  12 GB
    NVIDIA GeForce 9500 GT
    NVIDIA GeForce GTX 580
    2 Apple Monitors and a HP full HD Monitor
    With a BlackMagic Intensity Pro Capture Card

  • Premiere Pro CC 2014 TickTime Crash FIX (in some cases)

    In my experience so far, Premiere Pro can return a TickTime.ccp error in several different situations. In some instances (too much Warp Stabilizer) just clicking okay a gazillion times is a usable workaround. In a case I had recently, Premiere Pro CC2014 crashed completely every time I tried opening the project file and all its autosaved versions. Here's a description of what I figured out to be the problem and how I solved it.
    My project file was created in CS6, then edited in CC2014 on a Mac, then Windows. After this the crashing started on both Mac and Windows version of Premiere Pro CC 2014.
    Symptoms:
    An error message pops up on opening project [..\..\src\TickTime.ccp-290]. Clicking okay brings up another more serious one about a Serious Error and PP needing to close. Then it dies.
    The problem:
    Somewhere between CS6 and CC2014, Adobe seems to have changed their XML file structure from using a comma as decimal separator to instead using a period. Somewhere within my project file, Premiere left one as a comma.
    My fix:
    1. Make a copy of your project file and change the extension from ".prproj" to ".gz"
    2. Use something like 7zip and extract the file, this should give you a new file with no extention.
    3. Edit this file in a text editor (I'd reccomend Notepad++ or TextWrangler, but Notepad and TextEdit will also do).
    4. Search for the term <PlaybackSpeed>. Most of your clips would have a numerical value of 1 directly after this, referring to a playback speed of 100%. Click Find Next a few times and look at the numbers following the selected bits. Anything that is not a multiple of 100 will be a decimal number, that should look like "0.5" or "1.2759984", (referring to speed values of 50% and 127.59984% respectively). If you see a comma, replace it with a full stop. My project had a value of "0,8845" I had to change it to "0.8845"
    5. Save the file, and using 7-Zip, compress it into a new gz file.
    6. Change the ".gz" extension to ".prproj" and you should be set to continue your edit.
    If you didn't change the speed of any of you clips, chances are this is not your problem.

    Hi Karel,
    Thanks very much for writing this up. I hope this helps others having this issue.
    Thanks,
    Kevin

  • Premiere Pro CC 2014 Crashing on Start Up

    After installing Premiere Pro CC 2014 on my mac i opened the app but with in seconds of opening its crashed with this message '[/cloudroom/releases/2014.09/shared/adobe/MediaCore/Utilities/QTParser/Src/QTTrack.cpp-5 08]'
    It does this every time i open the app. Any ideas?

    Hi Nerd03, I have a similar problem on Windows which could relate to the issue discussed here:
    https://forums.adobe.com/message/7026671#7026671
    Do you get a starting screen or does it crash before you are asked to create a new project or open an existing one?
    I filed a bug report for mine on the Adobe bug form. Maybe worth monitoring the other thread for any news on this.

  • Premiere Pro CC (2014) crashing when making a sequence

    I just did a clean install of OS X Yosemite and installed Creative Cloud on my 2008 MacPro. Every time I make a new sequence or open a saved Premiere Pro CS6 project, Premiere Pro CC 2014 always crashes. I am not sure what is going on because before I updated OS X from Mavricks, I used Premiere Pro CS6 with no issues at all. Please help! Thanks!
    Here are my MacPro settings:
    Here are the errors I am getting:
    That blank space usually says this:

    Ok I have seemed to "fix" the problem. I have two video cards on my MacPro:
    I have a three monitor setup with two monitors on the 2600 XT and a single monitor on the 6870. I unplugged the two monitors on the 2600 XT and created a new sequence and it didn't crash. Not quite sure what is going on with this because this was never an issue while I was running Adobe Premiere Pro CS6. I still do want to run a three monitor setup but the 6870 doesn't want to support three monitors. Hopefully there is an update from Adobe that will fix this issue.
    Is there a way that Premiere will not try to use the other video card?

  • Premiere pro cc 2014 crashing my system

    I have a new Mac book pro (2014) 16 gbs ram.. everything is upgraded to max. downloaded the new premiere pro CC 2014. and it's crashing my system every time.
    it takes about 4 mins. with the spinning ball. Then all the processes and plugins load in.  Then it says "premiere pro couldn't find any capable video play modules. Please update your video display drivers
    and start again" WHICH IS FREAKING IMPOSSIBLE SINCE I AM ON A MAC BOOK PRO. So sick and tired of companies not working out glitches in this crap. Could someone please help. I am so
    angry and frustrated here.
    Sean

    Somewhat figured it out and extremely frustrated.
    I created another new user with administrative privileges. When i did this i got AE CC 2014 and Premiere Pro CC 2014 working. However, they will not work in my regular main account which has
    administrative priviledges.  On the phone with ADOBE they told me that it was a permissions issue and that it was Apple's Problem. Which I CALL B.S.!!!
    I tried to repair permissions in disk utility knowing full well that it wouldn't fix the issue. How on earth would apple know what the permissions errors in folders or files are for Adobe products!!
    I was very angry and upset with the Adobe technical support for this issue.
    On the new mac pro i am using i was able to create the new administrator account and erase the old administrator account since i have 0 documents or old data that i have on it other than programs.
    However, on my mac pro. I have well over 15 years of data on it including 100 GB of music, etc... that i simply can't just erase away.  Not too interested in working on 2 different accounts either.
    Not sure what to do now and i am extremely frustrated.

  • Adobe Premiere Pro CC 2014.2 (8.2) freezes up constantly on Mac OS X Yosemite

    After the latest update (no idea which one but the latest update) Premiere Pro cc just keeps freezing up constantly. There's no indication what brings it up but after different periods of time I just get the apple wheel and the entire program freezes up. I force quit and get the "sorry, a serious problem has occured", blabla. Sometimes it's in the middle of cutting a clip, sometimes it's while trimming. There isn't a single indication what causes it. At first I thought it was only because of using a multicam clip, but that's not the case anymore. I tried reducing memory to other apps, deleting preview files, deleting autosaves, turning off autosave altogether, deleting Adobe Premiere 8.0 preference file, changing permissions, basically everything in this post: Re: Adobe Premiere Pro CC keeps crashing... (Which now also seems totally neglected by Adobe).
    Believe me, there's hardly a thing I haven't tried.
    It's getting REALLY frustrating now and it's time something is done about this. Yes I know, "don't just say it's frustrating, explain the problem", but that fase has passed now. I'm paying for this product and it needs to work like it should.
    Also I know I'm not the only one who's having these problems.
    My specs are:
    OS X Yosemite 10.10.1
    MacBook Pro (Retina, Mid 2012)
    2,3 GHz Intel Core i7
    16 GB 1600 MHz DDR3
    NVIDIA GeForce GT 650M 1024 MB

    Hi JJ,
    JJ Millen wrote:
    It is not about the past times you may or may not have participated, but about the latest message from rob654 and my last messages in that thread (which are clearly not about Windows).
    One great reason to get a Mac only version of the post. It is never a good idea to post on a Windows post with Mac problems. And when threads get so long and unruly, the team can't focus on the actual issue so it doesn't get the attention it needs.
    Now that we have that sorted out...
    JJ Millen wrote:
    I checked that and it says 8.2.0. (65) build.
    Thanks for the verification. You are running Premiere Pro CC 2014.2 (8.2). It helps to have that absolutely clear.
    JJ Millen wrote:
    Here are all the checkpoints mentioned in that thread, applicable to my project:
    - Version 8.2.0;
    - My Creative Cloud says Premiere Pro is up-to-date;
    - Operating system is OS X Yosemite version 10.10.1 (14B25);
    Very well, did things operate any differently on Mac OS X 10.9.x? Or did you have the same problem?
    JJ Millen wrote:
    Type: MPEG Movie
    File Size: 4,0 GB
    Image Size: 1920 x 1080
    Frame Rate: 25,00
    Source Audio Format: 48000 Hz - 16 bit - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Total Duration: 00:12:35:16
    Pixel Aspect Ratio: 1,0;
    So is this H.264? What is the camera that you are working with? DSLR?
    JJ Millen wrote:
    - I do not get any error messages, except for the "Sorry, a serious problem has occurred"-message after I have to force quit my Premiere because of the freeze;
    What kind of drives are the media files stored on?
    Are the permissions set correctly (as Read/Write) for the Mac HD and your media drives?
    Are the permissions set correctly for all the Adobe folders as I outlined in my blog?
    JJ Millen wrote:
    - The problem mostly occurs when cutting a clip with the razor tool, regardless of the kind of clip;
    When you import clips, are you using File > Import, or are you importing via the Media Browser?
    JJ Millen wrote:
    - Yes this has worked before, the problems started either after creating a submix (which I've deleted, without result) and/or after updating to a newer version of Premiere CC;
    Definitely do not update Premiere Pro or OS X when in the middle of a project. Wait until it's complete. If you did either or both of these things, you can cause your project to become corrupt. After your current project is wrapped, test with a brand new project.
    JJ Millen wrote:
    - The only software I run actively besides Premiere is Apple's Mail program, Safari and/or Chrome, sometimes Wire, sometimes Spotify;
    - I currently have no third-part effects or codecs installed in Premiere;
    - I installed the latest CUDA Mac Driver, version 6.5.37 (release date 01/14/2015);
    - The problem just happens while working in my sequence, not in any final output. I don't know what is meant by "previews", but I have the yellow bar indicator in my sequence, if that's info you need.
    I have heard of others having issues with OS X 10.10 and NVIDIA GPUs. My advice is to consider downgrading your OS if you continue to have issues. I believe I have avoided a lot of trouble by sticking to OS X 10.8.5.
    Previews AKA the Media Cache are your "render files." They can become corrupt, so it's a good idea to trash them when troubleshooting. You can locate them via your Preferences > Media. Click the Browse button.
    JJ Millen wrote:
    Okay I went through that menu (which I'm not eager to do, I prefer direct contact) and came across the CUDA setting inside the project settings. I've now enabled the "Mercury Playback Engine GPU Acceleration (CUDA)", which might help.
    So were you set to "Mercury Playback Engine Software Only" or "Mercury Playback Engine GPU Acceleration (OpenCL)" prior to changing it to "Mercury Playback Engine GPU Acceleration (CUDA)?
    JJ Millen wrote:
    Testing with a brand new project is not an option. I have a deadline for my current project and it's impossible to start from scratch. What I did try is start a new project and importing the existing one, which didn't help so far.
    I was just wondering if you experienced the same issues in a new project. Any project you update to a new version is suspect, in my opinion. In the future, try to avoid doing that. If your current project is corrupt, I could see why you are having certain issues.
    For what it's worth, we had another user that exhibited similar issues until they started with a brand new Premiere Pro CC 2014.2 (8.2) file.
    Since importing your 8.1 file to a new 8.2 project isn't working, make sure to triple check permissions on all the Adobe folders I laid out in my blog post: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
    It's the #1 reason Mac users experience freezing and crashing. The other one I'd look at is that NVIDIA drivers are not working well with Yosemite. Finally, if you update a project across versions, it can become corrupt. Not much you can do about that except start a new project ASAP.
    Thanks,
    Kevin

  • Adobe Premiere Pro CC 2014 compatible with Nvidia 970 GTX?

    Good afternoon.
    I'm an owner of a GIGABYTE Nvidia 660 GTX Ti OC 2GB. The card is detected by Adobe Premiere Pro CC 2014 (Even though,i think,it said that it's not listed or something but will work under my own risk..Is there a way to check if it's certified/supported via my own program and NOT the typical "This is the list of supported GPUs"?)
    Anyways,i was thinking of buying one of the new 970GTX cards to game on better,but also to make full advantage of it's properties to do much more faster encoding/exporting (you know,create a H.264 MP4 720p@29,97FPS file) than my actual 660GTX card with Adobe Premiere Pro CC 2014.
    The thing is,any owner of such card (GIGABYTE,MSI,doesn't matter) have tried to launch Adobe Premiere Pro CC 2014 and export stuff by using the GPU's full potential to make everything faster?.. Because i have this fear of "Getting the newest n greatest Nvidia card so far and in the end see/notice it'll not work with Premiere Pro CC 2014"
    ....Can somebody please help me with this big fear of mine,please?
    Thanks in advance
    DV

    Locked... duplicate discussion... see GTX 970 and Premiere Pro

Maybe you are looking for

  • How to properly embed album art work into TV/Films itunes: home sharing lag

    My setup is a simple apple home sharing network. I have a mac mini running OS X 10.6.8 and itunes 11.0.4(4) it hosts a lot of music, DVD's that have been re-encoded and paid for content from itunes. The mac mini is conntected to the network over a ve

  • Error while configuring TMS in SAP (3 system Landscape)

    Hi, We need to replace our quality server with a new one.While configuring TMS,with the new replacement of our quality server,we are facing an error. Our development server is the domain controller and we have added our new QA and then deleted the ol

  • -Frustrated :  Multiple iPod Problems

    I've been attempting to fix several issues with my girlfriend's iPod (30Gb 5gen) which I gave to her for her birthday, with no success. #1 Files purchased from the iTunes store will not transfer directly into the iPod. When doing so an error message

  • Difference between web reports created in WAD & Visual Composer

    Hi All, Can anyone tell me 1.The Difference between web reports created in WAD & Visual Composer. 2.The Webreports created in Visual Composer is availble for normal users(users not having Visual composer). 3.how to create web reports & Publish using

  • Rating issue with explorer only

    Hi, We're having issue with IE 8-10 and "Ratings" on every page that hold them. Problem description: 1. Open some page containing Ratings (EnterpriseWiki layout if you may) 2. Ratings at the right side won't show pics (small stars) 3. After refreshin