I downloaded the clip from Jeyant Joshua Gonringe's blog, a blog of a 4-5 year old kid. By default windows codecs are not supported by SuSE (and hopefully others as well). I like Xine a lot, however, I equally like mplayer as well. Normally, I install both of them as some clips/movies are played well in Xine and some are played well in mplayer. After upgrading my laptop to SuSE 10, I actually forgot to recompile mplayer. So, downloaded their new 1.0pre7-try2 tarball and started compiling.
During configure itself it yelled at me asking for a gcc version that it supports. With their --disable-gcc-checking, I managed to get the configure stage going. However, the compilation borked with an error saying "memory input 4 is not directly addressable". Luckily google got me this patch which smoothened my mplayer compilation. Voila!! that video clip is amazing/relaxing. :-)
Wednesday, October 05, 2005
Beagle moments
Yesterday was talking to my buddies in #dashboard channel after a considerably long time. It feels really good and don't know why doesn't it happen with any other channel :-(. Well, may be because I know what I am doing in beagle and what beagle is doing. Myself and Joe were discussing about my archive filter hack for beagle. Joe came with a number of good points on my quick hack. Got to grab some time today to fix those things. From the channel log...
Oct 04 20:26:15 joe varadhan: ok, so the main issue I see with the patch is that it uses MemoryStream
Oct 04 20:26:40 joe mediterr: does your mono-web package have the same version number as your mono-core package?
Oct 04 20:26:59 joe varadhan: which is probably not avoidable with how the filtering system works right now
Oct 04 20:27:09 varadhan joe, Yes.
Oct 04 20:27:13 joe varadhan: but it's kind of an issue because files that are compressed tend to be compressed for a reason. :)
Oct 04 20:27:58 varadhan joe, Exactly, but just thinking of how "possbily" can we avoid that.
Oct 04 20:28:12 varadhan joe, one possible way is a .beagle/tmp stuff.
Oct 04 20:29:05 varadhan joe, we extract there, index the files and delete it. When the parent archive file is deleted, delete the sibling indexes.
Oct 04 20:29:21 joe varadhan: a temp file may make some sense, but then we're using a lot of disk space, which is another reason why the files are compressed in the first place. :)
Oct 04 20:29:50 joe i mean, it's a suboptimal situation either way
Well, sometimes we have to temporarily break the original intention of a thing to reach our goal.
Oct 04 20:26:15 joe varadhan: ok, so the main issue I see with the patch is that it uses MemoryStream
Oct 04 20:26:40 joe mediterr: does your mono-web package have the same version number as your mono-core package?
Oct 04 20:26:59 joe varadhan: which is probably not avoidable with how the filtering system works right now
Oct 04 20:27:09 varadhan joe, Yes.
Oct 04 20:27:13 joe varadhan: but it's kind of an issue because files that are compressed tend to be compressed for a reason. :)
Oct 04 20:27:58 varadhan joe, Exactly, but just thinking of how "possbily" can we avoid that.
Oct 04 20:28:12 varadhan joe, one possible way is a .beagle/tmp stuff.
Oct 04 20:29:05 varadhan joe, we extract there, index the files and delete it. When the parent archive file is deleted, delete the sibling indexes.
Oct 04 20:29:21 joe varadhan: a temp file may make some sense, but then we're using a lot of disk space, which is another reason why the files are compressed in the first place. :)
Oct 04 20:29:50 joe i mean, it's a suboptimal situation either way
Well, sometimes we have to temporarily break the original intention of a thing to reach our goal.
Tuesday, October 04, 2005
Grinding Evolution
Evolution a prestigious mail client for the users of GNOME desktop with integrated mail, addressbook and calendaring functionality, that supports "Microsoft Exchange" and "Novell Groupwise" servers as well. After my series of wrapper work around evolution-data-server, started preparing for another leap of something useful to the evolution community.
Preparing the test-bed took almost weeks together and finally, yes, started gathering details of holes in evolution code that kept leaking memory. Well, evolution behaves nicely when the sampling size is small. Still haven't gathered much, however, will be completing it in another couple of days. Did I mention anything about the tool that I used to watch and report the leaks? I guess not yet.
Valgrind a memory debuggind and threading profiler tool for linux programs. Well, I started using valgrind around August 2002 and since then, it has improved quite a lot. It pre-loads hooks for allocations/deallocations and other threading functions. Will write more about valgrind later. One negative aspect of valgrind is that its memcheck tool will slow down your application to a max of 25 times of its original speed.
Another tool that came very handy is LDTP. With new newly improved LDTP, I can run two tests a day. It is a must tool for profiling Desktop application, though, the actual intent of the tool is different. Just write ldtp-scripts for any operation and run it in a loop. That way, I don't have to manually interact with the application and be relaxed or do any other critical fix. ;-)
Well, just wanted to break my lazyness to blog interesting things that I have been doing since four weeks now. Will be posting a detailed blog soon.
Preparing the test-bed took almost weeks together and finally, yes, started gathering details of holes in evolution code that kept leaking memory. Well, evolution behaves nicely when the sampling size is small. Still haven't gathered much, however, will be completing it in another couple of days. Did I mention anything about the tool that I used to watch and report the leaks? I guess not yet.
Valgrind a memory debuggind and threading profiler tool for linux programs. Well, I started using valgrind around August 2002 and since then, it has improved quite a lot. It pre-loads hooks for allocations/deallocations and other threading functions. Will write more about valgrind later. One negative aspect of valgrind is that its memcheck tool will slow down your application to a max of 25 times of its original speed.
Another tool that came very handy is LDTP. With new newly improved LDTP, I can run two tests a day. It is a must tool for profiling Desktop application, though, the actual intent of the tool is different. Just write ldtp-scripts for any operation and run it in a loop. That way, I don't have to manually interact with the application and be relaxed or do any other critical fix. ;-)
Well, just wanted to break my lazyness to blog interesting things that I have been doing since four weeks now. Will be posting a detailed blog soon.
I am mp3
Praveen today told me about this site to find out what kind of a personality we are and got my personality as:
Which File Extension are You?
Which File Extension are You?
Subscribe to:
Posts (Atom)