Abstract: In some implementations, a computing system can reduce startup delays for presenting remote media items. For example, when a user requests media content from a media service, the computing system can include information about the first media item to be played in the initial startup messages to reduce the number of roundtrips needed between client and server devices to present the first media item. A media item can include an introductory asset. The introductory asset can be a portion of the full media item that can be decrypted with a local key or not encrypted at all so that a media client can receive and start presenting the introductory media asset quickly while the full media item is being processed by the media client. In some implementations, the system can remove leading silence from the media item so that the amount of delay perceived by the user is reduced.

Abstract: The present technology pertains to automatically contextlabeling media items with relevant contexts, and further for algorithmically generating high quality playlists built around a context that are personalized to a profile of an account. This is accomplished by combining data from observed playlists, and data representing intrinsic properties of media items to predict contexts for media items.

Abstract: Some implementations allow users to create and share data including playlists. Such playlists may be subscribed to by other users. Changes to such playlists, such as updates by the curator of the playlist, must be propagated to subscribers in a timely manner while efficiently utilizing resources. Some implementations allow updates to be propagated using a push notification to cause client devices to request the update (push). Alternatively, updates may be made when the client devices of the subscribers next accesses the system (pull). An aggregator system may be used to make decisions on which users to send push notifications, and which users to wait to pull updates on their own. Additionally, the aggregator may determine that certain playlist updates should be distributed using push notifications. The aggregator may determine that only certain playlist subscribers should receive push notifications regarding playlist updates.

Abstract: The content items presented to a user account as part of a media station can be recorded in a content history index, which can be requested and presented to the user account. The content history can enable a user to revisit the content items included in the content history and/or provide feedback regarding the content items. The version of the content item returned to the user can be based on the client device used to request the content item. For example, a user that was presented a content item on their mobile device, can later request to revisit the content item on their PC and receive a version of the content item best suited for presentation by the PC, rather than the version presented on the mobile device.

Abstract: Generating a customized playlist may include identifying a user account for which a playlist is to be generated, where the user account is associated with a user listening history, a taste profile, and a social profile, identifying one or more friend accounts linked to the user account based on the social profile, obtaining an indication of a plurality of songs associated with one or more of the friend accounts, determining a listening history for the one or more plurality of songs based on the friend accounts, obtaining a subset of the plurality of songs based on the listening history of the plurality of songs, and generating a playlist from the subset of the plurality of songs.

Abstract: Systems, methods, and non-transitory computer-readable storage media for generating an internet radio media station based on metadata available on the user's media library. The media station can be generated in response to a subscription request to an internet radio service. In one example, the media station is generated without a user seed. Metadata related to the user's media library is analyzed and format rules are selected and configured according to the analysis. The format rules are associated with slots in a media station that define the playback sequence of the media station.

Abstract: The present disclosure relates to synchronized sharing of playlists from a source client device to a listening client device. To facilitate synchronized sharing, a current playlist of one or more tracks of digital content is obtained from the source client device. A current playback location within the currently playing playlist is also obtained from the source client device. A shared queue accessible by the listener client device is generated. Further, a shared queue context for the listener client device is identified based in part upon the current playback location. This enables the listener client device to start playback synchronized with the source client device.

Abstract: Some implementations allow users to create and share data including playlists. Such playlists may be subscribed to by other users. Changes to such playlists, such as updates by the curator of the playlist, must be propagated to subscribers in a timely manner while efficiently utilizing resources. Some implementations allow updates to be propagated using a push notification to cause client devices to request the update (push). Alternatively, updates may be made when the client devices of the subscribers next accesses the system (pull). An aggregator system may be used to make decisions on which users to send push notifications, and which users to wait to pull updates on their own. Additionally, the aggregator may determine that certain playlist updates should be distributed using push notifications. The aggregator may determine that only certain playlist subscribers should receive push notifications regarding playlist updates.

Abstract: Users can share a content stream and can create and/or edit playlists that include content items of the content stream. Each user device, or a subset of the user devices, can edit the playback commands of the content stream once it is being shared. Playback of the content items is synchronized between the sharing devices. If one device is associated with a content restriction, an alternate version may be provided to that device. The two versions can still be played synchronously with one another.

Abstract: In some implementations, a computing device can be configured to manage playlist-only media items for a user's media library. For example, when a user adds a media item to a playlist, the user can be presented with an option to add the media item to the playlist as a playlist-only media item. When the user selects to add the media item to the playlist as a playlist-only media item, the computing device can update media metadata associated with the user's media library with data indicating that the media item is a playlist-only media item. When the computing device performs operations (e.g., displaying, searching, etc.) on the user's media library, the computing device can exclude the playlist-only media items from the operations. The computing device can change the playlist-only settings for a media item to add and/or remove a media item from the user's media library.

