Same as Romain: right now, I don't see what could have changed -- at least, what could have gotten worse...
But it is true that the mksafe between your source and the crossfade is a bad idea. If the source becomes temporarily unavailable it would add some blank, and crossfade would add transitions from/to the blank. Instead, if the mksafe is above the crossfade, it will be, from the crossfade point of view, as if there was no latency in radio -- in fact, the crossfade will just become unavailable (think of "taking a nap") when the radio becomes unavailable. Actually it's likely that the new "duppy" scheduler in 0.3.7 doesn't behave exactly as 0.3.6, thus creating different latencies. (It's certainly different, but hopefully not "bad".) In case it's unclear, here is how to modify your script: * change radio = mksafe(djlist_noshuffle) into radio = djlist_noshuffle * add radio = mksafe(radio) after the crossfade line Does that help? Keep us informed, -- David ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
