Difference between revisions of "Talk:SoC 2007"

From VideoLAN Wiki
Jump to navigation Jump to search
(→‎General talk: Keep the page CLEAN)
Line 2: Line 2:
  
 
== General talk ==
 
== General talk ==
 +
 +
=== Cache and GUI interface ===
 
This project may need to redesign a bit the cache handling module access. (How is this "Interface" related ? I agree that we might need to change the caching algorithms for web-content, but it's definitively not interface (nor web plugin) related. [[User:Dionoea|Dionoea]] 16:17, 8 March 2007 (CET))
 
This project may need to redesign a bit the cache handling module access. (How is this "Interface" related ? I agree that we might need to change the caching algorithms for web-content, but it's definitively not interface (nor web plugin) related. [[User:Dionoea|Dionoea]] 16:17, 8 March 2007 (CET))
% Because VLC caches in seconds and Youtube are just caching the most they can to have the whole file local.
+
: Because VLC caches in seconds and Youtube are just caching the most they can to have the whole file local.
 +
 
 +
=== MKV muxer ===
 +
From the VLC point of view i don't agree. It would be easier to integrate the muxer directly into VLC than put it in libavformat and then change the libavformat <-> VLC interface to use it. I'm not sure how the chapter / menu / subs system works in MKV but it sure will add complexitiy to or libavformat interface (and some lagg time between the time the mkv muxer makes it into ffmpeg and the time we make it work in VLC). -- [[User:Dionoea|Dionoea]] 16:25, 8 March 2007 (CET)

Revision as of 17:27, 8 March 2007

Questions

General talk

Cache and GUI interface

This project may need to redesign a bit the cache handling module access. (How is this "Interface" related ? I agree that we might need to change the caching algorithms for web-content, but it's definitively not interface (nor web plugin) related. Dionoea 16:17, 8 March 2007 (CET))

Because VLC caches in seconds and Youtube are just caching the most they can to have the whole file local.

MKV muxer

From the VLC point of view i don't agree. It would be easier to integrate the muxer directly into VLC than put it in libavformat and then change the libavformat <-> VLC interface to use it. I'm not sure how the chapter / menu / subs system works in MKV but it sure will add complexitiy to or libavformat interface (and some lagg time between the time the mkv muxer makes it into ffmpeg and the time we make it work in VLC). -- Dionoea 16:25, 8 March 2007 (CET)