oh, thank you.
OK, this is going to be a bit messy. I’m going to have a stab at a series of posts looking at how to best make use of the 1MSME-L kit. The more I look at it, the more there is so I thought I’d get started with something simple. This is a full blogpost with links and a photo from my flickr stream – bog standard blogging, from a table in Starbucks.
This is my basic workflow – plan, compose, edit, publish. I think that goes for pretty much anything although when it comes to twitter all of it goes on very quickly and only in my head and the screen. So here I am writing this, I already did some planning and right now I’m going to take a picture. *kch* there – and while I carry on writing, I’m just sending that up to flickr via Shozu (I’m using the mobile web though rather than forking out to *$s & tmobile.
So the next thing is to finish writing this – oh dear, it’s getting a bit recursive isn’t it? clearly didn’t plan it as well as I thought I had.
So once I’ve done that, I’ll fire up scribe and type up what I’ve got and add links to my previous post and insert the flickr photo.
The text link is siimple-ish I just need the url of the post, though the copying of a url with this keyboard needs a bit of a hack – at worst I can write down the url on my notepad and then type it in later. and then the flickr photo – I think that saving a bookmark and then copying and pasting it in is the way, but I’m also going to look at copying & pasting from the normal non-mobile flickr page. Then save and publish and there you are. no “real” computers involved (at least on the client side!)
Later… much later…
OK So that was an interesting experiment – the stuff above has sat in draft for a week since I wrote it. I can’t be bothered to do what I intended, which was to tidy it up and put some links in. But it got me started. The main thing I learned was to make sure that scribe had the mobile connection set as default – it kept failing because it was trying to connect to my home wifi, which was kind of out of range ‘cos I was in a Starbucks on Oxford St.
The post I did on Oli’s trip yesterday though was entirely written and posted from the field (to be precise, but not precise enough to spoil it for everyone, a public place with a mains connection, next door to a hotel with an open wifi spot) The video was also edited and posted from the phone at the same time.
It takes time. The Oli post took me *three* hours, not including shooting the video but including editing it down and lots of faffing about learning stuff. So what did I learn?
- Using the bluetooth keyboard is interesting – I had to keep switching between keyboard and buttons – would be fun to have some hotkeys set up to “Select Left Menu/Option” and “Select Right Menu/Option” Also need to play around more with selecting text. But I’m getting used to it.
- Using a bluetooth keyboard with an N95 is also interesting to passing geeks, which doesn’t help in getting things done quickly 🙂
- For simplicity I didn’t add any titles or credits to the video. Rupert has some smart way of doing this, I seem to remember, but it’s a long time since I had a tutorial. I got an inordinate amount of self-satisfaction from cutting a chunk of my waffling out of the middle and smoothing the cut with a cross-fade.
- I’m very pleased with the sound quality given that we were in a very noisy lunch reception in a bookstore. I used the external mic set up as described in the 1MSME-L post. I’m quite sure that the internal mic would not have coped so well, but I need to do some comparison testing to show the difference.
- Shozu has a 10MB limit but you can get round that by invoking it from the Video Editor (at least I think that’s how it happened) The video was a 44MB .mp4 file. I just realised I shot it at “TV High Quality” so I could have made life easier for myself.
- Stealing wifi like this means that the connection was occasionally flaky and there wasn’t much I could do about it. Roll on ubiquitous free and reliable wifi in Central London.
- Writing links in html is not as much of a faff as I remembered it to be.
- The ajax interface for blip.tv makes it hard to get the embed code for the video using the Nokia browser. But I made it in the end (about 60% of my entire faffing time was working this out). You need to select (for this blog anyway) Embed and WordPress.com just like you do normally and hit the “go” button but then you need to hit the “Newer” button in the sidebar element above to display the text box with the code in it. Now that I know it it’s not such a problem, but I’m guessing maybe a different browser or a video sharing site with a better mobile interface are both worth investigating.
- Copying URLs for links is indeed tricky. I didn’t work out an easier way of getting the flickr photo embedded than to go to the non-mobile version of flickr and get the code just as you would normally. Saving a URL as a scratch bookmark ready for copying and pasting is a useful technique too.
So progress. I’d love to hear from others who are trying this stuff out. How am I doing? Have you found any time-saving hacks along the way?
I thought I’d write about the stuff I took to my videoblogging masterclass last week. I’d like to repeat the process with other clients – and maybe a public one – it worked well in a small group of communications specialists and people from lines of business. I’d have liked to have done it all more openly too, but one of the requirements from the client was that everything was kept private (it was part of an internal conference on risk management)
I started with my background in social media as a whole and how I’ve been thinking about it helping internal communications and knowledge management for as long as I’ve been blogging.
Then I took a look at the technology. I started with the obvious – get a DV camera, point it at someone and record what they’re saying. I then showed how to simply take that footage, edit it quickly using Windows Movie Maker, add a title and some credits and create a movie file. I think this is simple now and there are tutorials all over the web, but I forgot how complicated it can seem if you’ve never seen it before.
Then I looked at video clips as conversations, using seesmic as an example. We looked at some conversations and saw how being informal helps to convey more information. I talked about how the community had grown up and about my experience of meeting and building relationships with people I’d known about before, but never got to know properly until we “met” on seesmic.
And finally we looked at mobile video – briefly touching on using your phone to record files, edit and transfer to the web like this master, but focusing mainly on live streaming, using qik as an example. I’m very grateful to Jackie at qik for shipping me an N82 so that I could demo this properly (and I seem to have really gotten the bug since then!) I’m not sure that the whole group in the class fully understood what was going on but one or two were gobsmacked and very excited by the potential of this.
We spent the second half of the morning talking about the cultural impact of doing this sort of thing, the risks involved and the kinds of practical applications that they could envisage. And then (oh noes!) we got onto why any use of video would be difficult (read “nigh on impossible”) in their current IT environment. This also led onto an interesting discussion about broadcast versus narrowcast and an understanding that not everything that gets published needs to be accessed by everybody else.
So yeah, give me more of these please.
A slow project this one. Ask as many people as I can remember to do when I’ve got my camera with me to answer a “simple” question – “What is the web for?”
I tried it out at the Tuttle Club a few weeks ago. This is what came out of the mouths of some of the Smartest People in Social Media (TM)
So there are two ways I want to take this forward. I want to do it with a more diverse group of people, and I want to edit a bunch of them together in a watchable way. Your thoughts on how to do this are welcome.
I have more. I will release them. Soon.