Printable View
Thanks for everything guys :)
I am probably going to finalize this object (And the Flash version today).
BackStages, I'm not exactly sure what you mean about the Overlay, but I would suggest you try out my Surface object as well. It does have some cool features and comes with a ton of examples.
Okay, here's the update.
http://clickteam.info/looki/Extensions/Beta/Sound.zip
- Looping should work fine now
- Delete sound fixed
- Name by index and vice versa now work with the actual index, not the numeric ID
- Count sounds expression, allows enumeration
- Sound memory address/binary size expressions
- Sound's original frequency expression
I see Lacewing in the future of uses. :DQuote:
Originally Posted by Looki
Thanks looki :D
Hello, I would like to know if anybody would have problems with me splitting up the object into two objects: A player and generator.
Obviously, I want to remove the 'generator' part from the main extension, to keep things simple (Somebody requested me to make a version without it, so I thought to myself, I might as well split them up).
By the way, the new version will also feature MMF's internal looping, and other flags such as 'uninterruptible'.
Yeah that sounds good, it would allow you to expand on the sound player options more also if needed.
I should have mentioned that there will be some internal restructuring and that some actions will break!
Well it's not a problem for me with that, i would just make a screenshot of the events and re-make it with the new and hopefully better objects.
Maybe you could just change the names of the objects to Sound Player and Sound Generator. Then people could keep the old object and duplicate any projects to the new objects if needed then delete the old object from the folders when ready.
By the way, in what order does things happen when you play a sound with parameters? I tried the option, and for a moment, like a few milliseconds, I heard the sound in both speakers, despite that it was panned hard right.
I know this is a problem with MMF2's own sound playback system, if you for example play a sample, and then set its sample volume and other parameters in a following action, you can get artifacts due to the time it takes from the moment MMF2 plays the sound, to the moment its parameters are set (it happens since sound runs in a separate thread from the events).
The only completely "safe" order to do it while completely avoiding stuff like clicks and pops that I've learnt is this:
* Stop sample on channel (to avoid the sound to be affected by the new settings before it's cut off by the new sound)
* Set channel volume/frequency/pan (in any order)
* Play sample on channel
...though in this case, I have the hunch the sample is started before its parameters are set.
The sound is played and then the parameters are set. However I changed the order now - I wasn't able to hear a difference though.
Since there is not much work to do I will probably release a beta of the Sound Player object soon. :)