I just started working with Storyline 2, and on several occasions when I return to work on a course and then try to save my work, I get a get a message saying "can't save, data file is corrupt".
I've seen similar messages from other users. Is it safe to continue using Storyline 2?
Thank you Wendy. I'll give your suggestions a try, but I'm concerned about continually losing work if there is an unresolved issue with Storyline 2. I've been saving work about every two sides, but the last four versions all give the corrupt data message, so I lost a lot of work.
Having the same issue with corrupted data, recovery file is corrupt, am working locally, the issue is with a slide on which I use an image with 100 states to combine with a sliderto create a nice 'look around' 3d effect, the file has corrupted twice on this. There is a possibility that it is caused by the fact that I copied the image with the states and then replaced the base image, who knows, it's a bit of a drama and has happened three times now. I have solved it before by copying and pasting the slides into a new file but this time it is giving me issues with copy and past as well. I'll let you know if I find out anything else
so far:
Yes I work locally and so on, plenty of ram, harddrive, latest update and bla.
Storyline file corrupt
Issue with slide on which uses image with many 90+ states
possibly issue because image is a changed duplicate
sent issue to storyline via the automatic sent option
copy and pasting from corrupt file to new file is not working properly
the slide that is causing the issue also has many triggers in conjunction with a slider, I don't think the triggers are a cause of the issue, the slide did share the same slidervariable as another slide which I will change
ok I restarted computer, removed the slide, created a new file, imported the slides. I noticed I could not copy and paste or cut and paste all the slides from one file to the other, which was unusual. I'll let you know how I go with the recreation of the culprit slide, which off course had to be the most convoluted slide to create:).
Thanks for sharing that information and update here. You mentioned copying and pasting slides, have you tried importing them in? I typically recommend that as I've seen others have odd or unusual behavior with copy/paste. If you continue to have difficulty with the file, we're also happy to take a look at it and see if there is anything else we can spot wrong with the file or course - you'll want to send it along here to our team for further investigation and let us know the specific slides that are problematic.
I did have to import the files later as indeed some really strange things happened with copy paste, to be exact if I selected and copied several slides only a couple or one would paste into the new file. After this happened I used the import function, luckily I make sure i make consistent saves such as filenamev1_0.story and filename1.1.story and so on, just in case this happens.
What I noticed is that one slide with an mp4 video file did not import with the group and had to imported separately, I will strip the file to contain the issue slides and send it for investigation.
I created a new slider and new image with multiple states (now 60, previously 100)
States triggered by the slider
This time I made sure the slider was not a copied slider
The states weren't a 'replace image' but images on top of a unique rectangle to avoid any potential optimisation routines that may be running in the background on duplicated images.
Thanks Byron for that update - and it sounds like the copy/paste may have played into this, and also perhaps the MP4 you mentioned? You'll want to check that the files are also saved locally before importing and that the file names adhere to the other guidelines here.
Having a similar issue. I have rebuilt the entire course in a new file, but it seems that as soon as the storyline file becomes bigger than 1gb it gives me this issue.
Corrupted slides can occur at ANY time within Storyline 2.
If your AS2 project gets corrupted, there IS a solution:
0. CLOSE your existing project, saving any changes if necessary.
1. Create a NEW, BLANK Storyline 2 Project and SAVE under a DIFFERENT filename.
2. Import your old corrupted project's content into the blank Project.
3. Save, close, and re-open the NEW Project.
Your project should now be reset and free to continue as normal.
As a general rule of thumb, I usually save my project under a new filename/version number once every 10-15 minutes or so, or even more frequently, if I am keying in detailed changes.
Are those video files that are making the project exceed 1gb, large files in any software often cause issues.
I'd probably chose to:
- Split the file into scenes and create a couple of projects no bigger than 300mb which I would merge at a later state into an import version.
- If you are using video, see if you can compress the video further, I would use handbrake or I let Storyline publish and compress after which I find the compressed video file in the storyline publish/story_content, this also takes the edits such as crop and trim in account.
- with large files like that you may want to consider editing and compressing of video and images before you import them.
- You could place short placeholder videos whilst you are working on your project and replace them with large videos on the end of the project.
- you could consider placing video content on a server and call in the videos through using webobjects or external links
- you often can reduce issues down to a single slide, if this happens, create a new project, import all slides except the problem slide into a new project. I have had issues due to duplicating sliders, and large amount of states(50+) on one element, creating new sliders fixed the issue. I have also had issue with video.
- Also maybe check your scratch disk settings and to which drive storyline writes.
It worked for a while. Now the issue is back -_- is there a way to get Storyline to use more ram and multicores? finding so many issues with SL2 lately.
What exactly worked for a while? You can only eliminate the issue through deductive elimination of possible causes. You'd have to try all variations to reduce the issue down to an instance, this way support or community will be much better able to help you.
e.g. storyline goes corrupt everything I use more than 200gb of video with codec such and so.
The real trick for me is to separate the files into separate Storyline files and find the culprit that is causing the crash. Any file on any software of that size will start creating issues for me,
3d software, photoshop, sfter effects all tend to crash when they get top heavy, it's painful I know. Your best bet is to make sure you have plenty of ram and allocate and look at the scratch disks also known as virtual memory, which is what you are heavily dependent on with a large file exceeding your ram. It also helps if the virtual memory is on a fast SSD and your system is of high end specifications, suitable to the large file work that you are doing. This means that all the compnonents such as processor, motherboard, ram, cache etc. need to be of a substantial level meant for high end applications such as photo-editing and video editing.
I would still recommend working in the smallest storyline files possible to pinpoint what is causing the issue, it may be a duplicate slide or a video codec.
18 Replies
Hi David
here is a thread about the auto save feature. Perhaps you have a recovery file you could continue with.
https://community.articulate.com/discussions/articulate-storyline/storyline-2-autorecovery-auto-save-where-do-i-find-the-file
IMO If you keep losing work in the same project I would create a new project file and import the slides in to see if that makes a difference.
Thank you Wendy. I'll give your suggestions a try, but I'm concerned about continually losing work if there is an unresolved issue with Storyline 2. I've been saving work about every two sides, but the last four versions all give the corrupt data message, so I lost a lot of work.
David Lautenschlager, Ph.D.
wdl0355@me.com
Hi David
are you working locally and not from a USB or network drive as that sometimes causes issues. see here
Do you have the latest update '3' installed --> link here
Here are a couple of links to read up on that might help you
http://www.articulate.com/support/storyline-2/unexpected-or-erratic-behavior-in-articulate-storyline-2
http://www.articulate.com/support/storyline-2/how-to-repair-articulate-storyline-sl2
I am working locally, but will check to see if I have the latest version. Thanks for the additional links.
David Lautenschlager, Ph.D.
wdl0355@me.com
Hi David,
Just an FYI, when you reply via email your signature is included in the forum post so you're welcome to delete that if you'd like.
Having the same issue with corrupted data, recovery file is corrupt, am working locally, the issue is with a slide on which I use an image with 100 states to combine with a sliderto create a nice 'look around' 3d effect, the file has corrupted twice on this. There is a possibility that it is caused by the fact that I copied the image with the states and then replaced the base image, who knows, it's a bit of a drama and has happened three times now. I have solved it before by copying and pasting the slides into a new file but this time it is giving me issues with copy and past as well. I'll let you know if I find out anything else
so far:
kind regards
Byron
ok I restarted computer, removed the slide, created a new file, imported the slides. I noticed I could not copy and paste or cut and paste all the slides from one file to the other, which was unusual. I'll let you know how I go with the recreation of the culprit slide, which off course had to be the most convoluted slide to create:).
Hi Byron,
Thanks for sharing that information and update here. You mentioned copying and pasting slides, have you tried importing them in? I typically recommend that as I've seen others have odd or unusual behavior with copy/paste. If you continue to have difficulty with the file, we're also happy to take a look at it and see if there is anything else we can spot wrong with the file or course - you'll want to send it along here to our team for further investigation and let us know the specific slides that are problematic.
Hi Ashley, thank you for your response as always.
I did have to import the files later as indeed some really strange things happened with copy paste, to be exact if I selected and copied several slides only a couple or one would paste into the new file. After this happened I used the import function, luckily I make sure i make consistent saves such as filenamev1_0.story and filename1.1.story and so on, just in case this happens.
What I noticed is that one slide with an mp4 video file did not import with the group and had to imported separately, I will strip the file to contain the issue slides and send it for investigation.
Kind regards
Byron
I removed the slide that gave the issue.
so far so good
Thanks Byron for that update - and it sounds like the copy/paste may have played into this, and also perhaps the MP4 you mentioned? You'll want to check that the files are also saved locally before importing and that the file names adhere to the other guidelines here.
Having a similar issue. I have rebuilt the entire course in a new file, but it seems that as soon as the storyline file becomes bigger than 1gb it gives me this issue.
Is there a decent fix for this yet?
Hi, Mitch -- Thank you for reaching out and so sorry to hear of your troubles! Just to confirm, may I ask if you are working locally, and have you gone through the troubleshooting steps listed here to see if you find improvement? If so and issues persist, perhaps you might want to connect directly with our Support Engineers here for additional technical insights.
Just a reminder for everyone:
Corrupted slides can occur at ANY time within Storyline 2.
If your AS2 project gets corrupted, there IS a solution:
0. CLOSE your existing project, saving any changes if necessary.
1. Create a NEW, BLANK Storyline 2 Project and SAVE under a DIFFERENT filename.
2. Import your old corrupted project's content into the blank Project.
3. Save, close, and re-open the NEW Project.
Your project should now be reset and free to continue as normal.
As a general rule of thumb, I usually save my project under a new filename/version number once every 10-15 minutes or so, or even more frequently, if I am keying in detailed changes.
Hope this helps!
Great tips here, Mark, and I am sure others who come across this discussion will find that reminder to be useful, as well!
Hi Mitch,
Are those video files that are making the project exceed 1gb, large files in any software often cause issues.
I'd probably chose to:
- Split the file into scenes and create a couple of projects no bigger than 300mb which I would merge at a later state into an import version.
- If you are using video, see if you can compress the video further, I would use handbrake or I let Storyline publish and compress after which I find the compressed video file in the storyline publish/story_content, this also takes the edits such as crop and trim in account.
- with large files like that you may want to consider editing and compressing of video and images before you import them.
- You could place short placeholder videos whilst you are working on your project and replace them with large videos on the end of the project.
- you could consider placing video content on a server and call in the videos through using webobjects or external links
- you often can reduce issues down to a single slide, if this happens, create a new project, import all slides except the problem slide into a new project. I have had issues due to duplicating sliders, and large amount of states(50+) on one element, creating new sliders fixed the issue. I have also had issue with video.
- Also maybe check your scratch disk settings and to which drive storyline writes.
- definitely work locally
Thank you for the suggestions.
It worked for a while. Now the issue is back -_- is there a way to get Storyline to use more ram and multicores? finding so many issues with SL2 lately.
What exactly worked for a while? You can only eliminate the issue through deductive elimination of possible causes. You'd have to try all variations to reduce the issue down to an instance, this way support or community will be much better able to help you.
e.g. storyline goes corrupt everything I use more than 200gb of video with codec such and so.
The real trick for me is to separate the files into separate Storyline files and find the culprit that is causing the crash. Any file on any software of that size will start creating issues for me,
3d software, photoshop, sfter effects all tend to crash when they get top heavy, it's painful I know. Your best bet is to make sure you have plenty of ram and allocate and look at the scratch disks also known as virtual memory, which is what you are heavily dependent on with a large file exceeding your ram. It also helps if the virtual memory is on a fast SSD and your system is of high end specifications, suitable to the large file work that you are doing. This means that all the compnonents such as processor, motherboard, ram, cache etc. need to be of a substantial level meant for high end applications such as photo-editing and video editing.
please find a link on how to set your virtual memory here https://community.articulate.com/discussions/articulate-storyline/suggestions-on-using-less-memory-when-creating-a-course
I would still recommend working in the smallest storyline files possible to pinpoint what is causing the issue, it may be a duplicate slide or a video codec.
Hope this helps
This discussion is closed. You can start a new discussion or contact Articulate Support.