0
0

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! :)):
[list:1hcs9po3]
[: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] Undo/redo[/:m:1hcs9po3]
[:1hcs9po3] Interface improvements[/:m:1hcs9po3]
[:1hcs9po3] Events can have no parameters at all[/:m:1hcs9po3][/list:u:1hcs9po3]

Completed recently
[list: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]

  • You must to post comments
0
0
  • Ability to open/edit sounds in external editor
  • Ability to stream from hard drive
  • parabolic curves
  • select multiple layers at the same time in event editor
  • ability to select and move curves/points with events in event editor
  • multiple cones in cone designer (multiple levels of attenuation)
  • display size of each (or multiple is shift-clicked) event groups
  • Diagnostic tool: estimation of total cpu load when selected sounds and effects are playing
  • You must to post comments
0
0

[quote="ssnyder":1erlbzmf]Either a new start mode called "Start Delay" or something, allowing you to delay a certain amount of time (in ms) before starting the sound def. This would also be effective as a layer effect.

Have a random range of start delay – ie: "delay between 1 and 8 ms on Play" – would allow more complex sounds to be dynamically created within the FMOD environment. If start delay was a layer effect, then start delay value could be set with an envelope.

–Scott[/quote:1erlbzmf]

I’d love to get this as well!
I was just looking for a way to do exactly that.

  • You must to post comments
0
0

I’d like a new parameter (angle), like (distance)

It would be an automatic realtime update of angle to sound from listener.

http://52.88.2.202/forum/viewtopic.php?p=33035#33035

cheers
-jason

  • You must to post comments
0
0

[quote="NotVeryLoud":12b77pwe]**FMOD FEATURE REQUEST **

It would be helpful to allow delaying the start time of an event by ‘n’ milliseconds. A simple text field under event properties would work.

Delay Event Start = ‘n’ milliseconds.

[/quote:12b77pwe]

I’d like to have this as an option on the spawn times for sound definitions as well: delay first instance by ‘n’ ms.

  • You must to post comments
0
0

Ok, any timetable on when to expect this in the Event Editor? Undo is vital, so is copy, paste and move – for layers, parameterstrips, envelopes and sounds.

M

  • You must to post comments
0
0

[quote="Skaven":3e3x1rck]

Tough, the delay is not random. But: what if, instead of plugin, it was a parameter in the sound definitions? (Initial Delay, 0 – xxxx ms).[/quote:3e3x1rck]

There is more utility to it being a layer plug-in, rather than a sound definition thing. While being able to set the delay on a sound definition would certainly solve the initial design problem for most of what we are trying to do, it would require me to create 2 sound definitions that were essentially the same, except for the delay. With the delay on a layer, I can put any sound definition on there and get the delay, which is better for the design process, and means I don’t have duplicate sound definitions if I want to delay them, or if I want the same sound def to have different delay values on multiple events.

  • You must to post comments
0
0

Feature Request: (Pretty sure this doesn’t exist already)

In game, a way to load Event Project files from an in-memory location rather than reading from an explicit .FEV file. This would make project loading similar to FSB loading, where you already have the choice to get at them from an in-memory location or from a file.

This is to support engines that have their own pre-loading solution for all resources. Would be particularly useful when loading several projects in burst.

Thanks!

-dpl

  • You must to post comments
0
0

It was on the feature to do list 5 years ago and still no undo for FMOD Designer in 2010. There are many other things the designer needs but one of the benefits of using computers is the ability to undo and redo and you might want to consider this feature again before the world ends in 2012 :)

  • You must to post comments
0
0

Currently most useful features for me would be:

  • to copy the complete path of an event (to paste it where i need it)
  • Only one step of undo would be great (for accidentally deleted stuff)

BTW, great work guys, keep it up!

  • You must to post comments
0
0

[quote="brett":5bppco4t]hi guys,
Thanks for the ideas, i think we’ll try to put in a start delay as a sound definition parameter first, then look at some effect thing later. We can probably slot this in for the next few weeks.
[/quote:5bppco4t]

Hi Brett.
Any idea when we’ll be getting this?
Is it close?

  • You must to post comments
0
0

Hi,

[quote="jocorok":2kak7utb]Were you guys thinking of adding a batch builder? We use different projects for every level and/or language (localization) which makes lots of opening files, clicking and waiting. It would be a nice simple feature that would make our lives easier :>
[/quote:2kak7utb]

We don’t currently have any plans to add a batch builder. Using fmod_designercl in conjunction with your own script is a fairly quick and easy solution to this problem.

[quote="AnimusSonitus":2kak7utb]
Have you considered writing one on your own in the meantime? I’m a total Python novice, but I managed to put together a program that lists all my FMOD projects in a GUI and lets me choose various compiling options for the command line after I multi-select which FDPs to compile. It then writes a BAT file and executes it. It took around 130 lines of code, and if I can do it, I’d imagine you could too.
[/quote:2kak7utb]

[quote="audiodev":2kak7utb]Yeah, we too have had great success whipping up some simple Python scripts for audio builds. We have some extra hoo-ha to integrate with Perforce our Python based build system, but the the core idea of finding fdps and processing them with fmod_designercl.exe is really quick to write.[/quote:2kak7utb]

