Cannot encode video!

May 12, 2015

I try to trim videos from my own screen recordings in Storyline 2, but I always get this message that "The video cannot be encoded."

Why? Can someone please help me with this?

Thanks!

/Sandra

18 Replies
Ashley Terwilliger-Pollard

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.
Sandra Eriksson

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.
>

Sandra Eriksson

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

Ashley Terwilliger-Pollard

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. 

Mark Basher

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.

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