Copy link to clipboard
Copied
I am using Captivate 4. I have a base project size 800x600. I have additional slides that I'm importing (795x560), because of a smaller screen. I'm am having major file corruption and file closing errors. Is this screen size diff. causing the errors?
Copy link to clipboard
Copied
Hello,
Normally you only get a warning when trying to import slides with different dimensions, and CP tries to adapt those to the new file with some loss of quality. Of course there is some problem because the width-height ratio is different.
Are you importing from another CP-file? And are both files created with the same AS-version?
A workaround could be to open both files and just copy and paste the slides instead of importing them. Perhaps there is a corrupt slide, or a corrupt object (like a click box) on one of the slides to be imported? Could you try the copy/pas method?
Lilybiri
Copy link to clipboard
Copied
Both files were created with the same AS-version. How would I narrow down which item/slide is corrupted? This is happening to me quite a bit. I did have a large file 180 slides or so - it got corrupted. Then I started breaking it down by exercise - only 20 slides and it became corrupted. I thought maybe it was the slide size difference. I did receive the warning prompt before inserting the smaller sized slides.
Copy link to clipboard
Copied
I would try the copy and paste workaround, slide per slide. Perhaps you could detect the failing slides that way?
Lilybiri
Copy link to clipboard
Copied
The copy/paste slide per slide workaround seems to have worked. When I tried this by importing slide by slide, the file corrupted. I did not, however, have any one slide that corrupted the file. Very odd. I will cross my fingers that it will not corrupt again. Thanks!
Copy link to clipboard
Copied
Hi there
Food for thought...
Where is your project when you are making edits? Does the drive letter reflect anything other than perhaps C or D? If so, odds are that you are operating on a network. That's one possible reason for corrupting. How are your PC specs? Hopefully beyond recommendations? Exhaustion of PC resources is another reason for corruption (hence the number of slide limitations).
Cheers... Rick ![]()
| Helpful and Handy Links Captivate Wish Form/Bug Reporting Form |
Copy link to clipboard
Copied
Yes, when it started freezing the first time, I went through the troubleshooting suggestions listed and immediately started working from my desktop. I still have the freezing problems regardless. My file is only 13,000 kb and it is still freezing. I have had a file size up to 68,000 and didn't have any problems. I am still confused on how an element in my project becomes corrupted. I have never had any problems like this in any other Adobe software. I am saving my files every hour now. This freezing has put me a month behind schedule...very frustrating.
Copy link to clipboard
Copied
I see back in 2009 you were having a problem with Captivate 4...which I now am also having. Seems to happened to me last week, when I tried to copy one or more slides over from one project to another...I got error message/s and everything closed down. I wasted a whole week with the Adobe Tech Support and got 100% nothing from them, and then got help from another Forum reader (Manish - my knight in silver armour)...who told me about the workaround (copy one slide at a time on to new project). I tired it and it worked.
Today, got same problem again, and I cannot waste my time copying slide by slide to a new project each time this "error" happens...I need someone from Adobe to establish what is the problem and fix it.If I am doing something wrong, fine...just tell me what to do or not to do to make sure I dont replicate the error again.
I have no confidence in Captivate 4, it seems to have a mind of it's own, and the Technical Support is not even worth considering. I need someone from Adobe to look in to the problem and fix it, for me and I am sure others, not just leave the issue out there on the Forum pages.
Any ideas/suggestions? (Non technical speak please, plain and simple is the only lanuage I understand)
Noel
England
Copy link to clipboard
Copied
Noel,
I totally understand your frustration. I too, have resorted to the copy slide by slide method. But I have done other things to deter freezes.
I have had to do several things:
1. Are you working from server? If so, start working on your document from your desktop. I then transfer my day's worth of saved documents back to the server to be backed up.
2. Save, save and save. I save a NEW document (File>Save As) every 15 minutes or so, depending upon how much work I've done to my project. (That way, if it does crash, I've only lost 15 minutes and have an uncorrupted file to go back to.
3. Keep your file size down.
a. That means saving your pictures at their actual size in the document. (Are you finding that when you insert a picture, you get the screen prompt that asks you to crop or reduce the picture size? - Then your pictures are too big.)
b. What screen capture size are you using? Use the smallest possible size. 800x600 has worked well for me and also makes it easier for the end user to view the project (they don't have to scroll up and down to see the screen.)
4. Delete unused items. In the library window, click the Select Unused Items icon (this will select all unused items from your documents) and then click the Trash can icon. (Just because you delete a picture or audio clip from a slide, Captivate does NOT remove it from the document until you delete from the library. This takes up a LOT of space).
5. Start a Freeze/Error log. I have started a log to remind me what I was doing at the time of the freeze up to try to pinpoint the cause. At this time it appears random. Maybe you can find a common link.
Adobe has not given me any other suggestions or fixes. The above steps are the only that have kept my sanity and freezes to a minimum.
Good Luck!
Twistergrl
Copy link to clipboard
Copied
Hi there
Twistergrl is offering some pretty good advice here. But I'd like to clarify one point that was made.
twistergrl wrote:
1. Are you working from server? If so, start working on your document from your desktop. I then transfer my day's worth of saved documents back to the server to be backed up.
Note that you may discover that even the desktop is actually found on the network. Personally, even though I don't have a network in the picture, I avoid the Desktop as well as the "My Documents" folders as project locations. I regularly recommend creating a folder on your C drive named "Projects". Then create new folders inside this one for each project. This keeps your content near the root and it has a reasonably short path. We have seen issues in the past where a lengthy path causes issues. When you save things on the Desktop, the path is fairly long. Here on my own PC, the desktop path looks like this:
D:\Documents and Settings\Rick\Desktop
And My Documents (the typical default location) looks like this:
D:\Documents and Settings\Rick\My Documents\My Adobe Captivate Projects
Cheers... Rick ![]()
| Helpful and Handy Links Captivate Wish Form/Bug Reporting Form |
Copy link to clipboard
Copied
Hi Rick,
Excellent suggestion. I was working in "My Documents" which did have a long string. I have now cut it right back to C:\Projects...lets see how we get on!
Noel
England
Copy link to clipboard
Copied
Hi ...
Thanks for the help suggestions and I will for sure put them in to place.
Let's hope Adobe get off their high horse and start to listen to the problems their customers have and come up with the fixes...afterall we pay enough for the product!
Noel
England
Copy link to clipboard
Copied
I must CHIME in and add my 2 cents ![]()
I have been using Captivate 4 for the past year with more success than errors, but in the last 2-weeks, (starting 2/12/10) Captivate FREEZES-UP on me all the time now. I'm currently scouring the forums looking for some help myself. I posted my issues in another thread. Please see "Captivate 4 Freezing - why?" (includes my system specs as well)
I read through Twistergirl's recipe list for avoiding errors, and have a couple more of them to add myself.
Truly seeking answers ... 'cuz I need help ...
MissyCher
Copy link to clipboard
Copied
Hi MissyCher,
I am convinced that there is a problem within Captivate that every so often, for no obvious reason you can identify,causes the project to freeze, to wipe out saved work and other similar related actions that really screw our work efforts up. If Adobe are aware of these issues (I guess they must be), I get the impression they are just turning a blind eye and leave the "Forum" to resolve the issues for them. If you try and get any help from Tech Support - you have more chance of getting blood from a stone.
The only way I got my "freezing" problem resolved was to make so much noise, to threaten to publish my nightmare to the trade press etc before Abobe woke up and jumped to action (but only after 4 weeks).
For now - my freezing problem seems to be OK...but I have no confidence it is fixed and I dread using Captivate each day, in fear it is going to freeze on me again and I will have to start the nightmare (on Adobe Street) again.
For me, as a customer, I would really like to see something from Adobe that acknowledges there is an irractic problem which can result in freezing and loss of saved work etc. and they are doing something about it. Furthermore that their Tech Support people are aware and know how to help you.
Noel
England
Copy link to clipboard
Copied
Hi Noel
And what did Adobe do that corrected your issue? ![]()
Mild rant here - Tech Support for nearly *ANY* company is most often luck of the draw. I say this because I myself used to work in a Technical call center. As with any job, you have folks that care a great deal about what they are doing and they work very hard to provide the best possible support. I tend to find that these fall into the 80/20 rule you hear so much about. You know, 20% of the folks do 80% of the work? Stuff like that. So let's say that in an average call center, you have 20% staff that is totally capable of resolving your issue. This means 80% of the typical staff just don't care. They are only there to collect a paycheck. They really don't care if they do a good job. The job is a means to an end. This means you have an 80% chance of reaching someone that isn't all that interested in solving your issue. Personally, I always strived to be in that 20% group. But I digress. The point to my story here is that Tech Support will often seem dreadful for nearly any company.
I have no idea if the Adobe help desk (which, as I understand it, is not really handled by Adobe, but is outsourced) is set up to categorize calls and connect you with someone actually familiar with the product you are having issues with. The last I heard, Adobe has about 90 different products. So imagine trying to be familiar with all the different products. Likely, they are using some form of scripting (ask the customer if this is happening and if so, choose this option. Otherwise choose this other option) This also isn't meant to say that an outsourced call center generally is worse than one provided in-house. It just seems reasonable to me that if your call center is in house, the staff are closer to the product and as such, should be able to have access to resources that can assist with sticky situations.
All that aside, it's been my own experience that with many software products you encounter issues that seem elusive at best. They seem only to manifest under very specific conditions. And these are the bane of any tech support area. After all, if you can't reproduce the issue during troubleshooting, it's really difficult to figure out where exactly the problem is. Troubleshooting then becomes either swap until you drop or what most folks think of as VooDoo. (Sincere apologies to anyone that practices the actual assorted VoDou religions.)
So sure, Captivate crashes on me occasionally. But I always have a decent backup handy and I save often when working on projects.
Sorry, you can probably tell this is a bit of a passionate subject for me.
It used to drive me crazy to see some co-workers play Tetris all day and come ask the same inane questions day after day. Jeez, if you spent only 10% of your Tetris time trying to learn about what you are paid to support, you would have no need to ask for my help!
Cheers and happy Friday... Rick ![]()
| Helpful and Handy Links Captivate Wish Form/Bug Reporting Form |
Copy link to clipboard
Copied
Hi Rick,
Thanks for detailed reply. However I beg to differ with regards your concept of "support". Sure, I can understand the easy (for easy read CHEAP) option to is put support out to people who just read scripts and really dont care and you fall in to the 80/20 trap...but that says it all about the mother company themselves, in this case Adobe...they just dont care themselves! If they really cared about their customers, regardless of how many products they have - they would make damn sure the support was the very best/better than the rest, for all products, for all their customers, at all times. Afterall they charge enough for their software.
Instead Adobe go down the road you outline which is "dump it outside and only if it starts to smell really bad will we do something about it". That is not the way to run any sort of customer support or service, as Adobe will sooner or later discover to their cost.
As to what they did for my problem...at first when my project froze, I had to copy "one slide at a time" my project over on to a new project. This was not the fix, but a long winded workaround that worked, albeit an hour's additional work 2-3 times each day just to keep going. Then, 4 weeks after trying to get help, I actually managed to speak (yes speak) to someone at Adobe in UK who really knew what he was doing and understood how to treat a customer in need, and is a credit to Adobe (I wont name him as he is my secret now) - I was sent some files to download to Captivate, and was also told if the problem happens again there is no need to copy/paste one slide at a time, but can copy ALL in one go to a new project.
So far since the download things have been OK - but I have no confidence in Captivate anymore and dread the day when this happens again. At least I now have a contact within Adobe....Pity Adobe cannt (wont) see the mess at their own feet.
Noel
Staffordshire
England
Copy link to clipboard
Copied
Rick,
Tech support = Help Desk software. That is the intelligent product behind outsourced companies technical support services to their customers-customers. Another form of GIGO (garbage in - garbage out). You must know that staff fielding support calls are tapping into the company's problem resolution knowledgebase, aka canned answers. Gone are the days of talking to an expert, today we have access to talking with those who are reading the answers from a screen. No one on the other end is actually an "expert" save maybe the occasional consultant called in to provide content to the help desk software database and no one has actually seen this person to provide an accurate description.
So using the 80/20 rule; 80% of the time information is translated by a customer service agent to answer or not-answer a customer's question and only 20% of time is the informatin of any real help. Actual resolutions cannot be quantified through help desk contacts, and help centers calculate resolution percentages on first-call to indicate that they are more successful than not. In reality, their phone systems are so over programmed with voice automation that users can not successfully return to customer service and tell the help desk agent that the help they received was not beneficial.
So Rick, having experience with Captivate crashing/freezing, do you have a handle on what leads up to the program crashing/freezing? And if so, can you provide that information to the forum? If I know how to avoid the problem, I will do my best to avoid crashing/freezing. So far all of my work in this area through problem/resolution journals has been unsuccessful in pointing to any one (or two, or three ...) reasons why this is happening. I rely upon the knowledge that I must save and exit the program often to ensure that I do not lose work. What kind of productivity is that? As our Campus Support Services said to me - "You're spending more time CYA than working."
Oh but I digress ... Dorothy, where are my ruby slippers? I need to click my heels 3-times to wish for a better solution (sigh).
MissyCher
Copy link to clipboard
Copied
Noel,
Thank you so much for the post. No I still do not have a solution. As of today, I am going on 25-days of lost productivity due to Captivate freezing problems.
Our campus Desktop Support Services became involved 21-days ago to try and assist me with a resolution. Here's a summary of actions taken to date by all parties involved on a single laptop trying to deal with Captivate freezes:
I am so jealous of you Brickyard
for getting a solution to the freezing problem. Why isn't the solution you obtained available for download from Adobe support? I am on the verge of losing confidence in Captivate. I think Adobe Customer Service practices are a joke. Have I mentioned yet that I have been using Adobe (previously Aldus) software products for 23 plus years?
Looking for a way out and wishing I was a Camtasia user ... ![]()
MissyCher
Copy link to clipboard
Copied
Only thing I can suggest, is Captivate is a very video-intensive program. Back with the good old Authorware product, such crashes were also often due to video card settings or capabilities (not enough RAM, which is rare these days - or a Windows Update that required and updated video card driver - or reducing 'hardware acceleration').
Some of those fixes seem to help with Captivate too. I wouldn't focus on the HD so much as the video card and settings.
It's almost surely a CP issue at the root so a shame to focus on the hardware, but may be helpful...
I do understand Adobe is working hard on the next version of CP, perhaps even a complete rebuild in order to provide Mac support as well, so perhaps the lack of attention to current issues is Adobe praying that all will be well with the next release...which I realize doesn't help folks with current problems too much.
Good luck!
Erik
Copy link to clipboard
Copied
Erik,
Thank you for the leads.
Desktop Support Services/IT are evaluating the video card and settings for the card in my system as a result of your feedback. I am very excited to read about your theory on Windows updates being a potential culprit. It was my original theory that the latest automatic update for Windows should be evaluated since Captivate starting having conniption fits shortly after receiving an auto update. IT said it would be very difficult to identify specific contents of a Windows auto-update so I dropped any research attempts into this area. But, I still see the need to examine the potential for 'cause and effect'.
By any chance do you (or anyone lurking) have a trusted site you use that lists what is contained in each released Windows update?
And Adobe (if you're watching) don't you know in advance what updates would potentially send Captivate into spams? This information should be available in the Troubleshooting portion of Captivate's support website. (If I missed it, please direct me to where I can find this) I know Adobe's states "some Windows drivers can affect Captivate ..." but that's not enough to go on to resolve problems. That's like saying "go find the needle in the haystack." More specifics are needed in this area.
Since the converation is taking a turn into video cards and settings, the question presents itself: If users are successfully using Captivate not freezing up, what is your video card (specs) and have you changed any settings for use in a video-intensive editing environment?
MissyCher
Copy link to clipboard
Copied
Hello Everyone,
I too have been experiencing Captivate freezing. My happens now with a PPT edit. I too believe it has something to do with Windows updates on my machine. My PC is very new and should be handling everything fine, plenty of RAM. I'll learned to keep my projects small, and began using CP$ with a PPT embeded, and that is when my problems began. I started seeing a STOP error when accessing project preferences. Now it is freezing when I come back into CP from an PPT edit within the tool. I am getting a fresh load of Windows soon, but at this point, CP4 is very fragile, and not working for me at all. I would love to here how your progress has gone since March.
Did you ever find any answers? Video card suggestions?
CP3 did not have any of these problems for me.
Cyndi
Copy link to clipboard
Copied
Hi Cyndi,
Welcome to the support group. I first posted my request for help to this thread back on 2/25/10 after experiencing program numbing freezes and system crashes that started back on 2/12/10. Since you took the time to post a request for help, I'm assuming you have read through everyone's suggestions for resolution, including mine, and still find yourself having to deal with Captivate freezing.
Your post is very timely, because I FINALLY got a resolution to my problems from Adobe Corporation on 5/26/10 that really works. That's right, you read it right: 104 days after contacting Adobe for help I finally got a fix to the CP 4 freezing problems. Here it is:
Call Adobe Customer Support, and open a case (Support is not free, it costs.) and tell them you are experiencing program freezes with various error messages concerning the file "Business.dll" and need a resolution because CP 4 will not run.
After months of working with and waiting on Adobe's technical support (up to it's highest senior product and engineer staff levels) evaluating my documentation and supporting files they provided me with a link and sign-in credentials to download 2 .dll files to fix my problems.
The CP 4 freezes (I experienced) were a result of a MS Windows XP update that occurred before 2/12/10 and created problems with Adobe's program environment. Adobe had a fix to the problem by 2/11/10 but this was not communicated to customer support, hence the unbearable wait and repeated follow-ups to get a solution.
Call them today and good luck. Holler back if you need anything and if I can help I will.
Cher
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more