0
0

Hey guys,

We’re trying to keep as many ‘simple sounds’ as possible to optimize our performance. However, we’ve noticed (4.38.03) that when we multiselect a bunch of simple events we can only edit the values represented in the ‘Fader View’ – there is no access to the values in the ‘Property List’ view (like 2d/3d and radius).

How would recommend bulk editing of simple sound properties such as 2d/3d and radius?

Thanks!

  • You must to post comments
0
0

Open Designer 2010’s View menu, expand the ‘Event Multi-Selection’ submenu, then select the ‘Property List’ submenu item. With this option checked, multi-selecting events will cause a bulk-editable property sheet to be displayed instead of the bulk-editable fader view that usually appears. When you need to see the fader view again, open the View menu, expand the ‘Event Multi-Selection’ submenu, and select the ‘Fader View’ submenu item.

Designer 2010 won’t let you see both the fader view and the property list at the same time, but you should be able to switch between them pretty quickly by using the keyboard shortcuts ‘F9’ and ‘F10.’

  • You must to post comments
0
0

Hey Joe,

Have you tested this? Because it definitely does NOT behave like how you describe for me in 4.38.03.

Let me define a more specific test case –

  1. create a few simple events (drag and drop .wavs into the event window) in FMOD Designer (4.38.03) (these simple events should NOT reference a sound definition, but rather are the ‘new’ type of simple event)
  2. In the Events tab, highlight all (must be more than 1) of these new simple events
  3. In the ‘View’ menu, select Event Multi-selection>Property List, OR hit F10

Current Result = blank property page

Desired Result = active property page for ALL selected (new format) simple events

This is a HUGE problem for folks with thousands of simple events that need to modify parameters not available through Fader view – such as 2d/3d and radius – especially because simple events do not appear to be created through ‘templates’. This issue represents a step backwards for simple events which can still be multi-edited from a property list IF they reference a sound definition, but NOT when they use this new ‘sound definition-less’ archetype. I assume this is an oversight that you intend to fix immediately, if not please advise as to best multi-edit the new simple event parameters that are NOT available thru ‘fader view’.

Thanks,

Rich

  • You must to post comments
0
0

Ah, that must have slipped past quality assurance. We’ll fix it.

In the meantime, there’s a simple workaround you can use. The bulk editable property list will appear properly if there’s at least one multi-track event in the selection, so just create one of those, include it in the multi-selection, make your bulk edit, then delete the multi-track event when you’re done. It’s slightly cumbersome, but should be less trouble than editing each simple event individually.

You should be prompted to select a template when dragging .wav files into the Groups Browser if your project contains templates.

  • You must to post comments
0
0

Hey Joe,

Unfortunately, your work-around does not help in regards to multi-editing of playLIST behavior for simple events (which defaults to random) – so get that fix in as soon as you can.

Many thanks!

-R

  • You must to post comments
0
0

Ah, I was under the impression that you wanted to bulk edit the property list properties, not the simple event-specific playlist settings. Unfortunately, that takes your entirely legitimate complaint from being a bug report to being a new feature request. That wouldn’t normally be a problem, but FMOD Studio is getting close to release, and we’re somewhat reluctant to add features to the tool it’s about to make obsolete.

Don’t get me wrong, I agree that Designer should include the ability to bulk edit simple event playlist properties. I’ll campaign for it, in fact, but I’m just one voice among many, and I can’t make any guarantees.

  • You must to post comments
Showing 5 results
Your Answer

Please first to submit.