Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>AVAudioPlayer should not be added to a persistant store in core-data since it does not conform to the NSCoding protocol.</p> <p>What I would do is remove the AVAudioPlayer from your model but keep it in your NSManagedObject. Then in the implementation switch @dynamic to @synthesized for the audioPlayer. (Add a line too to release the audio player on dealloc).</p> <p>Then do something like this</p> <pre><code>-(AVAudioPlayer*)audioPlayer { if (self.audioPlayer) return audioPlayer; else { NSError * error = nil; AVAudioPlayer * lAudioPlayer = [[AVAudioPlayer alloc] initWithContentsOfURL:self.fileURL error:&amp;error]; if (!error) { self.audioPlayer = lAudioPlayer; [lAudioPlayer release]; } else { [lAudioPlayer release]; NSLog(@"%@",error); } } } </code></pre> <p>I would also recommend to something similar with isLooping and duration and have them come off the audioPlayer directly and not store them in your persistant store unless you need them to persist.</p> <p>EDIT</p> <p>Sounds like your problem is that you are referencing the avaudioplayer in your object (for persistance sake) then saving the context then later when you come back you are rerequesting the object from the persistant store, this will not work since your persistant store can not handle avaudioplayer. There are multiple ways to solve this problem.</p> <p>The first is to store all your avaudioplayers in a nsmutabledictionary (i would make it static or in a singleton). This nsmutabledictionary would be keyed by a unique identifier. You can either create a unique identifier and store it in your persistent store (with a new attribute on your object) or just use the objectid of the sound object (I believe). At that point do what I said before about making the audioPlayer in your managed object class but instead of creating it there just get it back from the nsmutabledictionary with the unique identifier that was made, if there is none that means you need to make a new audio player and add it to the nsmutabledictionary.</p> <p>I hope I am understanding your problem, I think this is the easiest solution and also the most elegant. The other one that is also really easy is that you keep in memory all the sound managed objects that are playing, like that you won't need to rerequest them from the persistant store and therefor your audioplayer will still be accessible.</p> <p>There are really a thousand ways to do this, I am just giving you the 2 I would use, and don't forget to release your audioplayers and remove them from the mutable dictionary when you are done with them.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to store a reference of an audioPlayer instance in core data?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USthewormsterror
    1. USthewormsterror
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to store a reference of an audioPlayer instance in core data?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COisLooping and duration comes from an remote json file and i need that before i start the audioPlayer. hm, what i don't understand is why should i keep the AVAudioPlayer in my manged object if there is no attribute in the entity?
      singulars
      1. PO
      1. USrockstarberlin
    2. COoh ok for isLooping and duration.
      singulars
      1. PO
      1. USthewormsterror
    3. COThe reason for keeping AVAudioPlayer in the managed object is just for convenience, you wanted to do self.sound.audioPlayer.playing, this would allow it without pushing it to the persistant store (which it is not allowed) since it does not conform to NSCoding.
      singulars
      1. PO
      1. USthewormsterror
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload