Did you conduct the screen recordings in Storyline or in another screen recording tool? If you've done the recording outside of Storyline, it's worth noting that Storyline supports a number of codecs and bitrates, but the best option for an MP4, is the H.264 codec. Do you know what file type for your video you're working with?
I made and conducted the screen recordings in Storyline and I just clicked
"Save" when the programme asked between "Save" or "Cancel". Didn't use any
other program at all.
I thought producing everything in S2 without using any other programme
would be the easiest way since everything would immediately be saved in the
right type of format etc.
So what should I do now?
Do I have to "re-save" everything in another format? And how do I do that?
I still have many screen recordings to produce and without problems would
be nice.
/Sandra
My apologies if I confused you, from your original post I wasn't certain if the initial videos/recordings were conducted in Storyline or not - so I wanted to share the additional information. I haven't seen that error message before when conducting a screen recording within Storyline, so first I'd want to confirm that you're working on project files as described here and than I'd ask for you to go through the repair steps here.
Please let us know how it's behaving after checking into those elements.
Did you check into the other items I mentioned for Sandra? If so, can you share a copy of the .story file before you conducted any trimming and we'll take a look?
Did you check into the last items that I mentioned in regards to working locally, etc. We'd be happy to take a look at your file as well if you'd like to share a copy of the .story file here with us.
I checked into the last items etc, but it still doesn't work for me to save
changes (for ex trim or cut) in a video.
Here is a copy of one of the videos.
Hi all, user base I support was faced with a similar issue following rollout of Windows 8.1. assigning Admin rights did fix it but this was not a feasible solution for the environment.
Issue was AppLocker and users were being blocked from running the encoder.exe from their Local profile file temp folder.
When trimming video the application creates folders in %OSDRIVE%\Users\%Username%\AppData\Local\Temp\Storyline\Articulate and runs the encoder.exe from inside these folders. A rule to allow users to run .exes from any folder under this path was the solution.
My clients' Moodle has browsers compatibility issues. Original videos in MP4 format imported into Storyline 3 did not work. So I converted the MP4 videos using free online video into AVI format. Then imoprted them back into Storyline and they worked.
18 Replies
Hi Sandra,
Did you conduct the screen recordings in Storyline or in another screen recording tool? If you've done the recording outside of Storyline, it's worth noting that Storyline supports a number of codecs and bitrates, but the best option for an MP4, is the H.264 codec. Do you know what file type for your video you're working with?
Also, the following types of videos can't be edited using the features of Storyline's video editing:
Sorry, forgot!
File type for my video is mp4.
How do I choose H.264 codec? Don´t really understand. :/
/Sandra
2015-05-12 17:20 GMT+02:00 E-Learning Heroes :
> [image: E-Learning Heroes]
> ------------------------------
> Reply to Cannot encode video!
>
>
> *Ashley Terwilliger replied:*
>
> Hi Sandra,
>
> Did you conduct the screen recordings in Storyline or in another screen
> recording tool? If you've done the recording outside of Storyline, it's
> worth noting that Storyline supports a number of codecs and bitrates, but
> the best option for an MP4, is the H.264 codec. Do you know what file type
> for your video you're working with?
>
> Also, the following types of videos *can't* be edited using the features
> of Storyline's video editing:
>
>
> - *SWF* movies can't be edited in Storyline. You'll need to use
> third-party editing software, then import the edited file into Storyline
> again.
> - *FLV *videos with alpha channel transparency can't be edited in
> Storyline. (Videos without transparency can be edited.)
> - Website videos (Screenr, YouTube, Vimeo, etc.) can't be edited in
> Storyline.
>
> Reply
>
> View
>
> ------------------------------
>
> To post a response, simply reply to this email.
>
> You received this email because you subscribed to this discussion.
> Unsubscribe
>
> © 2015 Articulate Global, Inc. All rights reserved.
>
Hi and thanks for answering!
I made and conducted the screen recordings in Storyline and I just clicked
"Save" when the programme asked between "Save" or "Cancel". Didn't use any
other program at all.
I thought producing everything in S2 without using any other programme
would be the easiest way since everything would immediately be saved in the
right type of format etc.
So what should I do now?
Do I have to "re-save" everything in another format? And how do I do that?
I still have many screen recordings to produce and without problems would
be nice.
/Sandra
Hi Sandra,
My apologies if I confused you, from your original post I wasn't certain if the initial videos/recordings were conducted in Storyline or not - so I wanted to share the additional information. I haven't seen that error message before when conducting a screen recording within Storyline, so first I'd want to confirm that you're working on project files as described here and than I'd ask for you to go through the repair steps here.
Please let us know how it's behaving after checking into those elements.
I have the exact same issue. I cannot trim a video that I recorded in Storyline 2. Attached is the screenshot of the error.
Hi Jason,
Did you check into the other items I mentioned for Sandra? If so, can you share a copy of the .story file before you conducted any trimming and we'll take a look?
If you get an answer/solution for this problem then I would really
appreciate if you could send me an e-mail. Thanks!
Best regards Sandra
Hi Sandra,
Did you check into the last items that I mentioned in regards to working locally, etc. We'd be happy to take a look at your file as well if you'd like to share a copy of the .story file here with us.
Hi!
Sorry for the delay!
I checked into the last items etc, but it still doesn't work for me to save
changes (for ex trim or cut) in a video.
Here is a copy of one of the videos.
Hope you can find what's wrong.
/Sandra
Hi Sandra,
Replying via email doesn't include any attachments here, so you'll need to visit the thread to update with the video attachment.
Sorry, I am trying to sent a copy of the file via the thread, but it seems
i cannot even click on the post reply-button. Don`t know what´s wrong.
Is there any other way I can send a copy to you?
/Sandra
Hi Sandra,
If you're unable to post the file here in the forums, you can send along to us here. Please let me know once you've submitted it.
Thanks Ankit for sharing those steps here and I'm glad the first solution was able to resolve it for you.
Hi!
Thanks for answering!
Since yesterday I have Administrator rights and now it works perfectely! =)
Thanks once again!
//Sandra
Happy to hear it Sandra and thanks for the update.
Hi all, user base I support was faced with a similar issue following rollout of Windows 8.1. assigning Admin rights did fix it but this was not a feasible solution for the environment.
Issue was AppLocker and users were being blocked from running the encoder.exe from their Local profile file temp folder.
When trimming video the application creates folders in %OSDRIVE%\Users\%Username%\AppData\Local\Temp\Storyline\Articulate and runs the encoder.exe from inside these folders. A rule to allow users to run .exes from any folder under this path was the solution.
Thanks Mark for sharing that information here - and I'm glad that you were able to figure it out and work around the issue for your users.
My clients' Moodle has browsers compatibility issues. Original videos in MP4 format imported into Storyline 3 did not work. So I converted the MP4 videos using free online video into AVI format. Then imoprted them back into Storyline and they worked.
This discussion is closed. You can start a new discussion or contact Articulate Support.