Slow project

I am working on an HDV project that has a 45 minute sequence. There are a lot of video clips and motion clips and after a while the computers starts slowing way down. It gets to the point where every move I make no matter how simple requires the computer 3 to 5 seconds to perform. There also seems to be a lot more problems requiring me to either restart FCP or the computer itself. Is this because the project is too big or what?
Thank you
Vince

No way of knowing whether the project is 'too big', but is the sequence divisible into segments? Sometimes, if you do that, and work on the small segments separately, it will avoid such slowdowns.
If that isn't easily doable, then take a look at your project to see if there are sub-sequences loaded in the Canvas that you don't need to work on. You don't have any nested sequences in the main sequence, do you?
What about stills? Do you have a lot of stills? Maybe increasing the amount of RAM devoted to stills would help. That's in System Settings > Memory & Cache.
How large is the project file, BTW?

Similar Messages

A Very Slow Project!

I have one project - a normal, four-minute song with maybe sixty tracks - running on 8.0.2 in 10.5.5 on a 2 X 2.8 Quad-core machine, and I keep getting incredibly slow responses to simple commands, with the accompanying spinning ball. All other projects work fine, though plenty are larger - it's just this one song.
Any ideas on what steps to take to troubleshoot this? Everything I normally would do - trashing plist, repairing permissions, testing memory, etc. - apply to the whole operation, which is purring along just fine. It's just this song!
Thanks in advance ...
J

Thanks for getting back, Sample... Any command - put track in or out of Solo mode, for example - elicits a LONG pause and the spinning ball. Commands that would normally take less than a second take up to twenty, but only on this project.
I am starting to suspect some kind of link to control surfaces, because I did get an error notice regarding cs prefs being corrupted. However, when I try to trash those prefs, Trash sends me a notice that the cs prefs are in use and cannot be thrown out. Any ideas on how to trash them and rebuild?
Jason

Slow project opening

Using Premiere CS3 with 8 hours of HDV files captured in HDVsplit (m2t).
When I open the project it first looks good, then right at the end of the progress bar it slows right down and can take up to 15mins (!!!!) to load?? Happens everytime with a myriad of different configurations. Seems to be busy 'indexing' files...
Any help would be greatly appreciated....
Athlonx64(2.4ghz)
4gb ram (800)
SATA drive (100mb/s)

To throw my two cents in,
I've learnt to except this sort of time lag, for me it is a bit less though. You've just got to use this time to your advantage, get down, get ready and start, then take a five minute coffee break - that's the way to do business.
Seriously though CS3 is a siht hot product, don't be cruel and just except that it takes the little Adobe umpa lumpa's in your hard drive a while to wind up the rubber bands. Help 'em out by making sure your system is optimised -http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402169&sliceId=1

Slow Project Server with Project Permission Mode

Hi,
I have a Project Server 2013 Installation with Project Server Permission Mode.
The Sharepoint 2013 topology is composed of one application tier, one searh tier and two web fronts.
The issue is that Project Server is responding slowly especially when it is about to :
- logon
- display security groups (AddModifyGroup.aspx).
I enabled the development dashboard and I turned on network mon to follow any suspect communication but nothing seems to be related to this slowness.
Any Help ?

You can also review the Hardware and Software requirements http://technet.microsoft.com/en-us/library/ee683978(v=office.15).aspx by verifying the datasets from http://technet.microsoft.com/en-us/library/fp161198(v=office.15).aspx
Also please check if the Distributed Cache Service is running on the server where the Project Server Services are running http://technet.microsoft.com/en-us/library/jj219572(v=office.15).aspx
You have also mentioned that Search is configured in the farm. Is Project Service running on the server where Search is configured? If Project Services is running on a server where Search Services is also running it would be good to check if the server is
running out of memory when Crawl is running. (Look for noderunner.exe in Task Manager)
Cheers! Happy troubleshooting !!! Dinesh S. Rai - MSFT Enterprise Project Management Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can be beneficial to other community members reading
the thread.

Very slow project "updating" - Is this unavoidable?

