Hoi -devel,
I'm writing an application that streams video from live sources into matroska
files. The files are closed when they are 2GB. I noticed that this closing
can take 4-5 seconds on a high performance server. This is because
matroskamux, while writing its index, is writing 3-8 bytes and then seeking
back and forth for every frame in the stream. There is actually a cache
implemented in embl-write.c, but it has been disabled since 2003 because it
doesn't work.
So, my question is, before I start fixing this cache, does anybody know
what's wrong with it?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind
http://www.mind.beG.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile:
http://www.linkedin.com/in/arnoutvandecappelleGPG fingerprint: D206 D44B 5155 DF98 550D 3F2A 2213 88AA A1C7 C933
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Locked
