C4D to XPression Key Frame File Workflow Kit
※表示価格は米ドル建て商品の参考換算です。実際のお支払い金額は決済時のレートにより変動する場合があります。
A practical workflow package for using Cinema 4D Camera / Object keyframe motion data inside XPression as Key Frame File.
This package is designed for users who want to bring Camera / Object motion created in Cinema 4D into XPression, export it as Key Frame File txt data, assign it to XPression parameters, and use it as part of an XPression scene workflow.
This package includes a Cinema 4D sample scene, Cinema 4D Python exporter, Camera/Object txt samples, an XPression sample project with Key Frame File already applied, README files, and workflow guides.
Instead of directly copying Cinema 4D Position / Rotation / FOV values into XPression, this package provides a practical workflow for converting C4D motion into Key Frame File format and checking the required settings on the XPression side.
Product Notes
This product is a digital workflow package consisting of sample files and JP/EN documentation.
No video tutorial is included in v1.0.
This is not a finished broadcast template. It is a practical workflow package for converting, exporting, assigning, and checking C4D Camera / Object motion so it can be used in XPression through Key Frame File.
Use the included C4D sample, Python exporter, Camera/Object txt files, XPression sample project, README, and Workflow Guide to understand the workflow for bringing motion from Cinema 4D into XPression Key Frame File.
What You Can Do with This Package
This package helps you use Cinema 4D Camera / Object motion inside XPression through Key Frame File.
You can use the included files to:
-
Export C4D Camera / Object motion as txt
-
Use C4D Camera / Object keyframe motion data as XPression Key Frame File
-
Confirm the txt column structure for XPression Key Frame File
-
Understand the difference between Camera txt and Object txt
-
Apply Position / Rotation / FOV conversion rules
-
Assign Source Column settings in XPression
-
Check key settings such as Right Handed Coordinates, Scale, Offset, and Rotation Order
-
Inspect an XPression sample project with Key Frame File already applied
-
Separate C4D motion data from final screen placement in XPression
This is not just a script package. It is a practical workflow package designed to help you bring C4D motion into XPression, understand where offsets and mismatches can occur, and check the settings in the correct order.
Included Files
This product includes the following files:
-
Camera Sample.txt
-
Cube Sample.txt
-
README_JP.txt
-
README_EN.txt
-
WORKFLOW_GUIDE_JP.txt
-
WORKFLOW_GUIDE_EN.txt
-
LICENSE_AND_NOTES.txt
-
CHANGELOG.txt
-
XPression Key Frame File exporter.py
-
XPression Key Frame File exporter_Sample.c4d
-
XPression Key Frame File exporter_Sample.xpp
File Details
Camera Sample.txt
A Key Frame File sample for Camera.
It uses a 10-column structure including Position, Rotation, Scaling, and FOV.
In XPression, use this file to check Camera Position, Rotation, and FOV assignment.
Cube Sample.txt
A Key Frame File sample for a non-camera Object.
It uses a 9-column structure including Position, Rotation, and Scaling.
In XPression, use this file to check Object Position, Rotation, and Scaling assignment.
XPression Key Frame File exporter.py
A Python exporter to be executed from Cinema 4D Script Manager.
It reads the world transform of the selected Camera or Object and exports a txt file formatted for XPression Key Frame File.
XPression Key Frame File exporter_Sample.c4d
A Cinema 4D sample scene for this workflow.
Use this scene to check Camera and Object motion and export txt data with the Python exporter.
XPression Key Frame File exporter_Sample.xpp
An XPression sample project with Key Frame File already applied.
You can check how Camera Sample.txt and Cube Sample.txt are assigned inside XPression.
README_JP.txt / README_EN.txt
Documentation for included files, basic steps, how to open the files, and important notes.
WORKFLOW_GUIDE_JP.txt / WORKFLOW_GUIDE_EN.txt
Workflow guides explaining the concept, conversion rules, XPression settings, and practical steps for bringing motion from C4D to XPression.
LICENSE_AND_NOTES.txt
License terms, redistribution restrictions, disclaimers, and commercial-use notes.
CHANGELOG.txt
Version history and update notes.
Target Users
This product is intended for users who:
-
Want to use Camera / Object motion from C4D inside XPression
-
Want to reproduce C4D camera work in XPression through Key Frame File
-
Want to use C4D keyframe motion data as XPression Key Frame File
-
Want to check Source Column assignment with a practical sample
-
Have experienced mismatches when copying C4D Position / Rotation / FOV directly
-
Need to understand Right Handed Coordinates or Rotation Order in XPression
-
Want to separate conversion issues from scene-structure issues
-
Want to use practical sample files as a reference for their own XPression workflow
Basic Workflow
1. Open the C4D sample
Open XPression Key Frame File exporter_Sample.c4d in Cinema 4D.
2. Run the Python exporter
Open Script Manager in Cinema 4D and load the included Python file using Open Script...
File to use:
XPression Key Frame File exporter.py
Select only one Camera or Object, then press Execute in Script Manager to export the txt file.
3. Check the txt file
If a Camera is exported, the txt file uses a 10-column structure including FOV.
If an Object is exported, the txt file uses a 9-column structure including Position, Rotation, and Scaling.
Check Type, Rows, column number list, and first row in the Cinema 4D Console.
4. Load the txt in XPression
Load the txt file as Key Frame File in XPression.
Assign the Camera txt to the Camera.
Assign the Object txt to the Object.
5. Check Key Frame File settings
In XPression, check the following:
-
Column Delimiter = Tab
-
Decimal Separator = Dot
-
Right Handed Coordinates = OFF
-
Rotation Order = default
-
Source Column = Match the txt column number
-
Scale = 1.0
-
Offset = 0.0
6. Adjust screen placement with the parent Group
In this sample, the Object driven by Key Frame File is placed inside a Group, and screen-position adjustment is handled by the parent Group.
By separating C4D Position / Rotation / FOV data from final XPression screen placement, it becomes easier to avoid double correction and troubleshoot offsets.
XPression Screen Coordinate Notes
In XPression, when working with screen coordinates, 0,0 is based at the lower-left of the screen.
For a 1920×1080 XPression scene, the screen center is 960,540.
If C4D data built around the world origin needs to be placed at the XPression screen center, check parent Group offset and Global Transformations.
This screen-center offset is a separate issue from Position / Rotation / FOV conversion.
Conversion Concepts Used in This Product
Position
C4D X/Y values are used as-is, while Z is inverted.
Example:
C4D Position
100 / 200 / 300
Key Frame File Position
100 / 200 / -300
Rotation
C4D HPB values are not copied directly into XPression Rotation X/Y/Z.
The Python exporter reconstructs the C4D orientation as a matrix and converts it into Rotation X/Y/Z values that can be used in XPression.
FOV
This workflow assumes a Perspective Camera and uses Cinema 4D vertical FOV.
For Camera txt, FOV is column 10.
Important Notes
This product is a practical workflow package for using C4D Camera / Object motion inside XPression through Key Frame File.
Before using it as part of a production template, always test it in your own environment.
No video tutorial is included in v1.0. Please refer to README_JP / README_EN and WORKFLOW_GUIDE_JP / WORKFLOW_GUIDE_EN for setup and workflow instructions.
Results may vary depending on:
-
XPression version
-
Cinema 4D version
-
OS environment
-
GPU / driver environment
-
Frame rate
-
Scene resolution
-
Rotation Order
-
Right Handed Coordinates
-
Source Column settings
-
Scale / Offset
-
Parent Group
-
Global Transformations
-
Camera FOV
-
txt file path
-
Output environment
If you open the XPression project on another PC or from another folder, the Key Frame File txt references may be broken.
If this happens, manually reassign Camera Sample.txt and Cube Sample.txt.
What This Package Can and Cannot Guarantee
This package can help you:
-
Use C4D Camera / Object motion as XPression Key Frame File
-
Export C4D Camera / Object keyframe motion data as txt
-
Check Camera txt and Object txt column structures
-
Review Source Column assignment in XPression
-
Understand Position / Rotation / FOV conversion concepts
-
Inspect an XPression sample project with applied settings
-
Understand parent Group adjustment for screen placement
This package does not guarantee:
-
Identical behavior in all XPression versions
-
Identical behavior in all Cinema 4D versions
-
Guaranteed production operation in every environment
-
Support for special C4D scenes using Constraint, Target, Expression, or Deformer setups
-
Automatic adjustment for every project hierarchy or output environment
-
Individual technical support for each purchaser environment
License and Usage Terms
Commercial reference use in your own projects is permitted.
However, the following are prohibited:
-
Redistributing the product files
-
Sharing the ZIP file
-
Reselling the included script or sample project as another product
-
Selling a modified version as a competing product
-
Uploading the files to public repositories or file-sharing services
For details, please refer to LICENSE_AND_NOTES.txt.
Disclaimer
This product is a practical reference package based on workflow testing and sample project setup.
It does not guarantee full reproduction across all XPression versions, Cinema 4D versions, operating systems, GPUs, drivers, project settings, or output environments.
Always verify the workflow in your own environment before production use.
DekoBokoTech / DBT Partners Studio is not responsible for any production issue, data loss, operational problem, or damage caused by the use or modification of this workflow package.
C4D to XPression Key Frame File Workflow Kit
This is a practical workflow package for using Cinema 4D Camera / Object keyframe motion data as XPression Key Frame Files.
Instead of directly copying Position / Rotation / FOV motion created in C4D into XPression, this package includes a complete set of samples for exporting it as Key Frame File TXT, assigning it to Camera or Object parameters in XPression, and using it as part of an XPression scene workflow.
This package includes a C4D sample scene, a Cinema 4D Python exporter, Camera/Object TXT samples, an XPression sample project with Key Frame Files already applied, a README, and workflow guides.
This is not a finished production template, but a practical package that consolidates the conversion, export, assignment, and verification steps for using C4D Camera / Object motion as XPression Key Frame Files.
Instead of directly inputting C4D Position / Rotation / FOV values into XPression, you can use the actual samples to confirm how to convert it for Key Frame Files, which columns to assign to which parameters in XPression, and the order in which to check Right Handed Coordinates, Source Column, Scale / Offset, Rotation Order, Parent Group, and Global Transformations.
About the Product Content
This product is a digital workflow package consisting of sample files and English/Japanese documentation.
As of v1.0, no video tutorial is included.
This is not a finished broadcast template, but a complete workflow for using Camera / Object keyframe data created in Cinema 4D as XPression Key Frame Files.
You can use the included C4D samples, Python exporter, Camera/Object TXT files, XPression sample project, README, and Workflow Guide to understand the process of transferring motion from C4D to XPression Key Frame Files.
What You Can Do with This Product
This package allows you to confirm the process of importing Camera / Object motion created in C4D into XPression as Key Frame Files and assigning them to Camera or Object parameters.
It primarily addresses the following:
-
Exporting C4D Camera / Object motion as TXT
-
Using C4D keyframe data as XPression Key Frame Files
-
Confirming the column structure for XPression Key Frame Files
-
Understanding the difference between Camera TXT and Object TXT
-
Confirming Position / Rotation / FOV conversion rules
-
Confirming Source Column assignment
-
Learning verification points for Right Handed Coordinates, Scale, Offset, and Rotation Order
-
Checking actual settings in an XPression project with applied settings
-
Separating C4D motion from screen placement adjustments in XPression
This is not just a script distribution. It's a practical workflow package that organizes where discrepancies are likely to occur when importing and using motion from C4D in XPression, and the order in which to check them.
Included Files
This product includes the following files:
-
Camera Sample.txt
-
Cube Sample.txt
-
README_JP.txt
-
README_EN.txt
-
WORKFLOW_GUIDE_JP.txt
-
WORKFLOW_GUIDE_EN.txt
-
LICENSE_AND_NOTES.txt
-
CHANGELOG.txt
-
XPression Key Frame File exporter.py
-
XPression Key Frame File exporter_Sample.c4d
-
XPression Key Frame File exporter_Sample.xpp
Contents of Each File
Camera Sample.txt
A Key Frame File sample for a Camera.
It has a 10-column structure including Position, Rotation, Scaling, and FOV.
In XPression, it is used to check the assignment to Camera's Position, Rotation, and FOV.
Cube Sample.txt
A Key Frame File sample for an Object other than a Camera.
It has a 9-column structure including Position, Rotation, and Scaling.
In XPression, it is used to check the assignment to the target Object's Position, Rotation, and Scaling.
XPression Key Frame File exporter.py
A Python exporter to be executed from Cinema 4D's Script Manager.
It obtains the world transformation of the selected Camera or Object and exports it as a TXT file for XPression's Key Frame File.
XPression Key Frame File exporter_Sample.c4d
A Cinema 4D sample scene for workflow verification.
It is used as a sample to check Camera and Object motion and export TXT data with the Python exporter.
XPression Key Frame File exporter_Sample.xpp
An XPression sample project for verification with Key Frame Files applied.
You can check the state after loading Camera Sample.txt and Cube Sample.txt.
README_JP.txt / README_EN.txt
Documentation summarizing included files, basic steps, how to open files, and important notes.
WORKFLOW_GUIDE_JP.txt / WORKFLOW_GUIDE_EN.txt
Documentation summarizing the concepts, conversion rules, XPression settings, and pre-use verification steps when importing motion from C4D to XPression.
LICENSE_AND_NOTES.txt
Summarizes terms of use, redistribution prohibitions, disclaimers, and notes for commercial use.
CHANGELOG.txt
A file that records version history and updates.
Target Users
This product is suitable for those who:
-
Want to handle C4D-derived Camera / Object motion in XPression
-
Want to reproduce camera work created in C4D in XPression
-
Want to use C4D keyframe data as XPression Key Frame Files
-
Want to check Key Frame File's Source Column settings with practical examples
-
Have experienced discrepancies when directly inputting C4D's Position / Rotation / FOV
-
Have been confused by XPression's Right Handed Coordinates or Rotation Order
-
Want to differentiate between conversion issues and scene structure issues between C4D and XPression
-
Want to check how to apply XPression in their own environment while looking at practical samples
Basic Usage
1. Open C4D sample
Open XPression Key Frame File exporter_Sample.c4d in Cinema 4D.
2. Execute Python exporter
Open Cinema 4D's Script Manager and load the included Python file using Open Script...
File to use:
XPression Key Frame File exporter.py
Select only one Camera or Object, then press Execute on the Script Manager to export the txt file.
3. Check the txt file
If a Camera is exported, it will have 10 columns including FOV.
If an Object is exported, it will have 9 columns including Position, Rotation, and Scaling.
In the Cinema 4D Console, check the Type, Rows, a list of column numbers, and the first row.
4. Import into XPression
Import the txt file as a Key Frame File in XPression.
Assign the Camera txt file to the Camera.
Assign the Object txt file to the Object.
5. Check Key Frame File settings
In XPression, check the following settings:
-
Column Delimiter = Tab
-
Decimal Separator = Dot
-
Right Handed Coordinates = OFF
-
Rotation Order = default
-
Source Column = Match the column number in the txt file
-
Scale = 1.0
-
Offset = 0.0
6. Adjust the position on the screen with the parent Group
In this example, Objects driven by Key Frame Files are placed within a Group, and the screen positioning is handled by the parent Group.
By treating the Position / Rotation / FOV values from C4D and the screen positioning adjustments in XPression separately, it becomes easier to reduce double corrections and unexplained discrepancies.
About XPression's Screen Reference
In XPression, when treating screen coordinates, 0,0 is the bottom-left origin.
In a 1920x1080 XPression scene, the screen center is 960,540.
If you need to center data created around the world origin in C4D to the screen center in XPression, check the center offset in the parent Group or Global Transformations.
This center offset is a separate consideration from the Position / Rotation / FOV transformation conventions.
Transformation Concepts in This Product
Position
C4D's X/Y are used as is, and only Z's sign is inverted.
Example:
C4D Position
100 / 200 / 300
Key Frame File Position
100 / 200 / -300
Rotation
C4D's HPB is not copied directly to XPression's Rotation X/Y/Z.
The C4D orientation is reconstructed as a matrix within the Python exporter and converted to Rotation X/Y/Z that can be handled in XPression.
FOV
Assuming a Perspective Camera, C4D's vertical FOV is used.
For Camera txt files, FOV is in the 10th column.
Notes
This product is a practical workflow package for using C4D Camera / Object motion as XPression Key Frame Files.
Please verify it in your own environment before integrating it into production templates or projects.
As of v1.0, video tutorials are not included. Please refer to README_JP / README_EN and WORKFLOW_GUIDE_JP / WORKFLOW_GUIDE_EN for operation procedures.
Results may vary depending on the following conditions:
-
XPression version
-
Cinema 4D version
-
OS environment
-
GPU / Driver environment
-
Frame rate
-
Scene resolution
-
Rotation Order
-
Right Handed Coordinates
-
Source Column setting
-
Scale / Offset
-
Parent Group
-
Global Transformations
-
Camera FOV
-
txt reference path
-
Output environment
If you open an XPression project on a different PC or in a different folder, the txt reference path for the Key Frame File may be broken.
In that case, please re-specify the included Camera Sample.txt and Cube Sample.txt.
What It Can / Cannot Do
What it can do
-
Use C4D Camera / Object motion as XPression Key Frame Files
-
Export C4D Camera / Object key information as txt
-
Check the column structure of Camera txt and Object txt
-
Verify XPression's Source Column settings
-
Learn the transformation conventions for Position / Rotation / FOV
-
See setting examples in XPression-applied projects
-
Understand the concept of screen placement adjustment via Group settings
What this package alone does not guarantee
-
Full reproduction across all XPression versions
-
Full reproduction across all Cinema 4D versions
-
Full operational guarantee in a production environment
-
Support for C4D scenes containing special Constraints, Targets, Expressions, or Deformers
-
Automatic adjustments including output environment and parent-child hierarchy for each project
-
Individual support for purchaser's environment
License and Terms of Use
Reference use in commercial projects is permitted.
However, the following are prohibited:
-
Redistribution of product files
-
Sharing of ZIP files
-
Selling the included scripts or sample projects as separate products as is
-
Selling modified versions as competing products
-
Uploading to public repositories or file sharing services
For details, please check LICENSE_AND_NOTES.txt.
Disclaimer
This product is a reference package based on practical workflows and sample projects.
It does not guarantee complete reproduction across all XPression versions, Cinema 4D versions, OS, GPU, drivers, project settings, or output environments.
Always verify in your usage environment before deploying to production.
DekoBokoTech / DBT Partners Studio is not responsible for production issues, data loss, operational problems, or other damages arising from the use or modification of this workflow package.