Incredibly Long Lag Time When Working With Effects in Premiere Pro CC 2014

I am having incredibly long lag times when working with effects in Premier Pro CC 2014. Like 60 seconds or more. This also happens periodically when I am doing something as simple as cutting into a timeline (just ripple deleting from and in to an out point).
I have a MacBook Pro running OSX 10.9.4 2 GHz Intel Core i7 with 16 GB 1600 MHz DDR3.
I have seen that some people are having different versions of the same problem. I do have RedGiant plug-ins, but I am not using any of them in this project. The Red Giant plugs (again, not being used in the project) include MOJO and Universe. The previous version most certainly did not work like this. Any ideas? I did try moving the Red Giant plugs out of the COMMON folder and "alt" starting up to reset preferences. Still having same problems.
A specific example is I have an interview shot. I add brightness and contrast. Just making a change to the effect (increasing brightness) causes freezing of the interface and long delays. I added a piece of transparent video on a top layer to add a CIRCLE to create a vignette effect. Same deal -- ridiculously long times for effect changes to take place.
Does anyone have any clues as to how to fix these problems?
THANKS FOR ANYONE'S HELP!!!!!!!

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.

Similar Messages

Working with audio | Learn Premiere Pro CS6 | Adobe TV

This movie introduces the robust audio tools in Premiere Pro. Abba Shapiro shows how to preview and trim audio in the Source Monitor. Whether it’s an audio-only file or the audio channel of a video clip, Abba shows how to enable sub-frame audio scrubbing and trimming. He also shows how to interpret clips to combine or separate stereo channels. At the same time, he introduces fundamental audio tools that are essential to working with audio in Premiere Pro.
http://adobe.ly/To00IZ

Is it possible to specify what audio channels to capture during capture from tape? It seems Premiere wants to mix the lavaliere mic and camera mic into a stereo track all the time, and then I have to modify audio settings and force it to mono in the project. In Final Cut pro 7, I am able to specify which audio tracks to capture, and this simplifies things in editing. I cannot see anywhere to do this in Premiere....

Transcription Not Working in Trial of Premiere Pro CC 2014

I'm currently in a trial of adobe premiere pro cc 2014 and adobe media encoder. I am trying it specifically for the audio transcription and analysis featureset that final cut pro x lacks.
However, when I go to the metalogging workspace, right click on a clip and under the rename - there is no dropbown for analyze.
Also, when I select a clip and go to the window > metadata and under speech, there is no "analyze" button either. I can't get the transcription featureset to work - and I have used it before on a friends premiere pro cc....
Can someone help me understand what is going on and how I get the transcription working in premiere CC ASAP?
Thanks! - C

I believe that feature is now defunct
Look here Update on Speech to Text functionality in video tools | Premiere Pro work area

Working with AVCHD in Premiere Pro CS5

I'm editing a small promotional video for a new client and they have provided me with the footage. The problem is that I have never edited AVCHD in premiere before. I thought i would be okay as long as I used the AVCHD sequence presets, but I am already running into problems: 1) upon initial import, there appears to be artifacting in the bin footage that was not present when I viewed the raw files and 2) when i try to lay footage onto the sequence, no audio is imported. Someone please help! The footage was shot on a Sony HDR SR5 (1080i, 1440x1080, 29.97 fps, 6-channel compressed 48k audio, MPEG in .m2ts file extension).
Additionally, are there any other major obstacles I risk running into moving forward working with AVCHD?

Welcome to the forum.
Along with Harm's suggestion, make sure that you set up your Sequence with a 5.1 Master for that Audio.
Also, what is the Audio CODEC for that Audio Stream, AC3?
In addition, be sure to allow PrPro time to completely Conform the Audio and Index the file. There is a little progress bar, that will appear. Let it complete 100%.
Good luck,
Hunt

How come I need to render EVERY TIME I apply an effect in Premiere Pro CC?

I am using Premiere Pro CC version 7.2.2 (33) on a 2.9 GHz Intel Core i5 iMac with 24GB of memory and an NVIDIA GeForce GTX 660M 512 MB graphics card. The footage I am importing is ProRes 422 1920x1080 square pixel 24 frames progressive footage.
When I place clips onto the timeline, they play without any issue. In fact, they play beautifully! However, whenever I apply an effect, the clips needs to be rendered. Here's the biggest problem though, every effect needs to be rendered and I don't even need to change the settings of the effect. Just placing the effect on the clip causes a red line to appear above my clip.
Help!?

Kevin,
They do play back. They don't become labored or jerky until I begin taxing the GPU with stacked or complex effects. John T Smith was right on about the hardware deficiency and your insight into my FCP past and red render lines completed the answer for me.
It looks like I'm now in the market for a hardware upgrade.
Thank you, both.
Ephraim

