I made a tool to generate overlay graphics (HUD)

[JrVolt]

Sadly the Mini 3 Pro generates only very basic SRT info mostly focused around the camera parameters.

Like ? Can you share one line of the Mini3Pro sub?

To the others; i've seen dashware, it's not what i want.
Why you all guys are trying to convince me to use another tool ? I mean... I'M NOT LOOKING FOR ADVICE for tool.
I would like to have some opinion about mine, and feedback about compatibility.

I do not want and do not need a huge chonky cockpit-like graphics,
I do not want install any software or find xml gauge.
Only video.mp4 required, quick and easy.
(I'm not even on a Windows machine, i had to create a VM to install dashware only to respond to you guys)

 

[JrVolt]

P4P V2 Test

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

You made my day !!

 

[microlinux]

Like ? Can you share one line of the Mini3Pro sub?

It doesn't include data in the video, it generates corresponding .srt files, if video captions are enabled:

1
00:00:00,000 --> 00:00:00,016
<font size="28">SrtCnt : 1, DiffTime : 16ms
2025-04-25 20:11:02.153
[iso : 200] [shutter : 1/60.0] [fnum : 170] [ev : 0] [ct : 5400] [color_md : d_cinelike] [focal_len : 240] [latitude: 44.774913] [longitude: -93.404219] [rel_alt: 46.600 abs_alt: 184.451] </font>

The P4P v2 includes data in the video, if video captions are enabled. However, it does not include the DZOOM field, and the SS field is an integer. Other than these two things, it is what your parser expects.

 

[JrVolt]

It doesn't include data in the video, it generates corresponding .srt files, if video captions are enabled:

1
00:00:00,000 --> 00:00:00,016
<font size="28">SrtCnt : 1, DiffTime : 16ms
2025-04-25 20:11:02.153
[iso : 200] [shutter : 1/60.0] [fnum : 170] [ev : 0] [ct : 5400] [color_md : d_cinelike] [focal_len : 240] [latitude: 44.774913] [longitude: -93.404219] [rel_alt: 46.600 abs_alt: 184.451] </font>

The P4P v2 includes data in the video, if video captions are enabled. However, it does not include the DZOOM field, and the SS field is an integer. Other than these two things, it is what your parser expects.

I see, P4P telemetry syntax Is the same of the Air2, older drone (or firmware, not sure yet) have this kind of telemtry, with bracket and the srt along the video.
However, did you use that !? Where speed data came from ?

- Mini 3P .srt along video file, "new" sytntax ?
- P4P embedded sub with "old style" telemetry
Right ?