Sparrow Forum

1. 

   Stylish
   Member

   Hello,

   When I use a SPSoundChannel (a music file, aifc), I need to retain the object because if I don't, the object gets autoreleased (I read it in the forum).

   The problem is, when I do the explicit release, I get a EXC_BAD_ACCESS error, but the retainCount is 1 and the object is not nil.

   If I don't release the object have I a memory leak? I think so but I'm not an expert in Sparrow Framework nor Objective-C.

   Best regards,

   Posted 11 months ago #
2. 

   Mik
   Member

   Hum, i'm the master of noobs so i never retained nothing

   In my experience you don't need to retain it and everything will work just fine but i hope some expert will clarify this better for both of us.

   Posted 11 months ago #
3. 

   Shilo
   Master Sparrow

   Hello,

   This read might help: http://wiki.sparrow-framework.org/manual/audio_playback.

   You only need to retain the sound channel if you want to access it outside of the scope of the method/run loop.

   For instance, this is the proper way to use the sound channel when you only need to access it in the same method:

   SPSound *sound = [SPSound soundWithContentsOfFile:@"sound.caf"];
   SPSoundChannel *channel = [sound createChannel];
    
   [channel play];

   If you want to access the sound channel outside of the method, you need to retain it and release it when you are done with it, like this:

   - (void)loadSound {
       SPSound *sound = [SPSound soundWithContentsOfFile:@"sound.caf"];
       mSoundChannel = [[sound createChannel] retain];
   }
    
   - (void)playSound {
       [mSoundChannel play];
   }
    
   - (void)dealloc {
       [mSoundChannel release];
       [super dealloc];
   }

   mSoundChannel would be an instance variable declared in the interface.

   I assume you are getting EXC_BAD_ACCESS because you are releasing the wrong object. Just a warning, never NSLog an object that has a retainCount of 0 or you will get a crash.

   Posted 11 months ago #

RSS feed for this topic

Reply

You must log in to post.