Okay, I will try using fade.final() then. Just one more question: With smart_crossfade() what would be the point in time where fade.final() is supposed to kick in when its used in the default transition? Is that when the second track starts e.g. at start_next?
Henry On 16/11/2011 08:35, David Baelde wrote: > Hi Henry, > > I haven't had time to fully read and reflect on your recent mails, but > I can answer this for now. > > On Wed, Nov 16, 2011 at 2:18 AM, Henry Favretto <[email protected]> wrote: >> Curiously, when is the fade-out supposed to start? Does it depend on the >> start_next parameter or >> rather on the duration of the fade-out, e.g. counting backwards from the >> track ending? > > With fade.out() the fade starts when liquidsoap sees that the end of > track is in D seconds, where D is the duration parameter. So it relies > on remaining time estimations. > > With fade.final(), which I often use for transitions, the fade starts > immediately, and kills the source when the fade is over (if the track > hasn't ended before that). > > It is quite possible that remaining time estimations changed a little > bit, but I don't think there should be too much difference. In any > case, using fade.final() sounds like a good idea in your case and > could "fix" your problem. > > Cheers, ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