Abstract: Some implementations allow users to create and share data including playlists. Such playlists may be subscribed to by other users. Changes to such playlists, such as updates by the curator of the playlist, must be propagated to subscribers in a timely manner while efficiently utilizing resources. Some implementations allow updates to be propagated using a push notification to cause client devices to request the update (push). Alternatively, updates may be made when the client devices of the subscribers next accesses the system (pull). An aggregator system may be used to make decisions on which users to send push notifications, and which users to wait to pull updates on their own. Additionally, the aggregator may determine that certain playlist updates should be distributed using push notifications. The aggregator may determine that only certain playlist subscribers should receive push notifications regarding playlist updates.

Abstract: The present technology pertains to steering a playlisting service toward media items that are likely to receive positive feedback from a user operating a client device. The present technology permits a request to play media items without requiring an input context. A playlist service can begin to receive feedback on the playback of the media items and the received playback can be utilized by a steering service in response to a steering request to identify media items for playback that are likely to receive positive feedback based on the feedback received on a sequence of previously played media items.

Abstract: The present technology pertains to automatically contextlabeling media items with relevant contexts, and further for algorithmically generating high quality playlists built around a context that are personalized to a profile of an account. This is accomplished by combining data from observed playlists, and data representing intrinsic properties of media items to predict contexts for media items.

Abstract: In some implementations, a computing system can reduce startup delays for presenting remote media items. For example, when a user requests media content from a media service, the computing system can include information about the first media item to be played in the initial startup messages to reduce the number of roundtrips needed between client and server devices to present the first media item. A media item can include an introductory asset. The introductory asset can be a portion of the full media item that can be decrypted with a local key or not encrypted at all so that a media client can receive and start presenting the introductory media asset quickly while the full media item is being processed by the media client. In some implementations, the system can remove leading silence from the media item so that the amount of delay perceived by the user is reduced.

Abstract: The present technology pertains to automatically providing refreshed versions of personalized playlists of media items based on a refresh schedule. The automatically refreshed personalized playlists can be automatically downloaded to a client device associated with the user account. In some embodiments an animation can be presented to show that a playlist was automatically refreshed. The automatically refreshed personalized playlist can be created based on an assumption that playlists are a collection of media items that go well together in a collection.

Abstract: In some implementations, a computing device can be configured to manage playlist-only media items for a user's media library. For example, when a user adds a media item to a playlist, the user can be presented with an option to add the media item to the playlist as a playlist-only media item. When the user selects to add the media item to the playlist as a playlist-only media item, the computing device can update media metadata associated with the user's media library with data indicating that the media item is a playlist-only media item. When the computing device performs operations (e.g., displaying, searching, etc.) on the user's media library, the computing device can exclude the playlist-only media items from the operations. The computing device can change the playlist-only settings for a media item to add and/or remove a media item from the user's media library.

Abstract: The content items presented to a user account as part of a media station can be recorded in a content history index, which can be requested and presented to the user account. The content history can enable a user to revisit the content items included in the content history and/or provide feedback regarding the content items. The version of the content item returned to the user can be based on the client device used to request the content item. For example, a user that was presented a content item on their mobile device, can later request to revisit the content item on their PC and receive a version of the content item best suited for presentation by the PC, rather than the version presented on the mobile device.

Abstract: Users can share a content stream and can create and/or edit playlists that include content items of the content stream. Each user device, or a subset of the user devices, can edit the playback commands of the content stream once it is being shared. Playback of the content items is synchronized between the sharing devices. If one device is associated with a content restriction, an alternate version may be provided to that device. The two versions can still be played synchronously with one another.

Abstract: Some implementations allow users to create and share data including playlists. Such playlists may be subscribed to by other users. Changes to such playlists, such as updates by the curator of the playlist, must be propagated to subscribers in a timely manner while efficiently utilizing resources. Some implementations allow updates to be propagated using a push notification to cause client devices to request the update (push). Alternatively, updates may be made when the client devices of the subscribers next accesses the system (pull). An aggregator system may be used to make decisions on which users to send push notifications, and which users to wait to pull updates on their own. Additionally, the aggregator may determine that certain playlist updates should be distributed using push notifications. The aggregator may determine that only certain playlist subscribers should receive push notifications regarding playlist updates.

Abstract: The content items presented to a user account as part of a media station can be recorded in a content history index, which can be requested and presented to the user account. The content history can enable a user to revisit the content items included in the content history and/or provide feedback regarding the content items. The version of the content item returned to the user can be based on the client device used to request the content item. For example, a user that was presented a content item on their mobile device, can later request to revisit the content item on their PC and receive a version of the content item best suited for presentation by the PC, rather than the version presented on the mobile device.