If anyone feels like sharing their awesome batch-building script with the community, the FMOD wiki ([url:2kak7utb]http://www.fmod.org/wiki/[/url:2kak7utb]) is a convenient place to do it :-)
Perhaps adding a section to [url:2kak7utb]http://www.fmod.org/wiki/index.php5?title=Designer_%28Tool%29[/url:2kak7utb] would be the way to go.

Thanks,
Ben

  • You must to post comments
0
0

[quote="crouton":136nij3o]1. It would be really handy if the "FMOD Engine Designer" system (select it from the menu and use it to dynamically change rpm and load parameters) was available for any sound i.e. it reads the parameters you’ve set for the sound and creates a slider for each parameter. Saves me naming the parameters rpm and load just so I can test it easily ;)[/quote:136nij3o]

Amen Crouton!

I’d like to be able to select multiple sound instances and change their properties instead of changing them one at a time. If I import multiple loops to create an engine and they default as oneshots it gets tiring changing each one to looping by hand.

  • You must to post comments
0
0

[quote="Knucklesound":186ywil5][quote="ssnyder":186ywil5]Either a new start mode called "Start Delay" or something, allowing you to delay a certain amount of time (in ms) before starting the sound def. This would also be effective as a layer effect.

Have a random range of start delay – ie: "delay between 1 and 8 ms on Play" – would allow more complex sounds to be dynamically created within the FMOD environment. If start delay was a layer effect, then start delay value could be set with an envelope.

–Scott[/quote:186ywil5]

I’d love to get this as well!
I was just looking for a way to do exactly that.[/quote:186ywil5]

This would also extend the usefulness of sound events that are shared by multiple in-game objects. As an example, I have about 20 torches all sharing a single event in one scene. Because they all start at the exact same time, I only hear one torch, since the streams are synchronized. On occasion, one or two will be slightly delay in loading, resulting in a very odd flange effect. If I had a way to have each start at random, it would sound like multiple torches.

In fact, if there were a feature/property that instructed a sound definition to start playback of its wavetables at a random time position (so that one starts at 0:05.04, another starts at 0:01.25, and another starts at 0:23.28), that would be an even better way to handle multiple objects sharing the same event. This would prohibit shared events from synchronizing their sound defs without adding a silent load gap with looped material.

  • You must to post comments
0
0
  • randomized panning for 2D sounds
  • changing position each time a sound is spawned

cheers,
Templar

  • You must to post comments
0
0

FMOD Designer Feature Request

Would it be possible to add a basic log file output to the profiler?

I’m currently benchmarking FMOD CPU usage for playing sounds at different sample rates. The Profiler tab currently gives you a nice first glance at what the costs are, but I’d like to graph them out in a spreadsheet and use the actual figures I’m seeing, not to introduce a judgement error in this process.

I’m taking into account the mixer sample rate, data sample rate, active voice count, average CPU% and Peak CPU%.

Being able to have the item of the graph control dialog box out in a nice text file would really help me in this task.

Thanks guys,
Fred

  • You must to post comments
0
0

We’ll be adding these features over the next few months. I don’t have any exact dates for you at this stage.

  • You must to post comments
0
0

[quote="Skaven":2c8xh785][quote="ssnyder":2c8xh785]By shifting sound definitions within an event small amounts of time against each other, things like crashes and explosions become much more interesting and far less repetitive, without the addition of more sample data.[/quote:2c8xh785]
I agree with your point, but you can already do delays with a parameter that has a velocity. Such parameters slide through the event and trigger sounds along the way as they proceed. The slower velocity you give to the parameter, the longer the delay.

Tough, the delay is not random. But: what if, instead of plugin, it was a parameter in the sound definitions? (Initial Delay, 0 – xxxx ms).[/quote:2c8xh785]

i originally thought a sound def random delay parameter would be great, but if we had it as an effect, it could be combined with the velocity and layers, to allow, say, 2 sounds on the same layer to be randomly offset from their original position, using a min/max parameter.
as a way to achieve this,(haven’t tried this yet) we thought of using a paramXX as a layer property, and having the programmer speed up/ slow down the velocity on that param in-game, but doing it that way would be more work for him, and i wouldn’t hear the results till i got it in the game.
the sound def route would be ok, but it would globally affect the definition, and i’m sure many people reuse the same sound defs in several places, and don’t always want the same randomness. (i could just duplicate with a new name as a work around, i know.)
so i guess what i’m saying is……..i’ll take whatever i can get….

  • You must to post comments
0
0

[quote="DLawson":q2apm55s]Feature Request: (Pretty sure this doesn’t exist already)

In game, a way to load Event Project files from an in-memory location rather than reading from an explicit .FEV file. This would make project loading similar to FSB loading, where you already have the choice to get at them from an in-memory location or from a file.

This is to support engines that have their own pre-loading solution for all resources. Would be particularly useful when loading several projects in burst.

Thanks!

-dpl[/quote:q2apm55s]

Yes, I would like to have that feature added to, if possible. Specifically,
if EventSystem::load( ) could have an overload that takes a memory location and a file size, that would work great for us.

  • You must to post comments
0
0

Undo’s been implemented and is currently in test. It’ll go out in dev branch Designer in a few weeks.

  • You must to post comments
0
0

Recent files list in ‘File’.

  • You must to post comments
Showing 1 - 20 of 116 results
Your Answer

Please first to submit.