0
0

I have a multi-layer event that is not lining up with an animation. The audio occurs about 500ms too early. I want to delay the playback of the event so it will match the animation. How do I do this? How do I nudge the start time of the event by ‘n’ milliseconds?

Thanks!

  • You must to post comments
0
0

[quote="NotVeryLoud":3v2afrq6]I have a multi-layer event that is not lining up with an animation. The audio occurs about 500ms too early. I want to delay the playback of the event so it will match the animation. How do I do this? How do I nudge the start time of the event by ‘n’ milliseconds?

Thanks![/quote:3v2afrq6]

At this point there is no simple text field entry that will delay your event.
Generally, you would use a parameter with velocity to add a delay to your sounds…however if you have a complex event this might not be appropriate either.

I think this has already been added to the feature request thread. It might be worth bumping.

cheers,
Templar

  • You must to post comments
0
0

bump .. need this ..

As a work around I resorted to placing a dummy osc waveform in the top layer set to playback volume -60 so I can position a second layer sound later using the parameter set to time as if in a sequencer … lame but works. There must be some other way of doing this. Any hints ?

  • You must to post comments
0
0

You could have a sound definition that had only a "don’t play" entry in it.

  • You must to post comments
0
0

[quote="mattconnolly":6rr4zpyd]You could have a sound definition that had only a "don’t play" entry in it.[/quote:6rr4zpyd]

I just tried this and it didn’t work for me … :( back to the same old trick

  • You must to post comments
0
0

+1 bump… this would be a really useful function.

The work involved is incredibly tedious, and difficult to be accurate:[list:2ttig280]
[:2ttig280] adding a parameter[/:m:2ttig280]
[:2ttig280] setting a velocity on the parameter[/:m:2ttig280]
[:2ttig280] setting the range on the parameter[/:m:2ttig280]
[:2ttig280] adding a ‘do not play’ sound definition to the layer, and[/:m:2ttig280]
[:2ttig280] moving the two sound definitions to the appropriate positions to achieve the desired delay time.[/:m:2ttig280][/list:u:2ttig280]

I thought the setDelay function did this, hence [url=http://www.fmod.org/forum/viewtopic.php?t=11183&highlight=setdelay:2ttig280]this thread[/url:2ttig280], but it appears that isn’t the case.

In fact, I think the current "setDelay" function should be named "setExtendEndTime" to be more representative of what it does. (At least this is how I interpret the docs).

  • You must to post comments
0
0

[quote:3dvvwhq8]In fact, I think the current "setDelay" function should be named "setExtendEndTime" to be more representative of what it does.[/quote:3dvvwhq8]

Channel::setDelay can be used for either setting a start delay or extending the end.

I responded to [url=http://www.fmod.org/forum/viewtopic.php?t=11183&highlight=setdelay:3dvvwhq8]that thread[/url:3dvvwhq8].

-Pete

  • You must to post comments
Showing 6 results
Your Answer

Please first to submit.