Differences

This shows you the differences between two versions of the page.

--- visual3d:tutorials:real_time:biofeedback:mac_cortex [2024/06/19 12:55] – sgranger
+++ visual3d:tutorials:real_time:biofeedback:mac_cortex [2024/07/17 15:47] (current) – created sgranger
@@ Line 1: / Line 1: @@
-to install the real-time plugin you will need the following dlls
+====== MAC Cortex  ======
-==== motionanalysis_rt.dll ====
+To install the real-time plugin you will need the following dlls
-this is the real-time plugin. it should go into visual3d's plugin directory.
+=== MotionAnalysis_RT.dll ===
-you can view/change the current plugin directory under "plugin folder" on the "visual3d folder paths" tab of the "visual3d programs options" window (properties->program options on the main menu) in newer versions of visual3d.
-==== evacomm2.dll ====
-this is a support dll. the best place to put it is in the same directory as the visual3d binary (visual3d.exe). alternatively you may place it in any directory in the "path" environment variable.
+This is the real-time plugin. It should go into Visual3D's plugin directory.
-starting the export of the realtime stream in cortex
+You can view/change the current Plugin directory under "Plugin Folder" on the "Visual3D Folder Paths" tab of the "Visual3D Programs Options" window (Properties->Program Options on the main menu) in newer versions of Visual3D.
-you will need to select the option for sdk2 in cortex, and then select the ip address of the 2nd nic card (e.g. where cortex places the streaming packet). if there is only one nic card on the computer running cortex and visual3d is running on that computer, select the same ip address as the motion analysis cameras.
+=== Evacomm2.dll ===
-==== accessing the realtime streaming data ====
-if everything is working you should be able to select the real-time mode tab and the select motionanalysis_rt.
+This is a support dll. The best place to put it is in the same directory as the Visual3D binary (Visual3D.exe). Alternatively you may place it in any directory in the "PATH" environment variable.
-in most cases visual3d can be run on the same computer as cortex, but both cortex and visual3d like to use up the system resources, this will sometimes result in long latency response.
+Starting the export of the Realtime stream in Cortex
-it is recommended that visual3d should be run on a different machine than cortex. if you run visual3d and cortex on different computers you will need to copy or share the project directory to the visual3d computer. this is necessary because motion analysis doesn't provide these parameters over the network stream, in the version you currently have we grab this information from the cal file of the model being used but decided to change that to make it easier to synchronize the data between {| align="right"
+You will need to select the option for SDK2 in Cortex, and then select the IP address of the 2nd NIC card (e.g. where Cortex places the streaming packet). If there is only one NIC card on the computer running Cortex and Visual3D is running on that computer, select the same IP address as the Motion Analysis Cameras.
-| |} to install the real-time plugin you will need the following dlls
+=== Accessing The Realtime Streaming Data ===
-==== motionanalysis_rt.dll ====
+If everything is working you should be able to select the Real-Time mode tab and the select MotionAnalysis_RT.
+In most cases Visual3D can be run on the same computer as Cortex, but both Cortex and Visual3D like to use up the system resources, this will sometimes result in long latency response.
+It is recommended that Visual3D should be run on a different machine than Cortex. If you run Visual3D and Cortex on different computers you will need to copy or share the project directory to the Visual3D computer. This is necessary because Motion Analysis doesn't provide these parameters over the network stream, in the version you currently have we grab this information from the cal file of the model being used but decided to change that to make it easier to synchronize the data between {| align="right"
+| |} To install the real-time plugin you will need the following dlls
-this is the real-time plugin. it should go into visual3d's plugin directory.
+=== MotionAnalysis_RT.dll ===
-you can view/change the current plugin directory under "plugin folder" on the "visual3d folder paths" tab of the "visual3d programs options" window (properties->program options on the main menu) in newer versions of visual3d.
-==== evacomm2.dll ====
-this is a support dll. the best place to put it is in the same directory as the visual3d binary (visual3d.exe). alternatively you may place it in any directory in the "path" environment variable.
+This is the real-time plugin. It should go into Visual3D's plugin directory.
-starting the export of the realtime stream in cortex
+You can view/change the current Plugin directory under "Plugin Folder" on the "Visual3D Folder Paths" tab of the "Visual3D Programs Options" window (Properties->Program Options on the main menu) in newer versions of Visual3D.
-you will need to select the option for sdk2 in cortex, and then select the ip address of the 2nd nic card (e.g. where cortex places the streaming packet). if there is only one nic card on the computer running cortex and visual3d is running on that computer, select the same ip address as the motion analysis cameras.
+=== Evacomm2.dll ===
-==== accessing the realtime streaming data ====
-if everything is working you should be able to select the real-time mode tab and the select motionanalysis_rt.
+This is a support dll. The best place to put it is in the same directory as the Visual3D binary (Visual3D.exe). Alternatively you may place it in any directory in the "PATH" environment variable.
-in most cases visual3d can be run on the same computer as cortex, but both cortex and visual3d like to use up the system resources, this will sometimes result in long latency response.
+Starting the export of the Realtime stream in Cortex
-it is recommended that visual3d should be run on a different machine than cortex. if you run visual3d and cortex on different computers you will need to copy or share the project directory to the visual3d computer. this is necessary because motion analysis doesn't provide these parameters over the network stream, in the version you currently have we grab this information from the cal file of the model being used but decided to change that to make it easier to synchronize the data between cortex and visual3d.
+You will need to select the option for SDK2 in Cortex, and then select the IP address of the 2nd NIC card (e.g. where Cortex places the streaming packet). If there is only one NIC card on the computer running Cortex and Visual3D is running on that computer, select the same IP address as the Motion Analysis Cameras.
-==== trouble shooting ====
+=== Accessing The Realtime Streaming Data ===
-the most common reason the real-time tab doesn't show up is that the dlls aren't in the right place.
+If everything is working you should be able to select the Real-Time mode tab and the select MotionAnalysis_RT.
-==== marker names ====
+In most cases Visual3D can be run on the same computer as Cortex, but both Cortex and Visual3D like to use up the system resources, this will sometimes result in long latency response.
+It is recommended that Visual3D should be run on a different machine than Cortex. If you run Visual3D and Cortex on different computers you will need to copy or share the project directory to the Visual3D computer. This is necessary because Motion Analysis doesn't provide these parameters over the network stream, in the version you currently have we grab this information from the cal file of the model being used but decided to change that to make it easier to synchronize the data between Cortex and Visual3D.
+=== Trouble Shooting ===
-cortex passes the full marker names in the real time stream, but passes [[visual3d:documentation:partners:motion_analysis:c3d_file|truncated 4 character names to the c3d file]].
+The most common reason the Real-Time tab doesn't show up is that the dlls aren't in the right place.
-if you are trying to mix-and-match realtime models and post-processing models collected with cortex, you must be careful with the marker names.
+=== Marker Names ===
-one solution is to always use 4 character names in cortex, but this isn't always practical.
-another solution is to always modify the marker names in the c3d file using a [[visual3d:documentation:partners:motion_analysis:c3d_file|visual3d command]]
+Cortex passes the full marker names in the real time stream, but passes [[Visual3D:Documentation:Third-Party:Motion_Analysis:C3D_File|truncated 4 character names to the C3D file]].
+If you are trying to mix-and-match realtime models and post-processing models collected with Cortex, you must be careful with the marker names.
+One solution is to always use 4 character names in Cortex, but this isn't always practical.
+Another solution is to always modify the marker names in the C3D file using a [[Visual3D:Documentation:Third-Party:Motion_Analysis:C3D_File|Visual3D command]]
 <code>
