Inspect a GLB download before you build an animation pipeline around it. In mvntSTUDIO, GLB is the current 3D download; BVH and FBX exports are planned. Blender imports glTF 2.0 files, including GLB, but a clean import is only the first check. Confirm that your file contains the character, an armature, and playable animation before it goes into a production scene.
This guide is about accepting an asset, not about automatic conversion. It assumes no fixed MVNT skeleton, material result, or native Blender integration. Keep Blender's glTF import/export documentation open for your installed version, and see the export overview for current formats.
Preserve a clear source package
Keep an untouched copy of the downloaded GLB and work in a separate Blender file, so an experiment never becomes your only copy. Name files by track section and revision rather than with names that imply a final result, and add a short note with the clip duration and known issues.
Keep the music separately too. Audio playing in the browser doesn't mean the GLB embeds a synced soundtrack, so pass the correct track and start offset to the next editor. Note what you actually downloaded: a character-only asset and an animated character are different deliverables, even though both end in .glb.
Import into a clean inspection scene
Import the GLB into an empty scene with Blender's glTF 2.0 importer. A production scene can hide what arrived behind hidden collections, existing actions, or unusual scale. Check the Outliner first: find the mesh objects, any armature, and how they relate. Don't rename bones or restructure the hierarchy yet.
Blender converts glTF animation into its own animation data, so inspect that data instead of judging by the visible mesh. A character in a neutral pose could be a static asset, an animation that isn't playing, or a scene viewed outside the clip range. Work out which case applies before troubleshooting.
Check motion before appearance
Find the imported action in Blender's animation editors and check its frame range. Play the range, then scrub the start, middle, and end. Confirm that the mesh deforms with the skeleton and that the timeline covers the intended section. Record the actual playback duration instead of changing the frame rate until it looks right.
| Inspection | What to record | Why it matters |
|---|---|---|
| Animation | Action names, frame range, observed duration | An imported model alone is not a verified dance clip. |
| Skeleton | Armature presence, bone hierarchy, rest pose | Later retargeting depends on the actual rig. |
| Transform | Object scale, facing direction, ground position | Unexpected transforms can complicate conversion. |
| Contacts | Foot placement and hand/body intersections | These need a creative review, not just a clean import. |
| Appearance | Missing textures or changed material response | Materials can render differently in each application. |
| Audio | Track version and selected start offset | Sync depends on an explicit handoff. |
Measure scale and travel explicitly
Compare the character with an object of known size, and inspect object transforms and the motion path before changing anything. Decide whether the clip should keep its world travel or become an in-place animation. Removing translation silently changes the dance, and applying transforms without understanding the rig can break the next export.
Check the feet against the ground through the whole clip; a correct first frame proves nothing about the rest. Review turns and fast limb movement from more than one angle. Note the problem frames so the next animator can decide whether to adjust keys, add constraints, or pick a different draft. Fixes vary by rig and clip, so this guide doesn't prescribe one.
Separate inspection from retargeting and conversion
An animation that plays on its original character won't necessarily work on another skeleton. Bone names, rest rotations, proportions, and hierarchy can all differ. Retargeting needs a proper bone mapping and pose alignment; renaming a few bones is not a test.
If your team exports an FBX from Blender, that is your own DCC conversion, separate from the planned native mvntSTUDIO FBX download. Check the conversion settings, the destination's requirements, and the result in the receiving application, and keep the source GLB with a note on the conversion. Read the Unity and Unreal retargeting checklist before promising reusable engine clips.
Frequently asked questions
Does every GLB contain animation?
No. Check the file itself for animation data and playback. The extension doesn't guarantee a skeleton, a dance action, a soundtrack, or a fixed bone layout.
Is a Blender conversion a built-in MVNT integration?
No. It's an external step you choose and verify yourself. Native FBX and BVH exports from MVNT are planned but not yet available.
Sources and next step
See Blender's glTF documentation for version-specific import behavior. To create a new draft, open Studio and follow the music-to-dance checklist, then hand off the inspected GLB with your review notes.
Workflow and references reviewed October 7, 2026.
