| Summary: | Clip Properties: rounded frame rate, b/s vs kb/s, superfluous digit in audio bitrate | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | qubodup |
| Component: | User Interface | Assignee: | Jean-Baptiste Mardelle <jb> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | fritzibaby, wegwerf-1-2-3 |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | screenshot showing discrepancy between clip properties and ffprobe information | ||
Git commit 65f5f6544cff77e2016e8003e9ebe051d19dd1f2 by Jean-Baptiste Mardelle. Committed on 30/12/2015 at 22:39. Pushed by mardelle into branch 'Applications/15.12'. Fix wrong rounding and other small issues in clip properties display M +14 -13 src/mltcontroller/clippropertiescontroller.cpp http://commits.kde.org/kdenlive/65f5f6544cff77e2016e8003e9ebe051d19dd1f2 Thanks! - As a quick test: 59.94 and 29.97 are the same both in Kdenlive clip properties and ffprobe. - 23.98 (ffprobe) is now reported as 23.976 in the properties. Not sure if there's an issue there. - I noticed that Audio and Video bitrates are now in kb/s rather than KiB/s but the "Bitrate" is still in bits/s though without "b/s" (ffmpeg uses "kb/s" for all three it seems) Git commit c459544a4b8d88b4e2c2ad1109bc43ae413eade8 by Jean-Baptiste Mardelle. Committed on 31/12/2015 at 09:06. Pushed by mardelle into branch 'master'. Fix Bitrate unit M +8 -1 src/mltcontroller/clippropertiescontroller.cpp http://commits.kde.org/kdenlive/c459544a4b8d88b4e2c2ad1109bc43ae413eade8 Thanks! Two possible small issues: 1. (cosmetic) "Frame rate" values are missing " fps" at the end (ffprobe has it) 2. (not sure) "Bitrate" might be better as "Total bitrate", at least that's what the author of http://video.stackexchange.com/questions/11955/ used to differentiate between audio, video and total bitrate. Just for future reference: a 4K video made with a Samsung Galaxy Note 4 reports as 29.99 fps in ffprobe but as Frame rate 29.9898 in kdenlive-git 15.13.0.r6866.e43f3d4-1. I don't know why it has such a weird fps and I can't check (was a rental device). Qubodup, is this bug report still relevant, or can we close it? |
Created attachment 96363 [details] screenshot showing discrepancy between clip properties and ffprobe information Clip properties appears to rounds frame rate to one decimal digit. This turns 59.94 into 59.9 and 29.97 into 30. 1. (issue) frame rate should not be rounded or possibly only rounded to two decimal digits. A workaround is to use external software to find out the actual frame rate. 2. (suggestion) ffprobe reports audio bit rate without decimal digits, i would suggest using the same format. 3. (suggestion) I would suggest using kb/s rather than b/s for Bitrate (without decimal digits), since ffprobe does the same. Possibly with b/s as a mouse-hover tooltip.