I saw this property today in the wiki..

http://www.mediamonkey.com/wiki/index.p ... ngPlayback

I wish for this to be exposed as an 'event' so that I can stop playback as it starts! Assuming it will help avoid the 'buffer' sound that occurs when trying to stop after the 'onplay' event occurs.

As MediaMonkey is compatible with Winamp plugin Structure and Winamp Plugin Structure has Big Big Flaws regarding Controlling/Using Real Crossfade and Track Smooth playback MediaMonkey Suffer this also

Even this do not make lots of problems for regular usage, but like in your case this is noticeable for Events.

Simply said: Advanced Controlling of playback (SDB Events) with supporting outdated winamp plugin structure is very difficult
You could test it with SQR Crossfade plugin and you will see what the bug is. We are (As DJ especially me) hoping that something could be done in MM to make things better and resolve bug/feature that bothered me from 1996 and it is never been solved in Winamp and as DJ you are forced to use Advanced DJ apps for basic thing. That is reason why most DJs that use MM and/or Winamp start two instances of app to have control of playback.

I don't really understand what the winamp plugin stuff has to do with firing an sdb event when a track ends?

I don't use the crossfade (its unchecked), but I leave the rest of the options checked (remove silence/smooth pause/seek/stop).

I have not really tried unchecking them and seeing tho I could do that.

But with cross fade disabled, I still get a little bit of the next track.

It should be apparent when trying the stop or pause after script, queue up a few different songs and try the pause or stop button the script adds and listen for any bursts of sound inbetween tracks/pause/stop.

I see, Unfortunately as you already know it is not possible due to Plugin Architecture (Winamp).

Some timings when Events Are Triggered should be revised.
Best solution would be adding this events:
CrossfadeTrackStart - Triggered before Next Track is loaded so that Script can Execute CrossfadePause/Stop to pause/stop playback of next track until...

CrossfadeTrackEnd - Triggered when crossfaded track is ended and where script can execute CrossfadeUnPause/Play for next track

Those two events could be executed only if Crossfade is enabled for output plugin and if crossfade is not enabled normal Start/End should be fired.

Correct me if Im wrong?

actually, what I want is so my 'stop or pause after' script does not start the playback of the next track.

Currently the way I have to do it is wait for the next track to start, the immediate stop or pause it.

This causes the first few samples of the next track to be played the abruptly stopped.

This is less than ideal for use in example, DJ type situations where you want a track played and stop at that track (while still advancing to the next track, either automatically or via the script manually advancing it).

I think You are wrong It should be fired exactly on end as that way you can do things in in crossfade time TrackStart -> Background ScriptExecuted ->TrackEnd -> Script Stopped if not finished as track is ended.

Example: That is how Radio announcements are used mostly.

This would be a useful event to fire off scripts that based upon when a track ends, rather than when the next track starts.

It would need to fire before the next track is buffered or somehow prevent any 'crossfade' audio from being played until after the event passes.