[PR #57] [MERGED] Processing timestamps from DJI correctly #130

Closed
opened 2026-03-02 04:00:24 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/eerimoq/moblin/pull/57
Author: @ErAzOr2k
Created: 7/20/2024
Status: Merged
Merged: 7/20/2024
Merged by: @eerimoq

Base: mainHead: NewMain


📝 Commits (8)

  • 9b2c4e6 processing timestamps from DJI correctly
  • 73fbfaf Merge remote-tracking branch 'refs/remotes/origin/main'
  • c46d983 add logger info
  • 3613b83 New timestamps continue
  • 15e4216 New timestamps continue
  • 008a338 New timestamps continue
  • 2764d32 New timestamps continue
  • a65dd38 New Timestamp continue

📊 Changes

2 files changed (+20 additions, -14 deletions)

View changed files

📝 Moblin/RtmpServer/RtmpServerChunkStream.swift (+19 -13)
📝 Moblin/View/Settings/RtmpServer/RtmpServerStreamSettingsView.swift (+1 -1)

📄 Description

With the adjustment, the timestamps transmitted by DJI are processed correctly. A manual specification of the FPS is therefore obsolete.

The difference from the previous calculation of the timestamps is that video and audio now share a common basis. Previously, both were calculated separately.

The next step would be to find out how we can identify the required calculation at runtime, or make some kind of universal solution from it.

Therefore, it can initially only be activated via the debug settings. When the debug setting is enabled, the previous calculation and specification of the FPS are irgnored.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/eerimoq/moblin/pull/57 **Author:** [@ErAzOr2k](https://github.com/ErAzOr2k) **Created:** 7/20/2024 **Status:** ✅ Merged **Merged:** 7/20/2024 **Merged by:** [@eerimoq](https://github.com/eerimoq) **Base:** `main` ← **Head:** `NewMain` --- ### 📝 Commits (8) - [`9b2c4e6`](https://github.com/eerimoq/moblin/commit/9b2c4e6c6e6d55b787d7a4ca4c79ffa1d6be5d2e) processing timestamps from DJI correctly - [`73fbfaf`](https://github.com/eerimoq/moblin/commit/73fbfaf0a240b006bff0c5ca4f419491487eec73) Merge remote-tracking branch 'refs/remotes/origin/main' - [`c46d983`](https://github.com/eerimoq/moblin/commit/c46d98362dc5e45950562ecb510795bbfdd9b2e2) add logger info - [`3613b83`](https://github.com/eerimoq/moblin/commit/3613b839fd183651b2b0a9339f72188f5b895a21) New timestamps continue - [`15e4216`](https://github.com/eerimoq/moblin/commit/15e4216946079168258ae77faef1643bd259ee53) New timestamps continue - [`008a338`](https://github.com/eerimoq/moblin/commit/008a338208c6f73265067d911821661ea8e9115a) New timestamps continue - [`2764d32`](https://github.com/eerimoq/moblin/commit/2764d3208ad3b0c0d5c754f3468096f910966957) New timestamps continue - [`a65dd38`](https://github.com/eerimoq/moblin/commit/a65dd387994a909930b51fff5491358f8f839727) New Timestamp continue ### 📊 Changes **2 files changed** (+20 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `Moblin/RtmpServer/RtmpServerChunkStream.swift` (+19 -13) 📝 `Moblin/View/Settings/RtmpServer/RtmpServerStreamSettingsView.swift` (+1 -1) </details> ### 📄 Description With the adjustment, the timestamps transmitted by DJI are processed correctly. A manual specification of the FPS is therefore obsolete. The difference from the previous calculation of the timestamps is that video and audio now share a common basis. Previously, both were calculated separately. The next step would be to find out how we can identify the required calculation at runtime, or make some kind of universal solution from it. Therefore, it can initially only be activated via the debug settings. When the debug setting is enabled, the previous calculation and specification of the FPS are irgnored. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-02 04:00:24 +03:00
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/moblin#130
No description provided.