You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of the file creation time encoded within the file name, get the call start time from the JSON metadata.
Edit: To add some background. I made a small change to trunk-recorder that more accurately reflect call start time for conventional analog and conventionalP25 calls; compared to the original which was the end of the last recording/file creation time. Sometimes there can be long gaps between this time and when the next call actually starts.
The updated call start time is sent within the JSON metadata. I did not want to mess with renaming the file in trunk-recorder or changing the file creation logic.
The text was updated successfully, but these errors were encountered:
Instead of the file creation time encoded within the file name, get the call start time from the JSON metadata.
Edit: To add some background. I made a small change to trunk-recorder that more accurately reflect call start time for conventional analog and conventionalP25 calls; compared to the original which was the end of the last recording/file creation time. Sometimes there can be long gaps between this time and when the next call actually starts.
The updated call start time is sent within the JSON metadata. I did not want to mess with renaming the file in trunk-recorder or changing the file creation logic.
The text was updated successfully, but these errors were encountered: