Upon further investigation, I noticed that the frame rate (fps) tag in the video file metadata was empty for those videos defaulting to 60 fps, which is my system's native frame rate. Based on this, it appears that JRiver Media Center's frame rate change function relies heavily on the fps tag present in the video file's metadata.
Given these observations, I have the following suggestions to improve the functionality of JRiver Media Center:
1. Automated Frame Rate Detection: It would be beneficial if JRiver Media Center could automatically read the frame rate information from MediaInfo or a similar source, and populate the fps tag in the video file metadata accordingly. This would alleviate the need for manual updates and ensure accurate frame rate adjustments during playback.
2. Batch FPS Tagging Function: Introduce an automated function within JRiver Media Center that allows for batch fps tagging. This function could scan a selected batch of video files and populate the missing fps tags, either based on MediaInfo or internal frame rate detection algorithms.
3. Tag-Independent Frame Rate Adjustment: Another enhancement could be the introduction of a feature that allows JRiver Media Center to adjust the frame rate based on the actual content being played, independent of the fps tag in the video file's metadata. This would serve as a fail-safe for scenarios where the metadata is incomplete or incorrect, ensuring smoother playback.
I realized that a number of my files have empty fps tags, necessitating a time-consuming manual update process. Implementing one or both of the above-mentioned features could significantly improve user experience and functionality. Please, if there is some method already present to accomplish any of these steps, and alleviate the incorrect frame rate display, that would be much appreciated. Thank you.