Hi Michael,

The available format and frame rates for Aximmetry Eye are dependent on your phone model. Note that while other phone apps may offer different frame rates, they achieve this by discarding frames they don't require. Similarly, you can set your phone to a higher frame rate than your project's rendering frame rate in Aximmetry Composer.

Warmest regards,

Hi Eifert,

Thank you for your reply. Honestly, I already found this info in the documentation, but I guess this will not solve the problem. Skipping frames from 60FPS to get 50 is not a good solution in my opinion, timings are different and it is noticeable. Only when everything synced properly I get good output. And I'm afraid I have to use 50P. I will try other phone models when will have a chance. For now VIVE trackers + Sony A7III works perfect for me. Besides I noticed that tracking delay sometimes may vary. I didn't found the reason. iPhone 13 mini + ethernet adapter + cooler were used. WiFi also tested, with the same results.  All works, but during test I had 17 or 18 frames delay . But this day VIVE also has problems with delay. I didn't found the reason. Other days VIVE was ok, but I didn't tested Eye.

I will update if find solution

Regards

Michael

Hi Michael,

Recording at higher frame rates and downgrading to lower frame rates should be barely visible to the eye. Are you sure you're not experiencing the same problems when the phone is set to the same FPS as Aximmetry's rendering frame rate?

Also, what type of delay are you experiencing?
When using Aximmetry Eye to provide both video input and camera tracking simultaneously, the Tracking Delay value in Aximmetry Composer must be set to 0, and the Timecode Sync should be turned on. This is because Aximmetry Eye matches the tracking with the video and sends them with the same timecode to Aximmetry.

Warmest regards,