Flash CS4 slow opening file

The index page of my website contains an swf initially
created in 2003 and modified many times since. Every version of
Flash has opened this file immediately, within 5 seconds. CS4,
however, takes seven minutes to open or save it.
I have opened a case with Adobe. So far I've gotten a canned
list of things to try, none of which has had any effect. I have
sent the file to Adobe. No reply.

Hi. I am now case #0180543954 and I received a response from
Adobe today confirming the problem, and they have a copy of my
current file and are speaking of corrupt code.
Wish I could remember how to make it available via a URL
:–(. I have two early versions of this artwork, one with just
an array of kaleidoscope spheres, the other with this whole group
rotating. Without rotation takes maybe 1 second to open in CS4;
with rotation, 21 seconds.
The swf seems to take just as long to generate as it has in
previous versions.

Similar Messages

Slow opening files

Hi,
I recently a user's PC. They went to a Windows 7 64bit 12GB RAM, 1 x SSD drive and 1 x SATA. They have been upgraded from Photoshop 7 to PhotoShop CS5. The user is complained that opening files from the network is slower than it was with PS7. I did a comaprision and there is a difference in the speed with which files apepar in the Window in CS5. I have now had to put a version of PhotoShop 7 back on her PC to appease her but her point is correct. PS7 displays files quicker than CS5. Is there anything that can improve the speed with which files are displayed?
I have had a read and applied as many of the settings as are relevant from this article on optimizing performance but it hasn't changed things.
Thanks,
Dermot.

I have done some more research.
The original complaint was that CS5 was comapred to PS7.1. That comparison however was between two different machines. I checked and the slow machine (the new one with the spec in the original post) was using a 100mb network connection whereas the other was on 1GB. I re-patched the slow machine so it was operating at 1gb also. I thought that was the end of it but no!
I had already installed PS7.1 on the slow machine so I did a comparision. I took 10 jpeg whose disk size was between 200kb and 800kb (about 2mb un-compressed). I opened them in CS5 and they took between 8-9 seconds from draging into CS5 to fully rendered. I then did the same on the installed version of PS7. It too 2-3 seconds. These files were from a network share. There may be some improvement with PS7 due to disk caching somewhere.
The graphics card is an Nvidia Quardo 600 1GB DDR3. There is no direct option to disable OpenGL. In the Display options/Nvidia Control Panel you can control global and specific program graphics options. You can modify graphics options for PhotoShop CS (which incidently is called CS4). The options where Quardo or Global. I have set it to Quadro for now I am not sure that the graphics card is the issue but I'm happy to change any settings if they will have a bearing.
Does anyone have any other suggestions I can try?
Thanks,
Dp.

In CS4, "Cannot open file" "Please upgrade your plug-ins..."

Greetings,
I am using InDesign CS4 on a PC. I am trying to open an .indd file created by our marketing department. I don't know what version of InDesign they use nor whether they work on Macs or PCs.
When I double-click to open the file, I get a "Cannot Open File" popup box. The box reads "Cannot open docname.indd. Please upgrade your plug-ins to their latest versions, or upgrade to the latest version of Adobe InDesign." It then lists 18 different plugins:
ASSIGNMENTS.RPLN
TEXT.RPLN
SPREAD.RPLN
MASTER PAGE.RPLN
TEXT ATTRIBUTES.RPLN
.... and 13 more.
When I go to Help > Configure Plug-Ins, I can see that I do have all of these plug-ins. But apparently they are not the latest versions.
Anyone know how I can update these plugins? I have searched for them on the Adobe website, but no joy.
Thanks in advance.
Jen

It's a safe bet that they are working in CS5. The only way to get those plugins is to install CS5 on your machine.
You could ask your marketing department to export an IDML file from CS5, which you can open up in CS4, but it might fail horribly (and it's guaranteed to lay out incorrectly if they've used any tools in CS5 that aren't in CS4). If you rely on this workflow, by regularly using a document going back and forth between CS5 and CS4, chances are very, very good that it will fail at a critical moment. The only really safe thing to do here is to get everyone using the same version of InDesign.

Acrobat 9 Pro very slow open files over network in Windows 7

I have installed Acrobat 9 pro on my new PC. It's running Window 7 64bit. I use it for pre-press of high-resolution files for printing. Sometimes the file sizes run into the 100s of MB.The new PC has reasonably high specs, with 6Gb of RAM and a 2.8Ghz Quad core i7 CPU and gigabit networking.
Opening them when on the local hard disk is reasonably fast. For example a multi-page 400Mb file starts drawing the first page withing 3 seconds. But opening the same file when it's on the server of our gigibit network generates a very long pause. The application locks up and dispays a "not responding" message for 2-3 minutes. The bigger the file, the longer the pause. It doesn't completely crash -- eventually it starts to draw the pages and I can work as normal.
I used to have Acrobat 9 pro on my old XP PC which was a cheap low-end machine when bought 3 years ago. (has on-board shared RAM graphics card and only 1Gb of RAM). But what grieves me the most, is this slow old machine will open the same 400Mb file off the server so much faster than my expensive new machine. There is no lock up and it begins drawing the first page after only approx 5 seconds.
The problem doesn't seem to be simply related to slow network speed. I can copy the entire 400Mb file from the server to my hard disk in only 12 seconds. The old PC is actually slightly slower copying to/from the network. If the application was for some reason copying the entire file into memory or to a local cache, this should still only generate an extra 12 second delay -- not 3 whole minutes.
Adobe Reader 9 doesn't have the problem. I can open the 400Mb file off the network on either my new or old machine within seconds.
Acrobat 9 Pro doesn't have the problem on an old G5 mac either. It's somewhat slower than my old PC but will begin drawing the first page after a few seconds,
So what exactly is Acrobat doing for those 2-3 minutes?
I have already tried:
1. changing network ports/cables.
2. disabling anti-virus software
3. disabling "remote differential compression"
4. Patching Acrobat 9 to 9.2
5. Files located on Windows servers and Mac Xserves.
Not improvements from any of these.

I think I have isolated the source of this problem. It's the Pitstop Professional 9 plug in. I un-installed this, and everything opens quicker than greased lightning. I re-installed it and it's back to slowsville.
Unfortunately Pitstop is essential to my workflow.
Until recently I did my pre-press on a Mac G5 with Acrobat Pro 7 and Pitstop 6.5. I never had this problem with slow file opening. But it seems that the delays would occur when I used the plug-in with large complex files.. So it would open files as fast as you'd expect from an elderly machine. But starting to use Pitstop would result in a prolonged period of staring at a spinning beachball.
I wonder is there any way to stop the Pitstop plug-in from initializing until it is used? So the plug-in stays inert until you select the tool from from the menus.

Excel 2007 Slow Opening File

We were looking at migrating to Office 2007. To verify compatibility, several key users have loaded Office 2007 on their machines. There seems to be several problems related to opening files in Excel.
If Excel is open and the user does a File/Open, files will open quickly. However, if the user clicks on a file to open it, it can take up to a minute to open. I found a fix for this on this forum. It is to add "%1" to the end of the Open command line in the defined file types for XLS files. After this worked, I found that also needs it for the New on XLT, Open for XLSX, New on XLTM, and New XLTX files.
After adding in the above fix I wanted to verify that it worked correctly by recreating the problem so I went in and removed the "%1" from all of the commands. When I tried to open a file, I got an error. So I went back into the File Types and checked the command lines. Now all of the command lines had a %1 at the end of them without the quotation marks. When I would try to delet this %1, it would now allow me to. I could remove it but when I reopened the line, it was back again. If I added the "%1" back to the end of the line it would take that and it would fix the problem again but I was still unable to remove the %1 from the other commands such as New, Print, Save As, etc. I had to Restore my system in order to remove them.
Further testing on the fix reveals that when I file is opened, it attempts to open the file twice. The first time it opens very quickly and then a minute later it opens the second time. Notice that this is the same delay that was experienced previously. It you open the file and make a change before the minute has elapsed, then you get a message stating that the file is already open and if you open it again you will lose your changes. This is probably due to the Use DDE being selected. But If I turn off DDE, then when I click on the first file, it opens quickly and when I click on the second file, it also opens quickly but if I look at the Task Manager, their are 2 copies of Excel running. If I go to the View tool bar in either copy of Excel and try to view the other window, I can not. So it appears that there physically 2 copies of Excel running. When I went back into the File Types, the Use DDE that I had unselected before is now checked again but the DDE command line is blank.
Thinking that may this was something that was surely fixed now that it is 2008 and the software is 2007, I looked for updates and found that IT had not run the updates. Loaded the Compatibility Pack and Service Pack 1 and high hopes that this would correct the problems. After loading the updates, I found that the File Types had reverted back to their original form without the "%1". Now I was really excited. Why would they reset user changes unless they fixed something related to them? To my dismay, the slow startup was back. I had to go back and set the "%1" back into all of the proper command lines.
As of now, my recomendation to IT is to stay as far away from Office 2007 as possible until Microsoft gets their act together.
By the way...I have tried all of the other recomendations from Microsoft about Excel being slow to start. They make a difference of less than 1 second. They also only make the App start quicker. They are not related to clicking on a file to open it.

I didn't seem to get much help from this forum but I will pass on the fix that I have found.
The problem doesn't have anything to do with the %1 fix that everyone is using. All that does is to open the file before Excel is fully started. In particular, before the add-ins are opened.
You can verify this by changing the command line in the File Types to use a /s parameter which will bypass loading the add-ins.
What I found was that even though I had removed the Adobe AcrobatMaker add-in, the file PDFMaker.xla was still in the XLSTART folder and was being loaded.
Since Office now has it's own PDF functionality, this is no longer needed. I did however want to keep Acrobat so that I could print PDFs from other applications and edit PDF files so I wanted to keep it. Just not in Office.
Here are the steps to remove PDFMaker from Excel.
Choose Start > Control Panel > Add/Remove Programs.
Select Acrobat Professional and click Change/Remove.
Click Next.
Select Modify and click Next.
Expand the Create Adobe PDF menu, then select the Acrobat PDF Maker option, and change the status to "This feature will not be available".
Click Next, and then click Finish to complete the process and allow Acrobat to remove the PDFMaker component. Note: You need the installation disk to do this.
After completing this process, it is interesting that it disabled but did not remove the PDFMaker.xla add-in. It is therefore necessary to remove it manually by exploring to C:\Program Files\Microsoft Office\Office12\XLSTART and manually deleting PDFMaker.xla.
Now for those of you who have already tried the "%1" fix and found that it causes new problems and doesn't fix things, you may have already found out that when you try to remove the "%1" from the File Type Open command line, something puts it back in as %1 without the quotation marks. This causes errors when you open a document that has spaces in it's path such as unable to open C:\Documents.xlsx, Unable to open And.xlsx, unable to open Settings.xlsx. No matter how hard you try, you cannot remove the %1.
So here is 2 ways to overcome this.
You can change the parameter from %1 to "%10". This will work as long as you don't try to open 10 files at the same time.
Or you can edit your registry and remove the %1. The easiest way I found was to open the registry editor and search for excel.exe" /e %1. Notice that this is the end of the command line. When I found it, I removed the %1. If you edited more than just the Open command for XLS files, you will need to keep searching until you remove all of the changes. This will get you back to where you were before you tried the "%1" fix.
There may be other add-ins that cause similar problems. Look in the C:\Program Files\Microsoft Office\Office12\XLSTART folder to see what is really getting loaded.

Adobe reader x very slow opening files over vpn to samba share

Takes 2 to 3 minutes to open a file - Acrobat Pro v7 accesses immediately - downgrade
to Acrobat 7 reader works fine - true on XP and Windows 7 - all updates installed.

I think I have isolated the source of this problem. It's the Pitstop Professional 9 plug in. I un-installed this, and everything opens quicker than greased lightning. I re-installed it and it's back to slowsville.
Unfortunately Pitstop is essential to my workflow.
Until recently I did my pre-press on a Mac G5 with Acrobat Pro 7 and Pitstop 6.5. I never had this problem with slow file opening. But it seems that the delays would occur when I used the plug-in with large complex files.. So it would open files as fast as you'd expect from an elderly machine. But starting to use Pitstop would result in a prolonged period of staring at a spinning beachball.
I wonder is there any way to stop the Pitstop plug-in from initializing until it is used? So the plug-in stays inert until you select the tool from from the menus.

Fix for slow opening files... soon?

We have several stations set up globally in various offices using Photoshop CS...
Image files, no matter how small the file is... even a single small JPG takes a good 10-15 seconds to open (win xp) and we frequently need to work with hundreds of images. This seems to be a major problem and from what I find on Google, not uncommon...
I finally ran into this temporary 'fix' in the archives which involves setting up a LOCAL printer/driver as a DEFAULT...
While that DID alleviate that problem, I can't see that adobe is just letting this be THE fix for the problem... I've done updates to our CS3 products and have a difficult time believing that there is no permanent fix for this yet.
It seems unlike adobe to expect so many clients to have to experience this problem, spending hours or days trying to figure out why their systems have slowed down and asking themselves questions mostly unrelated to the problem, such as 'did i run out of swap space on my drive?', 'how are my history/cache settings?', 'is there some network drive causing the problem?', 'Is there some spyware slowing my box?', etc...
And on top of that having to notify all the offices... 'Okay guys, if you use photoshop you need to do this, this, and that... temporarily'
Please tell me there is a permanent fix soon...

I don't know which versions of photoshop need to check/contact the network printer...
For volumes of image processing via the batch commands I often need to use our old Photoshop 6 which, even with the network (a fairly large corporate network) the files open up almost instantly... every time... unless they're huge print resolution images...
On the same network for such a task (batching hundreds of images) PS CS3 is unuseable to us unless we implement the local printer 'fix'... and even so, there is more of a delay than with our old photoshop...
And why does it need to contact the printer for each file that is opened? For the first one, sure... check it, done... I'm not printing dammit, just opening files.
If it needs printer information the local OS already has drivers loaded up, couldn't it check those? It shouldn't have to look for other network devices on there unless it's using them... but I'm no tech... so there must be a reason that it simply MUST do it...
And even so... why is this 'fix' so damn hard to find on the net? Tons of people with issues and a lone, difficult-to-find blurb as an obscure fix...?

InCopy CS4 and InDesign CS4 cannot open file at the same time!

I have 2 editors that make changes in my indd file. The one editor is able to open the file concurrently with myself (i'm in indesign) just fine. But when the other editor wants to open the file....I cannot open the indd file and vice versa. We are PC based.
shane

Yes, we are all working on the same server.
And Yes on the Editor A / scenario 1 (Designer opens file and Editor A opens file concurrently). works fine.
Editor A closes out of Incopy and so does Designer. Editor B opens the file and Designer tries to open the indd file and now the designer gets the warning: Cannot open document. You may not have permission or the document may be open already. This is the same error if the Designer opens the file first and Editor B tries to open it while the designer has it open.
Editor A and B are able to have the file open at the same time no problem.
Also this happens to all indd files that Editor B tries to open. So it is not linked to a problem with the file.
one other note: on the server just above the indd file...when Editor B has the indd open in InCopy... a 'temporary' Indesign Lock File appears.
shane

Photoshop CS3 extremely slow opening files

Recently my Photoshop CS3 Extended has been taking an extremely long time to open files of all sizes as well as to create a new document. It takes several minutes to open files. While Photoshop is attempting to open, the program is unresponsive.
Photoshop version 10.0.1
OS: Vista 64bit
PC: HP tablet
Ram: 4G
Processor: AMD Turion X2 Ultra Dual-Core Mobile ZM-86 2.4GHz

That's good advice from John there Liz and if you really lose patience, uninstall the whole thing and re-install it. You should get your original speed back then - I'm assuming that all your other programs are running normally.
Steve Donovan
[signature deleted by forum host]

InDesign CS 5.5 very slow open file

Hi,
I've a problem with inDesign. When i shift from a file to another, it is very slow.
I 've to work with a lot of file ( 8 or 9) open concurrently.
Every file is about 200 Mb.
this not happen using inDesign CS4 (on the same MAC, before upgrading to CS 5.5)
Here my MAC configuration
Imac Intel core i5 2.5 Ghz
8 Gb RAM 1333Mhz DDR3
MAC OSx 10.7.4 updated
Indesign CS 5.5 update to 7.5.3
Anyone can explain me ????
Thanks in advance

Look in the upper left corner of your screen. I’ve seen instance where the program opens with nothing but a tiny window there.
If that doesn’t do it, then restart Windows.
Bob

InDesign Cs4 "Cannot Open File"

Trying to open a .idd file with Cs4, but receive this message. I have checked to make sure I have all updates and I do. If this file was made in Cs5 or Cs6, it should still be compatible with Cs4. Can anyone give me some advice?

My guess is it's a CS6 file since it mentions form fields in the list, but you can use Jongware's tool to find out: Adobe Forums: [Ann] Identify Your InDesign File
Your OS cannot identify a file as anything newer than the most recent version you've installed, which leads to a lot of confusion, and no, newer versions are not backward compatible -- never have been in ID. To move files back to earlier versions they must be exported as interchange format files from the version where they were saved. Since CS4 that has been .idml, and all versions of ID since CS4 can read .idml exported from any version, but unsupported features from newer documetns will be lost and text will probably reflow, so you shouldn't have any expectations of a perfect conversion.

Why do CS4 always open files on main monitor ???

in the older versions, photoshop opens all the files on the monitor on which the last time pictures were closed. in cs4 this does not work, alwasy opens the pics on the main monitor. so i have to drag every picture from the main to my "picture calibrated" second monitor.
can i fix this problem anyhow???

>didn´t wanna know anything about the workspaces.
However, dongsoo choi did:
>dongsoo choi - 2:56pm Nov 17, 08 PST (#1 of 11)
>Also, Why there is no way to Show All The Menu Items?
Sack:
If you typed in standard English (" I didn't want to know ), it might be easier to understand you.
I made a suggestion which might work to solve your problem with your monitors but if you are to idle to even try it, you will have to solve this for yourself.
Or you could telephone Adobe Tech. Support.

Slow opening files - WHY?

I’m wondering if anyone can help me with this? I’m getting frustrated because I get the spinning beachball every time I try to open a Pages document.
We use a number of 150 page (or so) long Pages files to keep track of invoices. Every page is a separate invoice. The file is fairly small -- about 300 K.
I have a IMac (2.4 Ghz and 1 GIg of ram). Pages opens and runs fairly fast, but when I open these documents, I get a spinning beachball of death for 45 - 50 seconds or so every time. This is VERY frustrating. I have just upgraded to Snow Leopard and despite all the ‘lean and mean’ hype, I have not noticed any speed-up (if anything, it’s a bit slower.) I have restarted, checked software update and repaired permissions.
Can anyone help?
Thanks in advance for your time.
Eric W.
Victoria, Canada

Eric Wieczorek wrote:
I'm sorry but this doesn't make any sense to me. If you say this is standard behavior, I guess there is nothing I can do to the file to make it quicker to open and I'm wondering why I should stay with Pages or recommend it to anyone?
Here we are end users.
We can't change the program behavior.
This is why I wrote:
we have to live with this slowness or leave the program.
Of course, I assume that like many of us, you used the dedicated channel to ask Apple to enhance this feature:
_Go to "Provide Pages Feedback" in the "Pages" menu_, describe what you wish.
Then, cross your fingers, and wait _at least_ for iWork'10
Yvan KOENIG (VALLAURIS, France) vendredi 11 septembre 2009 10:14:33

Xdg-open is slow opening files

Whenever I use xdg-open to open an application it takes a while until the application is shown, but if I try to open it with the application itself it works almost instantaneously. While using xdg-open I can notice a high increase of the cpu usage.
What could it be that's causing this issue? Is there maybe a log file I can check to see what's going on under the hood? This issue is happening with gpicview (for images), nemo, and thunar; I haven't tried with other applications but I assume it's going to be the same.
As relevant info I might add that I'm using openbox and no desktop environment. I'll upload any config files if requested, but I don't really know what to include as a start besides my mimeapps.list:
#~/.local/share/applications/mimeapps.list
[Default Applications]
inode/directory=Thunar.desktop
image/png=gpicview.desktop
[Added Associations]
image/png=gpicview.desktop;
I've checked the wiki for xdg-open and all the forums (arch and outside of arch) and have just found people with the same issue, but no answers whatsoever.
Any help on this would be much appreciated.

After analyzing the loop (and the inner search_desktop_file function), I can tell that function is what's taking all the CPU time, also I can tell that only 3 iterations of the loop are run, one for each X, which have the values:
$x_1 = Thunar.desktop /home/josep/.local/share/
$x_2 = Thunar.desktop /usr/local/share/
$x_3 = /usr/share/
I can tell the first two searches take close to no time, and actually, the binary /usr/bin/thunar, which is located in the third iteration, doesn't take much time either, so surprisingly what's eating most of CPU resources is this part of the script:
command="$(get_key "${file}" "Exec" | first_word)"
command_exec=`which $command 2>/dev/null`
arguments="$(get_key "${file}" "Exec" | last_word)"
arg_one="`echo "$arg" | sed 's/[&*\\]/\\\\&/g'`"
icon="$(get_key "${file}" "Icon")"
if [ "${icon}" != "" ]
then
icon="--icon '${icon}'"
else
icon="''"
fi
# FIXME: Actually LC_MESSAGES should be used as described in
# http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s04.html
localised_name="'$(get_key "${file}" "Name")'"
arguments_exec="$(echo "$arguments" | sed -e 's*%[fFuU]*"'"$arg_one"'"*g' \
-e 's*%i*'"$icon"'*g' \
-e 's*%c*'"$localised_name"'*g')"
The first two variables command and command_exec are set to "thunar" and "/usr/bin/thunar", and this happens relatively fast (although it takes some time to find it, it's not even a 10% of the total time).
EDIT: I think all signs lead to the disk read taking too long (for example the get_key function which reads the .desktop file looking for the asked key, takes too much), but this is weird, as I had never encountered this issue in other linux distributions, everything has ran always smooth and fine, despite not having a good machine.
EDIT2: After finally tracking down the issue, I've found this loop: (inside the get_key function)
while read line
do
echo "readline" 1>&2
case "$line" in
"[Desktop Entry]")
desktop_entry="y"
# Reset match flag for other groups
desktop_entry=""
# Only match Desktop Entry group
if [ -n "${desktop_entry}" ]
then
echo "${line}" | grep -E "^${key}=" | cut -d= -f 2-
fi
esac
done < "${file}"
More than 90% of CPU time is spent in this function, but I can't see why. Parsing a .desktop file is not a difficult task by any means and even if this was reading the file every time, everything would be cached in the ram anyway, as modern OSs use paging for that matter (and by modern I mean not modern at all) and I'm well aware that linux does).
So TL;DR I don't understand how can the simple task of parsing a .desktop file take more time than opening google chrome or gimp. Any help on that?
Last edited by setzer22 (2014-07-27 19:07:43)

Acrobat slow opening files with Digital IDs

hi! I was hoping others were having this issue. I have a client that has over a dozen Digital ID Signatures stored on our network drive.
When she tries to open a file with multiple Digital ID Signatures, Acrobat takes forever verifying the Signatures. I can disable the security end, but that's not an option because of the people we are sending these files to.
Is there anyway to speed up the performance? Or will they just have to accept it?
Thanks for everyone's time.
Alvin

Hi Alvin,
Sadly, there's not a whole lot that can be done to mitigate the problem. Even without a lot of digital IDs installed on the system any time you open a file with that many signatures it takes a long time to validate. Part of the problem is a design flaw where signature 1 gets validated, then when Acrobat moves onto signature 2 it validates signature 1 again because each signature creates a roll-back version of the PDF (View Signed Version) and each rollback version is validated independently. When you extrapolate that out to 20 signatures you can see how much signature validation is going on. We are working on streamlining this process for future versions of Acrobat, but for now it's a liability that you can't get around.
The number of digital IDs is a separate issue where Acrobat does all of the chain building at the front end (it's no longer on app open like it used to be, but as soon as Acrobat has to iterate the list of digital IDs). You don't have to open a signed file to trigger this, but that is one of the triggers. Acrobat has to test each signature to see if it has access to the private key in order to allow the user to clear the signature. It's access to the private key in the digital ID that enables the "Clear signature" menu item.
Sorry for the bad news,
Steve

Flash CS4 slow opening file

Similar Messages

Maybe you are looking for