How do I set Start Offset to a time or bar-based value?

Say I drag in a music-type asset into a Playlist, and I want to change the Start Offset in a precise way. Instead of % value, I want to either do this in X seconds or X bars.

The use case is simply to create more variations out of a single asset at the Playlist level.

So is there a way to specify time or bars offset instead here?

Or should I do this workaround:

  • Create a new event and drag the music asset inside.
  • Non-destructively “trim” the asset so it starts at 9 bars in or whatever.
  • Drag the event into the Playlist.

I could do this for each asset into multiple event variations that then get Playlist-ed, but it does get more cumbersome when I’m trying to derive multiple “slices” from a single asset. Although it has the strength of also letting me control the stop/fade-out of any assets, too.

Is there a better way to streamline this process?

1 Like

FMOD Studio does not currently support setting start offset in bars, beats, or units of time.

This would definitely be a useful feature to have, so much so that I’m surprised it’s not already in our feature/improvement tracker. I’ll add it now. Thanks for bringing this issue to our attention.

I can’t think of any way to make the process any simpler. Using the “Replace Audio with Trimmed Copy” context menu command before putting your trimmed instruments directly into the playlist might make the event slightly cleaner and easier to read, but wouldn’t meaningfully improve performance and wouldn’t be any easier than the method you’ve proposed.


@joseph As usual you are a font of validation! You keep helping me find an optimum workflow within current possibilities.

I’m surprised too, but glad I asked and you replied. I think there’s a lot of utility in offering different units for setting offsets and other time-based features, especially when you’re working within a rhythm-driven composition and need a tidy way to generate more variations on a theme.

(It reminds me of something else, that feature request to add BPM values for the Delay effect.)

I’ll keep doing the workaround for now. Appreciate it.

1 Like

I support this feature idea too. It would be great to have