This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:concept:start [2024/05/26 01:09] – Blendshapes - head: link to pitch roll yaw yussuna | en:concept:start [2025/02/21 19:47] (current) – [Bones and Blendshapes] What each bone value means yussuna | ||
---|---|---|---|
Line 43: | Line 43: | ||
+ | ===== Shortcuts ===== | ||
+ | Shortcut and hotkeys on Inochi2D' | ||
+ | * [[shortcut|List of Shortcut and hotkeys]] | ||
+ | ===== Bones and Blendshapes ===== | ||
- | ===== Blendshapes ===== | + | The terms of " |
- | Blendshapes are facial expression data, you can use it to input those expression | + | |
+ | In the context of camera tracking, tracking software usually creates an internal 3D model that is deformed to match the shape of the body seen by the camera. Then both **bone** and **blendshape** information is extracted from this internal 3D model to be sent as data. For example, a parameter that most camera tracking software abstracts as a **bone** is the **Head**, which has both a **position** and **orientation**. More advanced tracking solutions can also send **hand** and **finger** data as **bones**. In the case of **blendshapes**, | ||
+ | |||
+ | In short, | ||
\\ \\ | \\ \\ | ||
- | Visual representation of some blendshapes: | + | Example: |
- | * [[pitch-roll-yaw|Head]] | + | * [[pitch-roll-yaw|Head |
+ | * Bone ( [A, B, C], [D, E, F, G] ) | ||
+ | * **A:** X (Left-Right) | ||
+ | * **B:** Y (Up-Down) | ||
+ | * **C:** Z (Front-Back) | ||
+ | * **D:** Rx | ||
+ | * **E:** Ry | ||
+ | * **F:** Rz | ||
+ | * **G:** Rw |