Hello, we're migrating a fairly large application to BEA and having problems with long wait times when the project is rebuilt using Workshop.
The project uses servlets/xsl, entity beans and session beans and connects to around 100 database tables.
We're developing using Workshop and we have a distributed team with members in Seattle, New Jersey, Mexico and India. The database is Oracle and is located in New Jersey.
The problem is that for our team members in India, it is taking up to 8-10 minutes for the project to "update" after each rebuild. If we use a local database, this update time is eliminated. But due to security concerns, we cannot allow for each developer to have his/her own local database.
Does anyone have any ideas for how we might reduce this "updating" time? I believe what is happening is that after each project build, the entity beans are being re-initialized, and this takes a long time with a remote database.
Any help or suggestions will be greatly appreciated.
Our last app server (which wasn't fully J2EE), allowed us to update a single entity bean, or a single servlet and we did not have to wait so long for the project to build/update. The app server we had been using is now over 5 years old, yet strangly it allowed for much faster iterative development that Workshop/BEA As far as I can tell, quick interative development just isn't possible with our particular project/environment.
Thanks

Hi Stephen,
Which Service pack are you on ? please upgrade to the latest service pack, which is SP6 for best performance.
You should look into setting up the iterative build in cases where you can do so.
Regarding the performance issues with teams in different regions. I'm unsure if there is much which can be done to increase responsiveness.
One thing you could try is to delete the temp files on the machine by running the following command
cd /d "%TMPDIR%"
for /D /R %%i in (wlw*) do rd /s /q "%%i"
for /D /R %%i in (jave*) do rd /s /q "%%i"
for /D /R %%i in (jws*) do rd /s /q "%%i"
for /D /R %%i in (xbean*.d) do rd /s /q "%%i"
How many projects do you have in your application and what type of projects are they ?
cheers
Raj

Help for slow projects

As an Advanced Distributed Learning (ADL) administrator I
have been having trouble with some of my instructor developers
having a very slow, and there for unproductive, running of
Captivate 2 on some of my instructor/developer computers. I run the
same laptop they are and have no problems. I found the difference
between the two computers was in the system properties.
--Right click "My Computer" chose "Properties" the system
properties window will open.
--Chose the "Advanced" Tab them click the "Settings" button,
the "Performance Options" window will open\
--Under the "Visual Effects" Tab select custom
-- Uncheck all of the boxes except "Show window contents
while dragging", "Smooth edges of screen fonts", and "Use common
tasks in folders.
Prior to these changes a simple task such as dragging text to
a new position took 6 to 10 seconds to get a response and dragging
the timeline items was near impossible.
For those interested we are running Captivate on Dell
Latitude D-800 laptops with 1.70GHz Intel Pentium processors and
1.00gb Ram,1.70GHz
Any additional recommendations out there would certainly be
welcome.

While this will speed up Captivate performance, be aware that
it also changes the "look & feel" of Windows XP. If you are
trying to capture that, this could be problematic.
A good tip if you are not concerned with replicating the look
of the standard XP theme.

Ultra slow project load time

I was wondering if anyone else has encountered this problem and can point me to the solution.
After capturing 40+ hours of footage in a new project (log and capture only), every time I try to load the project it's a 10-minute affair.
I'm wondering if I'm low on memory (see 3GB and other specs below) or if it's my Firewire 800 LaCie drive. All the clips are either HDV or DV (NTSC), so nothing out of the ordinary.
If I need more memory, I'll get it. Just want to identify the problem and not throw money at random solutions. Any help would be appreciated.

Well...I broke. After waiting 20 minutes for the project to load up (for about the 25th time), only to do 'spinning beachball' every time I try to work with the project, I've decided to start the capture over again Hello, 40 hours of re-do capture time.
This time, all project files and media will be captured/stored on my CalDigit S2VR Duo drive (thanks Shane for the nice review and why I went this direction instead of G-Tech). Hopefully, this problem won't rear it's ugly head again on the new striped RAID drive.
I can only assume that it's one of two things: (1) I had some bad media in the whole mess and it's freezing the system when trying to access the project and relink video clips/files or (2) maybe the LaCie drive is on it's last leg. I don't know, but in the long run, it may take just as long (with the frozen state of the project) to figure it out as it will to recapture.
I will post back with an update once I've reached the 'old' video capture point on the new project file (on the new drive).
And before someone asks, the Media Manager was working just as slowly as the loading of the project, making it impossible to try and re-capture the project onto the new drive through FCP.

Slow project load

Hello,
Does anyone have any experience of RoboHelp HTML taking an
excessive length of time (over half an hour) to load a project? I
have a colleague who has a project of similar size that takes a
couple of minutes to load. Is there any way to identify the cause?
Thanks,
Alan

How big is the .cpd file?
If it is large, take a back up of the project file, delete
the .cpd file and try opening the project via the .xpj file. You
may see a significant reduction in the .cpd which can get a bit
bloated.
Kind Regards
Craig

Slow Saving Times in After Effects CC

Hi all,
I'm experiencing some really slow project saving times in After Effects CC. I'm used to having projects save in under two seconds in AE CS4, but AE CC is taking up to ten minutes to save a project of comparable size and complexity!
After reading a few threads about this potentially being caused by big project files and/or Warp Stabilizer, I thought I would just have to live with the long save times. But, I have since started another project that isn't using Warpy, and the saving time is no better - possibly even worse.
Any help would be greatly appreciated.
My computer specs:
Windows 7 64bit
Intel Core2Duo @ 2.5GHz
4GB RAM (AE uses 2.5-3GBs)
GeForce 8600M GS
Project specs (with Warpy): 4-6 main comps and around 25-30 precomps, 1080p, Warpy is used on maybe 5 short layers. Project file is 21 MBs.
Project specs (without Warpy): Around 10-15 main comps, and 5-10 precomps. Various comp definitions, ranging from 500x500 to 5100x3300. Project file is 3MBs.
Thanks!

Look at post #7 in the thread I previously linked to. Here's a direct link to that post: http://forums.adobe.com/message/5508252#5508252
There's currently a bug in After Effects where a file on your software drive is being checked any time you access a menu, use a keyboard shortcut, etc.
With your system drive (which I assume is what AE is installed on) being a slow, 5400 RPM laptop drive, I'd say this is the culprit. As Todd mentions, there could be a fix released. In September. If you're lucky. [Fail.]
You'll have to either run AE from a faster drive (probably not an option if you're on a laptop), wait until September, or go back to CS4.
I've not encountered the problem myself, but my system drive is super-fast: a SATA-3 SSD with 500+ MB read and writes.

