This is an old revision of the document!
file commands are separated into three categories:
1) file_management
2) file_open/import
3) file_save/export
for more pipeline commands, please see the pipeline commands reference page.
file_open/import
file_open
adds a file to the visual3d workspace.
file_close
closes the specified file(s).
import_data_from_ascii_file
imports signals from an ascii file formatted using the visual3d_ascii_format.
import_analog_signals
import_analog_anb_signals
import_analog_bioware_signals
import_analog_frappier_signals
import_analog_fsv_signals
import_analog_ndi_signals
imports analog signals from ndi toolbench into a c3d file.
import_analog_noraxon_emg_signals
import_pedar_data
import_analog_son_signals
import_analog_signals_from_amti_ascii_file
the ascii file exported by amti is a very simple file with no header, and the data stored in columns.
import_analog_signals_from_arsalis_ascii_file
import_analog_signals_from_dasylab_ascii_file
import_analog_signals_from_delsys_ascii_file
import_analog_signals_from_microstrain_ascii_file
import_analog_signals_from_winternet_signals
import_analog_signals_from_adinstruments_chart_ascii_file
import_data_from_ascii_file
import_analog_signals_from_datapac_files
import_signals_from_c3d_file
this command imports signals from a c3d file into the active file.
import_surrey_force_platform_signals
merge_aurora_files
import_xsens_mvnx_data
not available in visual3dv5:
import_fsv_files the fsv/tsv file formats were originally developed by manfred berger from innovision systems and are currently used by qualisys and innovision import_analog_signals_from_fsv_file importing analog signals stored in an fsv file into an existing c3d file.