Does Adobe Pixel Bender work with AE CS6/Premiere Pro CS6

Hello All,
I want to create a GPU accelerated video processing plugin for After Effects/Premiere.
I just came across Adobe "Pixel Bender" here:
http://www.adobe.com/devnet/pixelbender.html
It seems to Pixel Bender allows you to code for the GPU in a GLSL-like programming language.
Can I use Pixel Bender in an After Effects/Premiere Pro CS6 plugin?
If not, how do I go about using the GPU in an AE/Premiere plugin?
Thank you very much for any Help,
Sumo B.

I can't speak for Premiere Pro, but After Effects CS6 does not support Pixel Bender directly. However there is a plugin available from AEScripts.com, which allows you to compile and run Pixel Bender kernels from within AE CS6: http://aescripts.com/pixel-bender-kernel-accelerator/
Incidentally, even in CS4 - CS5.5, where PB plugins are supported, they don't use the GPU when run inside After Effects.
Otherwise you'll need to delve into the SDK using C++, which is much more complicated but a thousand times more flexible and powerful, and which allows you to code OpenGL for accessing the GPU.
Christian

Red Giant Trapcode plugins no longer work after updating to Premiere Pro CC 2014.1 (v8.1)

I'm not sure why but after updating Premiere Pro CC to 2014.1 none of my previously installed Trapcode plugins work. I tried uninstalling Trapcode and then re-installing the latest Trapcode update (12.1.6) but it didn't fix the problem. I'm also running Windows 8.1.
I checked the plugin loading log file (\AppData\Roaming\Adobe\Premiere Pro\8.0\Plugin Loading.log) and noticed all the Trapcode plugins had the message "The plugin is marked as Ignore, so it will not be loaded."
So to fix it, I had to manually modify the registry and change "Ignore"=dword:00000001 to "Ignore"=dword:00000000 for most instances of my Red Giant plugins. Everything works now.
Here's all the ones I had to modify:
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\3DStroke.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\HairLines.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\LightFactoryLERender-64.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\LightFactorySpectactularRender-64.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RadiumGlow.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RadiumGlowEdge.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RadiumGlowLite.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RGCornerPin.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RGReflection.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RGSGrowBounds.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\RGShadow.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Screen Text.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Shine.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Smooth Tiler.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Starglow.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Text Grid.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Text Hacker.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Text Matrix.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Text Spiral.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\ToonIt Blacklight Edges.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\ToonIt Goth.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\ToonIt Heat Vision.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\ToonIt Outlines Only.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\ToonIt Roto Toon.aex]
"Ignore"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\TypeOn.aex]
"Ignore"=dword:00000000
-Pete

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

Long estimate times when exporting with EXPDP

Hello Everyone,
I have a few questions about using EXPDP. I'm running Oracle Database 10g Enterprise Edition Release 10.2.0.1.0.
I'm trying to understand whether or not the export times I'm seeing are reasonable. First, I am performing a SCHEMA export, excluding users, grants, roles, statistics, and several tables. When using block estimation, the following operations take 10 minutes to complete for a single schema:
6/7/2010 12:39:39 PM: Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
6/7/2010 12:49:12 PM: Total estimation using BLOCKS method: 512 KB
6/7/2010 12:49:13 PM: Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
6/7/2010 12:49:14 PM: Processing object type SCHEMA_EXPORT/TABLE/TABLE
10 minutes seems completely unreasonable for 6 tables composing so little data. The 10 minute times appears to be constant regardless of the data size. For example, another schema (with about 30 tables) produces the following output:
6/7/2010 12:10:52 PM: Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
6/7/2010 12:20:33 PM: Total estimation using BLOCKS method: 16.08 GB
6/7/2010 12:20:35 PM: Processing object type SCHEMA_EXPORT/TABLE/TABLE
6/7/2010 12:20:36 PM: Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Also in about 10 minutes! I wouldn't expect these times to be so close for about 100000x more data! Why does the estimate take so much time? I would expect the block estimate to be a simple calculation over data the DB server is already keeping around.
When using estimate=statistics, the behavior is even stranger. In this case, the "Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA" operations all take ~17 minutes (regardless of the volume of data in the schema), and the actual export lines in the output (". . exported "test_schema"."table_a" 5.056 MB 5782 rows") complete very quickly (< 2 secs).
Is this kind of behavior expected?
To collect these times, I wrote a small application that kicks off expdp and reads the output along with a timestamp one line at a time. If the tool is buffering it's output, that might explain some of this, though for the block estimate, I see the following output during the table exports, which seems reasonable:
6/7/2010 12:20:47 PM: . . exported "test_schema"."table_a" 2.332 MB 915 rows
6/7/2010 12:22:58 PM: . . exported "test_schema"."table_b" 954.8 MB 32348 rows
6/7/2010 12:23:59 PM: . . exported "test_schema"."table_c" 975.6 MB 60573 rows
6/7/2010 12:24:38 PM: . . exported "test_schema"."table_d" 553.8 MB 973 rows
6/7/2010 12:24:56 PM: . . exported "test_schema"."table_e" 159.6 MB 2562 rows

