# Feature request - Visual representation of start offset on wav file

**URL:** <https://qa.fmod.com/t/feature-request-visual-representation-of-start-offset-on-wav-file/16361>\
**Category:** FMOD Studio\
**Created:** [October 28, 2020, 12:19am UTC](https://qa.fmod.com/t/feature-request-visual-representation-of-start-offset-on-wav-file/16361 "2020-10-28T00:19:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bradgentle](https://avatars.discourse-cdn.com/v4/letter/b/898d66/32.png) [@Bradgentle](https://qa.fmod.com/u/Bradgentle)\
**Post date:** [October 28, 2020, 12:19am UTC](https://qa.fmod.com/t/feature-request-visual-representation-of-start-offset-on-wav-file/16361/1 "2020-10-28T00:19:41Z")

</div>

Wondering if there is any possibilty of getting a visual representation of a start offset for the Sound module? It would be nice to be able to control it a bit more finely.  
See Image attached for suggestion.

[[Album] imgur.com ![](https://i.imgur.com/CJaYbog.jpg?fb "imgur.com") ](https://imgur.com/a/OFLunS0)

---

<div class="post-metadata">

**Author:** ![mathew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mathew/32/431_2.png) [@mathew](https://qa.fmod.com/u/mathew)\
**Post date:** [October 30, 2020, 4:29am UTC](https://qa.fmod.com/t/feature-request-visual-representation-of-start-offset-on-wav-file/16361/2 "2020-10-30T04:29:14Z")

</div>

Thanks for the idea, I think that would be pretty nice to see. I’ll record it in our feature backlog.

---

<div class="post-metadata">

**Author:** ![zanhulme](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/zanhulme/32/5069_2.png) [@zanhulme](https://qa.fmod.com/u/zanhulme)\
**Post date:** [April 2, 2025, 5:17am UTC](https://qa.fmod.com/t/feature-request-visual-representation-of-start-offset-on-wav-file/16361/3 "2025-04-02T05:17:48Z")

</div>

I’m also keen for this, but wanted to suggest that as a stop-gap even displaying what % the playhead is that when scrubbing would be very helpful.

That way I could scrub my cursor to the spot I want, take note of the % value, then pop that value into the Start Offset. Not as nice as what Brad’s suggesting, but if it’s simpler to implement for the time being it would be an improvement.

Currently it reads out the timecode position in the bottom-right corner, but I still have to figure out the intended % position by trial and error — which can be frustratingly slow if I’m setting individual start offsets for clips in a multi-instrument.

---

<div class="post-metadata">

**Author:** ![mathew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mathew/32/431_2.png) [@mathew](https://qa.fmod.com/u/mathew)\
**Post date:** [April 2, 2025, 11:45pm UTC](https://qa.fmod.com/t/feature-request-visual-representation-of-start-offset-on-wav-file/16361/4 "2025-04-02T23:45:28Z")

</div>

This feature is available today in 2.03.

---

<div class="post-metadata">

**Author:** ![Bradgentle](https://avatars.discourse-cdn.com/v4/letter/b/898d66/32.png) [@Bradgentle](https://qa.fmod.com/u/Bradgentle)\
**Post date:** [April 3, 2025, 12:19am UTC](https://qa.fmod.com/t/feature-request-visual-representation-of-start-offset-on-wav-file/16361/5 "2025-04-03T00:19:01Z")

</div>

> [@mathew](#):
>
> 2.03.

Very nice! Zander’s stopgap version is pretty good. You think adding the visualisation for the amount it randomizes could be implemented sometime too? I could probably work out the position of the randomizer based on dragging the actual offset position around and then matching that amount to calculate what the range needs to be (i.e. 50% offset + 50% random would be 25%-75% possible starting point) but that feels like a lot of work that could be improved with my suggestion?

---

<div class="post-metadata">

**Author:** ![mathew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mathew/32/431_2.png) [@mathew](https://qa.fmod.com/u/mathew)\
**Post date:** [April 3, 2025, 5:32am UTC](https://qa.fmod.com/t/feature-request-visual-representation-of-start-offset-on-wav-file/16361/6 "2025-04-03T05:32:58Z")

</div>

We already visualize the randomization range on the start offset dial, so I can see it making sense to similarly show the range on the waveform UI also. I’ll add the suggestion to our tracker.