Error Adding Old MS SourceSafe Robohelp Project Back to SourceSafe

Hello fellow Robohelp Gurus!
I was hoping of you smart and brave souls could help me out
with a pending issue!
Basically, I have a Robohelp X5 Project I USE TO have in
sourcesafe. I removed it from Sourcesafe for several months, but
would like to re-add it now. Unfortunately, every time I try to add
the project to Sourcesafe, it gives me an ERROR!
The error reads: Failed to create database at C:\XXXXXX, and
refers to data\aaaaaaaa.cnt
Database Creation Failed.
What is the data folder and why is it referencing this
specific cnt file? Any luck or ways to bypass this? Can I simply
remove that file? Please advise, if possible!
Any assistance in this is greatly appreciated!

I am not familiar with Visual Source Safe but my xperience
with MS SQL Express might (or might not) help.
I use RoboHelp HTML 6 with RoboSource Control 3 and MS SQL
Express 2.5. At one point, my project froze. I could no longer
check files in or out. Many attempts to remove the project from
version control failed. I finally succeeded after I deleted a file
using Windows Explorer. I also deleted the database in MS SQL
Express. The result was that my project worked but I no longer had
version control.
Since things were working, I returned my project to version
control. Immediately, my project was frozen again. To me, it looked
like I was adding a new project to version control. However, my new
project had the same name as before and the same problem as before.
I tried removing and adding to version control two or three times
before giving up.
Having no other ideas and having nothing to lose, I renamed
my project before I returned it to version control. Amazingly
enough, this small change made a difference. The project now
worked, although, very slowly.
I searched the forum. There was a post about slow projects
and XPJ files. Apparently, an XPJ file is updated when a file is
deleted in RoboHelp. Since I manually deleted a file outside of
RoboHelp, an XPJ file hadn't been updated. XPJ files are text files
with a simple format that inventory various files in a directory. I
checked all of my XPJ files and found one that was out of sync with
the contents of that directory. I updated that XPJ file and the
project has been working at normal speed ever since.
Even though we are using different versions of RoboHelp, and
even though one of us uses Visual Source Safe while the other uses
MS SQL Express, the common thread is removing a project from
version control and later returning it to version control.