-and visual3d.
+and Visual3D.
 </code>
-==== trouble shooting ====
+=== Trouble Shooting ===
-the most common reason the real-time tab doesn't show up is that the dlls aren't in the right place.
+The most common reason the Real-Time tab doesn't show up is that the dlls aren't in the right place.
-==== marker names ====
+=== Marker Names ===
-cortex passes the full marker names in the real time stream, but passes [[visual3d:documentation:partners:motion_analysis:c3d_file|truncated 4 character names to the c3d file]].
+Cortex passes the full marker names in the real time stream, but passes [[Visual3D:Documentation:Third-Party:Motion_Analysis:C3D_File|truncated 4 character names to the C3D file]].
-if you are trying to mix-and-match realtime models and post-processing models collected with cortex, you must be careful with the marker names.
+If you are trying to mix-and-match realtime models and post-processing models collected with Cortex, you must be careful with the marker names.
-one solution is to always use 4 character names in cortex, but this isn't always practical.
+One solution is to always use 4 character names in Cortex, but this isn't always practical.
-another solution is to always modify the marker names in the c3d file using a [[visual3d:documentation:partners:motion_analysis:c3d_file|visual3d command]]
+Another solution is to always modify the marker names in the C3D file using a [[Visual3D:Documentation:Third-Party:Motion_Analysis:C3D_File|Visual3D command]]