0
0

[code:3tlpp0mr]

06/06/08 4.17.00

  • Added automatic build optimisation for "simple" events
  • Added project workspaces – you can now have multiple projects loaded at the
    same time – great for realtime mixing!
  • Added music audition palette – audition music interactively within designer
  • Added segment playlists – segments may now contain multiple samples

  • Fixed problem with templates zeroing out properties

  • Fixed problem with wave bank tab not being refreshed for music data
  • Fixed problem with scene and theme editor canvas not being resized when
    loading new projects

  • Older FMOD Ex API branches will load "simple" events but FMOD Ex API 4.17.00
    or higher is required to realize their full resource saving benefits
    [/code:3tlpp0mr]

This thread is for discussion / bugreports for the current release.
Download the current release from the front page at http://www.fmod.org

  • You must to post comments
0
0

Bug report: Copying and pasting events between projects in a workspace works, but does not also copy the referenced sound definitions and audio files.

Bug report: Copying and pasting sound definitions between projects in a workspace causes a crash to desktop. This happens regardless of the number of sound definitions copied/pasted or the paste location (in terms of sound definition folders).

This is in XP, service pack 2. I’ve tried it with existing and with newly created test projects.

  • You must to post comments
0
0

[quote="PeteWard":3lvr3m8e]Bug report: Copying and pasting events between projects in a workspace works, but does not also copy the referenced sound definitions and audio files.[/quote:3lvr3m8e]
Copying and pasting between projects is supposed to be disabled for the present; you can see that the Paste option in the context menu is disabled if you’ve changed projects since copying. However, copying and pasting with shortcut keys (Ctrl+C, Ctrl+V) was still allowed, which is a bug. This has been fixed (i.e. all copying and pasting between projects is disabled) for the next release.

[quote="PeteWard":3lvr3m8e]Bug report: Copying and pasting sound definitions between projects in a workspace causes a crash to desktop. This happens regardless of the number of sound definitions copied/pasted or the paste location (in terms of sound definition folders).[/quote:3lvr3m8e]
As above, copying and pasting between projects is currently not supported. It will be added soon.

Thanks,
Ben

  • You must to post comments
0
0

Ah right :)

When do you think copying and pasting between projects will be allowed? It’s something that would be very useful indeed.

  • You must to post comments
0
0

[quote="PeteWard":12ngqzwb]When do you think copying and pasting between projects will be allowed? It’s something that would be very useful indeed.[/quote:12ngqzwb]
Agreed :-)

Copying and pasting between projects is a high priority for us, so we’re aiming to get it done as soon as possible, probably within the next month or two.

Ben

  • You must to post comments
0
0

with workspaces, is it possible to audition multiple projects simultaneously?

  • You must to post comments
0
0

[quote="dave7L":2ui92rxn]with workspaces, is it possible to audition multiple projects simultaneously?[/quote:2ui92rxn]

Yes…though you need to switch between projects using the ‘Project’ dropdown list.

Network auditioning is the main use case for workspaces at the moment. If your title is using multiple project files, you can load all projects into the Designer workspace and switch between the projects easily, while tweaking levels remotely.

cheers,
Templar

  • You must to post comments
0
0

I got a crash (error report to microsoft) when building using version 4.17. After going through all soundevents I found the problem being an event containing one layer that was both disabled and muted. Deleting this event fixed the problem. The previous designer version I used was 4.13.

  • You must to post comments
0
0

[quote="marten_b":2idqip80]I got a crash (error report to microsoft) when building using version 4.17. After going through all soundevents I found the problem being an event containing one layer that was both disabled and muted. Deleting this event fixed the problem.[/quote:2idqip80]

Thanks for reporting this, it has been fixed for the next release.

Just to confirm, I was seeing the crash when trying to build an event with all its layers disabled (mute state wasn’t a factor). Is this the behaviour you are seeing?

Ben

  • You must to post comments
0
0

What makes an event "simple" or not "simple"?

  • You must to post comments
0
0

Yeah, I was curious about that, too. Also, what are the runtime benefits of simple events?

  • You must to post comments
Showing 10 results
Your Answer

Please first to submit.