0
0

As I’ve been getting familiar with FMOD Designer I’ve been taking notes of some features that I think would improve the program. Please forgive me if there have been similar feature requests that I missed.

  1. Click and drag sound definitions in Event editor instead of clicking and dragging the end points separately.

  2. Make it possible to group sound definitions in to folders at least visually

  3. Make it possible to organize Sound definitions view alphabetically or in order of size or numbers of files

  4. Make it possible to adjust default settings for pitch randomization and other variables. I’d rather have random pitch default to [-0.03, 0.03] instead of [0,0].

  5. Make it possible to play events in the hierarchy without leaving the hierarchy view. For example, by right clicking on them and selecing play or by control clicking them.

  6. Have the “maximum” display placed visibly above the minimum in the GUI for pitch and volume randomization. It’s more intuitive. Maximum goes up, minimum goes down.

  7. Have the option to drag files from the waveform view into a sound definition folder instead of always having to drag files within the sound definition file view if you want to move one wave to another sound definition. This would be similar to moving files in the folder view in Explorer.

  8. Be able to use CTRL X to cut files from the waveform view and CTRL V to paste them in a different bank.

  9. When right clicking int the wavebank view and selecting “Add Bank” it would be great if the newly created bank was automatically selected. That way I won’t have to click on it again and then click in the Value field to rename it. That process gets tedious when creating many banks.
    An undo function would be nice for things which were accidentally deleted.

  10. Periodic Auto-Save function every 5-10 minutes?

  11. Create Events from sound Definitions. Example, drag a sound definition into the event hierarchy and have it prompt you to create a new event based on that sound definition. The default event in that case would call the sound definition just once at the beginning of the event.

  • You must to post comments
0
0

[quote="brett":3p4kez4r][quote="Adam Smith-Kipnis":3p4kez4r]1. Click and drag sound definitions in Event editor instead of clicking and dragging the end points separately.[/quote:3p4kez4r]You can do that? Just click on the box and drag it.[/quote:3p4kez4r]
When two events are crossfaded together, editing the crossfade length is a bit tricky. You can’t drag the edge of the crossfade directly, you first have to click to select the Event the edge belongs to, then drag the edge. It’s easy to miss the edge, so you may have to click repeatedly before you can move it. I presume this is what Adam means?

[quote:3p4kez4r][quote:3p4kez4r]3. Make it possible to organize Sound definitions view alphabetically or in order of size or numbers of files[/quote:3p4kez4r]
I think that is part of the above improvements.[/quote:3p4kez4r]
Since multiple Sound Definitions can cross-refer to multiple Waves, isn’t it only the size of Wave Banks that matters and affects memory allocation?

[quote:3p4kez4r][quote:3p4kez4r]4. Make it possible to adjust default settings for pitch randomization and other variables. I’d rather have random pitch default to [-0.03, 0.03] instead of [0,0].[/quote:3p4kez4r]We’ll have to note this down.[/quote:3p4kez4r]
Hint: It’s already possible to select multiple Sound Definitions at a time, and edit their parameters simultaneously. Very handy. Because of this, I might even consider default values confusing.

  • You must to post comments
0
0

[quote:23ot30u3][quote="Skaven":23ot30u3][quote="brett":23ot30u3][quote="Adam Smith-Kipnis":23ot30u3]1. Click and drag sound definitions in Event editor instead of clicking and dragging the end points separately.[/quote:23ot30u3]You can do that? Just click on the box and drag it.[/quote:23ot30u3]
When two events are crossfaded together, editing the crossfade length is a bit tricky. You can’t drag the edge of the crossfade directly, you first have to click to select the Event the edge belongs to, then drag the edge. It’s easy to miss the edge, so you may have to click repeatedly before you can move it. I presume this is what Adam means?[/quote:23ot30u3][/quote:23ot30u3]

I didn’t realize that you had to click the sound definition in the event viewer twice in order to move it. Clicking it twice to move it seems unnecessary. I’d like to be able to click it once and drag right away similar to Vegas.

[quote:23ot30u3][quote:23ot30u3][quote:23ot30u3]3. Make it possible to organize Sound definitions view alphabetically or in order of size or numbers of files[/quote:23ot30u3]
I think that is part of the above improvements.[/quote:23ot30u3]
Since multiple Sound Definitions can cross-refer to multiple Waves, isn’t it only the size of Wave Banks that matters and affects memory allocation?[/quote:23ot30u3]

While the Wave Banks are what ultimately determines memory allocation, I think it would be helpful to get a perspective of how Sound Definitions are requiring memory to be allocated by making those Wave Banks available in memory. If a sound definition is calling for some very large sounds requiring a lot of memory to be allocated, it would be good to be aware of that to give the designer the opportunity to be most efficient with Sound Definition construction. Now that I’m thinking about it a little more, it might be beneficial to have two views of memory allocation by a Sound Definition, view 1 would be the total size of all sound files called by that Sound Definition, view 2 would be the total size of all banks from which that Sound Definition references sounds. In regards to the alphabetical request, I’m anticipating working with hundreds if not thousands of Sound Definitions. Any quick way to filter through those would be quite useful. What do you think?

[quote:23ot30u3][quote:23ot30u3][quote:23ot30u3]4. Make it possible to adjust default settings for pitch randomization and other variables. I’d rather have random pitch default to [-0.03, 0.03] instead of [0,0].[/quote:23ot30u3]We’ll have to note this down.[/quote:23ot30u3]
Hint: It’s already possible to select multiple Sound Definitions at a time, and edit their parameters simultaneously. Very handy. Because of this, I might even consider default values confusing. [/quote:23ot30u3]

Thanks for the hint! I wasn’t aware of that one. The only reason I’d suggest using a default value for min/max pitch range and min/max attenuation would be that as a user, I would never select the randomization options unless I truly wanted to have random pitch or volume variation. Having them default to the most useful setting would be beneficial. That would be a setting which created a noticible variation but not to the extent of making it sound unnatural. I suggested those pitch values because they work for me in that regard.

  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.