title: What is the advantage of loading AVPlayerItem with an AVURLAsset than a URL
body: <p>As the title states, what advantage by doing one than the other?</p>
  
  <p>With asset:</p>
  
  <pre><code>MPMediaItem *song = [self.itemCollection objectAtIndex:self.currentIndex];
  NSURL *songURL = [song valueForProperty:MPMediaItemPropertyAssetURL];
  AVAsset *asset = [AVURLAsset URLAssetWithURL:songURL options:nil];
  AVPlayerItem *item = [AVPlayerItem playerItemWithAsset:asset];
  [self.myPlayer replaceCurrentItemWithPlayerItem:item];
  </code></pre>
  
  <p>With URL:</p>
  
  <pre><code>MPMediaItem *song = [self.itemCollection objectAtIndex:self.currentIndex];
  NSURL *songURL = [song valueForProperty:MPMediaItemPropertyAssetURL];
  AVPlayerItem *item = [AVPlayerItem playerItemWithURL:songURL];
  [self.myPlayer replaceCurrentItemWithPlayerItem:item];
  </code></pre>
  
  <p><strong>Update</strong></p>
  
  <p>Right, after some playing around I've observed the following:</p>
  
  <p>When using the former method (asset), there is one problem with remote control events:
  1. Lock the screen and wait for next song to be played.
  2. When next song has started, double click the home button to bring up the controls.
  3. Tap pause: nothing happens.
  4. Tap pause again: music is paused.</p>
  
  <p>Now there isn't actually a problem with remote control events, because it is being called on the first attempt. It's pausing the music (i.e. <code>[self.myPlayer pause]</code>) that isn't working - until you try it again.</p>
  
  <p>Haven't a clue why this is, but it's a reason for me to go with the URL-method.</p>