The command:
expdp 'schema/********@server' estimate=blocks directory=DATA_PUMP_DIR dumpfile=8be7d007-e6c1-4e10-8164-db27d9fce103.dmp logfile=8be7d007-e6c1-4e10-8164-db27d9fce103.log SCHEMAS='schema' EXCLUDE=SCHEMA_EXPORT/USER,SCHEMA_EXPORT/SYSTEM_GRANT,SCHEMA_EXPORT/ROLE_GRANT,SCHEMA_EXPORT/DEFAULT_ROLE,SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA,SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS,SCHEMA_EXPORT/TABLE/COMMENT,SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
The new output:
6/7/2010 4:22:19 PM: Estimate in progress using BLOCKS method...
6/7/2010 4:22:19 PM: Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
6/7/2010 4:29:48 PM: . estimated "schema"."table1" 11.89 GB
6/7/2010 4:29:48 PM: . estimated "schema"."table2" 1.298 GB
6/7/2010 4:29:48 PM: . estimated "schema"."table3" 1.041 GB
Judging by the output, I'm guessing that expdp is buffering the output and my tool is reading it all at once, such that each "estimated" line has nearly the same time. Is there a better way to to timing information from the estimation?
Thanks for the help!

Working with Stills in Premiere Pro

Are others having problems applying effects to stills or is it just me? Practically all the effects I have tried to apply to a still rather than a video have caused PP CS4 to freeze up or just crash. I now always put a still into a sequence first and then nest that sequence to apply the effect. Surely I shouldn't have to do this. I am using PPCS4 on two different desktops and have the same problem with both. Just wonder how common this is?

Really sorry for not getting back to your prompt reply sooner.It had gone into my Junk mail and I only just checked it. I should have been far more specific in describing my problems. I have deleted the project that I was working on so from memory, the problems I had were with firstly the Writeon effect which I have posted on previously and am happy to use the work around of nesting a sequence, although I would still love to see this patched.
The other problems I was having was when I used a shape, created in the Titler , which I used as a Track matte linked to a rectangular shape to feather the edges and overlayed this on a background photo (fairly high resolution) and also used a psd file that I had extracted my subject from to overlay over all the layers below. Sounds like a bit of a mess, doesn't it? Anyway, my problem was that PPCS4 would just suddenly close. No warning, on "How's your father?", just closed.It did this a few times. Once I had finished creating my sequence, I then did not have any problems once it was nested in the main sequence.
This has only happened to me when using stills and thought others might be having similar problems. Next project I will keep more useful notes on my problems so that kind experts like yourself can actually have a chance of making some helpful suggestions.
Very grateful for the Auto Save feature and am trying to remember to push the Save button more often.
Thank you for all your help.

Time remapping in After Effects using Premiere Pro clip

I'm probably losing it cause this should be idiot proof. I watched the Creative Cow tutorial but he must be using an earlier version of the suite.
The problem: I want to remap an 8sec clip and more radically slow down the footage then use the frame blend mode. When ever I dynamic link
the clip into AE and enable time remapping, the program does not give me the two set key frames at the clips beginning and end as the tutorial said it would. Now when I drag the footage to make it longer, it doesn't freeze frame at the end of the clip but instead brings in footage from the source file. What am I missing and is there a manual way to achieve this so that I can remap the premiere clip only?
Thanks for any help.

the program does not give me the two set key frames at the clips beginning and endThat is not true in general. As Mylenium told you, in PrPro and AE you are working in non-destructive way. That means when you replace your short clip in PrPro timeline, the whole footage is still there, but AE composition is properly trimmed according to your PrPro timeline.
When you enable time remapping, AE DOES create two keyframes, but you don't just see them because your original footage is much longer and the keyframes are simply out of your AE comp ongoing borders...

Matrox Mojito Max with GTX 970 Premiere Pro CC 2014

Good day everyone,
I am building a workstation and I would like to ask, if I can use both of the cards, The GTX970 for rendering and Matrox Mojito MAX for monitoring? I know, that Matrox card is hardware accelerating h.264, but is it faster than GTX970? If i can use this combo, how can I set? If i set the Mojito to preview, can I set the Mercury settings in the project settings for GTX970? Will it work? Thank you for respond.

Ask in the Premiere forum.
Mylenium

How do you export a working closed caption for Premiere Pro CC 2014 in .mpg format?

