My project is comprised of approximately 100 slides each lasting from 1 to 10 minutes long each filled with various multimedia. The total size of the project is approximately 4gb.
With my 16g RAM it has trouble on occasion, in the sense that it slows down or stops or even in some cases just crashes.
Is there any way that the slides could be compressed until in use?
Hi Ben! Is the slow-down occurring during the editing phase? If so, could you possibly break it up into different .story files for ease of editing, and then import them into a master file when you are ready to publish?
It looks like you tried to attach an image here but those won't come through when you respond via email so you'll want to visit the forum page and use the "add attachment" to upload anything else. Also, just an FYI that responding via email includes your signature here so you're welcome to edit the post to remove that information if you'd like.
As Crystal mentioned if you're able to share a copy of your .story file here with us we can take a look at the issue you're seeing.
We're having similar issues with large projects. A co-worker's project is only 184 MB, but it's comprised of over 300 slides. At this point in development, it's regularly taking up to 5 seconds to register a single mouse click, despite being located on her local hard drive.
From a cursory search of the forums, it appears this is a fairly widespread issue.
We *could* break the project down into individual .story files and recombine for publishing, but we deal in a high volume of projects with aggressive timelines, and that's an extra hurdle we have to jump over.
For these type of issues it's often been attributed to the overall system and amount of memory available or something specific in the file. Our team is happy to work with you one on one to figure out the root cause and then offer you some steps and advice to resolve it. If you'd like to reach out to our Support Engineers you can do so here, and they're around 24/7 to assist!
5 Replies
Hi Ben! Is the slow-down occurring during the editing phase? If so, could you possibly break it up into different .story files for ease of editing, and then import them into a master file when you are ready to publish?
That's what I've ended up doing but even at that it slows to a stop sometimes.
[image1.JPG]
Ben R. Griffin | Civil Aviation Security Instructor
Omni Air International
3303 N. Sheridan Road,<https://webmail.oai.aero/owa/redir.aspx?C=Hzx6COSB1k6EtG6Ct2CuINiVS2791dIIPqJlvZ9j
Hey Ben,
It looks like you tried to attach an image here but those won't come through when you respond via email so you'll want to visit the forum page and use the "add attachment" to upload anything else. Also, just an FYI that responding via email includes your signature here so you're welcome to edit the post to remove that information if you'd like.
As Crystal mentioned if you're able to share a copy of your .story file here with us we can take a look at the issue you're seeing.
We're having similar issues with large projects. A co-worker's project is only 184 MB, but it's comprised of over 300 slides. At this point in development, it's regularly taking up to 5 seconds to register a single mouse click, despite being located on her local hard drive.
From a cursory search of the forums, it appears this is a fairly widespread issue.
We *could* break the project down into individual .story files and recombine for publishing, but we deal in a high volume of projects with aggressive timelines, and that's an extra hurdle we have to jump over.
Hi Robert,
For these type of issues it's often been attributed to the overall system and amount of memory available or something specific in the file. Our team is happy to work with you one on one to figure out the root cause and then offer you some steps and advice to resolve it. If you'd like to reach out to our Support Engineers you can do so here, and they're around 24/7 to assist!
This discussion is closed. You can start a new discussion or contact Articulate Support.