Im deaf and rely on subtitles/closed captions to enjoy movies. A large number of recently uploaded movies available for rent/purchase through itunes Australia do not come with subtitles/CC. Some examples include: 12 Years a Slave, The Spectacular Now and Love, Rosie. All of these three movies have subtitles/CC on the USA itunes store, but not in Australia's itunes store.
What's the best way to make Apple Australia more disability friendly? Start a petition? Or should I go undercover an start purchasing movies from the US itunes store via US itunes vouchers? Report them to the Human Rights Commission? I've already enquired via the itunes help service but that didn't help as my query went to a team based in the USA who obviously are not able to influence itunes Australia's policies. They did not offer a suggestion as to what I should do in order to encourage itunes Australia to provide subtitles/CC on their movies.
It doesn't make sense that a film studio would discriminate based on country. For example, US iTunes have over 90% of their films subtitled, while in Australia's iTunes, only two of the current top five movies are subtitled. So if the US iTunes is offered movie rights with subtitles, so should Australia's iTunes.
I'm told it is Apple Australia's choice, as they choose to not pay for that little extra to buy the subtitles when they purchase the movie rights from the film studio. All studios provide their movies with a range of subtitles/captions (as demonstrated in US iTunes), but often as an additional cost.
Write to your government and file a formal complaint against studios/distributors/rights-holders, encourage the government to make an effort to make legalisation that request those studios/distributors/rights-holders to have to supply movies with subtitles. Also check your Australian laws, and see if there are any legalisations in there that you can use against the studios [...], and sue them.
It's not Apple's choice as to what content is available where, and what subtitles they have on the films, they can only sell in a particular country what they are licensed to sell. You can try requesting that the versions with subtitles be added to the Australian store (but without the rights-holders agreement it can't happen) :
The film studio or the distributor/rights-holder for a country keep the rights to their content - Apple don't buy the rights and they have no control over where a film (or any other item) is available for sale.
The studio/rights-holder grant Apple a license to sell their content in the iTunes store on a country-by-country basis. But a film may have different rights-holders for different countries, the Australian rights-holder/distributor may not have bought the rights from the studio for the subtitled versions, and so can't supply them to Apple (or they have agreed an exclusive deal with a different online store for them).
Apple may not have any control over getting movies to sell, but they COULD try to encourage the studios/distributors to see that if downloads is going to be the future, replacing DVDs, then the studios could make a little extra money if they sell their downloaded movies with subtitles, because usually deaf people tend to not bother buying any movies if it got no subtitles.
Apple could say to the studios "If you want to sell your movies via iTunes, and get more money for your box office movies, could you please make an effort to put subtitles on your movies for the deaf people!" If Apple and other services, like Netflix, could say to the studios "We're not selling those movies unless there are subtitles on them." The studios could lose money if they can't get to sell their movies as downloads.
Nope. I myself am mildly hearing impaired and always watch movies on TV with closed captioning on. But my post was about subtitles (i.e., words that are translations from the spoken language of a film), not closed captioning (i.e., words in the same language as the film, primarily meant as hearing assistance). They are different things.
Last time I checked, KMPlayer could output reading aloud of subtitles only via SAPI5 - no screen reader involved in this case. I don't know if braille output is possible in this case, but somehow - I doubt it.
On the other hand however, PotPlayer can output reading aloud of subtitles not only via SAPI5 or OneCore (with no screen reader involved), but with the screen reader involved (via UIA). The choice is left to the user. The options for configuring how the subtitle reading will occur Are located in PotPlayer's settings (opened with F5) -> Accessibility. The first group of options are for outputting via SAPI5/OneCore (TTS). The second group is for outputting via the screen reader. In the second choice, the subtitles are outputted as the title of the window. I don't know if this will help with reading the subtitles via braille, but you can try it and see. To stop the screen reader from reading the subtitles aloud via its voice, you can try disabling its speech (e.g. for NVDA - Insert+S or selecting "No Speech" as the current synthesizer). As I said - I'm not sure how well this will work, but try it if you want.
Hint: If you use the reading aloud via the screen reader option of PotPlayer and configure the screen reader to lower the volume of other audio while speaking, you can get a not bad dubbing result (winking smile).
It is hard to believe that actual people sit down to do the tedious task of writing down subtitles, who aren't even credited as part of the film. So how exactly are subtitles written? Do people write them? Or is there a software that can do that for you?
Subtitles designed for hearing people will not include these sound cues because the hearing people can... well... hear them. Generally these are used when translating subtitles from another language. In the US, at least, this is generally just called "subtitling"
Subtitles designed for deaf people will include these descriptions because they add details that explain why someone reacts to certain things. Because they can't hear the audio cues, they need textual versions. They add depth to the movie watching experience. These are usually subtitles written in the same language as the spoken language in the film. This is a specialized form of subtitling often referred to as "captioning".
"Captions" aim to describe to the deaf and hard of hearing all significant audio content - spoken dialogue and non-speech information such as the identity of speakers and, occasionally, their manner of speaking - along with any significant music or sound effects using words or symbols.
Most good subtitles are done manually and are either stored in a separate file marked with time code queues or they are hard coded into the video. The latter is more often done with films that have scenes in a language different from the bulk of the film or, occasionally, with fan subs but, usually, they're a separate file. If they are a separate file, that is referred to as "closed captioning" and if they are burned in, that is "open captioning".
The term "closed" (versus "open") indicates that the captions are not visible until activated by the viewer, usually via the remote control or menu option. On the other hand, "open", "burned-in", "baked on", or "hard-coded" captions are visible to all viewers.
Creating these files can be done with a variety of available software options but they are painstaking and difficult to make so you should appreciate the people who take the time to make them (assuming they're done well).
Some websites have bots that do subtitling. They use voice recognition to approximate the words being spoken. They're usually really bad. Youtube has this. If the creator of the video doesn't include a subtitle track, they will create one for you.
YouTube is constantly improving its speech recognition technology. However, automatic captions might misrepresent the spoken content due to mispronunciations, accents, dialects, or background noise. You should always review automatic captions and edit any parts that haven't been properly transcribed.
As to the timing, unless the dialogue is revelatory, the timing isn't really that important. A half second lead or delay isn't going to annoy people that much, so most of that granularity is simply a "because we can" thing. Multiple second delays or leads are a problem and you can actually usually sync the subtitles better (or edit them otherwise) if you have the software and can separate the files.
He has dictation software (Dragon), trained specifically to his voice. He listens to the TV show, and as he listens, he repeats the lines clearly into a microphone. The computer transcribes what he says.
This is somewhat more accurate than getting the software to try and understand the audio track of the TV programme directly, but fast enough that it works for live broadcasts (with a short delay and the occasional wrong word).
Many pieces of subtitling software help you sync stuff faster than doing it by trial-and-error, by allowing you to import your movie and showing you a waveform of the audio. It's easy to visually remember where a line starts and ends that way, so, once you've heard the audio once and you've transcribed/translated it (yes, manually), all you have to do is select the desired time frame by clicking and dragging and it sets the timecodes by itself.
Some programs also allow you to perform automatic quality checks on your subs. Now that Netflix is available almost everywhere on the planet, there is a lot of need for subtitlers, so they started hiring freelancers. So I was reading about Netflix's subtitling standards the other day and they recommend a few add-ons that show you whether you've passed the maximum number of characters per line, or whether you've exceeded the maximum reading speed, or whether you have useless leading/trailing spaces, whether you've timed your subtitles properly when near shot changes (!) etc., and those addons also allow you to export your subtitles to Netflix's preferred format.
3a8082e126