Hi Solvik (hope to see you on tuesday for the savonet beer btw),

Your problem is that the equeue only allows you to manipulate its
secondary queue, not its primary one. (If you need more info on these,
I hope that you can find them on our site, try googling.)

Currently, there is only a partial solution to this problem: tweak the
queue parameters (length, default_duration iirc) so that only one file
gets prepared in advance. You'll still have some lag but more 3-5mn
than 25mn.

The other "solution" is to manage the queue on your side, and feed
files only at the last moment to your request.queue() (the equeue
becomes pointless)...

It is planned to re-design (and merge) these queue operators. I
started a wiki page (http://savonet.rastageeks.org/wiki/Future) but
did not start to fill in the corresponding sub-node
(http://savonet.rastageeks.org/wiki/FutureQueued). Anybody is welcome
to help us keep in mind the features needed, and participate in the
discussion on how to change this.

Currently, the primary queue's role is to be able to promise an
available track. I'm still not sure if we need / want that this
#is_ready flag is seen as a promise. Even if it remains a promise,
there are solutions: if the promise was given, allow a track to be
removed from the queue only if it is to be replaced immediately by
another one. This would be a fun thing to code. But we might also
decide that this promise is too constraining, and realize that some
other sources cannot keep it (other than planning to produce an empty
track in case they want to retract).

Cheers,
-- 
David

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to