# Unexpected behavior on seek in Bitmovin Player

**URL:** <https://community.bitmovin.com/t/unexpected-behavior-on-seek-in-bitmovin-player/3408>\
**Category:** Support\
**Tags:** bitmovin-player, bitmovin\
**Created:** [November 14, 2024, 12:29am UTC](https://community.bitmovin.com/t/unexpected-behavior-on-seek-in-bitmovin-player/3408 "2024-11-14T00:29:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![alfsender](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@alfsender](https://community.bitmovin.com/u/alfsender)\
**Post date:** [November 14, 2024, 12:29am UTC](https://community.bitmovin.com/t/unexpected-behavior-on-seek-in-bitmovin-player/3408/1 "2024-11-14T00:29:43Z")

</div>

### Product

Player

### Question

Hi Team,

I am seeing unexpected behavior where when I try to seek in the bitmovin player it shows the buffer section after the cursor on my player seekbar. I am using SmpteController to calculate the SMPTE timecode and I am thinking because of this it’s not showing the correct value. I checked the FrameAccurate demo from Bitmovin and there it shows properly.

I applied same config as from the Bitmovin Frame Accurate demo but still I am seeing this issue. Please share inputs / suggestion to identify the issue.

Thanks.

---

<div class="post-metadata">

**Author:** ![alfsender](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@alfsender](https://community.bitmovin.com/u/alfsender)\
**Post date:** [November 14, 2024, 8:45pm UTC](https://community.bitmovin.com/t/unexpected-behavior-on-seek-in-bitmovin-player/3408/2 "2024-11-14T20:45:45Z")

</div>

Attaching Image here for reference. As you can see my cursor is shown at specific point but it seeks to couple of seconds after the cursor where it shows “07:15” as tooltip. Due to this issue, SmpteController to calculate the SMPTE timecode is not matching with the time shown by the player.

 ![seek_issue_1](https://us1.discourse-cdn.com/flex015/uploads/bitmovin/original/2X/e/e00758ad3dbdfc5182a52a364f9c3eb3d580c346.jpeg)

When I check the same behavior on Bitmovin Frame Accurate seek demo, I see the seek working properly.

 ![seek_working](https://us1.discourse-cdn.com/flex015/uploads/bitmovin/original/2X/7/782ec3a20126ab84cbbc0b8782a3b85a4d790b8c.jpeg)

I am not able to figure out why when I integrate bitmovin player in my application I see this issue. Any pointers or suggestion will be really helpful.

Thanks.

---

<div class="post-metadata">

**Author:** ![davidsteinacher](https://sea1.discourse-cdn.com/flex015/user_avatar/community.bitmovin.com/davidsteinacher/32/163_2.png) [@davidsteinacher](https://community.bitmovin.com/u/davidsteinacher)\
**Post date:** [November 15, 2024, 4:55pm UTC](https://community.bitmovin.com/t/unexpected-behavior-on-seek-in-bitmovin-player/3408/3 "2024-11-15T16:55:00Z")

</div>

Hi @alfsender,

To me, this seems like a UI glitch. Do you have any additional CSS in your application that could affect the positioning calculation on the seek bar? Maybe you could compare the CSS styles from your application and our demo to see if there is any difference.

BR,  
David

---

<div class="post-metadata">

**Author:** ![alfsender](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@alfsender](https://community.bitmovin.com/u/alfsender)\
**Post date:** [November 15, 2024, 5:36pm UTC](https://community.bitmovin.com/t/unexpected-behavior-on-seek-in-bitmovin-player/3408/4 "2024-11-15T17:36:50Z")

</div>

> [@davidsteinacher](#):
>
> styles from your application and our demo to

Thank you for the inputs David. I don’t think there is any application css that could affect the Bitmovin player. But I will double check just to be sure.

Thanks.