Skip to main content
C
charliez57575821
Participant
October 26, 2015
Answered

Captivate 6.1 on Mac audio spontaneously reverted to an earlier version of the course

  • October 26, 2015
  • 2 replies
  • 294 views

This is the strangest thing I have ever seen as a developer. I developed a course earlier this year that has sat untouched for several months. I recently found some of the hyperlinks in the course had changed and went in to update them. After that the audio had reverted to the previous version, which is wrong. I have to re-record all the voice over.

I had been experiencing lots of Captivate fatal errors and so I renamed the cached projects folder. After the audio reverted to an older version I renamed that folder back to the original name, started Captivate again, and the problem persisted. I never touched the audio tracks at all. I have no idea why or how this could have happened.

This topic has been closed for replies.
Correct answer RodWard

That bit of information about changing the project cache makes me theorize that somehow an earlier cached version of the course got mixed in when you opened the project to perform edits. 

If you were having lots of issues with errors, perhaps your cache folder had grown too large and needed to be cleaned out rather than having its name changed.  If the folder could not accept more cache files due to some imposed size limit, then that might have contributed to this error where an earlier cache version was used.

Still unusual though.

2 replies

C
charliez57575821Author
Participant
October 27, 2015

I think that's as good a hypothesis as we can find. I'm thinking I don't like the old audio track anyway and I have an opportunity to make some other changes so all's good. Thanks!

RodWard
Community Expert
RodWardCommunity ExpertCorrect answer
Community Expert
October 27, 2015

That bit of information about changing the project cache makes me theorize that somehow an earlier cached version of the course got mixed in when you opened the project to perform edits. 

If you were having lots of issues with errors, perhaps your cache folder had grown too large and needed to be cleaned out rather than having its name changed.  If the folder could not accept more cache files due to some imposed size limit, then that might have contributed to this error where an earlier cache version was used.

Still unusual though.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices