Thank you for the additions to the Region Playlist in build 2.3.0.8 however I did find some unexpected behavior.
When you set up multiple regions and have them all set to infinite loop.., start playback and then use one of the native actions "Regions: Go to region #n after current region finishes palying" ..., the region it goes to will only play through once even though it is set to infinite loop.
Since these are native actions I don't know if you guys can fix this, if not maybe you can create a set of similar S&M actions that will obey the infinite loop settings. If you do decide to create some similar S&M actions it would be nice to have a setting in the S&M.ini under [NbOfActions] that determines how many actions are listed.
Thanks for the detailed report (as usual!).
Well, I see the "prob" but this is not a bug.. I can't tell those native actions to obey something.
That being said, I'm planning some sort of "playlist re-sync" when the user seeks by hand or via the native actions you are talking about or etc..
=> I turn the issue into fr, "Region Playlist Infinite Loop: unexpected behavior" -> "FR: playlist re-sync"
From pyt...@yahoo.com on November 03, 2012 09:14:39
Hi Jeffos,
Thank you for the additions to the Region Playlist in build 2.3.0.8 however I did find some unexpected behavior.
When you set up multiple regions and have them all set to infinite loop.., start playback and then use one of the native actions "Regions: Go to region #n after current region finishes palying" ..., the region it goes to will only play through once even though it is set to infinite loop.
Since these are native actions I don't know if you guys can fix this, if not maybe you can create a set of similar S&M actions that will obey the infinite loop settings. If you do decide to create some similar S&M actions it would be nice to have a setting in the S&M.ini under [NbOfActions] that determines how many actions are listed.
Thank you,
Anton
Original issue: http://code.google.com/p/sws-extension/issues/detail?id=532
The text was updated successfully, but these errors were encountered: