Skip to main content

Thoughts Regarding the Use of Subtitles in Videos

 

Videos are a great way of getting Bible stories out to people, including children. If the audience is literate, it is often a good idea to include subtitles with videos. Even if they are functionally illiterate, it might make sense to include them, so as to encourage growth in literacy amongst the group. In YouTube it is possible to add these later in YouTube Studio. You can also allow others to add subtitles for their language, if you wish. For social media platforms like Facebook it is often better to hardcode the subtitles onto the video. If you are using a program like Shotcut this is not possible. You have to download another program that has this option e.g. Filmora (though this needs to be paid for) and Kdenlive (free and open source). If you want a program that is easy to use, go for Filmora over Kdenlive, as the former has a really nice user interface.

The reason we want to include subtitles is that people sitting on a bus, or in a waiting room, or somewhere like that, want to watch short videos on YouTube and other platforms without having to listen to the audio. There is usually an option to turn sound off within the program, and many users have this set to no audio by default. If they get really interested in a video, they might plug in their ear buds and turn on the sound. Might. 

The received wisdom on length of videos is that longer ones need to go on YouTube. If you only have short videos, other platforms are fine. You can put them on YouTube as well.

It is possible to create the subtitles in YouTube, by copying and pasting from Paratext or similar Bible program, then editing them to get rid of punctuation marks. Videos with quote marks and so on are not popular with viewers. It is possible to download the subtitles and timings in a settings file such as an .srt file. This can then be imported into Kdenlive or Filmora to create a video with hardcoded subtitles. The reason to use YouTube is that Studio is a really convenient subtitle editor - much better than the ones you'll find in Filmora or Kdenlive. Shotcut doesn't allow subtitles, unfortunately.

The really useful feature in YouTube is that viewers can turn subtitles on and off at will, change the language, and even speed up the video, whether or not they are reading the subtitles or listening to the audio. This can probably be done in other programs but I haven't tried it myself.

All in all, try and make the videos appropriate for the chosen (target) audience. It's no good going to all the work of creating subtitles when 99% of your audience can't read.

Labels:

Comments

Post a Comment

Popular posts from this blog

10 Reasons to Make Scripture Impact a Priority

This is a response to some recent posts about the importance of Bible translation in fulfilling the Great Commission. Yes, there is much truth in that, but more is needed. It really helps to have Scripture impact (or 'engagement') the top priority, the 'car' as it were, with translation the engine that sits beneath the bonnet. Not all drivers need to know all the details of the engine, but they need to be able to control the vehicle. The most important thing is to be able to get from A to B (see point 2), rather than knowing how the engine works. These are the ten reasons to make Scripture impact a priority: To help people flourish in their communities. There are all kinds of needs that need to be met for people to flourish. One is clean water. Another is good sanitation. Peace (lack of war), and freedom of religion. Access to education etc. etc. For a community to truly flourish they also need access to the Scriptures in a language (or languages) that they understand a...
Post a Comment
Read more

A Flow Chart for Bible Translation (a Relevance Theory Approach)

One of the current theories behind modern translation work is Relevance Theory. [1] Here is a flow chart that explains the process often used to produce a draft when using such an approach: *Make sure your translation committee makes the decision as to what kind of translation they want. A domesticated translation is one that submits to dominant values in the target language [2] whereas a foreignized translation is one that is happy to import foreign terms and ideas from Hebrew, Greek, or the language of wider communication such as the Greek term baptizo . The chart looks something like this: Text                                   Communicated Ideas                  Context A sower went out to sow  A farmer went out to sow grain   People scattered/threw seed etc. The text has very little information, but behind i...
Post a Comment
Read more

Asking the Right Questions in Bible Translation and Scripture Engagement Planning

If you want to get useful answers you have to ask the right questions. Do you agree? Yes, of course you do. In the Bible translation world we often ask a very narrow question when planning for the next stage of work: 'What would you like to see translated next?' Now, if you simply want to translate, and that's it, that question is fine, but what if you want to see some kind of result from your translation work? What if, for instance, you want to see transformation occur? Then a more powerful question to ask the community and positive stakeholders in the project would be: 'What kingdom goals would you like to see reached?' These kingdom goals should meet felt needs of the community - they should solve problems that are apparent to most or all in the community. See below on how those can be met. If that's too abstract, then try, 'What kinds of things, in your extended family, do you tend to worry about?' This will help establish some felt needs, from which...
7 comments
Read more