We do weekly 1/2 hour programs that require closed captioning for air. I need to know how to export a self contained .mpg format without using MacCaption. If not possible, is there another, less expensive, 3rd party program that I can use? Or better yet, is Adobe going to create one for us?

Look for the wrench icon in the monitors, above the playback area, to the right. Tooltip for it is "Settings..." -- the menu item is in the flag menu there: Closed Captioning Display...

Date/Time erros when working with Database Connectivity toolkit

Hi!,
We are observing errors with date/time when working with LV. The error occurs when the system datetime format is set such that day precedes month (e.g. dd/mm/yyyy). Our VI uses LV 7.1, Database Connectivity 1.0 and SQL Server 2000 on a Win2000 machine.
Problem details
Our database in SQL server has a table having columns with data type "datetime"
If the system date format (as set in control panel) is "mm/dd/yyyy", the 'insert into database' vi works fine. This function inserts the date and time (among other things) into the above mentioned table.
However, when the system datetime is set to dd/mm/yyyy we start receiving error that date and time is beyond range for dates in which the date had the day field greater than 12 (e.g. 23/10/2005). With the same settings, if the date is such that day field is equal or less than 12 (e.g. 03/10/2005), we do not receive an error but the date is interpreted as 10 March 2005 rather than 03 September 2005.
Clearly LV (or is it SQL) is mistaking the day field as month.
We have taken care that when sending and receiving date, the format date and time string is set as per system settings.
Thus, if system setting is "dd/mm/yyyy" our format string is "%d/%m/%Y"
And if the setting is "mm/dd/yyyy" our format string is"%m/%d/%Y"
Any help on problem cause and cure is welcome.
Thanks,
Gurdas
Gurdas Singh
PhD. Candidate | Civil Engineering | NCSU.edu

Hi Xu,
You answer led me to some very interesting fact finding on how SQL server handles date and time. I have attached a zip file which contains webpages that throw more light on this issue.
The attached pages tell me that SQL has an inbuilt date/time reference format. The default in mm/dd/yyyy. Which explains why my VI worked when I used that format to write to SQL.
However there is a catch:
SQL expects the date/time to be in its inbuilt reference format when you WRITE data to SQL. If the date/time is in a different format, better tell SQL about it by using say the SET command you mentioned.
BUT what about the date/time format when you are reading data from SQL?
Our finding is that SQL sends date/time string in the system date format when you READ from SQL !!! That is very surprising behaviour (why differentiate between write and read?).
Is our finding correct?
So, we adopted the following simple strategy (yet to be fully tested):
1) Whenever we write date/time to SQL, the string is formatted as mm/dd/yyyy. Presently, the user's SQL server is in the default state. Caveat is that if the user changes SQL date/time from default (which is mm/dd/yyyy) to anything else, our software will give errors. But then he changed it ;-)
2) When we read date/time from SQL we format the string as per system date/time format.
I know this is not very robust coding. But assuming the user keeps his SQL in the current setting, should we expect smooth working?
In other words, are there any errors and/or flaws in our strategy?
Thanks,
Gurdas
Gurdas Singh
PhD. Candidate | Civil Engineering | NCSU.edu

After Effect / Premiere Pro CC 2014 Video Importing Conflicts

Why are my Adobe software packages not cooperating? PRes imported out of AE and into PPRO, but no die? Why?
Today I have a brand new MacBook Pro, I also have Adobe CC installed, predominantly for PremierePro and After Effects.
First issue - With ProRes video files exported successfully from Davinci Resolve not being imported into AE. After a few hours of failed attempts, head scratching and searching online I found I had to delete certain files from the hard drive / Quicktime folder (DVCPROHDCodec.component / ApplDVCPROHDCodec.compnent / etc) It seems now that AE has these codecs packaged into the application (?)
Anyway this worked! And I was able to import files in without 'after effects 86. error 4. reading file from frame'. Popping up endlessly.
Second issue - I work on an AE composition & try to export as a PremierPro file from AE, this works and I open with Premire Pro, but some video files on the timeline are missing (?)
So I decide to go the long route and export the composition as a single clip at ProRes from After Effects. I attempt to bring this clip into Premiere Pro and I get another error 'The importer reported a generic error'.
This is highly frustrating, I want to know what Adobe are doing to provide the relevant support for us enthusiastic movie makers and editors. I seem to spend most of my time trying to get my software packages working
with one another than making creative content and this really is unproductive and irritating, especially since these softwares are from the same company.

Go to HD/Library/Quictime and delete all .component files. It appears that the correct procedure is to delete all QT components and everything so far works. I have to do this every time I run after effects or Premiere Pro, and remember to put them back in again after shutting down software. Any ideas why this is happening folks?

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

Incredibly Long Lag Time When Working With Effects in Premiere Pro CC 2014

Similar Messages

Maybe you are looking for