Sound continuing from one scene to another

cocos2d for iPhone » Programming » CocosDenshion (sound engine)

Sound continuing from one scene to another

(10 posts) (4 voices)

Started 1 year ago by kingsapo
Latest reply from kingsapo

Tags:

kingsapo
Member

Hey all! So I have this app where in one scene (the initial scene), I have it setup so that whenever you touch on the screen, a small sound clip of gunfire is played. I also have it so these gray enemy placeholder images are coming towards you, and as you either shoot them or they get close to you, they disappear and a counter increments. Once that counter exceeds 10, the scene switches, using the method code:

[[CCDirector sharedDirector]replaceScene:[ScoreScreenScene node]];

This switches the scene to what I want to someday be a score screen for the level the player just played.

Now that the introduction is done, my main problem is that when I switch scenes to the new ScoreScreenScene, the gunfire clip code sort of carries over. For example, just like in my initial scene, whenever I tap anywhere on my ScoreScreenScene, the same gunfire clip is played, despite the fact that there is no relevant code for that anywhere in the scene class. I have even tried not importing the initial scene class, and that did not work.

I didn't attach much code or my project because there is quite a bit of code that is unrelated to my problem, however if anyone would like me to post it because they think it would help, let me know and I'll get on it. I'm sure whatever this is is something stupid that I'm forgetting to do before switching scenes, or maybe it's a bug or something. Anyway, any help is appreciated. Thanks!

Posted 1 year ago #
jd
Member

Here are two ways you can do it:
1. Mute the channel, then unmute on next scene
2. When you play a sound it returns and unsigned integer. You can specifically stop the sound identified by that integer onExit.

Posted 1 year ago #
Steve Oldmeadow
Administrator

For example, just like in my initial scene, whenever I tap anywhere on my ScoreScreenScene, the same gunfire clip is played...

If that is true then it sounds like something isn't being deallocated when the scene is replaced. Check whatever is handling the touches to make sure it is being deallocated. A common mistake people make is adding an object as a delegate which causes it to be retained and then not removing the object as a delegate when appropriate.

Note there is nothing in CocosDenshion that can cause this behaviour, you must be triggering your sound playing code somehow.

Posted 1 year ago #
kingsapo
Member

jd, thanks for the response, but I don't think it'll really help. I'm not sure how, but it appears my game logic is still taking place in the new scene. For example, I have an ammo system and a little gun picture that you tap to reload. Although the gun isn't present in the new scene, I still get the reload sound by tapping where it would be.

Steve, thanks as well. I have tried your advice, and even manually put a [self dealloc] right before switching scenes, but that doesn't work. Actually, when I do that, it crashes on [super dealloc], which is kinda odd. I keep feeling like there is a different method that I'm supposed to be using than the replaceScene method, but there isn't anything else.

Also, sorry if I put this in the wrong section. This is my first forum post, and seeing as this is an audio-related problem, I thought it would be better suited in the audio engine section of the forum, rather than the graphics engine section. If there would be a better place to put a topic such as this, please let me know. Thanks!

Posted 1 year ago #
jd
Member
Well, in your original post you did mention a Scene being dealloc'd - which should happen. However, it will not dealloc when it is retaining something. Some things you may be retaining are anything scheduled as well as references to other objects that have not been released. You won't even reach dealloc in some cases. But there is also onExit() which is called when a scene is being replaced. I have used that in the past to print out the reference count and try to clean things up. This is something you can try if you are desperate enough:
```
- (void) onExit
{
CCLOG(@"retainCount: %i",[self retainCount]);
[self removeAllChildrenWithCleanup:YES];
[self unscheduleAllSelectors];
[self stopAllActions];
CCLOG(@"retainCount: %i",[self retainCount]);
}
```
If you still have a retain count > 1, then you are usually manually retaining something you need to manually release.
Posted 1 year ago #
kingsapo
Member

jd, THANK YOU! This is a really cool method, and I'm definitely gonna use this in the future for other stuff. It also helped me figure out the problem. In my new scene, the ScoreScreenScene, I imported the original HelloWorldLayer scene, so that when I tapped the button on the ScoreScreenScene, I would be able to re-load the HelloWorldLayer, and return to the game. What I didn't realize what that while importing the HelloWorldLayer, I also imported the methods contained within it; including the touches methods. That is why before, whenever I tapped anywhere, it looked to that HelloWorldLayer for the touchBegan and touchEnded method, and did whatever they said. At first, I thought all I had to do was implement the touchesBegan and touchEnded methods in my new scene, but that wasn't enough because I never told that scene that it would receive touches, so, like in the HelloWorldLayer, in the init section, I had to add:

'[[CCTouchDispatcher sharedDispatcher] addTargetedDelegate:self priority:0 swallowsTouches:YES];'

Your code, once again, really helped, though I do have one more question. When this code executes, there are two items on the second retainCount. I am 99% sure that these two items are the two sound files I have loaded. I used the SimpleAudioEngine to pre-load these two sound files in my init method, that way there isn't a pause the first time they are used.

So, my final question is, using the SimpleAudioEngine, how would you dealloc or remove or whatever pre-loaded sound files?

Posted 1 year ago #
jd
Member

I don't think it's the preloaded sounds. They can stay in memory and won't hurt your retain count as far as I know.

Put a CCLOG in your dealloc method. If it's getting called then your scene is now releasing properly and don't worry about the retain count at that point. I put dealloc methods with CCLOG's in all my scenes and layers to make sure they get released.

Posted 1 year ago #
kingsapo
Member

So I tried your advice, and it appears the dealloc method is not being called. Then, I tried putting [self dealloc] in the onExit method, and that got the error message "Program received signal: 'EXC_BAD_ACCESS'". Any ideas?

Posted 1 year ago #
jyoung
Member

You don't call dealloc on objects. You call release and let the system dealloc them.

Posted 1 year ago #
kingsapo
Member

Right, I know that, I was trying to manually call the dealloc method. Is there a more proper way to call the dealloc method other than [self dealloc];?

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.