View Bug Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000368 | DCP-o-matic | Features | public | 2014-06-07 21:11 | 2018-10-17 20:16 |
| Reporter | mhm | Assigned To | carl | ||
| Priority | high | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 2.6.0 | ||||
| Summary | 0000368: Use ffmpegs ebur128 filter when analyzing | ||||
| Description | This is useful to get a picture of the loudness of the source. I think it is enough to present the Integrated Loudness (in LUFS), Loudness Range, LRA (in LU) and the True Peak id dbTP. Here is an example run on a trailer with ffmpeg: $ ffmpeg -i FM_Trailer_V6_ENG_140517.mov -filter_complex ebur128=peak=true -f null - (...) Integrated loudness: Loudness range: True peak: | ||||
| Tags | No tags attached. | ||||
| Branch | |||||
| Estimated weeks required | |||||
| Estimated work required | Average | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-06-07 21:11 | mhm | New Bug | |
| 2014-06-10 14:25 | carl | Assigned To | => carl |
| 2014-06-10 14:25 | carl | Status | new => acknowledged |
| 2014-09-11 23:44 | carl | Relationship added | related to 0000236 |
| 2015-06-07 18:54 | carl | Relationship added | has duplicate 0000589 |
| 2015-06-12 12:20 | carl | Severity | minor => feature |
| 2015-06-12 16:37 | carl | Estimated work required | => Average |
| 2015-06-12 16:37 | carl | Priority | normal => high |
| 2015-08-27 16:56 | carl | Target Version | => 2.x |
| 2015-11-08 23:44 | carl | Target Version | => 2.6.0 |
| 2015-11-18 20:53 | carl | Note Added: 0001000 | |
| 2015-11-18 20:53 | carl | Status | acknowledged => resolved |
| 2015-11-18 20:53 | carl | Resolution | open => fixed |
| 2018-10-17 20:16 | carl | Status | resolved => closed |
