Hi Michael & Video Crew, I just saw that you guys were doing video for the sessions and I'm wondering if perhaps there would be any interest in displaying the videos directly on the EuroPython website instead of sending people over to Blip.TV?
I'm speaking at the conference about MediaCore which is a python based video CMS that we've been working on for the last year, and I think it might be perfect (especially considering it is a Python conference) to show the video in a Python web app. We'd be happy to integrate MediaCore with the EuroPython site, and we could add support for blip.tv clips pretty easily. MediaCore currently allows video to be added from any server on the web, so we could even stream the video ourselves. Let me know if you're interested at all in the idea and I'd be happy to give you a call to discuss the details. For information on the project/features etc. visit: http://getmediacore.com Cheers, Stuart ~~~~~~~~~~~~~~~~~~~~~~ Stuart Bowness Director, Simple Station Inc. Portfolio: simplestation.com Twitter: twitter.com/simplestation On 2010-07-11, at 5:15 PM, Michael Sparks wrote: > Hi, > > > Since plan A relied on all cameras having power, and that transpired > to be a bad assumption, plan B...... > > On Monday 5th July, Richard Taylor wrote: >> Have you progressed your plans for the video any further? >> >> It would be good to draft some instructions for the session chairs. > [fx: me utterly swamped ] > > > On Friday 9th July, Richard Taylor wrote: >> Sorry to chase... >> >> Just wondering what the plan is for video. I have had offers of memory >> sticks and people that would be willing to help but I need to know if you >> can coordinate during the conference because I do not have a handle on what >> the plan is. > [fx: me utterly swamped ] > > Sorry not to reply earlier, I've been completely swamped. This is the first > chance I've had to think about it and reply, and I've written a long reply > with detailed reasons, which is probably too long. > > As a result, I'll try and write something smaller and more focussed. > (edit: It ended up long again, but probably clearer) > > If there's questions on specific points I can also post the longer version. > > Summary of help needed > ====================== > 1 - 7 Volunteers needed. (preferably 1 or 2 dedicated ones) > 3 x 8GB ***CLASS 6*** SD Cards required [1] > 1 x tripod required > > [1] If necessary I can buy these myself, but I'm concerned about > delivery before europython. > > Note > ==== > No plan is perfect, this one is aiming to be practical. > > Volunteers needed > ================= > Due to the characteristics of the cameras I am seeking between 1 and 7 > volunteers to record sessions covering the following time periods: > M:AM: MONDAY MORNING > M:PM: MONDAY AFTERNOON > T:AM: TUESDAY MORNING > T:PM: TUESDAY AFTERNOON > W:AM: WEDNESDAY MORNING > W:PM: WEDNESDAY AFTERNOON > Thur: THURSDAY (MORNING) > > Clearly it is better if the volunteer for morning & afternoon is the same. > Also, it should be clear that 1 person could do all of the above. > > To be clear: > * I would prefer 1 or 2 dedicated volunteers who are prepared > to do a day or two each. > * What's required from a volunteer is to simply record the sessions > they attend and to make sure all 3 cameras get back. > > See below as to what a volunteer needs to do. > > Required Equipment > ================== > Either: > * 6 x 4GB SD card, class 2 , 4 or 6 > * 3 x 4GB SD card, class 6 > > Prefer: > * 3 x 8GB SD card, class 6 (removes need for swapping cards, makes life > less hectic) > > I think the most cost effective & practical option here is 3x8GB SD cards. > > I'm prepared to order 3 x 8GB SD cards if necessary. (I find them > useful anyway) I'm concerned about them getting here before I leave > for Europython though. > > (Note: The class matters, it affects how fast we can get the data off) > > 1 x Tripod for the europython cameras > > > Planned amount to be recorded > ============================= > Total amount to be recorded is 26.5 hours (or so) using the camera I'll be > borrowing. Total amount to be record in total using the 3 Europython cameras > is about 19 hours. The limiting factor really is power. (see key forces > below) Swapping batteries may mitigate this, but would definitely make things > harder. > > This will mean upto 45 hours out of the 100+ hours can be recorded. > (Minimum of about 26 hours though, which will still be higher than last > year I think) > > (This is better than last year, which is the point really) > > > Key forces > ========== > * I have 1 camera I can borrow which records at 4GB/hour, 10x optical > zoom, which can be powered by an external PSU. This means that I can > record 1 entire tracks' worth using that. > > Maximum session period is 10GB in length. > > * There are 3 cameras owned by the europython crew which can each record > about 1 hour each, before their batteries give out. They cannot > practically be powered by an external PSU. Same brand as the other so > can assume 4GB/hour, but only 5x optical zoom. Therefore not suitable > for recording the Adrian Boult room. Assumed recharge time of around > 60 minutes. (based on conversations and looking at specs) > > * 4GB/hour has to be assumed in order to capture speaker & slides. If we > could change GOP length we could reduce this. Typically these cameras > do not support that sort of tweaking. > > * Class 6 SD cards appear to have a good balance factor of "speed of > copying stuff off" vs "compatibility with devices" vs cost. You can > copy 4GB off a class 6 SD card in 5 minutes. On cheaper cards (class 1 > or 2, the time can be MUCH closer to an hour - this is a variable) > > Plan for the camera I'll be borrowing from colleague at work > ============================================================ > I'll use this for recording the sessions I attend. I will generally move to > a room at the end of a break and stay there until the next break. (Shifting > rooms last year was a pain point) > > I'll use this to record all keynotes & all lightning talks. > > I've not decided which sessions I'll be attending and recording yet, and > that's something I'll plan with volunteers for videoing stuff. (ie Calls > for specific stuff to be recorded, but without volunteering to help with > recording will be met with tumbleweed :-) (noted perhaps, but won't be the > deciding factor) > > > Suggested Plan for the 3 Europython cameras > =========================================== > Each day: > > Morning: > Give the 3 cameras to one person in the morning. > They record 1 session per camera. They do NOT record the keynote. > > Lunch - take the camera to the organisational area/room (assuming we have > that this year). > Hand in the cameras. > Their memory cards are removed, and swapped for 3 empty cards. > They are plugged in to be charged. > > Afternoon: > The 3 cameras are again given to one person. > They record the 3 sessions after lunch. > > Afternoon break: take the camera to the organisational area/room > Hand in the cameras. > Their memory cards are removed. > They are plugged in to be charged. > > Evening: > Contents of their cards copied off. > > As you'll see below, with 3 x 8GB cards, this would mean that the cards would > not need swapping at lunchtime - just their batteries recharging or swapping. > > > Detailed Schedule for the 3 Europython Cameras > ============================================== > > Monday: > MORNING - VOLUNTEER M:AM NEEDED > Volunteer will attend 3 sessions and record as follows: > 09:45 - 10:30 > * 0.75 hours - 3GB - Camera 1 (then assume battery & card exhausted) > 11:00 - 12:30 > * 0.75 hours - 3GB - Camera 2 (then assume battery & card exhausted) > * 0.75 hours - 3GB - Camera 3 (then assume battery & card exhausted) > > LUNCH > M:AM takes all 3 camera back to the tech area/crew area for recharge, > and card swapping. > > AFTERNOON - VOLUNTEER M:PM NEEDED > Volunteer will attend 3 sessions and record as follows: > 14:00 - 16:30 > * 1 hour - 4GB - Camera 1 (then assume battery & card exhausted) > * 0.75 hours - 3GB - Camera 2 (then assume battery & card exhausted) > * 0.75 hours - 3GB - Camera 3 (then assume battery & card exhausted) > > BREAK > M:PM then takes all 3 camera back to the tech area/crew area for > recharge, and card swapping. > > > Tuesday: > MORNING - VOLUNTEER T:AM NEEDED > Volunteer will attend 3 sessions and record as follows: > 09:45 - 10:30 > * 0.75 hours - 3GB - Camera 1 (then assume battery & card exhausted) > 11:00 - 12:30 > * 0.75 hours - 3GB - Camera 2 (then assume battery & card exhausted) > * 0.75 hours - 3GB - Camera 3 (then assume battery & card exhausted) > > LUNCH > T:AM takes all 3 camera back to the tech area/crew area for recharge, > and card swapping. > > AFTERNOON - VOLUNTEER T:PM NEEDED > 14:00 - 16:30 > Volunteer will attend 3 sessions and record as follows: > * 1 hour - 4GB - Camera 1 (then assume battery & card exhausted) > * 0.75 hours - 3GB - Camera 2 (then assume battery & card exhausted) > * 0.75 hours - 3GB - Camera 3 (then assume battery & card exhausted) > > BREAK > T:PM then takes all 3 camera back to the tech area/crew area for > recharge, and card swapping. > > Wednesday: > MORNING - VOLUNTEER W:AM NEEDED > Volunteer will attend 3 sessions and record as follows: > 09:45 - 10:30 > * 0.75 hours - 3GB - Camera 1 (then assume battery & card exhausted) > 11:00 - 12:30 > * 0.75 hours - 3GB - Camera 2 (then assume battery & card exhausted) > * 0.75 hours - 3GB - Camera 3 (then assume battery & card exhausted) > > LUNCH > T:AM takes all 3 camera back to the tech area/crew area for recharge, > and card swapping. > > AFTERNOON - VOLUNTEER W:PM NEEDED > Volunteer will attend 3 sessions and record as follows: > 14:00 - 16:30 > * 1 hour - 4GB - Camera 1 (then assume battery & card exhausted) > * 0.75 hours - 3GB - Camera 2 (then assume battery & card exhausted) > * 0.75 hours - 3GB - Camera 3 (then assume battery & card exhausted) > > BREAK > T:PM then takes all 3 camera back to the tech area/crew area for > recharge, and card swapping. > > Thursday: > MORNING - VOLUNTEER Thur NEEDED > Volunteer will attend 3 sessions and record as follows: > 09:45 - 10:30 > * 0.75 hours - 3GB - Camera 1 (then assume battery & card exhausted) > 11:00 - 12:30 > * 0.75 hours - 3GB - Camera 2 (then assume battery & card exhausted) > * 0.75 hours - 3GB - Camera 3 (then assume battery & card exhausted) > > LUNCH > Thur takes all 3 camera back to the tech area/crew area for recharge, > and card swapping. > > (remaining talks that day are lightning talks to be recorded by > the other camera which has power) > > Transcode & Upload > ================== > > Like last year, I plan to transcode the talks during the conference > overnight, where possible. (The transcode is to drop below blip.tv's 1GB > file limit, and in particular by changing GOP values, checking that > slides & command lines are still readable) > > However upload of talks will NOT happen during the conference. The reason > for this is to avoid hammering the uplink. Upload of talks will start the > following week, specifically from Monday 26th July onwards. This is because > I'll be able to do that from work, which has plenty of bandwidth available. > > > Finally > ======= > Please do volunteer to help. Last year I'd not recorded a single thing, and > learnt a lot. > > In this case, all you're really volunteering to do is: > * Turn up, borrow 3 cameras. > * Go to your favourite session, put tripod down, point camera at speaker > and screen. > * Hit record. When the session stops, hit stop. > * Do the same for the next 2 sessions, but each time _a new camera_. > * Return the cameras to the tech area at the break. > > It's fun, and a worthwhile contribution. > > Regards, > > > Michael. > _______________________________________________ > Europython-improve mailing list > Europython-improve@python.org > http://mail.python.org/mailman/listinfo/europython-improve
_______________________________________________ Europython-improve mailing list Europython-improve@python.org http://mail.python.org/mailman/listinfo/europython-improve
