Incomplete Import of 4:3 Course into 16:9 format

Oct 28, 2020

Hi everyone,

I need to convert courses from a 4:3 format into a 16:9 format. To do this, I opened a new project, set it to 16:9, imported the 4:3 course and set the project to "Scale to fit".

When the course is done importing, only a few of its elements are visible. As far as I can tell, they all appear on the time axis, but don't display for me or in preview mode. Also, a message pops up informing me that "an error has occured" (probably not exact wording, I am using a German interface).

I've tried this 4 times and the result is the same every time. Can someone advise on what the issue might be?

Thanks in advance!

 

Edit: I also tried to just change the format of the existing course, but many objects were out of whack as a result. I wanted to see if an import might work better.

3 Replies
Lauren Connelly

Hello Kolja!

Sorry, you're running into this error when changing the Story Size from 4:3 to 16:9. I haven't heard of a similar snag, so it might help us see the file.

With your permission, we'll take a look at your project file to investigate what's happening. We'll delete it after troubleshooting. You can upload it privately here: Support Upload Link

When you upload the file, we'll receive a notification. After reviewing the file, we'll get back to you as quickly as possible.

Laura Schlinke

Hi Lauren, thanks for replying and helping out. I just wanted to share the outcome of the support for others who run into the same issue and find this thread. The team wasn't able to recreate the error, so it was a bit of a mystery. I have tried using a different laptop since where the problem doesn't occur. I am fairly sure that the problem was due to the subpar computer I was using, which would explain why support had no way of recreating the problem.

It might have to do something with RAM or the speed of the HD. The loading times for story files were generally very long (up to 10 minutes until a media-heavy heavy course loaded) and I suspect that that's where the problem lay.

This discussion is closed. You can start a new discussion or contact Articulate Support.