Hi guys, I had explicitly disabled metadata overriding for fade.final(), and I'm afraid that enabling it won't really solve any problem. I wouldn't be surprised that using metadata overriding with fade.final will result in strange behaviors. In any case, it seems useless and may be confusing for users, since it does not fit nicely with the "normal" use of the operator.
The use of fade.final is rather different from fade.out. With fade.out, each track is faded, so it makes sense to change the duration dynamically, to have separate values for different tracks. However, the purpose of fade.final is to fade a stream without paying attention to any track information, and make it end (become unavailable) when fading out is finished. In other words it's just a smooth way to kill a stream. The fade.final operator is always used (as far as I've seen) in a dynamic way, for example a transition wraps a source in fade.final. There is already an opportunity to set the duration dynamically here, I wonder why you'd want to also do it based on metadata. What do you think? Azerty88, could you say a little more on what you're trying to do? Cheers, -- David ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
