tbeckman wrote:
> Can you tell me when the script actually moves songs... is it when it is chosen, when a song ends or other?
"If a track starts playing, the module checks if the next track is required to be a fast track."
> Also, I noticed your wording says a "minimum" of 4 consecutive songs... does that mean it will play more than 4 songs sometimes?
Yes, if you queue them that way. Think of the module as a 'guardian', as long as you don't violate the two rules it sleeps. Anytime a new track starts playing, it verifies if the next track conflicts with its rules, if so it looks ahead to see if there are any more fast tracks it can insert before the next track.
> Tell me if I have this right... but it looks like it waits for one slow song to play and then makes sure a second one doesn't play till 4 have passed through? Thanks... this is great.
Setting maximum slow tracks to '1' would make sure the second slow song would not play directly after the first. But depending on the original queue there could be 4 or more fast tracks before it finally got played.
You can easily experiment with the module by creating a queue with some fast & slow tracks, start playing, and the press the 'forward' button a few times with a few seconds in between while watching the queue (if using the default skin you can 'open' the queue window so it shows more tracks).
SilverEagle
Statistics: Posted by SilverEagle — 12. Mar 10, 09:28
]]>
=chris
Statistics: Posted by Guest — 5. Mar 10, 16:06
]]>
What's wrong with me lately? Seems every time I upload the wrong versions...
Changed to 1.01, nasty error should be gone.
SilverEagle
Statistics: Posted by SilverEagle — 5. Mar 10, 15:20
]]>
In answer to a a module which controls the number of slow songs played back-to-back.
Configure the module using rightclick->tools->NotSoSlow configuration
If a track starts playing, the module checks if the next track is required to be a fast track. If required but it is a slow track, it scans the queue for an upcoming fast track and relocates that before the next playing track in the queue.
A tip: Tracks with an empty BPM or set to zero are treated as fast tracks. If your tracks do not contain BPM information the easiest is probably to select your slow tracks in Silverjuke by hand, and set all their BPM's at once to '1' using Silverjukes tag editor (ctrl-I). This is clearly a bogus BPM, but it will then be treated by this module as a 'slow' track.
Note: if there are too many slow songs in the queue, they will all be played at the end. Which indirectly means this module does not work as you might hope with autoplay filling up the queue, as in that case there will be no fast tracks available to relocate. In its current shape this script is meant to be used in a party-environment, to assist in keeping up the beat...
Update 1.01
- fixed nasty errormessage when queueing a track
Enjoy,
SilverEagle
Statistics: Posted by SilverEagle — 5. Mar 10, 10:39
]]>