Have you tried having another instance of SL open and copying the slides one by one across to the new instance. Occasionally a SL file corrupts and gets larger with each save and this has cured it for me in the past. save you new version using version control so if a specific slide is causing problems you can always roll back to the previous version. Hope this helps
Thank you for reaching out and sharing what you experiencing with previewing and saving your project.
Is this happening to any file or this specific one?
If this single file: Please import your slides into a new file and see if this alleviates the issue?
If all files: Please be sure that you are using the latest version and if so, please conduct a repair of your software.
If you'd like to work directly with our support team, you can contact them directly here.
I definitely agree with trying the Import to a new project route that Leslie mentioned. Just be sure that your Story size in the new file matches what you're going to import in, before doing so.
If that doesn't work, there may be a few other options to try and get it into a new project file.
2. Not ideal, but sometimes if you go slide by slide on an import, you can figure out which slide is being the problem child, and can build that one out independently.
I would close the current file after you save to remove the undo buffer. Then reopen and do a save as to a different file name to clear out and oddities in the media library.
I am not an advocate of importing into a new file, this can cause so many issues such as extra slide masters, renamed results variables that it is a last resort for me and have probably used once in ten years.
There are things that can make saving always a slow process that you cannot change, lots of videos, different languages in the same file or even lots of large images. You may also have limited space on your C: drive.
You mention on LinkedIn that you have 550 slides. That is likely the reason your save is slow. Most of the courses I have that save slow have lots of slides, if possible I would split into separate modules. I would be worried that you may start to run out of memory. When you save if you add a lot more to this project Storyline is limited in how much memory it can address. I have one project that can only be saved 5 times before it runs out of memory and that takes 30 minutes plus to save.
One thing I'd agree with Phil on is that variables may have an impact...variables, especially built in ones that you can't pare down, are some things that cannot be removed once they exist.
Another thing - in reflecting on Phil's comment about the C: - Are you working off a Google Drive Stream? Asking because when the C:/ is depleted, this impacts the available resources on the G:/.
Thanks for all of the suggestions. I have to keep this as 1 project because of the way that it is going to be used. I have been told that there isn't a limit to the amount of slide that can be used in a project. the entire thing is only at 203,548kb... I have reinstalled and reformatted the title.
I can get it to save in a decent time now. But generating a preview takes a really long time. Is this normal?
9 Replies
Hi Sean and welcome to E-Learning Heroes. 😊
Thank you for reaching out and sharing what you experiencing with previewing and saving your project.
If you'd like to work directly with our support team, you can contact them directly here.
Have you tried having another instance of SL open and copying the slides one by one across to the new instance.
Occasionally a SL file corrupts and gets larger with each save and this has cured it for me in the past.
save you new version using version control so if a specific slide is causing problems you can always roll back to the previous version.
Hope this helps
I definitely agree with trying the Import to a new project route that Leslie mentioned. Just be sure that your Story size in the new file matches what you're going to import in, before doing so.
If that doesn't work, there may be a few other options to try and get it into a new project file.
1. I also agree with importing to a new project
2. Not ideal, but sometimes if you go slide by slide on an import, you can figure out which slide is being the problem child, and can build that one out independently.
I would close the current file after you save to remove the undo buffer. Then reopen and do a save as to a different file name to clear out and oddities in the media library.
I am not an advocate of importing into a new file, this can cause so many issues such as extra slide masters, renamed results variables that it is a last resort for me and have probably used once in ten years.
There are things that can make saving always a slow process that you cannot change, lots of videos, different languages in the same file or even lots of large images. You may also have limited space on your C: drive.
You mention on LinkedIn that you have 550 slides. That is likely the reason your save is slow. Most of the courses I have that save slow have lots of slides, if possible I would split into separate modules. I would be worried that you may start to run out of memory. When you save if you add a lot more to this project Storyline is limited in how much memory it can address. I have one project that can only be saved 5 times before it runs out of memory and that takes 30 minutes plus to save.
One thing I'd agree with Phil on is that variables may have an impact...variables, especially built in ones that you can't pare down, are some things that cannot be removed once they exist.
Another thing - in reflecting on Phil's comment about the C: - Are you working off a Google Drive Stream? Asking because when the C:/ is depleted, this impacts the available resources on the G:/.
Thanks for all of the suggestions. I have to keep this as 1 project because of the way that it is going to be used. I have been told that there isn't a limit to the amount of slide that can be used in a project. the entire thing is only at 203,548kb... I have reinstalled and reformatted the title.
I can get it to save in a decent time now. But generating a preview takes a really long time. Is this normal?
For 550 slides that would be normal. The second preview should be faster than the first
Sent from my iPhone