Does a RAIDed set of hard drives help project load/save time?

My editor has a project way above the '100 mb' recommended limit. Right now around 230 MB i believe. But I've also heard of people who have **3-4 GB** project files!! How on earth do they efficiently work in it?
My editor's project file takes a long time to load, save, autosave, and her FCP crashes occasionally, always during saving/autosaving. She has FCP installed on one hard drive, her project files located on a seperate hard drive. Not sure of speeds, but both have at least ~40% free space.
If she had like a RAID array, the one where you take 2 drives to make one big one with a theoretical 'double' write/read time, and she put her project file on that, would that speed things up? If she had 2 sets of that RAID configuration (what is it?), put her applications (inc. FCP) on one array, her project files on another, would that speed things up even more?
Also, we have all our media on a SAN connected to the editors through gigabit ethernet. Could this be slowing things down in anyway?

RAIDs get you faster read/write times with your MEDIA. They will not help with your project issues. Do what Randy suggested. Multiple project files are the key.
Raided drives get you more RT effects with media, and allow you to work with uncompressed formats. Nothing to help out slow projects.
RAM, Processor...and smaller project files.
Shane

Aspect ratio affects render time?

Hey,
We are a post production studio, working with 2011 Mac Pro machines (With 16-32 GB Ram, New Nvidia card utilising CUDA and an SSD drive for media cache) on the latest version of Premiere CC.
Lately we've notice certain projects take longer to render out of Premiere - We are mainly producing promos so our final movies are usually 30 seconds long. After checking what the "slow" projects had in common, I noticed that they all seem to be SD resolution. While exporting 1080p takes about two minutes, exporting SD (PAL 720x576) seems to take up to 5 times longer - between 5-10 minutes (again, for a 30 seconds video!).
We are working with ProRes 422 LT codec and are exporting via premiere (without queueing through ME), using the "Same as sequence" checkbox, with Maximum render quality checked. The footage is originally ProRes LT and the sequence settings match the files perfectly; The output file we are trying to get is also a ProRes LT mov file.
I've tested this on five different machines, tried locally and from our network, with different settings and presets, but the result always seems the same - exporting PAL takes a lot longer then exporting full HD footage.
This seems extremely strange to me, and I couldn't find any logical reason for this, so I'm hoping someone here will have the answer - why is this the case? Is Premiere just not built to handle SD footage well? Are there specific settings that might make our export quicker?
We have to export 5 versions for each promo, so this is a big problem for us - a process that usually takes 10 minutes in 1080p, is now taking an hour!
Any info would be greatly appreciated.
Thanks,
Michael

Hey,
Thanks again for your help, for some reason your export seems to be a lot faster than ours, even though we are using Mac Pro towers with stronger specs then an 2011 iMac.
The only thing you seem to be doing differently is having AVCHD in MOV wrapper as your original footage, our's is natively ProRes 422, and the export from ProRes (4x3 PAL) to ProRes seems to be extremely slow on Premiere. This should just be your run-in-the-mail "same as sequence" export, so I really don't see a reason for it to take so long.. I don't want to be "that guy" that comes into the Adobe forums with complains, but with FCP7 we obviously never had these issues.
We are indeed exporting to broadcast - we are making TV Promos for a couple of major channels and a big satellite company here in Israel. our kids channels unfortunately still air in 4x3, and since we are exporting 5 versions for each promo, and about 3 promos a day for that specific client - well.. that would be a lot of coffee!
I am also aware that PAL requires 25fps, that is the standard for broadcast here and the original footage is shot and delivered to us that way, so that shouldn't affect the export either.
The thing I'm still finding extremely weird about this whole thing is that this problem doesn't seem to exist with widescreen (16x9) PAL footage, but only with 4x3. I would understand it taking longer if this was a WS sequence which premiere had to re-conform during the export, but that is just not the case.. I'm basically taking a video that already has the exact specs I'm using for export (that was rendered out of AE), PAL 4x3 ProRes 422 LT, 30 seconds video, adding an audio track to it and exporting out with the same settings as both the sequence and original footage. There is no reason that should take 5-10 minutes on machines that do the same for 1080p in one minute.
Thanks again, and as always any further info would be greatly appreciated,
Michael

Can anyone tell me why Logic runs faster on an iMac G5 than my G5 2.7 PPC?

I am missing something. On my desktop tower Dual 2.7 PPC on which I run Logic Pro 7 and other programs like Protools 7.1, I noticed that Logic 8 runs slower than Logic 7 - graphic redraws are sluggish.
However, I just came back from a friend's and saw Logic 8 running on an iMac G5 - with a single processor to boot (can't remember exact clock speed but under 2G) and redraws are quicker and I didn't get the "Disk Too Slow" message when playing the demo content.
How can this imac run Logic better than the better spec'd machined?
Has anyone else seen this?
Some installation must be hampering Logic 8 performance on my 2.7G mac but I can't think of what. Maybe one of the Pro Application updates? Or maybe I need to install the Pro Application updates?
Any help is appreciated.

it is not a 'port' steve, it is as native on ppc as it is intel...and i think the OT was talking about an older imac that was still ppc.
ken, i would say that the problems you are encountering may very well be a pro app update. but it also depends on the project as well. i have been finding some projects behave very sluggishly and others, even more densely programmed ones are quite smooth. also i find the 'sticky' slower projects to be a bit crashier. but the thing is, i don't think it makes any difference between songs made in 8 or made in 7. i would have thought that the 7 songs might cause problems but there doesn't seem to be much rhyme or reason between what songs are going to behave oddly and those that don't.
also there are many factors that can affect GUI speed. someone was saying that if you have lots of icons and folders open on your desktop it can have an affect on your GUI.
but for what it's worth ken, i have 2.7 ppc as well and for the most part the GUI speed is ok (if not actually electrifying).

Aperture 3 library performance tip after upgrading

This tip may be helpful for anyone experiencing slow project/album loading and beachballing even with no background processes running in aperture 3.
I was having some major issues with performance in aperture 3 with all library/project/album and book loading operations. It was very odd because Adjustment performance is very good.
All my imported aperture 2 books would beach ball for about 50 seconds to load, and then each page would take 10 seconds to load after clicking on it. In comparison my aperture 2 library was near instantaneous.
After exporting the project as a separate library, rebuilding the library, repairing permissions, nothing was working.
As a last ditch effort before opening up Shark - I decided to open up the library in the finder, and manually delete all of the original previews. I then opened up the library in aperture and manually updated all the previews by highlighting all the thumbnails and right clicking -> update previews.
Once this process completed I quit aperture and restarted to see if I was still getting any slowdowns and the problem is now gone! Library loading and project switching operations are speedy as ever now, and the book navigation is faster than aperture 2 now.
Hope this helps anyone with performance issues.

Speak up if anyone has problems migrating because of previews or is successful in migrating without previews. I suspect this is my problem. I get to:
Upgrading Library 7% complete (updating master metadata - 5,068 remaining)
After restoring from a file vault with Aperture 2, I get to the same spot, with or without previews. Although this is a slightly different issue, I tried deleting previews within Aperture and reimporting. I got to the same exact spot as before. The computer becomes nearly unresponsive, and I have to force quit Aperture after hours of sitting at 5,068 remaining.

Can we Report BW Cube using Cognos Fornt End tools

Hello, Experts.
We need some inputs on how to Report BW cubes using COGNOS front end tools.
is this possible?
do we need to develop new cubes out in cognos again for making reports?
and in BW cube some attributes of material are not navigational if we go to cognos can we use this attributs for drill down or filtering?
Thanks in Advance.
Bharath.

i am currently working on bi 7 with cognos 8.2 and go live very soon
- best approach is to use query as datasource for cognos (cognos consultants agree)
.......without query as datasource, cognos cannot see any reusable objects.
- If i recall, cognos can leverage attributes as navigational even if bw does not have them set that way.
- one downside is that you need to make sure all your rkf descriptions are locked down 100% because cognos uses the description in their xml definitions.
- Make sure you have an experience cognos framework modeler that knows ins and out and does not use simple wizards. same happened to us and lots of settings occured very late and slowed project.
reach out to me via my profile and i can give you pointers.

Slow project

Similar Messages

Maybe you are looking for