[Marketing] Youtube channel

[Sean DALY]

I think having a YouTube channel is a grand idea, what we need are videos.

My objection to YouTube at the time was its exclusion of XO learners - the
vids would have been unavailable to children using Sugar.

The Sugar unfamiliarity barrier can be reduced with screencam videos
explaining the interface. These have the advantage of showcasing the
software, not the hardware where Sugar has always played second fiddle to
the XO.

I tried for some time to define a screencam workflow including cursor and
came up with only two solutions, neither of which are simple for community
members:

* Run Sugar virtualized fullscreen on Mac OS X, capture possible with many
tools but in particular vanilla QuickTime; transcode to OGV or H.264 at the
command line using ffmpeg2theora [1] (easily installed & updated with
fink). Disadvantage: the screen resolution does not match the XO's and
could disorientate kids using XOs (they can detect very minute differences
but also adjust to them!)

* Add an external USB to VGA video card to an XO, capture analog video on a
second machine (I used an H.264 digitizer on a Mac and transcoded as
above). I purchased one of these gadgets for around $100 (plus $100 for the
Mac digitizer), it has also been very useful for displaying XO output on
big screens at conferences. This method simplifies live voiceover, sound
capture, or both.

Sound complicates things. For sound-free screencam vids, voiceover is best,
either live at capture time or in post-production. Ideally, an explanatory
video for say Turtle Art would follow a script, simplifying translation and
voiceover in other languages and subtitles too. Screencam vids with sound
would probably be best as is, but the capture workflow needs to handle that.

Other types of videos would of course work, such as installation and
configuration how-tos (the installation barrier being the other great
hurdle to Sugar evaluators) and even talking-head vids (the enthusiasm of
community members is infectious cf. the YouTube Turtle Art Day vids [2]).

A video of Sugar used in a classroom would of course be very helpful. Most
such videos I have seen show kids working on / excited by their XOs but
skip the pedagogical aspect - a teacher prospect would like to see how a
teacher in the classroom organizes the session and what kids actually do.

I'm not sure I ever learned who has the access codes to our Dailymotion
channel [3], I believe a colleague from the OLPC France association.

Sean

1. http://v2v.cc/~j/ffmpeg2theora/
2. https://www.youtube.com/user/TurtleArtDay
3. http://www.dailymotion.com/sugarlabs



On Thu, Jan 9, 2014 at 1:03 AM, Ron Feigenblatt <docdtv at gmail.com> wrote:

> Hello,
>
> On 1/8/14, Walter Bender <walter.bender at gmail.com> wrote:
> > Have you seen this one:
> >
> > http://www.youtube.com/watch?v=tm5VdvRMvo4&feature=youtu.be
> >
> >> On Mon, Jan 6, 2014 at 2:10 AM, Sameer Verma <sverma at sfsu.edu> wrote:
> >>>
> >>> With the beginning of the new year, I'd like to (re)propose that
> >>> Sugarlabs have a YouTube channel to highlight both screencapture style
> >>> snippets and short interviews of users and developers of Sugar.
> >>>
> >>> Youtube is the largest video site out there. It only helps to be
> visible
> >>> on it.
> >>>
> >>> cheers,
> >>> Sameer
>
> I am with you 100% Sameer. "Publish YouTube videos" was practically
> the first thing I
> wrote to Sean when I touched based with him years ago. And after it
> embraced an OS
> codec, his one objection was removed.
>
> YouTube doesn't do speech recognition well on the video Walter cites.
> But it does let
> one automatically translate such "automatic captioning" to the
> language of one's choice.
> I hope by now it also supports likewise translation of any .srt
> caption file one provides, too.
> Automatic language translation is another reason to favor YouTube over
> similar sites today.
>
> Ron
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/marketing/attachments/20140109/81e307c8/attachment.html>