I meant moving forward, with 4.0, adding a loop variable to Sound3D makes complete sense. Obviously for the current version using a custom driver is the best solution. In 4.0, I submitted a SoundTransform3D class that is used by the new VideoMaterial to also handle 3D sound for videos. We could add a loop boolean to the Drivers interface and just use that from mySound3D.loop = true/false. Making it super easy for 4.0 and on!
Good stuff. Cheers, J. On Feb 28, 11:13 am, JustinAtMandala <[email protected]> wrote: > Jerome > > ( Justin posting from work ). > > > Adding looping is a great idea. > > Not mine just trying to help a friend with a project. > > > I think it should be at the Sound3D > > level, not the driver. The drivers are used to calculate > > transformation based on the 3D position of the sound and the > > listener. > > My solution was to avoid any changes to away classes as it is a pain > to maintain a custom version, to do it via the Sound3D class you would > need to change 2 classes and one interface which effects backwards > compatibility, I can submit a patch if it's considered worthwhile, but > actually I was thinking maybe worth allowing video to play mp3 sounds > as an option, that way we can try utilising the StageVideo in molehill > and video class seems to be simpler to listen for a sound end. > > But not really setup for compiling to molehill and not sure I can be > bothered getting latest sdk, does awaylite have this class, I could > try in haXe first. > > Cheers ;j
