Representation of concatenated playlists #34
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Concatenated playlist should be shown as one row in the sync tab instead of showing the individual videos. In this way, only one sync action can be selected for the entire playlist.
Also, metadata suggestions have to be generated from the playlist metadata instead of the video metadata.
The Collection URL should have its tracks as normal, but all tracks point to the same file.
Concatenation works on entire playlist-type URLs or arbitrary Tracks from a collection.
Data structures
concat_groups. These have a name which is unique in their parent Collection. They have almost the same attributes as Tracks, and have an entry in the metadata table (the key can be something likeconcat_group:[name]).concat_group. If it is empty, the Track doesn't belong to a concat group, otherwise it contains the name of the concat group. It also has an attributeconcat_group_positionto set its position in the concat group.concatset toTrue, a concat group with the name[url]:[occurrence_index]will be created and all Tracks will be added to it (in the same order they appear in the playlist)