I changed compatibility to 0.82 only. I have experienced the problem you described. When I experienced that problem I thought it was caused by an unsupported webcam and microphone. I found that Record and Measure activities did not work for me either because of this. I am curious whether they work for you, but I'm guessing you know a lot more about gstreamer and gstreamer comparability than I do. <div class="gmail_quote">On Tue, Jan 19, 2010 at 9:17 PM, Aleksey Lim <<a href="mailto:alsroot@member.fsf.org" target="_blank">alsroot@member.fsf.org</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div>On Tue, Jan 19, 2010 at 06:42:09PM -0500, Peter Hufford wrote: > I'm sorry about the problem, thanks for the feedback. > > A little more information would be helpful. By "endless" do you mean a few > dozen or hundreds. </div>at least it worked for 5min and generated 1M of logs(head of this log is attached, the rest of log is the same) <div> > Also, were you running TimeLapse on the XO or some other > computer running sugar? </div>non-XO box w/ sugar 0.86 installed <div> > Did you have an external webcam or microphone > plugged in? </div>yup, I can capture sound and video via mencoder -- I launched activity on newly reflashed XO-1 and it works fine, so you can restrict compatibility range only for 0.82 and add 0.82+ support later </blockquote><div> Saying it works fine is a bit of a stretch. I started programming TimeLapse a month ago for my python programming class with Jeff Elkner. The class ended before I finished TimeLapse and now I have no time to work on TimeLapse. It is many bugs and some incomplete parts right now. I hope someone will pick up on TimeLapse where I left off. If that doesn't happen I'm considering making TimeLapse inactive until summer when I have time to finish it. I did not realize timelapse development would come to a halt when my class ended. It should definitely remain experimental for now and perhaps it should I should make it inactive until June when school gets out. </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div> > > Thanks, > Peter Hufford > > On Tue, Jan 19, 2010 at 5:12 PM, Sugar Labs Activities < > <a href="mailto:activities@sugarlabs.org" target="_blank">activities@sugarlabs.org</a>> wrote: > > > A Sugar Labs Activities Editor requested further information from you > > regarding version 2 of your activity TimeLapse. > > > > Aleksey Lim wrote: > > > > "Hi, sorry for long reply > > > > I started TimeLapse-2 in my 0,86 environment, chose "Single Collection" and > > clicked "Collect" and got endless(I didn't count how much) write-to-log > > session with strings like: > > > > 1263938576.381824 WARNING root: DSObject was deleted without cleaning up > > first. Call DSObject.destroy() before disposing it. > > > > is your activity was tested on 0.86(since 0.86 is in compatibility list)? > > if yes, such strings are warnings an will be loged in anyway which will make > > using your activity not comfortable(there is a "feature" which sync disk > > buffers)." > > > > > > Please reply to this e-mail or join #sugar on <a href="http://chat.freenode.net" target="_blank">chat.freenode.net</a>. > > > > Sugar Labs Activities > > <a href="http://activities.sugarlabs.org" target="_blank">http://activities.sugarlabs.org</a> > > > > </div>> _______________________________________________ > ASLO mailing list > <a href="mailto:ASLO@lists.sugarlabs.org" target="_blank">ASLO@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/aslo" target="_blank">http://lists.sugarlabs.org/listinfo/aslo</a> -- Aleksey </blockquote></div> Thanks again for your feedback and for taking the time to try out TimeLapse, Peter Hufford