Have there been any recent changes to the output behaviour when publishing ?
I have a project that I published in early April, which created an output folder of 77MB ( which Zips to 52MB).
Re-publishing from the same original story file today, the output is now 108MB and it Zips to 84MB. This makes it too large to upload to a basic account on SCORM Cloud for testing.
The difference appears to all be in the "Mobile" folder in the output, where many of the files (mostly PNG and JPG) appear to be 50% larger, or more - hard to tell exactly, as the auto-generated filenames don't match exactly. Some files appear ten times the size.
Sorry to hear that you ran into this issue. We are currently tracking incidents where published Storyline courses are increasing in file size. We are seeing this occur in recent releases of the application. I’ve added this forum post to the report we have open for it so we can notify you as soon as a fix is released.
Thank you for reaching out! In Update 66, we've included important fixes and new features.
One of the fixes we've included is:
Publishing a project with the previous update caused larger file sizes in the published output.
To take advantage of this bug fix, launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
Please let us know if you have any questions by posting here or by reaching out to our Support Engineers directly.
We just updated to Build 3.68.28773.0 and just began having this problem. Unfortunately, we are low priority on our IT's list so we jumped (skipped) many updates to where we are now including Update 66 which is supposed to fix this issue but all previous updates should be included in 68, correct??
You are correct. The updates in version 66 should be included in version 68. I'm sorry you are having this issue! We would love to troubleshoot this for you! Would you be willing to share your file here or with our support engineers privately in a support case?
there was a significant update/change for publishing images
before - import a big png (width/height) into the course and scale it in storyline, then publish the course -> png is resized while publishing (look at the filenames of the images in the publish folder)
now - import a big png (width/height) into the course and scale it in storyline, then publish the course -> png is NOT resized anymore -> so the file size can increase significantly
example: - original PNG 1 MByte, scaled in storyline to 50% - then publish - before: around 0.25 MByte - now: 1 MByte
Is there any fix for this? We are having the same problem, and I can't revert back farther than update 67. Currently our file is too big for our LMS, and every time we replace an image with a smaller version of the image, the file gets larger. I just replaced 10 images (previously 4MB, now 95KB) - and my file grew by 2.5Mb. I opened a support case, but I'm trying for answers anywhere. Also, publishing with a lowered image quality produces a larger published file than if I publish with standard quality.
11 Replies
screenshots of the names and sizes of a few of the files in the old small version and the new larger one.
Hi Archie,
Sorry to hear that you ran into this issue. We are currently tracking incidents where published Storyline courses are increasing in file size. We are seeing this occur in recent releases of the application. I’ve added this forum post to the report we have open for it so we can notify you as soon as a fix is released.
As a workaround, you might consider downgrading your Storyline 360 installation to Update 62 so you can publish courses that would be within the limits of your LMS account.
Any news on this issue yet? We're managing to publish smaller files using the downgraded version, but it means we're now missing out on any updates.
Hi, Archie.
Thank you for reaching out! In Update 66, we've included important fixes and new features.
One of the fixes we've included is:
Publishing a project with the previous update caused larger file sizes in the published output.
To take advantage of this bug fix, launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
Please let us know if you have any questions by posting here or by reaching out to our Support Engineers directly.
We just updated to Build 3.68.28773.0 and just began having this problem. Unfortunately, we are low priority on our IT's list so we jumped (skipped) many updates to where we are now including Update 66 which is supposed to fix this issue but all previous updates should be included in 68, correct??
Hi Dan,
You are correct. The updates in version 66 should be included in version 68. I'm sorry you are having this issue! We would love to troubleshoot this for you! Would you be willing to share your file here or with our support engineers privately in a support case?
Thanks for reaching out!
there was a significant update/change for publishing images
before
- import a big png (width/height) into the course and scale it in storyline, then publish the course -> png is resized while publishing (look at the filenames of the images in the publish folder)
now
- import a big png (width/height) into the course and scale it in storyline, then publish the course -> png is NOT resized anymore -> so the file size can increase significantly
example:
- original PNG 1 MByte, scaled in storyline to 50%
- then publish
- before: around 0.25 MByte
- now: 1 MByte
result -> don't scale images in storyline
Is there any fix for this? We are having the same problem, and I can't revert back farther than update 67. Currently our file is too big for our LMS, and every time we replace an image with a smaller version of the image, the file gets larger. I just replaced 10 images (previously 4MB, now 95KB) - and my file grew by 2.5Mb. I opened a support case, but I'm trying for answers anywhere. Also, publishing with a lowered image quality produces a larger published file than if I publish with standard quality.
Hi Lindsay,
Thanks so much for reaching out! I'm sorry to hear you're experiencing this issue.
I see that you've opened a support case and you are working with my colleague Ian. You are in great hands!
Ian will reach out shortly via email to better assist you. Thanks so much for your patience.
not the quality of the imported image is the size problem - its the width and height of the imported image (especially with PNG)
you can see what happens with images and "publish to web"
[publish folder]\mobile\