FBX Import Resets Framerate to 25fps Incorrectly #98604

New Issue

Robert Tolppi · 2022-06-05T04:08:19+02:00

Robert Tolppi commented

2022-06-05 04:08:19 +02:00

System Information
Operating system:
Graphics card:
MacBook Pro (16-inch, 2021)
Apple M1 Max
64 GB Memory

Blender version: 3.1.2

Short description of error
When importing certain fbx files, framerate incorrectly resets to 25FPS and incorrectly scales animation data.

Exact steps for others to reproduce the error

Open blender
Set fps to 29.97
Import attached fbx file (in this case, a 3d scene from davinci resolve exported at 29.97 fps)
Observe that the framerate changes to 25 fps

The fbx file is not corrupted and imports correctly into Houdini. This error is likely due to the default behavior when importing an FBX file that doesn't clearly specify its framerate in a way blender understands is to reset the framerate to 25 fps. There are cumbersome workarounds apparently (see this unreal engine thread which points to the code that needs changing in the importer script ) but the error still persists in the latest version of blender. I am not a developer so there may be a technical reason why the fps resets to 25fps but, if possible, it would be better if the file was interpreted to match Blender's set frame rate so that animations for things such as camera tracks line up correctly timewise.

Thank you so much to the Blender development team for all your hard work!
test track.fbx

**System Information** Operating system: Graphics card: MacBook Pro (16-inch, 2021) Apple M1 Max 64 GB Memory Blender version: 3.1.2 **Short description of error** When importing certain fbx files, framerate incorrectly resets to 25FPS and incorrectly scales animation data. **Exact steps for others to reproduce the error** 1. Open blender 2. Set fps to 29.97 2. Import attached fbx file (in this case, a 3d scene from davinci resolve exported at 29.97 fps) 3. Observe that the framerate changes to 25 fps The fbx file is not corrupted and imports correctly into Houdini. This error is likely due to the default behavior when importing an FBX file that doesn't clearly specify its framerate in a way blender understands is to reset the framerate to 25 fps. There are cumbersome workarounds apparently (see [this unreal engine thread which points to the code that needs changing in the importer script ](https://forums.unrealengine.com/t/fbx-export-from-ue4-bug-and-blender-animation-import-25-fps-work-around/436668)) but the error still persists in the latest version of blender. I am not a developer so there may be a technical reason why the fps resets to 25fps but, if possible, it would be better if the file was interpreted to match Blender's set frame rate so that animations for things such as camera tracks line up correctly timewise. Thank you so much to the Blender development team for all your hard work! [test track.fbx](https://archive.blender.org/developer/F13133131/test_track.fbx)

Robert Tolppi commented

2022-06-05 04:08:19 +02:00

Added subscriber: @RobertTolppi

Omar Emara commented

2022-06-06 14:34:57 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-06-06 14:34:57 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Omar Emara commented

2022-06-06 14:34:57 +02:00

Looks like TimeMode is 8 in this file, yet the FBX_FRAMERATES dictionary doesn't contain a mapping for it.

Looks like TimeMode is 8 in this file, yet the `FBX_FRAMERATES` dictionary doesn't contain a mapping for it.

Bastien Montagne commented

2022-06-13 11:48:48 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2022-06-13 11:48:48 +02:00

Problem is, mode 7 and 8 are NTSC 'drop frames' modes... Don't think we have any ways to represent/handle this in Blender.

Guess we'll have to assume 'regular' 30/1.001 NTSC framerate for those as well...

Problem is, mode 7 and 8 are NTSC 'drop frames' modes... Don't think we have any ways to represent/handle this in Blender. Guess we'll have to assume 'regular' `30/1.001` NTSC framerate for those as well...

blender-admin commented

2022-06-13 12:15:39 +02:00

This issue was referenced by b91319aead

This issue was referenced by b91319aead96a5f6eaa11728626765dc288e8649

Bastien Montagne commented

2022-06-13 12:26:02 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Bastien Montagne closed this issue

2022-06-13 12:26:02 +02:00

Bastien Montagne self-assigned this 2022-06-13 12:26:02 +02:00

Thomas Barlow referenced this issue

2023-09-24 01:32:34 +02:00