- Added MP2 support
- Added linked control for event "Volume" parameter, which maintains relative dB gain between selected events. The operational gain values are clamped between -60dB and 0dB.
- Added "music" category
Removed "Music" event property
Fixed "Seek Speed" in "Parameter Properties"
- Fixed drag and drop in category hierarchy
- Fixed envelope point value tab disappearing when mouse approaches edge of layer
- Fixed parameter velocity and seek speed now in terms of parameter units
- Fixed bug in eventplayer loading
Fixed sounds jumping into different layers
EventCategory indices may be incorrect (+1) until projects are rebuilt
This thread is for discussion / bugreports for the current release.
Download the current release from the front page at http://www.fmod.org
See programmers API revision.txt for updates in FMOD Event runtime engine / API.
Sorry Brett, I was going to be using it for Xbox 360 too but was also (mis :wink:)using it to tag it generally as music too using that method. You’re right enough though, I’ll just tag it separately using the User Properties for that purpose since the Xbox 360 will pick it up from being in the Music category even if it’s nested.
It’s possible there might be other uses to need to know the full category name instead of the last entry in the directory structure though.
With the new music category replacing the music event property, I can’t see a simple way of extracting whether an event is a music file from the event itself. If I have an event and call getCategory, then call getInfo on that category, you only get the last entry in the directory structure, so for "music/SomeKindOfMusic", you only get "SomeKindOfMusic", which doesn’t help. Obviously it works if you don’t nest your music, but that seems to be an unnecessary restriction.
Is there a way of determining whether an event is music or not from the event, or am I missing something obvious? I’d rather not have to parse the event structure fully just to get details of the nesting so I can tell if an event is music or not.
Right, that’s just re-adding the music property that you removed though really. The real problem with that is that it would be possible to accidentally mismatch these if a property isn’t set. It’s not a major problem, but it does seem like there should be a pathway for the event to know if it’s tagged as music or not, without having to do this.
The event property was never really an info flag for people to get, it was to tell the xbox 360 that this event was to be automatically muted/paused when the dashboard music was started, so if people want extra flags/info they can just add it themselves for now. It shouldn’t have been there in the first place.
Please login first to submit.