# Time difference with Bitmovin Frame Accurate Demo

**URL:** <https://community.bitmovin.com/t/time-difference-with-bitmovin-frame-accurate-demo/3415>\
**Category:** Bugs\
**Tags:** bitmovin-player, bitmovin\
**Created:** [November 15, 2024, 1:43pm UTC](https://community.bitmovin.com/t/time-difference-with-bitmovin-frame-accurate-demo/3415 "2024-11-15T13:43:26Z")\
**Posts on this page:** 1\
**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 15, 2024, 1:43pm UTC](https://community.bitmovin.com/t/time-difference-with-bitmovin-frame-accurate-demo/3415/1 "2024-11-15T13:43:26Z")

</div>

### Affected product

Player

### Affected platforms

Web

### Description

Hi Team,

I was testing bitmovin frame accurate seek from the [GitHub - bitmovin/demos](https://github.com/bitmovin/demos/tree/develop) repository. I ran the frame accurate seek in my local and updated the source file to dash.mpd file with frame rate of 23.976.

When I play the content it looks good and SMPTE timecode and the player timecode matches. But when I try to seek to certain point for eg: 00:57:05, the player timecode shows as 00:57:05 but the SMPTE timecode shows as 00:57:02:11, so it’s off by few seconds.

### Expected behavior

On seek the Player time and the SMPTE timecode should match

### Reproduction steps

Clone the [GitHub - bitmovin/demos](https://github.com/bitmovin/demos/) repository and update the source for frame-accurate-seek player to point to a dash.mpd file with frame rate of 23.976 and update the frameRate attribute to 23.976

### Additional details

Versions used:  
[https://cdn.bitmovin.com/player/web/8/bitmovinplayer.js](https://cdn.bitmovin.com/player/web/8/bitmovinplayer.js)  
[https://cdn.bitmovin.com/player/web/8/bitmovinplayer-ui.js](https://cdn.bitmovin.com/player/web/8/bitmovinplayer-ui.js)