This thread is a rough way of communicating what’s coming up in FMOD Designer and in what order. This list is by no means complete and it [b:1hcs9po3]will[/b:1hcs9po3] change periodically so use it as a guide only! It is meant to be a quick look at what’s "just around the corner", not an exhaustive roadmap.
If you have any suggestions or things you’d like to see in FMOD Designer then post them here.
being worked on ([b:1hcs9po3]updated 22nd December[/b:1hcs9po3] Happy Holidays! :)):
[:1hcs9po3] Runtime memory/cpu optimisations[/:m:1hcs9po3]
[:1hcs9po3] "Effect" events. These can be attached to a category and the final mixed output of everything in that category appears as a layer in the effect event so you can apply dsp effects etc. to a whole category using FMOD Designer.[/:m:1hcs9po3]
[:1hcs9po3] More cut’n’paste functionality[/:m:1hcs9po3]
[:1hcs9po3] Multichannel streaming improvements – channel mix curves[/:m:1hcs9po3]
[:1hcs9po3] Interface improvements[/:m:1hcs9po3]
[:1hcs9po3] Events can have no parameters at all[/:m:1hcs9po3][/list:u:1hcs9po3]
[:1hcs9po3] More event properties are network tweakable[/:m:1hcs9po3]
[:1hcs9po3] More sound crossfade curves[/:m:1hcs9po3]
[:1hcs9po3] Sample rate optimisation[/:m:1hcs9po3]
[:1hcs9po3] Notes field for wave bank waveforms[/:m:1hcs9po3]
[:1hcs9po3] Override wave bank compression on command line[/:m:1hcs9po3]
[:1hcs9po3] More informative error codes[/:m:1hcs9po3]
[:1hcs9po3] MP2 support[/:m:1hcs9po3]
[:1hcs9po3] Added "music" category and removed "music" event property[/:m:1hcs9po3][/list:u:1hcs9po3]
Oh I did’nt realize the meaning of this parameter "Velocity" : much clearer now.
Thank you very much.
Now I’m playing with units in ruler and real duration of sounds to have something useful for code execution (I’m also coding a test dialog to play the events I’m designing).
- oroussel answered 12 years ago
Fmod Designer feature requests are being compiled here:
Feel free to add requests even if they are just titles (stubs). I’m happy to format any wiki entries made.
The major of these features will be targetted towards FMOD Designer 2.
- templar answered 11 years ago
In the 3D Audition modal window, it would be nice to be able to input an X and Z coordinate by keyboard entry. I had an instance where i needed to hit an exact dB level when exactly 4 units away, and it was quite difficult to drag the little red dot to exactly x = 4.
- Rosin answered 9 years ago
[quote="ssnyder":3lw33s7n]This doesn’t actually work for a one shot Explosion or Crash. Since there is only one trigger event, even having a velocity parameter would only serve to play the sound defined at that velocity point, and if there was nothing, then no sound would play. [/quote:3lw33s7n]
I meant, if you create a parameter (you can name the parameter "Time" if you will), and give this "Time" parameter a Velocity, the parameter will actually increase at a set velocity and trigger all events along the value range as it passes them. This can be used to create timed effects. The slower velocity the "Time" parameter has, the longer the event is.
See the earlier pages in this thread on how to do it.
[code:var9wmr1]i would like the ability to ctrl-z things in the tab that i am currently in. a simple undo basically. [/code:var9wmr1]
[code:var9wmr1]I also feel it would basic and nice if you had the equivalent of an ALT tag that is on website images and buttons. Meaning that when you hover over any button or thing of that nature you get a small description of that item or button. This is usually a common thing seen in most software from what i know. Thanks[/code:var9wmr1]
[code:var9wmr1]also some basic shortcuts, like to load the FMOD Engine Designer, maybe a build shortcut, etc.[/code:var9wmr1]
- solomonjames answered 11 years ago
Along the lines of alphabatized things:
If you have a ton of sound definitions and highlight them all then right-click, you do not see the option to "sort alphabetically". It seems as though you need to right-click in some unused space in the sound definitions window. If you have a lot of sound definitions, then there is no unused space, thus, cannot sort alphabetically.
I really like TapeMaster’s idea.
The categories tab is a good way of showing the group structure and where events lie in it. As a UI way of reinforcing the notion that this tab displays a group or buss structure, it would be good if it [b:2elod6yw]didn’t[/b:2elod6yw] allow the user to edit events from that tab. Instead, the only editing possible would be to move events from one group to another or to ‘clone’ them as TapeMaster says. This would remove any confusion about editing an event that appears in more than one category. Events could of course still be edited normally from the Hierarchy tab.
An extension of this group system that I would find very useful indeed would be the ability to have sounds in one group affect the parameters of sounds in other groups, and to have this functionality available in the Designer. So if a sound in group A is played, groups B and F could be ducked by 6dB for the duration of the group A sound (and have fancy timing and fade settings for the volume effect). Ducking is the most obvious application for this, but I’m sure all sort of other interesting things would be possible…
- PeteWard answered 10 years ago
If the width of the event or category tree views is changed, that width should come back the same when the program is quit and relaunched. This should also be implemented for the add sound definition dialog in the event editor.
I am constantly having to make views wider than default to see long names.
- jcobb answered 12 years ago
1) I do not undestand where I am supposed to post feature request (in the forum, in the wiki now ?): could you say which way is better for you ?
2) so here, a feature request:
would it be possible to get an eventParameter property that indicates if this parameter has a sustain point defined in it ?
(we’d like to have some automatic treatment applied on event with such parameters. May be something returning the number of sustain points defined for a parameter, to begin)
– Olivier –
- oroussel answered 11 years ago
Designer usability requests and bugs
I haven’t read all the pages of this thread, so I apologize if this has been covered. I’m using version 4.25.02 on OSX.
1) Don’t auto-scroll the Event Hierarchy tree view when a new event is added. It makes me have to constantly scroll up to right-click on the group to add the next event. It might be acceptable if the view centered the just-added event rather than moving it to the top of the window. This only happens when there are enough items in the hierarchy and scrolling down is possible. This applies to the Sound Definitions hierarchy too.
2) Make "Sort alphabetically" work on all selected folders rather than just the last one selected. Also, there’s no way to sort the root folders except by dragging them.
3) Make Edit->Clean Project display a confirmation dialog before it actually modifies the project so we can see exactly what will be removed from the project before it’s too late.
4) Don’t automatically expand the entire Sound Definitions tree view when a file is added (via drag-drop) to a definition. Don’t expand anything, in fact. This only happens when the other items in the tree view were collapsed at a root folder that contains an expanded subfolder. If you need more clarification, let me know. This applies to the Sound Definitions hierarchy too.
5) The Event hierarchy should be visible in the event editor pane.
6) The "New Sound" dialog when adding a sound to an event layer should come up in the exact same state it was in when it was last dismissed (i.e. folders expanded the same way and scrolled to the same position.
7) It’s not possible to drag an item and make it the last item in a folder.
8) It would save me a bunch of time if there were a view that displayed the Events hierarchy and the Sound Definition hierarchy next to eachother so that I could just drag Sound Definitions to Events. Doing that should either prompt for an action on drag finished (new layer, add to layer, etc) or switch to the Event editor tab for that Event (and allow dropping the sound onto a layer or onto a "new layer" action somehow).
9) Same as #8, except for dragging from Wave banks to Sound definitions.
10) It should be possible to right-click a Sound definition and "Create event". This could go in place of the "Go to event" option on the context menu. The event should have the exact same path as the sound def, and any folders that don’t exist should be created as necessary.
11) Move the project properties window out of the Events pane and into its own pane. The event properties should fill that part of the view. Once you set up the project properties, you don’t need to edit them and that’s just useless space. Alternately, allow that splitter to completely hide that part of the view.
[i:2aqpc472]Regarding all the pane-related items: A superior solution, IMO, is to just make all the panes dockable so they can be arranged on the desktop however we want.[/i:2aqpc472]
13) The default sound type should be Oneshot, and the default event "Oneshot" property should be yes.
14) The fdp.bak file should not be modified unless the project has actually changed. Otherwise, hitting save twice in a row results in a useless backup.
(edit: consolidated my posts. I’ll update this post if I have any more wish lists )
- BananaRaffle answered 9 years ago
Having a file explorer window on the bottom third of the screen where we could drag and drop files into definitions and events would speed things up (like what Sony ACID and Vegas has).
Also, a tickable option that would have the designer tool group source files into one sound definition using file naming conventions would save a tremendous amount of time.
For example, if I have these files:
…it would notice that all the characters except for the last one are the same, so they would get grouped up in definitions named "str_body_foot" and "gte_gren_exp" respectively.
Edit: I should be more clear. This grouping would perhaps occur when multiple files were drag-and-dropped into the Sound Definition page. It could also perhaps be in the right-click context menu as "Group by name". There would be a setting in the Preferences menu to determine how many trailing characters it uses to group the files.
in no special order,
The ability to sync to n bars instead of just bars/beats (maximum is now every 4 bars, using 16/4 timing and selecting just the first beat) (afterthought: actually by halving the bpm you can get 8 bars, which services my need, but the idea isn’t that bad)
Music files as sound definitions, with weight, percentage etc, to be able to randomize musical content. Would be useful for the way I see my usage.
Allow .ogg as a compression format.
The ability to load and save themes, for those ultra complex routings.
Global BPM or BPM relations between concurrent themes. (a running sequencer in background)
Debug output for the music player or some sort of information to find out what you might be doing wrong when your "logic" isn’t going the way you planned.
Have the ability to "detach" any of the tabs and rearrange them on your screen as you see fit. I’d like to have the sound definition, events, and event editor up on the same window (or spread across multiple screens) at the same time so I can drag and drop from one to the other.
got it thanks. That’s quite a difference! Some other usability issues which would be nice to address:
have FMOD remember size and positioning of the Designer window when it was last closed (it’s currently opening really small every time on a 1600×1200 display)
easier/more responsive means to resize layers in the Event Editor (once more than one effect is loaded on a layer, rather than clicking anywhere in the bottom of a layer to get the resize arrow, you can only get it by clicking on the bottom left)
easier/more responsive means to add and move points (it can take multiple right-click attempts before the "add point" shows up in the contextual menu. I get the "Add sound" menu about 40-50 percent of the time).
-when adding sounds to a Sound Definition, have the tool remember the last directory and point there rather than C:\Program Files\FMOD SoundSystem\FMOD Designer\examples
- broodley answered 12 years ago
Please login first to submit.