at first buckets are just for keeping your house clean. think of them as “folders”, “bags”, “cans” or whatever. at second they are usable as “subchannels” since you can request them separately as described here. last but not least they are to assign logical parameters like “shuffle”, “offline” etp. pp. to videos they contain. that´s it. and they are good to fill white spaces in the playlist manager itself :).

easiest parameter ever: setting a bucket “offline” will suppress all contained videos from being played back on channel-root requests. also “offline” buckets can not requested stand alone as described here.

this is a kind of “semi-offline”. buckets set to “cut” will be suppressed on root-playback but can still be requested stand alone as described here.

to randomize videos, you have to load them into a bucket which is set to “shuffle”. click here to see a video tutorial. you can not shuffle root videos. videos are relatively shuffled to their absolute position in the playlist root. E.g: Assumed your have tinkered the following playlist:

• video (A) - root
• video (B) - root
• video (C) - bucket “testing”
• video (D) - bucket “testing”
• video (E) - root
• video (F) - bucket “testing”

Also assumed that bucket “testing” is set to “shuffled” - possible output results may be the following:

• (A) - (B) - (F) - (D) - (E) - (C)
• (A) - (B) - (C) - (F) - (E) - (D)
• (A) - (B) - (D) - (C) - (E) - (F)

Please not that the “root” items are static. So will all other videos in relation to bucket “testing”.

buckets marked as trailer repository do provide videos for dynamic video injections. videos contained in this buckets are not played back in their relative order to root. their playback depends on your channel configurations made on channel level.

Assumed you made the following config settings:

• minimum amount of regular videos between each trailer (0=random)? : 3
• how many regular videos to play before first injection (0=start playlist with a trailer)? : 2
• loop all available trailers till end of playlist? : yes

Assumed you gathered the following playlist:

• video (A) - root
• video (B) - root
• video (C) - bucket “my trailers”
• video (D) - bucket “my trailers”
• video (E) - root
• video (F) - root
• video (G) - root
• video (H) - root
• video (I) - root
• video (J) - bucket “my trailers”
• video (K) - root
• video (L) - root
• video (M) - root
• video (N) - root
• video (O) - root

You will get the following result:

• (A) - (B) - (C) - (E) - (F) - (G) - (D) - (H) - (I) - (K) - (J) - (L) - (M) - (N) - (C) - (O)

1. (C) because ” how many regular videos to play before first injection” is “2”
2. (D) (J) (C) “because minimum amount of regular videos between each trailer” is “3”
3. last (C) because “loop all available trailers till end of playlist” is “yes”
   1. setting this to “no” the result would be: (A) - (B) - (C) - (E) - (F) - (G) - (D) - (H) - (I) - (K) - (J) - (L) - (M) - (N) - (O)