Player object and memory

Peter T. Evensen pevensen at
Thu Mar 9 12:56:37 EST 2006


Thanks for your input.  I'll try setting it to empty and then setting it to 
the next filename.  I was thinking part of the issue was that at one point 
I was setting the filename to empty and I thought that might be causing the 

I'm locking message before I set the filename so I don't get a playStopped 
message.  I had seen that issue before, which caused some nasty recursion 
in my other program.

At 11:45 AM 3/9/2006, you wrote:
>Recently, Peter T. Evensen wrote:
> > I am trying to play a sequence of MP3s.  I am using 3 interleaved players
> > to speed up the transition between the sounds.  I set up the first 3 sounds
> > on Player 1 - Player 3.  I then start Player 1 and when I get a playStopped
> > message, I start Player 2 and set the filename for Player 1 to the next
> > sound file for that player (if there is one).  Is there any memory
> > management issues I need to be aware of?  My stack freezes eventually on
> > XP, both as a standalone, and in the IDE.
>You might try setting the fileName of each player to empty before setting
>new fileNames.  I had an issue way back that was alleviated by doing this --
>it might help in your situation.
>Also, you might make sure that no playStopped message is being sent when
>*setting* the fileName of a player.  This was a bug some time ago that
>caused some frustration -- don't know if it was ever fixed, but even if it
>is still present, I can't say if it would be a problem in your situation.
>Scott Rossi
>Creative Director
>Tactile Media, Multimedia & Design
>E: scott at
>use-revolution mailing list
>use-revolution at
>Please visit this url to subscribe, unsubscribe and manage your 
>subscription preferences:

Peter T. Evensen
314-629-5248 or 888-628-4588 

More information about the Use-livecode mailing list